[Bug 255337] ath(4): Atheros AR9462 identified correctly but does not function

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255337

--- Comment #10 from John Nielsen <john@jnielsen.net> ---
According to feedback from Adrian and others on freebsd-wireless it seems the
EEPROM is not being read correctly for this card under FreeBSD. This is part of
the dmesg output from FreeBSD on my laptop:

ath0: <Atheros AR946x/AR948x> mem 0xf7a00000-0xf7a7ffff at device 0.0 on pci4
ar9300_flash_map: unimplemented for now
Restoring Cal data from DRAM
Restoring Cal data from EEPROM
Restoring Cal data from Flash
Restoring Cal data from Flash
Restoring Cal data from OTP
ar9300_eeprom_restore_internal[4338] No vaid CAL, calling default template

It tries to read all the places and doesn't succeed from any of them. The
hard-coded ar9300 default template is where the 00:02:03:04:05:06 MAC address
comes from.

I was able to boot the same laptop under Linux (where the wireless works as
expected) with the ath9k EEPROM debug messages enabled and got the following:

[    0.039398] Kernel command line:
BOOT_IMAGE=/arch/boot/x86_64/vmlinuz-linux-jn archisobasedir=arch
archisodevice=UUID=2023-06-08-21-40-20-00 ath9k.debug=0x4
[   17.692752] ath9k 0000:04:00.0: enabling device (0000 -> 0002)
[   17.696711] ath: phy0: Trying EEPROM access at Address 0x03ff
[   17.697238] ath: phy0: Found valid EEPROM data
[   17.697763] ath: phy0: Found block at 3ff: code=3 ref=4 length=794 major=4
minor=6
[   17.803208] ath: phy0: checksum a5cc a5cc
[   17.803214] ath: phy0: restore eeprom 0: block, reference 4, length 794

It succeeds at reading the EEPROM data on the first attempt and gets all the
appropriate information (including a valid MAC address).

Hopefully this gets us closer to at least knowing where the problem is. I plan
to keep poking at it as I have time.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.