(01-18-2016, 07:40 AM)Jerry link Wrote: May be of use - https://bugs.launchpad.net/ubuntu/+sourc...ug/1221995 seems it could be fussy with kernel choice.
Will give it a boot change to a different kernel. Just not on this laptop to check. Because
Code:
$ dpkg --list | grep linux-image
ii linux-image-linuxlite-3.19.0 0010 i386 Linux kernel binary image for version 3.19.0-linuxlite
ii linux-image-linuxlite-4.1.0 0010 i386 Linux kernel binary image for version 4.1.0-linuxlite
ii linux-image-linuxlite-4.2.0 0010 i386 Linux kernel binary image for version 4.2.0-linuxliteBecause your link points at 3.10 and I need to check what old kernels I may have kept around .
Also. That bug report mentions.
Quote:device simply doesnt appear on bluetooth manager. blueman UI is broken.
I will be approaching this issue methodically and with patience in mind.
Next is to try on my Mint 17 Mate 64 bit install on my Samusng rv410 laptop.
I will post my findings and specs on it later on in my next post.
One Idea I am pondering. I recieved a mini cd disk with the 4.0 bluetooth dongles for the Windows drivers.
Maybe NDIS-GTK (loading windows .inf file) and blacklisting btusb driver may be a experiment worth trying out later on.
No hurry on my end for this yet. Being cautious before proceeding too fast on this.
I'd like to see a linux fix. Instead of using the cd and windows driver.
That kinda defeats the purpose of this thread. But I may try the cd route just to see if it works.
Then if it does. Uninstall the Windows .inf file in NDIS-GTK. Then un-blacklist the btusb driver.
To bring everything back to stock.
This is mostly just a self learning exercise for this biker.
LL 3.6,2.8
Dell XT2 > Touchscreen Laptop
Dell 755 > Desktop
Acer 150 > Desktop
I am who I am. Your approval is not needed.
Dell XT2 > Touchscreen Laptop
Dell 755 > Desktop
Acer 150 > Desktop
I am who I am. Your approval is not needed.