On Fri, 2004-02-27 at 13:13, Peter Onion wrote:
On Fri, 2004-02-27 at 12:33, Matt Parker wrote:
Hi All,
I've got 3 boxen I want to use in my configuration - 2 RedHat 7.3 boxen (one running Oracle 9i, one running IBM WebSphere) and 1 Mandrake 9.1 box. I've got 1 two-port KVM switch so I can view one of the RedHat boxen as well as my Mandrake desktop. The problem is that I cannot get the other RedHat box to boot in headless mode (I don't want to reinstall since a lot of time and effort went into getting Oracle and WebSphere set up correctly). I've tried using serial cable/minicom for the second box, but no joy. Anyone here managed to get Linux/x86 booting in headless mode?
How does it fail ?
Who knows? I'm trying to run it headless!!!
Matt
On Fri, 2004-02-27 at 13:27, Matt Parker wrote:
On Fri, 2004-02-27 at 13:13, Peter Onion wrote:
On Fri, 2004-02-27 at 12:33, Matt Parker wrote: How does it fail ?
Who knows? I'm trying to run it headless!!!
Matt
So you turn it on and it does absolutly nothing ?
Peter
On Fri, 2004-02-27 at 13:38, Peter Onion wrote:
On Fri, 2004-02-27 at 13:27, Matt Parker wrote:
On Fri, 2004-02-27 at 13:13, Peter Onion wrote:
On Fri, 2004-02-27 at 12:33, Matt Parker wrote: How does it fail ?
Who knows? I'm trying to run it headless!!!
Matt
So you turn it on and it does absolutly nothing ?
Peter
No, I've nothing to view output on...it stalls somewhere in the boot-up process.
Matt
On Fri, Feb 27, 2004 at 01:46:41PM +0000, Matt Parker wrote:
On Fri, 2004-02-27 at 13:38, Peter Onion wrote:
On Fri, 2004-02-27 at 13:27, Matt Parker wrote:
On Fri, 2004-02-27 at 13:13, Peter Onion wrote:
On Fri, 2004-02-27 at 12:33, Matt Parker wrote: How does it fail ?
Who knows? I'm trying to run it headless!!!
Matt
So you turn it on and it does absolutly nothing ?
Peter
No, I've nothing to view output on...it stalls somewhere in the boot-up process.
Well surely the first thing to do is to connect a monitor, you should then be able to see where it's stopping. Connecting the monitor is unlikely to have any effect, especially an old VGA one if you have one lying around.
On Fri, 2004-02-27 at 13:48, Chris Green wrote:
On Fri, Feb 27, 2004 at 01:46:41PM +0000, Matt Parker wrote:
On Fri, 2004-02-27 at 13:38, Peter Onion wrote:
On Fri, 2004-02-27 at 13:27, Matt Parker wrote:
On Fri, 2004-02-27 at 13:13, Peter Onion wrote:
On Fri, 2004-02-27 at 12:33, Matt Parker wrote: How does it fail ?
Who knows? I'm trying to run it headless!!!
Matt
So you turn it on and it does absolutly nothing ?
Peter
No, I've nothing to view output on...it stalls somewhere in the boot-up process.
Well surely the first thing to do is to connect a monitor, you should then be able to see where it's stopping. Connecting the monitor is unlikely to have any effect, especially an old VGA one if you have one lying around.
Perhaps I'm not explaining myself well. It (both) RedHat boxen boot-up just fine with monitor/keyboard/mouse attached, but will not boot up without (what I want). So I have no idea where it's going wrong. I don't get anything in /var/log/messages on a failed bootup, so it's stopping somewhere before syslogd gets started. That's all I know.
Matt
On Fri, Feb 27, 2004 at 02:39:31PM +0000, Matt Parker wrote:
No, I've nothing to view output on...it stalls somewhere in the boot-up process.
Well surely the first thing to do is to connect a monitor, you should then be able to see where it's stopping. Connecting the monitor is unlikely to have any effect, especially an old VGA one if you have one lying around.
Perhaps I'm not explaining myself well. It (both) RedHat boxen boot-up just fine with monitor/keyboard/mouse attached, but will not boot up without (what I want). So I have no idea where it's going wrong. I don't get anything in /var/log/messages on a failed bootup, so it's stopping somewhere before syslogd gets started. That's all I know.
Yes, I think I do understand, connect *just* the monitor. The Redhat box will almost certainly still fail to boot in the same way that it fails without keyboard, mouse and monitor. While one could possibly program in something that would complain about a missing monitor I've never seen it, from the boot process' point of view 'no monitor' is equivalent to a very basic monitor of some sort so it should still boot OK.
I'm pretty certain you'll find that it's the missing keyboard that's stopping it booting, you may be able to change the BIOS to bypass that.
On 27 Feb 2004, at 2:39 pm, Matt Parker wrote:
Perhaps I'm not explaining myself well. It (both) RedHat boxen boot-up just fine with monitor/keyboard/mouse attached, but will not boot up without (what I want). So I have no idea where it's going wrong. I don't get anything in /var/log/messages on a failed bootup, so it's stopping somewhere before syslogd gets started. That's all I know.
Matt
I think the problem is more likely to be the missing mouse and/or keyboard than the monitor, I would put a monitor on because you have zero chance of seeing what's wrong without one. If it works with a monitor and no mouse/keyboard then it's the monitor.
Regards, Rob.
Hi Matt
Often there is a bios setting that aborts the boot process if no keyboard and/or monitor is detected. I'd suggest looking in there to start with.
Bios setup is usually launched by pressing the Del key at power on time.
Regards, Paul.
On Friday 27 February 2004 2:39 pm, Matt Parker wrote:
Perhaps I'm not explaining myself well. It (both) RedHat boxen boot-up just fine with monitor/keyboard/mouse attached, but will not boot up without (what I want). So I have no idea where it's going wrong. I don't get anything in /var/log/messages on a failed bootup, so it's stopping somewhere before syslogd gets started. That's all I know.
On Fri, 2004-02-27 at 14:55, Robert Tillyard wrote:
On 27 Feb 2004, at 2:39 pm, Matt Parker wrote:
Perhaps I'm not explaining myself well. It (both) RedHat boxen boot-up just fine with monitor/keyboard/mouse attached, but will not boot up without (what I want). So I have no idea where it's going wrong. I don't get anything in /var/log/messages on a failed bootup, so it's stopping somewhere before syslogd gets started. That's all I know.
Matt
I think the problem is more likely to be the missing mouse and/or keyboard than the monitor, I would put a monitor on because you have zero chance of seeing what's wrong without one. If it works with a monitor and no mouse/keyboard then it's the monitor.
Finally, got it going. One of the machines has an Award BIOS and I found a setting in there "Halt On" and changed it to "All except keyboard". The other machine has a Compaq BIOS with no such setting, but it's OK, I can have that one on my KVM switch.
So now I have the marvellously spec'd machines:-
Compaq Deskpro 233MHz, 9Gb HDD, 512Mb RAM running Oracle 9i AMD K62-450MHz, 13Gb HDD, 384Mb RAM running WebLogic and WebSphere
Slow, but usable for development purposes...
Thanks for the help all,
Matt
-
Chris Green -
Matt Parker -
Paul -
Peter Onion -
Robert Tillyard