 3.5.4.1-alpha2 And Bluetooth Socket Rev G, Working..but only up to 3.5.4.1-test |
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > Angstrom & OpenZaurus  |
 Mar 19 2006, 02:20 PM
Post
#1
|
|
 Group: Members Posts: 163 Joined: 11-March 04 From: IT Member No.: 2,270  |
Hi,
still unable to get Socket CF 2.5 Rev. G properly working with 2.6 kernels on my 860. It's a serial_cs bluetooth card. Any hints? TIA Ant |
 |
 
|
|
Mar 20 2006, 07:40 AM
Post
#2
|
|
 Group: Members Posts: 5 Joined: 8-December 03 Member No.: 1,091 |
This is a known problem in 2.6 kernel tree - patch could not get to the mainline
for several months now. But this can be fixed by aplying the following patch: http://www.ussg.iu.edu/hypermail/linux/ker...509.2/0072.html and rebuilding the kernel. I hope someone would include it in OE and creates a fixed build. --Alex Y. QUOTE(ant @ Mar 19 2006, 05:20 PM) Hi,
still unable to get Socket CF 2.5 Rev. G properly working with 2.6 kernels on my 860. It's a serial_cs bluetooth card. Any hints? TIA Ant  |
|
|
|
|
Mar 20 2006, 08:54 AM
Post
#3
|
|
|
Group: Members Posts: 163 Joined: 11-March 04 From: IT Member No.: 2,270 |
Thanks, Alex Y.
Very interesting...but I fear there's more: it seems to me the bt interface is ttyS1 but the scripts are binding ttyS3... Is it right so? |
|
|
|
|
Mar 20 2006, 10:30 AM
Post
#4
|
|
|
Group: Members Posts: 31 Joined: 19-November 04 From: None Member No.: 5,530 |
In Opie there is missing something :-( In 3.4.5 RC I got my BT-card up and running. Now I got an error that hciattach can't set the port /dev/ttyS3 and initialize the device. The same for /dev/ttyS1
The much stranger because in GPE it works directly after the hciattach. Did I miss something  <edit> How strange  Inserting the BT-card and looking in the logfile with dmesg gives no output. Restarting the pcmcia-service did the trick  . Dmesg gives me the output that the BT-card was attached to /dev/ttyS03, but using /dev/ttyS3 also works.</edit> |
|
|
|
|
Mar 20 2006, 03:40 PM
Post
#5
|
|
|
Group: Members Posts: 163 Joined: 11-March 04 From: IT Member No.: 2,270 |
Good news!
All seems now working with 3.5.4.1-test. Great! Ant |
|
|
|
|
Mar 20 2006, 11:25 PM
Post
#6
|
|
 Group: Members Posts: 1,376 Joined: 11-January 04 From: Poznań, Poland Member No.: 1,413 |
ant: good to know - thx
|
|
|
|
|
Apr 11 2006, 06:55 AM
Post
#7
|
|
|
Group: Members Posts: 163 Joined: 11-March 04 From: IT Member No.: 2,270 |
QUOTE(Hrw @ Mar 21 2006, 08:25 AM) ant: good to know - thx Problem is back with 3.5.4.1-test/alpha2. I did ipkg upgrade yesterday evening but I see there are some new init scripts dated Apr. 11: I'll try these later. Ant EDIT: http://www.kernel.org/pub/linux/utils/kern...mcia/howto.html 3.2. pccardctl (replaces cardctl). but pccardctl segfaults... EDIT2 actually pccardctl does NOT segfault if invoked with these 2 args: pccardctl ident pccardctl info I think the problem is caused by the permission on /dev/ttyS3: I see different settings in etc/device_table and in /etc/default/devpts. session log: ... ... df: /dev/.static/dev: Permission denied BCSP initialization timed out Thus, I suppose there is a problem with udev: what is this "failed" dir? /dev/.udev/failed/class@pcmcia_socket@pcmcia_socket0 |
|
|
|
|
Apr 12 2006, 02:49 PM
Post
#8
|
|
|
Group: Members Posts: 163 Joined: 11-March 04 From: IT Member No.: 2,270 |
After a reflash with the latest alpha2 the card works (at 230400 for the moment).
From hciattach.c 00830 /* Socket Bluetooth CF Card (Rev G) */ 00831 { "socket", 0x0104, 0x0096, HCI_UART_BCSP, 230400, 230400, 0, bcsp }, Just edited /etc/sysconfig/bluetooth BLUETOOTH=yes BLUETOOTH_PORT=/dev/ttyS3 BLUETOOTH_PROTOCOL=bcsp BLUETOOTH_SPEED=230400 et voilà... The speed should come up to 921600, but I have before to check the speed of the serial port. (setserial /dev/ttyS3 baud_base 921600 would be optimal but I have to try) Here another related post: http://66.249.93.104/search?q=cache:PF5PvA...en&ct=clnk&cd=6 Ant P.S. I don't see the dbus_pin_helper mentioned in /etc/bluetooth/hcid.conf, so I tried installing bluez-dbus-bluepin but don't see any difference, the phone disconnects after "spdtool browse". I think it is just a "pairing" issue. The last option would be the "old but good" givepin script. |
|
|
|
|
Dec 5 2006, 05:47 AM
Post
#9
|
|
 Group: Members Posts: 902 Joined: 22-May 04 Member No.: 3,385 |
Hi:
I have the same card and can't get it to work. Could you provide a summary of what you had to change to get it to work? Which files you edited and where you changed prefs, if you had to install anything to get it to work. I have an Anycom Bluetooth card that works, but it sticks out, so would like to use the Socket one, since it doesn't stick out, but can't get it working. Thanks. |
|
|
|
|
Dec 6 2006, 07:09 AM
Post
#10
|
|
|
Group: Members Posts: 902 Joined: 22-May 04 Member No.: 3,385 |
By clean booting and then restarting PCMCIA services and sticking the Socket card in, I can pair with the phone. This is progress. But how do I dial and connect to the Web?
Using the Anycom card the ppp/peers file I dial uses /dev/rfcomm0 I've determined this needs to be changed to /dev/ttyS3 right? But now when I dial it says: warning: write() on stdout returned 0 -- write failed: No such file or directory It's not a permissions thing, since it does it if I dial as root too? What can I do to make this work? |
|
|
|
|
Dec 9 2006, 08:05 AM
Post
#11
|
|
|
Group: Members Posts: 163 Joined: 11-March 04 From: IT Member No.: 2,270 |
QUOTE(ShiroiKuma @ Dec 6 2006, 05:09 PM) ... What can I do to make this work? Probably nothing...something is really broken in the oz 3.5.4.1 release... pcmciautils vs cardctl ... that's the change I guess. Let's follow up here: http://www.oesf.org/forums/index.php?showtopic=22066 THX Ant |
|
|
|
|
2 User(s) are reading this topic (2 Guests and 0 Anonymous Users)
0 Members:
|
Lo-Fi Version | Time is now: 21st May 2013 - 05:22 AM |