From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5pre) Gecko/2008030513 Remi/3.0b5pre-0.beta4.20080305.fc8.remi Minefield/3.0b5pre Description of problem: I get the following when I insert the card: pccard: CardBus cardpccard: CardBus card inserted into slot 1 ACPI: PCI Interrupt 0000:07:00.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 PCI: Setting latency timer of device 0000:07:00.0 to 64 rt2x00pci -> rt2x00pci_alloc_reg: Error - Failed to allocate registers. ACPI: PCI interrupt for device 0000:07:00.0 disabled rt2500pci: probe of 0000:07:00.0 failed with error -12 inserted into slot 1 ACPI: PCI Interrupt 0000:07:00.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 This is from lspci -vvv: 07:00.0 Ethernet controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01) Subsystem: ASUSTeK Computer Inc. Unknown device 107f Control: I/O- Mem- BusMaster- SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR+ INTx- Interrupt: pin A routed to IRQ 11 Region 0: Memory at <ignored> (32-bit, non-prefetchable) [disabled] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Kernel modules: rt2500pci PCI: Setting latency timer of device 0000:07:00.0 to 64 rt2x00pci -> rt2x00pci_alloc_reg: Error - Failed to allocate registers. ACPI: PCI interrupt for device 0000:07:00.0 disabled rt2500pci: probe of 0000:07:00.0 failed with error -12 Version-Release number of selected component (if applicable): kernel-2.6.24.3-22.fc8 How reproducible: Always Steps to Reproduce: 1. Boot up the laptop 2. Insert the card 3. Actual Results: Card does not work Expected Results: Working wireless networking Additional info: This happens also happens on released kernel-2.6.24.3-12.fc8
There are some recently posted patches which I think may help here. I'll let you know when I get them into a Fedora kernel build.
The kernels here contain an update to rt2x00 version 2.1.4: http://koji.fedoraproject.org/koji/buildinfo?buildID=42735 Could you give those kernels a try to see if they resolve this issue for you?
No luck, I'm afraid. I get a very similar message with the new kernel (2.6.24.3-34) as well: pccard: CardBus card inserted into slot 1 ACPI: PCI Interrupt 0000:07:00.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 PCI: Setting latency timer of device 0000:07:00.0 to 64 rt2x00pci -> rt2x00pci_alloc_reg: Error - Failed to allocate registers. ACPI: PCI interrupt for device 0000:07:00.0 disabled rt2500pci: probe of 0000:07:00.0 failed with error -12
Hmmm...looking at where the message originates, it would seem to indicate a fundamental problem. I think this problem is indicated by this line in the lspci output above: Region 0: Memory at <ignored> (32-bit, non-prefetchable) [disabled] It looks as if you have this device disabled in your BIOS settings. Please reboot and go into your BIOS setup routines and enable the wireless device. Afterwards, can you replicate this issue?
This is actually a pcmcia card, I could find no settings for it in the BIOS. I should also mention I have tried it with two different laptops (an old Dell Inspiron 8200 and an HP 8510w) - both give the same error.
Cardbus perhaps, but not pcmcia -- if it were pcmcia then it wouldn't show-up in lspci. (This is perhaps a technicality.) Anyway, the point remains that the device is disabled. I suspect that this either still originates with a BIOS setting or the card itself is broken. It might be worthwhile for you to post the entire 'dmesg' output or contents of /var/log/messages in case there are messages from the PCI subsystem that shed some light on the situation.
You're right of course (meant to say Cardbus). I have gotten a hold of a win laptop now and this card actually seems to be broken - there it causes a blue screen with NMI: parity check/memory parity error. I'll take it back and get a replacement, sorry to have wasted your time...
No need to apologize! Let me know if you have problems once you get good hardware! :-)
*** Bug 437392 has been marked as a duplicate of this bug. ***