public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Koch <efraim@clues.de>
To: linux-kernel@vger.kernel.org
Subject: getting my serial ports back? ;-)
Date: Sat, 11 Jan 2003 11:12:42 +0100	[thread overview]
Message-ID: <20030111101241.GA3589@clues.de> (raw)

What do I have to do to get my serial ports back?

devfs: v1.22 (20021013) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
pnp: the driver 'serial' has been registered
pnp: pnp: match found with the PnP device '00:0f' and the driver 'serial'
pnp: the device '00:0f' has been activated
devfs_register(tts/2): could not append to parent, err: -17
tts/2 at I/O 0x3e8 (irq = 4) is a 16550A
pnp: pnp: match found with the PnP device '00:10' and the driver 'serial'
pnp: the device '00:10' has been activated
devfs_register(tts/3): could not append to parent, err: -17
tts/3 at I/O 0x2e8 (irq = 3) is a 16550A

Effectively as my mouse is on the serial port and it
obviously does not work in gpm or with X directly.

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

That's coming from gpm startup, at least one of it, although
I have /dev/tts/0 in my gpm.conf... Ah, it's hardcoded in the
binary, it seems (doing a strings on it).

Anyway, does anyone have a clue as to why my serial modules
are not working any longer since 2.5.53 (and neither 2.5.55)?
I am not missing it much for X but at least gpm is a good
thing.

Thanks,
Alexander


             reply	other threads:[~2003-01-11  9:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-11 10:12 Alexander Koch [this message]
2003-01-11  9:44 ` getting my serial ports back? ;-) Russell King
2003-01-11 12:52   ` Alexander Koch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030111101241.GA3589@clues.de \
    --to=efraim@clues.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox