Help - Search - Members - Calendar
Full Version: Bluez: Billionton Annoying Problems
OESF Forums > General Forums > General Support and Discussion > Security and Networking
merli
Hello. I got to work billionton BT CF card with Z. I had to edit /etc/pcmcia/serial, installed Bluetooth applet from maslovsky and it works .... but
1) I have to start BT manually /etc/pcmcia/serial start ttyS3....
2) When I want to connect and BT is UP (hcitool scan finds my SE T610) in network applet I dont see in menu my bluettoth dial-up. I have to go to settings-> network-> edit bluetooth config -> press OK and _then_ in in network connection applet bluettoth dialup is shown.. and working
So internet connection via bluetooth is usable but a bit annoying. Can any1 help?
Grimmy
Sorry, I don't want to hijack your thread, but I am also having problems with the Billionton card and this seems like an appropriate place to mention it (I have SL5500 and am running the TKr alpha ROM).

What did you edit in the /etc/pcmcia/serial to get it to work?

I installed the Bluez drivers pinned in this forum, and the card is detected as the Billionton ok... I followed the instructions here:

http://www.oesf.org/forums/index.php?showt...indpost&p=61877

but when I attempt the "hciattach /dev/ttyS3 bcsp" it fails giving me the error:

Can't set device: No such device.
Can't initialize device: No such device.

If I try your step 1) /etc/pcmcia/serial start ttyS3 the light on top of the card stops flashing?

Any pointers you could give would be appreciated smile.gif
merli
QUOTE(Grimmy @ Jun 9 2005, 12:35 PM)
Sorry, I don't want to hijack your thread, but I am also having problems with the Billionton card and this seems like an appropriate place to mention it  (I have SL5500 and am running the TKr alpha ROM).

What did you edit in the /etc/pcmcia/serial to get it to work?

I installed the Bluez drivers pinned in this forum, and the card is detected as the Billionton ok...  I followed the instructions here:

http://www.oesf.org/forums/index.php?showt...indpost&p=61877

but when I attempt the "hciattach /dev/ttyS3 bcsp" it fails giving me the error:

Can't set device: No such device.
Can't initialize device: No such device.

If I try your step 1) /etc/pcmcia/serial start ttyS3 the light on top of the card stops flashing?

Any pointers you could give would be appreciated smile.gif
*


Basically I added to /etc/pcmcia/serial this line

setserial /dev/ttyS3 baud_base 921600

and I had to run it manually ... I dont know why it dont start with insert card ....
dont have time right now to deal with it ... I am using it as I written above:-)
If you will have more problems just ask ... I can e-mail you may configs
tumnus
Cards are automatically recognised as a bluetooth card if you add an entry for them in /etc/pcmcia/bluetooth.conf . I don't know what other PCMCIA scripts you have through since you are running a custom ROM and the standard BlueZ way of doing things is slightly different to that of the Cacko ROM's way.

With the latest ipk I produced (attached to a post in this section), all the serial initialisation stuff was moved into /etc/pcmcia/bluetooth.
rleao
Sorry to invade this discussion but I am getting crazy with my bluetooth CF:

it is a d-link DCF650BT cacko rom (64-0) with the kernel 2.4.18 (in a SL5500)

i have installed bluez 2.3.2.4.18d and the bluez serial

modified the uart:

"Socket", "CF+ Personal Network Card Rev 2.5":/dev/ttyS3 bcsp 230400
"Bluetooth BT0100M", "", "":/dev/ttyS3 bcsp

hciconfig returns nothing ohmy.gif

cardctl ident:

Socket 0:
product info: "Bluetooth BT0100M", "", ""
function: 2 (serial)
Socket 1:
no product info available

when i do /etc/rc.d/init.rd/bluetooth restart:

# ./bluetooth restart
Shutting down Bluetooth... Done.
Starting Bluetooth... Note: /etc/modules.conf is more recent than /lib/modules/2.4.18-rmk7-pxa3-embedix/modules.dep
Note: /etc/modules.conf is more recent than /lib/modules/2.4.18-rmk7-pxa3-embedix/modules.dep
Can't open serial port: No such device
Can't initialize device: No such device
Done.

setserial also says:

setserial /dev/ttyS3 baud_base 921600
... no such device
if i do ttyS2 in stead I get input/output error

/dev/ttyS3 exists and I have no idea why it's not working

when the pda is booting I can see:
can't initialize serial: no such device

in /etc/pcmcia/serial.opts

case "$ADDRESS" in
*,*,*)
INFO="Default modem setup"
# Symbolic link to dialout device
LINK="/dev/modem"
# Options for 'setserial'
SERIAL_OPTS=""
# Should we create an inittab entry for this port?
----> INITTAB="/sbin/mgetty"
# Card eject policy options
NO_CHECK=n
NO_FUSER=n
;;
esac

