kudzu won't update modprobe.conf
lupus
de_lupus at pandora.be
Tue Nov 25 12:41:23 UTC 2003
I Quote man page kudzu:
When started, kudzu detects the current hardware, and checks it against
a database stored in /etc/sysconfig/hwconf, if one exists.
Only when no previous database exists, kudzu attempts to determine
what devices have already been configured, by looking at
/etc/modules.conf, /etc/sysconfig/network-scripts/, and
/etc/X11/XF86Config.
I install fedora core 1 with kernel 2.4.22 kudzu will generate
/etc/sysconfig/hwconf and find new hardware. Edits /etc/modules.conf.
When I install kernel 2.6 and start fedora core 1 kudzu will compare
hwconf against his probing and won't find new hardware. So
/etc/modprobe.conf won't get edited. But kernel 2.6 uses
/etc/modprobe.conf instead of /etc/modules.conf.
So my proposal is to generate hwconf when booting 2.4 and hwconf26 with
2.6. So kudzu will chance /etc/modprobe.conf when hwconf26 has changed
or does not exist.
Kristof Vansant
Op di 25-11-2003, om 04:15 schreef Bill Nottingham:
> lupus (de_lupus at pandora.be) said:
> > kernel 2.6 uses /etc/modprobe.conf
> > kernel 2.4 uses /etc/modules.conf
> >
> > I installed kernel 2.6-test9 next to my kernel 2.4.22 (fedora core 1),
> > but when I boot kernel 2.6 Kudzu won't edit modprobe.conf because
> > /etc/sysconfig/hwconf hasn't changed.
>
> It only updates the one for the running kernel.
>
> > Isn't it possible to use /etc/sysconfig/hwconf for 2.4.22 and
> > /sysconf/hwconf26 for kernel2.6, then kudzu can correctly detect
> > hardware and configure modprobe.conf and modules.conf depending on
> > what kernel I boot?
>
> That really doesn't make sense. The hwconf file doesn't
> change depending on which kernel you boot.
>
> > After I removed hwconf and booted with kernel 2.6 he configured
> > modprobe.conf correctly. But still my bttv and audio don't work.
> > Witch package/programme normally modprobes them?
>
> Normally, they should be loaded by opening the proper v4l devices;
> i.e., there's an alias for char-major-81, and then whatever app
> opens the device will cause it to get loaded.
>
> Bill
>
>
> --
> fedora-devel-list mailing list
> fedora-devel-list at redhat.com
> http://www.redhat.com/mailman/listinfo/fedora-devel-list
>
>
More information about the fedora-devel-list
mailing list