Hello,
as there is no response from you by now, I would like to ask, if I can do
something to help you in investigating my problem?
According to the upstream bug I filed, the error seems to occur because of the
order the modules are built.
How can the order of compiling modules can be set? Could you look into it to
support upstream!?
Thanks!
Hello,
after just updating my kernel, I searched for log-files again and I found one
in /var/lib/dkms/vboxnetflt/kernel-2.6.32-7.slh.3-sidux-686-i686/log/make.log:
DKMS make.log for vboxnetflt-3.1.4_BETA1 for kernel 2.6.32-7.slh.3-sidux-686
(i686)
Do 4. Feb 00:00:25 CET 2010
make:
For the first: I hope, it is the correct part of the correct log:
/var/log/apt/term.log:
Richte linux-headers-2.6.32-7.slh.1-sidux-686 ein (2.6.32-32) ...
Richte linux-image-2.6.32-7.slh.1-sidux-686 ein (2.6.32-32) ...
Running depmod.
Running update-initramfs.
update-initramfs: Generating
For the first: I hope, it is the correct part of the correct log:
/var/log/apt/term.log:
Richte linux-headers-2.6.32-7.slh.1-sidux-686 ein (2.6.32-32) ...
Richte linux-image-2.6.32-7.slh.1-sidux-686 ein (2.6.32-32) ...
Running depmod.
Running update-initramfs.
update-initramfs: Generating
This is two separate issues.
For the first:
Can you post the apt log to see if the kernel postinst.d hook was not
getting ran?
For the second,
That depends on what that script is actually doing. And are you running
it from the kernel you are supposed to be booted into? It could
possibly be
6 matches
Mail list logo