There's no kernel issue here, so closing the kernel task. I can confirm that ath5k is loaded and *not* ath_pci by default.
I do see that Jockey pops up and suggests using the madwifi driver. Selecting this causes ath_pci to be loaded, even though ath5k is already loaded. This does seem like a jockey bug.
There's no kernel issue here, so closing the kernel task. I can confirm that ath5k is loaded and *not* ath_pci by default.
I do see that Jockey pops up and suggests using the madwifi driver. Selecting this causes ath_pci to be loaded, even though ath5k is already loaded. This does seem like a jockey bug.