Macbook Pro 5,2 Express Card Slot IRQ 0 Error

[SlickT10]

I cannot load Express cards without getting irq errors such as this one for the Ubiquiti SRX Wireless card:

[ 12.429860] ath5k_pci 0000:06:00.0: PCI INT A -> GSI 0 (level, low) -> IRQ 0
[ 12.429868] ath5k_pci 0000:06:00.0: setting latency timer to 64
[ 12.429969] ath5k_pci 0000:06:00.0: registered as 'phy0'
[ 12.429972] ath5k phy0: request_irq failed
[ 12.429980] ath5k_pci 0000:06:00.0: PCI INT A disabled
[ 12.429984] ath5k_pci: probe of 0000:06:00.0 failed with error -16

Ive tried multiple cards, all with similar results. I am dual booting a Macbook Pro 5,2. Ive also had extensive troubleshooting sessions with other experts, and the fault seems not to be in the Modules. I know my express card slot works in OSX, and the cards work in other circumstances. Just to make sure I tried the ubuntu live cd on another comupter and had the express card inserted. It worked fine. I also tried BackTrack, a security suite built on ubuntu, and had injection working without further todo. The problem is tied to this slot in linux. None of the hardware seem to be defective.

Look at the related question for more information that I provided earlier.

Any help would be supremely appreciated. I will attach dmesg's for other cards as I am able.

Thanks

[Fabio Marconi (fabiomarconi)]

Hello SlickT10
Is this issue reproducioble with the latest updated Lucid's packages?
Thanks in advance
Fabio

[Fabio Marconi (fabiomarconi)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[SlickT10 (nick4jesus)]

It turns out that adding the boot argument acpi_osi="Darwin" fixes the problem. See this issue on the kernel bug tracker for complete information: https://bugzilla.kernel.org/show_bug.cgi?id=14128 .

[SlickT10 (nick4jesus)]

Oh, and sorry for the late reply, Its been almost a year since I was trying to fix this. :)

[Fabio Marconi (fabiomarconi)]

This bug report is being closed due to your last comment. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.