From: "William Knop" <w_knop@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Modules and DevFS
Date: Wed, 31 Jan 2001 16:34:53 -0500 [thread overview]
Message-ID: <F148MamEWkeMEwuwi7N000015ef@hotmail.com> (raw)
I decided recently to go bleeding-edge on one of my Linux boxes and
discovered I had a problem with module loading while using DevFS.
Correct me if I'm wrong, but DevFS only makes /dev entries when a device is
present, and the device is not present until the module is loaded. So if I
want to access /dev/hda and the IDE module has not been loaded yet, I will
get a message telling me the device doesn't exist or some such instead of
autoloading the module and being happy. Same goes for hotswap devices,
right? I boot directly into X and have to crash out (otherwise it
continually tries to unsuccessfully load X) so I could enable my USB mouse
and various other devices.
I realize modularizing the entire IDE subsystem is not really good anyway,
because every time it reloads it will rescan the bus... But what about USB?
Suppose I don't have any IDE or USB devices, but want support so I can use
them later. Especially in the case of USB, plugability is a must for desktop
"home" systems.
I also have enabled the "module autoload" feature of DevFS, which
conveniently autoloads my 3c59x driver. :)
Does the kernel only autoload modules through userspace request, or can a
hardware request cause loading? For instance, inserting a USB peripheral
would cause the USB chipset to signal the OS. So therefore the OS can update
its device tables and unload the module again when it becomes inactive. This
goes for all hot-swap devices, IMHO.
I read all the FAQs and stuff and found nothing that really addresses this,
so here I ask if anyone has any idea as to a solution. No doubt I screwed
something up somewhere along the line... If my kernel or XF86 config files
are needed, I can pull 'em up and post 'em. Also, please CC responses to me
because I'm not currently subscribed.
Thanks a bunch,
Will
Box info:
Linux 2.4.1
Abit M/B
P3 550
256MB RAM
AGP Devices:
Nvidia TNT2 AGP display card
PCI Devices:
S3Virge/VX display card
Adaptec 3940UW SCSI card
3Com "Boomerang" ethernet card
ISA Devices:
SB AWE 64 Gold ISA sound card
IDE Drives:
2 CDROM drives
SCSI Drives:
4.5 GB UW drive
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-31 21:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 21:34 William Knop [this message]
2001-01-30 22:20 ` Michael B. Trausch
2001-01-31 22:05 ` Brian May
2001-02-01 10:31 ` Helge Hafting
2001-02-01 8:44 William Knop
2001-01-31 22:56 ` Michael B. Trausch
2001-02-02 10:35 ` Helge Hafting
2001-02-02 20:00 ` Michael B. Trausch
2001-02-05 10:36 ` Helge Hafting
2001-02-02 20:33 ` Georg Nikodym
2001-02-01 10:23 ` Peter Samuelson
2001-02-01 15:22 ` John Jasen
2001-02-01 16:13 ` Georg Nikodym
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=F148MamEWkeMEwuwi7N000015ef@hotmail.com \
--to=w_knop@hotmail.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
all inboxes | Powered by JetHome®