fujitsu-siemens pc card

Hi!

I recently obtained a Fujitsu-Siemens Bluetooth PC Card and tried a lot but could not make it work. I tried with debian sid, kernel 2.4.22 (from kernel.org, not the debian one), on an Asus L3400Tp notebook.

Pcmcia support is in the kernel (not in a module), the pcmcia socket itself seems ok (though I can not test it with another card as I only have this one):

# cardctl ident
Socket 0:
  product info: "OXSEMI", "OXCB950", "Rev A"
  manfid: 0x0279, 0x0001
  function: 2 (serial)
Socket 1:
  no product info available

I applied this patch to my kernel: http://www.ussg.iu.edu/hypermail/linux/kernel/0203.0/0040.html
(Shouldn't 'cardctl ident' tell the real vendor and name for the bluetooth card, instead of the uart?)

I edited modules.conf according to the BlueZ Howto, now bluez modules load automatically on boot, rfcomm l2cap and bluez is loaded all right.

When I plug in the card, the following is written to /var/log/messages:

Oct  2 11:17:30 lgnote kernel: cs: cb_alloc(bus 2): vendor 0x1415, device 0x950b
Oct  2 11:17:30 lgnote kernel: PCI: Enabling device 02:00.0 (0000 -> 0003)
Oct  2 11:17:30 lgnote kernel: ttyS04 at port 0x4000 (irq = 9) is a 16C950/954
Oct  2 11:17:30 lgnote pci.agent[577]: ... no modules for PCI slot 02:00.0

There was no /dev/ttyS04 (and no ttyS4 either), so i created one (major number 4, minor 68).

Then I tried hciattach:

# hciattach -n /dev/ttyS04 any
It seems to work OK, hci0 device is created, but hciconfig hci0 up does not work:
Can't init device hci0. Connection timed out(110).

I tried loading all the bluetooth modules (hci_uart, btuart_cs, ...) one by one and all of them together ( :) ), but the result is the same. I also tried hciattach with different device types (ericsson, digi, ...), some of them seems OK (but the problem with hciconfig still remains), with others it does not even start (for example with csr it says "Initialization timed out").

I have no further ideas, am I doing something wrong? Or is this card not supported at all? :(

Thank you all,
Gabor Lengyel (Lgaga)

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Hi Gabor,

it seems that this is a serial cardbus card with a Bluetooth chip on it. So please use the yenta_socket PCMCIA bridge driver and you must find out which Bluetooth chip they are using.

Do you got this card working with Windows? If yes, please try to get access to another machine with Bluetooth running Linux and run

hcitool info <bdaddr>

Regards

Marcel

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Hi,

I did have yenta compiled in the kernel, but I recompiled the whole pcmcia support as a module, so now I have a yenta_socket module (loaded). Searching through the net with google, I found somewhere that in /etc/default/pcmcia I probably should have PCIC=yenta_socket, so I changed that (it was PCIC=i82365 before). However, nothing changed. :( It still does exactly the same I tried to explain in my previous post. Maybe I should add some parameters to yenta_socket? I am not very familiar with pcmcia, should I do anything besides these to "use the yenta_socket PCMCIA bridge driver" as you said?

I might be able to do this next Tuesday, but not until then. :(

Thank You very much,
Gabor Lengyel (Lgaga)