Bug 150542 - rc.sysinit runs kmodule before mounting /usr
Summary: rc.sysinit runs kmodule before mounting /usr
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts (Show other bugs)
(Show other bugs)
Version: 3
Hardware: All Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2005-03-08 04:17 UTC by Lev Iserovich
Modified: 2014-03-17 02:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-03-08 05:29:58 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Lev Iserovich 2005-03-08 04:17:30 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.3; Linux) (KHTML, like Gecko)

Description of problem:
rc.sysinit runs kmodule and and attempts to load modules for all hardware in the system.
The problem is that at that point, no filesystems from /etc/fstab are mounted, specifically /usr.
kmodule needs files in /usr/share/hwdata, which are not visible yet.
So kmodule does not detect almost any devices (since it can't read any hardware data descriptions).
module insertion should either be moved after /usr is mounted, or devices should be re-scanned after mounting /usr or something to this effect.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create a system where /usr is on a separate partition or drive
2. Have some hardware that kmodule needs definitions for - usually PCI cards - a SoundBlaster Live! in my case.

Actual Results:  The module for the PCI device in question (SBLive in my case - snd-emu10k1) is not loaded until I load it manually.

Expected Results:  Module should be loaded automatically.

Additional info:

Comment 1 Bill Nottingham 2005-03-08 05:29:58 UTC
See bug 150123. It's fixed in 1.1.110-1.

Note You need to log in before you can comment on or make changes to this bug.