Opened 12 years ago

Closed 12 years ago

#3270 closed defect (fixed)

Section 8.3.2. Configuring Linux Module Load Order wrong

Reported by: bdubbs@… Owned by: bdubbs@…
Priority: normal Milestone: 7.3
Component: Book Version: SVN
Severity: normal Keywords:
Cc:

Description

We no longer use /etc/modprobe.d/

Change History (6)

comment:1 by bdubbs@…, 12 years ago

Owner: changed from Bruce Dubbs to bdubbs@…
Status: new → assigned

in reply to:  description ; comment:2 by Armin, 12 years ago

Replying to bdubbs@…:

We no longer use /etc/modprobe.d/

Huh? Did I miss something?

in reply to:  2 ; comment:3 by bdubbs@…, 12 years ago

Replying to Krejzi:

Replying to bdubbs@…:

We no longer use /etc/modprobe.d/

Huh? Did I miss something?

My mistake, but we need to clarify. /etc/modprobe.d/ is not used by the bootscripts for loading modules. That's either done automatically or by /etc/sysconfig/modules.

/etc/modprobe.d/ is used by the modprobe command and is still valid.

in reply to:  3 comment:4 by Armin, 12 years ago

Replying to bdubbs@…:

My mistake, but we need to clarify. /etc/modprobe.d/ is not used by the bootscripts for loading modules. That's either done automatically or by /etc/sysconfig/modules.

/etc/modprobe.d/ is used by the modprobe command and is still valid.

Makes sense now

comment:5 by Bryan Kadzban, 12 years ago

FYI the file we add to modprobe.d is actually only there for the automatic module loading.

If the USB1.1 host controller is modprobe'd before the USB2 host controller, then that rule ensures that the USB2 driver is actually loaded up first. (Which became required in some kernel or other that I can't recall anymore.) The rules should be used by kmod when udev invokes it for the USB1.1 host controller driver(s).

comment:6 by bdubbs@…, 12 years ago

Resolution: → fixed
Status: assigned → closed

Added additional explanation for /etc/modprobe.conf.

Fixed at revision 10094.

Note: See TracTickets for help on using tickets.