From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] "hciconfig -a" ok, but "hcitools scan" shows no devices
Date: Sat, 11 Dec 2004 23:41:01 +0100 [thread overview]
Message-ID: <1102804861.8750.2.camel@pegasus> (raw)
In-Reply-To: <35275.80.146.4.18.1102802831.squirrel@schrell.de>
Hi Andreas,
> I am new on this list with the following problem:
>
> "hciconfig -a" shows
>
> hci0: Type: USB
> BD Address: 00:10:C6:3A:B5:70 ACL MTU: 192:8 SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN
> RX bytes:4187 acl:0 sco:0 events:370 errors:0
> TX bytes:1902 acl:0 sco:0 commands:72 errors:0
> Features: 0xff 0xff 0x8f 0x78 0x18 0x18 0x00 0x80
> Packet type: DM1 DH1 HV1
> Link policy: RSWITCH HOLD SNIFF PARK
> Link mode: SLAVE ACCEPT
> Name: 'delli-0'
> Class: 0x000100
> Service Classes: Unspecified
> Device Class: Computer, Uncategorized
> HCI Ver: 1.2 (0x2) HCI Rev: 0x4f2 LMP Ver: 1.2 (0x2) LMP Subver:
> 0x4f2
> Manufacturer: Cambridge Silicon Radio (10)
>
> "hcitools scan" or "hcitools inq" only show scanning but no device.
>
> Kernel versions tested where 2.6.8.1 and 2.6.10-rc3 and the following
> debian packages
>
> ii bluez-firmware 1.0-2
> ii bluez-hcidump 1.12-1
> ii bluez-pcmcia-support 2.10-5
> ii bluez-pin 0.24-1
> ii bluez-utils 2.10-5
>
> dmesg:Bluetooth: Core ver 2.7
> Bluetooth: HCI device and connection manager initialized
> Bluetooth: HCI socket layer initialized
> Bluetooth: HCI USB driver ver 2.7
> Bluetooth: L2CAP ver 2.6
> Bluetooth: L2CAP socket layer initialized
> Bluetooth: RFCOMM ver 1.3
> Bluetooth: RFCOMM socket layer initialized
> Bluetooth: RFCOMM TTY layer initialized
>
> Tested also with --length=30, --flush
>
> System is a Dell 8600 and a Siemens S65 mobile.
so this is the original firmware in the Bluetooth chip? You haven't
flashed it? Is there a wireless switch on that machine? Maybe you need
to activate the antenna.
Please show us "/proc/bus/usb/devices" and what "hcidump -X" showing.
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
next prev parent reply other threads:[~2004-12-11 22:41 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 [this message]
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 ` [Bluez-users] SOLVED: Dell Inspiron 8600 was: " Andreas Schrell
2004-12-12 11:42 ` 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=1102804861.8750.2.camel@pegasus \
--to=marcel@holtmann.org \
--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