public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Erdfelt <johannes@erdfelt.com>
To: "Daniel I. Applebaum" <danapple@danapple.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: built-in USB /proc bug
Date: Tue, 20 Nov 2001 13:37:35 -0500	[thread overview]
Message-ID: <20011120133735.A32355@sventech.com> (raw)
In-Reply-To: <200111201750.fAKHoYa03354@danapple.com>
In-Reply-To: <200111201750.fAKHoYa03354@danapple.com>; from danapple@danapple.com on Tue, Nov 20, 2001 at 11:50:34AM -0600

On Tue, Nov 20, 2001, Daniel I. Applebaum <danapple@danapple.com> wrote:
> 
> I tried building a 2.4.13 kernel with USB support as built-in, instead
> of modules.  The system worked, and USB devices worked, but there were
> no entries in /proc/bus/usb Yes, I had enabled both /proc filesystem
> and USB /proc filesystem support.  When the same kernel was built but
> with USB support as modules, the /proc/bus/usb entries appear.
> 
> Although no expert in these matters, I suspect that when the USB
> subsystem is built-in, it is initialized before /proc is mounted, and
> the USB /proc filesystem support either turns itself off or puts the
> "files" elsewhere.
> 
> A viable solution might be to have make menuconfig warn against this
> combination.

The problem is likely that it's a filesystem and you need to mount it
after loading the module.

Try running:

mount /proc/bus/usb

JE


      reply	other threads:[~2001-11-20 18:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-20 17:50 built-in USB /proc bug Daniel I. Applebaum
2001-11-20 18:37 ` Johannes Erdfelt [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=20011120133735.A32355@sventech.com \
    --to=johannes@erdfelt.com \
    --cc=danapple@danapple.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox