Package: nvidia-kernel Severity: normal Tags: patch Is there any reason for nvidia-kernel-xxx not to depend (but just recommend) linux-image-xxx?
The problem we ran into with an automatic (FAI) install is that without that dependency, nvidia-kernel may get configured before kernel-image. But this then failes since there's no /lib/modules/xxx directory at that point. So you end up with /lib/modules/xxx_nnn (with nnn presumably the process id of the failed counfiguration) and nvidia.ko in there. Adding the dependency (here with a change from linux-image to kernel-image) to control.template seems to fix the problem: < Depends: nvidia-kernel-common (>= 20051028+1-0.1) < Recommends: linux-image-#KVERS# > Depends: nvidia-kernel-common (>= 20051028+1-0.1), > kernel-image-#KVERS# -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.18.2.mib.smp.amd64 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
