On Mon, 3 Feb 2003, Terry Lambert wrote:
Lucky Green wrote:
However, the Intel L440gx+ motherboard I have (it came in a VA Linux
rackmount) seems to have a separate CPU performing all kinds of
monitoring tasks, watchdog, etc, so I was hoping this separate CPU was
actually performing the
On Tue, 4 Feb 2003, Andrew Gordon wrote:
- On the latest machines featuring 'serial over LAN', you can
persuade the management CPU to subvert the serial port and
pass the data over one of the ethernet ports. This seems to use
a proprietary protocol, but if you have one Windows
Hello,
The sense of the -P option was changed, and it makes it so you have to
do extra work to get the console driver to do the right thing from
inside FreeBSD proper, on a machine that could have its keyboard removed
(or not). It's because the -h is implied, and it's a toggle.
Oh, I see
Hello,
This motherboard provides access to the BIOS via sio1. When booting, the
serial BIOS shows everything that's happening until the point of booting
the kernel (where it seems to switch video modes to have a bright white
character set rather than the dull white/grey characters used
From: Lucky Green [mailto:[EMAIL PROTECTED]]
1) Is there a way to prevent the FreeBSD kernel from ever
switching into
this different video mode, thus allowing me to continue to use the
built-in serial terminal? The machine is a headless server, I
don't care
if video works as long as I
Lucky Green wrote:
I have a dual PIII Intel L440gx+ (VA Linux) server. I am running CURRENT
cvsupped a few hours ago.
This motherboard provides access to the BIOS via sio1. When booting, the
serial BIOS shows everything that's happening until the point of booting
the kernel (where it seems
Attila Nagy wrote:
I think you need to read the Serial Console section of the Handbook.
You will find it here:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html
This is actually no longer accurate. PHK changed the defaults, and
it no longer does correct
Hello,
This is actually no longer accurate. PHK changed the defaults, and it
no longer does correct autodetection from the boot loader config file.
It may be my fault, but I could set up a serial console to a 5.0-RELEASE
box using this page.
5.0 uses hints, I think this is the only change, I
Attila Nagy wrote:
This is actually no longer accurate. PHK changed the defaults, and it
no longer does correct autodetection from the boot loader config file.
It may be my fault, but I could set up a serial console to a 5.0-RELEASE
box using this page.
5.0 uses hints, I think this is
From: Terry Lambert [mailto:[EMAIL PROTECTED]]
...
Anyway, it was a particular problem with the SuperMicro motherboards
with the AMI BIOS that's been the subject of the rest of this
discussion (i.e. the ones that kick out the escape sequence at the
end, for no good reason, except to screw
Don Bowman wrote:
Anyway, it was a particular problem with the SuperMicro motherboards
with the AMI BIOS that's been the subject of the rest of this
discussion (i.e. the ones that kick out the escape sequence at the
end, for no good reason, except to screw up non-monochrome VTxxx
Attila wrote:
The reason that you lost the serial console after the kernel started is
that you BIOS from that point is launched to the nearest galaxy's
trashcan via hyperspace, I mean is not functional. You have to set up
the serial console.
A good answer on your average
Lucky Green wrote:
However, the Intel L440gx+ motherboard I have (it came in a VA Linux
rackmount) seems to have a separate CPU performing all kinds of
monitoring tasks, watchdog, etc, so I was hoping this separate CPU was
actually performing the serial console task.
According to Doug's Intel
On Mon, 3 Feb 2003, Lucky Green wrote:
However, the Intel L440gx+ motherboard I have (it came in a VA Linux
rackmount) seems to have a separate CPU performing all kinds of
monitoring tasks, watchdog, etc, so I was hoping this separate CPU was
actually performing the serial console task. As
14 matches
Mail list logo
