Serial console only works if set tty com0 is specified in boot.conf
Hi all, I'm having a strange problem. I wanted to get a serial console working, but not necessarily divert the console to the serial port at boot time, so what I did was just edit /etc/ttys as specified in FAQ part 7.7 and rehupped getty. I couldn't get a peep out of /dev/tty00 (despite ps showing getty was running on /dev/tty00), so I ran fstat /dev/tty00 and nothing showed up. Then I rebooted and checked again. Still nothing in fstat, nothing on the serial port, and getty was still running on /dev/tty00. I added 'set tty com0' to /etc/boot.conf, rebooted, and then logged in and ran fstat /dev/tty00 to be greeted with 3 lines saying getty finally grabbed the serial port. The serial connection worked fine. So I'm just a bit confused here. Are we meant to have 'set tty com0' in boot.conf if we are to get serial console working in amd64? I tested this on 4 different machines, some were 4.4-release, others 4.4-stable and they had the same result. I haven't tried i386 yet as I don't have OpenBSD on any i386 platforms. I could just keep the 'set tty com0' in there, but I would like to know why I can't just have getty grab /dev/tty00 when told? Without the 'set tty com0', I was able to load up minicom, and specify /dev/cua00 and have it talk to minicom on a machine on the other side of the null modem cable. (I was able to echo characters back and forth.) Perhaps getty is silently failing because it can't open /dev/tty00? Thanks, Tom
Re: Serial console only works if set tty com0 is specified in boot.conf
On Fri, Jan 30, 2009 at 11:12 PM, Tom wrote: > Hi all, > > I'm having a strange problem. I wanted to get a serial console working, > but not necessarily divert the console to the > serial port at boot time, so what I did was just edit /etc/ttys as specified > in FAQ part 7.7 and rehupped getty. I couldn't > get a peep out of /dev/tty00 (despite ps showing getty was running on > /dev/tty00), so I ran fstat /dev/tty00 and > nothing showed up. Then I rebooted and checked again. Still nothing in > fstat, nothing on the serial port, and getty > was still running on /dev/tty00. > Hi Tom, The /etc/boot.conf deals with loading the kernel - adding "set tty com0" tells the kernel to use com0 as the default console. Using boot.conf won't solve your serial console issue man 4 cua might help... Fred
Re: Serial console only works if set tty com0 is specified in boot.conf
I have exactly the same problem. When i redirect default console to com0 (set tty com0 in /etc/boot.conf) serial console on tty00 then is working. But when i don't want to have default console there, then serial access is not working, but /usr/lib/getty std.9600 tty00 is running Only if i edit /etc/ttys and replace tty00 with cua00 - serial console is then working fine. Is this some bug ? -- View this message in context: http://www.nabble.com/Serial-console-only-works-if-set-tty-com0-is-specified-in-boot.conf-tp21757534p22179579.html Sent from the openbsd user - misc mailing list archive at Nabble.com.
