Difference Between Openzaurus And The Sharprom

[EdbO]

Hello,

what is exactly the difference between the OpenZaurus rom and the SharpRom? Is the base the same or are the Roms totally different?

I want to know this because my bluetoothcard (Billionton) is working great with the SharpRom, but I can't get it working with the OpenZaurus rom.

I think that I have to migrate back to the SharpRom  

[lardman]

what is exactly the difference between the OpenZaurus rom and the SharpRom? Is the base the same or are the Roms totally different?

Totally different, though they're both Linux of course, and run basically the same kernel (version).

I want to know this because my bluetoothcard (Billionton) is working great with the SharpRom, but I can't get it working with the OpenZaurus rom.

I've only just got a BT card, so am no expert, but stick with it (that's the only way problems get fixed with Open Source).

First off, which machine do you have, which OZ ROM? Is the card detected when you plug it in?


Si

[EdbO]

Okay let start  

I have a Billionton CFBT02 (see website ). This works great with the SharpRom version 3.10 on my Zaurus SL-5500.

When I flash OZ 3.5.1 and insert my bluetoothcard I got the message "New card Serial or Modem". hciconfig gives nothing, so I searched around here and found this.   I did setserial /dev/ttyS3 baud_base 921600 : WORKS
Next i do hciattach /dev/ttyS3 bcsp : BCSP initialization timed out.

I got the same with OZ 3.5.2, only when I insert the card I got the message "Billionton bluetoothcard". The rest is the same   Above works for the SharpRom.

I don't give up and installed the bluez-kernel from here, but these packages are for the SharpRom and won't work. I changes several files in /etc/pcmcia and /etc/bluetooth but no luck  

IMO this is dealing something with the kernel. And because the kernelversion is the same we can look to the configfiles for the kernels and see what is different. Maybe you can look here

For now I moved to the SharpRom until bluetooth works good with OZ.

P.S. The card works also on my laptop with Fedora Core2 and kernel 2.6.9. I have also do the trick with setserial.

[EdbO]

  I'm STUPID      I forgot to load a kernelmodule  

I moved to the SharpRom and installed the opie sysinfo, so I saw that kernelmodule hci_uart was loaded.

So I probed this on OZ 3.5.1 -->  IT WORKS!!       YES!!

HEHE, problem solved    I'm looking for another  

[Rev.Tigger]

  I'm STUPID      I forgot to load a kernelmodule  

I moved to the SharpRom and installed the opie sysinfo, so I saw that kernelmodule hci_uart was loaded.

So I probed this on OZ 3.5.1 -->  IT WORKS!!       YES!!

HEHE, problem solved    I'm looking for another   
[div align=\"right\"][a href=\"index.php?act=findpost&pid=57724\"][{POST_SNAPBACK}][/a][/div]

Did you make anyother changes?  I have the same card here and would love to have bluetooth back (my socket card died on me).

I tried modprobing hci_uart and still no joy on OpenZaurus 3.5.3 (Henges Rom).

It would be really handy to have the details for getting these working as they are £20 from e-buyer UK atm (plus post and packing etc etc so worth getting if you are making a big order).

[EdbO]

I'm downloading the Hentgens rom and will report it later.

{edit}
Okay here we go  

First you have to download and install setserial from the feed.

Open with you texteditor the file:

Code: [Select]

/etc/pcmia/bluetooth.confand look for the following code:

Code: [Select]

card "Billionton Bluetooth Card"
  version "Compact Flash", "Bluetooth Card"
  bind "bt950_cs"Change the bind-rule to:

Code: [Select]

bind "serial_cs" class "bluetooth"
Remove the bluetoothcard and restart the pcmcia-service

Code: [Select]

/etc/init.d/pcmcia restart
Insert the bluetoothcard. Mention that the billionton card would be found.
Open the terminal and type

Code: [Select]

root@collie:/#setserial /dev/ttyS3 baud_base 921600
root@collie:/#hciattach /dev/ttyS3 bcsp
root@collie:/#hciconfig
If there were not errors, your card is now up and running.

{/edit}

[HeavyWeaponDude]

I got a Billionton bluetooth card too, and folowing the advice from here, I've been able to make it works  

Now I'm wondering:  why if I type

Code: [Select]

root@collie:/#setserial /dev/ttyS3 baud_base 921600
root@collie:/#hciattach /dev/ttyS3 bcsp
root@collie:/#hciconfig
it works well, and if i try instead:

Code: [Select]

/etc/init.d/bluetooth start
I got this error message:

Starting Bluetooth subsystem: hcid sdpd Can't open HIDP control socket: No such file or directory
   hidd rfcomm.

?

I've tired to just type "hidd" at the console, and I get the same message...
Somebody has any hint about this? Thanks in advance!

[koen]

I got this error message:

Starting Bluetooth subsystem: hcid sdpd Can't open HIDP control socket: No such file or directory
   hidd rfcomm.

?

I've tired to just type "hidd" at the console, and I get the same message...
Somebody has any hint about this? Thanks in advance!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=94319\"][{POST_SNAPBACK}][/a][/div]

Your kernel is missing HIDP support (sort of every 2.4 kernel is missing that) and it's harmless.

[posicat]

I'm running into the same issues with my Belkin bluetooth card

Card : Belkin FBT020 Ver 2.0

cardctl info :
   PRODID_1="Bluetooth BT0100M"
   PRODID_2=""
   PRODID_3=""
   PRODID_4=""
   MANFIND=0000,0000

I've managed to get it up and running far enough that I can "hcitool scan" and find my phone, but it will not connect.  I'm thinking that this might be related to the baudrate, and I'll give it a try tonight when I'm home and can download packages.

[lardman]

MANFIND=0000,0000

Doesn't look right. There should at least be some numbers in there...


Si

[posicat]

MANFIND=0000,0000

Doesn't look right. There should at least be some numbers in there...


Si
[div align=\"right\"][a href=\"index.php?act=findpost&pid=96411\"][{POST_SNAPBACK}][/a][/div]

I would have thought so too, but I've been tinkering with it all morning, and just got it to connect via dialup.  It was a cheap card, so perhaps they cut corners.

The "serserial" was part of the trick.  I also had to create a pin program as the one on my Zaurus was broken.  I finally created a link, and it's working.  What I know of bluetooth now just makes me dangerous

[Mickeyl]

MANFID=0000,0000

Doesn't look right. There should at least be some numbers in there...

Actually it looks perfect  It's braindead for sure, but unfortunately it's pretty common at the same time. Most No-Name Bluetooth card manufacturers basing on cheap CSR chipsets using the BCS protocol set their MANFID CIS date to the infamous double zero.