Hi,
I've been trying to make my embedded bluetooth card work, but it seems i
have a big problem...
Before explaining it, here is my hardware specification:
Dell D830 laptop, and my bluetooth card (running lsusb):
Bus 001 Device 003: ID 413c:8140 Dell Computer Corp. Wireless 360 Bluetooth
I have installed bluez-utils, bluez-libs, bluetooth, everything that is seem
to be needed.
Here is what hciconfig give me:
hci0: Type: USB
BD Address: 00:1A:6B:8A:xx:xx ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:4134 acl:0 sco:0 events:136 errors:0
TX bytes:2047 acl:0 sco:0 commands:133 errors:0
So my BT card seems to work ... but when I run a scan or an inq (with
hcitool), nothing is found. Also, the bluetooth led of my laptop is off ...
After doing many test, i was wondering if it was not a hardware problem, so
i have boot to windows to see if my card words. Everything worked fine, the
led was on, the scan showed my phone. Then i reboot on linux, and here is
the thing weird, my bluetooth card was still working (the led was on).
So i start bluetooth daemon (hcid, sdpd), i run a scan, and my phone is
found !!!
The problem seems to be the bluetooth card doesn't "start"/"stop" on linux
(the led story confirms that). So, is there a way to solve this thing ? Have
I done something wrong ?
Thanks
--
Franck F.
Hey Frank
had a similar problem on my acer Ferrari 3000? I could not turn the
Bluetooth (led) on or off whit the button on the side, but if I booted up in
windows it was on when I booted in to Linux (and Bluetooth worked).. I
solved by using acerhk module? if this is the problem you should look for a
hot key module for your dell?
Regards
Morten Kromann
_____
Fra: [email protected]
[mailto:[email protected]] P? vegne af Franck F
Sendt: 6. december 2007 00:15
Til: BlueZ users
Emne: Re: [Bluez-users] Dell D830 laptop BT card doesn't start
Well, of course i did :) (the wifi works fine ;) )
2007/12/5, Michael Mauch <[email protected]>:
Franck F wrote:
> Well, it seems my problem will not be solved soon ...
Did you enable the WiFi/Bluetooth switch on the left side
of the box?
Regards...
Michael
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
--
Franck Farina.
Well, of course i did :) (the wifi works fine ;) )
2007/12/5, Michael Mauch <[email protected]>:
>
> Franck F wrote:
>
> > Well, it seems my problem will not be solved soon ...
>
> Did you enable the WiFi/Bluetooth switch on the left side
> of the box?
>
> Regards...
> Michael
>
> -------------------------------------------------------------------------
> SF.Net email is sponsored by: The Future of Linux Business White Paper
> from Novell. From the desktop to the data center, Linux is going
> mainstream. Let it simplify your IT future.
> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
> _______________________________________________
> Bluez-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
--
Franck Farina.
Franck F wrote:
> Well, it seems my problem will not be solved soon ...
Did you enable the WiFi/Bluetooth switch on the left side
of the box?
Regards...
Michael
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Well, it seems my problem will not be solved soon ...
Anyway, thanks for your help :)
Regards,
Franck F.
Marcel Holtmann wrote:
> Hi Franck,
>
> > if I am not mistaken, then this is a CSR based dongle. Would
> > need to
> > decode the Rev=43.15 into the build id. However an easier way
> > is when
> > you boot into Windows first and then into Linux so the dongle
> > works and
> > then execute bccmd buildname (as root).
> >
> > Here is the result of bccmd buildname:
> > Build name: cyt_8unified_fl_bt2.0_kymodo_21d_0702212310_encr56
> > 2007-02-21
>
> this is a special build for Dell as it seems. I have no idea what's so
> special about it. Only Dell or CSR people can answer that.
>
> Maybe you need to enable the antenna or something. I don't know. There
> could be also some ACPI magic that does this job.
>
> > You could sniff the init sequence under Windows. Would help to
> > find the
> > init sequence.
> >
> > hmm, How can i do that ? and what should i do when i'll find the init
> > sequence ?
>
> You can use USBsnoopy or run Linux and then Windows in a VMware and use
> usbmon. There is no easy way to explain this task. Find someone who
> donates one of these laptops and I can do it by myself. Otherwise you
> are on your own here.
>
> Regards
>
> Marcel
>
>
>
> -------------------------------------------------------------------------
> SF.Net email is sponsored by: The Future of Linux Business White Paper
> from Novell. From the desktop to the data center, Linux is going
> mainstream. Let it simplify your IT future.
> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
> _______________________________________________
> Bluez-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Franck,
> if I am not mistaken, then this is a CSR based dongle. Would
> need to
> decode the Rev=43.15 into the build id. However an easier way
> is when
> you boot into Windows first and then into Linux so the dongle
> works and
> then execute bccmd buildname (as root).
>
> Here is the result of bccmd buildname:
> Build name: cyt_8unified_fl_bt2.0_kymodo_21d_0702212310_encr56
> 2007-02-21
this is a special build for Dell as it seems. I have no idea what's so
special about it. Only Dell or CSR people can answer that.
Maybe you need to enable the antenna or something. I don't know. There
could be also some ACPI magic that does this job.
> You could sniff the init sequence under Windows. Would help to
> find the
> init sequence.
>
> hmm, How can i do that ? and what should i do when i'll find the init
> sequence ?
You can use USBsnoopy or run Linux and then Windows in a VMware and use
usbmon. There is no easy way to explain this task. Find someone who
donates one of these laptops and I can do it by myself. Otherwise you
are on your own here.
Regards
Marcel
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
2007/12/5, Marcel Holtmann <[email protected]>:
>
> Hi Franck,
>
> > > I've been trying to make my embedded bluetooth card work,
> > but it seems
> > > i have a big problem...
> > > Before explaining it, here is my hardware specification:
> > > Dell D830 laptop, and my bluetooth card (running lsusb):
> > > Bus 001 Device 003: ID 413c:8140 Dell Computer Corp.
> > Wireless 360
> > > Bluetooth
> >
> > show me /proc/bus/usb/devices for your card.
> >
> > T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
> > D: Ver= 2.00 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
> > P: Vendor=413c ProdID=8140 Rev=43.15
> > C:* #Ifs= 3 Cfg#= 1 Atr=e0 MxPwr= 0mA
> > I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> > E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
> > E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> > E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> > I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> > E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
> > E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
> > I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> > E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
> > E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
> > I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> > E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
> > E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
> > I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> > E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
> > E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
> > I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> > E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
> > E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
> > I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> > E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
> > E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
> > I:* If#= 2 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none)
>
> if I am not mistaken, then this is a CSR based dongle. Would need to
> decode the Rev=43.15 into the build id. However an easier way is when
> you boot into Windows first and then into Linux so the dongle works and
> then execute bccmd buildname (as root).
Here is the result of bccmd buildname:
Build name: cyt_8unified_fl_bt2.0_kymodo_21d_0702212310_encr56 2007-02-21
What should i do with that ?
> The card might need a special init sequence to make it work.
> > You can try
> > to load hci_usb with reset=1 module option. That might be
> > enough.
> >
> >
> > I tried and nothing change :(
>
> You could sniff the init sequence under Windows. Would help to find the
> init sequence.
hmm, How can i do that ? and what should i do when i'll find the init
sequence ?
Thanks again.
--
Franck F.
Hi Franck,
> > I've been trying to make my embedded bluetooth card work,
> but it seems
> > i have a big problem...
> > Before explaining it, here is my hardware specification:
> > Dell D830 laptop, and my bluetooth card (running lsusb):
> > Bus 001 Device 003: ID 413c:8140 Dell Computer Corp.
> Wireless 360
> > Bluetooth
>
> show me /proc/bus/usb/devices for your card.
>
> T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
> D: Ver= 2.00 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
> P: Vendor=413c ProdID=8140 Rev=43.15
> C:* #Ifs= 3 Cfg#= 1 Atr=e0 MxPwr= 0mA
> I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
> E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
> E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
> I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
> E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
> I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
> E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
> I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
> E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
> I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
> E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
> I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
> E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
> E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
> I:* If#= 2 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none)
if I am not mistaken, then this is a CSR based dongle. Would need to
decode the Rev=43.15 into the build id. However an easier way is when
you boot into Windows first and then into Linux so the dongle works and
then execute bccmd buildname (as root).
> The card might need a special init sequence to make it work.
> You can try
> to load hci_usb with reset=1 module option. That might be
> enough.
>
>
> I tried and nothing change :(
You could sniff the init sequence under Windows. Would help to find the
init sequence.
Regards
Marcel
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Marcel, thanks for the previous answer :)
> I've been trying to make my embedded bluetooth card work, but it seems
> > i have a big problem...
> > Before explaining it, here is my hardware specification:
> > Dell D830 laptop, and my bluetooth card (running lsusb):
> > Bus 001 Device 003: ID 413c:8140 Dell Computer Corp. Wireless 360
> > Bluetooth
>
> show me /proc/bus/usb/devices for your card.
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=413c ProdID=8140 Rev=43.15
C:* #Ifs= 3 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=(none)
E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
I:* If#= 2 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none)
> I have installed bluez-utils, bluez-libs, bluetooth, everything that
> > is seem to be needed.
> >
> > Here is what hciconfig give me:
> > hci0: Type: USB
> > BD Address: 00:1A:6B:8A:xx:xx ACL MTU: 310:10 SCO MTU: 64:8
> > UP RUNNING PSCAN ISCAN
> > RX bytes:4134 acl:0 sco:0 events:136 errors:0
> > TX bytes:2047 acl:0 sco:0 commands:133 errors:0
> >
> > So my BT card seems to work ... but when I run a scan or an inq (with
> > hcitool), nothing is found. Also, the bluetooth led of my laptop is
> > off ...
> >
> > After doing many test, i was wondering if it was not a hardware
> > problem, so i have boot to windows to see if my card words. Everything
> > worked fine, the led was on, the scan showed my phone. Then i reboot
> > on linux, and here is the thing weird, my bluetooth card was still
> > working (the led was on).
> >
> > So i start bluetooth daemon (hcid, sdpd), i run a scan, and my phone
> > is found !!!
> >
> > The problem seems to be the bluetooth card doesn't "start"/"stop" on
> > linux (the led story confirms that). So, is there a way to solve this
> > thing ? Have I done something wrong ?
>
> The card might need a special init sequence to make it work. You can try
> to load hci_usb with reset=1 module option. That might be enough.
I tried and nothing change :(
--
Franck.
Hi Franck,
> I've been trying to make my embedded bluetooth card work, but it seems
> i have a big problem...
> Before explaining it, here is my hardware specification:
> Dell D830 laptop, and my bluetooth card (running lsusb):
> Bus 001 Device 003: ID 413c:8140 Dell Computer Corp. Wireless 360
> Bluetooth
show me /proc/bus/usb/devices for your card.
> I have installed bluez-utils, bluez-libs, bluetooth, everything that
> is seem to be needed.
>
> Here is what hciconfig give me:
> hci0: Type: USB
> BD Address: 00:1A:6B:8A:xx:xx ACL MTU: 310:10 SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN
> RX bytes:4134 acl:0 sco:0 events:136 errors:0
> TX bytes:2047 acl:0 sco:0 commands:133 errors:0
>
> So my BT card seems to work ... but when I run a scan or an inq (with
> hcitool), nothing is found. Also, the bluetooth led of my laptop is
> off ...
>
> After doing many test, i was wondering if it was not a hardware
> problem, so i have boot to windows to see if my card words. Everything
> worked fine, the led was on, the scan showed my phone. Then i reboot
> on linux, and here is the thing weird, my bluetooth card was still
> working (the led was on).
>
> So i start bluetooth daemon (hcid, sdpd), i run a scan, and my phone
> is found !!!
>
> The problem seems to be the bluetooth card doesn't "start"/"stop" on
> linux (the led story confirms that). So, is there a way to solve this
> thing ? Have I done something wrong ?
The card might need a special init sequence to make it work. You can try
to load hci_usb with reset=1 module option. That might be enough.
Regards
Marcel
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users