Atheros Device Error
-
Hello everyone
I've come across a problem using an atheros based wireless card that I know is good, but I have no idea what it means. The error seems to be specific to FreeBSD
ath0: <atheros 5212="">mem 0xfeae0000-0xfeaeffff irq 17 at device 9.0 on pci2
ath0: cannot map register space
device_attach: ath0 attach returned 6Needless to say, it doesn't initialize properly upon boot of the machine. Could anyone shine any light on this? Thanks.</atheros>
-
From the man page:
ath%d: could not establish interrupt The driver was unable to install
the device interrupt handler. This should not happen.
Sounds like a hardware issue. Perhaps some details on what type of card this is (pci/cardbus/minipci/etc) and what kind of machine/motherboard you are using would help. You could try it in another machine and see if that helps. -
Motherboard: ABIT NF8-V
Processor: AMD Athlon 64 3000+
RAM: 1GB
Wireless Type: PCI -
So… interesting turn of events..... I went back to 1.2 and everything works great. Does this mean future versions of pfSense won't be supporting my wireless card?
-
Hi,
I also have a Atheros 5212 based wireless card from DLink. I have exactly the same problem: works under 1.2 but not in 1.2.1 or 1.3.
Best regards,
Jan -
I'm guessing the devs changed the version of the driver, kernel level
Would there be a way to revert back to the old one w/o having to rebuild the OS with a dev install?
-
Backup the config, Install 1.2, Restore the config.
I think it was mentioned elsewhere that this might be a driver regression in FreeBSD 7.
The best way to verify this would be to install FreeBSD 7.0 Release, and see if the issue is present. If it is, file a FreeBSD bug report. -
I tried restoring a config like this, and it didn't work before
-
Another data point: I have an atheros PCI based card working fine on a 1.2.1-RC 4 system.
The reported error message is emitted by the ath driver when it fails to allocate virtual memory to map onto the physical memory allocated to the PCI memory address space assigned to the device by the BIOS.
Here's the startup report on the Atheros in my system:
ath0: <atheros 5212="">mem 0xee000000-0xee00ffff irq 12 at device 8.0 on pci0
ath0: [ITHREAD]
ath0: using obsoleted if_watchdog interface
ath0: Ethernet address: 00:19:e0:68:31:4b
ath0: mac 7.9 phy 4.5 radio 5.6</atheros>I'm a bit suspicious of the physical address range assigned to the Atheros on your system: On an Intel based system with a fairly recent PCU and chipset that physical address range (0xfeae0000-0xfeaeffff) would be reserved for "system functions". I don't know enough of the details of AMD CPUs to know if they have the same sort of requirement.
At least a couple of recent Intel chipsets (I don't know this sort of detail about AMD chipsets) also potentially allocate 256MB of physical address space to direct map the PCI configuration registers. In the couple of BIOSes I have encountered that allocation has been in the high physical address range. The difference in behaviour of 1.2 and 1.2.1 might be due to the 1.2.1 software (being based on a later version of FreeBSD and later ACPI implementation) taking more notice of BIOS assigned memory allocations than 1.2.
I'd be inclined to take a look at the other device physical memory allocations reported during startup to see if there are other devices with allocations in a similar range. ( output from the dmesg command; post it here if you would like me to look at it.) If there aren't I'd look into whether your motherboard has the latest BIOS and if not, upgrade and see if that helps.
Misteragony: Do you have the same motherboard as ShadowLab? If not, could you post the dmesg output from your system?
-
Hi,
I use a mini ITX motherboard. A VIA PD series motherboard.
I just installed 1.2.1 final release and my wireless NIC started working. Although I seem to be losing connection every 10 minutes or so…dmesg | grep ath
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
ath0: <atheros 5212="">mem 0xea000000-0xea00ffff irq 11 at device 20.0 on pci0
ath0: [ITHREAD]
ath0: using obsoleted if_watchdog interface
ath0: Ethernet address: 00:19:5b:89:e7:d2
ath0: mac 10.5 phy 6.1 radio 6.3So far wireless is not what I would call very stable for me unfortunately. :-</atheros>
