Messages

31

Zaurus - pdaXrom / Rc10 Out For Testing..

« on: June 20, 2005, 12:16:58 am »

What a fantastic ROM! I'm using a C1000 and have a couple of issues, however.

1. The right shift key doesn't work (won't capitalize or get symbols)
2. My ambicom wl-1100c connects to my ap (wep) without problems but I can't get it to work with kismet.
I've tried using the "hostap" driver as per the instructions I've seen on the forums but to no avail.

32

Angstrom & OpenZaurus / Ambicom Bt 2000 E And 5600 Problems...

« on: March 30, 2005, 11:28:13 pm »

Thanks for the links but I'm using OZ 3.5.2. I actually did use those instructions when setting up bluetooth (with the same card) using the Sharp/Watapon ROM and it worked great!

My impression was that OZ has a different kernel config so those instructions won't apply.

33

Angstrom & OpenZaurus / Ambicom Bt 2000 E And 5600 Problems...

« on: March 30, 2005, 09:08:49 pm »

I've got an ambicom BT2000-CF (yellow sticker) and am having issue with bluetooth on OZ 3.5.2. Searching through the forums seems to suggest that this card should work and I've had no problems with the bluez stuff with the Sharp ROM (1.32) or Watapon (1.4).

I installed task-opie-bluetooth and for good measure installed the libs from the bluetooth kernel from another thread (bluecard_cs.o and friends). "Cardctl ident" gives me:

Socket 0:
    Product info: "Ambicom,Inc", BT2000E, "Bluetooth PC/CF Card"
    manfid: 0x22d, 0x2000
    function: 2 (serial)
Socket 1:
    no product info available

 but "hciconfig hci0 up" gives me:

Can't open HCI socket: Address family not supported by protocol

After a "modprobe bluez" followed up with an "hciconfig hci0 up" I get:

Can't get device info: No such device.

Needless to say, the bluetooth manager also does not indicate any BT card. Am I missing something obvious here? Any tips or suggestions would be much appreciated.