PDA

View Full Version : I'm totally stuck on Atheros card install. Please some ideas


wenis
15th January 2007, 04:21 AM
Wow, this has been some trouble to get working. I have been trying to get an Atheros pcmcia card working on my workstation through a pcmcia to pci adapter. After first dealing with the kernel bug with anaconda installing i586 modules instead of i686 and not being able to get the madwifi driver through yum to install I finally got the right kernel and the madwifi drivers to install.

Right now my kernel is 2.6.18-1.2869.fc6. I've sucessfully installed the madwifi driver with yum. I've added these lines to /etc/modprob.conf:

alias wifi0 ath_pci
alias ath0 ath_pci
options ath_pci autocreate=sta

created an /etc/sysconfig/networking/devices/ifcfg-ath0 file and run modprobe ath-pci.

I rebooted the machine but the card is not being initialized.

My output from lspci is 02:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)

And dmesg reads ( I've only included parts of the output )

PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
NetLabel: Initializing
PCI: Failed to allocate mem resource #10:2000000@e2000000 for 0000:01:0a.0
PCI: Bus 2, cardbus bridge: 0000:01:0a.0
IO window: 00009000-000090ff
IO window: 00009400-000094ff
PREFETCH window: 50000000-51ffffff
PCI: Setting latency timer of device 0000:00:02.0 to 64
pccard: CardBus card inserted into slot 0
PCI: Failed to allocate mem resource #0:10000@e1010000 for 0000:02:00.0
Yenta: CardBus bridge found at 0000:01:0a.0 [0000:0000]
Yenta: ISA IRQ mask 0x0000, PCI irq 177
Socket status: 30000820
Yenta: Upper limit for fixing this bridge's parent bridge: #02
pcmcia: parent PCI bridge I/O window: 0x9000 - 0xbfff
cs: IO port probe 0x9000-0xbfff: clean.
pcmcia: parent PCI bridge Memory window: 0xe0000000 - 0xe1ffffff
pcmcia: parent PCI bridge Memory window: 0x50000000 - 0x52ffffff
ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
wlan: 0.8.4.2 (0.9.2.1)
ath_rate_sample: 1.2 (0.9.2.1)
ath_pci: 0.9.4.5 (0.9.2.1)
ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [APC1] -> GSI 16 (level, high) -> IRQ 177
ath_pci: cannot reserve PCI memory region
ACPI: PCI interrupt for device 0000:02:00.0 disabled

It looks like some sort of memory issue at this point and I've done some searching and found a few things pointing to pcmcia, yenta and so on but these were older messages and I couldn't find anything relating to FC 6 on this.

I've tried to be as clear and concise as possible ans include as much info as I can. I feel like I'm really close to getting this thing to work but I really need some help at this point.
Thanks

wenis
15th January 2007, 02:47 PM
Hmm.... No replies. I could really use the help.

NJDevil
15th January 2007, 09:38 PM

I'm getting ready to try installing mine. I'll let you know if it works for me.

NJDevil
17th January 2007, 03:48 AM
Ok, finally got it working. I used yum and installed the whole nine yards....madwifi kmod-madwifi (which was not available until now) madwifi-devel and madwifi-debuginfo. When I rebooted the computer it worked. Hope this helps.

joe.pelayo
17th January 2007, 04:18 AM
This thread may be useful for you: http://www.fedoraforum.org/forum/showthread.php?t=126266

NJDevil
17th January 2007, 05:53 PM
Here's an update for you Wenis. I removed devel and degug via yum and my wireless is still working. Looks like all I needed was the kmod-madwifi and madwifi packages. The problem was the kmod package. It wasn't available till last night. Hope this helps.

wenis
17th January 2007, 06:36 PM
Thanks for the replies guys. I got so frustrated with this I putthe hardrive in my other machine and did a quick FC6 install. Downloading madwifi via yum and had the card working in minutes. It turns out and I've only found a few links on the net (including a burried Madwifi.com) post that certain motherboards have real issues with these cards, if see something like this in dmesg it may be a motherboard issue. "PCI: Failed to allocate mem resource". The board I was using was an old Nforce2 Asus board. Apparently, you can correct the issue with some boot parameters and I tried that, but after I saw how easy it was with a supported board, I gave into the urge and ordered a cheap SFF Shuttle machine that I hope serves my purpose.