Help - Search - Members - Calendar
Full Version: Bluetooth In R198
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > pdaXrom
zeigerpuppy
I am trying to get PPP over bluetooth going in R198,
however, the PPP settings program does not scan for bluetooth devices.
dmesg shows my socket low power card gets recognised.

I am trying to set it up manually, basically by editing the config files with my DUN and trying from there but I am getting the error
/dev/rfcomm0 not found
when I try to connect.

Am I barking up the wrong tree... anyone got it going?
InSearchOf
Did it work in r121?
I'm trying to do a process of elimination... since I dont have a BT card to test with...

Late
Chero
I have a different card and don't use ppp (only for playing/testing).
I can make my phone dial.

What does "hcitool scan" tell you ?
(you should find some devices)

Did you setup "/etc/bluetooth/rfcomm.conf" and "/etc/bluetooth/hcid.conf" correctly ?

Chero.
InSearchOf
Thanks Chero

Late
Meanie
I got a socket bluetooth cf as well and when i plug it in, it detects a serial_cs device and sets up /dev/ttyS0 (normally it is /dev/ttyS3 on 2.4.20 kernel). however, a hciconfig -a detects no devices, ie no hci0 or whatsoever. without hci0 being available, you got nothing to bind for /dev/rfcomm0 anyway sad.gif
Chero
QUOTE(Meanie @ Jun 19 2007, 07:55 AM)
I got a socket bluetooth cf as well and when i plug it in, it detects a serial_cs device and sets up /dev/ttyS0 (normally it is /dev/ttyS3 on 2.4.20 kernel). however, a hciconfig -a detects no devices, ie no hci0 or whatsoever. without hci0 being available, you got nothing to bind for /dev/rfcomm0 anyway sad.gif
*


try :
# setserial /dev/ttyS3 baud_base 921600
# hciattach -s 921600 /dev/ttyS3 bcsp
followed by
# hciconfig -a

(it could be ttyS0 in your case, not sure)

Chero.
Meanie
QUOTE(Chero @ Jun 19 2007, 08:21 PM)
QUOTE(Meanie @ Jun 19 2007, 07:55 AM)
I got a socket bluetooth cf as well and when i plug it in, it detects a serial_cs device and sets up /dev/ttyS0 (normally it is /dev/ttyS3 on 2.4.20 kernel). however, a hciconfig -a detects no devices, ie no hci0 or whatsoever. without hci0 being available, you got nothing to bind for /dev/rfcomm0 anyway sad.gif
*


try :
# setserial /dev/ttyS3 baud_base 921600
# hciattach -s 921600 /dev/ttyS3 bcsp
followed by
# hciconfig -a

(it could be ttyS0 in your case, not sure)

Chero.
*



hmm,

interestingly,

# setserial /dev/ttyS0 baud_base 921600

fails with Cannot set serial info: Invalid argument, while

# setserial /dev/ttyS3 baud_base 921600

actually works even though dmesg spits out the following when i insert the card:
ttyS0: detected caps 00000700 should be 00000100
1.0: ttyS0 at I/O 0xc48403f8 (irq = 137) is a 16C950/954

well
# setserial /dev/ttyS3
shows
/dev/ttyS3, UART: undefined, Port 0xc48403f8, IRQ: 137
so I set it to 8250 since that is the only available serial module

anyway, when i run
# hciattach -s 921600 /dev/ttyS3 bcsp
i get BCSP initialization timed out
Chero
QUOTE(Meanie @ Jun 20 2007, 03:49 AM)
QUOTE(Chero @ Jun 19 2007, 08:21 PM)
QUOTE(Meanie @ Jun 19 2007, 07:55 AM)
I got a socket bluetooth cf as well and when i plug it in, it detects a serial_cs device and sets up /dev/ttyS0 (normally it is /dev/ttyS3 on 2.4.20 kernel). however, a hciconfig -a detects no devices, ie no hci0 or whatsoever. without hci0 being available, you got nothing to bind for /dev/rfcomm0 anyway sad.gif
*


try :
# setserial /dev/ttyS3 baud_base 921600
# hciattach -s 921600 /dev/ttyS3 bcsp
followed by
# hciconfig -a

(it could be ttyS0 in your case, not sure)

Chero.
*



hmm,

interestingly,

# setserial /dev/ttyS0 baud_base 921600

fails with Cannot set serial info: Invalid argument, while

# setserial /dev/ttyS3 baud_base 921600

