OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Sharp ROMs => Topic started by: Anonymous on March 06, 2004, 06:52:01 pm
-
Sashz, please upgrade the bluez drivers for the Socket CF \"2.5G\".
I\'m finally posting over GPRS-Bluetooth with the damned card. BTW it is very small and fits perfectly in the CF slot. Also needs 40 ma in average.
1st problem
The card rev. 2.5 G is not recognized correctly
I needed to comment out the 3 lines referring to the card in /etc/pcmcia/bluetooth.conf, eject the card, reinsert it and run /etc/pcmcia/bluetooth restart.
At first I tried without installing the bluez_csr_serial_01 package but apparently it is needed too!
After these steps \"spdmstool browse\" and \"hciconfig\" are giving valid output.
2nd problem
Finally, to connect to my Nokia6310i i needed to edit /etc/bluetooth/rfcomm.conf everytime I reinsert the card... IMhO rfcomm.conf should not get overwritten by ppp dialer!
Now I\'m going to reboot the SL-C860 just to see if my rfcomm.conf get overwritten...and I loose my phone again
-
OK, after reboot my rfcomm.conf is unchanged ... I was doing something wrong before... probably if you start the ppp dialer with bluethoot stopped and it doesn\'t find any card then it fills \"device\" and \"channel\" values with <void>.
Anyway, i forgot to say I\'m using the last Cacko - Qtopia Rom dated 05 March 2004, with \"dynamic\" bluetooth loading.
Previously I got the Socket CF+ 2.5 G card working on 860\'s stock kernel + TKC 2.51 ROM with the bluez-zaurus_2.3-2.4.18d_arm.ipk. Please note the _18d_ version.
-
Now if you could calm down and explain what exactly is needed to make this card work, we\'ll be glad to add support for it to the ROM
What does bluez_csr_serial_01 package package does? Other then that package - looks like the only problem was extra lines in /etc/pcmcia/bluetooth.conf, correct?
-
blurz_csr_serial is a hack that replaces /etc/pcmcia/serial to setup the CSR based uart BT cards and runs hciattach and loads hci_uart at the right point.
I tried putting the setserial stuff in /etc/pcmcia/bluetooth and then run hciattach and load hci_uart there instead. That\'s in version E of the BlueZ packages but doesn\'t work for some reason and I don\'t have a CSR card to debug it with.
-
Tumnus is right. The Bluez \"E\" are not working either with the stock kernel nor with the preemptive one from toshiro.
Also, I never got the card functional after suspend/resume...
The issue is pointed out here in the ZUG in the Bluetooth How-To and the suggestion is to install the following scripts:
susp-resume_0.9-3.1.ipk
sudo-0.1.ipk
susp-resume-bluez_0.9.1_arm.ipk
Unfortunately the packages didn\'t solve the problem for me.
For the moment the only solution is to restart pcmcia or bluetooth by hand from the terminal or simply to eject and reinsert the card (for normal users ;-)
Finally, GREAT JOB, thank you all developers !
-
It works for me when after I added \"killall hciattach\" and \"cardctl eject\" to the suspend part of /etc/apm.d/bluetooth. My Zaurus now takes longer to suspend and wake up, but the card works fine most of the time.
Gunnar
-
Strange, a \'cardctl eject\' should do a \'killall hciattach\' automatically anyway, and susp-resume-bluez_0.9.1_arm.ipk ensures that the card is always ejected and reinserted on every resume.
-
Hi,
Yes, this is basically the problem that I was having over on devnet at http://www.zaurususergroup.com/board/index9231.html?showtopic=7490 ://http://www.zaurususergroup.com/boar...showtopic=7490 ://http://www.zaurususergroup.com/boar...showtopic=7490 ://http://www.zaurususergroup.com/boar...showtopic=7490 ://http://www.zaurususergroup.com/boar...showtopic=7490 (http://www.zaurususergroup.com/board/index9231.html?showtopic=7490%20).
I don\'t have the time to do much detailed investigation at the moment, but I did get as far as convincing myself that /etc/pcmcia/bluetooth is not run when the card is defined in /etc/pcmcia/bluetooth.conf. I put lines like:
echo in bluetooth > /var/log/bt.txt
in /etc/pcmcia/bluetooth, but I never found any evidence that /etc/pcmcia/bluetooth was invoked at all.
I\'ve fallen back on using this card without a /etc/pcmcia/bluetooth.conf file, and starting and stopping bluetooth manually.
Regards,
P.
Update: I am using the \"E\" revision of the BlueZ drivers, not the \"D\" revision.
-
Strange, a \'cardctl eject\' should do a \'killall hciattach\' automatically anyway, and susp-resume-bluez_0.9.1_arm.ipk ensures that the card is always ejected and reinserted on every resume.
I experimented a bit more and they are both needed. If I remove one or both, then the card is down after a suspend (and can\'t get up), but the network icon stays in the taskbar. If I then try to eject the card manually I am told that a program is using the card.
With \"killall hciattach\" and \"cardctl eject\" the network icon disappears after a suspend (it comes back if I start Opera or the network settings applet), but bluetooth still works.
Is cardctl really supposed to know which driver program to kill?
Gunnar
-
Strange, a \'cardctl eject\' should do a \'killall hciattach\' automatically anyway, and susp-resume-bluez_0.9.1_arm.ipk ensures that the card is always ejected and reinserted on every resume.
I forgot to say that I am using the D version of the driver, the E version didn\'t work for me.
Gunnar
-
I get the same problem too with my Socket CF 2.5 card. I\'m not sure what revision it is, though... can\'t find any model number on the card or in the docs that came with it.
So, are the E drivers not working for everyone? I\'m also running Cacko Qt ROM 1.20 and `sdptool browse` prompt returns \"Inqury failed\" and `hciconfig` does nothing.
I\'ll try messing with the config files tomorrow. I wish there was a GUI in the network app for discovering and pair BT devices... perhaps I\'ll have to write one.
Also, I noticed the Bluetooth How-To is either not accurate or the Cacko ROM is different than the ROM that one was written to. I went to setup a Dialup - IrDA connection, but that wasn\'t listed in the drop down. I ended up selecting the Dialup - Bluetooth connection... and I did not install the Bluetooth applet whose link was present in the How-To.
Thanks
Curt
-
I went to setup a Dialup - IrDA connection, but that wasn\'t listed in the drop down
To setup IRDA connection you need to select Dialup-PPP and then select IRDA-PPP.
-
The program locking the card seems to be related to bluetooth. if i do a /etc/rc.d/init.d/bluetooth stop i can then eject the card
-
Can anyone tell me where the bluez_csr_serial_01 package is available. I could not find anything on the Bluez site nor did a Google search yield any response.
I did uncomment the 3 lines associated with the Socket CF Bluetooth Rev 2.5 card, ejected and reinserted the card, and then restarted the /etc/pcmcia/bluetooth command. That gave me the following error:
Starting Bluetooth... Note: /etc/modules.conf is more recent than /lib/modules/2.4.18-rmk7-pxa3-embedix/modules.dep
Note: /etc/modules.conf is more recent than /lib/modules/2.4.18-rmk7-pxa3-embedix/modules.dep
Can\'t get port settings: input/output error
Can\'t initialize device: input/output error
parse error line 3
Done.
-
I also noticed that Socket Communications has a link to killfilez.de for the Socket card. It\'s for the Affix Bluetooth protocol stack. Strange thing is, when you go to that page it specifically says it no longer works with new Socket cards.
Curt
-
ccrandal,
you are almost there... now:
pull out the card,
#su
#cardctl resume
insert the card
/etc/pcmcia/bluetooth restart
P.S. Ignore the messages about modules.conf...
but you could also have an error on line 3 of your /etc/bluetooth/rfcomm.conf, check device and channel
-
if you are using the Cacko Rom the stack is restarted with
/etc/pcmcia/bluetooth restart
but if you are on the Sharp ROM + Bluez rev. D it is
/etc/rc.d/init.d/bluetooth restart
-
I think that\'s where the error is coming from. the device and channel are both \"(null)\". Is something supposed to be populating these fields?
Other than that, I\'m following the directions exactly. `sdptool browse` and `hciconfig` aren\'t showing anything useful.
Do I really need that bluez_csr_serial_01 package? I still have been unable to locate it on the web.
Thanks
Curt
-
Oh, and now my Zaurus will not power down w/o ripping out the battery. Lovely!
I think it\'s time to give this ROM another flash and if that doesn\'t do it I\'ll move on to another ROM.
Curt
-
ccrandal,
please give it a last try: erase the user-rom and reboot with the clean QT 1.2.
Then you only need to comment out the in/famous 3 lines and install bluez_csr_serial_01. Nothing more.
If you install the suspend/resume fixes your Z will seldom power down.The packages need some more work.
-
Can you tell me where the bluez_csr_serial_01 is?
What I meant by power down is that when I hit the off button, everything freezes. I think a new install will fix that... unless the suspend/resume ipk is the culprit.
I\'d really like to try a X11 ROM, but I really like Hancom Office. Much nicer than my DataViz Documents To Go on my Clie.
Thanks
Curt
-
Ah Ha! I finally stumbled across the bluez_csr_serial_01.ipk on sourceforge. I\'ll have to try the reflash tonight since I forgot the power cable... but at least I\'m starting to put all the pieces together on this. Thank you very much for the help.
Curt
-
csr_serial here:
ZUG ] how-to ] other ] bluetooth
then install the two qtopia-dial up and qtopia-pan applets to have it easier...
-
OK, I\'m dumb. I guess I need new glasses or something. I\'ve been to that page a dozen times, even printed it off, and never saw those links. Thanks again.
Curt
-
If you install the suspend/resume fixes your Z will seldom power down.The packages need some more work.
The suspend/resume ipks work fine. If they don\'t then you\'ve probably forgot to install something like sudo or the ROM you are using has gone even further away from the Sharp ROM.
-
tumnus,
no way to suspend/resume NORMALLY.
The Cacko QT 1.20 ROM has a preinstalled & customized bluetooth stack but the installation layout is different. See \"/etc/pcmcia/bluetooth\" vs. \"/etc/rc.d/init.d/bluetooth\".
Please note following points:
1-sudo is already installed (another build though, smaller)
2-suspend_resume_0.9.3.1 is preinstalled
3-susp-resume-bluez is installed BUT the script /etc/apm.d/bluetooth is different:
Cacko-QT 1.2:
case \"$1\" in
suspend)
if [ \"`/usr/sbin/hciconfig`\" != \"\" ]; then
hcitool dc `hcitool con | awk \'/ACL/ {print $3}\'`
hciconfig hci0 down
fi
;;
From susp-resume-bluez:
case \"$1\" in
suspend)
if [ \"`/usr/sbin/hciconfig`\" != \"\" ]; then
hcitool dc `hcitool con | grep ACL | sed \'s/^.*([0-9A-F]{2}(:[0-9A-F]{2}){5}).*$/1/\'`
hciconfig hci0 down
fi
;;
4- rfcomm.conf is empty at the beginning. That\'s for the pairing problems.
Byez
Ant
-
Huh? The two /etc/apm.d/bluetooth scripts do exactly the same thing. I simply removed the dependence on awk from my ipk because the Sharp ROM doesn\'t come with awk.
rfcomm.conf isn\'t empty in the latest BlueZ ipks.
In any case I don\'t see why you cannot suspend \'normally\'. If the Cacko ROM comes with the suspend/resume scripts preinstalled then that\'s nothing to do with the suspend/resume ipks. They work fine with the Sharp ROM and also tkcROM which comes with them preinstalled too.
-
hi tumnus,
I\'m talking about Cacko QT 1.20 distro.
]Huh? The two /etc/apm.d/bluetooth scripts do exactly the same thing. I ]simply removed the dependence on awk from
So it means Cacko\'s ROM has this \"newer\" version of the script.
I don\'t know what for a mixed bluetooth-stack is installed. It\'s newer than Bluez _D but older then _E because /etc/pcmcia/bluetooth.conf contains the 3 \"offending\" lines for the Socket Rev. 2.5.
BTW /etc/bluetooth/uart mentions the Socket card.
-
Cacko QT 1.20 has awk preinstalled, so both suspend/resume scripts will work fine.
The rfcomm.conf file is populated automaticaly when you configure a dialup connection using Network Applet. This file is not needed initialy, the bluetooth stack will initialise even wihout it.
The only difference between the two stacks seems to be the handling of Socket 2.5 cards. I wish I had one to test before releasing the ROM...
-
OK, I\'m still stuck. Here\'s what I\'ve done so far:
1.) Reloaded the Cacko Qt 1.20 ROM
2.) Installed bluez_csr_serial_01.ipk, qtopia-bluetoothnetworkapplet.ipk, qtopia-pannetworkapplet.ipk
3.) Opened Qkonsole and su\'d to root
4.) Edited /etc/pcmcia/bluetooth.conf to comment out the 3 offending lines related to the Socket CF rev2.5 card
5.) Ejected the Socket CF card
6.) Executed `cardctl resume`
7.) Reinserted the Socket CF card
8.) Executed `/etc/pcmcia/bluetooth restart`
I now get the errors:
Can\'t get port settings: Input/output error
Can\'t initialize device: Input/output error
I checked /etc/bluetooth/rfcomm.conf and it is empty (no channel, no device). When I insert the card, though, the card applet correctly identifies the card, though.
I did not install the susp-resume, sudo, and susp-resume-bluez packages as the last time I did that, I could not turn my Z off. I\'d rather try getting bluetooth working before introducing another potential problem.
Thanks,
Curt
-
Also forgot to mention I did set up a dial-up connection in the network panel per the Bluetooth How-To instructions. /etc/bluetooth/rfcomm.conf is still empty, though.
-
now you should type
#sdptool browse
and note the device # (like 00:11:22:33:44:55) and channel # of your phone (usually Dial-Up is channel 1).
then write these in rfcomm.conf like this:
rfcomm0 {
bind yes;
device 00:11:22:33:44:55; ==] your device #
channel 1;
comment \"test connection\";
}
-
sdptool browse is giving \"Inquiry failed...\" and hciconfig returns without writing anything to stdout.
I\'ll try hunting down the device # and editing the rfcomm.conf file.
Thanks
Curt
-
]sdptool browse is giving \"Inquiry failed...\" and hciconfig returns without writing anything
]to stdout.
magic trick to reset the things after suspend:
#su
#cardctl resume
#/etc/pcmcia/bluetooth restart
if cardctl resume gives errors you have network up. Simply pull out the card, reinsert it and retype te a.m. commands.
-
I run those commands each time and it still does not work. I\'ll try one more ROM flash and start from scratch and if that doesn\'t work, I\'m done.
Right now, no matter what I do I still get the:
Can\'t get port settings: Input/output error
Can\'t initialize device: Input/output error
everytime I restart bluetooth.
Thanks
Curt
-
you must give the MAC address an the channel or you receive this:
Can\'t get port settings: Input/output error
Can\'t initialize device: Input/output error
if \"sdptool browse\" and \"hciconfig\" are working your setup is ok.
Restart the phone and start bluetooth on it!
-
I just got my Ambicom card to work after giving it up two weeks ago. Hope this might help:
-when you type \"sdptool browse\", do \"sdptool browse |more\" instead becasue the output is more than one page long. The MAC address is on the first line so I missed it. But I was able to see the MAC address of my mobile (Siemens S56) throught the phoen itself so I never thought twice. That\'s why I didn\'t know my phoen has TWO channel numbers: channel 1 for \"Serial\" and Channel 3 for \"voice gateway\". For the longest time, I have channel 3 in rfcomm.conf file. Instead, it should be channel 1.
-In the network dial-up applet, change the flow control from 1 sec to something longer (I set it at 35 sec now). I don\'t knwo if this actually matters but it looked as if helped when I set up the Irda dail-up for the same phone.
Good Luck and thanks to Tumnus and everyone that helped out.
Frank W
-
Can\'t find the MAC... dug around /proc looking for it but came up with nothing. Since sdptool is not displaying anything but an error, I\'m not sure how else to get that info. I think I\'ll give the Affix drivers a try and hope they don\'t collide with the bluez drivers already on the ROM.
Thanks,
Curt
-
Curt,
Since you are trying to find the MAC address of your phone, can\'t you find out that through your phone? For the Siemens S56 I have, I went to Bluetooth menu, click on \"My BT name\". It will display both the name and the MAC address.
Frank W
-
I thought it would be looking for the MAC of the Bluetooth card since I\'m not necessarily setting up a connection to a phone as of yet. I just want the bluetooth manager to recognize the card.
Thanks
Curt
-
By the way, susp-resume-0.9-3.1 seems to have been the culprit preventing me from turning my Z off after its installation. This is also true after a complete reinstall of the Cacko Qt 1.20 ROM.
Curt
-
OK, this is messed up. I installed susp-resume-0.9-3.1. After that, hitting the On/Off button causes the Z to freeze for many minutes. I need to yank to battery out for 5sec to get it to reboot.
After installing this package, I also noticed that the behavior of the \"/\" key changes in Qkonsole. Before install, it works as it should by printing a comma when it is pressed of a \"/\" if shift is pressed with it. After install, it\'s the exact opposite.
I then uninstalled susp-resume-0.9-3.1. The Qkonsole behavior is the same, however, the On/Off button just does nothing. So, while it may not freeze, I still need to yank the battery out to kill it.
The ONLY good thing to come of this is that `sdptool browse` and `hciconfig` now return meaningful data. This is really messed up. If I had more time and more experience with these pieces of software, I\'d be more than willing to help fix this... I just hope the next version of either the rom, the suspend packages, bluez drivers, whatever fix this.
I now need to reflash my ROM for the 5th time and try this all over again... this time staying away from susp-resume completely (maybe just using susp-resume-bluez). If it doesn\'t work, I\'ll try the Affix drivers. If that fails, I try another ROM. If that fails, there\'ll be a Z SL-C750 up for sale soon!
Thanks all
Curt
-
Before putting your Z up for sale, try another bluetooth card. While new Socket cards are perfectly fine, they are serial cards and require running hciattach. Again, nothing wrong with that, but it might be a little bit more complex than you can manage. Some other bluetooth cards use dedicate drivers and alittle easier to setup...
-albertr
-
Any recommendations? I really like this Socket card since it doesn\'t stick out.
Thanks,
Curt
-
The Socket CF Bluetooth Rev 2.5 does work fine with the included BlueZ hci_uart driver, but the Cacko ROM seems to have a different implementation of the Bluetooth scripts and a few other things.
This is probably why the bluez-csr-serial and susp-resume ipks do not work with the Cacko ROM. I think maslovsk needs to take a look at the script I changed in the bluez-csr-serial ipk (Which is reference in my Bluetooth howto BTW) to see how it can be done with the Cacko ROM.
I like the Socket card too, but I have the previous revision which is completely different internally and works fine with a different driver.
-
Wanna trade cards?
Would using Affix help? Sounds like it might have a better UI as well.
-
You can always get an Ambicom BT2000E card (that uses a different driver) from Amazon.com for around $53 or so. Or maybe even less if you shop around. The recent version of bt2000e_cs driver should be able to survive suspend/resume without need of additional steps, or at least I hope so. However, the old driver in tumnus\' ipk does require apm scripts to reset the card after resume.
If you really wanna trade, I have an old Socket card (revision \"F\" that is 1.1 - compliant and doesn\'t stick out too). It works fine, but requires a reset after resume with BlueZ. I believe it survives suspend just fine with Affix (or at least it has with old Affix 1.2.6).
As far as GUI goes, Affix has a Connector Qtopia application that helps to browse and establish rfcomm connection to remote device (kick off pppd, etc), but unfortunately afaik development sorta stopped and no new versions were produced for a while. You probably don\'t want to stick with software that is no longer actively supported and updated...
-albertr
-
You don\'t need to install the applets - they are already included in the 1.20 ROM. Just go to the Network Setup application and create a connection to your cell phone (using dialup applet) or PC with bluetooth (using PAN applet). You don\'t have to edit any conf files - frcomm.conf is populated when you create a dialup connection uusing the applet.
-
Ya, after messing around I did realize that those applets were already there. I thought the applets I installed had the ability to scan for bluetooth devices and list all those that were discovered.
Actually, just running the applet did not create the appropriate entry in the rfcomm.conf file. Only after installing sudo, susp-resume, and susp-resume-bluez did it work... of course, as I stated earlier, the susp-resume messed up my ability to power down.
Hopefully, since I\'m pretending to be sick today, I\'ll have time to reflash the ROM and start fresh again. If I can get the Socket CF rev2.5 to work, I\'ll post my procedure in case anyone else could benefit. Otherwise, I\'ll have to hunt for another card.
Thanks,
Curt
-
Actually, just running the applet did not create the appropriate entry in the rfcomm.conf file.
This is strange. Did you actualy created a new connection to the phone?
Did it fnid your phone when you clicked Search button?
-
Well, when I was finally able to get info from sdptool, it did display my phone\'s MAC. So, somehow it did find it. However, I did not see any option to search when creating a bluetooth-dialup connection in the applet. I did see something in the bluetooth-pan applet, but the search button never found anything and would tell me to search manually.
I did open the terminal and did a `dund --search 30`... that was the only set of switches and args that caused my phone to respond (the bluetooth icon briefly showed a connection. I need to do more research on how to properly use the dund command as there\'s no man page available (no man util installed right now I believe).
Thanks,
Curt
-
OK, before I bricked my Z, I did locate the BT DUN Search widget in the Bluetooth Dialup Applet, but when hitting the search button it quickly returned saying it could not locate any devices with a DUN profile.
Seems like I need susp-resume and susp-resume-bluez installed to get this to work, however, under this ROM it seems to mess up my ability to turn the Z on and off (and has now bricked the device... I\'m letting it sit for a few hours w/o a battery or AC to see if that clears up that problem).
I\'ll play some more if I can get the Z running again, but it\'s looking like I either need a different ROM or a different BT card.
Thanks,
Curt
-
I got the Z back up and running after letting it sit w/o power for an hour or so. While I was waiting, I noticed I did not try one thing... adding the `killall hciattach` and `cardctl eject` to the /etc/apm.d/bluetooth file. Now, my bluetooth card is being recognized, and I was able to search for my phone.
So, I\'m all set except for one small detail.... my SE T610 phone wants a passkey. The bluetooth applet did request that I create a passkey, so I assume there\'s a default passkey. I tried 0000, 000000, 0000000, 9999, 999999, 99999999, 1111, etc., but none work. Did a quick search in the forum and didn\'t find anything... anyone here know the correct passkey to use?
Thanks
Curt
-
I think I spent too much time on this last night and needed to come at this again fresh. I found where the passkey is... kept reading over it in the bluetooth how-to and it just didn\'t register.
Curt
-
ccrandal, sorry to put you in all this mess... I realy appriciate your efforts. I will ask tumnus what he did in his packages for the revision G cards to work and will include those fixes into the next ROM version.
BTW, the default pin code is 1234 you did not try that one...
-
No need to apologize. I had a SL-5000D, so I knew when diving back in with another Zaurus this was going to be a bit of a project. The Cacko ROM is pretty dang good! Thanks for your efforts and let me know how I can be of assistance to help.
Yep, I got the right pin... I just read that how-to too many times and kept skipping over that little nugget of info.
To recap, in case anyone else is having the same issues I just went through, to get the Socket CF rev2.5G card to work under the Cacko Qt 1.20 ROM perform these procedures:
1.) Install the bluez_csr_serial_01.ipk package (link on the bluetooth how-to page)
2.) Install sudo (do not install susp-resume or susp-resume-bluez)
3.) Go to Qkonsole and su to root
4.) vi /etc/pcmcia/bluetooth.conf and comment out the 3 lines related to the Socket CF rev2.5G card
5.) vi /etc/apm.d/bluetooth and add the lines \"killall hciattach\" and \"cardctl eject\" to the suspend case block
6.) Using the applet or cmd line, eject the card and then execute `cardctl resume` at the cmd line
7.) Create a Bluetooth Dialup connection in the network applet
8.) In the applet, do a search for your phone (haven\'t gotten PAN to work yet, though... I\'ll keep trying)
9.) Go back to Qkonsole and execute `sdptool browse` and `hciconfig`... both should be giving valid output
10.) Be patient (unlike me), carefully read this thread and the bluetooth how-to... if you can\'t get it to work, go to sleep and try again in the morning.
Thanks all for the help!
Curt
-
BTW, thanks everyone for being patient with me. I\'m an angry IT professional and quickly lose patience when things don\'t work right the first time or two... kinda like road rage behind a monitor.
Now that I\'ve got my BT connection working, I\'m really loving the Cacko Qt ROM a lot. Kudos to maslovsky and tumnus and everyone else involved for their hardwork.
Curt
-
thanks Curt, I now seem to know what needs to be fixed in the ROM to make it work with Socket G cards out of the box.
I\'m planning on new ROM builds next week - would you like to beta test them to make sure Socket G cards are indded handled properly?
Regarding PAN - first double check that it\'s configured properly on the PC end. If it\'s set up then \" sdptool search NAP\" should find your PC as well as the applet.
-
I would be more than happy to beta test the new ROM, just let me know when it\'s ready.
I think my Powerbook should be setup properly. I actually tried to pair from the Powerbook side, but it failed... can\'t remember the error message. But, the Powerbook did find the device \"zaurus\". I need to check out the Mac forums here to see if there\'s something a little special I need to do.
One thing I would like to work on are the WiFi and Bluetooth applets in the network application. I really like how Palm detects and sets up bluetooth devices and WiFi access points. So, after I get a couple of other projects out of the way, I\'d like to give that a try.
Thanks
Curt
-
Hi,
Well I just tried to get my Socket BT card to connect (I think it\'s RevG - I bought it from someone who told me it was - is there a way I can tell)?
ccrandal, I followed your instructions (and after a reboot) everything seems to work (at least I can do hcicontrol ans sdptool now). I am in the process of getting a BT phone so I was trying to get PAN to work. My WinXP machine can detect my Z (shows up a \"Laptop\") when I hit the connect in the applet and it prompts me for a PIN which I typed in. After a short while my XP machine returns with \"Error in pairing with device Laptop\". Reason: Timeout occurred during pairing. I even tried using pand directly from the instructions at http://www.jens-koenen.de/index.html (http://www.jens-koenen.de/index.html) but same error. The sdptool search NAP does find my PC as a NAP.
I am running Cacko 1.2 with the sudo and bluez-serial drivers listed previously in this post. When I commented out the settings in the bluetooth.conf file and insert my CF card, I get a generic Serial or modem type whereas before I got Socket Bluetooth. I am using a Kensington USB BT adapter (on sale at Best Buy this week) on my PC. At the moment I don\'t have any other BT devices to check either my PC or Z against.
Any suggestions?
Thanks.
-Gary
-
Well I finally got PAN to work with my XP machine! I tried lots of things (WinXP-PPP connection, etc) so I\'m not sure of the exact thing that worked. However I think it was modifying the hcid.conf file to enable authentication and encryption (auth enable; encrypt enable; ). Now I am able to do intellisync over BT without any issues as well as FTP to my desktop. It now finds the device as \'zaurus\'.
Now my next task is to setup ICS so I can surf over BT through my PC...
-
I was not able to get PAN to work with my Powerbook, but I only gave it one try. But as in your case, I also was recognized by the Powerbook but would always get an error when trying to pair. I have not gotten around to running sdptool for PAN yet.
I had the bluetooth stuff all working well until I tried ejecting it. It wouldn\'t let me eject because it said it was busy. So, I had to take bluetooth down and then pull it. Afterward, I put my Ambicom WiFi card in and got that set up. Then I powered down... now the On/Off button will not turn it on. This is the same behavior I got when I installed the susp-resume-bluez package.
Obviously there\'s something about the changes I made to the /etc/apm.d/bluetooth script that\'s screwing things up. Perhaps later this week I\'ll be able to take a look. For now, until I\'ve got bluetooth running reliably, I\'m just going to use my Clie for work.
I\'d be interested in hearing about ICS... if you are successful, please let us know.
-
Yeah, I got the cannot eject error message as well so I just pulled it and that seemed to work (I got the card ejected message). I was then able to put in my Ambicom and it worked fine. My power button doesn\'t seem to have any issue (I have an 860). However, when I tried to pull the \"nicely\" using the Bluetooth stop command, my Ambicom WiFi wouldn\'t work afterwards until a reboot (there might of been a way to restart a service... but I don\'t know which one).
Now after my reboot, I get my original errors about timing out Actually, when I did have the PAN working I had the same error when I converted over to using ICS. Ahh, well its getting late so I\'ll take a fresh look at this tomorrow night.
-
I\'m sure the Cacko guys are well on their way to fixing issues with this card... give it a week or two and maybe by then this\'ll be solved.
While I\'m thinking of it, has anyone ever seen a bluetooth/wifi combo CF card? I hate having to carry the extra card with me all the time... I know I will eventually lose it.
-
I can report PAN working with WIDCOMM 1.4.2 Build 10 SP 4 on a win98se machine in our network, without any modification.
The Windows network settings need some attention, though.
Regards
Ant
-
ccrandal,
You ROCK! I\'ve been lurking for quite a while, and trying to get bluetooth to work between my 760 and my Erricson phone for a couple of weeks, and finally, your instructions worked. The only thing I had to do differently was at step 6, I had to re-boot the machine before the card would be recognized. Other than that, it worked great. I\'m posting from my 760 right now!
Thanks again... you were a great help!
-
Glad to hear it worked for you. It\'s a little easier with the Cacko Qt 1.21 ROM, although I\'m getting a couple new problems that I\'m not sure is related or not to bluetooth.
With the new ROM, I find I have to physically eject the card each time I come out of suspend. Trying to eject through the GUI doesn\'t work. Also, when connecting to my phone, it\'ll look as if it\'s connected once the bluetooth connection to the phone has been established, however it is still dialing, so it takes another minute for the internet connection to be established.
Curt
-
GRRR....
Ok... it WAS working... all of the sudden, for now apparent reason, my network connection now just hangs at \"Initializing Modem\"... I just have ATZ in the init string like I always had, and now it doesn\'t work...
Oh well..... back to the drawing board.
-
Pull the card out and reinsert it. If that doesn\'t work, go to the terminal and do a `cardctl resume` after pulling it out and then reinsert it. Hopefully, that\'ll work.
Also, upgrade to Cacko Qt ROM 1.21. It\'s handling of this BT card is better... although I still need to pull the card and reinsert it everytime I turn it on.
HTH,
Curt
-
The problem is that Socket G card has to be treated as a serial card, so bluetooth scripts don\'t apply. This may be the root of the problems.
-
Ok. Here is the problem I am having and reading through this I can seem to find what to do. I have a 860, Cacko 1.21 and the socket 2.5G card and have setup the rfcomm.conf, givepin and dial up connection (though the applet). I am using the drivers, applet, etc that comes in Cacko 1.21.
When I insert the card I can do a spdtool browse and it finds my T68i. But when I try to connect it just sits at Initializing Modem. Now I can use an Ambicom card with this same setup and everything works so it has to be something with the 2.5G card.
Is there any kind of work around to get this card to work? Is there something additional that needs to be setup for the 2.5G card?
Thanks
-
Pull the card and reinsert it. This always happens after coming out of suspend with this card.
-
ccrandal,
Yes I should have mention that. I can pull the card out and reinsert and it doesn\'t make a difference. One thing that I\'m not sure what it means is that when I reinsert the socket card it it pops up \"new card: serial modem\", but the network icon at the botton never comes up. Where the ambicom card does. Not sure if this is normal or not.
Are there any commands you can recommend I can run to make sure everything is ok?
Thanks for your help
-
How do you start the network connection if the network icon never appears? The Socket Rev G card currently needs to be recognised as a serial card due to the interface it uses.
-
I have to go to network, under setting and open it up. Then the network icon at the bottom will appear.
But I am now able to connect through my phone to internet. For some reason it needed a \"1\" in the rfcomm.conf file for channel. I used a \"4\" with the Ambicom card and thought it would be the same.
So I can now successful connect by pulling out the card, putting it back in, opening the network program and then connecting.
Thanks for all of you help and hopefully we can find a solution so it doesn\'t require some many steps.
-
Ok. Now I am having a problem creating a PAN to share my broadband connection and would really appreciate all of your input. I am using the instructions on www.jens-koenen.de/index.html. I can successfully connect to the bluetooth card on my PC, but can\'t ever get the shared Internet access to work. Here is what I have done.
1. Activate LAN access profile on my PC. Added attachment.
2. Changed IP address to 192.168.129.1 for bluetooth network. Added attachment.
At this point I can successfully ping my PC at 192.168.129.1. But since I don\'t have Internet sharing setup I can\'t access the Internet.
3. So now I attempt to sharing my Internet connection with my bluetooth card. So I go to network devices, right click on my Wifi card, go to properties, click on advanced, and check Allow of users to connect through this computers network connect, and then click ok. Once I do this it pops up a message say When Internet Connection sharing is enable, your LAN adapter will be set to use IP 192.168.0.1. If I click ok it changes the IP I setup earler for the bluetooth card and I can no longer ping the PC or get on the Internet. Added attachment for this too.
Any ideas of what I am doing wrongs. Also I am using the startpan.sh and killpan.sh for the website with only the MAC changed to mine. startpan.sh works find until step 3 and then I can ping anything.
Thanks
-
anyone?
-
When you set up internel connection sharing in WinXP, your bluetooth adapter will have IP address 192.168.0.1. So you need to set IP addres for your Zaurus bluetooth interface to be in the same range, ex. 192.168.0.100. After you connect, you should be able to access your network and internet via the shared connection.
-
Hi!
Can this card now be used relatively \"hassle-free\" under 1.21? I really like the fact that it sits flush in the CF slot, but I also don\'t want to rip out my hair in frustration getting it to work. Maybe a Blue Monkey card is still the easiest to get up and running?
Thanks!
-
Well its not hassle-free, but easier than before. The setup is the same as it is with the other cards. But each time you turn it on (or come back from resume) you have to pull the card out, push it back in, open the network app, and then connect. So its not hassel free, but it looks alot better not have a card sticking out
-
maslovsky, thanks. I tried this and still no luck. I can ping 192.168.0.1 sucessfully, but I can\'t get anything outside of this. Do you have any idea of something else I can check?
-
I have to go to network, under setting and open it up. Then the network icon at the bottom will appear.
I have this same problem--after a bit of hacking my /etc/apm.d/bluetooth file so that the card gets reset and bluetooth gets restarted at all. The network icon doesn\'t appear after the reappearance of the CF icon, unless and until I open the Network Settings application. I\'ve semi-solved this problem by even more adulteration of the /etc/apm.d/bluetooth file, so it starts and then kills a copy of /home/QtPalmtop/bin/netsetup after it starts bluetooth. This seems like a very clumsy workaround, though, so I ask: is there any way to force the GUI to re-check the availability of networking (which it obviously does when netsetup launches)?
-
Glad to hear it worked for you. It\'s a little easier with the Cacko Qt 1.21 ROM, although I\'m getting a couple new problems that I\'m not sure is related or not to bluetooth.
Curt
Hello could you tell me if there is anything different in your instructions for the 1.2.0 ROM for the 1.2.1A ROM?
Could someone tell me what is included in the new ROM with regards to the Sockect Rev. card?
Thanks in advance.
Guy
-
Glad to hear it worked for you. It\'s a little easier with the Cacko Qt 1.21 ROM, although I\'m getting a couple new problems that I\'m not sure is related or not to bluetooth.
Curt
Hello could you tell me if there is anything different in your instructions for the 1.2.0 ROM for the 1.2.1A ROM?
Could someone tell me what is included in the new ROM with regards to the Sockect Rev. card?
Thanks in advance.
Guy
Socket G card should work out of the box (though still not perfect) under 1.21 and later ROMs. I\'m getting such card soon and hopefully we\'ll get to improve support for it.
-
Socket G card should work out of the box (though still not perfect) under 1.21 and later ROMs. I\'m getting such card soon and hopefully we\'ll get to improve support for it.
Following above notes and the how to guide - I can\'t seem to find the bluetooth program in order to restart bluetooth etc on the rom - it\'s not on the same place - do I need to install any packages in order to get the card to work? - Sorry being stupid again!
Guy
-
Socket G card should work out of the box (though still not perfect) under 1.21 and later ROMs. I\'m getting such card soon and hopefully we\'ll get to improve support for it.
Following above notes and the how to guide - I can\'t seem to find the bluetooth program in order to restart bluetooth etc on the rom - it\'s not on the same place - do I need to install any packages in order to get the card to work? - Sorry being stupid again!
Guy
Go to Network Setting and create a new bluetooth connection.
-
Go to Network Setting and create a new bluetooth connection.
Excellant - it now works - I was rather easier than I expected!
-I had to pull and then re-insert the card
-Then I used VI to change the pin code in the pin file
-Executed paring from the phone and input the above new pin - paired fine (had to pull the card and re-insert it again for it to take on the pin change, how do I re-start the bluetooth from the command line as in the how to doc?)
-Did a search for the modem whilst setting up the new connection - selected the right ID for my phone
- Now it connects- cool.
Thanks very much for all your help.
Guy
-
I\'m glad it works now.
how do I re-start the bluetooth from the command line as in the how to doc?
IN Cacko ROMs bluetooth is restarted whenever you eject/insert the card
-
Some good news about Socket G cards. Recently I finaly got my hand on one such card (many thanks to ccrandal) and decided to play with it and make it easier to use on Cacko ROM.
So far I was able to make this card be properly initialized upon insertion and even being recognized and displayed by the cardmon applet as a bluetooth card, not just serial one. Also, the bluetooth stack starts and stops properly and cleanly.
There are a couple of small issues (mostly innoyences) remain, and I don't know if I'll get to fix them:
- the globe icon does not appear immidiately when card is inserted, you have to start Network Setting application for it to appear;
- the speed is limited to 230400, which is twice less than Ambicom/Pretec cards can do;
If I don;t find any other issues while testing, I'll inslude this into the next ROM update (or hotfix)
-
I got my rev g card working, and wrote up a little howto. Apologies for mistakes/omissions. No guarantees made, your house and car will explode if you follow these instructions, etc. etc.
Cacko 1.21b + Socket Rev G + Sony Ericsson T610 + T-mobile HOWTO (obscurite nov 04)
1. Pair phone with zaurus
a. On phone, connectivity -> bluetooth -> my devices -> new device. This will search for and find the zaurus.
2. Create CID/APN on phone
a. On phone, connectivity -> data comm -> data accounts -> new account -> gprs
b. Enter a single digit as a number (I used 2). This will be referred to as the CID.
c. For the APN, if you have T-mobile unlimited internet use internet2.voicestream.com. I've heard that internet3.voicestream.com is for "VPN" from other posts.
3. Create bluetooth dialup
a. On zaurus, open network app
b. Select "Dial-up (Bluetooth)" from dropdown menu, click "Add"
d. In the account tab, for the "phone" field, use *9***2#. 2 is my CID, but if you selected a different one in step 2, use that instead of 2.
e. In the modem tab, click the search button. Make sure your phone is in visible mode, and it should pick up the DUN for your phone. It will look like 00:0E:D3:83:F1:EE, 1 (I made that up but yours should look similar).
4. Make sure you can connect. Open a console and try pinging google.com or something. Once you do that, make your phone invisible again. You will be able to receive calls while connected, but your connection will essentially freeze while you are on the phone. You will also be able to receive calls (but again, data is frozen automatically, it seems).
5. When you suspend (power off) your zaurus, and resume, your card will not be ready to reconnect. You'll have to either eject/insert your card physically or run /etc/pcmcia/bluetooth restart as root (or with sudo). Also, if you had the network app open, you may need to close it and re-open it. The globe network icon on the bottom will not re-appear until you restart the network app.
6. If you prefer to dial from the command line use "pppd call BLUETOOTH" where BLUETOOTH is the name of the peers file in /etc/ppp/peers/ that has been created for your dial up connection. Mine was BLUETOOTH1098189070. You could set up a start stop script really easily... on my todo list
Issues + Comments
------------
* The dialup network app always goes back to 115200 but in actuality the /etc/ppp/peers/BLUETOOTHwhatever script has 230400... a little confusing
* Of course, we need to automate the running of /etc/pcmcia/bluetooth restart upon trying to dial...
* My best GPRS speeds are around 40kbps or better which seems on par with what I've read from others... about 1000ms latency, which isn't great but hey, better than CDPD like the old days
UPDATE:
I have automated the connection/disconnection in such a way that I no longer need to:
* re-insert the card when I resume from suspend
* open the network app
I personally use the console most of the time, rather than the gui, so this is great for me. I just log in and type "bton" or btoff" and my bluetooth is connected or disconnected.
1. Add "%users localhost=/etc/pcmcia/bluetooth" to /etc/sudoers (you'll need to su to root first)
2. Edit /home/zaurus/.profile and add the following two lines
alias bton="sudo /etc/pcmcia/bluetooth/restart && sudo pppd call BLUETOOTH"
alias btoff="sudo /etc/pcmcia/bluetooth/stop"
In step 2, replace BLUETOOTH with the name of your bluetooth peer file in /etc/ppp/peers/. Mine was BLUETOOTH with some numbers after it and no extension.
-
One other thing... I'd really like to get the network connection icon (the globe) to show as being in a connected state when I am connected but I have no idea how to activate the icon or change it's state... maslovsky?
-
I just replaced my aircable bluetooth adapter with a socket card. Under cacko 1.21b, here's what I did to be lazy.
In network app I added the a bluetooth dail-up profile with all the trimmings.
then i replaced my aircable profile in /etc/ppp/peers with a symlink to the bluetooth file created by the network app
except for the need to re-insert the card after a resume, i can just click on the globe and startup my connection. the network dockapp works exactly as expected.
In the future i may add a pcmcia restart somewhere in there so i don't have to think about it.
--matrix
-
Hi, I have Socket Bluetooth rev G card, can use PAN with WinXP, but real speed is about 52kBps instead of 700 kbps. Any ideas? Driver is BlueZ 2.3-2.4.18d
-
Hi all,
I have a Socket bluetooth card. I had tried setting the bluetooth with all the instructions listed throughout this post but I can't have the zaurus C750 to connect to the internet.
The problem:
I had setup a Bluetooth Connection using the instructions listed throughout this post and getting the device number and channel number.
When I try tapping the globe to bring out the connection applet (I am using Cacko 1.21b), there is no option for the connecting via bluetooth and instead I saw the option to connect to the internet via IrDA. This happened even the Network Setting Applet. That means I have no way to connect to internet through Bluetooth.
I had done a bluetooth restart, and the bluetooth options of connecting to the internet is still unavailable.
Any advice/help will be appreciated.
Thank you.
-
You need a new globe "connection" applet that knows about bleutooth modules. There's no such applet yet. I was sent the source of a nice "network monitor" applet by IRK author, which I will try to turn into a replacement of the globe applet. But it's low priority.
Use qcop meanwhile.
-
Delete IRDA connection and your bluetooth connections will show up. This will be fixed in 1.22 Cacko ROM.
-
Delete IRDA connection and your bluetooth connections will show up. This will be fixed in 1.22 Cacko ROM.
-
Hi guys,
thanks for all your replies. i will try when i get back home this evening. i forgot to bring the bluetooth card with me to work today.
cheers