This rhymes with sio deciding that your TTY is something other than ttyd0. We had this same problem on Rackable -- even though the proper tty was setup 0x3f8 irq 4 it was being assigned to sio1. You can see this by 'grep sio /var/log/messages'

The only fix for this is to edit /boot/device.hints and reassign the flags to the sio1 interface, like so:

hint.sio.1.at="isa"
hint.sio.1.port="0x3F8"
hint.sio.1.flags="0x10"
hint.sio.1.irq="4"
hint.sio.0.at="isa"
hint.sio.0.port="0x2F8"
hint.sio.0.irq="3"

On Jul 1, 2008, at 8:23 AM, Marian Hettwer wrote:
I installed a recent (as of today) RELENG_7 on one of our HP Blades.
Unluckily my serial output stops right when a getty at ttyd0 should kick
in. So I'm blind for the rest of the startup.
Very unfortunate.
The boot menu, as the bootup itself is printed out on serial console until:
da0: <COMPAQ RAID 0  VOLUME OK> Fixed Direct Access SCSI-5 device
da0: 135.168MB/s transfers
da0: 139947MB (286611840 512 byte sectors: 255H 32S/T 35124C)
Trying to mount root from ufs:/dev/da0s1a
bce0: link state changed to DOWN
bce0: link state changed to UP
bce1: link state changed to UP

Which is, what I think, the point when init should take over and spawn a
serial console on ttyd0, according to my /etc/ttys:
# grep ttyd0 /etc/ttys
ttyd0   "/usr/libexec/getty std.9600" vt100   on secure

# cat /boot/loader.conf
comconsole_speed="9600"
console="vidconsole,comconsole" # A comma separated list of console(s)
boot_multicons="-D"   # -D: Use multiple consoles
boot_serial="-h"              # -h: Use serial console

# uname -a
FreeBSD db46-202.mobile.rz 7.0-STABLE FreeBSD 7.0-STABLE #0: Tue Jul 1 14:59:43 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ GENERIC
amd64

The blade itself is a HP BL465c G5

Any ideas? I don't have this blade for a long time, so I'm a bit in a
hurry.
In fact, right now I'm testing this setup against a Debian 4.0 with Linux
2.6.25.9 under MySQL load, and up until now the machine looks good.
If I wind up with a fully working, nearly as fast and stable as our linux boxes installation, I'd might be able to convince "the boys at work" to
give FreeBSD a try.
And in a 600 server setup, I'd be thrilled to do so :-)
So lets get started with this serial console issue... which is indeed a
pain :(

TIA,
Marian

_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED] "

--
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source and other randomness


_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to