I’m testing new sleekbook HP Pavilion 15-b150er for few days. Its equipped with Qualcomm Atheros QCWB335 (Atheros AR9565 802.11 b/g/n 1 × 1 WiFi + Bluetooth 4.0 combination adapter).
When I was trying to push my BT to work, I had done terrible thing. I loaded ath9k with “modprobe ath9k bt_coex_enable=1” command.
That was end of my easy life. I tryed reinstall ath9k as usually, then with bt_coex_enable=0, then I updated kernel, recompiled ath9k and reinstall it as usual - no success. After command “sudo modprobe ath9k” nothing happend. In hardware list I see my wi-fi adapter, but driver is not loaded.
On 02/22/2013 10:36 AM, lanchardan wrote:
>
> Hello all!
>
> I’m testing new sleekbook HP Pavilion 15-b150er for few days. Its
> equipped with Qualcomm Atheros QCWB335 (Atheros AR9565 802.11 b/g/n 1 ×
> 1 WiFi + Bluetooth 4.0 combination adapter).
>
> The only driver, that worked for wi-fi is from
> http://tinyurl.com/b8lpc68
> Bluetooth looks as all ok even with default drivers from OpenSuse 12.2,
> but in fact doent working. Other devices cant see it, and adapter cant
> see others. Anyway, I hope, soon I’ll test it with OpenSuse 12.3 and
> newest kernel.
>
> When I was trying to push my BT to work, I had done terrible thing. I
> loaded ath9k with “modprobe ath9k bt_coex_enable=1” command.
> That was end of my easy life. I tryed reinstall ath9k as usually, then
> with bt_coex_enable=0, then I updated kernel, recompiled ath9k and
> reinstall it as usual - no success. After command “sudo modprobe ath9k”
> nothing happend. In hardware list I see my wi-fi adapter, but driver is
> not loaded.
>
> What I can do now?
> Im on 3.4.32-2-desktop #1 SMP PREEMPT x86_64 x86_64 x86_64 GNU/Linux
> from repo ‘Index of /repositories/Kernel:/openSUSE-12.2/standard’
> (http://tinyurl.com/96r5kz4)
All you needed to do was ‘sudo /sbin/modprobe -r ath9k’ to undo the bad command.
As ath9k is built into the kernel, you should not have had to reinstall
anything. What you did with all your manipulations is unknown. Perhaps the
output of dmesg will give you a clue.
“modprobe -r ath9k”, and then “modprobe -r --force --verbose” was first thigs, that I tryed.
Anyway, wifi get recovered about 15 minutes ago, and now works fine. Cured after “rmmod -f ath9k”.
But strange things strange.
Isnt module options specified with modprobe command supposed to be temporary? As I remember, they dont supposed to affect anything after reboot.
And about why I compiled compat modules - my adapter isnt recognized without it.
Bluetooth still cannot detect anything and cannot be detected. Tryed external BT 1.1 USB dongle - he works.
On 02/22/2013 03:46 PM, lanchardan wrote:
> “modprobe -r ath9k”, and then “modprobe -r --force --verbose” was first
> thigs, that I tryed.
> Anyway, wifi get recovered about 15 minutes ago, and now works fine.
> Cured after “rmmod -f ath9k”.
> But strange things strange.
>
> Isnt module options specified with modprobe command supposed to be
> temporary? As I remember, they dont supposed to affect anything after
> reboot.
They are temporary unless you add the option to one of the .conf files in
/etc/modprobe.d/.
> And about why I compiled compat modules - my adapter isnt recognized
> without it.
OK, now I understand. When someone talks about compiling a driver, 90% of the
time they are referring to a vendor driver. Compat-drivers is different.
> Bluetooth still cannot detect anything and cannot be detected. Tryed
> external BT 1.1 USB dongle - he works.
As I understand, compat-drivers is a part of newest kernels, like 3.6.8, backported to older kernels. Plus, in package that I used there is additional experimental patches from orbit-lab.org.
On 02/23/2013 05:16 AM, lanchardan wrote:
>
> As I understand, compat-drivers is a part of newest kernels, like 3.6.8,
> backported to older kernels. Plus, in package that I used there is
> additional experimental patches from orbit-lab.org.
The wireless drivers in compat-drivers are backported from the wireless-testing
tree, which is where devs are now working on material for kernel 3.10. Thus that
is where you get the very latest in wireless drivers. Along with the name change
from compat-wireless to compat-drivers come additional drivers.
have you found a Solution for the Bluetooth problem? I’m using Ubuntu with the newest 3.12 mainline kernel and suffer under the same issue, it seems to be detected correctly but my laptop can’t find any device and another device can’t find my laptop too.
