LinuxQuestions.org - installing a mandrake 2.6 kernel

- Mandriva (https://www.linuxquestions.org/questions/mandriva-30/)

- - installing a mandrake 2.6 kernel (https://www.linuxquestions.org/questions/mandriva-30/installing-a-mandrake-2-6-kernel-133874/)

installing a mandrake 2.6 kernel

i got the source on there and configured it, and from what i remember with mandrake's 2.4 kernels, they have their own series of make commands. are they different with 2.6 and if so how?

It should be the same. To make sure, look at the README file in the source tree. It will tell you what steps to take.

If the kernel is like mine on Gentoo the commands for 2.6 are

Code:

make 

make modules_install

That was all I did and I'm running it now.

Code:

bash-2.05b# uname -r

2.6.0-test11

bash-2.05b#

That help?

:D :D :D :D

Quote:

Originally posted by dalek
If the kernel is like mine on Gentoo the commands for 2.6 are

Code:

make make modules_install

That was all I did and I'm running it now.

Code:

bash-2.05b# uname -r 2.6.0-test11 bash-2.05b#

That help?

:D :D :D :D

Are you running the 2.6 on the Mandrake 9.1?

Quote:

Originally posted by Kramer
Are you running the 2.6 on the Mandrake 9.1?

Don't hardly use Mandrake any more. This Gentoo is so much faster and more up to date. I am more up to date than 9.2 till it ain't funny. I just emerge sync and then emerge -u world and it downloads, compiles and installs everything on the system.

I may try it though sometime. I may just point the bootloader to the other root and see what happens.

That may get complicated. I'll figure out something though.

Later

:D :D :D :D

*first mv your current kernel (e.g. at /boot/vmlinuz) to /boot/<kernelname>.old
*alter /etc/lilo.conf:
*change 'image=/boot/<kernelname>' to 'image=/boot/<kernelname>.old' and 'label=<currentlabel>' to 'label=<currentlabel>.old' on the entry you boot from
*make a second entry exactly the same as the one you altered except for 'image=/boot/vmlinuz' and 'label=<currentlabel>'
now your lilo.conf looks like:

Code:

...

image=/boot/vmlinuz-2.4.22-10mdk

        label="linux-nonfb"

        root=/dev/hda2

        initrd=/boot/initrd.img

        append="devfs=mount splash=silent splash=silent splash=silent resume=/dev/hda5"

        read-only

image=/boot/vmlinuz

        label="linux"

        root=/dev/hda2

        initrd=/boot/initrd.img

        append="devfs=mount splash=silent splash=silent splash=silent resume=/dev/hda5 

image=/boot/vmlinuz.old

        label="linux.old"

        root=/dev/hda2

        initrd=/boot/initrd.img

        append="devfs=mount splash=silent splash=silent splash=silent resume=/dev/hda5 splash=silent"

        vga=788

        read-only

image=/boot/vmlinuz-2.4.22-10mdk

        label="failsafe"

        root=/dev/hda2

        initrd=/boot/initrd.img

        append="failsafe devfs=nomount splash=silent splash=silent splash=silent resume=/dev/hda5"

        read-only

*then just type:

make config (or make menuconfig)
make
make install
make modules_install
lilo (this is very important DO NOT FORGET!!! Else you won't be able to boot!)

That's it! This way, you can use the old entry as a backup kernel if it would happen that things didn't turn out as expected...

I'm also going to try installing a 2.6 kernel. I have the source installed...but on a lark I tried to rpm the kernel-2.6 package...which says it needs a bunch of updated packages (which I hadn't found when looking that time) ...

Does compiling from the source require new packages also? Or can I just jump my mdk 9.2 install into a 2.6 kernel by compiling it the normal way?

You should install the packages, as they are needed by the new kernel. There should only be 4 or 5 of them I think. When I updated, i remember they were much smaller in size than the kernel source, so it is not that bad.

There is a thread around with the minimum version of these packages, if i find it, I will link it here.

no one said anything about make dep

...elluva corrects me, sorry for being misleading.

I guess it makes sense if you are compiling yourself rather than installing the binary compilled against the other package versions.

My first attempts to compile 2.6 from scratch were unsuccessful, perhaps i was doing something else wrong in the config, anyway, at the time I assumed it was the package versions, as there ere several threads with package update lists floating around at the time.

Good luck.

PS here is the thread with the package lists, more than 4or5, but not toobad:
http://linuxquestions.org/questions/...5&pagenumber=2

Quote:

Originally posted by wldkos
no one said anything about make dep

No need for make dep in 2.6. Matter of fact, mine puked when I typed it in. :tisk: :tisk:

Later

:D :D :D :D

Quote:

Originally posted by colnago
...elluva corrects me, sorry for being misleading.
...
My first attempts to compile 2.6 from scratch were unsuccessful, perhaps i was doing something else wrong in the config, anyway, at the time I assumed it was the package versions, as there ere several threads with package update lists floating around at the time.

Good luck.

if you are reffering to the modutils, I thought mdk 9.2 was 2.6 ready, could be wrong though I am quit sure.
It is always better to compile a kernel yourself because you can compile it exactly to the needs of your hardware and this will certainly speed up your system. It won't work at first (chances are small), but after searching what things you need in YOUR kernel, you will notice the difference in speed.
Also on a kernel compile, keep it as small as possible, if you don't have a RAID device, then don't compile support for it. You will notice it is worth the time.

another thing: Colnago, I didn't mean to correct you, since I hadn't read your post ;)

I'm also compiling and installing (attempting to anyway) a 2.6 kernel in Mdk 9.2

Make dep says its unnecessary

what about make modules (I ask because only make modules_install was mentionned)?

I assume Gentoo compile will be the same as yours. I did:

make
make modules_install

and that was it.

It says it does dep and modules during the make process and the you install them and that is it.

Hope that helps.

Later

:D :D :D :D