OESF Portal | OESF Forum | OESF Wiki | LinuxPDA | #planetgemini chat on matrix.org | #gemini-pda chat on Freenode | #zaurus and #alarmz chat on Freenode | ELSI (coming soon) | Ibiblio

IPB

Welcome Guest ( Log In | Register )

2 Pages V   1 2 >  
Reply to this topicStart new topic
> Bluez: Billionton Annoying Problems
merli
post Jun 6 2005, 07:13 AM
Post #1





Group: Members
Posts: 227
Joined: 27-April 05
Member No.: 7,008



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?
Go to the top of the page
 
+Quote Post
Grimmy
post Jun 9 2005, 02:35 AM
Post #2





Group: Members
Posts: 17
Joined: 18-May 05
Member No.: 7,160



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:

https://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
Go to the top of the page
 
+Quote Post
merli
post Jun 9 2005, 05:19 AM
Post #3





Group: Members
Posts: 227
Joined: 27-April 05
Member No.: 7,008



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:

https://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
Go to the top of the page
 
+Quote Post
tumnus
post Jun 11 2005, 03:21 PM
Post #4





Group: Members
Posts: 1,176
Joined: 3-October 03
From: UK
Member No.: 547



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.
Go to the top of the page
 
+Quote Post
rleao
post Jul 3 2005, 07:13 PM
Post #5





Group: Members
Posts: 9
Joined: 26-June 05
Member No.: 7,462



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.
Go to the top of the page
 
+Quote Post
zmiq2
post Jul 4 2005, 02:20 AM
Post #6





Group: Members
Posts: 383
Joined: 3-December 03
Member No.: 1,038



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.
Go to the top of the page
 
+Quote Post
Rev.Tigger
post Jul 4 2005, 05:19 AM
Post #7





Group: Members
Posts: 48
Joined: 21-May 05
From: Staffs, UK
Member No.: 7,176



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.
Go to the top of the page
 
+Quote Post
zmiq2
post Jul 4 2005, 06:31 AM
Post #8





Group: Members
Posts: 383
Joined: 3-December 03
Member No.: 1,038



As far as I can see, you should also
# modprobe bluez

before haciattach
Go to the top of the page
 
+Quote Post
Rev.Tigger
post Jul 4 2005, 06:37 AM
Post #9





Group: Members
Posts: 48
Joined: 21-May 05
From: Staffs, UK
Member No.: 7,176



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
Go to the top of the page
 
+Quote Post
zmiq2
post Jul 4 2005, 08:41 AM
Post #10





Group: Members
Posts: 383
Joined: 3-December 03
Member No.: 1,038



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.
Go to the top of the page
 
+Quote Post
Rev.Tigger
post Jul 4 2005, 09:45 AM
Post #11





Group: Members
Posts: 48
Joined: 21-May 05
From: Staffs, UK
Member No.: 7,176



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
Go to the top of the page
 
+Quote Post
Hrw
post Jul 5 2005, 04:49 AM
Post #12





Group: Members
Posts: 1,366
Joined: 11-January 04
From: Poland
Member No.: 1,413



try to add "sleep 2" before hciattach - maybe card need some time to get working...
Go to the top of the page
 
+Quote Post
Rev.Tigger
post Jul 5 2005, 07:52 AM
Post #13





Group: Members
Posts: 48
Joined: 21-May 05
From: Staffs, UK
Member No.: 7,176



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
Go to the top of the page
 
+Quote Post
zmiq2
post Jul 6 2005, 01:46 AM
Post #14





Group: Members
Posts: 383
Joined: 3-December 03
Member No.: 1,038



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.
Go to the top of the page
 
+Quote Post
Grimmy
post Jul 6 2005, 02:40 AM
Post #15





Group: Members
Posts: 17
Joined: 18-May 05
Member No.: 7,160



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.
Go to the top of the page
 
+Quote Post

2 Pages V   1 2 >
Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 13th December 2019 - 07:20 AM