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

Bug#105451: update

Please do not just reply to me, retain the CC to the other addesses,
especially the <105451@bugs.debian.org> address.

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

> It's possible Slackware has a *working* kernel and something is broken in
> Debian ....

Possible -- that would be a kernel-image-* bug.

> > 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?
> No.  The reason for using ttyS14 is that the modem is using a non-standard
> irq and memory port, which have to be set by setserial (at least in the
> Slackware system) to make it work.  This is all explained in detail in the
> original bug report -- please go back and *read* what I first submitted.

I have.

> This is why MAKEDEV can't configure ttyS14 by itself:

MAKEDEV never configures *anything* really.  It just makes files in

> somebody has to tell
> it how to configure the port.  In Debian's /etc, there is a file called
> something like serial.conf in which you can enter the necessary info;
> but that, again, gives "No such device" when the startup script calls
> setserial to initialize the port.

/etc/serial.conf is controlled by setserial.  You'd have to see the
documentation on that for how it is supposed to be configured.
Perhaps you could cite what line you have  there.

> > Maybe you need one of the binary only drivers, e.g., as discussed on 
> > http://www.toppoint.de/~chl/linux_on_512t.html ?
> That points to www.linmodems.org so supposedly it applies to "Winmodems"
> and not to real hardware modems, which is what I have.  The only thing
> that's strange about the modem is the irq and the memory port it uses;
> apart from that, it's a normal (but made by some no-name clonemaker)
> modem.

Ok.  Well, that's good.

> > 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 .
> If I add the port-configuration info to serial.conf, the "No such device"
> error appears there.  I find no other output related to this serial-port
> problem.

That's irrelevant.  My question is still appropriate.

> > This really feels like more of a hardware/kernel issue than Debian
> > issue, really.
> But if it worked under kernel 1.2.9 (the Slackware system), why is it
> broken now?  The provision of the configuration line for ttyS14 in the
> serial.conf file shows that it's *supposed* to work, still....

It has nothing to do with a provision for /dev/ttyS14 per se, just a
provision for your non-standard serial port IO/base address sitting on
some (assigned by you) /dev/ttyS* device.

Again, this is either a setserial issue, or a kernel issue.  I doubt
it's a kernel issue unless the device uses a uart which is not
supported by the kernel, which seems unlikely.  

As you say, it works in Slackware so it's clearly not a hardware

Thus by elimination its either misconfiguration of /etc/serial.conf by
you  or else some setserial bug.  I've CC'd the setserial author.
Perhaps he could review the evidence, but I'm sure he too would like
to see the serial.conf you are using.

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

Reply to: