OESF Portables Forum
Everything Else => General Support and Discussion => Zaurus General Forums => Archived Forums => Security and Networking => Topic started by: tumnus on January 09, 2005, 08:28:39 pm
-
I've finally got around to updating the Bluetooth BlueZ driver ipk.
This is only for Sharp ROMs and variants of Sharp ROMs, excluding Cacko ROMs, that use the 2.4.18 kernel. So for example this includes Sharp ROMs on SL-5500, SL-5600, SL-6000, SL-C850, but NOT SL-3000.
Here's some of the improvements:- Ambicom BT2000C Support. Thanks to tetron for spotting this had been included in the latest drivers. EDIT: Actually it doesn't look like this is working
- Socket Card Rev G Support without requiring the extra bluez-csr-serial ipk. Thanks to maslovsky for sorting this out
- Hopefully Dlink, Mavin, Billionton, BrainBoxes, and Dell cards should all be supported 'out of the box'
- Should work 'out of the box' on the SL-6000. (It moves /etc/pcmcia.bm3.conf out of the way on installation and back again on removal) Thanks to DrWowe for spotting what was wrong previously
- EDIT: Included hci_usb driver would should allow SL-6000L owners to use USB Bluetooth dongles with the appropriate USB cable.
EDIT: The PAN profile should be working now as I resolved a kernel module problem.
Before installing the new ipk, backup your files under /etc/bluetooth and /etc/pcmcia/peers. Then you can easily restore them after installing the new ipk. (You will need to run '/etc/rc.d/init.d/bluetooth restart' after restoring rfcomm.conf and hcid.conf)
Also uninstall all bluez packages before installing this one, including the bluez-csr-serial, which is no longer required with the new package.
So here is the new ipk (Note: the 1st, 3rd and 4th underscores [_] in the filename need to be changed to dashes [-] after downloading):
-
I have also improved the susp-resume-bluez package so that all Bluetooth cards should come back automatically after a suspend resume cycle. This includes Socket Rev G cards.
Remember to install susp-resume (http://www.elsix.org/index.php?w=project&p=suspresume) and sudo (http://www.zaurususergroup.com/modules.php?op=modload&name=UpDownload&file=index&req=getit&lid=184) if you haven't already.
Uninstall the old package and try this one instead (Note: change the 1st and 2nd underscores [_] to dashes [-] after downloading):
-
Please test the ipks above and let me know whether they work with your Bluetooth card or not.
As stated above, the PAN profile currently isn't working, but DUN should work fine.
-
I think I might have made a mistake for the serial based cards. They probably work when bluetooth is started or restarted, but not after a resume or inserting the card.
If this is the case, I think it may be fixed by replacing the following line in /etc/pcmcia/bluetooth.conf
class "serial" module "serial_cs"
with
class "bluetooth" module "serial_cs"
-
No one tested these ipks yet?
-
Sorry, I don't have anything bluetooth to test with... Great to hear that someone's doing such cool stuff anyway Are you using OpenEmbedded, or do you have plans to integrate your work? Would surely be great...
Cheers
Philipp
-
I've fixed the unresolved symbols problem in the bnep module, so the PAN profile should now be working. I think I've also corrected the PCMCIA config file so serial cards should always work. The alpha2 ipk can be downloaded from the first post above.
-
Here are some results:
Zaurus 5500, Sharp ROM 3.10
sudo, suspend-resume, suspend-esume-bluez, bluez drivers, qpe-terminal
Ambcom BT2000E, Anycom - work
Socket G, Billionton, Anycom C300 (new rev) - don't work. You should be able to make both cards working - see my PM I've sent you yesterday.
-
To get the Billionton Bluetoothcard working you must first set up the serial device with "setserial /dev/ttyS3 baud_base 921600". Then you load the kernelmodule "modprobe hci_uart" and last do "hciattach /dev/ttyS3 bcsp".
When you do "hciconfig -a" you see that the bluetoothcard is working.
Above works for me Both for the SharpRom (with tumnus packages) and for OZ 3.5.2
-
To get the Billionton Bluetoothcard working you must first set up the serial device with "setserial /dev/ttyS3 baud_base 921600". Then you load the kernelmodule "modprobe hci_uart" and last do "hciattach /dev/ttyS3 bcsp".
When you do "hciconfig -a" you see that the bluetoothcard is working.
Above works for me Both for the SharpRom (with tumnus packages) and for OZ 3.5.2
Yes, I know - that's what is done automaticaly in Cacko ROM
I've sent tumnus all nessesary scripts to make it work in his package too.
-
I know I need to add some scripting options for the setserial stuff for other cards, but I don't know why the Socket Rev G card is not working as that does not need any special setserial settings.
It's a little hard to debug these things without the card. I'm guessing there is an error or something lacking in my bluetooth pcmcia script somewhere and because of its dependencies I haven't been able to test any of the serial section.
-
I know I need to add some scripting options for the setserial stuff for other cards, but I don't know why the Socket Rev G card is not working as that does not need any special setserial settings.
It's a little hard to debug these things without the card. I'm guessing there is an error or something lacking in my bluetooth pcmcia script somewhere and because of its dependencies I haven't been able to test any of the serial section.
The only way it worked for me is when all scripts are executed from /etc/pcmia/serial, not /etc/pcmcia/bluetooth (like in your serial package). That's how it's done in Cacko ROM
-
Hi folks,
I have the SL5000D and cacko rom. I recently bought the Socket bluetooth CF card and would appreciate any help and pointers to get it going. If you can just direct me to any posts or how-to's I'd appreciate it.
Thanks,
spectrum
-
I've just installed the drivers on my Zaurus c860 using Cacko 1.21b and a Socket rev F card.
When I go into Network Settings and attempt to add add a modem to my Bluetooth Dial-up connection the script immediately says "No devices with DUN profile found" without scanning. It was able to discover my mobile phone immediately prior to installing the ipkg listed above.
Do you have any idea what I might try to get my phone working again with your updated drivers? I'd love to get these working (and contribute any resulting knowledge), but if that's not possible, will it be possible to "roll back" to my working driver, or will I need to restore a backup?
Thanks.
EDIT: sorry, I just noticed that you said EXCLUDING Cacko roms. I'ma go restore a backup now...
-
OK, here's a challenge to anyone with a serial based Bluetooth card (such as the Socket Rev G/H):
- Get the latest ipk working with your card without hacking any default ROM files (i.e. /etc/pcmcia/serial) or at least tell me why using the same serial commands in /etc/pcmcia/bluetooth won't work
No one has reported whether the new susp-resume-bluez ipk works better either...
-
Tumnus,
You are the man
I've been tearing my hair out trying to get PAN to work with my C860. Finally came to the conclusion that the bnep module must be the problem (seemed to be no communication between UDP/TCP and L2CAP). Thinking I'm out of luck, I did a search and here you are with an instant (and very new) solution ! Many Thanks.
By the way, I can't comment on the new suspend/resume - the old one worked fine for me.
By the way(2), any idea how to auto set the IP when bnep port becomes available on connection ? All the searches I've done come up with a recommendation which doesn't work.
(C-860 Standard ROM, BlueMonkey (LSE039), PANning to XP with D-Link DBT-120)
-
Using BT2000E on 6000L.
Downloaded the driver and changed th (_) to (-) where required.
I got the driver installed and confirmed with hciconfig.
Then I began the connecting to bluetooth enabled phone. Nokia 3660. It's bluetooth and Irda enabled.
The link to 'Bluetooth Dialup Applet' was broken so I went to the next suggestion ' Instead create a dialup connection with the Bluetooth entry in the Network application and set the rfcomm device to /dev/rfcomm0'
I can't find 'Bluetooth entry in the network application"
When I go to /dev I get a window that says 'can't show /dev directory'.
I have an Irda connection to my phone I use it for transferring files. I use the bluetooth connection to talk to another bluetooth cell phone. But I can't talk to my Zaurus.
-
I've corrected the applet links in the Bluetooth howto (https://www.oesf.org/index.php?title=Bluetooth).
But as for not using the applets, if you read the howto carefully, you create an IrDA network connection and then hack the PPP script to make it use the Bluetooth rfcomm device.
I don't know what you were using to get that error message about /dev, but in the terminal, if you type 'ls -l /dev/rfcomm*' it should list all of the rfcomm devices.
-
OK, here's a challenge to anyone with a serial based Bluetooth card (such as the Socket Rev G/H):
- Get the latest ipk working with your card without hacking any default ROM files (i.e. /etc/pcmcia/serial) or at least tell me why using the same serial commands in /etc/pcmcia/bluetooth won't work
No one has reported whether the new susp-resume-bluez ipk works better either...
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=62761\")
Hi, I'm back.
I'm going to try the new drivers soon (I'll probably have time to play over the weekend). I've just been looking over some of the old forum posts about this. For me, the show-stopper is described at [a href=\"https://www.oesf.org/forums/index.php?showtopic=2275&st=0&p=13402&#entry13402]https://www.oesf.org/forums/index.php?showt...402&#entry13402[/url] i.e. it is not that the commands don't work when invoked from /etc/pcmcia/bluetooth, but that /etc/pcmcia/bluetooth isn't run at all when the card description is in /etc/pcmcia/bluetooth.conf . The only way around this that I found was to remove the card description from bluetooth.conf, so my Z falls back on /etc/pcmcia/serial. I never managed to find out how to investigate this beyond the obvious/trivial (file permissions, etc.), so if anyone could give me any pointers I would be very grateful.
By the way, just unpacking the IPK and eyeballing your files, I found the following syntax error in /etc/pcmcia/bluetooth:
case "$1" in
start,resume)
...
stop,suspend)
should be
case "$1" in
start|resume)
...
stop|suspend)
But I don't think that is the problem from the past - the current version of this file on my Z (which would have been the last one I tried) is syntactially OK
Regards,
P.
-
/etc/pcmcia/bluetooth isn't run at all when the card description is in /etc/pcmcia/bluetooth.conf .
In the latest bluetooth.conf, you should see a device entry called "serial_cs". Any card entry bound to "serial_cs" will run the script as defined by the class attribute of the device. So the latest script should in theory run /etc/pcmcia/bluetooth for serial cards after binding the serial driver to it.
By the way, just unpacking the IPK and eyeballing your files, I found the following syntax error in /etc/pcmcia/bluetooth:
case "$1" in
start,resume)
...
stop,suspend)should be
case "$1" in
start|resume)
...
stop|suspend)[div align=\"right\"][a href=\"index.php?act=findpost&pid=64704\"][{POST_SNAPBACK}][/a][/div]
Aha! Thanks for spotting that. Don't know how that got in there. Maybe that's why the script wasn't working
I'll post a new ipk with the corrections shortly.
-
I've corrected the syntax error spotted by pakman and included the hci_usb driver for SL-6000 users with USB dongles. The alpha3 package is now available on the first post in this topic.
-
No one with a serial based Bluetooth card tried the alpha3 package (https://www.oesf.org/forums/index.php?showtopic=9995&view=findpost&p=61520) yet?
-
I'm in the process. Making the Irda connection a bluetooth connection is my sticking point.
-
Tumnus,
Thanks for your effort to bring Bluetooth to Zaurus.
I had SL-6000 in stock Sharp ROM and Ambicom (old one) working with the old package. Just got a Socket N CF card lately and try to make it work with the new pacakge but didn;t quite work. The Z went as far as "connecting" (after "initialing modem") but never made the "connected" status. The phone (Siemens S56) also shows they were connecting so I think I am pretty close.
I also misplaced my Ambicom card so I have no way to test if that card will work with the new package. Where should I look to make the Socket card work with the new package?
Thanks
Frank
-
Ok, it's working now. All I did was eject the Bluetooth card and reinserted again. Work just like before and the card is flush with the Z.
However, the resume is not working. Even tried it one more time and same result. Have to re-insert the card everytime I power the Z off.
Frank
-
hey tumnus,
Here's another input.
I tried the alpha3 with a Socket revG and the new susp-resume-bluez (0.9.2) on SL-C860.
The alpha3 package seemed fine, but after a suspend I had to eject/insert the card to get it to work again.
Actually, I noticed 2 things when coming back from standby.
1. "hciconfig" would not display any info about the card.
2. cardctl status would show the card as being in "suspend" mode. Issuing a "cardctl resume" changes the status to ready, and both "hcitool dev" and "hciconfig" would now display the card information.
So I added "cardctl resume" inside the apm.d/bluetooth script (outside of "if" statements) and now my card seems to come back up without having to eject it.
I'm not sure what I'm doing, just trying things out. Hope this can make sense to you.
-
Does the card automatically eject and reappear when you resume? Look at the CF icon on the taskbar when you resume. If nothing happens to it, did you remember to install the susp-resume and sudo packages too?
-
Hi Tumnus,
Finally got around to trying the new bluez-zaurus packages, and it works! I deinstalled the old bluez-zaurus, susp-resume-bluez and bluez-csr-serial packages (after carefully making copies of all the files involved so I wouldn't lose my hacks - I used 'ipkg files ...' to help with this).
I installed the new bluez-zaurus package, copied my previous /etc/bluetooth/rfcomm.conf and /etc/bluetooth/hcid.conf back, and everything worked! (Pairings were still OK because this procedure doesn't touch /etc/bluetooth/link_key.) The name of the card now correctly appears when inserted or when I tap the eject icon. More importantly, when the Z is suspended, I only have to do a 'cardctl resume', and after a second or two, 'hciconfig' shows that the interface is up again - this is a real advance over the previous state of affairs where the interface stayed obstinately down unless I did '/etc/rc.d/init.d/bluetooth stop' followed by '/etc/rc.d/init.d/bluetooth start' . Unlike sornett, I didn't have to do an eject/insert to get this to work.
I haven't tried the new susp-resume scripts yet, because being paranoid I would rather leave the card suspended and explicitly enable it when I need it My own scripts are pretty trivial now - a one-liner to start using the card, and a couple of lines to shut down any running PAN's before suspending the card when I have finished.
Many thanks to you and Maslovsky for sorting this out,
P.
-
Does the card automatically eject and reappear when you resume? Look at the CF icon on the taskbar when you resume. If nothing happens to it, did you remember to install the susp-resume and sudo packages too?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=68085\"][{POST_SNAPBACK}][/a][/div]
hello tumnus.
Yes sudo and susp-resume are installed.
With a Socket Rev F card, I observed that the icon disappeared and reappeared.
But with an H/G card, it does not happen.
The script /etc/apm.d/bluetooth has the follwing section
if ["'/usr/sbin/hciconfig" != "" ]; then
...
fi
I tried commenting out all the resume lines in that script and issuing the commands manually. That's where I noticed that the hcidonfig command returned nothing, which means that the other commands in the if statement won;t be executed either.
The other thing was that cardctl status showed the card as suspended. resuming the card restored everything: hciconfig ok, hcitool ok etc...
that's why I simply added the cardctl resume statement to the apm.d/bluetooth script, and things are now working fine.
shouldn't the card manager take care of resuming the card ?
-
sornette, thanks for pinpointing that. maslovsky just told me about that too.
I'll see if I can write some commands on resume that work with all cards. The reason for that if statement on resume was to only run those commands when there is a Bluetooth card inserted or was inserted when your suspended. For the non-serial based cards this seems to work.
-
Tumnus,
Thanks for the effort!!!
I need some help here. I have a SL-5500 running TKC ROM with cacko latest kernel upgrade, and as I understand, this cacko release already support my Ambicom BT-2000CF (white label), as I have been having some trouble trying ambicom to exchange it for the old one. I only have basic experience with linux (SUSE 8 and 9 who babysits us newbies with the graphical configuration program).
I have not applied your patches as I already have latest Cacko, Card is recognized when plugged in as MAVIN BLUETOOTH CARD. From there on, I have no idea how to get devices paired (my interest is mainly with cell phone ericsson T39m and PC).
I am in the process to get an Aircable device and try to sell this one to an Ipaq owner down here (in Costa Rica).
What do you think? Any hope to make this one work?
Any help appreciated.
Otto Acuña
Servinfor Data Recovery Services
www.recuperacion.net
San Jose, Costa Rica
Central America
-
I'm afraid the latest Ambicom BT CF card still isn't supported at all. There are no Linux drivers for it.
In any case, instructions for setting up Bluetooth can be found here (https://www.oesf.org/index.php?title=Bluetooth)
-
I've uploaded a new version of the susp-resume-bluez package that should resume serial based cards like the Socket Rev G card properly. See the Second Post (https://www.oesf.org/forums/index.php?showtopic=9995&view=findpost&p=61521)
-
*sigh* yep, can definitely confirm the ambicom bt2000c CF card isn't working.... *grumble* ... but the ambicom bt2000 usb dongle works fine... though I really look rather over-techied out when I whip out my digital river usb converter, smack the bluetooth dongle on it, slap it into my gigantic sharp zaurus (with the expansion CF pack lol...) ... ohhh boy... batman factor is on an all-time high these days...
-
I'm afraid the latest Ambicom BT CF card still isn't supported at all. There are no Linux drivers for it.
I have no problem to use this card on my laptop Toshiba Satellite 1115-S103 with SUSE 9.2.
-
I have no problem to use this card on my laptop Toshiba Satellite 1115-S103 with SUSE 9.2.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=68928\"][{POST_SNAPBACK}][/a][/div]
What does 'cardctl ident' give for your card? The BT2000E card is supported. The BT2000C card is not. The BT2000C card is the later card.
-
I have no problem to use this card on my laptop Toshiba Satellite 1115-S103 with SUSE 9.2.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=68928\"][{POST_SNAPBACK}][/a][/div]
What does 'cardctl ident' give for your card? The BT2000E card is supported. The BT2000C card is not. The BT2000C card is the later card.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=68933\"][{POST_SNAPBACK}][/a][/div]
Socket 1:
product info: "AmbiCom BT2000C", "Bluetooth PC/CF Card", "", ""
manfid: 0x022d, 0x2000
function: 2 (serial)
In fact I have both BT2000E (black top) and BT2000C (blue top).
BTW, SUSE 9.2 found the card BT2000C and Belkin Bluetooth USB adapter once!
Just works!
-
6k, stock rom, adf's fast kernel
Socket BT rev H with stamp "8510-00159H". Did a search with "rev H" in the whole forum. People reported this exact card did work both with Cacko and Pdax rom.
installed
sudo
bluez-zaurus_2.13-2.4.18-alpha3_arm.ipk
susp-resume-bluez_0.9.3_arm.ipk
card recongnized fine as: Socket Bluetooth CF Card Rev G+
but stuck at the point with hciconfig giving back
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU 0:0
etcI know these numbers shouldn't be all zero.
tried
hciattach /dev/ttyS3 bcsp 230400same result.
Anybody get hint? TIA
-
i got it figured out. i'm typing using the bt dialup. my phone LG PM-325 with Sprint PCS Vision.
first of all, I flashed back to the stock 6K kernel. Now hciconfig returns the correct MAC addr dor my bt card
secondly, I have to do a SW update on my LG phone. This updates the phone OS to v18, which specificly says "improves the bluetooth performance". Without this, sdptool browse won't find anyservice and returns time out.
now. with sdptool browse working. the rest is just following up the bt how-to
note: dial up service is actually set as channel 4 in the LG
enabled my bt phone as always visible
and fire up dial-up connection. that't it. I see the 3G RX TX in my LG phone. Thanks Tumnus for the bluz driver.
-
more updates about suspend-resume
bluez-zaurus_2.13-2.4.18-alpha3_arm.ipk
susp-resume-bluez 0.9.3
sudo 0.1
suspend resume seems still problematic
hciconfig is able to return the correct MAC address for the BT CF card. However, sdptool browse returns : "inquiry failed".
hcitool dev didn't report any device
then tried. /etc/rc.d/init.d/bluetooth restart
shutting down is ok, but
starting Bluetooth ... BCSP initialization timed out
have to do an
cardctl eject/insert or physically reinsert the card to bring the bluetooth back
-
will those nice drivers work with a c1000 used with a belkin bluetooth cf?
-
will those nice drivers work with a c1000 used with a belkin bluetooth cf?
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=77150\")
Look here: [a href=\"https://www.oesf.org/index.php?title=Bluetooth_Card_Support]https://www.oesf.org/index.php?title=Bluetooth_Card_Support[/url]
If a card isn't listed here, then at best no one has tried or updated the list and at worst it doesn't work at all.
-
thanks for your reply and continuous support tumnus. if it werent for helpful ppl like you the zaurus community would be a whole lot different. thanks again, we really owe you a lot of things..
-
https://www.oesf.org/index.php?title=Bluetooth_Card_Support (https://www.oesf.org/index.php?title=Bluetooth_Card_Support)
If a card isn't listed here, then at best no one has tried or updated the list and at worst it doesn't work at all.
At this webpage I can see that the Billionton card is unsupported while at post #9 I've read that it works...what's the truth then?
-
https://www.oesf.org/index.php?title=Bluetooth_Card_Support (https://www.oesf.org/index.php?title=Bluetooth_Card_Support)
If a card isn't listed here, then at best no one has tried or updated the list and at worst it doesn't work at all.
At this webpage I can see that the Billionton card is unsupported while at post #9 I've read that it works...what's the truth then?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=78211\"][{POST_SNAPBACK}][/a][/div]
That would come under "no one has updated the list"
If Edbo has tried his Billionton card with the packages I created and got it to work then I guess it sort of is supported. It's not working out of the box at the moment though. You have to make the changes Edbo gives.
I am also not sure whether there are several versions of the Billionton card, so I would prefer that someone with a working card updates the list as they can give specific model and ident details. That's why the list is on a Wiki page after all.
-
- All is well, essentially. So, if I only had a brain. Case closed.
-
DELETED
-
can some one confirm that bt2000c is working as stated here https://www.oesf.org/index.php?title=Bluetooth_Card_Support (https://www.oesf.org/index.php?title=Bluetooth_Card_Support) or still a no no?
thanks
-
Will this stuff work with pdaXrom?
Will this stuff work with a USB Bluetooth adaptor?
Thanks!
-
Could somebody please do me a favour & comment on the belkin card I've posted about in this thread (https://www.oesf.org/forums/index.php?showtopic=13657&hl=). I'd like to know if I have the slightlest chance of getting it to work or should I just return it? thks
-
Could somebody please do me a favour & comment on the belkin card I've posted about in this thread (https://www.oesf.org/forums/index.php?showtopic=13657&hl=). I'd like to know if I have the slightlest chance of getting it to work or should I just return it? thks
[div align=\"right\"][a href=\"index.php?act=findpost&pid=89934\"][{POST_SNAPBACK}][/a][/div]
Neither Affix nor Bluez list that BE2830 as being directly supported (but not listed as not working either). Might be too new. Bluez mailing lists mention other Belkin devices, but not that one. Affix mailing lists don't talk about anything belkin at all. If it will work with anything, it will work with Bluez.
You should see if you can find out what the chipset is on the thing... Bluez and Affix seem to list chipsets that are supported rather than all the adapters that may use them.
If the chipset is similar to other devices (it probably will be) you might have a chance.
I'd say right now your chances of it working out of the box are like 10-30%. With some work 40-70% and 30% chance of not working without you adding support (eg. writing code) yourself.
-
Here is a list of places you can by the one i use.
-------------------------------------------------------
Make sure it-
1. made in taiwan and the
2. antena is black and not blue.
3. there is also a cute sticker of a tooth surfing away from the laptop.
4. return policy if they send you the wrong one too.
http://www.amazon.com/exec/obidos/tg/detai...e&s=electronics (http://www.amazon.com/exec/obidos/tg/detail/-/B0000ALPBN/ref=ase_kaufenundbest-20/104-9271964-7246352?v=glance&s=electronics)
http://www.pricegrabber.com/search_getprod...earch=bt2000+cf (http://www.pricegrabber.com/search_getprod.php?masterid=1119175&search=bt2000+cf)
http://shopper-search.cnet.com/search?qt=b...1-cnet&tag=5017 (http://shopper-search.cnet.com/search?qt=bt2000-cf&subj=bt2000-cf%E2%88%82=google1-cnet&tag=5017)
-------------------------------------------------------
good luck
-
OK, I got to jump in here with a request for assistance.
My setup is a uk 5500 with Sharp 3.10 Rom, Bluemonkey CF card, Siemens s65 phone, UK O2 mobile account.
I followed the BlueZ howto at the top of this thread a while back and got a fair amount of success. I managed to pair up the Z & phone and allocate /dev/rfcomm0 to the pairing on the serial port channel of the s65. I created an IR dialup via the network wizard, then went into the equivalent script under /etc/ppp/peers and added in the /dev/rfcomm0 line at the top, set the phone MAC address in /etc/bluetooth/rfcomm.conf
I don't think I ever managed to get the network connection going, though the devices did pair. (Annoyingly the phone and WinXP on my work laptop function without incident.)
I had to do a Z restart a while ago & since then, everything seems to have gone horribly wrong :-/ I'm pretty sure I kicked off the bluetooth with a manual restart.
When the phone BT is enabled & nearby, I get the pairing icon for a moment then it drops,. I run the network connection and it sits in 'modem initializing'.
Even though the phone is discoverable, I do an "sdptool browse" after sudo'ing to root, all I get is
Inquiring...
Inquiring failedSo why does that happen?
Do the symptoms I've described point to something obvious?
I think the rest of my woes are with getting a connection script sorted for GPRS to O2 using the s65, but let's not go there for now! I've not managed via IR yet.
Tim
-
I don't think I ever managed to get the network connection going, though the devices did pair. (Annoyingly the phone and WinXP on my work laptop function without incident.)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=95034\"][{POST_SNAPBACK}][/a][/div]
If you use the same bluetooth cf card to pair your laptop, you loose the pair on the cellphone and thus need to repair the zaurus and cellphone.
after you successfully repair the 2 items, you need to go into settings->network and add a dial-up(bluetooth). There is such a network protocol to add. after you add this, then you go into account....
Mines is setup through at&t with digital access unlimited at 24 dollars a month.
no username and password but dialup is *99# (call service provider for this info)
init string is ATZ with bt device being the default /dev/rfcomm0
everything else is autodetect and you should just dial into it as soon as the icon appears in the taskbar when inserting the bluetooth card.
-
so What's new with everybody?
Still waiting to hear more success stories and tips on getting connected via gprs.
My problem is similar to alot of people: pairing is good, ininitializing is good, then the connected portion just hangs with nothing happening.
I'm using a socket card rev h with new 3100 standard rom with Moto razor on Rogers in Canada.
I have not found any posts on what what the chat file or PPP options etc... may be required.
I'm thinking that perhaps that is the problem.
Can people post their configurations for gprs access?
Thanks,
Bob
-
I had some trouble to get the Billionton CFBT02-B2 Bluetooth CF-Card working on my SL-C750 with original Sharp ROM. The problem was that I need to set the serial speed to 921600 and use the option "-s 921600" when calling hciattach.
To solve this problem I changed the script /etc/pcmcia/bluetooth so that the start code looks like this:
....
UART_SET=`grep "$ID" $UART_CONF | cut -f2 -d":"`
if [ "$UART_SET" != "" ]; then
DEVICE=/dev/`echo $UART_SET | sed 's,.*/dev/,,'| cut -f1 -d" "`
SPEEDOK=`echo $UART_SET | grep '^ *-s'`
IRQ=`setserial $DEVICE | sed -e 's/.*IRQ: //'`
setserial $DEVICE irq 0; setserial $DEVICE irq $IRQ
if [ "$SPEEDOK" != "" ]; then
SPEED=`echo $UART_SET | sed 's,.*-s *,,' | cut -f1 -d" "`
setserial $DEVICE baud_base $SPEED
fi
/usr/sbin/hciattach $UART_SET
fi
....
This allows to use the following line in /etc/bluetooth/uart:
"Compact Flash", "Bluetooth Card", "", "":-s 921600 /dev/ttyS3 bcsp
Maybe this helps others who have problems with this card.
Lothar
-
can some one confirm that bt2000c is working as stated here https://www.oesf.org/index.php?title=Bluetooth_Card_Support (https://www.oesf.org/index.php?title=Bluetooth_Card_Support) or still a no no?
thanks
[div align=\"right\"][a href=\"index.php?act=findpost&pid=82653\"][{POST_SNAPBACK}][/a][/div]
Has there been any progress on the BT2000CF compatibility? In a previous thread it was reported to work on SUSE 9.2? Is any of what makes this work in SUSE portable to the zaurus? Also, as stated, this link at bluez says:
Ambicom (http://www.ambicom.com/products/air2net/bt2000cf.html) BT2000C CSR Yes ? The following option is needed for hciattach initialize this card: /dev/ttyS3 bt2000c flow.
I am sorry for saying this, but to me (business user), this seems like "dark arts". I have no idea what to make of this.... ;(
Regards from the Tropics
Otto
-
might be worth looking at OpenTom and TomTom's own linux stuff as per https://www.oesf.org/forums/index.php?showtopic=16826 (https://www.oesf.org/forums/index.php?showtopic=16826) to see what TomTom have done for bluetooth!
-
This is only for Sharp ROMs and variants of Sharp ROMs, excluding Cacko ROMs, that use the 2.4.18 kernel. So for example this includes Sharp ROMs on SL-5500, SL-5600, SL-6000, SL-C850, but NOT SL-3000.
Also uninstall all bluez packages before installing this one, including the bluez-csr-serial, which is no longer required with the new package.
So here is the new ipk (Note: the 1st, 3rd and 4th underscores [_] in the filename need to be changed to dashes [-] after downloading):
[div align=\"right\"][a href=\"index.php?act=findpost&pid=61520\"][{POST_SNAPBACK}][/a][/div]
The latest package works fine for the stock sharp kernel, but is not working for the fast kernel in 6K. I believe the 6k fast kernel is a preemptive one as in Tetsu's (actually they are the same, common zaurus kernel project). Tumnus, is it possible to build a bluez package for the preemptive kernel?
after installing the package, dmesg
ttyS03 at port 0xf60003f8 (irq = 43) is a 16C950/954
BlueZ HCI UART driver ver 2.1 Copyright (C) 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky
Internal error: branch through zero: 0
CPU: 0
pc : [<00000004>] lr : [<0000a010>] Not tainted
sp : bffffa98 ip : c05bf3ec fp : c1351e5c
r10: 00000000 r9 : 00000000 r8 : c05bf080
r7 : 80000013 r6 : c1350000 r5 : c379a0a0 r4 : c05bf3a0
r3 : 00000000 r2 : 00000002 r1 : 00000009 r0 : c379a0a0
Flags: nZCv IRQs on FIQs on Mode SVC_32 Segment user
Control: 197F Table: A129C000 DAC: 00000015 PID: 0
Process hciattach (pid: 1536, stackpage=c1351000)
Stack: (0xc1351e24 to 0xc1352000)
1e20: 0000a010 00000004 60000013 c379a0a0 c05bf080 c3832248 00000008
1e40: 00000004 00000001 c1351e8c 00000000 c1351e88 c1351e60 c5996a88 c5996ae4
1e60: 00000001 c2cf8004 c2cf8004 c1350000 00000000 c3c7aa80 c2cf8014 c1351ea8
1e80: c1351e8c c59984c8 c59969ac 00000001 c59991dc c2cf8004 00000001 c1351ec4
1ea0: c1351eac c0053df4 c599849c 00000000 00000001 c2cf8004 c1351ed4 c1351ec8
1ec0: c5990d84 c0053dc8 c1351efc c1351ed8 c5992d58 c5990d78 c2cf8000 c2cf8000
1ee0: c59e2cfc c2cf8164 00000000 00000001 c1351f10 c1351f00 c59e0738 c5992b08
1f00: 00000000 c1351f2c c1351f14 c59e07fc c59e06f4 c2cf8000 c1c7c000 00000000
1f20: c1351f54 c1351f30 c59e0880 c59e07bc 00000001 c1c7c000 c1c7c000 400455c8
1f40: 400401c8 c16b5440 c1351f80 c1351f58 c0104424 c59e0824 c16b5440 400455c8
1f60: 00000003 00000001 ffffffe7 c1350000 00000004 c1351fa4 c1351f84 c007fc34
1f80: c0103f04 bffffa9c 00000003 00012b48 00000036 c0030b04 00000000 c1351fa8
1fa0: c0030960 c007f9f0 bffffa9c c0034550 00000003 400455c8 00000001 0000000f
1fc0: bffffa9c 00000003 00012b48 00000000 00012e7c bffffb18 00000004 bffffaf4
1fe0: 00012db0 bffffa98 0000a010 400fec54 60000010 00000003 00000000 00000000
Backtrace:
Function entered at [] from []
Function entered at [] from []
Function entered at [] from []
r6 = 00000001 r5 = C2CF8004 r4 = C59991DC
Function entered at [] from []
r6 = C2CF8004 r5 = 00000001 r4 = 00000000
Function entered at [] from []
Function entered at [] from []
Function entered at [] from []
r4 = 00000000
Function entered at [] from []
r6 = 00000000 r5 = C1C7C000 r4 = C2CF8000
Function entered at [] from []
Function entered at [] from []
Function entered at [] from []
r8 = C0030B04 r7 = 00000036 r6 = 00012B48 r5 = 00000003
r4 = BFFFFA9C
Code: bad PC value.
note: hciattach[1536] exited with preempt_count 2
<<<< Init_Module PASS >>>
not surprisingly, hciconfig didn't give me back any MAC address
hci0: Type: UART
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:12 acl:0 sco:0 events:0 errors:0
TX bytes:6 acl:0 sco:0 commands:0 errors:0
-
I just bought an AIRNET ABT201 USB dongle, and I haven't been able to get it to work on my Zaurus. (I used bluez_zaurus_2.13_2.4.18_alpha3_arm.ipk, attached to the first post in this thread.) Has anybody else tried this dongle?
Zaurus 6000L, stock kernel 2.4.18, no other bluetooth software installed.
It worked with my desktop system, so I know there exist Linux drivers--although that was the 2.6 kernel.
I bought it because (a) it was $1 after rebate (newegg.com) and ( I wasn't able to find good information on what dongles work with Linux; the only reference I could find mentioned the supported chips, not the consumer devices.
Thanks!
-
I just bought an AIRNET ABT201 USB dongle, and I haven't been able to get it to work on my Zaurus.
I've since tried a Kensington and a D-Link, and all three exhibit the same behavior: if bluez is installed when I plug in the dongle, the Z freezes and I have to hit the Reset button. I think I'll go for a CF card...
-
I really don't know why....
I've just got a AmbiCom BT-2000-CF (Blue head) card and found that is not working for the ipk in the 1st post...
but when i used Meanie's package with qshdlg installed, the bluetooth gui and the hciconfig package runs that properly....
of course, for pdaxrom (in beta4 & r121), that CF BT is still not working (/dev/ttyS3 is not present for any hciattach) ....
Re: you can get the latest version of qshdlg from there: -
http://tbox.jpn.org/wiki/linuzau/wiki.cgi?qshdlg (http://tbox.jpn.org/wiki/linuzau/wiki.cgi?qshdlg)
-
I really don't know why....
I've just got a AmbiCom BT-2000-CF (Blue head) card and found that is not working for the ipk in the 1st post...
but when i used Meanie's package with qshdlg installed, the bluetooth gui and the hciconfig package runs that properly....
of course, for pdaxrom (in beta4 & r121), that CF BT is still not working (/dev/ttyS3 is not present for any hciattach) ....
[div align=\"right\"][a href=\"index.php?act=findpost&pid=143856\"][{POST_SNAPBACK}][/a][/div]
please explain the qshdlg. I cant get meanies to work on mines. Maybe i need qshdlg?
-
I really don't know why....
I've just got a AmbiCom BT-2000-CF (Blue head) card and found that is not working for the ipk in the 1st post...
but when i used Meanie's package with qshdlg installed, the bluetooth gui and the hciconfig package runs that properly....
of course, for pdaxrom (in beta4 & r121), that CF BT is still not working (/dev/ttyS3 is not present for any hciattach) ....
[div align=\"right\"][a href=\"index.php?act=findpost&pid=143856\"][{POST_SNAPBACK}][/a][/div]
please explain the qshdlg. I cant get meanies to work on mines. Maybe i need qshdlg?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=143869\"][{POST_SNAPBACK}][/a][/div]
qshdlg is a shell dialog app like opie-sh but superior in functionality
-
installed qshdlg. finds phone but wont connect through DUN. Anyhelp will suffice. The old drivers work but not the new ones. I'll dive into it later and see whats going on. Most likely i missed a step somewhere.
-
Who kept this driver, please answer! I can not run BT2000c on the SL-5500.