[SOLVED] Pulling out what is left of my hair

AuroraZero · 02-15-2010, 08:17 PM

Well I finally got Bluez running correctly. Now the problem is kbluetooth or blueman recognize my device.

Here is the output of hciconfig -a

Code:

hci0:   Type: USB
        BD Address: 00:1B:DC:0F:CD:84 ACL MTU: 310:10 SCO MTU: 64:8
        UP RUNNING PSCAN ISCAN
        RX bytes:972 acl:0 sco:0 events:28 errors:0
        TX bytes:600 acl:0 sco:0 commands:28 errors:0
        Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x83
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'BlueZ (0)'
        Class: 0x080100
        Service Classes: Capturing
        Device Class: Computer, Uncategorized
        HCI Ver: 2.1 (0x4) HCI Rev: 0x12e7 LMP Ver: 2.1 (0x4) LMP Subver: 0x12e7
        Manufacturer: Cambridge Silicon Radio (10)

So I know it is running and configured properly. Obexftp works just these two programs will not pick it up.

Code:

Here is lsusb output
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 002 Device 003: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button)
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

No clue what could be wrong here. I have rebooted about a million times and recompiled and installed both a million times. Tried new packages from different sources all with the exact same result. I have even tried rworkman's slackbuild for blueman. Nothing is working and it is now getting to me after a week and a half or so.

So if anyone has any idea at all what is causing this fiasco please do not hesitate to speak up and be heard. Iffor nothing then to let me know I am not a lone or insane.

uppman · 02-17-2010, 03:31 AM

Have you upgraded bluez? I think you need Bluez4 for blueman to work.

Also have a look at this thread:

http://www.linuxquestions.org/questi...hlight=blueman

/Magnus

AuroraZero · 02-17-2010, 04:45 PM

When I built bluez it was the newest available 4.60. Now I think 4.61 is available. I know this error makes no sense.

AuroraZero · 02-17-2010, 05:59 PM

Another thing to add to the mix. When I type hcid -n I get this result.

Code:

hcid[7412]: Bluetooth HCI daemon
hcid[7412]: Unable to get on D-Bus

If I could solve this issue I think it may solve the other one.

uppman · 02-18-2010, 04:36 AM

Quote:

Originally Posted by AuroraZero

Another thing to add to the mix. When I type hcid -n I get this result.

Code:

hcid[7412]: Bluetooth HCI daemon
hcid[7412]: Unable to get on D-Bus

If I could solve this issue I think it may solve the other one.

The hcid command doesn't exist in Bluez4..

Do you have something like this in rc.bluetooth or rc.local?

Code:

# Start bluetooth
/usr/sbin/bluetoothd -d

/Magnus

AuroraZero · 02-18-2010, 11:01 AM

NO I do not have that in either place. The problem is if I remove bluez utils and libs I get a bunch of errors ending with bluez must not be installed.

Edit:
I removed all bluez packages and doanloaded bluez-4.61. Compiled and installed it. Now when I run bluetoothd (which is in /usr/local/sbin btw) I get this error:

Code:

/usr/local/sbin/bluetoothd: error while loading shared libraries: libbluetooth.so.3: cannot open shared object file: No such file or directory

So I slocate the file:

Code:

/usr/local/lib/libbluetooth.so.3.5.0
/usr/local/lib/libbluetooth.so.3

This now where I am. The file is obviously there but bluetoothd is not seeing it for some reason.

AuroraZero · 02-18-2010, 04:16 PM

I have it running finally thank you for all the help guys.

dive · 02-18-2010, 05:05 PM

And the solution was?

AuroraZero · 02-18-2010, 07:29 PM

I removed everything bluez and obex. Then I reinstalled bluez then obex. Left out the libs and utils packages. of bluez. Typed /usr/sbin/bluetoothd into a konsole. Saw that it was running. Then I typed hciconfig hci0 up. Used hciconfig dev to see if it was running it was. Installed blueman from rworkman slackbuild and it picked it up and started running.

vehn · 02-20-2010, 11:43 PM

Quote:

Originally Posted by AuroraZero

I removed everything bluez and obex. Then I reinstalled bluez then obex. Left out the libs and utils packages. of bluez. Typed /usr/sbin/bluetoothd into a konsole. Saw that it was running. Then I typed hciconfig hci0 up. Used hciconfig dev to see if it was running it was. Installed blueman from rworkman slackbuild and it picked it up and started running.

bluez 3.x or 4.x?

AuroraZero · 02-21-2010, 02:35 PM

Bluez 4.61 on Slackware Current. For some odd reason my phone says it supports serial but it doesn't show up when I type sdptool browse <MAC>. I have no clue why but I am working on it.