PDA

View Full Version : FC2 modprobe.conf & modules.conf


lvanek
9th July 2004, 02:16 PM
Greetings -

I have completed an upgrade from RH9 to FC2. After several trials & tribulations I have a mostly working system.

I note that I have two module configuration files after the upgrade:

/etc/modprobe.conf (I assume this is new for FC2)
/etc/modules.conf (I assume this is residue from RH9)

I find this statement has been entered into the old /etc/modules.conf file:

# Note: for use under 2.6, changes must also be made to modprobe.conf!

Does this mean I need both files for FC2? Are both used? what does modprobe do in this case?
I have eth0 & eth1 NICs defined in both.

Thanks in advance.

Darkmage
9th July 2004, 04:00 PM
/etc/modules.conf has been phased out for FC2, only /etc/modprobe.conf is used. I will suggest editing the /etc/modules file and but a comment (#) on all entries, save it and restart. Then check if anything breaks :D

lvanek
10th July 2004, 02:24 AM

Thanks for the advice, however, this system is loading modules only defined in modules.conf.

I will try your advice to see what breaks.

mhelios
10th July 2004, 02:38 AM
There is a tool that can (try) to convert between the older /etc/modules.conf and the new /etc/modprobe.conf format. Run /sbin/generate-modprobe.conf as root. See man modprobe.conf for more info. Don't trust it religiously though, it's early code yet.

lvanek
10th July 2004, 07:32 AM
Thanks for the help.

Any thoughts as to impact on having eth0 & eth1 aliases in both files? Might explain strange kudzu behavior before I disabled it.

mhelios
10th July 2004, 05:24 PM
Not sure whether both files are used once you've converted to modprobe.conf format. I would suggest either renaming /etc/modules.conf after you've a working modprobe.conf or at least commenting out the ethx aliases in modules.conf. Then you can test that things still work fine w/o module.conf. Here's my modprobe.conf in case it helps you:

alias eth0 8139too
alias eth1 8139too
# turn IPv6 support off
alias net-pf-10 off
alias ipv6 off

Mine's simple as I don't have a soundcard etc.

lvanek
10th July 2004, 07:20 PM
Thanks again.

My /etc/modprobe.conf file looks like this:

=====================

alias usb-controller ehci-hcd
alias usb-controller1 uhci-hcd

alias snd-card-0 snd-emu10k1
alias snd-card-1 cmpci
alias char-major-195* nvidia

alias char-major-89-* i2c-dev

alias eth1 tulip
alias eth0 3c59x

alias net-pf-10 off

=====================

The old modules.conf file is completely commented out. System boots ok, NIC's both recognized, seems
more predictable than before.

Only remaining issue is to get ipt_MASQUERADE to load on boot. I have to modprobe for it after boot. modprobe.conf file does not like an alias for that module for some reason.

mhelios
11th July 2004, 03:44 PM
Only remaining issue is to get ipt_MASQUERADE to load on boot. I have to modprobe for it after boot. modprobe.conf file does not like an alias for that module for some reason.
Any iptables module needed should automagically be loaded after the rules are parsed and loaded. FOr example adding this line would trigger ipt_MASQUERADE to load on save:

logger -t iptables Turning on NAT
# masquerade from internal network
/sbin/iptables -t nat -A POSTROUTING -s ${lannet} -o ${IFext} -j MASQUERADE

Then do:
service iptables save
service iptables restart

Here's part of my lsmod output for your reference:

ipt_MASQUERADE 2560 1
ipt_state 1536 3
ipt_REJECT 4736 2
ipt_LOG 5120 7
ipt_limit 1792 4
iptable_nat 17708 2 ipt_MASQUERADE
ip_conntrack 24968 3 ipt_MASQUERADE,ipt_state,iptable_nat
iptable_mangle 2176 0
iptable_filter 2176 1
ip_tables 14208 8 ipt_MASQUERADE,ipt_state,ipt_REJECT,ipt_LOG,ipt_li mit,iptable_nat,iptable_mangle,iptable_filter

For future reference, please start a new thread for a new question.

foolish
12th July 2004, 09:46 AM
In Core 2 you're using a 2.6 kernel, the 2.6 kernel uses a modprobe.conf and a modprobe.conf.dist file. The 2.4 kernel will use modules.conf

You edit /etc/modprobe.conf if you have to edit anything. modprobe.conf.dist is simply modules that don't depend on any specific hardware and we all may need those. Like the OSS emulation for ALSA drivers, the driver itself is in modprobe.conf, the OSS emulation and other extras that are the same with every sound card, are in modprobe.dist.