Re: Upgrading pcmcia-* breaks ppp

[Brian May <bam@debian.org>]

>>>>> "lehman" == lehman  <lehman@gmx.net> writes:

    lehman> After buying a pcmcia nic I thought that upgrading the pcmcia-* 
    lehman> packages and recompiling the pcmcia modules would be a good 
    lehman> idea. While I was at it, I upgraded modutils as well. Now I'm 
    lehman> running:

    lehman> pcmcia-cs_3.1.8-4.deb
    lehman> pcmcia-source_3.1.8-4.deb
    lehman> modutils_2.3.9-2.deb

    lehman> I didn't even start to mess with the nic yet, because this broke
    lehman> my ppp setup somehow. I have a 56K pcmcia modem, running as 
    lehman> ttyS2 (pppd uses /dev/modem which is a symlink pointing to 
    lehman> /dev/ttyS2). Now, whenever I fire up pppd I get:

I recently upgraded my laptop to Linux 2.2.14 (from 2.0.36) with the
latest pcmcia-* and modutils, too. I compiled both the kernel and the
pcmcia-source myself. I don't know if the kernel upgrade is
significant or the upgrade of pcmcia-*.

(I can't compile pcmcia-source for Linux 2.0.36 as my compiler is
too new. Perhaps I should try and compile pcmcia-* from slink
with Linux 2.2.14??? Will that work???)

I have a xircom combo Ethernet/28.8k Modem card. It works find with
Linux 2.0.36 and pcmcia-* from slink.

(sidenote: I have noticed recently that this card runs very hot - is
this normal?)

The Ethernet card part works fine.

    lehman> Jan 15 19:16:30 sirius pppd[352]: pppd 2.3.5 started by lehman, uid 1001
    lehman> Jan 15 19:16:30 sirius pppd[352]: tcgetattr: Input/output error(5)
    lehman> Jan 15 19:16:31 sirius pppd[352]: Exit.

I haven't tried pppd myself, but minicom cannot talk to the modem (no
errors, just nothing displayed).

    lehman> ...just as if the modem wasn't inserted at all. But when 
    lehman> inserting the modem, the output of cardmgr looks ok:

    lehman> Jan 15 19:17:28 sirius cardmgr[109]: initializing socket 2
    lehman> Jan 15 19:17:28 sirius cardmgr[109]: socket 2: Serial or Modem
    lehman> Jan 15 19:17:28 sirius cardmgr[109]: executing: 'insmod
    lehman> /lib/modules/2.2.9/pcmcia/serial_cs.o'
    lehman> Jan 15 19:17:28 sirius kernel: tty02 at 0x17f8 (irq = 5) is a 16550A
    lehman> Jan 15 19:17:28 sirius cardmgr[109]: executing: './serial start ttyS2'

I get that too. Curiously, with the slink pcmcia-* packages, the
modem is assigned tty03, not tty02 - could that be significant?

    lehman> And setserial says:

    lehman> [lehman] ~>sudo setserial -a /dev/ttyS2
    lehman> /dev/ttyS2, Line 2, UART: 16550A, Port: 0x17f8, IRQ: 5
    lehman> Baud_base: 115200, close_delay: 50, divisor: 0
    lehman> closing_wait: 3000, closing_wait2: infinte
    lehman> Flags: spd_normal skip_test

I get similar results from "setserial -a /dev/modem", but
"setserial -a /dev/ttyS2" just returns an error:

/dev/ttyS2: pcmcia controlled device (/var/run/stab)

    lehman> I checked /etc/pcmcia.conf and /etc/pcmcia/serial.opts and 
    lehman> didn't find anything that looks offensive to me. What's 
    lehman> going on here? I don't know how to track this down, any help 
    lehman> appreciated...

Also, this isn't the worst of my problems... If I try to bootup with
the card in, or shutdown, the computer will lock up, and require a
hardware reset in order to fix the problem. Inserting/removing the
card after bootup seems to be OK though.

When I asked about this on the linux-kernel mailing list, somebody
suggested I replace the following parameter to my pcmcia.conf
file with:

PCIC_OPTS='pci_csc=0'

however, that doesn't help :-(.

-- 
Brian May <bam@debian.org>