Angus McMorland, 2003-Jan-25 18:29 +1300: > Hi all, > > Thanks, Jeff, for the reply. > > I've compiled PCMCIA_SERIAL_CS into my 2.4.19 kernel now (heard about > the problems with 2.4.20 and don't want to mess with 2.4.18 which is my > vaguely working version), but with no improvement. > > Yes, it was missing, but I think I've tried it before. > > The help documentation for that option clearly states it's for 16-bit > cards, which the RBEM56G isn't.
I have the same Xircom card and the eth0 and modem are working fine. I went ahead and recompiled a 2.4.20 kernel (I ain't scared!). I'm using all the built-in drivers too. Here are some details on my setup: Insert card: Jan 26 08:56:47 jcoppock kernel: cs: cb_alloc(bus 2): vendor 0x115d, device 0x0003 Jan 26 08:56:47 jcoppock kernel: PCI: Enabling device 02:00.0 (0000 -> 0003) Jan 26 08:56:47 jcoppock kernel: PCI: Setting latency timer of device 02:00.0 to 64 Jan 26 08:56:47 jcoppock kernel: eth0: Xircom cardbus revision 3 at irq 11 Jan 26 08:56:47 jcoppock kernel: PCI: Enabling device 02:00.1 (0000 -> 0003) Jan 26 08:56:47 jcoppock kernel: ttyS04 at port 0x4080 (irq = 11) is a 16550A Jan 26 08:56:47 jcoppock cardmgr[311]: socket 0: CardBus hotplug device Kernel options: <snip> CONFIG_HOTPLUG=y # # PCMCIA/CardBus support # CONFIG_PCMCIA=y CONFIG_CARDBUS=y # CONFIG_TCIC is not set # CONFIG_I82092 is not set # CONFIG_I82365 is not set # # PCI Hotplug Support # CONFIG_HOTPLUG_PCI=y <snip> # PCMCIA network device support # CONFIG_NET_PCMCIA=y # CONFIG_PCMCIA_3C589 is not set # CONFIG_PCMCIA_3C574 is not set # CONFIG_PCMCIA_FMVJ18X is not set CONFIG_PCMCIA_PCNET=m # CONFIG_PCMCIA_AXNET is not set # CONFIG_PCMCIA_NMCLAN is not set CONFIG_PCMCIA_SMC91C92=m # CONFIG_PCMCIA_XIRC2PS is not set # CONFIG_ARCNET_COM20020_CS is not set # CONFIG_PCMCIA_IBMTR is not set CONFIG_PCMCIA_XIRCOM=y # CONFIG_PCMCIA_XIRTULIP is not set CONFIG_NET_PCMCIA_RADIO=y CONFIG_PCMCIA_RAYCS=m CONFIG_PCMCIA_NETWAVE=m CONFIG_PCMCIA_WAVELAN=m # CONFIG_AIRONET4500_CS is not set <snip> # PCMCIA character devices # CONFIG_PCMCIA_SERIAL_CS=y CONFIG_PCMCIA_CHRDEV=y # CONFIG_SYNCLINK_CS is not set # CONFIG_MWAVE is not set <snip> > Another point I've noticed while on this quest: > dmesg has an entry: > > Linux Kernel Card Services 3.1.22 > > which is obviously not the latest version (I've got the pcmcia-source > 3.1.33-6 package now). Is that a problem? If I try I also have Linux Kernel Card Services 3.1.22, as indicated in my dmesg log. Also, I have pcmcia-cs version 3.1.33-6 installed...the package, not the source. > #modprobe serial_cb > > which, I believe, is the correct module for the serial function of the > card, I get: > > /lib/modules/2.4.19/pcmcia/cb_enabler.o: init_module: Invalid argument > Hint: insmod errors can be caused by incorrect module parameters, > including invalid IO or IRQ parameters. > You may find more information in syslog or the output from dmesg > /lib/modules/2.4.19/pcmcia/cb_enabler.o: insmod > /lib/modules/2.4.19/pcmcia/cb_enabler.o failed > /lib/modules/2.4.19/pcmcia/cb_enabler.o: insmod serial_cb failed > > and dmesg reports: > > cb_enabler: Card Services release does not match! > > Any more ideas anyone? Since I've put the drivers into the kernel, I can't confirm this. > Thanks for your time, np. > Angus. > > P.S. With 2.4.19 and 2.4.20, I'm also experiencing bug #142940 where > #apm -s doesn't work, supposedly something to do with the pcmcia system. > Is this a symptom of the same problem? I don't have this problem on my Dell Latitude CPx. Neither with the previous kernel 2.4.19 or the currect 2.4.20. jc -- Jeff Coppock Systems Engineer Diggin' Debian Admin and User
