Re: [SLE] Serial Console...

Sorry it has been so long, but I've only now gotten back to this. So, here's where I'm at. Tried to run the below setup. In fact, also ran the agetty direct from the command line. It seems to keep dying and then being respawn by init, so the inittab option is just broken. When running the command line version, I get a whole lot of garbage... it seems to try many different things, then exits. I know the serial port is connected right, because I see the boot messages during startup, but once the machine is up, I never get a login on the serial port... Any helpful hints or advice would be much appreciated. TIA - Herman # strace /sbin/agetty -L 9600 ttyS0 vt100 ( a whole lot of this, where the "read" line chages to different values , but also ends up wit the same result) -------------8<-------------- fcntl(3, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}) = 0 read(3, "\10\0\0\0y\25\0\0pts/2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 384) = 384 fcntl(3, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}) = 0 rt_sigaction(SIGALRM, {SIG_DFL}, NULL, 8) = 0 alarm(0) = 1 alarm(0) = 0 rt_sigaction(SIGALRM, {0x400fcf80, [], 0x4000000}, {SIG_DFL}, 8) = 0 alarm(1) = 0 fcntl(3, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}) = 0 read(3, "\10\0\0\0\202\25\0\0pts/9\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 384) = 384 fcntl(3, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}) = 0 rt_sigaction(SIGALRM, {SIG_DFL}, NULL, 8) = 0 alarm(0) = 1 alarm(0) = 0 rt_sigaction(SIGALRM, {0x400fcf80, [], 0x4000000}, {SIG_DFL}, 8) = 0 alarm(1) = 0 fcntl(3, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}) = 0 read(3, "\10\0\0\0\343\25\0\0pts/10\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 384) = 384 fcntl(3, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}) = 0 rt_sigaction(SIGALRM, {SIG_DFL}, NULL, 8) = 0 --- SIGALRM (Alarm clock) --- +++ killed by SIGALRM +++ Mike Kenzie wrote:

I have got them to work. It takes a little tweaking. I often get the respawing too fast message.

I run it through strace and it connects.

I can then see where the trouble lies.

I use

S0:123:respond:/sbin/agetty -mL 19200,9600,2400 ttyS0

As a test to see if the port is open try

echo junk > /dev/ttyS0 or the port of your choice

you should see "junk" on the terminal screen if there is nothing then the ports are not connected, if you see stuff but not "junk" then the comm settings are off. Check the baud and parity.

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/