Description of problem:
/etc/modprobe.conf does not exist.
Our understanding is that the file is deprecated. Is this correct?
On RHEL4 and 5, you can specify the order of kernel modules loading, for
example, by writing "alias host_scsiadapter xxx" in modprobe.conf.
Is there any other means to do this on RHEL6?
Version-Release number of selected component:
Red Hat Enterprise Linux Version Number: RHEL6
Release Number: 6.0 beta
Kernel Version: 2.6.32-19.el6
Related Package Version: module-init-tools-3.9-5.el6.x86_64
Related Middleware / Application: N/A
Drivers or hardware or architecture dependency:
Step to Reproduce:
1. Boot RHEL6.0 beta system.
2. ls /etc/modprobe.conf
- Model: PRIMERGY BX620S4
- CPU Info: Intel Xeon X5470
- Memory Info: 2GB
Taking a quick look at how the kernel and udev work together,
on RHEL6.0 beta, to detect/probe devices and assign device node name
to them, it seems to me that there is no other means to specify the
order of kernel modules loading.
On RHEL6, dracut is introduced instead of mkinitrd, then users will have
to understand some difference with them to manage their systems.
So, customer requests some documents about this. I think we need to
provide the following information, at least.
- changing package mkinitrd to dracut
(this information has been in release notes and migration guide)
- there isn't /etc/modprobe.conf by default
- needing to add kernel parameter 'rdloaddriver' to order module loading instead of 'scsi_hostadapter'
- loading all drivers to initramfs by default
As long as I checked internal/external RHEL6 beta documents, I could not
find like that. So, can we publish like the above information for
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
/etc/modprobe.conf is still read, if the user creates it. (In RHEL 6, that is. It may go away in RHEL 7.) The user can also create a file under /etc/modprobe.d, with the same syntax. (This is more future-compatible.)
Wouldn't this be more appropriate for the Migration Guide?
Could be, the idea here is to check all RHEL 6 docs about the changes listed in the summary.
Can you please assess this for Migration Guide/other guides? Cheers, - Mike
The Installation Guide doesn't ask users to do anything with modprobe.conf at all, so I think this is out of scope for that guide.
However, I reviewed the Installation Guide for any references to mkinitrd, modprobe.conf, scsi_hostadapter, or loading drivers to initramfs.
The only reference to any of these was a reference to mkinitrd in "25.3.4. Configuring a System z Network Device for Network Root File System", mentioned only in the context of Dracut anyway: "Dracut (the mkinitrd successor that provides the functionality in the initramfs that in turn replaces initrd) provides a boot parameter to activate network devices on System z early in the boot process"
I'm therefore changing the component to the Deployment Guide -- Dracut is discussed in section "29.5. Verifying the Initial RAM Disk Image" of that book.
However, please feel free to re-open against the Installation Guide if there's a specific place in the Installation Guide where you feel this should be mentioned.
Notes have been now been added to the Migration Guide about these changes.
I was aware of this change, though I just got rid of the last two lingering references to modprobe.conf (except to mention it as deprecated) in the channel bonding sections of the Network Interfaces and General Parameters chapters.
commit dd6a4c3 - GenParams, NetInterfaces: mk DG modprobe.conf-clean
→ Fix BZ#594479: make final chgs to bonding sections to instruct in modprobe.d/ use; only mention modprobe.conf as deprecated
Othewise the Deployment Guide is modprobe.conf clean. I will CC Don so as to pass this hot potato 'round.
Harald Hoyer has provided me with the rdloaddriver and module-loading specifics, so I'll be updating the General Parameters and Modules chapter with that information. Because of the nearness of the deadline, this will not make it into the beta 2 Deployment Guide release.