when I un-comment the INITTAB line, i get rid of the no such device error but in stead I get:

# hciattach /dev/ttyS3 bcsp
BCSP initialization timed out

or:

Shutting down Bluetooth... Done.
Starting Bluetooth... Note: /etc/modules.conf is more recent than /lib/modules/2.4.18-rmk7-pxa3-embedix/modules.dep
Note: /etc/modules.conf is more recent than /lib/modules/2.4.18-rmk7-pxa3-embedix/modules.dep
BCSP initialization timed out
Done.


I would very, very much appreciate any help.
zmiq2
Could it be that the card is powered off.

Please type:
cardctl status

and to put the card alive:
cardctl resume

and after that, all previous commands should work, since the card will be powered on.
Rev.Tigger
Hi, I am struggling to get this billionton card running, I have followed all the instructions in the forum I can find, I am running OZ3.5.3 (hentges) and I get the following :

CODE
root@collie:~# setserial /dev/ttyS3 baud_base 921600
root@collie:~# modprobe hci_uart
Using /lib/modules/2.4.18-rmk7-pxa3-embedix/kernel/drivers/bluetooth/hci_uart.o
root@collie:~# hciattach /dev/ttyS3 bcsp
Can't get port settings: Input/output error
Can't initialize device: Illegal seek
root@collie:~# cardctl status
Socket 0:
 3.3V 16-bit PC Card
 function 0: [ready]
Socket 1:
 no card


Any ideas? The card shows up as a Billionton Bluetooth card when inserted.
zmiq2
As far as I can see, you should also
# modprobe bluez

before haciattach
Rev.Tigger
Just tried that... and it is the same error, the modprobe does not give me anything back, so I assume it is already loaded.

I can't start bluetooth throught init/d either... I just get :

CODE
root@collie:~# /etc/init.d/bluetooth start
Starting Bluetooth subsystem: hcid sdpdCan't open HIDP control socket: No such file or directory
hidd rfcomm.
root@collie:~#


Thanks for any help! smile.gif
zmiq2
Can you eject and reinsert the card, and post the contents of /var/log/messages while doing so? That might reveal some problems.

Also, to verify what modules are loaded ok, you can launch
# lsmod

Note: I don't have this card, but I assume someone had it working according to first post in this thread.

The problem you are facing is that even ttyS3 (you might also try ttyS03) seems to be recognized, it is not functional when doing the first access attempt, which is the setserial command. Am I rigth?

Thus, you should concentrate to make the setserial command work without errors before proceeding with other more high-level commands like the hciattach and so.
Rev.Tigger
The setserial command works fine without errors, I only get errors when I do the hciattach.

I will post the logs later as I have to go out this evening now, thanks for all your help smile.gif
Hrw
try to add "sleep 2" before hciattach - maybe card need some time to get working...
Rev.Tigger
I tried it, no joy sad.gif

I am running all these from the command line not a script, untill I get it working smile.gif

Also I don't seem to have a /var/log/messages on here, closest I have is lastlog but this appears to be a binary file.

From dmesg I can spot the following bluez stuff :
CODE
BlueZ Core ver 2.4 Copyright © 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
BlueZ L2CAP ver 2.3 Copyright © 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
BlueZ RFCOMM ver 1.1
Copyright © 2002 Maxim Krasnyansky <maxk@qualcomm.com>
Copyright © 2002 Marcel Holtmann <marcel@holtmann.org>
BlueZ HCI UART driver ver 2.1 Copyright © 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>


Thank you to everyone for the help! smile.gif


edit:

In case it helps :

CODE
root@collie:~# lsmod
Module                  Size  Used by    Tainted: P
hci_uart               12412   0 (unused)
usbdmonitor             5448   0 (autoclean)
rfcomm                 33512   0 (autoclean)
l2cap                  17316   2 (autoclean) [rfcomm]
bluez                  32632   1 (autoclean) [hci_uart rfcomm l2cap]
sharp_mmcsd_m          25792   2
sa1100_bi              22924   0 (unused)
net_fd                 16636   1
usbdcore               22504   0 [sa1100_bi net_fd]
ipv6                  152344  -1
ipsec                 280008   0
zmiq2
In order to have /var/log/messages, you may need to start syslogd:
#syslogd

or

/etc/rc.d/init.d/syslog start

