Date: Sat, 31 Jan 2009 12:09:28 -0700 From: Tim Judd <tajudd@gmail.com> To: Martin Schweizer <office@pc-service.ch>, freebsd-questions@freebsd.org Subject: Re: Using Serial Port Other Than sio0 for the Console Message-ID: <ade45ae90901311109x3cc9454j58027bfd6571b4cd@mail.gmail.com> In-Reply-To: <20090130172843.GB89911@saturn.pcs.ms> References: <20090130172843.GB89911@saturn.pcs.ms>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 30, 2009 at 10:28 AM, Martin Schweizer <lists_freebsd@bluewin.ch > wrote: > Hello > > I want to use sio1 for console access. I read chapter 26.6 in the handbook > and did the following: > > /boot.config: > -P > > /boot/device.hints: > [snip] > hint.sio.0.at="isa" > hint.sio.0.port="0x3F8" > ### hint.sio.0.flags="0x10" > hint.sio.0.irq="4" > hint.sio.1.at="isa" > hint.sio.1.port="0x2F8" > hint.sio.1.flags="0x10" > hint.sio.1.irq="3" > [snip] > > My custom kernel: > [snip] > device sio > [snip] > > /var/run/dmesg.boot: > [snip] > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 on acpi0 > sio0: type 16550A > sio0: [FILTER] > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on > acpi0 > sio1: type 16550A, console > sio1: [FILTER] > [snip] > > /etc/ttys: > [snip] > ttyd0 "/usr/libexec/getty std.9600" vt100 on secure > ttyd1 "/usr/libexec/getty std.9600" vt100 on secure > ttyd2 "/usr/libexec/getty std.9600" vt100 on secure > ttyd3 "/usr/libexec/getty std.9600" vt100 on secure > [snip] > > The baud rate etc. are correct as well (the standard settings). > > The problem is I get no connection. I'm sure that my terminal works correct > because I can connect other FreeBSD sever over the serial cable but not the > above. > Any ideas? > > Kind regards, > > -- > > Martin Schweizer > <office@pc-service.ch> > > PC-Service M. Schweizer GmbH; Bannholzstrasse 6; CH-8608 Bubikon > Tel. +41 55 243 30 00; Fax: +41 55 243 33 22; http://www.pc-service.ch; > public key : http://www.pc-service.ch/pgp/public_key.asc; > fingerprint: EC21 CA4D 5C78 BC2D 73B7 10F9 C1AE 1691 D30F D239; > Surprised nobody's really responded. Enabling serial logins on ttyd1 (COM2 in Microsoft terms) is on -- it's defined in your ttys. The guaranteed "enabling" is to restart, but I've heard that sigHUP init will reread ttys and enable logins (but I hadn't got that to work yet). Enabling serial as your console output (in terms of the boot process and everything) should be, if available, enabled in /boot/loader.conf There doesn't seem to be a setting to enable COM2 as your console device, the only options (by reading through /boot/defaults/loader.conf) is to enable comconsole, which runs over COM1 You would likely have to hack the bootloader files in source and reinstall to get that kind of functionality. Does this help? let me know if you want more help. I like enabling serial console for the fact that you can get into out-of-bounds management this way easily. --Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ade45ae90901311109x3cc9454j58027bfd6571b4cd>