Comment 13 for bug 1024884

Revision history for this message
Max Schillinger (maxschillinger) wrote :

No problem. Thanks for your effort!
I have installed your new package and after a reboot I get following output:
~$ dkms status
ar9462, 1.1, 3.2.0-29-generic, x86_64: installed
bbswitch, 0.4.2, 3.2.0-27-generic, x86_64: installed
bbswitch, 0.4.2, 3.2.0-29-generic, x86_64: installed
bbswitch, 0.4.2, 3.5.0-030500-generic, x86_64: installed
bbswitch, 0.4.2, 3.5.0-3-generic, x86_64: installed
bbswitch, 0.4.2, 3.5.0-5-generic, x86_64: installed
bbswitch, 0.4.2, 3.5.0-8-generic, x86_64: installed
ndiswrapper, 1.57, 3.2.0-26-generic, x86_64: installed
ndiswrapper, 1.57, 3.2.0-27-generic, x86_64: installed
ndiswrapper, 1.57, 3.2.0-29-generic, x86_64: installed
nvidia-current, 304.37, 3.5.0-030500-generic, x86_64: installed
~$ hciconfig --all
~$ lsmod | grep ath
ath9k 132390 0
mac80211 506816 1 ath9k
ath9k_common 14053 1 ath9k
ath9k_hw 411151 2 ath9k,ath9k_common
ath 24067 3 ath9k,ath9k_common,ath9k_hw
ath3k 12910 0
cfg80211 205544 3 ath9k,mac80211,ath
bluetooth 180104 11 rfcomm,bnep,ath3k
~$ dmesg | grep ath
[ 15.864420] ath9k 0000:0d:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 15.864442] ath9k 0000:0d:00.0: setting latency timer to 64
[ 15.877230] ath: EEPROM regdomain: 0x6a
[ 15.877232] ath: EEPROM indicates we should expect a direct regpair map
[ 15.877235] ath: Country alpha2 being used: 00
[ 15.877236] ath: Regpair used: 0x6a
[ 15.898793] ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'
[ 15.899296] Registered led device: ath9k-phy0
[ 16.291130] usbcore: registered new interface driver ath3k
[ 18.641993] type=1400 audit(1346059965.992:10): apparmor="STATUS" operation="profile_load" name="/usr/lib/telepathy/mission-control-5" pid=1072 comm="apparmor_parser"
[ 18.642378] type=1400 audit(1346059965.992:11): apparmor="STATUS" operation="profile_load" name="/usr/lib/telepathy/telepathy-*" pid=1072 comm="apparmor_parser"

It looks like the installation of the package was successful. But the blueetoth module doesn't use the ath9k module (if I understand correctly). Does ath9k replace ath3k? When I unload ath3k, my bluetooth still doesn't work.