You are not logged in.
I am running a Dell Latitude D810, and was attempting to set up a 3Com wireless PC card. Originally, I thought that my wireless card not working due to an issue with the card itself, but unfortunately, after trying another card, I have concluded that it is the Cardbus interface itself that is fracked up. I was able to capture this information from dmesg:
yenta_cardbus 0000:03:01.0: CardBus bridge found [1028:0186]
yenta_cardbus 0000:03:01.0: Using CSCINT to route CSC interrupts to PCI
yenta_cardbus 0000:03:01.0: Routing CardBus interrupts to PCI
yenta_cardbus 0000:03:01.0: TI: mfunc 0x01111122, devctl 0x64
yenta_cardbus 0000:03:01.0: TI: probing PCI interrupt failed, trying to fix
yenta_cardbus 0000:03:01.0: Yenta TI: no PCI interrupts. Fish. Please report.
yenta_cardbus 0000:03:01.0: no PCI IRQ, CardBus support disabled for this socket.
yenta_cardbus 0000:03:01.0: check your BIOS CardBus, BIOS IRQ or ACPI settings.
yenta_cardbus 0000:03:01.0: ISA IRQ mask 0x0cf8, PCI irq 0
yenta_cardbus 0000:03:01.0: Socket status: 30000820
yenta_cardbus 0000:03:01.0: pcmcia: parent PCI bridge window: [io 0x3000-0x3fff]
yenta_cardbus 0000:03:01.0: pcmcia: parent PCI bridge window: [mem 0xdfb00000-0xdfbfffff]
yenta_cardbus 0000:03:01.0: pcmcia: parent PCI bridge window: [mem 0x40000000-0x43ffffff pref]The lspci info for the Cardbus interface:
03:01.0 CardBus bridge: Texas Instruments PCI6515 Cardbus Controller
03:01.5 Communication controller: Texas Instruments PCI6515 SmartCard ControllerThe Cardbus does in fact work on a stock Xubuntu installation, in which case the card itself is listed right under those two entries, so it's possible there is some special cardbus driver somewhere I don't have.
After much Internet searching, I attempted to boot by disabling fast boot and adding "pci=noacpi" and "pnpbios=off" to my GRUB command line, but it still gave me this message. As far as I can tell, all the BIOS's PCI settings are fully enabled.
Does anyone have any suggestions for how to get the Cardbus working? Once it works, I should be able to take installing the wireless from there.
Thanks,
Matthew Frazier
Offline
Hi,
I'm actually using Gentoo on a Latitude D505. Since i upgraded the kernel to version 2.6.34, i get the exact same issue. The cardbus refuse to detect my wireless pcmcia card and i get the same traces. If I boot using the kernel 2.6.32, it works perfectly. In fact, it worked without problem since at least 2 years.
Sadly I did not find a solution yet exept using my old kernel. I checked every option in the kernel and I can't find what's wrong.
I attaching the log for the kernel 2.6.32 as a comparison.
[ 4.110868] yenta_cardbus 0000:01:01.0: CardBus bridge found [1028:0163]
[ 4.113382] yenta_cardbus 0000:01:01.0: Using CSCINT to route CSC interrupts to PCI
[ 4.115856] yenta_cardbus 0000:01:01.0: Routing CardBus interrupts to PCI
[ 4.118309] yenta_cardbus 0000:01:01.0: TI: mfunc 0x012c1222, devctl 0x64
[ 4.343652] yenta_cardbus 0000:01:01.0: ISA IRQ mask 0x04d8, PCI irq 11
[ 4.346072] yenta_cardbus 0000:01:01.0: Socket status: 30000020
[ 4.348439] pci_bus 0000:01: Raising subordinate bus# of parent bus (#01) from #01 to #05
[ 4.350872] yenta_cardbus 0000:01:01.0: pcmcia: parent PCI bridge I/O window: 0xe000 - 0xefff
[ 4.353341] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xe000-0xefff: clean.
[ 4.356486] yenta_cardbus 0000:01:01.0: pcmcia: parent PCI bridge Memory window: 0xfc000000 - 0xfdffffff
[ 4.359084] yenta_cardbus 0000:01:01.0: pcmcia: parent PCI bridge Memory window: 0x60000000 - 0x63ffffffhere's my kernel 2.6.34 log:
[ 4.650754] yenta_cardbus 0000:01:01.0: CardBus bridge found [1028:0163]
[ 4.652710] yenta_cardbus 0000:01:01.0: Using CSCINT to route CSC interrupts to PCI
[ 4.654690] yenta_cardbus 0000:01:01.0: Routing CardBus interrupts to PCI
[ 4.656699] yenta_cardbus 0000:01:01.0: TI: mfunc 0x012c1222, devctl 0x64
[ 4.759029] yenta_cardbus 0000:01:01.0: TI: probing PCI interrupt failed, trying to fix
[ 4.862028] yenta_cardbus 0000:01:01.0: Yenta TI: no PCI interrupts. Fish. Please report.
[ 4.864067] yenta_cardbus 0000:01:01.0: no PCI IRQ, CardBus support disabled for this socket.
[ 4.866122] yenta_cardbus 0000:01:01.0: check your BIOS CardBus, BIOS IRQ or ACPI settings.
[ 4.990650] yenta_cardbus 0000:01:01.0: ISA IRQ mask 0x04d8, PCI irq 0
[ 4.992672] yenta_cardbus 0000:01:01.0: Socket status: 30000020
[ 4.994671] pci_bus 0000:01: Raising subordinate bus# of parent bus (#01) from #01 to #05
[ 4.996737] yenta_cardbus 0000:01:01.0: pcmcia: parent PCI bridge window: [io 0xe000-0xefff]
[ 4.998811] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xe000-0xefff: excluding 0xe000-0xe0ff 0xe400-0xe4ff 0xecc0-0xecff
[ 5.005846] yenta_cardbus 0000:01:01.0: pcmcia: parent PCI bridge window: [mem 0xfc000000-0xfdffffff]
[ 5.008061] pcmcia_socket pcmcia_socket0: cs: memory probe 0xfc000000-0xfdffffff: excluding 0xfc000000-0xfc1fffff 0xfce00000-0xfcffffff
[ 5.012682] yenta_cardbus 0000:01:01.0: pcmcia: parent PCI bridge window: [mem 0x60000000-0x63ffffff pref]
[ 5.015092] pcmcia_socket pcmcia_socket0: cs: memory probe 0x60000000-0x63ffffff: excluding 0x60000000-0x63ffffffOffline
Hi,
I found a solution! The bug is resolved in the kernel.
https://bugzilla.kernel.org/show_bug.cgi?id=16015
I manually updated the sources, recompiled the kernel and it's working!
Offline
Thanks for the link. However, I'm not sure how exactly to recompile the kernel in this situation, since most of the guides seem to be about compiling kernels with custom options as opposed to just "manually updating the sources". How do you do that?
Thanks,
Matthew Frazier
Offline