![]() ![]() |
Dec 4 2006, 09:15 AM
Post
#1
|
|
|
Group: Members Posts: 7 Joined: 27-November 06 Member No.: 12,814 |
My bluetooth card for SL5500 is pretec BT 2000E(CF stocket). The problem is that when I insert it into the stocket, it can be recognized.
But when I use the command "hcitool dev" to check the MAC address, there is no devics. I had put the bt950_cs.o into the correct path. and reboot the machine again and again. It still doesn't work. Can some one give me some hits? my situation is similar with the article describe before, but using this method still can't solve my problem. http://www.oesf.org/forums/lofiversion/index.php?t20488.html Thanks |
|
|
|
Dec 4 2006, 01:34 PM
Post
#2
|
|
![]() Group: Admin Posts: 3,277 Joined: 29-July 04 From: Cambridge, England Member No.: 4,149 |
please provide output from
cardctl status cardctl ident cardctl info thanks |
|
|
|
Dec 4 2006, 02:25 PM
Post
#3
|
|
|
Group: Members Posts: 7 Joined: 27-November 06 Member No.: 12,814 |
CODE root@collie:~# cardctl status Socket 0: 3.3V 16-bit PC Card function 0: [ready], [bat dead], [bat low] Socket 1: no card CODE Socket 0: product info: "Pretec", "BT2000E", "Bluetooth PC/CF Card" manfid: 0x022d, 0x2000 function: 2 (serial) Socket 1: no product info available CODE PRODID_1="Pretec" PRODID_2="BT2000E" PRODID_3="Bluetooth PC/CF Card" PRODID_4="" MANFID=022d,2000 FUNCID=2 PRODID_1="" PRODID_2="" PRODID_3="" PRODID_4="" MANFID=0000,0000 FUNCID=255 Thanks a lot |
|
|
|
Dec 5 2006, 04:38 AM
Post
#4
|
|
![]() Group: Admin Posts: 3,277 Joined: 29-July 04 From: Cambridge, England Member No.: 4,149 |
hm, well, your card looks like it's working.
I've been looking at my config files in /etc/pcmcia and /etc/hotplug and can't find anything that seems to match. My guess is that you should be able to hack an entry into your /etc/pcmcia/serial.conf to bind a serial device to it... something like card "Pretec BT2000E Bluetooth PC/CF Card" manfid: 0x022d, 0x2000 bind "serial_cs" eject the card and "HUP" the cardmanager (or reboot). sorry, that's my best guess. |
|
|
|
Dec 5 2006, 04:39 AM
Post
#5
|
|
![]() Group: Admin Posts: 3,277 Joined: 29-July 04 From: Cambridge, England Member No.: 4,149 |
might be worth asking in the security and networking forum too, as this is a generic hardware/config problem and not necessarily 5000 specific
|
|
|
|
Dec 5 2006, 12:26 PM
Post
#6
|
|
|
Group: Members Posts: 7 Joined: 27-November 06 Member No.: 12,814 |
QUOTE(speculatrix @ Dec 5 2006, 01:38 PM) hm, well, your card looks like it's working. I've been looking at my config files in /etc/pcmcia and /etc/hotplug and can't find anything that seems to match. My guess is that you should be able to hack an entry into your /etc/pcmcia/serial.conf to bind a serial device to it... something like card "Pretec BT2000E Bluetooth PC/CF Card" manfid: 0x022d, 0x2000 bind "serial_cs" eject the card and "HUP" the cardmanager (or reboot). sorry, that's my best guess. CODE In my machine there is no /etc/pcmcia/serial.conf but only /etc/pcmcia/bluetooth.conf and in bluetooth.conf I found some similar link device "bt950_cs" class "bluetooth" module "bt950_cs" card "Pretec BT2000E Bluetooth Card" version "Pretec", "BT2000E" bind "bt950_cs" there is no specified like manfid: 0x022d, 0x2000. Do I need to tell the machine this, but which file I should add this line. in bluetooth.conf, there no similar line exit for other brand bluetooth card. |
|
|
|
Dec 6 2006, 03:07 AM
Post
#7
|
|
![]() Group: Admin Posts: 3,277 Joined: 29-July 04 From: Cambridge, England Member No.: 4,149 |
QUOTE(yanyan @ Dec 5 2006, 09:26 PM) QUOTE(speculatrix) card "Pretec BT2000E Bluetooth PC/CF Card" manfid: 0x022d, 0x2000 bind "serial_cs" In my machine there is no /etc/pcmcia/serial.conf but only /etc/pcmcia/bluetooth.conf and in bluetooth.conf I found some similar link there is no specified like manfid: 0x022d, 0x2000. Do I need to tell the machine this, but which file I should add this line. in bluetooth.conf, there no similar line exit for other brand bluetooth card. try then putting my config snippet into your bluetooth.conf file (after taking a backup!) and see if that works. |
|
|
|
![]() ![]() |
|
Lo-Fi Version | Time is now: 18th May 2013 - 06:26 AM |