public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Max <spamhole@gmx.at>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Bluez and D-Link DBT-120
Date: Sun, 4 Apr 2004 21:46:57 +0200	[thread overview]
Message-ID: <20040404194656.GA15485@venus> (raw)
In-Reply-To: <1081105392.5533.4.camel@pegasus>

On Sun, Apr 04, 2004 at 09:03:13PM +0200, Marcel Holtmann wrote:

Hi,

> > Lucky me - I just updated to 2.6.5 today! :-) Here is the verbose output
> > of lspci (and further below the output of lsusb):
> 
> and you still get this error? Maybe this is a problem with your VIA UHCI
> host controller. Check the Linux USB mailing list for more details.

Yes, the problem is still the same with 2.6.5. What kind of things should
I look/ask for on the Linux USB mailinglist? Are there known problems
with VIA USB/Bluetooth?

Is there a way to verify that the firmware upload with bluefw was
successful?

Max



-------------------------------------------------------
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

  reply	other threads:[~2004-04-04 19:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-03 19:06 [Bluez-users] Bluez and D-Link DBT-120 Max
2004-04-04 10:09 ` Marcel Holtmann
2004-04-04 18:13   ` Max
2004-04-04 18:19     ` Marcel Holtmann
2004-04-04 18:33       ` Max
2004-04-04 19:03         ` Marcel Holtmann
2004-04-04 19:46           ` Max [this message]
2004-04-04 19:58             ` Marcel Holtmann

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=20040404194656.GA15485@venus \
    --to=spamhole@gmx.at \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    /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