OESF Portables Forum
Everything Else => Sharp Zaurus => Model Specific Forums => Distros, Development, and Model Specific Forums => Archived Forums => C1000/3x00 General discussions => Topic started by: Stilgar on December 07, 2004, 06:17:46 pm
-
I have been trying to set up bluetooth with the bluez drivers and apps. Sadly, that's not a howto - I did not suceed. The main thing that lacked was drivers for the 2.4.20 kernel. I had drivers for the 2.4.18 so I used them, but it caused kernel panic (though the drivers would load).
Did anyone have any success? Got the drivers compiled for the 2.4.20 kernel (now that you can fetch the source) ?
-
Good news.
Had a word with tumnus (the person that has been doing much of the bluez stuff) and he is planning to look at recompile of bluez for use with the C3000.
So, should get it soon (hopefully).
-
Yeah, the SL-3000 kernel modules are compiling as I type.
Hopefully there won't be any problems (the latest BlueZ patches had a few failed chunks, but it doesn't look like it was on bits I will be compiling).
So then I'll compile the latest BlueZ utilities and libraries, package them up as before and then put them somewhere for testing.
If that all works, I'm going to update the other BlueZ packages with the latest utilities and libraries and see about getting cards like Socket Rev G working out of the box and put that into both sets of packages.
-
Modules have compiled ok. Now I need to know where they go, so what is the directory under /lib/modules on the SL-3000? I'm guessing this has changed in more than just the kernel version.
-
Have all the utilities and libs compiled now (well I think so. libsdp seems to have been removed in the latest BlueZ) and the package is ready to be zipped up. All I need now is that directory info I asked for above.
-
tumnus,
The directory under lib/modules is: 2.4.20
Inside 2.4.20 we have the directories: kernel, net, pcmcia and rsaipsecc. Also inside 2.4.20 are the files modules.dep, modules.generic_string, modules.isapnpmap, modules.parportmap, modules.pcimap, modules.usbmap.
If you need anymore info, let me know soon as I have to send the C3000 back on Monday the 20th.
Lisa
-
It's just /lib/modules/2.4.20 ?
On the other Zauruses its /lib/modules/2.4.18-rmk7-pxa3-embedix
Obviously the kernel version is different, but I didn't know if the rest of the directory name had changed.
-
Yep, it's really /lib/modules/2.4.20.
-
Ok, thanks. I was having a hard time believing they did something sane
Here is the ipk then (as long as the upload works).
It is equivalent to the bluez-zaurus_2.3-2.4.18d.ipk for other Zauruses, so the Bluetooth howto should still apply.
Whoever tests this, please check your Bluetooth card comes up with hciconfig and test the discovery or other devices with hcitool and sdptool.
EDIT: bluez_zaurus_2.12_2.4.20_alpha_arm.ipk doesn't work. Look out for an alpha2 ipk below.
-
tumnus,
I gave it a try. On installation it told me to rename the package to bluez-zaurus_arm and try again. Did that and the installer then launched successfully.
As it ran, the machine dopped to runlevel 5, and was attempting modprobe if I recall corectly. It echoed this about 5x on the display then gave an error to the effect that it couldn not find wlan0. No BT card was in the slot, but my wifi card was-- been a while since I installed Bluez on my c860 but I dont recall anything like this happening or it being a no-no to have an wifi card in the slot.
Then the machine rebooted. Hmmm... I will play more tomorrow.
Since this is a review unit, I'll be returning the c3000 on Monday. So I'll try to explore some more tomorrow. If it's easier tumnus, you can email me directly with any questions. I think you have my email- it's my first name @pdabuyersguide.com.
lisa
-
Tried again without the wifi ccard in the slot and the installer worked fine
-
Cool. Thanks for testing it. Don't know what happened there with the WiFi card in it. Must remember that as an instruction for installation.
The filename got mangled in the upload to the forum. It should be:
bluez-zaurus_2.12-2.4.20-alpha_arm.ipk
Do all of the BlueZ tools work? Anyone else had a go at this package?
-
Hi
It' a very nice project.
I'm trying to use HP's Bluetooth foldable keyboard.
I have modified Cwaig's IRK driver and the keyboard can work with SL-C750 now.
However, it does not work with SL-C3000 because Bluez does not support C3000.
I have not tried your ipk yet, sorry, but I'd like to request a support for USB devices because the SL-C3000 has a USB host function.
I want to use a Bluetooth USB adapter, which is cheaper than a Bluetooth CF card.
Thanks in advance.
-
I have installed the package on my unit, and here is the log
Hope it helps
bash-2.05$ su
# ipkg install bluez_zaurus_2.12_2.4.20_alpha_arm.ipk
Unpacking bluez...Done.
Configuring bluez...depmod: *** Unresolved symbols in /lib/modules/2.4.20/kernel/net/bluetooth/bnep/bnep.o
Starting Bluetooth... /lib/modules/2.4.20/kernel/net/bluetooth/bluez.o: kernel-module version mismatch
/lib/modules/2.4.20/kernel/net/bluetooth/bluez.o was compiled for kernel version 2.4.20-mh18
while this kernel is version 2.4.20.
/lib/modules/2.4.20/kernel/net/bluetooth/bluez.o: insmod /lib/modules/2.4.20/kernel/net/bluetooth/bluez.o
failed
/lib/modules/2.4.20/kernel/net/bluetooth/bluez.o: insmod rfcomm failed
/lib/modules/2.4.20/kernel/net/bluetooth/bluez.o: kernel-module version mismatch
/lib/modules/2.4.20/kernel/net/bluetooth/bluez.o was compiled for kernel version 2.4.20-mh18
while this kernel is version 2.4.20.
/lib/modules/2.4.20/kernel/net/bluetooth/bluez.o: insmod /lib/modules/2.4.20/kernel/net/bluetooth/bluez.o
failed
/lib/modules/2.4.20/kernel/net/bluetooth/bluez.o: insmod l2cap failed
Can't open RFCOMM control socket: Address family not supported by protocol
Done.
ioctl(): Device or resource busy
ioctl(): Device or resource busy
Done.
#
-
I got exactly the same result
# pwd
/home/root/modules/2.4.20/kernel/net/bluetooth
# ls
bluez.o bnep l2cap.o rfcomm sco.o
# depmod -a
depmod: *** Unresolved symbols in /lib/modules/2.4.20/kernel/net/bluetooth/bnep/bnep.o
# modprobe bnep
/lib/modules/2.4.20/kernel/net/bluetooth/bluez.o: kernel-module version mismatch
/lib/modules/2.4.20/kernel/net/bluetooth/bluez.o was compiled for kernel version 2.4.20-mh18
while this kernel is version 2.4.20.
/lib/modules/2.4.20/kernel/net/bluetooth/bluez.o: insmod /lib/modules/2.4.20/kernel/net/bluetooth/bluez.o failed
/lib/modules/2.4.20/kernel/net/bluetooth/bluez.o: insmod bnep failed
-
Ok thanks everyone. I'm gonna have to try with an unpatched kernel and hope the latest BlueZ utilities work with it. Won't take long...
-
So it's going to take a bit longer. The unpatched kernel seems to be missing the rfcomm stuff, which is pretty crucial to dial up.
This is where I wish I had a SL-3000 for testing....
-
No luck with those modules - but keep up the good work!
Indeed the kernel seems unpatched.
-
Bakkeo,
your mods to cwaig's IRK package sound great. Perchance have you posted your mods anywhere?
I want to trade my IR keyboard for a BT version.
Regards,
J.
-
Bombur
The ipk is here:
http://www.geocities.jp/bakkeo2004/irk-zau....1f_arm.ipk.bin (http://www.geocities.jp/bakkeo2004/irk-zaurus-j_0.11.1f_arm.ipk.bin)
This modified package supports some IR keyboards and HP's bluetooth foldable keyboard.
http://www.mobile-review.com/pda/review/hp...yboard-en.shtml (http://www.mobile-review.com/pda/review/hp-ipaq-bluetooth-keyboard-en.shtml)
HP's bluetooth foldable keyboard has Bluetooth serial port profile (SPP)(like cellular phones and GPS receivers),
so I have merely added a combo-box menu for the /dev/rfcomm port to the IRK package to communicate with the keyboard.
Be careful that the HID-profile type bluetooth keyboard, like Thinkoutside's product, doesn't work with this driver.
To use HP's keyboard, configure the "/etc/bluetooth/rfcomm.conf" file, and choose "HPfoldableBT" and "Bluetooth(rfcommX)"
menus at the comboboxes in IRK settings dialogue.
If you use this package
bluez-zaurus_2.3-2.4.18d_arm.ipk
set the PIN number to "0000" in "/etc/bluetooth/givepin" and "/etc/bluetooth/pin" files.
Press the pairing button of the keyboard first, and then click the "on" radio-button on the IRK controlbar.
The pairing process will start.
Sometimes deleting the "/etc/bluetooth/link_key" file may be needed, if pairing could not be made.
After the LED on the keyboard turns off, you can type a word without taking care of the direction nor level of the IR port.
-
Ok, here is alpha 2 of the ipk for the SL-3000 BlueZ. Please make sure the previous version, if you tried it, has been uninstalled cleanly before testing this. Thanks.
I have hopefully resolved the kernel version mismatch (well, hacked it ). I'm not sure why there were unrecognised symbols in the bnep module. The bnep module handles PAN connections, so that may still be broken, but rfcomm (which handles serial/dialup connections) may be working now so connecting to a phone might be possible with this package.
P.S. The Bluetooth mods to IRK are cool, but since it is not SL-3000 specific, it probably belongs in its own thread. Cwaig himself said he was going to have a look at this. Putting it in the Accessories forum will get it more exposure too.
Again, the ipk filename should be 'bluez-zaurus_2.12-2.4.20-alpha2_arm.ipk' but some of the dashes may get turned to underscores with this upload.
EDIT: Look further down this thread for alpha3 of this ipk.
-
woo , thx, i will try it soon,
Good Job!!
-
Thanks,
Big backlog of emails, voicemails and orders to clear through. But will try in the next few days...
-
Wel, I am able to connect to my Motorola V600 this time with alpha2
I follow the HOW TO steps
and ignored all the error and reboot
Here is the log from the installation:
Configuring bluez...depmod: /lib/modules/2.4.20/kernel/net/bluetooth/bnep/.bnep.o.flags is not an ELF file
depmod: /lib/modules/2.4.20/kernel/net/bluetooth/bnep/.core.o.flags is not an ELF file
depmod: /lib/modules/2.4.20/kernel/net/bluetooth/bnep/.crc32.o.flags is not an ELF file
depmod: /lib/modules/2.4.20/kernel/net/bluetooth/bnep/.depend is not an ELF file
depmod: /lib/modules/2.4.20/kernel/net/bluetooth/bnep/.netdev.o.flags is not an ELF file
depmod: /lib/modules/2.4.20/kernel/net/bluetooth/bnep/.sock.o.flags is not an ELF file
depmod: /lib/modules/2.4.20/kernel/net/bluetooth/rfcomm/.core.o.flags is not an ELF file
depmod: /lib/modules/2.4.20/kernel/net/bluetooth/rfcomm/.crc.o.flags is not an ELF file
depmod: /lib/modules/2.4.20/kernel/net/bluetooth/rfcomm/.depend is not an ELF file
depmod: /lib/modules/2.4.20/kernel/net/bluetooth/rfcomm/.rfcomm.o.flags is
not an ELF file
depmod: /lib/modules/2.4.20/kernel/net/bluetooth/rfcomm/.sock.o.flags is not an ELF file
depmod: /lib/modules/2.4.20/kernel/net/bluetooth/rfcomm/.tty.o.flags is not an ELF file
depmod: *** Unresolved symbols in /lib/modules/2.4.20/kernel/net/bluetooth/bnep/bnep.o
Starting Bluetooth... Done.
ioctl(): Device or resource busy
ioctl(): Device or resource busy
Done.
# /etc/rc.d/init.d/bluetooth restart
Shutting down Bluetooth... Done.
Starting Bluetooth... Note: /etc/modules.conf is more recent than /lib/modules/2.4.20/modules.dep
Note: /etc/modules.conf is more recent than /lib/modules/2.4.20/modules.depsyntax error line 15
Done.
This time hciconfig show my card info, and sdptool show my motorola phone
I could pair with it without any problem
But I still have problem with the internet access, but maybe just because the t-mobile APN configuration.
Hope this help
and thanks for your hard work
-
Oops. Didn't noticed I had copied those files into the package. They shouldn't affect anything though. That bnep module is still causing problems, but it looks like all the other modules loaded ok.
Yan, if you run the following command you will be able to see if it is connecting to your phone:
pppd call BT-GPRS -detach debug
where BT-GPRS is the name of the PPP peers script that should connect to your phone. If you see a line containing someting like "/dev/rfcomm1 <--> ppp0" in the output, then the Bluetooth connection to your phone is probably working fine.
Thanks for testing.
-
Yeah. Bluetooth works. That's really great, thanx a lot.
Some remarks:
Bluetooth network applet: The network applet doesn't work correctly. If e. g. opera or qtmail wants to initiate a new connection everything is fine. But if you try to use the applet from the taskbar, the bluetooth connection isn't shown and you cannot connect. I seems that something about the applet has changed. Ad-hoc-solution: Create an irda-connection as described here: http://www.zaurususergroup.com/modules.php...ename=Bluetooth (http://www.zaurususergroup.com/modules.php?op=modload&name=phpWiki&file=index&pagename=Bluetooth)
Suspend-resume: After a suspend-resume cycle, bluetooth will not work any more. The suspend-resume packages don't work. Ad-hoc-solution: Eject and reinsert the bluetooth card. I wrote the following script to do so:
#! /bin/sh
cardctl eject
cardctl insert
sleep 5
I linked the script into the Settings-tab and after a resume I can reset the bluetooth-card manually by starting the script and without physically ejecting and reinserting it.
-
tumnus,
Oh, sorry.... I will make a new thread.
Your new package works fine with my SL-C3000 + LinkEvolution Bluetooth CF card (LSE039).
It's very nice, thanks!
-
Neato. At least dialup is working then . Don't know what is going on with the PAN module. I'm away over Christmas and New Years so I don't think I'll be able to fix it until January. (I may get some time to work on the Bluetooth GUI though on my 5600)
I'm guessing the Network applet doesn't show up because the way a BT card is seen has changed with the latest BlueZ utilities and libraries. Maslovsky wrote those so I might speak with him about upgrading everything to the latest BlueZ stuff.
As for the suspend/resume stuff, I don't know why it isn't working. It doesn't work at all? Did you install the sudo package? Does the file /usr/local/bin/apm exist on the 3000? Sudo and the apm binary being in that directory are about the only dependencies of the suspend/resume stuff.
-
I'm guessing the Network applet doesn't show up because the way a BT card is seen has changed with the latest BlueZ utilities and libraries. Maslovsky wrote those so I might speak with him about upgrading everything to the latest BlueZ stuff.
Actualy bluetooth applets work fine with the latest bluez drivers, libs and utilities - I got them all on Cacko 1.22.
BTW, it's great to hear that we might finaly see bluez GUI completed
-
Did you have to change anything for the latest stuff?
-
Hi all , i have tried the alpha2 driver, it got nothing when i type hciconfig command, it seems my BT card is not supported. but i cannot found a uninstall item of bluez driver in add/remove option. anyone can teach me how to remove the driver completely for next version installation?
Thanks and Regards
-
It must not have installed properly if it does not show up in the Uninstall list.
Which BT card do you have?
-
i am using EagleTec ET-CFBTH-B
Thanks your help
-
Tumnus,
thank you so much for your work!
For the record, I have a 3k, Socket CF BT (Rev H.) and a Sony Ericsson T637.
I installed:
bluez-csr-serial
bluez-zaurus
qtopia-bluetoothnetworkapplet
I can now get on-line via a GPRS connection.
Best Regards,
J.
-
i have fail to install the driver, how can i remove the driver manaually?
-
You can probably try installing it again.
I have never heard of your card. What does the command 'cardctl ident' output on your zaurus when you have the card inserted?
-
You can probably try installing it again.
I have never heard of your card. What does the command 'cardctl ident' output on your zaurus when you have the card inserted?
it just show as belows:
Socket 0:
product info : "Compact Flash","Bluetooth Card","",""
manfid:0x022d,0x2000
function: 2 (serial)
-
Your card looks like it needs to be setup like other serial based Bluetooth cards. The hardest part is guessing the initialisation parameters.
In the file /etc/bluetooth/uart you need to add a new line for your card that looks something like this:
"Compact Flash","Bluetooth Card","","":/dev/ttyS3 bcsp 115200
The first part, before the colon ( must match the output of cardctl exactly. The second part is what is passed to hciattach to initialise your card. /dev/ttyS3 must always be there, but the other two parameters can be changed. The speed may be some other multiple. You should be able to change it and test any new settings just by ejecting and reinserting your card.
-
Thx, i will try again.. or buy a compatible BT
-
Can someone with a SL-3000 post the output from the following command using my alpha2 ipk found in this thread:
modprobe -v bnep
I think the only unresolved symbol should be sockfd_lookup. If it is, then I can fix it as I have done for the new BlueZ ipk for all other Zaurus models. Then I can make an alpha3 package that will also include some other improvements.
-
# modprobe -v bnep
/sbin/insmod /lib/modules/2.4.20/kernel/net/bluetooth/bnep/bnep.o
Using /lib/modules/2.4.20/kernel/net/bluetooth/bnep/bnep.o
Symbol version prefix ''
/lib/modules/2.4.20/kernel/net/bluetooth/bnep/bnep.o: unresolved symbol sockfd_lookup
/lib/modules/2.4.20/kernel/net/bluetooth/bnep/bnep.o: insmod /lib/modules/2.4.20/kernel/net/bluetooth/bnep/bnep.o failed
/lib/modules/2.4.20/kernel/net/bluetooth/bnep/bnep.o: insmod bnep failed
hope this help
-
That's what I was expecting, thanks.
-
I've created another ipk. The bnep module problems should be fixed now, so the PAN profile should be working.
I think I have also eliminated the need for the extra bluez-csr-serial ipk, so if you have a UART based card like the Socket Rev G/H, you can remove that ipk altogether.
I have switched to a different driver for the Ambicomm/Pretec BT2000E card, which uses a higher comms speed and can survive suspends, so people with BT2000E cards should not need the susp-resume-bluez ipk either.
For all other cards, I have improved the susp-resume-bluez ipk, so that all cards should come back automatically after a suspend/resume. That ipk can be found in the 2nd post of this thread:
https://www.oesf.org/forums/inde...?showtopic=9995 (https://www.oesf.org/forums/index.php?showtopic=9995)
EDIT: Look further down the post for a later ipk
-
tumnus thanks!
Everything work, no errors during installation.
I couldn't test the PAN profile, but all others work well on my Socket Rev H card.
I'm typing this in my car with bluetooth connection
-
Would anyone who has bluez_zaurus_2.12_2.4.20_alpha3_arm.ipk be able to post it somewhere until the ZUG site is sorted out?
I (and others) would greatly appreciate the favour.
Thanks in advance,
j.
-
offroadgeek was going to put all the attachements back, but I can repost them when I get home.
-
Thanks Tumnus!
j.
-
Hmmm, ok, I'm getting nothing but errors when trying to upload. Hang on...
-
I've put the alpha3 ipk back on my previous previous post above.
-
Hi Tumnus,
An update on the alpha3 package:
I have a 3000 with a Socket BT CF card rev H.
I tried the alpha 3 release but nothing worked.
I removed alpha 2 and the csr package. I then installed alpha 3 and the bluez suspend resume package. I made sure my rfcomm.conf file was configured as before when things were working with the alpha 2.
hciconfig found nothing when I inserted the BT CF card and of course the gprs dial up to my bluetooth phone did not work. I tried installing the csr package to see if that would work... but alas no joy. I tried three times to uninstall everything, reboot and reconfigure just to make sure. No success.
I re-installed the alpha 2, the csr package and left in the suspend resume package, configured my rfcomm.conf and I was off to the races. Everything worked.
hciconfig reported data about my CF card as expected and the gprs dial-up worked.
Did I miss something? I assumed the installation of alpha 3 would pretty much be the same affair as alpha 2.
J.
-
There's something wrong with the /etc/pcmcia/bluetooth script for serial based BT cards, but I can't debug it cos I haven't got a serial BT card. I'm trying to remove the hack that the bluez-csr-serial ipk is by putting all the serial initialisation into /etc/pcmcia/bluetooth.
-
Strange. I got it working most of the time with alpha3.
A few times when I restarted bluetooth, I got "BCSP initialization timed out". But I remove and insert again, everything work fine.
I have a 3000 with a Socket BT CF card rev H too and also removed alpha 2 and the csr package before I installed alpha3.
-
Strange. I got it working most of the time with alpha3.
A few times when I restarted bluetooth, I got "BCSP initialization timed out". But I remove and insert again, everything work fine.
I have a 3000 with a Socket BT CF card rev H too and also removed alpha 2 and the csr package before I installed alpha3.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=63572\"][{POST_SNAPBACK}][/a][/div]
Hi Yan,
What files did you touch when configuring? I only modified my /etc/bluetooth/rfcomm.conf file to setup my BT connections to my cell phone and BT-serial adapter. I did try re-insertion but no joy. I wonder what we each did differently.
J.
-
That is strange
Yan, I'm wondering if something didn't uninstall/install properly and left the old files. In /etc/pcmcia/serial, are the words Bluetooth or hciattach in there? Also in /etc/pcmcia/bluetooth.conf, after the line 'device "serial_cs"' do you have 'class "bluetooth"' or 'class "serial"'?
-
tumnus:
1) No Bluetooth or hciattach in /etc/pcmcia/serial
2) class "bluetooth" under device "serial_cs"
heh hope I'm not using old alpha2 files
-
No it sounds like you have only alpha3 ipks files. Strange that it works for you and not for others.
Yan, could you post the output of 'cardctl ident' just to make sure you have a serial based model? Thanks.
-
Here is the output:
bash-2.05# cardctl ident
Socket 0:
product info: "Socket", "CF+ Personal Network Card Rev 2.5"
manfid: 0x0104, 0x0096
function: 2 (serial)
Socket 1:
product info: "HITACHI", "microdrive"
manfid: 0x0319, 0x0000
function: 4 (fixed disk)
-
Thanks Yan. Yep, that's a serial based Socket card. Which is sort of good, but I'm still really puzzled as to why other people's installations aren't working
-
Thanks Yan. Yep, that's a serial based Socket card. Which is sort of good, but I'm still really puzzled as to why other people's installations aren't working
[div align=\"right\"][a href=\"index.php?act=findpost&pid=63668\"][{POST_SNAPBACK}][/a][/div]
Tumnus,
My card output (alpha2 with csr):
bash-2.05$ cardctl ident
Socket0:
product info: "Socket", "CF+ Personal Network Card Rev 2.5"
manfid: 0x0104, 0x0096
function: 2 (serial)
Socket 1:
product info: "HITACHI", "microdrive"
manfid: 0x0319, 0x0000
function: 4 (fixed disk)
After I have installed alpha 3, what files should I be checking?
/etc/pcmcia/serial
/etc/pcmcia/bluetooth
/etc/pcmcia/blootooth.conf
Maybe I can compare them against Yan's?
J.
-
Bombur, try checking for the things I mentioned in Post #54 when you have alpha3 installed.
-
Another success story for BlueZ on a C3000. I just got a usb Bluetooth adapter working. Here's the info from "System Info"
Vendor: National Semiconductor Corp
Product: RF Controller
Class: RF Controller
ID: 0400/0807
Driver: hci_usb
I can do a sdptool browse and see my computer and a bluetooth access point. That's all I know how to do right now with BlueZ, but I get the same results as with a Socket bluetooth CF card.
If anyone wants to know the exact model of bluetooth adapter I'm using I could only find it here (http://www.a2zsolutions.com/computer/bluetooth/bafo-bf-8010.htm). But if this thing works (I bought it because it was cheap - $18), I'm pretty sure others will too. It was in a drawer because the Windows software was so bad (no XP support ).
Now for the confusing part. I couldn't get my Ambicom CF card to work in the C3000. The Model# is BT-2000D-CF. Yep, not an E, nor a C, but a D. I'm guessing it's too new for the drivers to recognize it, but that's a guess. The manfid is: 0x022d, 0x2000 & the output from cardctl ident is:
Socket 0:
product info: "Compact Flash", "Bluetooth Card", "", ""
manfid: 0x022d, 0x2000
function: 2 (serial)
Thanks to tumnus for all the hard work so far.
Jason M.
-
Hi,
I am very keen to get my bluetooth usb dongle to work on the C3000.
I see from Jason's post above that he is able to get the hci_usb driver loaded.
I have installed the updated alpha3 ipk but this doesn't appear to have the hci_usb driver.
I was wondering which other package(s) are required (or config files that need modifying) for this driver or whether I will have to compile Bluez myself? I haven't used Linux for a while.
Thanks,
Steve
Vendor: Momitsu WIF-0402C Bluetooth Adapter
Product: RF Controller
Class: RF Controller
ID: 03ee/641f
Driver: none
-
Um, I never considered USB devices so I never included the hci_usb driver. I guess Jason must have compiled that himself. I suppose I could include it in the SL-3000 BlueZ ipk. In fact as long as the USB dongle uses a CSR chip they're a piece of cake to get working with BlueZ (would you believe most USB dongle manufacturers use a standard interface rather than re-inventing the wheel? *cough*Ambicom CF cards*cough*).
-
Thanks for the quick reply Tumnus.
The USB-Host function of the C3000 seems to be a winner!
I would appreciate if you could add in the HCI_USB module next compile.
Steve
-
Um, I never considered USB devices so I never included the hci_usb driver. I guess Jason must have compiled that himself. I suppose I could include it in the SL-3000 BlueZ ipk. In fact as long as the USB dongle uses a CSR chip they're a piece of cake to get working with BlueZ (would you believe most USB dongle manufacturers use a standard interface rather than re-inventing the wheel? *cough*Ambicom CF cards*cough*).
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=64681\")
Actually, I thought for sure that it was part of the BlueZ package you posted. Since it obviously isn't, I think that I got it from [a href=\"http://tetsu.homelinux.org/zaurus/kernel/v17f/kernel-modules_v17f-C3000_arm.ipk]here[/url]. The site is in Japanese and has custom kernels for all the zaurii. Not speaking Japanese, I don't have any idea how to install them or what they do.
-
I have attached the alpha4 ipk for the SL-3000 to this post.
Changes:- Added the hci_usb driver for USB bluetooth dongles
- Corrected a syntax error spotted by pakman
Remember to rename the download and change some of those underscores (_) to bluez-zaurus_2.12-2.4.20-alpha4_arm.ipk
Please test this latest package, especially if you have a serial card. Enjoy
-
Thanks Colin
HCI_USB works perfectly!
Keep up the good work
Steve
-
Hello, Tumnus and others.
To be short, I was able to establish a PAN connection between my SL-C3000 and my laptop using different revisions of Socket cards (rev F/dtl1_cs and H/hci_uart)
I've been trying the bluez stack on SL-C3000 with various Socket cards, and here's a couple of things I can share with you. Unfortunately, I don' seem to be able to get back to a clean image and restart from scratch, so, as I tried many things before I got things working, the steps may not be in the right order.
1. First I backed up my fresh SL-C3000 and I tried the bluez stack for the SL-C860 (2.4.18) on the SL-C3000 and tried forcing the modules to load. I stopped when the 3000 froze when loading rfcomm I think.
That's where I came to this forum, and found out about the SL-C3000 port.
2. So I uninstalled 2.4.18 and installed the 2.4.20-alpha3 patch. I noticed that some files were not restored to their original state, for instance: modules.dep, modules.conf, and also some libbluetooth files. And my bluetooth card didn't seem to be recognized correctly: a "hcitool dev" would not be able to display any device information.
3. Even after restoring my original backup, bluez files were still there. So I tried t remove as much as possible manually, and restored them again.
4. I reinstalled alpha-3 package. "hcitool dev" returned nothing. tried restarting bluez stack (/etc/rc.d/init/d/bluetooth restart)... , ejecting and inserting the card... nothing. Then I rebooted and finally "hcitool dev" displayed the MAC address of my card (a rev F) socket card.
5. So I tried with a rev H socket card. "hcitool dev" > nothing. Installe csr-serial patch - nothing. But got something after rebooting the PDA.
6. Finally I installed the pannetworkapplet and was able to connect to my laptop.
7. Oh yes, and at some point, when I installed the bluez-zaurus package from the "Add/Remove" GUI program, the system would hang. So I ended up installing it from the console. And so it seems that I will have to uninstall it from the console as well...
Although I'm not sure this is clear, I still hope it can help.
And in summary, it seems that:
- Uninstalling the stack does not uninstall everything.
- The backup/restore is not reliable
- Sometimes I have to reboot to get my cards recognized (and I feel like I shouldn't have to).
- Sometimes bnep driver is loaded automatically, sometimes it's not (and when it's not, of course no networking). Is the pan-network applet responsible for loading it ?
I'm new to the Zaurus and that's my first post here, don't be too hard on me please.
Thanks for your efforts Tumnus!
-
Hello sornett and welcome to the forums.
I think most of your troubles stemmed from trying to force the kernel modules to load that were not for the same version of kernel as is on your SL-3000.
You shouldn't need the bluez-csr-serial package installed and it shouldn't be using the file from that anyway. It sounds like it should be working for serial based cards now, like the rev H socket card, as long as you're using the alpha4 package and not the alpha3.
-
Tumnus,
alpha4 worked for me on the 3000.
- I removed the csr package and the alpha2 package.
- Installed alpha4 package.
- rebooted.
- re-entered my /etc/bluetooth/rfcomm.conf settings
- initial insertion of the Socket rev H card did not register with hcitool dev
- tried /etc/rc.d/init.d/bluetooth start didn't work either
- re-inserted the card. hcitool dev finally found the card.
I tested against my GPRS capable phone and sure enough the Internet was my oyster.
Thank you for your awesome and very appreciated work!
J.
-
Woohoo! Thanks for testing that Bombur.
How well does it survive suspend/resume cycles with the new susp-resume-bluez package (v0.9.2) (https://www.oesf.org/forums/index.php?showtopic=9995&view=findpost&p=61521)?
-
Woohoo! Thanks for testing that Bombur.
How well does it survive suspend/resume cycles with the new susp-resume-bluez package (v0.9.2) (https://www.oesf.org/forums/index.php?showtopic=9995&view=findpost&p=61521)?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=65304\"][{POST_SNAPBACK}][/a][/div]
Hi Tumnus,
I don't think the suspend-resume works. I set my suspend timout to 4 minutes and allowed the system to go into screen saver and then tried to reconnect. I also closed the screen which automatically puts the system into suspend. Upon resume, my card was not recognized nor did it come up again when I tried to manually manipulate.
In the end after much testing, it looks like /etc/rc.d/init.d/bluetooth start must be done manually to get the card to be recognized and in some instances, a card re-insertion is also necessary. Is /etc/rc.d/init.d/bluetooth start supposed to be called when the card is inserted or during a resume? Is there some funkiness with these Socket cards?
I have a Socket Communications BT card Rev H. I have the bluez-susp-resume_arm.ipk version 0.92.
Best Regards,
J.
-
Ejecting the card and reinserting it should be all that is needed for this card with the latest BlueZ ipk. '/etc/rc.d/init.d/bluetooth start' should only be called once when the system boots up, which it is.
-
hi tumnus.
i tried your alpha4 bluez drivers with a bt0100m card and got some problems.
after i do hciattach, i can use hciconfig and sdptool as i expect, but after a while it stops working an dmesg reports
bcsp_pkt_cull: Peer acked invalid packet
bcsp_handle_le_pkt: Found a LE sync pkt, card has reset
bcsp_pkt_cull: Peer acked invalid packet
bcsp_handle_le_pkt: Found a LE sync pkt, card has reset
bcsp_pkt_cull: Peer acked invalid packet
bcsp_handle_le_pkt: Found a LE sync pkt, card has reset
bcsp_pkt_cull: Peer acked invalid packet
....
and the tx an rx counter in hciconfig go up, even after switching my mobile off.
i ve been trying to compile the bluez modules myself, but it seems the bluetooth support in the slc3000-kernel i downloaded does not support bcsp uart cards.
is this a problem with bcsp-support in linux or is it related to the slc3000?
or just configuration?
-
hciattach should be executed automatically. I don't know what is wrong with your card.
To compile the kernel modules you have to patch the kernel source: http://www.holtmann.org/linux/kernel/ (http://www.holtmann.org/linux/kernel/)
-
Finally , i bought another CF BT card (AnyCom) and it works great. Thanks Tummus!!
Just a little problem with suspend/resume issue even using updated ver.
-
Did you install the susp-resume architechture (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) packages too?
-
Guys, did someone experienced problems pairing Nokia 6230 with new Tumnus' drivers? I have tried both Socket G and Ambicom cards. Both refused to pair with this phone and at the same time normally functioned with Ericsson T610i. Prior to C3000 I used 6230 with C760 under Cacko 1.21 and everything worked fine
-
Do you have an existing pairing on your Nokia 6230? You might just need to delete that as it pairs with the MAC address of your Bluetooth card, but the pair key gets stored on your Zaurus and Phone memory.
To debug the issue with your Nokia 6230, you'll have to turn on syslog and look at the messages in /var/log/messages when you try to pair.
To turn on syslog, as root, edit /etc/syslog.conf and uncomment the line that contains *.info (remove the # at the start of the line). Then run '/etc/rc.d/init.d/syslog restart' . This will (re)start syslog and begin logging all the Bluetooth messages to /var/log/messages . Remember to comment that line out again afterwards and restart syslog again as /var/log/messages can get big fairly quickly.
-
Thanx Tumnus.
I have deleted previous pairing and debuged my pppd process.
My syslog shows the following:
pppd 2.4.0 started by root,Feb 17 22:13:54 localhost pppd[10617]: Failed to open /dev/rfcomm0 Feb 17 22:13:54 localhost pppd[10617]: Exit.
Do you have any clue?
-
There was nothing before that, about a key and showing MAC addresses?
-
Did you install the susp-resume architechture (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) packages too?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=67263\"][{POST_SNAPBACK}][/a][/div]
i got it, thanks..
haha.. i can pair my sharp GZ15/GZ100 M.phone but cannot use its gprs..
it seems a problem of the m.phone. it works great with Nokia 6230..
poor me.... may need get another BT m.phone...
-
Hello tumnus, here is some more feedback...
Ejecting the card and reinserting it should be all that is needed for this card with the latest BlueZ ipk. '/etc/rc.d/init.d/bluetooth start' should only be called once when the system boots up, which it is.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=65511\"][{POST_SNAPBACK}][/a][/div]
Hi!
I tried different Socket bluetooth cards on both SL-C3000 and SL-C860 after installing latest packages:
SL-C3000:
sudo 0.1
susp-resume 0.9-3.1
bluez-zaurus 2.12-2.4.20-alpha4
susp-resume-bluez 0.9.2
qtopia-pannetworkapplet 1.0.1
SL-C860:
sudo 0.1
susp-resume 0.9-3.1
bluez-zaurus 2.13-2.4.18-alpha3
susp-resume-bluez 0.9.2
qtopia-pannetworkapplet 1.0.1
On the SL-C3000:
* bootup: rev H card is recognized automatically, and the bluetooth applet is launched automatically.
* eject/insert: After ejecting the card and reinserting it, it looks that things don't all restart.
"cardctl ident" returns the card information, but "hcitool dev" does not return anything. I had to restart bluetooth and things went back into place.
* susp/resume: similar behavior, had to restart bluetooth
On the SL-C860:
* bootup: rev G card is recognized but the bluetooth applet is not launched.
* eject/insert: seems ok (tried hcitool dev/inq/scan)
* suspend/resume: cardctl ident displays the card info. hcitool dev does not display MAC address. after ejecting/reinserting the card things went back into place
here are the messages I get on SL-C3000 after eject/insert:
----> ejecting the card:
#tail -f /var/log/messages
cardmgr[79]: executing: './bluetooth check ttyS3'
cardmgr[79]: shutting down socket 0
cardmgr[79]: executing: './bluetooth stop ttyS3'
hcid[377]: HCI dev 0 down
hcid[377]: Stoping security manager 0
hcid[377]: HCI dev 0 unregistered
kernel: ttyS03 unloaded
/sbin/hotplug: no runnable /etc/hotplug/bluetooth.agent is installed
kernel: pxa_pcmcia_init(0)
----> reinserting the card:
#tail -f /var/log/messages
cardmgr[79]: initializing socket 0
cardmgr[79]: socket 0: Socket bluetooth CF Card Rev G+
cardmgr[79]: executing: './bluetooth start ttyS3'
kernel: ttyS03 at port 0xf60003f8 (irq=135) is a 16C950/954
and stops here... I guess I should have seen more than that...
-
Tumnus,
I currently have a brand spanking new SL-C3000 with virtually nothing installed except the following:
sudo 0.1
susp-resume 0.9-3.1
bluez-zaurus 2.12-2.4.20-alpha4
susp-resume-bluez 0.9.2
qtopia-pannetworkapplet 1.0.1
I have a Socket rev. F bluetooth card. Everything installed without a problem and I'm able to pair and dial-out using a Motorola V710 phone. The problem is, my C3000 crashes after browsing with Netfront for a few pages - same behavior with Opera 7.30. It never crashes while browsing using wifi. Interestingly enough, my C700 exhibited the same behavior with this bluetooth card.
Any ideas?
If the solution is to buy a new bluetooth card, which do you recommend?
-
What do you mean by 'crashes'. Does it lockup? Does Qtopia restart?
I've got the Socket Rev F card and it seems to be the most reliable of the lot.
-
What do you mean by 'crashes'. Does it lockup? Does Qtopia restart?
I've got the Socket Rev F card and it seems to be the most reliable of the lot.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=68386\"][{POST_SNAPBACK}][/a][/div]
It completely locks up. I need to remove the battery to restart. When I first had my C700, it seemed much more stable. It became unstable after many new apps were installed. I assumed an app. was causing the problem and that it would go away on a clean C3000. I was wrong.
-
It completely locks up. I need to remove the battery to restart. When I first had my C700, it seemed much more stable. It became unstable after many new apps were installed. I assumed an app. was causing the problem and that it would go away on a clean C3000. I was wrong.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=68417\"][{POST_SNAPBACK}][/a][/div]
Hmmm. I have never experienced this and I have not heard anyone else report this with the Socket Rev F card. Perhaps you have a faulty card?
-
It completely locks up. I need to remove the battery to restart. When I first had my C700, it seemed much more stable. It became unstable after many new apps were installed. I assumed an app. was causing the problem and that it would go away on a clean C3000. I was wrong.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=68417\"][{POST_SNAPBACK}][/a][/div]
Hmmm. I have never experienced this and I have not heard anyone else report this with the Socket Rev F card. Perhaps you have a faulty card?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=68424\"][{POST_SNAPBACK}][/a][/div]
The rev. F card was faulty - I replaced it with a Socket rev. H. Everthing is fully functional without any crashes. I have the same suspend/resume issues as Sornette, however:
On the SL-C3000:
* bootup: rev H card is recognized automatically, and the bluetooth applet is launched automatically.
* eject/insert: After ejecting the card and reinserting it, it looks that things don't all restart.
"cardctl ident" returns the card information, but "hcitool dev" does not return anything. I had to restart bluetooth and things went back into place.
* susp/resume: similar behavior, had to restart bluetooth
Any fixes in sight for your favorite brand bluetooth card?
-
I have uploaded version 0.9.3 of the susp-resume-bluez package (https://www.oesf.org/forums/index.php?showtopic=9995&view=findpost&p=61521) which should resume serial based cards such as the Socket Rev G properly.
-
I have uploaded version 0.9.3 of the susp-resume-bluez package (https://www.oesf.org/forums/index.php?showtopic=9995&view=findpost&p=61521) which should resume serial based cards such as the Socket Rev G properly.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=68865\"][{POST_SNAPBACK}][/a][/div]
It's better. The globe now appears on suspend/resume. An hciconfig -a, however, shows nothing and it still requires a bluetooth restart to recover.
Any ideas?
-
Have a look at /etc/apm.d/bluetooth . That is the script that does the business. I was told that the Socket Rev G card can be brought back simply by running 'cardctl resume'
-
Have a look at /etc/apm.d/bluetooth . That is the script that does the business. I was told that the Socket Rev G card can be brought back simply by running 'cardctl resume'
[div align=\"right\"][a href=\"index.php?act=findpost&pid=68877\"][{POST_SNAPBACK}][/a][/div]
I modified the bluetooth script with the following line at the end of the "resume" section:
/etc/rc.d/init.d/bluetooth restart
The card now works after a resume - sometimes brute force is the way to go.
Thanks for your help!
-
Have a look at /etc/apm.d/bluetooth . That is the script that does the business. I was told that the Socket Rev G card can be brought back simply by running 'cardctl resume'
[div align=\"right\"][a href=\"index.php?act=findpost&pid=68877\"][{POST_SNAPBACK}][/a][/div]
I modified the bluetooth script with the following line at the end of the "resume" section:
/etc/rc.d/init.d/bluetooth restart
The card now works after a resume - sometimes brute force is the way to go.
Thanks for your help!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=68906\"][{POST_SNAPBACK}][/a][/div]
Oi! That's done it for me as well.
J.
-
None of the overclocking kernels appear to work with my Socket rev. H. Upon resume, my Zaurus reboots. The problem disappears when I switch back to the stock kernel.
Are any overclocking kernels available that do not have this problem?
-
It may be worth mentioning the suspend-resume architecture IPK renames /usr/local/bin/apm to /usr/local/bin/apm.rom then creates it's own as a script.
If you are having problems with your Z not suspending then this is the issue. When you hit the power button the command 'apm -s' is run as the Zaurus user which doesn't have rights to suspend the box. To fix you must edit /usr/local/bin/apm and prefix the commands with 'sudo' i.e.
#!/bin/bash
# Replacement apm script that eventually
# calls the real apm with all arguments
# passed to it.
# Before that, however, it calls a script
# that will run all suspend commands in
# /etc/apm.d/suspend.d and then kicks off
# a resume script that carries on running
# when we resume and runs all commands in
# /etc/apm.d/resume.d
if [ "$1" = "--suspend" -o "$1" = "-s" ]; then
sudo /usr/local/bin/susp.sh
sudo /usr/local/bin/resume &
fi
sudo /usr/local/bin/apm.rom $@
the IPK that is being mentioned on this thread doesn't have this.
-
Actually I think you must have got the pre SL-5500 3.1 ROM version of the ipk from ELSI where everything ran as root. If you go to the home page of the susp-resume ipk, you'll find the version that has had the sudo lines in it since the 3.10 ROM came out.
I didn't realise ELSI had only grabbed the old version of the ipk. I have added a link to the current ipk. Sorry about that.
-
Would it be possible for someone to make an overall summary of setup instructions for this topic? Eg. SL-C3000 + Socket BT card + Nokia 6630 (or other Symbian series 60 model) phone?
I have tried all of the tricks and tips on this and other sites, but I still cannot get it to work. Previously, I had an SL-C760 + Nokia 7600 that paired and connected successfully with the Socket BT card, but I am utterly confused with the new Zaurus.
Current ZUG Howto document ( under SL-Cxxx) on this topic is outdated....
Thanks in advance.
-
Would it be possible for someone to make an overall summary of setup instructions for this topic? Eg. SL-C3000 + Socket BT card + Nokia 6630 (or other Symbian series 60 model) phone?
------------------------------------
Here is a first try at the proper sequence of actions. But I failed after trying this, so additional steps are probably required.... Please feel free to add on you own knowledge. Please!!!
----
1) download--> bluez_zaurus_2.12_2.4.20_alpha4_arm.ipk ( 211.87k )
[https://www.oesf.org/forums/index.php?act=Attach&type=post&id=279]
- Remember to rename the download and change some of those underscores (_) to bluez-zaurus_2.12-2.4.20-alpha4_arm.ipk
2) alpha4 (plus additional packages) installation:
- Removed the csr package and the alpha2 package.
- Installed alpha4 package.
-Install additional packages (not part of alpha4):
-Install bluez libs??
-Install bluez utils??
-Install qtopia-bluetoothnetworkapplet (*Java installation required first)
-reboot.
3) Settings in Zaurus SL-C3000
-eject and reinsert BT card
#cardctl ident (check that card is recognized by zaurus)
#hciconfig (get BT mac address of zaurus side--> xx:xx:xx:xx:xx:xx)
??? not necessary --> #sdptool browse (scan to find mac id)
# hcitool scan (scan for BT mac address of phone side--> xx:xx:xx:xx:xx:xx)
-Service name : dial-up network ==> channel 1.
- re-entered settings in /etc/bluetooth/rfcomm.conf
- initial insertion of the Socket rev H card did not register with hcitool dev
- tried /etc/rc.d/init.d/bluetooth start --> didn't work either
- re-inserted the card. hcitool dev finally found the card.
vi /home/zaurus/Applications/Network/modules/IRDA.conf
find IRDA code --> IRDAxxxxxxxxxxx
vi /etc/ppp/peers/IRDAxxxxxxxxxxx
-add '/dev/rfcomm0' at top line
4) Phone side settings (Vodafone in Japan, using Nokia 6630 phone with BT)
-Connect your phone via USB or BT and put setting to the phone:
Access point: vodafone (Tools->Settings->Connection->
Packet data->Access point)
5) Pairing between Zaurus and phone (use common pin numbers such as 1234 and then set for auto-pairing...)
6) Zaurus dial-up network settings (for Vodafone network in Japan)
User name: ai@vodafone
Pass word:vodafone
Dial: *99#
-
I am using a Anycom BTCF card in a SL-C3000 with the following packages installed:
sudo 0.1
susp-resume 0.9-3.1
bluez-zaurus 2.12-2.4.20-alpha4
susp-resume-bluez 0.9.2
qtopia-pannetworkapplet 1.0.1
The Anycom card is recognized by cardctl ident, but the card address is all zeroes when queried with hciconfig hci0. Dmesg shows thw following driver error messages when the card is ejected and then inserted:
bluecard_cs: Unknown HCI packet with type 0x28 received.
bluecard_cs: Unknown HCI packet with type 0x20 received.
bluecard_cs: Unknown HCI packet with type 0xfc received.
Any ideas for resolving the problem appeciated.
-
Would that be the Anycom CF-300? If it is, it requires a kernel patch backported from kernel 2.6, which means replacing your Sharp kernel with a custom one.
The packages I have put together only support the stock Sharp kernel.
-
Tumnus,
Thanks for the quick response. My card is the Anycom CF-300, so I'd appeciate you recommendations as to a compatible CF format BT card. I'd like to avoid the custom kernel if possible.
-
Here's a list of cards and their compatibility with the Zaurus drivers:
https://www.oesf.org/index.php?title=Bluetooth_Card_Support (https://www.oesf.org/index.php?title=Bluetooth_Card_Support)
-
Can anyone please give corrections/comments/advice about why the steps below have not worked for me? Or should this configuration work?
SL-C3000 + Socket BT card (Version F) + Nokia 702NK/6630 phone?
----------------------------------------------------------------------------------------------------------------
1) download--> bluez_zaurus_2.12_2.4.20_alpha4_arm.ipk ( 211.87k )
[https://www.oesf.org/forums/index.php?act=Attach&type=post&id=279]
- Remember to rename the download and change some of those underscores (_) to bluez-zaurus_2.12-2.4.20-alpha4_arm.ipk
2) alpha4 (plus additional packages) installation:
- Removed the csr package and the alpha2 package.
- Installed alpha4 package.
-Install additional packages (not part of alpha4):
-Install bluez libs??
-Install bluez utils??
-Install qtopia-bluetoothnetworkapplet (*Java installation required first)
-reboot.
3) Settings in Zaurus SL-C3000
-eject and reinsert BT card
#cardctl ident (check that card is recognized by zaurus)
#hciconfig (get BT mac address of zaurus side--> xx:xx:xx:xx:xx:xx)
??? not necessary --> #sdptool browse (scan to find mac id)
# hcitool scan (scan for BT mac address of phone side--> xx:xx:xx:xx:xx:xx)
-Service name : dial-up network ==> channel 1.
- re-entered settings in /etc/bluetooth/rfcomm.conf
- initial insertion of the Socket rev H card did not register with hcitool dev
- tried /etc/rc.d/init.d/bluetooth start --> didn't work either
- re-inserted the card. hcitool dev finally found the card.
vi /home/zaurus/Applications/Network/modules/IRDA.conf
find IRDA code --> IRDAxxxxxxxxxxx
vi /etc/ppp/peers/IRDAxxxxxxxxxxx
-add '/dev/rfcomm0' at top line
4) Phone side settings (Vodafone in Japan, using Nokia 6630 phone with BT)
-Connect your phone via USB or BT and put setting to the phone:
Access point: vodafone (Tools->Settings->Connection->
Packet data->Access point)
5) Pairing between Zaurus and phone (use common pin numbers such as 1234 and then set for auto-pairing...)
6) Zaurus dial-up network settings (for Vodafone network in Japan)
User name: ai@vodafone
Pass word:vodafone
Dial: *99#
[div align=\"right\"][a href=\"index.php?act=findpost&pid=73446\"][{POST_SNAPBACK}][/a][/div]
[/quote]
-
Well which bit hasn't worked?
Has your phone paired?
Did the GPRS connection fail? If it did fail, please post the contents of /tmp/qpe-ppp-log .
You don't need any extra packages to get basic Bluetooth working. The qtopia--bluetoothnetworkapplet package doesn't need Java.
You do need to to a 'sdptool browse' to find the actual channel of the DUN profile of your phone as this can differ from model to model.
-
Hi,
I have two SL-C3000 with Socket Rev H bt card.
I established "manually" a PAN connection:
C3000#1: pand --listen --role GN
C3000#2: pand –connect MACaddrC3000#1
ifconfig bnep0 192.168.0.101
C3000#1: ifconfig bnep0 192.168.0.100
The problem is a communication performance / freezing after a while:
C3000#1: ping -s 1024 192.168.0.101
1032 bytes from 192.168.0.101: icmp_seq=0 ttl=64 time=4464.8 ms
1032 bytes from 192.168.0.101: icmp_seq=1 ttl=64 time=4285.7 ms
1032 bytes from 192.168.0.101: icmp_seq=2 ttl=64 time=5131.8 ms
1032 bytes from 192.168.0.101: icmp_seq=3 ttl=64 time=6461.1 ms
ping: sendto: Network is unreachable
However C3000#2 still show the connection:
C3000#2: pand -l
bnep0 MACaddrC3000#1
When I tried to have more input with hcidump, syslog, I notice that ping response time decreased, meaning that with a takeCPUBusy.sh script I was able to reduce the response time below 100ms:
C3000#2: cat files of a directory in loop
C3000#1: ping -s 1024 192.168.0.101
PING 192.168.0.101 (192.168.0.101): 1024 data bytes
1032 bytes from 192.168.0.101: icmp_seq=0 ttl=64 time=129.2 ms
1032 bytes from 192.168.0.101: icmp_seq=1 ttl=64 time=75.5 ms
1032 bytes from 192.168.0.101: icmp_seq=2 ttl=64 time=74.5 ms
1032 bytes from 192.168.0.101: icmp_seq=3 ttl=64 time=67.7 ms
1032 bytes from 192.168.0.101: icmp_seq=4 ttl=64 time=65.2 ms
1032 bytes from 192.168.0.101: icmp_seq=5 ttl=64 time=70.2 ms
...
I tried to reduce the speed rate from 230400 to 115200 on /etc/bluetooth/uart, without success (i.e. hciattach failed with BCSP timout error).
what else can I change try?
Any explanation, tip or any kind of help is welcome!
Following is dump of log that may be interessting:
# hciconfig -a
hci0: Type: UART
BD Address: 00:02:C7:42:B0:22 ACL MTU: 340:4 SCO MTU: 64:10
UP RUNNING PSCAN ISCAN
RX bytes:5828 acl:29 sco:0 events:55 errors:0
TX bytes:10399 acl:44 sco:0 commands:15 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'zaurus'
Class: 0x120114
Service Classes: Networking
Device Class: Computer, Palm
HCI Ver: 1.1 (0x1) HCI Rev: 0x1bb LMP Ver: 1.1 (0x1) LMP Subver: 0x1bb
Manufacturer: Cambridge Silicon Radio (10)
syslog:
Feb 2 12:45:31 localhost kernel: bcsp_recv: Error in BCSP hdr checksum
Feb 2 12:45:32 localhost kernel: bcsp_recv: Short BCSP packet
Feb 2 12:45:32 localhost kernel: bcsp_recv: Error in BCSP hdr checksum
Feb 2 12:45:32 localhost kernel: bcsp_recv: Short BCSP packet
Feb 2 12:45:33 localhost kernel: bcsp_recv: Short BCSP packet
Feb 2 12:45:33 localhost kernel: bcsp_recv: Error in BCSP hdr checksum
Feb 2 12:45:34 localhost last message repeated 7 times
Feb 2 12:45:34 localhost kernel: bcsp_recv: Out-of-order packet arrived, got 7 expected 6
Feb 2 12:45:34 localhost kernel: bcsp_recv: Out-of-order packet arrived, got 0 expected 6
Feb 2 12:45:34 localhost kernel: bcsp_recv: Out-of-order packet arrived, got 1 expected 6
Feb 2 12:45:35 localhost kernel: bcsp_recv: Error in BCSP hdr checksum
Feb 2 12:45:36 localhost last message repeated 7 times
Feb 2 12:45:36 localhost kernel: bcsp_recv: Out-of-order packet arrived, got 7 expected 6
Feb 2 12:45:36 localhost kernel: bcsp_recv: Out-of-order packet arrived, got 0 expected 6
Feb 2 12:45:36 localhost kernel: bcsp_recv: Out-of-order packet arrived, got 1 expected 6
Feb 2 12:45:37 localhost kernel: bcsp_recv: Error in BCSP hdr checksum
Feb 2 12:45:37 localhost last message repeated 2 times
-
syslog:
Feb 2 12:45:31 localhost kernel: bcsp_recv: Error in BCSP hdr checksum
Feb 2 12:45:32 localhost kernel: bcsp_recv: Short BCSP packet
Feb 2 12:45:32 localhost kernel: bcsp_recv: Error in BCSP hdr checksum
Feb 2 12:45:32 localhost kernel: bcsp_recv: Short BCSP packet
Feb 2 12:45:33 localhost kernel: bcsp_recv: Short BCSP packet
Feb 2 12:45:33 localhost kernel: bcsp_recv: Error in BCSP hdr checksum
Feb 2 12:45:34 localhost last message repeated 7 times
Feb 2 12:45:34 localhost kernel: bcsp_recv: Out-of-order packet arrived, got 7 expected 6
Feb 2 12:45:34 localhost kernel: bcsp_recv: Out-of-order packet arrived, got 0 expected 6
Feb 2 12:45:34 localhost kernel: bcsp_recv: Out-of-order packet arrived, got 1 expected 6
Feb 2 12:45:35 localhost kernel: bcsp_recv: Error in BCSP hdr checksum
Feb 2 12:45:36 localhost last message repeated 7 times
Feb 2 12:45:36 localhost kernel: bcsp_recv: Out-of-order packet arrived, got 7 expected 6
Feb 2 12:45:36 localhost kernel: bcsp_recv: Out-of-order packet arrived, got 0 expected 6
Feb 2 12:45:36 localhost kernel: bcsp_recv: Out-of-order packet arrived, got 1 expected 6
Feb 2 12:45:37 localhost kernel: bcsp_recv: Error in BCSP hdr checksum
Feb 2 12:45:37 localhost last message repeated 2 times
[div align=\"right\"][a href=\"index.php?act=findpost&pid=79424\"][{POST_SNAPBACK}][/a][/div]
i had a aimilar problem with the sharp rom. i had to do a
echo 1 > /proc/lock_fcs
which solved the problem for me.
anyway after i updated to cacko 3kb1 my card works without problems.
-
FINALLY I'm on the right drivers/thread. Many apologies for my blatant ignorance!!
BUT it won't connect. Here's the latest:
- Wipe everything done so far, except sudo. (grin)
- Install susp-resume
- Install alpha4 bluez for 2.4.20.
- Install susp-resume-bluez
- Set up everything as given in the BT HowTo that Tumnus so conveniently has a link to in his signature. (cheshire grin) sdptool shows the phone's services, mac, etc. Network applet appears as expected.
- BUT it won't pair. Issuing "dund -c <mac>", then retrying, says the device is not available, so I rebooted the Z, even though it just says to turn it off.
- Still nothing. This keeps asking me for a password when I try to connect, even though I never put one in the profile. It doesn't seem to matter what I put here, it still fails. That shouldn't be necessary to pair, should it? Just to connect to Sprint once the link is active?
- Here's my configuration:
# hciconfig -a
hci0: Type: PCCARD
BD Address: ACL MTU: 672:8 SCO MTU: 64:0
UP RUNNING PSCAN ISCAN
RX bytes:961 acl:34 sco:0 events:51 errors:1
TX bytes:828 acl:32 sco:0 commands:15 errors:0
Features: 0xff 0xfb 0x01 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'hiroshi'
Class: 0x120114
Service Classes: Networking
Device Class: Computer, Palm
HCI Ver: 1.1 (0x1) HCI Rev: 0x8103 LMP Ver: 1.1 (0x1) LMP Subver: 0x8b40
Manufacturer: Ericsson Technology Licensing (0)
# rfcomm -a
rfcomm0: channel 4 closed
# rfcomm connect /dev/ttyS3
Can't connect RFCOMM socket: Connection refused
# rfcomm connect /dev/ttyS3 4
Can't create RFCOMM TTY: Address already in use
# /etc/rc.d/init.d/bluetooth restart
Shutting down Bluetooth... Done.
Starting Bluetooth... Done.
# rfcomm connect /dev/ttyS3 4
Can't connect RFCOMM socket: Resource temporarily unavailable
# cat uart
"AmbiCom BT2000E", "Bluetooth PC/CF Card", "", "":/dev/ttyS3 bt2000c flow
"CF Card", "GENERIC", "", "":/dev/ttyS3 bcsp
"Compact Flash", "Bluetooth Card", "", "":/dev/ttyS3 bcsp
# cat rfcomm.conf
#
# RFCOMM configuration file.
#
# $Id: rfcomm.conf,v 1.1 2002/10/07 05:58:18 maxk Exp $
#
rfcomm0 {
# Automatically bind the device at startup
bind yes;
# Bluetooth address of the device
device ;
# RFCOMM channel for the connection
channel 4;
# Description of the connection
comment "Diver Link";
}
# cat /etc/ppp/peers/IRD*
/dev/rfcomm0
noipdefault
115200
connect '/usr/sbin/chat -s -v -t 60 ABORT "NO CARRIER" ABORT "NO DIALTONE" ABORT
"BUSY" "" "ATZ" OK "ATQ0V1S100=1" OK "ATDTLG PM325" CONNECT "\\d\\d"'
crtscts
lock
modem
usepeerdns
defaultroute
mtu 576
mru 576
connect-delay 1000
remotename IRDA1116159478
- After rebooting, hcitool no longer functions. I used to be able to "cc" a connection, and "name" to at least get the BT Name of the phone. Now it's down, even after restarting bluetooth. (pout) Ah. Ejected the CF and reseated. Now we're back in business:
# hcitool dev
Devices:
hci0
# hcitool cc --role m
# hcitool name
Diver
# hcitool inq
Inquiring ...
clock offset: 0x5c2a class: 0x400204- After doing the above, rfcomm shows /dev/ttyS3 is already in use, implying some sort of connecting, even though the Network Applet won't pair. It just sits there at "Connecting" for a minute or so, then pops to "Network Offline".
- If I tell the phone to do "Searching and pairing" instead of "Waiting for pairing", and I do this when the Network Applet says "Connecting", I see "hiroshi" (Z's hostname) in the list of devices. If I select that, and enter the PIN from hiroshi, the phone says "pairing". Now as far as I know this isn't DUNS, so it fails to establish a network link, BUT it does show that, from the phone's standpoint, hiroshi is present and accounted for. I *assume* (eeeek!) that I need to use "Waiting for pairing" to get DUNS to work, but I haven't seen any real information to support that assumption, actually.
- So hiroshi can obviously talk to the phone just fine, and the phone can talk to hiroshi just fine, but it won't establish a faux IR link. I'm sure I'm missing something patently simple, since I'm such a Noob. If someone could point out that simple thing I'd really appreciate it! (cheshire grin)
-
You need to pair your Zaurus and Phone for any such connection. Read the bit about pins in the BlueZ Introduction (https://www.oesf.org/index.php?title=Bluetooth#BlueZ_Introduction) and it should be clear what pin you need to enter in which file.
-
- Thanks, Tumnus!
- Actually, I did all this. I have 'pin' and 'givepin' setup as described. When I do "Wait for pairing" I enter the PIN I put in each of those files. If I don't, it fails instantly, so that part must be working to some degree. After this post, I did in fact get it to work, sort of. This post (https://www.oesf.org/forums/index.php?showtopic=12628) indicates the results.
- Since then, I've experienced very, very inconsistent results from BlueZ, and I started poking around with it. I just put a bunch of echos in the ../init.d/bluetooth startup script, and took out all of the output redirections to /dev/null so I could see exactly what it's doing. I also whipped up a script to run bits of BT init/shutdown individually, based on the contents of the bluetooth initialization script. Here's the result:# $HOME/bt restart
Shutting down Bluetooth...
- Releasing rfcomm binding...
- Killing hcid...
- Killing sdpd...
- Killing hciattach...
- Unloading modules...
bluez: Device or resource busy
Done.
Starting Bluetooth...
- Loading modules...
- Creating devices...
- Loading hcid...
- Loading sdpd...
- Finding uart settings for: "AmbiCom,Inc", "BT2000E", "Bluetooth PC/CF Card"
- Starting uart with: /dev/ttyS3 bt2000c flow
Can't get port settings: Input/output error
Can't initialize device: Input/output error
- Binding rfcomm...
Done.
#- It always says bluez is busy, and in fact I don't even know why it's trying to unload that. It unloads when the BT card is ejected, and loads when it's put back in, so the startup script doesn't need to bother with it. (shrug) Minor, at best.
- Using this, I initially discovered that my /etc/bluetooth/uart file didn't have the right entry for an AmbiCom BT2000E (it says "AmbiCom" as shipped instead of "AmbiCom,Inc" in the first entry), so it wasn't finding it. I fixed the line so it does find it now. Despite this, it did work from time to time. Go figure! (grin)
- The "Starting uart with..." line appears just before the hciattach call to dump the parms it's passing to that. So I tried:# $HOME/bt attach /dev/ttyS2 bt2000c flow
Can't get port settings: Input/output error
Can't initialize device: Input/output error
#which just runs hciattach with the given parameters, mimicing what the bluetooth initialization script should be doing.
- I also stopped BT and manually entered the commands listed in the startup script. No surprise, I get the *same* result! (snicker)
- Are these input/output messages this normal?
- I found a post that indicates restarting pcmcia on a SL6000 fixed things. Not so here ... doing that ejects the CF ... when I pop and reseat, then restart bluetooth, I get exactly the same results.
- That same post also indicates loading the hci_uart module helped. When I stop bluetooth and manually run through the startup procedure, tossing in a "modprobe hci_uart", it still does the same thing when I get to hciattach.
- I haven't located how it "pairs". I'd like to poke around with doing that manually as well. Is hciattach supposed to do that?
- DESPITE the errors on load, running hcitools gives this:# hcitool cc --role m
# hcitool name
Diver
# hcitool info
Requesting information ...
BD Address:
Device Name: Diver
LMP Version: 1.2 (0x2) LMP Subversion: 0xdb0
Manufacturer: Texas Instruments Inc. (13)
Features: 0xff 0xff 0x2d 0xf8 0x1b 0x18 0x00 0x80
<3-slot packets> <5-slot packets>
#- Seems pretty wierd to me, that it apparently errors on restart, and hcitool works, but I don't claim to know what's happening here. I do know it won't pair, and it won't connect unless my phone is in "full discover", and even then it's flakier than psoriasis. (shrug) Just information, mind you. Just information.
- Here's some files, just 'cause I can:# cat /etc/bluetooth/rfcomm.conf
#
# RFCOMM configuration file.
#
# $Id: rfcomm.conf,v 1.1 2002/10/07 05:58:18 maxk Exp $
#
rfcomm0 {
# Automatically bind the device at startup
bind yes;
# Bluetooth address of the device
device ;
# RFCOMM channel for the connection
channel 4;
# Description of the connection
comment "Diver modem";
}
# cat /etc/bluetooth/uart
"AmbiCom,Inc", "BT2000E", "Bluetooth PC/CF Card", "", "":/dev/ttyS3 bt2000c flow
"CF Card", "GENERIC", "", "":/dev/ttyS3 bcsp
"Compact Flash", "Bluetooth Card", "", "":/dev/ttyS3 bcsp
# cat /etc/bluetooth/pin
# cat /etc/bluetooth/givepin
##############givepin#########
#!/bin/sh
echo "PIN:"
################
#- /etc/bluetooth/hcid.conf has not been touched from the default, so far.
- Could you advise? Thanks for your time!
-
FOUND IT.
- I found a post that mentioned /etc/apm.d/bluetooth, so I looked in there, and found out what it does on resume from suspend. I do those steps:rfcomm bind all
cardctl eject
cardctl insert
hciconfig hci0 up*POOF* Connects like a charm, stays connected, works fine. Googe maps loads *really* slow! (foolish giggle) So I updated my bt script to do this for me ... if I stick in the card and it won't work, I drop to the command line, run "sudo bt fix", and try to connect again. Works every time!
- So, what I'd like to know, is how do I just run these commands (i figured the bind isn't really needed, but it doesn't seem to hurt) each time I try to connect with the Network Applet? Can I just stick them into the /etc/ppp/peers/IRDA<blah> file? That doesn't seem like it's a script file to me, but it may be possible to run some script from there, and that would certainly do the trick. Since it actually seems to be necessary *each* time I stick the BT card in, I may as well just make it do that anyway.
- BTW, it seems it was actually "paired", but hiroshi just doesn't appear in the list of paired connections on the phone. (shrug) During this latest little stint, I didn't make sure the phone was set to "Show always" (it keeps reverting to 'hide' all the time, which is *good*), and even though it was set to "Hide", it linked up and surfed without any troubles. Didn't expect it to do a "stealth pairing". (chuckle)
- Thanks for your time...
-
i had a aimilar problem with the sharp rom. i had to do a
echo 1 > /proc/lock_fcs
which solved the problem for me.
anyway after i updated to cacko 3kb1 my card works without problems.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=79477\"][{POST_SNAPBACK}][/a][/div]
Could you please elaborate on what /proc/lock_fcs precisely does?
-albertr
-
Hi-
I recently traded up to a C3k from a C860. I used the Bluez pkg from this thread to connect the C3k with my Moto V635 (Cingular). I have successfully paired the two but everytime I try to BT connect from the C3k, I see the BT session starting on the cellphone, but it dies after a minute or so.
How can I debug what's going on?
Thanks in advance!
-
Just an update....I just removed all the init strings in the setup and it connects to Cingular GPRS now! Thanks, Tumnus for the package!
-
Yes, I am sorry that I forgot to mention what bit hasn't worked...
I am able to pair the devices. But I am not able to connect or send files between them. The network application (with bluetooth applet installed) has been set, but when I try to dial it, the phone does not respond at all. The zaurus just continues to say "initializing modem" but it never gets beyond that point.
I checked in /tmp/ and there was a file called "bluetooth-pppd-log". Inside the file was only the following line:
"Failed to open /dev/rfcomm1: Host is down".
----
Well which bit hasn't worked?
Has your phone paired?
Did the GPRS connection fail? If it did fail, please post the contents of /tmp/qpe-ppp-log .
You don't need any extra packages to get basic Bluetooth working. The qtopia--bluetoothnetworkapplet package doesn't need Java.
You do need to to a 'sdptool browse' to find the actual channel of the DUN profile of your phone as this can differ from model to model.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=78862\"][{POST_SNAPBACK}][/a][/div]
-
Hey,
I've been trying to get my bluetooth keyboard working.
The hidp module exists, but not the hidd server.
Can anyone please post a compiled version of the hidd server?
Thanks.
-
I checked in /tmp/ and there was a file called "bluetooth-pppd-log". Inside the file was only the following line:
"Failed to open /dev/rfcomm1: Host is down".
[div align=\"right\"][a href=\"index.php?act=findpost&pid=81742\"][{POST_SNAPBACK}][/a][/div]
The Bluetooth link is not being established. You need to enable syslogging to /var/log/messages to see what is going on.
-
Has anyone gotten the Bluetake card (DLink clone, I think) working with the SL-C3000?
I installed the alpha 4 ipk. The card is now somewhat recognized when inserted (light turns on, cf icon displays). However:
hcitool dev
displays nothing.
cardctl ident displays:
Socket 0:
product info: "Bluetooth BT0100M", "",""
function: 2 (serial)
Any help is greatly appreciated.
-
who is hosting bluez-zaurus_2.12_2.4.20_alpha4_arm.ipk?
Never mind I found it in a link that wasnt even a link.
update!
here is that link for that one file. the rest should be around..somewhere
{https://www.oesf.org/forums/index.php?act=Attach&type=post&id=279}
just copy that along the address bar without parenthesis.
the rest are here
http://www.zaurususergroup.org/modules.php...ename=Bluetooth (http://www.zaurususergroup.org/modules.php?op=modload&name=phpWiki&file=index&pagename=Bluetooth)
for easier use, i used su zeditor for the files and konsole for executing commands (sl5500 version programs). or held click the icon and changed it to execute with root privalage.
Hey tumnus! thanks. I don't know how to pay you for this man but you did a good job here.
-
I didn't see this elsewhere, so I thought I'd post it in case it might help someone else.
Zaurus C3100
Socket Bluetooth CF Rev. H
Using susp_resume_bluez_0.9.3_arm.ipk (the current version?), my card would not resume properly after suspending. By looking at /etc/rc.d/init.d/bluetooth, I found that the trick was to call hciattach (in the init script, it is part of the 'start_uarts()' function).
My modified version of /etc/apm.d/bluetooth contains the following:
resume)
if ... # this part is unchanged
cardctl resume
/usr/sbin/hciattach /dev/ttyS3 bcsp 230400
rfcomm bind all
hciconfig hci0 up
else
...
Note that the hciattach line listed above is specific to my card, and was found by looking at the file /etc/bluetooth/uart. You could look up the same info for your own card, or make the resume portion generic by pasting the code from start_uarts().
Also note that the rfcomm and hciconfig lines do not seem to be necessary - at least, I am still able to resume and reconnect PAN without those lines. I left them in just to be safe.
- ashikase
- anpachi, gifu, japan
-
Thanks for your post ashikase! That fixed my problem as well. I also have a Zaurus C3100 and am using the Socket Bluetooth CF Rev. H and was really getting sick and tired of having to stop and restart bluetooth all the time by hand. With your changes, I can suspend and resume and everything just works.
I wonder if perhaps a check for Socket Bluetooth CF Cards should be added to the bluetooth suspend/resume script to do the hciattach if it's needed? I wonder if it's only needed for certain cards or if it causes problems for anyone using a different card? Hmm...
-
i do have this problem with my card. I just simply eject the card with the icon and reinsert it after reboot. If i just pull the card out without ejecting, it totally locks up my pda.
im gona try this code.
-
Thanks for your post ashikase! That fixed my problem as well. I also have a Zaurus C3100 and am using the Socket Bluetooth CF Rev. H and was really getting sick and tired of having to stop and restart bluetooth all the time by hand. With your changes, I can suspend and resume and everything just works.Â
[div align=\"right\"][a href=\"index.php?act=findpost&pid=91673\"][{POST_SNAPBACK}][/a][/div]
I am also using a 3100 with a rev H socket card. Could one of you post your entire bluetooth file (or at least the entire "resume" section)? I can't seem to get this to work, and I think may have the syntax wrong.
By the way, when I run
/usr/sbin/hciattach /dev/ttS3 bcsp 230400
in the terminal, I get
BCSP initialization timed out
And a cardctl eject give me a "ioctl(): Device or resource busy" message.
Is that normal?
-
rather than double post i'm hoping someone can help me with my SL-C3100 and GPRS
heres the topic i started,
https://www.oesf.org/forums/index.php?showtopic=15613 (https://www.oesf.org/forums/index.php?showtopic=15613)
I'm hoping someone from this thread can help me :S