On Wednesday 19 April 2006 01:42, Digby Tarvin wrote: > But the modprobe.d method doesn't work on my system for installation or > post installation, and I think there is a good chance the two issues > are be related.
This is the code that parses the option you pass as a kernel option:
if [ -n "$PARAMS" ] && [ "$TYPE" = options ]; then
for file in /etc/modules.conf /etc/modprobe.conf; do
if [ -e "$file" ]; then
grep -v "$MODULE " $file > $file.new
mv $file.new $file
else
touch $file
fi
echo "options $MODULE $PARAMS" >> $file
done
fi
In other words: it creates a /etc/modprobe.conf and /etc/modules.conf.
IIRC modules.conf is only for 2.4 kernels, so that leaves modprobe.conf.
Hmm. Actually, I think I've read that modprobe.conf overrules anything
that is in /etc/modprobe.d...
Could you check if that is the case if you use the second method? Is there
a file (maybe empty) /etc/modprobe.conf that could overrule what you've
manually put in /etc/modprobe.d/libata?
Could that also be the case on the installed system?
pgpi8FrrAT7mL.pgp
Description: PGP signature