actually works even though dmesg spits out the following when i insert the card:
ttyS0: detected caps 00000700 should be 00000100
1.0: ttyS0 at I/O 0xc48403f8 (irq = 137) is a 16C950/954

well
# setserial /dev/ttyS3
shows
/dev/ttyS3, UART: undefined, Port 0xc48403f8, IRQ: 137
so I set it to 8250 since that is the only available serial module

anyway, when i run
# hciattach -s 921600 /dev/ttyS3 bcsp
i get BCSP initialization timed out
*



I used to have the time out as well, so now I :

pull out my card
Then I run /etc/rc.d/init.d/bluetooth restart
wait a few secs
put the card back in
wait a few secs
then run the two commands above (from a script)

My card is a billionton. Don't have it with me, but I'll check dmesg output this evening.

Chero.
zeigerpuppy
QUOTE(Chero @ Jun 19 2007, 02:21 AM)
try :
# setserial /dev/ttyS3 baud_base 921600
# hciattach -s 921600 /dev/ttyS3 bcsp
followed by
# hciconfig -a

(it could be ttyS0 in your case, not sure)

Chero.
*


Hi,
Tried the above (my card is also attached to ttyS0)
and I get the error:

Cannot set serial info: Invalid argument

When I enter the command
setserial -v /dev/ttyS0
I get:
/dev/ttyS0, UART: undefined, Port: 0x0000, IRQ: 22

The card was working fine in pdaXii13/beta3 and Cacko
Thanks for the suggestions
Meanie
QUOTE(zeigerpuppy @ Jun 20 2007, 08:52 PM)
QUOTE(Chero @ Jun 19 2007, 02:21 AM)
try :
# setserial /dev/ttyS3 baud_base 921600
# hciattach -s 921600 /dev/ttyS3 bcsp
followed by
# hciconfig -a

(it could be ttyS0 in your case, not sure)

Chero.
*


Hi,
Tried the above (my card is also attached to ttyS0)
and I get the error:

Cannot set serial info: Invalid argument

When I enter the command
setserial -v /dev/ttyS0
I get:
/dev/ttyS0, UART: undefined, Port: 0x0000, IRQ: 22

The card was working fine in pdaXii13/beta3 and Cacko
Thanks for the suggestions
*



ok, i found the problem. /etc/pcmcia/bluetooth is calling cardctl instead of pccardctl. also, since there is a bug in the current kernel, the SOCKET variable needs to be 1 instead of 0 on C3x00 devices.

UART needs to be set as 16950/954

the essential commands are:

modprobe hci_uart
hciattach /dev/ttyS3 bcsp 230400
hciconfig hci0 up
zeigerpuppy
QUOTE(Meanie @ Jun 20 2007, 05:10 PM)
ok, i found the problem. /etc/pcmcia/bluetooth is calling cardctl instead of pccardctl. also, since there is a bug in the current kernel, the SOCKET variable needs to be 1 instead of 0 on C3x00 devices.

UART needs to be set as 16950/954

the essential commands are:

modprobe hci_uart
hciattach /dev/ttyS3 bcsp 230400
hciconfig hci0 up
*


I edited /etc/pcmcia/bluetooth and changed cardctl to pccardctl
Then did: export SOCKET=1

when I insert the card, I get this in dmesg
ttyS0: detected caps 00000700 should be 00000100
1.0: ttyS0 at I/O 0xc48403f8 (irq = 137) is a 16C950/954

then
modprobe hci_uart
hciattach /dev/ttyS0 bcsp 230400

but I get:
BCSP initialization timed out

Not sure what to do next??
Meanie
QUOTE(zeigerpuppy @ Jun 21 2007, 06:19 PM)
QUOTE(Meanie @ Jun 20 2007, 05:10 PM)


ok, i found the problem. /etc/pcmcia/bluetooth is calling cardctl instead of pccardctl. also, since there is a bug in the current kernel, the SOCKET variable needs to be 1 instead of 0 on C3x00 devices.

UART needs to be set as 16950/954

the essential commands are:

modprobe hci_uart
hciattach /dev/ttyS3 bcsp 230400
hciconfig hci0 up
*


I edited /etc/pcmcia/bluetooth and changed cardctl to pccardctl
Then did: export SOCKET=1

when I insert the card, I get this in dmesg
ttyS0: detected caps 00000700 should be 00000100
1.0: ttyS0 at I/O 0xc48403f8 (irq = 137) is a 16C950/954

then
modprobe hci_uart
hciattach /dev/ttyS0 bcsp 230400

but I get:
BCSP initialization timed out

