Bluetooth down after BT upgrade - SOLVED

[Just17]

Glad you found the reason we were confused 

At least now we know that BT is actually working and your devices are listed.

The most common pairing number is 4 zeros .....  0000 .....

I don't know if you have accessed the KDE BT settings in this manner or not, but if not try it

Configure your desktop - Network & connectivity - Bluetooth ......  enable KDE BT integration and check the devices ......  double-clicking on a device listing will give more options ....  you should probably mark the devices as 'trusted' is that is available.

[kah5683]

Still no go.

When it tells me to put in pairing pin, I assume I use the BT keyboard, but nothing can enter - I press keys and nothing happens.  I even tried changing the batteries in the keyboard, which I had checked and were fine, and that didn't work.

Here's what I am trying to do to pair:

As I said in my prior post:  When I right-click the white BT icon in systray, it lists known devices, and the keyboard is listed.  When I put the cursor on the keyboard there, it shows on first line "input service" and the second line connect.  When I press connect, 2 boxes open, one on the lower right saying kde workspace, and that the keyboard paired successfully. The other box says Bluetooth Device Wizard.  In the box it says:  The following compatible services have been found, and the box is empty.

[kah5683]

Is there something we can use here?

http://stuffivelearned.org/doku.php?id=os:linux:ubuntu:mx5500

[kah5683]

Ok, so I took my last posts article link and search pclinux forum and found this:

http://www.pclinuxos.com/forum/index.php/topic,93889.0.html

So what I did is this.  In terminal with root, I ran "hcitool scan" and got nothing.  I then pressed the connect button on the back of the keyboard, and then ran hcitool scan again, and I got:

00:1F:20:26:BC:31       Logitech MX5500 Keyboard

I then put this in root terminal:  "hidd --connect 00:1F:20:26:BC:31" and it connected, and the keyboard works!

So, I thought I would put it to the test and reboot.  The keyboard connection did not survive the reboot (the mouse did, though).  I entered the info into terminal again and reconnected, so the keyboard works again - until next reboot.

How can I make this permanent?

[sling-shot]

There is this file:
/etc/rc.d/rc.local

Open it with a text editor and add those lines which worked for you to the end.

These will be executed each time computer boots.

NOTE: You would need root privileges for editing this file.

[Just17]

As I said in my prior post:  When I right-click the white BT icon in systray, it lists known devices, and the keyboard is listed.  When I put the cursor on the keyboard there,

This is what I was trying to describe .... 

Right ckick on the icon and select Configure Bluetooth ..... this gives a window with the devices showing .......  now double click on the device you wish to examine or change and a smaller window pops up with the option to "Trust" etc.

That window also has the MAC address of the device.

[kah5683]

Thank you so much Just17 and slingshot!

Edited /etc/rc.d/rc.local in terminal root - but did not start up on reboot.  Then I tried rebooting after pressing the connect button on the back of the keyboard, and that worked.

Obviously, I don't want to have to press the connect button every time I reboot (unless I don't have any alternative).  Is there a workaround?

I did find this:

http://bccd.net/wiki/index.php/Bluetooth

and these two:

https://wiki.archlinux.org/index.php/Bluetooth_mouse_configuration

https://wiki.archlinux.org/index.php/Bluetooth_Mouse

Will the script in the first link work (solution 2)?

While looking through these links, I realized I have 2 adapters listed for my bluetooth:

[root@localhost kevin]# hciconfig
hci0:   Type: BR/EDR  Bus: USB
        BD Address: 00:26:83:17:52:F4  ACL MTU: 1022:8  SCO MTU: 121:3
        UP RUNNING PSCAN ISCAN
        RX bytes:1287945 acl:75383 sco:0 events:548 errors:0
        TX bytes:1500 acl:37 sco:0 commands:60 errors:0

hci1:   Type: BR/EDR  Bus: USB
        BD Address: 00:1F:20:39:A6:A8  ACL MTU: 1017:7  SCO MTU: 64:1
        UP RUNNING PSCAN ISCAN
        RX bytes:1241 acl:0 sco:0 events:46 errors:0
        TX bytes:470 acl:0 sco:0 commands:46 errors:0

