From: Greg KH <greg@kroah.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.31-rc0-git: lsusb stopped working?
Date: Sat, 11 Jul 2009 17:25:36 -0700 [thread overview]
Message-ID: <20090712002536.GC9308@kroah.com> (raw)
In-Reply-To: <20090710161336.GA1350@ucw.cz>
On Fri, Jul 10, 2009 at 06:13:37PM +0200, Pavel Machek wrote:
> Hi!
> > > > >
> > > > > On thinkpad x60. Otherwise usb seems to work, including btusb dongle.
> > > > >
> > > > > /proc/bus/usb does not seem to exists.
> > > >
> > > > Newer (as in the past 2 years) versions of lsusb should not need
> > > > /proc/bus/usb/
> > > >
> > > > What version of usbutils are you using?
> > >
> > > root@amd:/home/pavel# lsusb --version
> > > lsusb (usbutils) 0.73
> > > root@amd:/home/pavel#
> > >
> > > I may have done something stupid with not runing udev and linking
> > > /proc/bus/usb to /dev, instead...
> >
> > the opensuse FACTORY tree now has a more modern version of usbutils in
> > it, which works just fine without usbfs mounted.
>
> Well, this is heavily hacked debian :-)
Take it up with the Debian maintainers then, there are newer usbutils
packages availble somewhere...
> > > But it is not only usbutils that is broken, I first noticed breakage
> > > on android fastboot.
> >
> > Android needs it? That's crazy, given that they don't have any usb host
> > controllers in their devices. Very wierd...
>
> fastboot runs on PC and uploads kernels to Android device(s).
Oh, that program. That sounds like a Debian configuration issue.
good luck,
greg k-h
next prev parent reply other threads:[~2009-07-12 0:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 13:55 2.6.31-rc0-git: lsusb stopped working? Pavel Machek
2009-06-23 15:01 ` Greg KH
2009-06-23 15:01 ` Greg KH
2009-07-11 9:10 ` Pavel Machek
2009-07-11 17:43 ` Greg KH
2009-07-10 16:13 ` Pavel Machek
2009-07-12 0:25 ` Greg KH [this message]
2009-06-23 15:09 ` Frans Pop
2009-06-23 16:13 ` Greg KH
2009-06-23 20:35 ` Olivier Galibert
2009-06-23 20:37 ` Pavel Machek
2009-06-23 20:57 ` Greg KH
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=20090712002536.GC9308@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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