From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: 8/16bit usb minor device number problem
Date: Wed, 27 Sep 2006 15:22:54 +0000 [thread overview]
Message-ID: <20060927152254.GA13967@kroah.com> (raw)
In-Reply-To: <451A4559.80109@ciphirelabs.com>
On Wed, Sep 27, 2006 at 11:33:13AM +0200, Andreas Jellinghaus wrote:
> I have the minor number of usb devices in /dev/bus/usb trunkated.
> where do I look for debugging this problem? kernel? filesystem code?
> udev? glibc? something else?
>
> foo:/dev/bus/usb/003# ls -l
> total 0
> crw-rw-r-- 1 root root 189, 0 Sep 26 11:52 001
> crw-rw-r-- 1 root root 189, 1 Sep 26 11:52 002
> foo:/dev/bus/usb/003# cat /sys/class/usb_device/usbdev3.2/dev
> 189:257
> foo:/dev/bus/usb/003#
This is probably a glibc issue. Can you manually create a device node
with a minor of 257?
What version of glibc are you using?
thanks,
greg k-h
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2006-09-27 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 9:33 8/16bit usb minor device number problem Andreas Jellinghaus
2006-09-27 15:22 ` Greg KH [this message]
2006-09-27 16:03 ` Andreas Jellinghaus
2006-09-27 17:17 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2006-09-27 9:00 Andreas Jellinghaus
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=20060927152254.GA13967@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.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 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.