On Wednesday 10 November 2004 06:57, patheve2 wrote:

Hello all

My previous mails were sent during last August about this problem with PCMCIA card and Linux 2.6.5. I could hope that the kernel 2.6.8 should solve it, as it was written by some users.

As described at that time, the kernel >= 2.6.7 is helping, but it is just half of the solution. You also need to get the memory range and port range used by your system and configured in config.opts in sync. A very quick check (sorry, not much time at the moment) seems to show that you didn't finish that part, see below.

Hereafter my proble

0== my laptop, the PCMCIA cards and linux system :

Asus L5800DF Athlon64 socket 754 - modem PCMCIA Platinum Card MC227 v90 of ComOne (should work fine according to tuxmobil.org) - ethernet card Netgear FA411 (a 16 bits one) SuSE Linux 9.1 AMD64 with the kernel of the SuSE 9.2 AMD64, a 2.6.8-24-3 (the previous one : a 2.6.5-7-111)

1== what says linux during boot without PCMCIA card (dmesg) :

Linux Kernel Card Services options: [pci] [cardbus] [pm] ACPI: PCI interrupt 0000:02:01.0[A] -> GSI 9 (level, low) -> IRQ 9 Yenta: CardBus bridge found at 0000:02:01.0 [1043:1854] Yenta: ISA IRQ mask 0x0098, PCI irq 9 Socket status: 30000006 ACPI: PCI interrupt 0000:02:01.1[B] -> GSI 11 (level, low) -> IRQ 11 Yenta: CardBus bridge found at 0000:02:01.1 [1043:1854] Yenta: ISA IRQ mask 0x0098, PCI irq 11 Socket status: 30000006

2== details about cardbus with "lspci -vv" :

0000:02:01.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ab) Subsystem: Asustek Computer, Inc.: Unknown device 1854 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-

here are the ports your system uses:

I/O window 0: 0000c000-0000c7ff I/O window 1: 0000c800-0000cfff

BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001

3== the config.opts file in /etc/pcmcia (partial view)

# This are the official ports to use from pcmcia-cs, but ... # include port 0x100-0x4ff, port 0x800-0x8ff, port 0xc00-0xcff # ... ports 0x810-0x81f hurt on some DELL machines and ... # ... ports 0x3b0-0x3df hurt on some FSC machines. #include port 0x100-0x4ff #include port 0x800-0x8ff #include port 0xc00-0xcff #include port 0x3000-0x7fff

and here is what you have configured:

# according to lspci -vv for Cardbus include port 0x0000-0x1000 include port 0xb000-0xcfff

i do not see where you got the values 0x0000-0x1000 and 0xb000 from. I do not see them in your "lspci -vv" output. Why don't you try just the port and memory ranges "lspci -vv" gave you, such as : include port 0xc000-0xc7ff include port 0xc800-0xcfff

# include memory 0xc0000-0xfffff include memory 0xa0000000-0xa0ffffff include memory 0x60000000-0x60ffffff include memory 0xe0100000-0xe17fffff # according to lspci -vv for Cardbus include memory 0xf8a00000-0xfd1ff000

Also this is not the same as what your "lspci -vv" says, which is fba00000-fc5ff000 and fc600000-fd1ff000. Since 0xf8a00000 is smaller as fba00000 it might be OK though.

#

# High port numbers do not always work... # include port 0x1000-0x17ff

# Extra port range for IBM Token Ring #include port 0xa00-0xaff

# Resources we should not use, even if they appear to be available

# First built-in serial port exclude irq 4 # Second built-in serial port #exclude irq 3 # First built-in parallel port exclude irq 7

4== with the inserted network card FA411 :

--- cardctl status Socket 0: 5V 16-bit PC Card function 0: [ready] Socket 1: no card

--- cardctl ident Socket 0: product info: "NETGEAR", "FA411", "Fast Ethernet" manfid: 0x0149, 0x0411 function: 6 (network) Socket 1: no product info available

--- cardctl info PRODID_1="NETGEAR" PRODID_2="FA411" PRODID_3="Fast Ethernet" PRODID_4="" MANFID=0149,0411 FUNCID=6 PRODID_1="" PRODID_2="" PRODID_3="" PRODID_4="" MANFID=0000,0000 FUNCID=255

===> it seems OK but nothing else done with this card. Wiith Yast, the NetGear FA411 is well seen for configuration. A good new :-) ?

check if you need to install and load a driver for this ethernet card, and if it is available / installed in a 64 bit version. I do not know this card, sorry. The fact that yast sees it doesn't mean that it has installed a driver. If there is no 64 bit driver, it will see it, but it will not install a driver, obviously. Check also what dmesg says for this ethernet card, I do not see it listed here.

4== with the inserted modem card :

--- dmesg serial_cs: no usable port range found, giving up serial_cs: RequestIO: No more items

As long as serial_cs is not happy, it will not work. As it says, it does not find the port, so check the ports you use, see above. But then again, it might not use serial_cs. For example, if it is a smartmodem, you would need the smartmodem driver, which is not available in 64 bit. So google and check if you need to install and load a driver for this modem card, and if it is available / installed in a 64 bit version. I do not know this card, sorry.

====> no such info with last kernel 2.6.5-7-111

--- in /dev/ a symbolic link /dev/modem is done with /dev/ttyS2, instead of /dev/cua2 with kernel 2.6.5-7-111 NB : ttyS0 is serial port, ttyS1 is the irda port

--- cardctl status Socket 0: 5V 16-bit PC Card function 0: [ready], [wp] Socket 1: no card

--- cardctl ident Socket 0: product info: "PCMCIA CARD MEMBER", "FM56R-NCTV2", "021", "A" manfid: 0x0013, 0x0000 function: 2 (serial)

that's why it tries serial_cs.

Socket 1: no product info available

--- cardctl info PRODID_1="PCMCIA CARD MEMBER" PRODID_2="FM56R-NCTV2" PRODID_3="021" PRODID_4="A" MANFID=0013,0000 FUNCID=2 PRODID_1="" PRODID_2="" PRODID_3="" PRODID_4="" MANFID=0000,0000 FUNCID=255

5== with kppp when a request is sent to the /dev/modem or /dev/ttyS2 with kppp, the answer is : modem is busy :-(

obviously, as long as serial_cs did not connect to the card, or another driver took over that job. Usually you see in dmesg then that serial_cs did attach it to /dev/ttyS2, or to another device. This step is apparently not successful yet, see above. It's too early to try kppp etc, as long as you did not solve the step before.

So, I am probably doing something bad but I don't see what. If you see what I have to do, thanks very much to write it me :-)

Pascal

Again, first get your config.opts and your lspci -vv output in sync, and try again. Then, if this did not help yet, check if you need drivers for these cards, and if yes, if they are available as 64 bit. HTH, Matt