Kernel Compile Guide for 2.6.0

BroX · 06-25-2007, 02:40 AM

Quote:

Originally Posted by o2bfishn

what if you edited the lilo file as below?

Lines preceeded by '#' are merely comments.

Basslord1124 · 06-25-2007, 10:36 AM

Quote:

Originally Posted by H_TeXMeX_H

He's not using window$ boot loader, it is being chainloaded by lilo ... which is the only way ...

Yeah my bad on the wording lol. Basically booting up to the Windows boot menu only points to the location on the disk where Slack is stored and from there I enter the lilo screen and make my selection. Which at that point it's no different than if I installed Linux as the only OS. So I still edit and configure lilo like any other Linux user out there that uses lilo.

Basslord1124 · 06-25-2007, 10:43 AM

As a side note, I should just go ahead and remove that Windows entry....that's only pointing to my 2nd hard drive which I use for Windows data storage (also an ATA drive too) that doesn't even have an OS on it.

winfinit · 06-25-2007, 11:39 AM

hey, i see that you did place new vmlinuz-2.6.x.x but how did you you get that, just want to make sure, because i think your problem is that you are still using boot image from 2.4.x.x kernel just renamed, please make sure that you copied that from your compiled source of 2.6.x.x arch/i386/boot/bzImage,

if you are doing cp of your bzImage like this

cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinux-2.6.x.x then make sure that /usr/src/linux is actually pointing to your 2.6 source dir, since /usr/src/linux is a symbolic link usually.

there is no other reason why it would boot into 2.4

here is my little shell script that i am using for compilation of my kernel (!!!edit version numbers!!!) so if you want just drop this script into your 2.6.x.x and execute it, then reboot, that should do the job. (ofcourse it assumes that you already specified all the changes in your lilo.conf)

#!/bin/sh

make bzImage
make modules
make modules_install
cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.21
cp System.map /boot/System.map-2.6.21
cp .config /boot/config-2.6.21
lilo

let us know how whats up

-------------------------------
Linux powaaaah

Basslord1124 · 06-25-2007, 03:58 PM

Quote:

Originally Posted by winfinit

hey, i see that you did place new vmlinuz-2.6.x.x but how did you you get that, just want to make sure, because i think your problem is that you are still using boot image from 2.4.x.x kernel just renamed, please make sure that you copied that from your compiled source of 2.6.x.x arch/i386/boot/bzImage,

if you are doing cp of your bzImage like this

cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinux-2.6.x.x then make sure that /usr/src/linux is actually pointing to your 2.6 source dir, since /usr/src/linux is a symbolic link usually.

there is no other reason why it would boot into 2.4

here is my little shell script that i am using for compilation of my kernel (!!!edit version numbers!!!) so if you want just drop this script into your 2.6.x.x and execute it, then reboot, that should do the job. (ofcourse it assumes that you already specified all the changes in your lilo.conf)

#!/bin/sh

make bzImage
make modules
make modules_install
cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.21
cp System.map /boot/System.map-2.6.21
cp .config /boot/config-2.6.21
lilo

let us know how whats up

-------------------------------
Linux powaaaah

As for the vmlinuz name...I technically was just following a guide and that's the sample name it picked, so for simplicity's sake, that's what I did...editing the version number of course. Ya know what you said might very well be my problem...I copied bzImage to the /boot directory but I never read anything in those guides about symbolic links. Also in your script, I never did anything regarding System.map or the command following that. Basically after I compiled it, I did make bzImage, make modules, make modules_install, the copying bzImage to boot, then running lilo (well after I made the changes of course).

winfinit · 06-25-2007, 06:27 PM

please paste results of the following

1. ls -l /usr/src/linux
2. egrep '^[^#]' /etc/lilo.conf
3. cd into your 2.6 source dir and do "pwd"

BroX · 06-25-2007, 07:16 PM

Quote:

I never did anything regarding System.map or the command following that. Basically after I compiled it, I did make bzImage, make modules, make modules_install, the copying bzImage to boot, then running lilo (well after I made the changes of course).

I bet that explains it. You need to copy System.map to /boot as well. Hope that solves it.

Cheers, Leon.

Basslord1124 · 06-25-2007, 09:20 PM

Quote:

Originally Posted by LJSBrokken

I bet that explains it. You need to copy System.map to /boot as well. Hope that solves it.

Cheers, Leon.

Yeah, thanks for the tips though....I'll definitely give it a try here soon. It kinda got my hopes up though, compilation went ok and I did what the guides said and I'm thinking to myself how cool it's gonna feel when I get this new kernel in place. And sadly enough, I couldn't get it to work. I suppose those guides I was using failed to mention some things.

