On Sat, 24 Apr 1999 20:17:00 +0200, Miquel van Smoorenburg wrote: >In article <[EMAIL PROTECTED]>, >Ralf G. R. Bergs <[EMAIL PROTECTED]> wrote: >>I followed the instructions in /usr/src/linux/Documentation/serial- >>console.txt in order to control a Debian box from a serial terminal. > >That should work. The guy who wrote the serial console kernel stuff, >also wrote sysvinit, and also happens to maintain the Debian sysvinit >package :)
I'm aware of that, and I know that YOU are the guy. :) >>There IS "some" output on the screen, but it's not nearly as much as appears >>on the VGA console, nor can I login on the serial console. > >Did you: > >a) create a new /dev/console > crw-rw-rw- 1 root root 5, 1 Apr 24 10:22 /dev/console Ok, I'm an idiot. :-( I DID check that the device nodes are ok, but obviously I checked them on the wrong system. :-/ (I have several Linux boxes at home, and I was logged in on a different one to do some sysadmin stuff.) >b) run a getty on /dev/ttyS0 (or S1, or whatever) > S1:23:respawn:/sbin/getty -L 9600 ttyS1 No, I did not. I was under the impression that I need not explicitly start a getty on the serial line if the kernel command-line contains "console=ttyS0,9600". I thought that a line like this would make the serial console EXACTLY the same as the VGA console, i.e. that I could use both in parallel (everything gets output to both the VGA and serial console, and everything I type on each console gets accepted.) Ok, now that I corrected /dev/console and started a getty on /dev/ttyS0 my setup is working almost as intended with one exception: If I include append="console=tty0 console=ttyS0,9600" in my lilo.conf EVERYTHING that one would expect gets output to the serial console, BUT there's a lot of stuff missing on the VGA console. If I reverse the two "console" statements above, the output changes accordingly (everything appears on the VGA console, but only a subset appears on the serial console.) The problem seems to be related to kernel logging (klogd), since klogd doesn't log ALL messages to syslogd either (there are the SAME lines missing in /var/log/kern.log as in the cases described above.) I already tried starting klogd with "-c 8" but to no avail. The volume of output doesn't change. I also tried the "debug" kernel command-line parameter -- didn't help either. Any idea that could make me happy again? :) Thanks, Ralf -- Sign the EU petition against SPAM: L I N U X .~. http://www.politik-digital.de/spam/ The Choice /V\ of a GNU /( )\ Generation ^^-^^
