From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] No working Bluetooth adapter found
Date: Sun, 27 Mar 2005 17:23:38 +0200 [thread overview]
Message-ID: <1111937018.9195.224.camel@pegasus> (raw)
In-Reply-To: <200503271708.10663.tmp@nitwit.de>
Hi Timo,
> I currently run SuSE 9.2 and have a MSI PC2PC USB bluetooth dongle and it
> doesn't work: No working bluetooth adapter found. This is the log when I plug
>
> Mar 27 16:47:09 tcn kernel: usb 1-4: new full speed USB device using address 7
> Mar 27 16:47:10 tcn hcid[24373]: HCI dev 0 registered
> Mar 27 16:47:13 tcn kernel: hci_cmd_task: hci0 command tx timeout
> Mar 27 16:47:18 tcn sdpd[24748]: init_server: binding L2CAP socket: Address
> already in use
> Mar 27 16:47:18 tcn sdpd[24748]: main: Server initialization failed
> Mar 27 16:47:18 tcn opd[24752]: OBEX Push Daemon - version 0.2 started
> Mar 27 16:47:18 tcn opd[24752]: OBEX Object Push service registered with sdpd
> Mar 27 16:47:18 tcn opd[24752]: Failed to register BtOBEX server on RFCOMM
> channel 10. (-1 / 98)
>
> Hmm. So I switched to channel 9.
>
> Mar 27 17:05:43 tcn kernel: hci_cmd_task: hci0 command tx timeout
> Mar 27 17:05:49 tcn kernel: usb 1-4: USB disconnect, address 7
> Mar 27 17:05:49 tcn hcid[28768]: HCI dev 0 unregistered
> Mar 27 17:05:49 tcn /sbin/hotplug[28997]: unknown command
> Mar 27 17:05:49 tcn /sbin/hotplug[28999]: unknown command
> Mar 27 17:05:49 tcn /sbin/hotplug[28996]: unknown command
> Mar 27 17:05:49 tcn /sbin/hotplug[28998]: unknown command
> Mar 27 17:05:57 tcn kernel: ohci_hcd 0000:00:02.1: wakeup
> Mar 27 17:05:58 tcn kernel: usb 2-4: new full speed USB device using address 3
> Mar 27 17:05:58 tcn hcid[28768]: HCI dev 0 registered
> Mar 27 17:06:01 tcn kernel: hci_cmd_task: hci0 command tx timeout
> Mar 27 17:06:06 tcn sdpd[29323]: init_server: binding L2CAP socket: Address
> already in use
> Mar 27 17:06:06 tcn sdpd[29323]: main: Server initialization failed
> Mar 27 17:06:06 tcn opd[29327]: OBEX Push Daemon - version 0.2 started
> Mar 27 17:06:06 tcn opd[29327]: OBEX Object Push service registered with sdpd
> Mar 27 17:06:06 tcn opd[29327]: Failed to register BtOBEX server on RFCOMM
> channel 9. (-1 / 98)
> Mar 27 17:06:35 tcn kernel: hci_cmd_task: hci0 command tx timeout
>
> Does somebody have a clue on this?
what does "/proc/bus/usb/devices" contain?
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-03-27 15:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-27 15:08 [Bluez-users] No working Bluetooth adapter found tmp
2005-03-27 15:23 ` Marcel Holtmann [this message]
2005-03-27 15:32 ` tmp
2005-03-27 15:38 ` Marcel Holtmann
2005-03-27 16:04 ` tmp
2005-03-27 16:07 ` Marcel Holtmann
2005-03-27 16:12 ` tmp
2005-03-27 16:59 ` Marcel Holtmann
2005-03-27 17:06 ` tmp
2005-03-27 17:11 ` Marcel Holtmann
2005-03-27 17:25 ` tmp
2005-03-28 8:27 ` tmp
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=1111937018.9195.224.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.