Date: Wed, 16 Nov 2005 21:03:36 -0800 From: Joe Rhett <jrhett@svcolo.com> To: hardware@freebsd.org Subject: com1 incorrectly associated with ttyd1, com2 with ttyd0 Message-ID: <20051117050336.GB67653@svcolo.com>
next in thread | raw e-mail | index | archive | help
This is funny. This is true in both 5.4-RELEASE and 6.0-RELEASE
1. Plug serial connection into com1, configure as console
2. Edit /etc/ttys, enable ttyd0
3. set console=comconsole in /boot/loader.conf
4. Boot system (generic kernel) -- all output goes to com1
5. No login prompt...
Edit /etc/ttys, enable ttyd1
kill -HUP 1
Login prompt
devinfo -r shows
sio0
Interrupt request lines:
0x3
I/O ports:
0x2f8-0x2ff
sio1
Interrupt request lines:
0x4
I/O ports:
0x3f8-0x3ff
So... so COM1 is sio0/ttyd0 until the system finishes booting, at which time
it swap with com2 and becomes sio1/ttyd1 ?
NOTE: in the BIOS I've assigned 3f8/int4 to serial B, and 2f8/int3 to
serial A. But why would sio assignments be tied to the hardware order
instead of the io assignments? And better yet, why would they swap during
the boot process?
I'm more than happy to gather debug. I have a toy server set aside just to
play with this stuff. Tell me what you need.
--
Joe Rhett
senior geek
SVcolo : Silicon Valley Colocation
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051117050336.GB67653>