Is the System.map a Slackware dependent thing since I haven't seen it in any other kernel compile guides?

H_TeXMeX_H · 06-25-2007, 09:22 PM

See here:
http://www.dirac.org/linux/system.map/

o2bfishn · 06-25-2007, 10:36 PM

Quote:

Originally Posted by LJSBrokken

Lines preceeded by '#' are merely comments.

i know that, what i meant was what would happen if you rearranged the file so that the new 2.6 stuff was in the section beginning with # Linux bootable partition config begins. before, it was above that.

before, he had this

Code:

#Linux 2.6 kernel
image = /boot/vmlinuz-2.6.21.4
 root = /dev/sda3
 label = Linux_2_6
 read-only
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda3
  label = Linux
  read-only
#Windows
other = /dev/hdb1
  label = Windows
  table = /dev/hdb
# Linux bootable partition config ends

and i changed it to this

Code:

# Linux bootable partition config begins
#Linux 2.4 kernel
image = /boot/vmlinuz
 root = /dev/sda3
 label = Linux
 read-only
#Linux 2.6 kernel
image = /boot/vmlinuz-2.6.21.4
 root = /dev/sda3
 label = Linux_2_6
 read-only
#Windows
other = /dev/hdb1
 label = Windows
 table = /dev/hdb
# Linux bootable partition config ends

but i guess its a moot point, this probably isnt whats causing his problem anyhow.

winfinit · 06-29-2007, 01:09 PM

maaaan just follow compilation guide on previous page, i bet that missing symbolic link will do the job, also system.map shouldnt affect the boot, i removed mine, well not removed but moved it out of /boot and it worked, well it booted, not sure about working...

just do
rm /usr/src/linux
ln -s /path/to/your/kernel/source /usr/src/linux

EXAMPLE ON MY BOX

root@localhost:/usr/src# ln -s /usr/src/linux-2.6.21/ /usr/src/linux

root@localhost:/usr/src# ls -lah | grep linux
lrwxrwxrwx 1 root root 22 2007-06-29 14:11 linux -> /usr/src/linux-2.6.21//
drwxr-xr-x 15 root root 584 2006-09-01 02:47 linux-2.4.33.3/
drwxr-xr-x 19 root root 824 2007-06-29 14:11 linux-2.6.21/

Basslord1124 · 07-01-2007, 07:01 PM

I'm not sure what I am doing wrong but it still isn't working guys. I even removed the Windows entry from lilo and it still shows up at boot time. I am starting to think it's possessed or something. I ran both the system.map command as well as copying the .config like you did winfinit but it didn't seem to do any good. I did notice something though that I think might be the problem, and unfortunately I am a little clueless on what it means so bear with me. If I run ls on /boot this is what I get...

Code:

chris@chris-desktop-1:~$ ls -lsh /boot
total 6.4M
   0 lrwxrwxrwx 1 root root   37 2007-01-03 08:55 README.initrd -> /usr/doc/mkin                                                                           itrd-1.0.1/README.initrd
   0 lrwxrwxrwx 1 root root   23 2007-01-03 08:55 System.map -> System.map-ide-2                                                                           .4.33.3
1.3M -rw-r--r-- 1 root root 1.3M 2007-07-01 13:13 System.map-2.6.21.4
620K -rw-r--r-- 1 root root 615K 2006-09-01 02:51 System.map-ide-2.4.33.3
4.0K -rw-r--r-- 1 root root  512 2007-01-03 09:08 boot.0803
4.0K -rw-r--r-- 1 root root  198 2007-07-01 13:30 boot_message.txt
4.0K -rw-r--r-- 1 root root  239 2007-07-01 13:30 boot_message.txt~
   0 lrwxrwxrwx 1 root root   19 2007-01-03 08:55 config -> config-ide-2.4.33.3
 40K -rw-r--r-- 1 root root  37K 2007-07-01 13:14 config-2.6.21.4
 44K -rw-r--r-- 1 root root  41K 2006-09-01 02:51 config-ide-2.4.33.3
8.0K -rw-r--r-- 1 root root 5.0K 2006-08-08 01:34 diag1.img
 64K -rw------- 1 root root  60K 2007-07-01 13:27 map
   0 lrwxrwxrwx 1 root root   20 2007-01-03 08:55 vmlinuz -> vmlinuz-ide-2.4.33.                                                                           3
