Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Disabled COM1: ttyS0: LSR safety check engaged!

1,028 views
Skip to first unread message

Jon

unread,
Mar 5, 2003, 2:30:05 AM3/5/03
to
Hi all.

Recently I got cable internet access. So I removed my serial-port 56k modem
and decided to disable COM1 in the BIOS. My computer does not have a
keyboard or mouse attached, never has.


Now when I boot, I get the following lines that weren't there before:

Detected PS/2 Mouse Port.
keyboard: Timeout - AT keyboard not present?(ed)
keyboard: Timeout - AT keyboard not present?(f4)

and a little further down...

ttyS0: LSR safety check engaged!
ttyS0: LSR safety check engaged!


Why would I be getting these just because I disabled COM1? And are they a
problem? I haven't noticed any problem but just curious.


Thanks
Jon

--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Jack Pistachio

unread,
Mar 5, 2003, 6:20:07 AM3/5/03
to
Not sure about the keyboard error, but the LSR safety check
messages are because setserial is trying to load your
autosaved seriel port settings, which are now different.
To update it (and thus fix the error message) do the
following:

man setserial
setserial /dev/ttyS0 autoconfig
setserial /dev/ttyS0 autoconfig
(not sure why but sometimes I've had to actually do this
twice)

then remove the 1st line in /etc/serial.conf if it is
###PORT STATE GENERATED USING AUTOSAVE-ONCE###

That should update your serial ports to the new settings.
-jackp


--- Jon <jmd...@myrealbox.com> wrote:
> Hi all.
>
> Recently I got cable internet access. So I removed my
> serial-port 56k modem
> and decided to disable COM1 in the BIOS. My computer does
> not have a
> keyboard or mouse attached, never has.
>
>
> Now when I boot, I get the following lines that weren't
> there before:
>
> Detected PS/2 Mouse Port.
> keyboard: Timeout - AT keyboard not present?(ed)
> keyboard: Timeout - AT keyboard not present?(f4)
>
> and a little further down...
>
> ttyS0: LSR safety check engaged!
> ttyS0: LSR safety check engaged!
>
>
> Why would I be getting these just because I disabled
> COM1? And are they a
> problem? I haven't noticed any problem but just curious.
>
>
> Thanks
> Jon


__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/

Jon

unread,
Mar 5, 2003, 6:40:09 AM3/5/03
to
Thanks Jack, I hadn't thought of setserial.

On my Sarge system I don't have a /etc/serial.conf

But I do have a /var/lib/setserial/autoserial.conf

I just ran dpkg-reconfigure setserial and chose the 'manual' option for
editing the config file. Then I commented out the line for /dev/ttyS0.

Rebooted to check the output and the message is gone. I really should learn
the Debian way for these kind of things but for now that'll do. And the
keyboard error has most likely always been there, didn't notice.


Thanks
Jon.

Tauno Voipio

unread,
Mar 5, 2003, 6:50:48 AM3/5/03
to

"Jon" <jmd...@myrealbox.com> wrote in message
news:20030305073005$52...@gated-at.bofh.it...

> Hi all.
>
> Recently I got cable internet access. So I removed my serial-port 56k
modem
> and decided to disable COM1 in the BIOS. My computer does not have a
> keyboard or mouse attached, never has.
>
>
> Now when I boot, I get the following lines that weren't there before:
>
> Detected PS/2 Mouse Port.
> keyboard: Timeout - AT keyboard not present?(ed)
> keyboard: Timeout - AT keyboard not present?(f4)
>
> and a little further down...
>
> ttyS0: LSR safety check engaged!
> ttyS0: LSR safety check engaged!
>
>
> Why would I be getting these just because I disabled COM1? And are they a
> problem? I haven't noticed any problem but just curious.
>

If you want to get rid of the messages, re-enable COM1 in the BIOS.
/dev/ttyS0 is the same thing as COM1 in Windowspeak.

HTH

Tauno Voipio
tauno voipio @ iki fi


Rob Weir

unread,
Mar 8, 2003, 7:40:14 AM3/8/03
to
On Wed, Mar 05, 2003 at 10:15:51PM +1100, Jon wrote:
> Rebooted to check the output and the message is gone. I really should learn
> the Debian way for these kind of things but for now that'll do. And the
> keyboard error has most likely always been there, didn't notice.

Yeah, that error just means that the kernel can't find an AT keyboard
(duh). My gateway has it too, but the kernel doesn't seem to care after
boot.

--
Rob Weir <rw...@ertius.org> http://ertius.org/

0 new messages