(I'm typing from my memory, so use autocompletion in console to find the command properly).

Then, eject/insert the card and see the contents of that file

p.s.- your loaded modules seem ok to me.
Grimmy
Incidently I have exactly the same problem with OZ-Opie 3.5.3 (Can't initialize device: Illegal seek) and similar problems (different error messages at the hciattatch stage) with Sharp 3.10, Cacko/Crow and TheKompanyROM.

The strange thing is it works fine with Merli's ROM which is a cross between Cacko Hybrid and TheKompanyROM.
Rev.Tigger
Right, I get nothing in /var/log/messages when inserting/ejecting the card.

But when I do a :

CODE
root@collie:~# /etc/init.d/bluetooth start
Starting Bluetooth subsystem: hcid sdpdCan't open HIDP control socket: No such f
ile or directory
hidd rfcomm.


In the /var/log/messages I get:

CODE
Jul  6 12:24:06 collie daemon.info hcid[2235]: Bluetooth HCI daemon
Jul  6 12:24:06 collie daemon.err sdpd[2239]: init_server: binding L2CAP socket: Address already in use
Jul  6 12:24:06 collie daemon.err sdpd[2239]: main: Server initialization failed


Which looks promising...

Nothing in the log when I get the error on hciattach /dev/ttyS3 bcsp
Rev.Tigger
Right I am now finally getting somewhere :

lastlog gives me more info and it looks like I am missing a kernel module :

CODE
Jul  6 12:50:25 collie daemon.info cardmgr[1166]: socket 0: Billionton Bluetooth Card
Jul  6 12:50:25 collie daemon.info cardmgr[1166]: executing: 'modprobe bt950_cs 2>&1'
Jul  6 12:50:25 collie daemon.info cardmgr[1166]: + modprobe: module bt950_cs not found.
Jul  6 12:50:25 collie daemon.info cardmgr[1166]: + modprobe: failed to load module bt950_cs
Jul  6 12:50:25 collie daemon.notice cardmgr[1166]: modprobe exited with status 1
Jul  6 12:50:25 collie daemon.notice cardmgr[1166]: module /lib/modules/2.4.18-rmk7-pxa3-embedix/pcmcia/bt950_cs.o not available
Jul  6 12:50:27 collie daemon.err cardmgr[1166]: get dev info on socket 0 failed: Resource temporarily unavailable


So off I go and installed it via ipkg -d sd -V2 install kernel-module-bt950-cs and it does not complain... but it does not find it when I either insmod or modprobe.

What do I have to do? (I am not a kernel scientist smile.gif )

Ed: I did an ipkg-link too smile.gif
Rev.Tigger
right, removed the module and reinstalled it to RAM... smile.gif

Now I can :

CODE
root@collie:~# insmod bt950_cs
Using /lib/modules/2.4.18-rmk7-pxa3-embedix/kernel/drivers/bluetooth/bt950_cs.o


Hurrah... or even hurroo sad.gif logread now is full of :

CODE
Jul  6 13:44:49 collie user.notice kernel: bt950_cs: RLSI interrupt, LSR=0xe9
Jul  6 13:44:49 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0xC0 received.
Jul  6 13:44:49 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0x00 received.
Jul  6 13:44:49 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0x41 received.
Jul  6 13:44:49 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0x00 received.
Jul  6 13:44:49 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0xBE received.
Jul  6 13:44:49 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0xB5 received.
Jul  6 13:44:49 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0xDC received.
Jul  6 13:44:49 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0xED received.
Jul  6 13:44:49 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0xED received.
Jul  6 13:44:49 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0x01 received.
Jul  6 13:44:49 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0xFF received.


Soooo close yet sooo far smile.gif

ed: and still can't modprobe sad.gif
zmiq2
Hi Rev,

ok, it seems we are doing some progress ....

But I would suggest to go step by step:

1) reboot without the card
2) insert the card
3) post the contents of logread, so we know exactly how it works

4) you can try, after inserting the card,
cardctl resume
setserial .....
hciattach ...

and post the result of those commands

HTH
Rev.Tigger
Right rebooted after boot, pre card logread says :

CODE
Jul  6 14:17:53 collie daemon.info hcid[1016]: Bluetooth HCI daemon
Jul  6 14:17:53 collie daemon.err sdpd[1023]: init_server: opening L2CAP socket: Address family not supported by protocol
Jul  6 14:17:53 collie daemon.err sdpd[1023]: main: Server initialization failed
Jul  6 14:17:53 collie user.info kernel: BlueZ Core ver 2.4 Copyright (C) 2000,2001 Qualcomm Inc
Jul  6 14:17:53 collie user.info kernel: Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
Jul  6 14:17:53 collie user.info kernel: BlueZ L2CAP ver 2.3 Copyright (C) 2000,2001 Qualcomm Inc
Jul  6 14:17:53 collie user.info kernel: Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
Jul  6 14:17:53 collie user.info kernel: BlueZ RFCOMM ver 1.1
Jul  6 14:17:53 collie user.info kernel: Copyright (C) 2002 Maxim Krasnyansky <maxk@qualcomm.com>
Jul  6 14:17:53 collie user.info kernel: Copyright (C) 2002 Marcel Holtmann <marcel@holtmann.org>


