From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] dongles won't initialize
Date: Wed, 13 Apr 2005 22:51:23 +0200 [thread overview]
Message-ID: <1113425483.15359.2.camel@pegasus> (raw)
In-Reply-To: <425D8196.2090608@gmx.ch>
Hi Marco,
> maybe someone has an idea:
>
> On my PC, I have:
> Kernel 2.6.8-24.14-default
> bluez-utils and bluez-libs 2.15
>
> this is exactly the same setup as on my laptop where everything works
> perfectly fine.
> the same dongle(s) used in the laptop refuse to work with the pc.
>
> I made several (>20) tries with reboot and hcid reload.
> hcitool dev and hciconfig -a:
> - mostly showed nothing (no devices)
> - about two times showed the dongles correctly but hciconfig -a failed with
> a timeout (hciconfig hci0 revision as well)
> - once, the dongle wasn't up. doing hciconfig hci0 up freezed
> - lsusb [-b] freezed
> - dmesg, /var/log/messages didn't get any entries
>
> I strongly assume this has something to to with the usb port. maybee it's
> broken or i'm missing something important (software)...
try to use a 2.6.12-rc2 kernel.
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-04-13 20:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 20:31 [Bluez-users] dongles won't initialize Marco Trudel
2005-04-13 20:51 ` Marcel Holtmann [this message]
2005-04-14 15:00 ` Marco Trudel
2005-04-14 15:59 ` Marcel Holtmann
2005-04-14 20:35 ` Marco Trudel
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=1113425483.15359.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