From: Marcel Holtmann <marcel@holtmann.org>
To: "Nicholas A. Preyss" <nalp@gmx.net>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Problem with kernel-2.6.5
Date: Wed, 21 Apr 2004 21:22:18 +0200 [thread overview]
Message-ID: <1082575338.23959.59.camel@pegasus> (raw)
In-Reply-To: <20040421194424.GA26270@gmx.net>
Hi Nicholas,
> > give 2.6.6-rc2 a shot, because it includes the outstanding Bluetooth and
> > USB updates. If it still oopses report it on the USB mailing list.
>
> It should solve his problem, as it it possible too connect the dongle,
> when hci_usb already loaded. Unfortunately it seems to contain a bunch
> of new problems.
> You can't unplug the dongle or unload the hci_usb module anymore, without
> crashing the usb subsystem.
there are some outstanding USB patches. Report all problems to the USB
mailing list or try the 2.6.6-rc2-mmX if available.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&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:[~2004-04-21 19:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 3:27 [Bluez-users] Problem with kernel-2.6.5 Timothy Murphy
2004-04-21 12:32 ` Marcel Holtmann
2004-04-21 19:44 ` Nicholas A. Preyss
2004-04-21 19:22 ` Marcel Holtmann [this message]
2004-04-21 20:48 ` Timothy Murphy
2004-04-21 13:09 ` Nicholas A. Preyss
2004-04-23 7:17 ` Russell Neches
2004-04-23 7:23 ` Russell Neches
2004-04-23 7:29 ` Marcel Holtmann
2004-04-23 19:47 ` Russell Neches
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=1082575338.23959.59.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=nalp@gmx.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.