I insert the card and then :
CODE
Jul  6 14:20:24 collie daemon.info cardmgr[960]: socket 0: Billionton Bluetooth Card
Jul  6 14:20:24 collie daemon.info cardmgr[960]: executing: 'modprobe bt950_cs 2>&1'
Jul  6 14:20:24 collie daemon.info cardmgr[960]: + modprobe: module bt950_cs not found.
Jul  6 14:20:24 collie daemon.info cardmgr[960]: + modprobe: failed to load module bt950_cs
Jul  6 14:20:24 collie daemon.notice cardmgr[960]: modprobe exited with status 1
Jul  6 14:20:24 collie daemon.notice cardmgr[960]: module /lib/modules/2.4.18-rmk7-pxa3-embedix/pcmcia/bt950_cs.o not available
Jul  6 14:20:25 collie daemon.err cardmgr[960]: get dev info on socket 0 failed: Resource temporarily unavailable


For kicks I carry on regardless smile.gif
CODE
root@collie:~# cardctl resume
ioctl(): Device or resource busy
root@collie:~# setserial /dev/ttyS3 baud_base 921600
root@collie:~# modprobe hci_uart
Using /lib/modules/2.4.18-rmk7-pxa3-embedix/kernel/drivers/bluetooth/hci_uart.o
root@collie:~# modprobe bluez
root@collie:~# modprobe bt950_cs
modprobe: module bt950_cs not found.
modprobe: failed to load module bt950_cs
root@collie:~# hciattach /dev/ttyS3 bcsp
Can't get port settings: Input/output error
Can't initialize device: Illegal seek
root@collie:~#


Blasted thing smile.gif
zmiq2
Hi Rev,

so from your last log, it seems that even you could insmod the module before, you cannot load it anymore, and you should focus on having that solved first.

Verify that bt950_cs.o file is at /lib/modules/2.4.18-rmk7-pxa-embedix/drivers/bluetooth

run
# depmod -a

and then try the modprobe command again
Rev.Tigger
Right, I can load the module fine but it fills the logs with crap sad.gif
This is from when I put the card in:

CODE
Jul 12 16:03:59 collie daemon.info cardmgr[1166]: executing: './bluetooth start hci0 2>&1'
Jul 12 16:03:59 collie daemon.info cardmgr[1166]: + /dev/hci0: No such file or directory
Jul 12 16:03:59 collie daemon.info cardmgr[1166]: + /dev/hci0: No such file or directory
Jul 12 16:03:59 collie daemon.info cardmgr[1166]: + /dev/hci0: No such file or directory
Jul 12 16:03:59 collie daemon.info cardmgr[1166]: + Can't open serial port: No such file or directory
Jul 12 16:03:59 collie user.notice kernel: bt950_cs: RLSI interrupt, LSR=0xe9
Jul 12 16:03:59 collie daemon.info cardmgr[1166]: + Can't initialize device: Invalid argument
Jul 12 16:03:59 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0xC0 received.
Jul 12 16:03:59 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0x00 received.
Jul 12 16:03:59 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0x41 received.
Jul 12 16:03:59 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0x00 received.
Jul 12 16:03:59 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0xBE received.
Jul 12 16:03:59 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0xDA received.
Jul 12 16:03:59 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0xDC received.
Jul 12 16:03:59 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0xED received.
Jul 12 16:03:59 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0xED received.
Jul 12 16:03:59 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0x01 received.
Jul 12 16:03:59 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0xFF received.
Jul 12 16:03:59 collie user.notice kernel: bt950_cs: RLSI interrupt, LSR=0xe9
Jul 12 16:03:59 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0xC0 received.
Jul 12 16:03:59 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0x00 received.
Jul 12 16:03:59 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0x41 received.
Jul 12 16:03:59 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0x00 received.
Jul 12 16:03:59 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0xBE received.
Jul 12 16:03:59 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0xB5 received.
Jul 12 16:03:59 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0xDC received.
Jul 12 16:03:59 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0xED received.
Jul 12 16:03:59 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0xED received.
Jul 12 16:03:59 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0x01 received.
Jul 12 16:03:59 collie user.warn kernel: bt950_cs: Unknown HCI packet with type 0xFF received.


And it just keeps filling the log with it sad.gif
zmiq2
Hi Rev,

once again, I'd suggest to go step by step; the logs that you post is for the 'bluetooth start' command, while the problem happens well before. Can you post the log from the point when you insert the card?
Grimmy
QUOTE(merli @ Jun 6 2005, 04:13 PM)
2) When I want to connect and BT is UP (hcitool scan finds my SE  T610) in network applet I dont see in menu my bluettoth dial-up. I have to go to settings-> network-> edit bluetooth config -> press OK and _then_ in in network connection applet bluettoth dialup is shown..


I have had the same problem with the Billionton Card using your ROM, however I recently obtained an Anycom LSE039 and this problem does not happen with that card.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2015 Invision Power Services, Inc.