|
FreeBSD General Other questions regarding FreeBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
|||
getty dies on serial console?
Hi Everyone
I have a small but extremely annoying problem. when connecting to to my freebsd serial console if I hit the <Enter> key then the getty will die?! (or sometimes hang...and I'm not able not log in anymore ) If I type "root" directly (or any other username) instead I will the get the password prompt and everything works fine. Once I'm logged in through the serial connection then also everything works fine. On my linux box if I hit enter I just get the login prompt displayed again. Anyone having similar problem? Any hints why the getty just dies? (It's not being restarted by init either I have restart it manually from the command line) Thanks in advance Michael Quote:
Quote:
|
|
|||
Can you find any error messages about the dying getty in the log files?
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
|||
The only message I get is sometimes in /var/log/messages:
getty[81323]: login_tty /dev/ttyd0: Device not configured But I don't know if it's related...it might just be me trying to start another getty from the command line..otherwise I don't get any messages or core files... Is there some way to get getty to be more verbose? //Michael |
|
|||
The error message mentions /dev/ttyd0, which is a so-called call-in port. From http://www.freebsd.org/doc/en_US.ISO...ok/serial.html
Quote:
Or try to use 3wire.9600 instead of std.9600 in the "/etc/ttys" file as recommended in the FreeBSD handbook (24.3.3 Troubleshooting Your Connection)
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
|||
I tried both 3wire.9600 and std.9600 but without success...
The cable I'm using is a standard null modem cable bought in the store which worked fine om my linux box. Note that I only have trouble during the login phase: Quote:
login prompt but here the getty/login hangs and get unresponsive. Once I'm logged in everything works fine...Thats why I suspect getty or login....I'll try to get hold of multimeter tomorrow to check the cable physically. //Michael |
|
|||
Just tried to connect from serial2 to serial1 on my freebsd using cu
and get exactly the same behavior.. This starts to drive me crazy //Michael |
|
|||
I only use a serial console from OpenBSD to OpenBSD. Never experienced problems like you.
Did you have this problem on a previous version of FBSD or is just 7.0 ?
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
|||
I did not use serial console in previous versions...and at the moment I only have
one freebsd machine (7.0). I tried the getty from freebsd 6.3 but it's the same behavior.... I begin to suspect that it's either the cable (tried 2 different null modem cables) or the login program which really is the problem.. //Michael Last edited by michaelk; 15th May 2008 at 07:31 AM. |
|
|||
I did some more testing and this seems hardware related.
I installed freebsd on old HP vectra and there it works... while on my compaq deskpro (also old) it doesn't work On the machine the it works I have: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console While on the machine that it doesn't I have: sio0: <Standard PC COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console Same settings on both machines... I also managed to find a work around...When the login hangs I can press ^D (ctrl-D => eof ) twice which will respawn a new getty and enables me to log in. (so I'm not stuck any more ) //Michael |
|
|||
In earlier times a motherboard had a physical 16550 serial chip. Later the serial chip was integrated in a separate I/O chip. Maybe the serial emulation of the problematic motherboard is not completely following the 16550 specs, and hence gives problems.
But at least you now have found a work-around.
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
Tags |
serial console getty |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
init: can't exec getty after power failure | mtx | FreeBSD General | 0 | 20th January 2009 10:14 AM |
Controlling a RS-232 Serial Console from a Shell Script | ishikawanakano | Programming | 0 | 9th January 2009 10:00 PM |
Setting up the serial console | PeterSteele | FreeBSD General | 6 | 3rd November 2008 04:42 PM |
Serial connections | JMJ_coder | General software and network | 9 | 25th July 2008 03:28 PM |
cyrus-sasl2 dies | chavez243 | FreeBSD Ports and Packages | 9 | 10th May 2008 03:01 PM |