RE: PCMCIA problem (update)
Ok, I've managed to get a bit closer to the root of the problem. When I
played a bit more with the cardctl utility I found out that the card seems
to actually have a Asix AX88190 PCI chip, and when I checked the pcmcia-cs
homepage, it seems support for that chipset was removed a while ago.
However, I found a linux driver on the Asix homepage. But when I checked the
readme file it said that the driver was for kernel 2.2.*. I'm running Slink
with kernel 2.1.36, and since I've not been able to connect to the net I
can't fetch me a new kernel! So, I was wondering, before I go further, I was
wondering if anyone had tried this with a 2.1.* kernel.
regards,
Gudmundur
> -----Original Message-----
> From: Guðmundur Erlingsson [mailto:txakolin@bok.hi.is]
> Sent: Thursday, July 27, 2000 8:49 AM
> To: debian-laptop@lists.debian.org
> Subject: PCMCIA problem
>
>
> Hi there,
>
> I'm having a bit of trouble getting my (surprise!) pcmcia
> card working under
> Debian Slink. After a few hit'n'miss tries I finally managed
> to get it
> recognized at boot time, the lights now flash and
> /var/lib/pcmcia/stab shows
>
> this:
>
> <stab>
> Socket 0: empty
> Socket 1: NE2000 Compatible Ethernet
> </stab>
>
> However, I can't get any connection going and whatever I try
> with ifconfig,
> it always insists that "eth0: unknown interface".
>
> There are a few things going on during boot-time that might
> give some clue,
> but I'm just not knowledgable enough to say. F.ex. it
> complains about not
> being able to handle kernel paging requests, like this:
>
> <dmesg>
> Unable to handle kernel paging request at virtual address c6820503
> current->tss.cr3 = 055f8000, %cr3 = 055f8000
> *pde = 00001067
> *pte = 00000000
> Oops: 0000
> CPU: 0
> EIP: 0010:[<06820503>]
> EFLAGS: 00010246
> eax: 00000000 ebx: 00000100 ecx: 06820488 edx: 00000000
> esi: 055fbf24 edi: 0000002a ebp: 055df718 esp: 058b4ff8
> ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
> Process insmod (pid: 39, process nr: 15, stackpage=058b4000)
> Stack: 06820488 058ae018
> Call Trace: [<06820488>]
> </dmesg>
>
> This is repeated 4-5 times in dmesg, always at a different
> addressm although
>
> it seems to be sorted out in the end. Maybe it hasn't got
> anything to do
> with
> anything. And this is what happens when PCMCIA is enabled:
>
> <dmesg>
> Linux PCMCIA Card Services 3.1.18
> kernel build: 2.0.36 #1 Fri Jul 21 08:35:07 BST 2000
> options: [pci] [cardbus] [apm]PCI routing table version
> 1.0 at 0xfe840
> ds: no socket drivers loaded!
> unloading PCMCIA Card Services
> Linux PCMCIA Card Services 3.1.18
> kernel build: 2.0.36 #1 Fri Jul 21 08:35:07 BST 2000
> options: [pci] [cardbus] [apm]
> PCI routing table version 1.0 at 0xfe840
> Intel PCIC probe:
> TI 1225 rev 01 PCI-to-CardBus at slot 00:03, mem 0x68000000
> host opts [0]: [pci + serial irq] [pci irq 10] [lat
> 64/32] [bus 32/34]
> host opts [1]: [pci + serial irq] [pci irq 10] [lat
> 64/32] [bus 35/37]
> ISA irqs (scanned) = 3,4,7,9,11 PCI status changes
> </dmesg>
>
> And then comes this mysterious bit at the end:
>
> <dmesg>
> cs: IO port probe 0x1000-0x17ff: excluding 0x1000-0x103f 0x1400-0x140f
> cs: IO port probe 0x0100-0x04ff: excluding 0x330-0x337 0x398-0x39f
> 0x4d0-0x4d7
> cs: IO port probe 0x0a00-0x0aff: clean.
> cs: memory probe 0xa0000000-0xa0ffffff: clean.
> pcnet_cs: sorry, the AX88190 chipset is not supported.
> pcnet_cs: unable to read hardware net address for io base 0x300
> </dmesg>
>
> Like I said, I don't know how to interpret all this and any
> help would be
> appreciated. This may be a irq problem, the card is under irq
> 11 in windows,
> but "cat /proc/interrupts" shows this:
>
> 0: 73642 timer
> 1: 4764 keyboard
> 2: 0 cascade
> 4: 7 + serial
> 5: 1 sound blaster
> 10: 4 i82365
> 12: 2244 PS/2 Mouse
> 13: 1 math error
> 14: 24624 + ide0
> 15: 0 + ide1
>
> Irq 11 doesn't show up on the list. Might that be it? and how
> to resolve it?
>
> So, that's about wraps it up, I guess.
>
> regards,
>
> Gudmundur
>
>
> --
> To UNSUBSCRIBE, email to debian-laptop-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
>
Reply to: