[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#105451: update

[please retain the CC to the bug tracking system]

Andrew Young <aty@sciences.sdsu.edu> writes:

> >> So the problem is still: how to get ttyS14 working so I can use the
> >> modem?
> > 
> > No idea.  It's a kernel issue, i would gather. 
> > 
> > You are using the ppp on ttyS14 to install base, right?
> No.  I installed the base system from floppies.  But I need the modem up
> to get the rest of the stuff off the Net.  I'm trying to get ppp going,
> but pppd says "No such device" when I try to use the modem.

Oh.  Is the original bug closable then?

If the device in /dev/ wasn't there but should have been, that's a bug
in the 'makedev' package, btw, that you might want to file.

If the kernel is not seeing a port that it should, that would be a bug
in kernel-image-2.2.19 or whatever you used.

> I *have* setserial installed, from the floppies.  But when I try to use it
> to configure the ttyS14 port, I get "No such device" -- even though ls -l
> /dev/ttyS14 indicates the device is there.  Any other ideas?  Remember,
> the hardware itself works -- I've been using this modem on /dev/cua14 for
> 5 years with the old Slackware kernel.

Well, maybe the kernel is not detecting it (whereas the slackware one
did).  Its possible slackware has a hacked kernel which looks for more
serial devices.

Maybe the device is coming  up as some other device, rather than
/dev/ttyS14.  I mean, you're just putting it at ttyS14 arbitrarily,
right?  Why not ttyS4 or something?

Maybe you need one of the binary only drivers, e.g., as discussed on 
http://www.toppoint.de/~chl/linux_on_512t.html ?

You've looked through all the kernel output it gives at bootup?  That
should be visible with 'dmesg |less' or looking in /var/log/messages .

This really feels like more of a hardware/kernel issue than Debian
issue, really.

.....Adam Di Carlo....adam@onshore.com.....<URL:http://www.onshored.com/>

Reply to: