Jerome Vizcaino wrote: > dh_installmodules is used to create postinst and postrm scripts for > debianized kernel modules. The problem is the following : > I'm running kernel 2.6.x and I'm building a bundle of two debian > packages (kernel-image-2.6.y and foobar-module for 2.6.y) > Install of both packages goes well but when I try to load the foobar > module after booting my new 2.6.y kernel, foobar is not known. The > problem comes from the update-modules script : update-modules only > updates the running kernel's modules.dep. In my case, 2.6.x modules.dep > got updated when installing the foobar-module package for 2.6.y. Looking > at the alsa-source, I found that they didn't use dh_installmodules at all > and wrote their own postinst and postrm template scripts to call depmod -a > using the associated System.map file (in my case System.map-2.6.y) and > specifying explicitly the kernel version (2.6.y). > depmod command looks like this : > depmod -A -F /boot/System.map-2.6.y 2.6.y > > By the way, I've only been testing with 2.6 kernels but I think the > problem is the same with the 2.4 series. > > Could you change how dh_installmodules behaves and generate postinst and > postrm scripts that takes this problem into account ?
Both module-init-tools and modutils have init scripts that run during boot and run depmod -a. The only way I can see that not working would be if /lib/modules were not writable. -- see shy jo
signature.asc
Description: Digital signature