HOWTO: Kernel compilation

[TheRealEdwin]

I tried your command since I also like to get the headers but I recieve this error when I try to.

edwin@Doomhammer:/usr/src/linux$ make-kpkg --rootcmd fakeroot --initrd --append_to_version -custom --revision $(date +'%d%m%y') kernel_image kernel_headers
I note that you are using the --revision flag with the value
   210605.
However, the ./debian/changelog file exists, and has a different value
   10.00.Custom.
I am confused by this discrepancy, and am halting.

[skoal]

"However, the ./debian/changelog file exists, and has a different value 10.00.Custom."

That's from you using the $(date +'%d%m%y') in --revision. Just use '--revision 10.00.Custom' instead.

That date part I use is part of a compile script I have, so you don't need to use it and I probably should have left it out altogether in my instructions.

\\//_

[Heliode]

I've got a question... I would like to try this, but does this procedure overwrite the current kernel, or does it add the new kernel to GRUB, so you keep the option to boot the old one?

I use my Ubuntu machines quite a lot and I don't want to have them in an unusable state.

[oddabe19]

edit 2: Bah! Still getting "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)".

I get the exact same thing, and I compiled Ext3 and Ext2 into the kernel NOT as a module.

[dresnu]

I get the exact same thing, and I compiled Ext3 and Ext2 into the kernel NOT as a module.

Check this thread: http://www.ubuntuforums.org/showthre...light=mkinitrd
Scroll down to the last post and do what is suggested there.

[dresnu]

oh, and after that do update-grub obviously

[luca_linux]

I've got a question... I would like to try this, but does this procedure overwrite the current kernel, or does it add the new kernel to GRUB, so you keep the option to boot the old one?

I use my Ubuntu machines quite a lot and I don't want to have them in an unusable state.

The new kernel will be added, so you'll be able to continue using the old one.

[luca_linux]

I hesitate to post my kernel .config, but I will anyway. So before you post back with this .config don't work, please read my specs below (and make the appropriate changes with 'menuconfig' for any differences). - see attached -

My rig with relevant kernel config parameters:

• Pentium 4
• Intel motherboard chipsets
• All IDE host hardware
• Nvidia Ti-4600
• ALSA (only emu10k1 driver installed)
• only e100 for NIC driver
• only ACPI, no APM.
• USB and Filesystems all modules and should work for any rig.
• probably sumtin' sumtin' else impotant I'm missing here.

NOTES:

• I stripped this kernel like a true playa would. All my kernels are phat, not fat. You feelin' me?? Any driver I don't use, ain't using me?? You feelin' this??
• I do not use local APIC or any framebuffer devices -> not good with Nvidia cards and performance stability (in general). Those 2 cause more Nvidia related problems (outside of RenderAccel) than spilling crunk juice on some green fab marked with Nvidia TM.
• All (and everything) SCSI is stripped. I'm all IDE bay-bee - living large and in charge.
• All irrelevant networking (experimental) doohickeys only IT netadmins would remotely care about, have been pimp slapped to /dev/null. Don't even look for it in my configs.

howto Build:

1. copy attached config to /usr/src/linux/.config
2. * run 'make menuconfig' and change any subtle differences between my rig and yours. (note the asterisk).
3. make-kpkg --rootcmd fakeroot --initrd --append_to_version -custom --revision $(date +'%d%m%y') kernel_image kernel_headers
4. dpkg -i kernel-image-2.6.12-custom_190605_i386.deb
5. dpkg -i kernel-headers-2.6.12-custom_190605_i386.deb (for installing nvidia drivers after reboot)
6. reboot.
7. You'll see some 'warning' when your ramdisk starts, like missing dis or dat. Just ignore it like a true playa rollin' through stop signs while flippin' the switches on his '64. That's how we roll...
8. drop to custom init level for console, or /etc/init.d/gdm stop, or wait for gdm to puke on it's own. Compile nvidia drivers, startx, and off you go! weeeeeeeeee!!!!

If you want to fix the 'modules missing' stuff at startup when your ramdisk mounts, you can play with adding those particular ones to /etc/mkinitrd/modules. If you want to see what's missing from your ramdisk module startup:

skoal@morpheus://~ $ sudo mount -t cramfs -o loop /boot/initrd.img-2.6.12-custom /mnt && cd /mnt

check what filesystem/modules are missing...

skoal@morpheus:///mnt $ cat loadmodules
modprobe -k fan 2> /dev/null
[...]
modprobe -k ide-generic
modprobe -k ide-disk

add 'em to /etc/mkinitrd/modules (in the proper order), remake ramdisk, and drop it like it's hot. That's how we roll...

\\//_

Ok, I'll give you the kernel config back tomorrow.

[TheRealEdwin]

How would I go about uninstalling multiple kernels? Here is what I want to do.

title		Ubuntu, kernel 2.6.12 
root		(hd0,2)
kernel		/boot/vmlinuz-2.6.12 root=/dev/hda3 ro quiet splash
savedefault
boot

title		Ubuntu, kernel 2.6.12 (recovery mode)
root		(hd0,2)
kernel		/boot/vmlinuz-2.6.12 root=/dev/hda3 ro single
savedefault
boot

title		Ubuntu, kernel 2.6.10-5-686 
root		(hd0,2)
kernel		/boot/vmlinuz-2.6.10-5-686 root=/dev/hda3 ro quiet splash
initrd		/boot/initrd.img-2.6.10-5-686
savedefault
boot

title		Ubuntu, kernel 2.6.10-5-686 (recovery mode)
root		(hd0,2)
kernel		/boot/vmlinuz-2.6.10-5-686 root=/dev/hda3 ro single
initrd		/boot/initrd.img-2.6.10-5-686
savedefault
boot

title		Ubuntu, kernel 2.6.10-5-386 
root		(hd0,2)
kernel		/boot/vmlinuz-2.6.10-5-386 root=/dev/hda3 ro quiet splash
initrd		/boot/initrd.img-2.6.10-5-386
savedefault
boot

title		Ubuntu, kernel 2.6.10-5-386 (recovery mode)
root		(hd0,2)
kernel		/boot/vmlinuz-2.6.10-5-386 root=/dev/hda3 ro single
initrd		/boot/initrd.img-2.6.10-5-386
savedefault
boot

title		Ubuntu, kernel memtest86+ 
root		(hd0,2)
kernel		/boot/memtest86+.bin  
savedefault
boot

I want to get rid of the 2.6.10-5-386 (why use 386 when I have a 686 kernel that works), the .12 kernel (doesn't work). Is there a way to remove them cleanly? Only thing I can think of is if dpkg has a command to list all packages. Any suggestions?

edit: After much searching I found it. Still don't know how to uninstall the 386 version of the kernel.

sudo dpkg --get-selections | less
sudo dpkg -r kernel-image-2.6.12

[Seer]

You forgot to mention that you also need

sudo apt-get install kernel-package

in order to use

sudo make-kpkg clean

if you don't already have it... (...which I didnt and I have no clue what they are but I googled it )