Short version: the official driver fixed it.
Basically I'm just trying to get a working access point using hardware I
already have. I knew my Dlink DWL-G520 worked for that in 2009 under FreeBSD,
so I was surprised to have trouble under OpenBSD.
This machine triple-boots into OpenBSD, D
I'm just Googling, but see
https://bitbucket.org/freebsd/freebsd-head/src/3ce34df9366f/sys/dev/ath/ath_hal/ar5212/
They look closely related. I started by Googling "AR5212 datasheet" and
ended up with 2 copies of a 1-page advertising PDF. The 5112 and 5212
seem to be parts of the AR5002x. The
> The odd thing is that this card works in a machine with FreeBSD 7.1 and that
> identifies the chip as "Atheros 5212". So which chip number is right?
> Could the problem have to do with misidentifying the chip? dmesg, pcidump
> and the driver think it's an AR5311.
> I've got 4.7 running on my l
I've got a Dlink DWL-G520 PCI WiFi card (looks like mini-pci on a carrier)
which I'm trying to use with 5.0 i386. In dmesg I see:
ath0 at pci2 dev 9 function 0 "Atheros AR5311" rev 0x01: apic 2 int 18
ath_hal_attach: unable to init EEPROM
ath0: unable to attach hardware; H
4 matches
Mail list logo
