(First of all, sorry for `flooding` you with huge messages ;)) > What card, exactly? > You can try fiddling with the memory window definitions in > /etc/pcmcia/config.opts and see if that makes a difference. Try > removing the high memory window (0xa0000000-0xa0ffffff), for instance, > or change it to 0x60000000-0x60ffffff. As i specified in later mails, it's the 3CCFE575BT card. Also, as the cardmgr and core modules load corectly, i suspect a mem range problem. I tried: -leave only a "include memory 0xc000-0xfffff" mem range -removing 0xa0000000-0xa0ffffff and 0x60000000-0x60ffffff separately None of this worked. The only success (so far) I got by plugging the card into a Dell Inspiron (Cpi?, don't know the exact model) and i get it working. Here is the relevany excerpt of /var/log/messages: -------------------- Jul 13 16:43:51 villes kernel: Linux PCMCIA Card Services 3.0.9 Jul 13 16:43:51 villes kernel: kernel build: 2.2.5-15 #1 Mon Apr 19 23:00:46 EDT 1999 Jul 13 16:43:51 villes kernel: options: [pci] [cardbus] [apm] Jul 13 16:43:51 villes kernel: Intel PCIC probe: Jul 13 16:43:51 villes kernel: TI 1131 PCI-to-CardBus at bus 0 slot 3, mem 0x68000000, 2 sockets Jul 13 16:43:51 villes kernel: host opts [0]: [ring] [pci + serial irq] [no pci irq] [lat 32/176] [bus 32/34] Jul 13 16:43:51 villes kernel: host opts [1]: [ring] [pci + serial irq] [no pci irq] [lat 32/176] [bus 35/37] Jul 13 16:43:51 villes kernel: ISA irqs (scanned) = 3,4,9,10 status change on irq 10 Jul 13 16:43:51 villes kernel: cs: IO port probe 0x1000-0x17ff: clean. Jul 13 16:43:51 villes kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x210-0x217 0x220-0x22f 0x280-0x287 0x378-0x37f 0x4d0-0x4d7 Jul 13 16:43:51 villes kernel: cs: IO port probe 0x0a00-0x0aff: clean. Jul 13 16:43:51 villes kernel: 3c59x.c:v0.99H 11/17/98 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html Jul 13 16:43:51 villes kernel: cs: cb_config(bus 32): vendor 0x10b7, device 0x5157 Jul 13 16:43:51 villes kernel: fn 0 bar 1: io 0x400-0x47f Jul 13 16:43:51 villes kernel: fn 0 bar 2: mem 0xa0021000-0xa002107f Jul 13 16:43:51 villes kernel: fn 0 bar 3: mem 0xa0020000-0xa002007f Jul 13 16:43:51 villes kernel: fn 0 rom: mem 0xa0000000-0xa001ffff Jul 13 16:43:51 villes kernel: vortex_attach(bus 32, function 0, device 5157) Jul 13 16:43:51 villes kernel: eth0: 3Com 3CCFE575 Cyclone CardBus at 0x400, 00:50:04:93:e3:19, IRQ 3 Jul 13 16:43:51 villes kernel: eth0: CardBus functions mapped a0020000->c805c000 Jul 13 16:43:51 villes kernel: 8K byte-wide RAM 5:3 Rx:Tx split, MII interface. Jul 13 16:43:51 villes kernel: MII transceiver found at address 0, status 7809. Jul 13 16:43:51 villes kernel: Enabling bus-master transmits and whole-frame receives. ----------------------- So, my only guess is now that I should try and narrow somehow the 0xa0000000-0xa0ffffff memory range (which AFAICT is used by the card in the range 0xa0000000-0xa002007f). If you ahve _any_ other suggestion, or suggest how to find the memory ranges used by other devices (? cat /proc/pci ? ) and detect conflicts will most appreciated. If I'm completely off-track here, please point me where i should look for. > -- Dave Many, many thanks, Florian
