Bluetooth In R198

[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

[Chero]

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
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163372\"][{POST_SNAPBACK}][/a][/div]

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]

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
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163372\"][{POST_SNAPBACK}][/a][/div]

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.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163378\"][{POST_SNAPBACK}][/a][/div]

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]

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
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163372\"][{POST_SNAPBACK}][/a][/div]

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.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163378\"][{POST_SNAPBACK}][/a][/div]

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
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163426\"][{POST_SNAPBACK}][/a][/div]

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]

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.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163378\"][{POST_SNAPBACK}][/a][/div]

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]

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.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163378\"][{POST_SNAPBACK}][/a][/div]

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
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163447\"][{POST_SNAPBACK}][/a][/div]

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]

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
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163473\"][{POST_SNAPBACK}][/a][/div]

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]

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
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163473\"][{POST_SNAPBACK}][/a][/div]

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??
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163484\"][{POST_SNAPBACK}][/a][/div]

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

[zeigerpuppy]

you still need to setserial before that, and although, dmesg says ttyS0, it really is ttyS3
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163486\"][{POST_SNAPBACK}][/a][/div]

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  

[Meanie]

you still need to setserial before that, and although, dmesg says ttyS0, it really is ttyS3
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163486\"][{POST_SNAPBACK}][/a][/div]

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  
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163632\"][{POST_SNAPBACK}][/a][/div]

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]

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)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163634\"][{POST_SNAPBACK}][/a][/div]

I tried SP8 and setting the uart to 16550A but still no luck, hciattach still times out.