DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
For the first time in many years I;ve had to make a kernel rather than just downloading the debian image.
I've configured, make,make modules_install then make install. All appears well. I then use mkinitrd to get ramdisk, from inside /usr/src/linux-2.6.22 I type mkinitrd -o /boot/testinitrd.
I then add it to grub.
When I boot it all starts up then I get messages like
mount:unknown filesystem type 'devfs'
modprobe:FATAL: could not load /lib/modules/2.6.22/modules.dep:No such file or irectory
and lots of similar errors and finally
mount:devfs:not monted
kernel panic -not syncing:attempted to kill init!
I should add I'm using Etch, raiserfs partitions and a SATA harddrive, and have tried with several kernel buils, Can anyone advise. I should also add lib/mod/2.6.2 exists
And sorry if this mesage seems starange (spelling gramma, my text box will only open 4 characters wide :s
Debian has for some time distributed and installed modular kernels by default, depending on the helper package initrd-tools to add the needed modules in a cramfs initrd-image.
2.6 has a newer format, initramfs, which is an cpio gzipped archive. The handoff to early userspace is much earlier. Initramfs allows a cleaner interface.
Thanks for that.
Could someone be kind enough to give me or point me in the direction of how to use this?
For example with initrd I'd just mkinitrd -o /root/kernelname module name eg makinitrd -o /root/custombuild 2.6,22
Location: Europe:Salzburg Austria USA:Orlando,Florida;
Distribution: Debian
Posts: 643
Rep:
Quote:
Originally Posted by knobby67
Thanks for that.
Could someone be kind enough to give me or point me in the direction of how to use this?
For example with initrd I'd just mkinitrd -o /root/kernelname module name eg makinitrd -o /root/custombuild 2.6,22
Distribution: Debian /Jessie/Stretch/Sid, Linux Mint DE
Posts: 5,195
Rep:
Compiling the kernel the Debian way is a good idea. However, for a kernel compiled for just one machine you don't need initrd. If you compile the device driver support for your IDE and or SCSI disks and the support for the file system you use, you can do without initrd.
It won't hurt to compile it with initrd until you are more familiar with your hardware. It will save you some frustrations while you get the hand of it.
In fact, if you follow the how to mentioned, it will do it for you.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.