Bluez problems

[Almost-retired]

Greetings;

Uptodate 32 bit pclos install, running your 2.6.38.8-pae-bfs kernel (bfs is sweet!), with a USB  tree that looks like a weeping willow.

I have a bluetooth dongle, a broadcom BCM92046DG-CL1ROM, that shows up in a dmesg as:
usb 1-10.4.4.3: new full speed USB device using ehci_hcd and address 18
usb 1-10.4.4.3: New USB device found, idVendor=0a5c, idProduct=2148
usb 1-10.4.4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-10.4.4.3: Product: BCM92046DG-CL1ROM
usb 1-10.4.4.3: Manufacturer: Broadcom Corp
usb 1-10.4.4.3: SerialNumber: 000272A176A4

And an lsusb:
Bus 001 Device 014: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)

but which apparently never gets a /dev/ttyUSBX number assigned to it by udev.

Going into /etc/udev/rules.d and executing:
[root@coyote rules.d]# sh ./97-bluetooth.rules
./97-bluetooth.rules: line 3: TEST{040000}!=/sys/fs/cgroup/systemd,: No such file or directory
./97-bluetooth.rules: line 4: TEST{040000}!=/sys/fs/cgroup/systemd,: No such file or directory

And indeed the only entry in /sys/fs is fuse, no cgroup/xx exists

I installed blue-who, and blueman, but neither can find the device.

The device itself is already paired with another device a wall,  a floor and 15 feet away in the basement, and was working for mandriva before I installed pclos.

What's next in the pclos way of setting this up to Just Work(TM)?

Thanks

[rubentje1991]

So, you tried bluez, blueman and blue-who....
[searched for another package in Synaptic, but didn't find it  ]
=> I thought there existed something like kbluetooth, but where it is?

[Texstar]

So, you tried bluez, blueman and blue-who....
[searched for another package in Synaptic, but didn't find it  ]
=> I thought there existed something like kbluetooth, but where it is?

There is no more kdebluetooth.

[Almost-retired]

I did get it working.  blueman-manager was telling me that bluetoothd wasn't running, and apparently udev is not starting it, so I hunted it down and ran it with an &.  The /etc/init.d/bluetooth script most distro's use is nowhere to be found, and a package that installs that doesn't fall out of a search in synaptic either.  Between that, and installing rfkill, /dev/rfcomm0 eventually appeared.  blueman-manager was then able to run, find the other device and pair them.  So now I have a 2nd minicom session running, giving me 2 terminal session logins to a TRS-80 Color Computer 3 in the basement.  Its running nitros9, which is a lot like linux.  Multi-user, and multitasking.

However, it seems to me that udev /should/ have done that.  But udev needs a lot of tlc it seems, it yelps about ATTRS not being used for everything it does do.  I tried to fix that a couple times, but docs to tell one whats right about re-writing its .rules files seem to be non-existent.

Whatever change that is needed, is probably needed in every /etc/udev/rules.d/*.rule file.

I would like to thank Texstar for the BFS kernels, damn they run sweet for a desktop. ;-)

Firefox 5 is out, and 4 is officially deprecated, so I assume we'll see that shortly.

Cheers, Gene

[Almost-retired]

Re udev, so it has, the latest dmesg does not contain any of those complaints.  Thank you.

Re kde service center, unk name here, and yes I am running the latest kde you offer.  In the PCLos services and daemons menu, there is no bluetooth.

It does show up in the hardware section of kde-4.6.4's system settings but all options are blank when the device is selected & the configure bar is clicked.

Over in kde's system settings, startup & shutdown, bluedevel is checked and running.  But I had to start bluetoothd by hand to make it work.
ps -ea|grep blue is now showing:
[gene@coyote ~]$ ps -ea|grep blue
16386 ?        00:00:00 blueman-applet
26080 ?        00:00:04 bluetoothd
26094 ?        00:00:00 bluedevil-helpe
26100 ?        00:00:00 bluedevil-monol
26216 ?        00:00:00 blueman-applet

But I don't recall seeing any bluedevil stuff in htop when I checked last night trying to get it to work before I started bluetoothd by hand.

Call me puzzled I guess.

Cheers, Gene

[rubentje1991]

There is no more kdebluetooth.

Thanks for the info... (then I don't have to search for it anymore) 

[Almost-retired]

BUT,,,

I had a power outage that outlasted my ups yesterday, and the bluez package was also updated yesterday, and now nothing I do can make it work, with both bluetoothd and blueman-manager complaining about a miss-configured DBus and cannot connect.

From the log:

Jun 24 00:12:06 coyote bluetoothd[6574]: Bluetooth deamon 4.93
Jun 24 00:12:06 coyote bluetoothd[6574]: Unable to get on D-Bus
Jun 24 00:13:35 coyote bluetoothd[6094]: Stopping hci0 event socket
Jun 24 00:13:35 coyote bluetoothd[6094]: Stopping SDP server
Jun 24 00:13:35 coyote bluetoothd[6094]: Exit

And my logs are being spammed mercilessly with:
Jun 24 01:25:02 coyote klogd: usb 1-1.1.4.4.4: usbfs: interface 0 claimed by usblp while 'usb' sets config #1
Jun 24 01:25:37 coyote last message repeated 7 times
Jun 24 01:26:42 coyote last message repeated 13 times
Jun 24 01:27:47 coyote last message repeated 13 times
Jun 24 01:28:52 coyote last message repeated 13 times
Jun 24 01:29:57 coyote last message repeated 13 times

That address is a brother laser printer.

Can someone more familiar with bluetooth being used as a serial connection over the /dev/rfcomm0 device, please describe to me what it takes, starting from a reboot, to make this work?

Thank you.

Cheers, Gene.

[Almost-retired]

I found this last problem, a printer did not latch its on state, so it was still off after the power came back on. And there was a job in its queue after the amanda run.

As for the bluez problem, I think my machine has an infestation of snilmerg.  About midnight last night, long (at least an hour) after I had given up on bluetooth for the 10th time at least, an icon popped up in the dock where the volume control and clipboard stuff live, with a bluetooth logo in it.  Clicking on that turned out to be blueman-manager, which had found the device it was supposed to, and a click on that, then an add, and that is now up and running.  and here all this time I thought we were the masters of linux.  Not really, this stuff has a mind of its own.

Cheers, Gene

[sling-shot]

There is no more kdebluetooth.

Thanks for the info... (then I don't have to search for it anymore) 

It has been replaced by BlueDevil, the next generation KDE Bluetooth.
-SS.

[Almost-retired]

Just one problem, bluedevil doesn't work.  In fact I think it is running too, spinning its wheels so to speak.
Yes.
[gene@coyote ~]$ ps -ea|grep blue
 4083 ?        00:00:01 blueman-applet
 6331 ?        00:00:05 bluetoothd
 6345 ?        00:00:00 bluedevil-helpe
 8855 ?        00:08:29 blueman-manager
15278 ?        00:00:00 bluedevil-monol

Yup, but it was blueman-manager that actually made the working connection.

If bluedevil is supposed to work, what do I need to configure so it Just Works(TM)?

Personal opinion:

That kdebluetooth thingy should have been removed from the barn, put out of its misery and buried at least a year ago.  Changing its name does not polish that turd nor remove the smell.

Just for grins, I am killing its pieces, but I do not think my connection will go away.  Nope, its pieces are all gone but blueman is still there because I'm monitoring link quality.  For bluetooth, its a long link.

Cheers & thanks, Gene