Eli Gwynn <e...@egwynn.com> changed:
What |Removed |Added
--- Comment #27 from Eli Gwynn <e...@egwynn.com> ---
I have zero experience with wlan drivers, but this thread was the key to making
my hardware work, so I figured I'd add my own details here in case they are
helpful to someone else. My use case involves the wlan device in hostap mode
bridged with my wired nic to expand the wifi coverage in my house.
--- My Hardware
Rosewill RNWD-N9003PCE (Ver 1.0)
- WikiDevi: https://wikidevi.com/wiki/Rosewill_N900PCE
- Amazon: https://www.amazon.com/gp/product/B009VKON0S
FWIW, I live in the US and didn't have any inclination that I might end up with
a non-US device. The only hint that my device might be non-US (Canadian?) is
that some of the packaging is doubled up in French.
ath0@pci0:2:0:0: class=0x028000 card=0x3112168c chip=0x0030168c rev=0x01
vendor = 'Qualcomm Atheros'
device = 'AR93xx Wireless Network Adapter'
class = network
--- dmesg (pre-patch)
Jun 11 09:51:02 zfs kernel: pcib2: <ACPI PCI-PCI bridge> irq 17 at device 28.5
Jun 11 09:51:02 zfs kernel: pci2: <ACPI PCI bus> on pcib2
Jun 11 09:51:02 zfs kernel: ath0: <Atheros AR938x> mem 0xdf100000-0xdf11ffff
irq 17 at device 0.0 on pci2
Jun 11 09:51:02 zfs kernel: ar9300_attach: calling ar9300_hw_attach
Jun 11 09:51:02 zfs kernel: ar9300_hw_attach: calling ar9300_eeprom_attach
Jun 11 09:51:02 zfs kernel: ar9300_flash_map: unimplemented for now
Jun 11 09:51:02 zfs kernel: Restoring Cal data from DRAM
Jun 11 09:51:02 zfs kernel: Restoring Cal data from EEPROM
Jun 11 09:51:02 zfs kernel: ar9300_hw_attach: ar9300_eeprom_attach returned 0
Jun 11 09:51:02 zfs kernel: ath0: ath_getchannels: unable to collect channel
list from hal, status 12
Jun 11 09:51:02 zfs kernel: device_attach: ath0 attach returned 22
--- Steps I took
1. I ran `make buildworld` in order to get my build tools back in sync with my
2. I added `options AH_DEBUG` to my kernel's conf
3. I ran `make buildkernel`, `make installkernel`, and rebooted
4. I ran `sysctl hw.ath.hal.debug=1`
5. I used `devctl detach pci2` and `devctl attach pci2` to trigger the
6. I observed that my device was also showing up as
> Jun 12 14:53:41 zfs kernel: isEepromValid: invalid regulatory domain/country
> code 0x14
7. I applied both of Jung-uk Kim's attached patches
8. I ran `make buildkernel` and `make installkernel` again
9. I rebooted and then my card worked
Are the solutions presented in this thread good enough to make it into the
mainline driver? I'd hate to have to do this again when next I do a
Thanks to everyone for all the good work!
You are receiving this mail because:
You are the assignee for the bug.
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"