When it works
Reboot to your new kernel and pray. Ensure that your hardware is detected properly during the boot. If it does not boot, reboot again and try to find why it didn't work. Don't be scared to recompile it again, you can have to do it more than a time. Now if everything goes ok put the new kernel as default:
$ rm /usr/src/linux-2.4
$ ln -s /usr/src/linux-2.4.19 /usr/src/linux-2.4
or (it depends the version you have):
$ rm /usr/src/linux
$ ln -s /usr/src/linux-2.4.19 /usr/src/linux
To see which one you have to choose, simply do this:
$ ls -ld /usr/src/linux*
lrwxrwxrwx 1 root root 12 Oct 30 18:55 /usr/src/linux -> linux-2.4.17
drwxr-xr-x 14 root root 4096 Oct 30 17:26 /usr/src/linux-2.4.17
drwxr-xr-x 14 root root 4096 Oct 30 15:16 /usr/src/linux-2.4.17-openmosix-r2
drwxr-xr-x 14 root root 4096 Nov 1 20:11 /usr/src/linux-2.4.19
drwxr-xr-x 15 root root 4096 Nov 1 18:01 /usr/src/linux-2.4.19-openmosix-r7
It will show you lines with linux in their name. Have a look at the symlink, you will find it by looking at the rights of the files: lrwxrwxrwx. The "l" let you know it is a symlink so look at the name of this file and remove it to place the new symlink. Here you will choose the second solution as the symlink is called linux (/usr/src/linux). You can also change your "default=" in lilo.conf. Now make a bootdisk with the new kernel installed (mkbootdisk $(uname -r) or mkbootdisk 2.4.19). If after many efforts it didn't decide to work, apply backuped files in their original path. If everything goes good, just enjoy :)
Find more infos about kernel compiling in /usr/src/linux/README (general view on kernel compilation), /usr/src/linux/Documentation/Configure.help (explain in detail every elements of make config) or /usr/src/linux/Documentation/modules.txt for modules explanation. |
Printable Version
TalkBack / Comments
Write a Comment