public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Schrell" <as@schrell.de>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] SOLVED: Dell Inspiron 8600 was: 'hciconfig -a' ok, but 'hcitools scan' shows no devices
Date: Sun, 12 Dec 2004 11:38:32 +0100 (CET)	[thread overview]
Message-ID: <33016.80.146.4.18.1102847912.squirrel@schrell.de> (raw)
In-Reply-To: <1102838764.8750.32.camel@pegasus>


Marcel,

thanks a lot for your help.

SUMMARY:

hciconfig -a         looked right
hcitool scan         did not show any devices

RESOLUTION:

Bluetooth was diabled under Windows!
There was no way to start it from Linux as far as I know.

After booting Windows and activation Bluetooth (right click on icon in
task bar, then activate) it works under Linux. Nothing to do with <FN-F2>.
Now the blue Bluetooth LED is on even on Linux startup.

Thank You, Marcel, for your help!

Andreas


> Hi Andreas,
>
>> And hcidump -X from "hciconfig -a" and "hcitool scan":
>>
>> HCIDump - HCI packet analyzer ver 1.12
>> device: hci0 snap_len: 1028 filter: 0xffffffff
>> < HCI Command: Read Local Name (0x03|0x0014) plen 0
>> > HCI Event: Command Complete (0x0e) plen 252
>>   0000: 01 14 0c 00 64 65 6c 6c  69 2d 30 00 00 00 00 00
>> ....delli-0.....
>>   0010: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>> ................
>>   0020: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>> ................
>>   0030: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>> ................
>>   0040: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>> ................
>>   0050: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>> ................
>>   0060: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>> ................
>>   0070: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>> ................
>>   0080: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>> ................
>>   0090: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>> ................
>>   00a0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>> ................
>>   00b0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>> ................
>>   00c0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>> ................
>>   00d0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>> ................
>>   00e0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>> ................
>>   00f0: 00 00 00 00 00 00 00 00  00 00 00 00              ............
>> < HCI Command: Read Class of Device (0x03|0x0023) plen 0
>> > HCI Event: Command Complete (0x0e) plen 7
>>   0000: 01 23 0c 00 00 01 00                              .#.....
>> < HCI Command: Read Local Version Information (0x04|0x0001) plen 0
>> > HCI Event: Command Complete (0x0e) plen 12
>>   0000: 01 01 10 00 02 f2 04 02  0a 00 f2 04              ............
>> < HCI Command: Inquiry (0x01|0x0001) plen 5
>>   0000: 33 8b 9e 08 64                                    3...d
>> > HCI Event: Command Status (0x0f) plen 4
>>   0000: 00 01 01 04                                       ....
>> > HCI Event: Vendor (0xff) plen 7
>>     CSR: VM (channel 13)
>>     0000: 03 00 04 00 00 00                                 ......
>> > HCI Event: Vendor (0xff) plen 7
>>     CSR: VM (channel 13)
>>     0000: 03 00 04 00 00 00                                 ......
>> > HCI Event: Vendor (0xff) plen 7
>>     CSR: VM (channel 13)
>>     0000: 03 00 04 00 00 00                                 ......
>> > HCI Event: Vendor (0xff) plen 7
>>     CSR: VM (channel 13)
>>     0000: 03 00 04 00 00 00                                 ......
>> > HCI Event: Vendor (0xff) plen 7
>>     CSR: VM (channel 13)
>>     0000: 03 00 04 00 00 00                                 ......
>> > HCI Event: Vendor (0xff) plen 7
>>     CSR: VM (channel 13)
>>     0000: 03 00 04 00 00 00                                 ......
>> > HCI Event: Vendor (0xff) plen 7
>>     CSR: VM (channel 13)
>>     0000: 03 00 04 00 00 00                                 ......
>> > HCI Event: Vendor (0xff) plen 7
>>     CSR: VM (channel 13)
>>     0000: 03 00 04 00 00 00                                 ......
>> > HCI Event: Vendor (0xff) plen 7
>>     CSR: VM (channel 13)
>>     0000: 03 00 04 00 00 00                                 ......
>> > HCI Event: Vendor (0xff) plen 7
>>     CSR: VM (channel 13)
>>     0000: 03 00 04 00 00 00                                 ......
>> > HCI Event: Inquiry Complete (0x01) plen 1
>>   0000: 00                                                .
>
> this looks not good, because you shouldn't get any vendor events from
> your Bluetooth chip. Is Bluetooth working for you under Windows?
>
>> I can switch Bluetooth off and on. If I press the button I get
>>
>> < HCI Command: Reset (0x03|0x0003) plen 0
>> Receive failed: Broken pipe
>>
>> and in syslog
>>
>> Dec 12 08:44:57 localhost kernel: atkbd.c: Unknown key pressed
>> (translated
>> set 2, code 0x88 on isa0060/serio0).
>> Dec 12 08:44:57 localhost kernel: atkbd.c: Use 'setkeycodes e008
>> <keycode>' to make it known.
>> Dec 12 08:44:57 localhost kernel: usb 1-2: USB disconnect, address 6
>> Dec 12 08:44:57 localhost hcid[9862]: HCI dev 0 down
>> Dec 12 08:44:57 localhost hcid[9862]: Stoping security manager 0
>> Dec 12 08:44:57 localhost hcid[9862]: HCI dev 0 unregistered
>>
>> next time I get
>> Dec 12 08:46:06 localhost hcid[9862]: HCI dev 0 up
>> Dec 12 08:46:06 localhost hcid[9862]: Starting security manager 0
>> Dec 12 08:46:09 localhost usb.agent[25983]:      hci_usb: already loaded
>> Dec 12 08:46:09 localhost usb.agent[25988]:      hci_usb: already loaded
>> Dec 12 08:46:09 localhost usb.agent[25993]:      hci_usb: already loaded
>>
>> Look ok for me.
>
> This is exactly how it should be. The complete Bluetooth module is
> physically connected/disconnected from the USB bus.
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-12-12 10:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-11 22:07 [Bluez-users] "hciconfig -a" ok, but "hcitools scan" shows no devices Andreas Schrell
2004-12-11 22:41 ` Marcel Holtmann
2004-12-12  7:48   ` [Bluez-users] 'hciconfig -a' ok, but 'hcitools scan' " Andreas Schrell
2004-12-12  8:06     ` Marcel Holtmann
2004-12-12 10:38       ` Andreas Schrell [this message]
2004-12-12 11:42         ` [Bluez-users] SOLVED: Dell Inspiron 8600 was: " Marcel Holtmann
2004-12-13 17:17           ` Andreas Schrell
2004-12-13 20:01             ` Marcel Holtmann
2004-12-14  9:36               ` Andreas Schrell
2004-12-14  9:56                 ` Marcel Holtmann
2004-12-14 21:23                   ` Andreas Schrell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=33016.80.146.4.18.1102847912.squirrel@schrell.de \
    --to=as@schrell.de \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox