From: Daniel Lang <dl@leo.org> To: freebsd-hackers@freebsd.org Subject: Problems with Serial Console Message-ID: <20001006093627.A17383@atrbg11.informatik.tu-muenchen.de>
next in thread | raw e-mail | index | archive | help
Hiho, I have some problems with serial console now under 4.1-STABLE. Ok, this is how I set it up: Flags set for sio0, plugged in cable to terminal-server. dmesg: [..] sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa 0 sio0: type 16550A, console [..] /etc/make.conf: [..] BOOT_COMCONSOLE_PORT= 0x3F8 [..] /boot.config: -Dh This works so far: The boot sequence can be monitored (and changed for e.g. set single-user in loader prompt, visual user config works, too, etc) on the terminal. Now the problem is: I cannot write anything to /dev/console, this just blocks (after the system is up). I realized this, because syslog stopped working, when it tried to do so. I got around this, telling syslog not to write to /dev/console but to /dev/cuaa0. This is another strange thing. The handbook and examples tell, you should use /dev/ttyd0 to run a getty. This did not work either, same problem: I cannot write anything to /dev/ttyd0, it blocks, too. But I got around this by using cuaa0, /etc/ttys: [..] cuaa0 "/usr/libexec/getty std.9600" vt100 on secure [..] Maybe somehow, /dev/console is redirected to /dev/ttyd0 and so both don't seem to work. Well I could live with using /dev/cuaa0 instead, but there comes another problem. When syslog is first started during boot, it complains, it cannot open /dev/cuaa0, because the device is busy. It doesn't hang, but it doesn't write anything to it. Later, if the machine is up, I can send a HUP to syslog, and then it's able to use /dev/cuaa0, without any complaint (and the getty is set up and working, too). Any suggestions ? Best regards, Daniel Lang -- IRCnet: Mr-Spock - ceterum censeo Microsoftinem esse delendam - *Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001006093627.A17383>