3.1M -rw-r--r-- 1 root root 3.1M 2007-06-23 21:09 vmlinuz-2.6.21.4
1.3M -rw-r--r-- 1 root root 1.3M 2006-09-01 02:51 vmlinuz-ide-2.4.33.3

The thing that captured my eye was the lines with the arrows...I am assuming these are the symbolic links? Well I noticed each line that contains something to do with the 2.4 kernel version has them....none of my 2.6 ones do. Could this be part of the problem??

winfinit · 07-02-2007, 02:23 AM

yepp those are symbolic links. here is output of my /boot and output of my /usr/src try to clone it

root@localhost:~# ls -lah /boot
drwxr-xr-x 2 root root 504 2007-06-24 14:16 ./
drwxr-xr-x 22 root root 520 2007-06-27 01:16 ../
lrwxrwxrwx 1 root root 37 2007-06-05 20:57 README.initrd -> /usr/doc/mkinitrd-1.0.1/README.initrd
-rw-r--r-- 1 root root 1.1M 2007-06-05 21:07 System.map
-rw-r--r-- 1 root root 772K 2007-06-24 14:15 System.map-2.6.21
-rw-r--r-- 1 root root 615K 2006-09-01 02:51 System.map-ide-2.4.33.3
-rw-r--r-- 1 root root 512 2007-06-05 21:10 boot.0800
-rw-r--r-- 1 root root 168 2007-06-05 21:10 boot_message.txt
-rw-r--r-- 1 root root 62K 2007-06-05 21:07 config
-rw-r--r-- 1 root root 45K 2007-06-24 14:15 config-2.6.21
-rw-r--r-- 1 root root 41K 2006-09-01 02:51 config-ide-2.4.33.3
-rw-r--r-- 1 root root 5.0K 2006-08-08 01:34 diag1.img
-rw------- 1 root root 68K 2007-06-24 14:16 map
-r-------- 1 root root 3.4M 2007-06-05 21:07 vmlinuz
-rw-r--r-- 1 root root 1.8M 2007-06-24 14:15 vmlinuz-2.6.21
-rw-r--r-- 1 root root 1.3M 2006-09-01 02:51 vmlinuz-ide-2.4.33.3

ignore initrd and boot_*

root@localhost:~# ls -lah /usr/src
total 1.5K
drwxr-xr-x 8 root root 240 2007-06-29 14:14 ./
drwxr-xr-x 19 root root 568 2006-03-12 18:29 ../
drwxr-xr-x 2 root root 88 2007-06-24 15:18 ati/
drwxr-xr-x 2 root root 48 2007-06-24 19:32 gnu/
lrwxrwxrwx 1 root root 21 2007-06-29 14:14 linux -> /usr/src/linux-2.6.21/
drwxr-xr-x 15 root root 584 2006-09-01 02:47 linux-2.4.33.3/
drwxr-xr-x 19 root root 824 2007-06-29 14:11 linux-2.6.21/
drwxr-xr-x 7 root root 168 2003-10-29 01:08 rpm/
drwxr-xr-x 2 root root 176 2006-08-22 23:13 speakup-2.4.33.3/

now your linux link will be pointing to /usr/src/linux-2.4.33.3 of you are running SW11, you have to 'rm linux' and do 'ln -s /usr/src/linux-2.6.21 /usr/src/linux'

Basslord1124 · 07-02-2007, 09:30 PM

All right, both of my directories basically look like yours with the obvious differences in version numbers....but, it still appears like nothing has changed when I reboot. I swear it seems like no matter what editing I do to lilo it doesn't seem like it takes any of the changes I put in. I had removed all former symbolic links from my first display of /boot and then I added a link pointing to the new 2.6 kernel source directory. But alas, nothing. Oh well, I monkey more with it the next few days.

winfinit · 07-11-2007, 10:41 PM

ok man

i was bored here and was trying to duplicate your issue

here is what i did to fix it, i just went back to /usr/src/linux redid
make bzImage && \
make modules && \
make modules_install && \
cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.21 && \
cp System.map /boot/System.map-2.6.21 && \
cp .config /boot/config-2.6.21 && \
lilo

so i reran lilo, rebooted and it worked for me.

how i was able to duplicate it:

i was messing around with lilo and random options so after i ran lilo, it told me for some reason that boot image for my 2.6.21 doesnt exist, while it was in boot dir, so i cam beack to stock config of my lilo, added all the entries reran lilo again, and it looked like everything went ok, but it didnt, because my 2.6.21 was not bootable it was going to 2.6.17.13 for uknown reason, after recompiling kernel and replacing all the images, and just running lilo command again, i was able to get my 2.6.21 working again.