Not sure what to do next??
*



you still need to setserial before that, and although, dmesg says ttyS0, it really is ttyS3
zeigerpuppy
QUOTE(Meanie @ Jun 21 2007, 12:36 AM)
you still need to setserial before that, and although, dmesg says ttyS0, it really is ttyS3
*


Hi Meanie,
I have tried with setserial also (immediately after inserting the card)
This command works but then hciattach fails (I have used ttyS3)

Could you please list the order that you used the commands, it would be great to have internet access back again laugh.gif
Meanie
QUOTE(zeigerpuppy @ Jun 24 2007, 08:38 PM)
QUOTE(Meanie @ Jun 21 2007, 12:36 AM)

you still need to setserial before that, and although, dmesg says ttyS0, it really is ttyS3
*


Hi Meanie,
I have tried with setserial also (immediately after inserting the card)
This command works but then hciattach fails (I have used ttyS3)

Could you please list the order that you used the commands, it would be great to have internet access back again laugh.gif
*



in addition to setting the baud rate, you also need to set the correct uart. try SP8, it should make bluetooth work (it did it for me)
zeigerpuppy
QUOTE(Meanie @ Jun 24 2007, 02:54 AM)
in addition to setting the baud rate, you also need to set the correct uart. try SP8, it should make bluetooth work (it did it for me)
*


I tried SP8 and setting the uart to 16550A but still no luck, hciattach still times out.
sad.gif
dproldan
It is working for me here with a Sitecom Compact Flash Bluetooth adaptor.

Installed r198
Installed SP8
inserted card
setserial /dev/ttyS3 baud_base 921600
hciattach -s 921600 /dev/ttyS3 bcsp

Then you can use hcitool scan, etc.


Thanks for your help!
Meanie
QUOTE(dproldan @ Jun 24 2007, 11:00 PM)
It is working for me here with a Sitecom Compact Flash Bluetooth adaptor.

  Installed r198
  Installed SP8
  inserted card
  setserial /dev/ttyS3 baud_base 921600
  hciattach -s 921600 /dev/ttyS3 bcsp

  Then you can use hcitool scan,  etc.


  Thanks for your help!
*



actually, with SP8 installed, all that is set for you automatically...

/etc/rc.d/init.d/bluetooth start or stop will do the trick
dproldan
QUOTE(Meanie @ Jun 24 2007, 02:12 PM)
actually, with SP8 installed, all that is set for you automatically...

/etc/rc.d/init.d/bluetooth start or stop will do the trick
*


That isn't working for me. I still had to enter those commands for it to work.

There are two entries for "Compact Flash", "Bluetooth Card", "", "" in bt-uart.conf , could that be the reason?
zeigerpuppy
QUOTE(dproldan @ Jun 24 2007, 08:07 AM)
QUOTE(Meanie @ Jun 24 2007, 02:12 PM)


actually, with SP8 installed, all that is set for you automatically...

/etc/rc.d/init.d/bluetooth start or stop will do the trick
*


That isn't working for me. I still had to enter those commands for it to work.

There are two entries for "Compact Flash", "Bluetooth Card", "", "" in bt-uart.conf , could that be the reason?
*



I couldn't get it to work either, still fails whe attaching the device, unfortunately I have had to flash back to pdaXii13 for the moment as I am going on the road for a few weeks. Hoping to give it another try when I get back, thanks for the help
louigi600
I've my usb bluetooth dongle working on my C1k running r198 ... but I did it manually.
I've documented what I did to get the ppp link to my old ISP on my homepage along with a bluetooth connection manager help script. ("Zaurus" on the left, "Issues" on the top and then "ppp_over_bluetooth" or just go directly here)

BTW: I also checked out GPRS connectivity with a slightly modified chat script.
I've no means to check out UMTS connectivity but I guess it should be fine too.
louigi600
I also got bluetooth networking going ... but that took a little more effort:
apparently there is an issue between bluez version 2.21 (default on pdaXrom) and version 2.25 (the one I've on my laptop) .... while negotiating a connection with pand I was getting protocol errors.
Since this did not happen if I used 2 devices to do the whole thing on my laptop alone ... I upgraded the bluez stack on my C1K also to version 2.25. Once the upgrade was done bnep started working correctly.

I've also made some extensions to my bluetooth managing script "blue" and written a very simple but functional daemon to manage NAP in a way to make it similar to an ordinary wifi access point. If anyone is intrested I'll share ;-)
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-2014 Invision Power Services, Inc.