FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 03-19-2009, 02:36 PM
maximilian attems
 
Default Bug#518412: initramfs-tools: must support relative paths in modules.dep

> Recently kernels I built from upstream kernel source failed to boot
> after unpacking them because no modules got included in the initramfs
> initrd (and thus no root file system).
> This problem was solved after downgrading to m-i-t 3.4.1.

how can i reproduce this?

upgraded to latest m-i-t 3.7-pre9-1 and run depmod + mkinitramfs.
the generated initramfs had all modules i expect it to have.





--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 03-19-2009, 03:15 PM
Frans Pop
 
Default Bug#518412: initramfs-tools: must support relative paths in modules.dep

On Thursday 19 March 2009, maximilian attems wrote:
> > Recently kernels I built from upstream kernel source failed to boot
> > after unpacking them because no modules got included in the initramfs
> > initrd (and thus no root file system).
> > This problem was solved after downgrading to m-i-t 3.4.1.
>
> how can i reproduce this?
>
> upgraded to latest m-i-t 3.7-pre9-1 and run depmod + mkinitramfs.
> the generated initramfs had all modules i expect it to have.

You have to build a kernel from source while having the new m-i-t installed.
And then install that kernel *without* running depmod (which is currently
also not done by i-t).
If you do run an extra depmod manually before calling i-t the problem will
have fixed itself because depmod is then called differently than during the
kernel build.

I saw this issue after installing a kernel built from upstream source using
'fakeroot make deb-pkg' (i.e. without using kernel-package or anything).
With the stable version of m-i-t kernels built that way install perfectly
(using custom hook scripts to create the initrd and update grub etc.).

You can probably also reproduce it by running the following sequence of
commands, which should emulate the way the upstream kernel Makefile calls
depmod (using any kernel version you have installed for <kvers>):
# kvers=<kvers>
# mkdir -p /tmp/lib/modules
# cp -r /lib/modules/$kvers /tmp/lib/modules/
# rm /tmp/lib/modules/$kvers/modules.*
# depmod -ae -F /boot/System.map-$kvers -b /tmp/ -r $kvers

The file /tmp/lib/modules/<kvers>/modules.dep should then show the problem.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 03-19-2009, 03:51 PM
maximilian attems
 
Default Bug#518412: initramfs-tools: must support relative paths in modules.dep

thanks for quick feedback.

On Thu, Mar 19, 2009 at 05:15:06PM +0100, Frans Pop wrote:
>
> You have to build a kernel from source while having the new m-i-t installed.
> And then install that kernel *without* running depmod (which is currently
> also not done by i-t).

well linux-2.6 images postinst and even k-p do this,
so this quite arguiably a bug in make deb-pkg.

> If you do run an extra depmod manually before calling i-t the problem will
> have fixed itself because depmod is then called differently than during the
> kernel build.
>
> I saw this issue after installing a kernel built from upstream source using
> 'fakeroot make deb-pkg' (i.e. without using kernel-package or anything).
> With the stable version of m-i-t kernels built that way install perfectly
> (using custom hook scripts to create the initrd and update grub etc.).
>
> You can probably also reproduce it by running the following sequence of
> commands, which should emulate the way the upstream kernel Makefile calls
> depmod (using any kernel version you have installed for <kvers>):
> # kvers=<kvers>
> # mkdir -p /tmp/lib/modules
> # cp -r /lib/modules/$kvers /tmp/lib/modules/
> # rm /tmp/lib/modules/$kvers/modules.*
> # depmod -ae -F /boot/System.map-$kvers -b /tmp/ -r $kvers
>
> The file /tmp/lib/modules/<kvers>/modules.dep should then show the problem.

copied over that file and saw still no sign of a trouble:
mkinitramfs -v -o /tmp/foo | head -n 12
Adding module /lib/modules/2.6.29-rc8-amd64/kernel/drivers/usb/host/ehci-hcd.ko
Adding module /lib/modules/2.6.29-rc8-amd64/kernel/drivers/usb/host/ohci-hcd.ko
Adding module /lib/modules/2.6.29-rc8-amd64/kernel/drivers/usb/host/uhci-hcd.ko
Adding module /lib/modules/2.6.29-rc8-amd64/kernel/drivers/hid/hid.ko
Adding module /lib/modules/2.6.29-rc8-amd64/kernel/drivers/hid/usbhid/usbhid.ko
Adding module /lib/modules/2.6.29-rc8-amd64/kernel/drivers/hid/hid-a4tech.ko
Adding module /lib/modules/2.6.29-rc8-amd64/kernel/drivers/hid/hid-apple.ko
Adding module /lib/modules/2.6.29-rc8-amd64/kernel/drivers/hid/hid-belkin.ko
Adding module /lib/modules/2.6.29-rc8-amd64/kernel/drivers/hid/hid-cherry.ko
Adding module /lib/modules/2.6.29-rc8-amd64/kernel/drivers/hid/hid-chicony.ko
Adding module /lib/modules/2.6.29-rc8-amd64/kernel/drivers/hid/hid-cypress.ko
Adding module /lib/modules/2.6.29-rc8-amd64/kernel/drivers/hid/hid-ezkey.ko

testbooted fine in qemu.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 03-19-2009, 04:11 PM
Frans Pop
 
Default Bug#518412: initramfs-tools: must support relative paths in modules.dep

On Thursday 19 March 2009, maximilian attems wrote:
> thanks for quick feedback.
>
> On Thu, Mar 19, 2009 at 05:15:06PM +0100, Frans Pop wrote:
> > You have to build a kernel from source while having the new m-i-t
> > installed. And then install that kernel *without* running depmod
> > (which is currently also not done by i-t).
>
> well linux-2.6 images postinst and even k-p do this,
> so this quite arguiably a bug in make deb-pkg.

No. deb-pkg CANNOT do this because it is executed on the system building
the kernel and the extra depmod would need to be run on the system where
the kernel is installed.
So *at most* my custom hook scripts that get executed when the kernel is
installed would be at fault for not doing the extra depmod (and I could
easily change them to do that, but that would be only solving the problem
for me and not for everybody else).

However, IMO a modules.dep file created by the upstream kernel Makefile
using an official version of m-i-t should be assumed to be valid and
should thus be supported by i-t.
If the file is not valid, then there would be a bug in m-i-t, but Marco
has argued that it is not.

> > You can probably also reproduce it by running the following sequence
> > of commands, which should emulate the way the upstream kernel
> > Makefile calls depmod (using any kernel version you have installed
> > for <kvers>): # kvers=<kvers>
> > # mkdir -p /tmp/lib/modules
> > # cp -r /lib/modules/$kvers /tmp/lib/modules/
> > # rm /tmp/lib/modules/$kvers/modules.*
> > # depmod -ae -F /boot/System.map-$kvers -b /tmp/ -r $kvers
> >
> > The file /tmp/lib/modules/<kvers>/modules.dep should then show the
> > problem.
>
> copied over that file and saw still no sign of a trouble:
> mkinitramfs -v -o /tmp/foo | head -n 12

Are you sure you have the new version of m-i-t installed? Did you check
the contents of the generated modules.dep file?

Maybe my command was broken though. I did not check it as I've put m-i-t
on hold on all my machines. I'll check the actual command executed by the
kernel later.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 

Thread Tools




All times are GMT. The time now is 12:11 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org