The first one is called localhost.localdomain-0 (00:26:83:17:52:F4)  and the second localhost.localdomain-1 (00:1F:20:39:A6:A8).

Ok, I just did a test...I unplugged the BT usb adapter I got with the keyboard and mouse (the package is the Logitech MX5500).  I figured the mouse and keyboard wouldn't work after unplugging and I can see which of the two adapters listed it is, or maybe both?  Well, I unplugged it, and both the mouse and keyboard still work.  The first adapter listed above - localhost.localdomain-0 (00:26:83:17:52:F4) - is still listed.  So, that must be an adapter on my motherboard (Asus P8Z68-V Pro/Gen3)?  Should I be somehow disabling the motherboard BT adapter (making it "hidden" and unclicking "powered" when right-clicking white BT icon in systray, choosing "Configure Bluetooth" and then choosing adapters?  Or do I not need the MX5500 BT adapter at all?

Ok, did more testing...I made the localhost.localdomain-0 (00:26:83:17:52:F4) hidden and unclicked powered.  Both keyboard and mouse didn't work.  Getting somewhere.  Couldn't pair them in white BT icon in systray because it didn't find the two when it searched, even after pressing connect buttons, so tried blue icon in systray.  The blue icon under devices found both on a search after pressing connect buttons on the two.  I added them, trusted them, then went into setup from the menu on top for each.  Chose input service, then pair without pin.  Got the mouse to work, but still issues with keyboard.  With the keyboard, I always saw where it asked for a pin, I typed it but it never worked.  I then tried it again, put in the manual pin of 1234, and then saw on the display of my keyboard (didn't really look here much before since doesn't really work in linux) and saw was asking for pin.  I typed it in and saw the 4 spaces showing on the display and staying that way.  I pressed enter (for the first time) and it worked!  Didn't know I had to press enter.

The big test was whether it would survive reboot.  It didn't.  I looked under the white BT icon in systray and saw that the localhost.localdomain-0 (00:26:83:17:52:F4) was clicked for powered and showing visible again.  I figured at this point it had to be motherboard, so I went into BIOS, disabled bluetooth, started up and VOILA', it works!

So main take-aways from this:

Make sure you don't have motherboard BT AND keyboard/mouse BT usb both running.

Look at your keyboard display. 

Press enter after putting in pin.

By the way, I did remove hidd --connect 00:1F:20:26:BC:31 from /etc/rc.d/rc.local that I added.  Do you think I need to remove bluetoothd -u that I put in there also?  I don't want to fool around with success right now, unless you feel it is necessary.

[Just17]

I have renamed my adapters so that I know which one is being referred to ......  through the window that I posted about above.
There are three adapters I use on occasion ....  one is built in and the other two USB dongles.

I have given them names by which I can identify each.

In my /etc/rc.d/rc.local  I have the following lines

Code: [Select]

# start bluetooth at boot
/sbin/bluetoothd &
I had forgotten about that 

[kah5683]

So it is not a problem to disable the motherboard bluetooth?  I would assume I would need it for anything else I have bluetooth, but I don't want it to interfere with the keyboard and mouse.  Is there a way to keep it from interfering with them so I can enable it?

With the /etc/rc.d/rc.local file, should I just keep the bluetoothd -u I put in there, or switch to your:

# start bluetooth at boot
/sbin/bluetoothd &

[Just17]

If   bluetoothd -u   is working for you then I don't know of a reason not to continue to use it.

In your position I would be inclined to us ONLY the built in BT and set up the mouse and keyboard to use that .....  unless you have some problem doing so.

Sorry if I am misunderstanding things ......  but if you have a BT device on board, why not use ot for the mouse and keyboard, instead of adding another USB dongle to handle the same devices?

I don't KNOW that things will work to your satisfaction this way, but that is what I would try in your position.

.....  sometimes it takes a bit of effort trying different setups to know which suits best .........

[kah5683]

Just17:  Tried to switch adapters to onboard BT, but it didn't survive a reboot - even with your:

# start bluetooth at boot
/sbin/bluetoothd &

I went back to the dongle.

Thanks for all your help - and sling-shot too!

I will mark as solved.

[Just17]

Glad you have a solution