Date: Thu, 08 Jun 2023 23:02:19 +0000 From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 255337] ath(4): Atheros AR9462 identified correctly but does not function Message-ID: <bug-255337-21060-s4BkL971pz@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-255337-21060@https.bugs.freebsd.org/bugzilla/> References: <bug-255337-21060@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255337 --- Comment #10 from John Nielsen <john@jnielsen.net> --- According to feedback from Adrian and others on freebsd-wireless it seems t= he EEPROM is not being read correctly for this card under FreeBSD. This is par= t of the dmesg output from FreeBSD on my laptop: ath0: <Atheros AR946x/AR948x> mem 0xf7a00000-0xf7a7ffff at device 0.0 on pc= i4 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 addre= ss 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 followin= g: [ 0.039398] Kernel command line: BOOT_IMAGE=3D/arch/boot/x86_64/vmlinuz-linux-jn archisobasedir=3Darch archisodevice=3DUUID=3D2023-06-08-21-40-20-00 ath9k.debug=3D0x4 [ 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=3D3 ref=3D4 length=3D794= major=3D4 minor=3D6 [ 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 p= lan to keep poking at it as I have time. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-255337-21060-s4BkL971pz>