upgrading from 2.4.31 to 2.6.17.9

sharathg786 · 08-22-2006, 06:30 AM

hi, i'm sort of a newbie using slackware 10.2, 2.4.31 kernel, can anyone help me with upgrading to new kernel 2.16.17.9, since this is the 1st time i'm doing this?

Samoth · 08-22-2006, 07:18 AM

That is a pretty big upgrade, so I would recommend installing the stock 2.6.16 kernel first, so you have udev/alsa/sysfs all set up. YMMV, but it would help IMHO to upgrade like that. Cheers.

<<Samoth>>

hitest · 08-22-2006, 07:36 AM

I did a clean install with 2.6.13. If you want to upgrade to a more cutting edge kernel shilo and DaOne have two excellent kernel compile guides that are pinned at the top of this forum:-)

rkrishna · 08-23-2006, 03:04 AM

this topic is discussed many times since u r new i can send the tutorial once more
also i think that, "installing new kernel" is corerct word than "upgrading kernel"

this is my small how to on kernel compile
--------------
download the kernel source to ur home/build/ dir
http://kernel.org/pub/linux/kernel/v....17.10.tar.bz2
say /home/xxxx/build (u have a dir called build in home. $mkdir build ..wil do)
now u r in /home/xxxx/build$,
$wget -c http://kernel.org/pub/linux/kernel/v....17.10.tar.bz2
$tar -xvjf
(if needed, u can create a simlink as we do in /usr/src,
$ln -sf linux-2.6.17.10/ linux)
$cd linux-2.6.17.10/ directory, then issue:

Code:

$ make menuconfig (from text node) {make xconfig or gconfig, i do gconfig -both this are for xwindow} (make your changes then save the file) --->how simple!! it will take some time if doing first time, if u read the helps a day or one week .... 
$ make <---then su to root and 
# cp System.map /boot/System.map-2.6.17.10 ; ln -sf /boot/System.map-2.6.17.10 /boot/S ystem.map 
# make modules_install 
# cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.17.10 
# lilo <----before doing this edit lilo 
# reboot <--if u want to try this kernel

editin lilo
---------
image = /boot/vmlinuz-2.6.17.10
root = /dev/hda1 <-- put your / (root/boot) partition here
label = 2.6.17.10 <-- or lin2.6
read-only
-------------

User61 · 08-24-2006, 02:40 AM

make bzImage is obselete now?

willysr · 08-24-2006, 02:58 AM

i think make will include make bzImage on it, but the way i do it

Code:

cp /boot/config ./.config
make oldconfig
<adjust the configuration if needed>
make bzImage
make modules
make modules_install
cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.xx.yy
cp System.map /boot/System.map-2.6.xx.yy
cp .config /boot/config-2.6.xx.yy
<adjust symlink in /boot>
<edit lilo.conf>
/sbin/lilo -v (make sure no errors)
restart

Vampirite · 08-24-2006, 05:34 AM

What does "oldconfig" do?

I have only used "menuconfig" and "gconfig".

Only one of my Kernels has ever worked, and that is my LFS one, which is also a modified Slackware one!

willysr · 08-24-2006, 06:21 AM

it will use the old config file (if you don't want to build another config file). I usually saved it in my other directory so that i can use it again to build the next kernel. I derived it from Slackware's default config file

Vampirite · 08-25-2006, 12:52 PM

I shall have to try that!

Though... if I use oldconfig, and load an old config file, will I still be able to change the config eg. processor, etc...?

raska · 08-25-2006, 12:56 PM

Quote:

Originally Posted by Vampirite

... if I use oldconfig, and load an old config file, will I still be able to change the config eg. processor, etc...?

yes you will. Just issue a make menuconfig when the make oldconfig had finished :P

after configuring with make menuconfig I just type

Code:

make
make modules_install
make install -- the /etc/lilo.conf file should functional at this point as the lilo command gets called here

Check for errors and reboot.
Could it be any easier I ask?

netcrawl · 08-25-2006, 01:02 PM

Quote:

Originally Posted by raska

after make menuconfig I just type

Code:

make
make modules_install
make install -- the /etc/lilo.conf file should functional at this point as the lilo command gets called here

Check for errors and reboot.
Could it be any easier I ask?

make && make modules_install && make install

raska · 08-25-2006, 01:09 PM

damn you got me... ok the actual command that I type is:

Code:

date > ~/k.start && make && make modules_install && make install; date > ~/k.end; ls -lh /boot/; cat ~/k.*

The k.start and k.end files are for measuring compiling times.
the ls -lh /boot/ command is to review the sizes and files there

Vampirite · 08-26-2006, 05:25 AM

Makes my life much easier