public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Mohan K <kmohangda@gmail.com>
To: bluez-users@lists.sourceforge.net
Cc: digitalfredy@debiancolombia.org
Subject: Re: [Bluez-users] Bluetooth dongle not working under extendedUSB2.0 host
Date: Fri, 5 Aug 2005 11:30:51 +0530	[thread overview]
Message-ID: <7aa80ced05080423005e4e8a78@mail.gmail.com> (raw)
In-Reply-To: <1123166702.3903.4.camel@localhost.localdomain>

Hi Fredy,

Thankyou for your mail.=20

There are two hcid drivers, i)uhci_hcd ii)ehci_hcd, right? I removed
ehcid_hcd module using "rmmod ehcid_hcd". Now its working.

I can't understand what is happening!:-( Can u tell me why this is happenin=
g?

Thanks & Regards,
Mohan



On 8/4/05, Fredy P <digitalfredy@debiancolombia.org> wrote:
> El mi=E9, 03-08-2005 a las 14:14 +0530, Mohan K escribi=F3:
> > Hi All,
> > We are using a VIA mother board with FC3(kernel2.6.12) installed.  We
> > have extended one of the USB port using a USB controller.
> > When I plugged a mouse it is working fine. But if I plug and use a
> > bluetooth dongle it is not working. The kernel is detecting the USB.
> > I tried to use "hcitool scan",but it fails with an error message "No
> > route to host".
> >
> > Can anyone tell me why this is happening? Advanced thanks for your sugg=
estions.
>=20
> try restart the hotplug
> in debian is:
> /etc/init.d/hotplug restart
> >
> > Thanks & Regards,
> > Mohan
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > informative Webcasts and more! Get everything you need to get up to
> > speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&op=3Dclick
> > _______________________________________________
> > Bluez-users mailing list
> > Bluez-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bluez-users
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practic=
es
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & Q=
A
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2005-08-05  6:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-03  8:44 [Bluez-users] Bluetooth dongle not working under extended USB2.0 host Mohan K
2005-08-03  9:17 ` [Bluez-users] " Mohan K
2005-08-04 14:45 ` [Bluez-users] Bluetooth dongle not working under extendedUSB2.0 host Fredy P
2005-08-05  6:00   ` Mohan K [this message]

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=7aa80ced05080423005e4e8a78@mail.gmail.com \
    --to=kmohangda@gmail.com \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=digitalfredy@debiancolombia.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