linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Bluetooth with Latitude X1
Date: Tue, 31 Jan 2006 19:21:32 +0100	[thread overview]
Message-ID: <1138731692.3968.5.camel@localhost.localdomain> (raw)
In-Reply-To: <200601310012.39402.arthur.breitman@gmail.com>

Hi Arthur,

> I already asked questions about this, without any success. I am retrying.
> Here are the informations.
> I have a Dell Latitude X1 Notebook. Bluetooth works flawlessly on windows and 
> is reported to work fine on this notebook on the internet.
> I believe I have installed and loaded all the necessary modules.
> 
> if I set my mobile phone in discovery mode and starts a scan on the laptop:
> 
> arthurb@coin:~$ sudo hcidump  -V -X
> HCI sniffer - Bluetooth packet analyzer ver 1.28
> device: hci0 snap_len: 1028 filter: 0xffffffff
> < HCI Command: Inquiry (0x01|0x0001) plen 5
>     lap 0x9e8b33 len 8 num 0
> > HCI Event: Command Status (0x0f) plen 4
>     Inquiry (0x01|0x0001) status 0x00 ncmd 1
> > HCI Event: Vendor (0xff) plen 7
>   0000: cd 03 00 04 00 00 00                              .......
> > HCI Event: Vendor (0xff) plen 7
>   0000: cd 03 00 04 00 00 00                              .......
> > HCI Event: Vendor (0xff) plen 7
>   0000: cd 03 00 04 00 00 00                              .......
> > HCI Event: Vendor (0xff) plen 7
>   0000: cd 03 00 04 00 00 00                              .......
> > HCI Event: Vendor (0xff) plen 7
>   0000: cd 03 00 04 00 00 00                              .......
> > HCI Event: Vendor (0xff) plen 7
>   0000: cd 03 00 04 00 00 00                              .......
> > HCI Event: Vendor (0xff) plen 7
>   0000: cd 03 00 04 00 00 00                              .......
> > HCI Event: Vendor (0xff) plen 7
>   0000: cd 03 00 04 00 00 00                              .......
> > HCI Event: Vendor (0xff) plen 7
>   0000: cd 03 00 04 00 00 00                              .......
> > HCI Event: Vendor (0xff) plen 7
>   0000: cd 03 00 04 00 00 00                              .......
> > HCI Event: Inquiry Complete (0x01) plen 1
>     status 0x00

since this is a CSR chip, call "hcidump -X -V -m 10" and see what it
tells you when you scan again.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2006-01-31 18:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-31  5:12 [Bluez-users] Bluetooth with Latitude X1 Arthur Breitman
2006-01-31 18:21 ` Marcel Holtmann [this message]
2006-02-04 21:07   ` Arthur Breitman
2006-02-07 11:13     ` Marcel Holtmann
2006-02-08 22:25       ` Arthur Breitman
2006-02-08 22:30         ` Marcel Holtmann
2006-02-11 23:06           ` Niv

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=1138731692.3968.5.camel@localhost.localdomain \
    --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;
as well as URLs for NNTP newsgroup(s).