Messages

1

Security and Networking / New Bluetooth Drivers

« on: February 22, 2005, 12:58:18 pm »

Does the card automatically eject and reappear when you resume? Look at the CF icon on the taskbar when you resume. If nothing happens to it, did you remember to install the susp-resume and sudo packages too?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=68085\"][{POST_SNAPBACK}][/a][/div]

hello tumnus.
Yes sudo and susp-resume are installed.
With a Socket Rev F card, I observed that the icon disappeared and reappeared.
But with an H/G card, it does not happen.

The script /etc/apm.d/bluetooth has the follwing section

Code: [Select]

if ["'/usr/sbin/hciconfig" != "" ]; then
   ...
fi
I tried commenting out all the resume lines in that script and issuing the commands manually. That's where I noticed that the hcidonfig command returned nothing, which means that the other commands in the if statement won;t be executed either.
The other thing was that cardctl status showed the card as suspended. resuming the card restored everything: hciconfig ok, hcitool ok etc...
that's why I simply added the cardctl resume statement to the apm.d/bluetooth script, and things are now working fine.
shouldn't the card manager take care of resuming the card ?

2

Security and Networking / New Bluetooth Drivers

« on: February 21, 2005, 12:03:24 pm »

hey tumnus,
Here's another input.
I tried the alpha3 with a Socket revG and the new susp-resume-bluez (0.9.2) on SL-C860.

The alpha3 package seemed fine, but after a suspend I had to eject/insert the card to get it to work again.

Actually, I noticed 2 things when coming back from standby.
1. "hciconfig" would not display any info about the card.
2. cardctl status would show the card as being in "suspend" mode. Issuing a "cardctl resume" changes the status to ready, and both "hcitool dev" and "hciconfig" would now display the card information.
So I added "cardctl resume" inside the apm.d/bluetooth script (outside of "if" statements) and now my card seems to come back up without having to eject it.

I'm not sure what I'm doing, just trying things out. Hope this can make sense to you.

3

C1000/3x00 General discussions / Bluetooth On The Sl-3000?

« on: February 18, 2005, 12:58:34 pm »

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...

4

Cxx0 General discussions / File Type Association On C860

« on: February 09, 2005, 01:29:22 pm »

Hi,
I seem to have lost all file types / programs associations on my C860 with its original Sharp ROM.

It doesn't know anymore how to open a .txt file for instance.

Is there a file somewhere that maps mime/types to given applications ?
Thanks!

5

C1000/3x00 General discussions / Bluetooth On The Sl-3000?

« on: February 01, 2005, 06:39:51 pm »

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!