Re: 2.6.0 modules, hotplug, PCMCIA

[Norman Diamond]

I replied to Russell King:

> > > 5.  However, file /etc/pcmcia/serial.opts is still getting ignored under
> > > 2.6.0.
> > > The modem is detected as containing a TI 16750 UART, and whatever
> > > the serial driver does then, it causes the modem to hang up.  The serial
> > > driver in 2.4.20 defaults to the same thing but 2.4.20 reads file
> > > /etc/pcmcia/serial.opts, obeys the line SERIAL_OPTS="uart 16550A", and lets
> > > the modem operate at 33% of its rated speed instead of hanging up.
> >
> > "hang up"?  Do you mean "on-hook" or do you mean "stop working"?  Is
> > there anything in /var/log/messages about this
>
> I think both.  "on-hook" happens immediately, and the only way to try again
> is to eject the card and reinsert it.
>
> > On my RH systems, cardmgr logs a fair amount to the system messages log,
>
> As far as I can tell, in SuSE 8.2 with SuSE's default version of the 2.4.20
> kernel, this isn't happening, but in 2.6.0 it is happening even when I
> didn't ask for it.

Sorry for misstating that.  It's actually the other way around.  2.6.0 is
not giving me a ton of unrequested log syslog messages, but neither is it
giving any reason for the modem to stop working.  It only observes that the
modem hung up with no visible reason, and it doesn't even notice that the
modem cannot be retried until ejection and reinsertion.  In both 2.4.20 and
2.6.0, the serial_cs driver detects the UART as a TI 16750, which either
means that the UART really is a 16750 but the chip and the driver don't
agree on how the chip should be handled, or that the UART is a 16550A (or
something else) being misdetected.

SuSE's 2.4.20 PCMCIA configuration is writing around 6,000 syslog messages
every time I boot it.  I don't think you want that, especially when it's
from 2.4.20 which is obeying my addition in file /etc/pcmcia/serial.opts
saying  SERIAL_OPTS="uart 16550A"

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/