bluez problem

[Razzle]

I managed to install bluez (partly from http://externe.net/zaurus/bluetooth-audio-sco/ and partly from bluez.sf.net).
I couldn't find any information on which packages I need so I installed

• bluez-kernel
• libbluetooth1
• bluez-zaurus (which seems to contain bluez-libs, -utils and various other packages from the sf site)

Searching the forums I found out that I have to run "/etc/rc.d/init.d/bluetooth start".

Doing this returns an error, generated by hciconfig hci0 up:
Can't get device info: No such device.

Any ideas what I might've missed?

Note: I'm using a 6000W, not a CF bluetooth card.

[guylhem]

You need 2 things:
 - kernel modules (depend on your kernel - on the 6000 use the custom kernel where the module is already compiled in)
 - binaries (bluez from audiosco dir is the latest version - 2.10)

First install the module. On the 6000W, you need hci serial module. Then run hciattach as presented in the script bt-on. the blue led will light up. to stop bluetooth, run bt-zu

bt-on launches everything you need. I recommand against the bluetooth script in /etc/init.d because you won't need it 24/7

If you are interested in "overclocking" the 6000W bluetooth (from 115200 bps to 4 times as much) I can give you instructions. But this is only usefull if you do pan networking or ppp over rfcomm.

[Razzle]

You need 2 things:
 - kernel modules (depend on your kernel - on the 6000 use the custom kernel where the module is already compiled in)
 - binaries (bluez from audiosco dir is the latest version - 2.10)

First install the module. On the 6000W, you need hci serial module.

Those are installed (see last post).  I used bluez-kernel-2.4.18-mh15_arm.ipk

Then run hciattach as presented in the script bt-on. the blue led will light up. to stop bluetooth, run bt-zu

lsmod tells me that hci_uart is loaded (not in use though) but hciattach returns "Can't set device: Protocol not supported" and "Can't initialize device: Protocol not supported".
The bluetooth led lights up for a second but doesn't stay on.

lsmod:

Code: [Select]

fcomm  33664    0 (unused)
l2capv  16352    1 [rfcomm]
hci_uart    3760    0
bluez   32896    1 [rfcomm l2cap hci_uart]

[Razzle]

One thing I forgot to mention:

I didn't follow the instructions in PSKEY-README.txt as they seem to be written for an ipaq h3600 and I don't want to break my Z.
Do they apply to the Z without changes?

[guylhem]

strange. which hciattach line are you typing?
can you do ls -l /dev/ttyS*
Can you post a dmesg after a reboot (to see kernel messages)

[Razzle]

I'm running the one from the bt-on file.

Code: [Select]

# /usr/sbin/hciattach /dev/ttyS2 csr 115200
CSR build ID 0x02-0x0D
Can't set device: Protocol not supported
Can't initialize device: Protocol not supported
# bt-on
rm: cannot remove `/etc/bluetooth/link_key': No such file or directory
CSR build ID 0x02-0x0D
Can't set device: Protocol not supported
Can't initialize device: Protocol not supported
Can't get device info: No such device

Code: [Select]

# ls -l /dev/ttyS*
crw-------    1 zaurus   root       4,  64 Feb 17  2004 /dev/ttyS0
crw-------    1 zaurus   root       4,  65 Feb 17  2004 /dev/ttyS1
crw-------    1 zaurus   root       4,  66 Nov 16 10:10 /dev/ttyS2
crw-------    1 zaurus   root       4,  67 Feb 17  2004 /dev/ttyS3
crw-r--r--    1 root     root     204,   5 Feb 17  2004 /dev/ttySA0
crw-r--r--    1 root     root     204,   6 Feb 17  2004 /dev/ttySA1
crw-r--r--    1 root     root     204,   7 Feb 17  2004 /dev/ttySA2
dmesg

[guylhem]

there's no line about ttyS2 in the dmesg.
can you lit up the blue led with:
echo > /dev/ttyS2

Regardingn hciattach, what if you replace csr by bscp?

Finally, also try pskey :

pskey -d /dev/ttyS2 -s 115200
it may give you some more information about the firmware the device etc.

If all that fails, can you try the custom kernel as explained on externe.net/zaurus/kernel ?

[Razzle]

there's no line about ttyS2 in the dmesg.
can you lit up the blue led with:
echo > /dev/ttyS2

This works, blue led lights up for a short moment.

Regardingn hciattach, what if you replace csr by bscp?

Unknown device type or id

pskey -d /dev/ttyS2 -s 115200
it may give you some more information about the firmware the device etc.

Code: [Select]

# ./pskey -d /dev/ttyS2 -s 115200
Physical device :/dev/ttyS2
Speed           :115200
Use BCSP        :NO
Initiating read thread
BT SYS: ERROR: hci_receive_data: discarding 2 bytes
Now trying to read firmware info
Successfully read firmware info.and blue led is glowing.

If all that fails, can you try the custom kernel as explained on externe.net/zaurus/kernel ?

Hm..maybe that's a bit drastic? I mean you managed to get bluetooth running with the standard sharp rom, right? Maybe I just forgot to do something...

[guylhem]

I have bt running on my 6000w with my custom kernel.
looks like your chip is there (pskey works) but for some reason it doesn't work.

the strange part is the speed, port and chipset type are correct. Try the kernel so we have an identical environment. Carefully follow the instructions to install every module. (ie remove opera pdf plugin)

[Razzle]

ok I will follow http://www.externe.net/zaurus/kernel/READM...mk7-pxa3-common then and report back once I'm done.

Update:
Might take a while because I'll have to do this at university where we have Solaris (which forces me to recompile the crosscompiler).
My harddrive died recently and I can't reinstall linux until I have rescued all data that I can..which means I need an additional 100-150GB temporal storage space. Oh well..