based on my reading, the new kernel prefers to read from the file /etc/modprobe.conf, rather than the older /etc/modules.conf.
to help in the migration, there is the utility "generate-modprobe.conf", but in this situation, it doesn't work -- it fails complaining of a missing "modprobe.old".
i'm suspecting that generate-modprobe.conf was written with the assumption that one would have upgraded separately to the newer version of modutils, which was backwards compatible and, IIRC, moved the older versions of the module commands to their corresponding ".old" names.
this is, i'm guessing, what generate-modprobe.conf is looking for, but severn, since it comes with the newer version of modutils already, has no such ".old" backups. hence the failure.
thoughts?
rday
Le jeu 31/07/2003 à 12:57, Robert P. J. Day a écrit :
based on my reading, the new kernel prefers to read from the file /etc/modprobe.conf, rather than the older /etc/modules.conf.
to help in the migration, there is the utility "generate-modprobe.conf", but in this situation, it doesn't work -- it fails complaining of a missing "modprobe.old".
i'm suspecting that generate-modprobe.conf was written with the assumption that one would have upgraded separately to the newer version of modutils, which was backwards compatible and, IIRC, moved the older versions of the module commands to their corresponding ".old" names.
this is, i'm guessing, what generate-modprobe.conf is looking for, but severn, since it comes with the newer version of modutils already, has no such ".old" backups. hence the failure.
thoughts?
Try to copy modprobe from RH9 to modprobe.old.
rday
-- Rhl-beta-list mailing list Rhl-beta-list@redhat.com http://www.redhat.com/mailman/listinfo/rhl-beta-list
On 31 Jul 2003, Féliciano Matias wrote:
Le jeu 31/07/2003 à 12:57, Robert P. J. Day a écrit :
based on my reading, the new kernel prefers to read from the file /etc/modprobe.conf, rather than the older /etc/modules.conf.
to help in the migration, there is the utility "generate-modprobe.conf", but in this situation, it doesn't work -- it fails complaining of a missing "modprobe.old".
i'm suspecting that generate-modprobe.conf was written with the assumption that one would have upgraded separately to the newer version of modutils, which was backwards compatible and, IIRC, moved the older versions of the module commands to their corresponding ".old" names.
this is, i'm guessing, what generate-modprobe.conf is looking for, but severn, since it comes with the newer version of modutils already, has no such ".old" backups. hence the failure.
thoughts?
Try to copy modprobe from RH9 to modprobe.old.
i suspect that would work fine, but it doesn't help someone testing a severn box who doesn't have access to any RH 9 rpms.
is there a usable way to run this under the circumstances, or should i bugzilla this?
rday
Robert P. J. Day (rpjday@mindspring.com) said:
based on my reading, the new kernel prefers to read from the file /etc/modprobe.conf, rather than the older /etc/modules.conf.
to help in the migration, there is the utility "generate-modprobe.conf", but in this situation, it doesn't work -- it fails complaining of a missing "modprobe.old".
A new modprobe.conf should be generated on the first upgrade to 2.6 capable modutils, with the contents of whatever's in modules.conf at the time. Changes aren't kept in sync back and forth, however.
Bill
On Thu, 31 Jul 2003, Bill Nottingham wrote:
Robert P. J. Day (rpjday@mindspring.com) said:
based on my reading, the new kernel prefers to read from the file /etc/modprobe.conf, rather than the older /etc/modules.conf.
to help in the migration, there is the utility "generate-modprobe.conf", but in this situation, it doesn't work -- it fails complaining of a missing "modprobe.old".
A new modprobe.conf should be generated on the first upgrade to 2.6 capable modutils, with the contents of whatever's in modules.conf at the time. Changes aren't kept in sync back and forth, however.
but in what way does this help when one starts with a fresh install of severn, *then* upgrades to a 2.6.x kernel? that doesn't involve a modutils upgrade since the new modutils are there from the beginning in severn, no?
at the moment, on my system -- severn + kernel 2.6.0-test2 -- i have an informative, 7-line /etc/modules.conf file, which contains information about my nvidia card, my orinoco wireless driver and a few other things. in other words, it's valuable information.
i also have a lengthy /etc/modprobe.conf.dist full of utterly generic info. i want to, if it's possible, automatically generate a new modprobe.conf based on the older info from modules.conf.
at the moment, i don't see a way to do that since the one utility that might have helped, /sbin/generate-modprobe.conf (sp?), is adamant about finding an *old* modprobe version, otherwise it chokes and dies. and there *is* no older version on severn.
i'm not asking for changes to be kept in sync back and forth. i want to go forward just once. and it appears that there's no obvious way to do that.
rday
p.s. am i making any sense? or am i just embarrassing myself as usual?
Robert P. J. Day (rpjday@mindspring.com) said:
but in what way does this help when one starts with a fresh install of severn, *then* upgrades to a 2.6.x kernel? that doesn't involve a modutils upgrade since the new modutils are there from the beginning in severn, no?
Correct. If you need to re-run it:
echo "include /etc/modprobe.conf.dist" > /etc/modprobe.conf /sbin/generate-modprobe.conf --stdin < /etc/modules.conf >> /etc/modprobe.conf
I'll look at a better way to handle this.
i also have a lengthy /etc/modprobe.conf.dist full of utterly generic info.
Yes. modutils for 2.4 has built-in aliases for most of the common protocols & devices. module-init-tools for 2.6 does not have this info, ergo, the required table.
Bill
-
Bill Nottingham -
Féliciano Matias -
Robert P. J. Day