Bluetooth.

cwizardone · 10-24-2010, 11:50 AM

Here is an interesting twist:

From a fresh start (boot) neither Blueman or Kbluetooth will work and report
the error messages mentioned in the previous posts above.

If I fire up XP in VirtualBox and run the bluetooth software therein, which
works properly, then close XP and VB, Blueman will work in a limited
form, i.e., it will allow a file to be sent to the device (a cellphone), but
it shows the folders on the phone, which contain files, to be empty.
Kbluetooth will fire up, but won't perform.

lumak · 10-24-2010, 08:33 PM

Here is an example of what I get from inserting and removing my usb bluetooth adapter...

Insert: This is common. USB devices should always display this type of information with dmesg when they are inserted.

Code:

usb 1-6: new full speed USB device using ohci_hcd and address 31
usb 1-6: New USB device found, idVendor=0a12, idProduct=0001
usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
usb 1-6: USB disconnect, address 31

Removed: This appears to be the service freaking out because it was not properly ended before removing the bluetooth adapter

Code:

btusb_bulk_complete: hci0 urb ffff88011d248780 failed to resubmit (19)
btusb_intr_complete: hci0 urb ffff88011d248540 failed to resubmit (19)
btusb_bulk_complete: hci0 urb ffff88011d248180 failed to resubmit (19)
btusb_send_frame: hci0 urb ffff8801329e3480 submission failed

I would conclude that if you don't get the above usb notifications, then the bluetooth adapter is broken... maybe...

And if you don't get the other part when it's removed, then the service is not being initialized when you plug in the adapter.

But this is just me guessing and I can only assume you are using a USB bluetooth adapter.

cwizardone · 10-24-2010, 10:56 PM

Quote:

Originally Posted by lumak

....I would conclude that if you don't get the above usb notifications, then the bluetooth adapter is broken... maybe...

Well, no. As previously mentioned it works just fine in Xp and in Xp within VirtualBox in Linux.
From what I've seen so far, and error reported in the dmesg log (see post #5 in this thread),
it would appear there is something wrong with the /etc/rc.d/rc.bluetooth file.

lumak · 10-24-2010, 11:38 PM

Yes... my mistake... sorry

Quote:

So I opened rc.bluetooth in mc and line 50 reads, "$HCID_EXEC -s -f $HCID_CONFIG".

There is your problem.

In both slackware 13.1 and current, the rc.bluetooth.new file does not have this line at all. The script is much MUCH simpler.

If you 'updated' to current from an older slackware and didn't apply the new scripts, then you are running on an older script that initializes bluez a different way.

Try this code to start bluez

Code:

udevadm trigger --subsystem-match=bluetooth --action=add

And this to kill it

Code:

pkill -TERM bluetoothd

These two lines are essentially what gets run with the rc.bluetooth distributed with n/bluez-4.64-x86_64-1.txz in current and 13.1

The script is 30 lines of code.

cwizardone · 10-25-2010, 01:29 AM

Lumak,
Thanks. Now I've had some partial success.

Blueman-manager will now come up and connect to the phone, but it
shows the folders on the phone to be empty (there are not) and it
refuses to transmit a file to the phone from the computer.
Oh, well.... I'll keep on trying.
Thanks, again.

titopoquito · 10-27-2010, 01:26 PM

Just some experience from my own tries to get bluetooth working: The hardware can make the difference. The first USB bluetooth device I bought seemed to be recognized, it even showed my Wii remote, but could neither connect nor could other tools necessary for the Wii remote. With the second one it works nicely, no time-outs, no sync problems. So even though the first adapter looked right and supported by the kernel it looks it wasn't actually. So what I want to say: If you can try another device before you pull out all your hair

cwizardone · 10-28-2010, 11:24 AM

Thanks, but at this point I'll just do what I do to scan and that is, run the adapter's windows software in XP in Sun's VirtualBox on my Slackware64/Xfce desktop. It is stuff like this that drives me to think I should just run
Xp, for business purposes, and get it over with, but I don't like mickeysoft and almost any distribution of Linux
is technically superior to mickeysoft winblows.

patostevens · 10-31-2010, 11:16 AM

I'm trying to use bluetooth to connect to a droid x (standard Slack 13.1 with normal updates through slackpkg). After trying everything in the forums I am still getting the "Bluez daemon not found". Could someone please give me a list of what software should be installed - or re-installed - for basic bluetooth functionality.

Thanks for the help.

Hangdog42 · 10-31-2010, 12:31 PM

Quote:

Originally Posted by patostevens

I'm trying to use bluetooth to connect to a droid x (standard Slack 13.1 with normal updates through slackpkg). After trying everything in the forums I am still getting the "Bluez daemon not found". Could someone please give me a list of what software should be installed - or re-installed - for basic bluetooth functionality.

Thanks for the help.

On both my laptop and my netbook, I'm running Slackware 13.1 stable with normal updates, I haven't messed with bluetooth at all and it works fine. Check your lsmod output and see if bluetooth is in the list.

As far as the packages goes, there seem to be four that are relevant, bluez-4.64, bluez-hcidump, bluez-firmware and blueman (the KDE tool for bluetooth). In /etc/rc.d, rc.bluetooth should be executable.

lumak · 10-31-2010, 01:36 PM

@ patostevens

If you did a fresh and full install of slackware 13.1, then everything is setup and ready for you to use.

just run blueman-applet (systemtray icon) or blueman-manager to get started.

If something is wrong, make sure the /etc/rc.d/rc.bluetooth script is set to executable and that you run it once or reboot your system. Check the output of dmesg when you insert and remove your bluetooth adapter to make sure everything is registering correctly. Make sure your device is in discover mode when you do a search for available devices.

If you did not do a fresh and full install of slackware 13.1, you have to tell us exactly what you did.

patostevens · 11-02-2010, 10:14 AM

My install was 'fresh and full'. I have re-installed (via slacpkkg) the four packages mentioned in Hangdog's post and am using the newest version of rc.bluetooth. When running blueman I still get the "BlueZ daemon not installed" message.

Where to look now?

Hangdog42 · 11-02-2010, 11:55 AM

Have you looked at lsmod to see if the bluetooth module is loaded? The only other thing I can think of is that somehow the Bluetooth hardware has been disabled. Does hciconfig return anything?

patostevens · 11-03-2010, 09:42 AM

hciconfig returns nothing.

Hangdog42 · 11-03-2010, 11:41 AM

Is the bluetooth module loaded?

patostevens · 11-03-2010, 07:42 PM

lsmod shows that bluetooth is loaded.