kernel 2.6.12.3 compilation problem

rkrishna · 08-06-2005, 06:17 AM

i just followed the thread by DaOne and compiled 2.4.29 tehn gaining confidence
moved to 2.6.12.3 but error i cant boot ...
it will start going as usual

boot: Slackware %name in lilo
Linux Slackware
BIOS.data check successfull
Uncompressing linux .......OK, booting the kernel
usual messages for 2-3 sec
but a screen will come suddently and shows the message

boot: Slackware %name in lilo
Linux Slackware
BIOS.data check successfull
Uncompressing linux .......OK, booting the kernel
Linux version 2.6.12.3test (root & ibmlinphysics)(gcc version 3.3.4)#2 fri Aug5 22

%i remember somewhere i wrote like 2.6.12.3test,
ibmlinphys is my box name
%slocate gives a folder called /lib/modules/2.6.12.3test/ %how this came
where i had gone wrong

actually i logged as root and done everything
and also i do
su -c "make modules_install" as described by DaOne %was su needed

after that i copied bzimage to /boot as vmlinuz %to check wether it will work or not
by cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-2.6.12.3
edited lilo same problem same screen

now i am booting to the system through newly made kernel 2.4.29 %compiled by me

where i had gone wrong

thanks in advance

Bruce Hill · 08-06-2005, 06:34 AM

Please post the exact error message as it appears on your screen, and the steps of your kernel compile.

And /lib/modules/2.6.12.3test/ is the directory containing the modules for your new kernel.

That guide has instructions that do not conform to Linus Torvald's instructions. If you will read ./linux-2.6.12.3/README you will see the proper way to build a 2.6 kernel. Here is a link to a guide which you can use to build the kernel, also. You can copy and paste from it. One thing ... do not symlink System.map as he says at the bottom. Everything else will work fine.

I build all my kernels (2.4 and 2.6) under /home/mingdao/build/ and never have one single problem.

Edit: I also notice that you issued
cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-2.6.5
which named your kernel image incorrectly. It should be vmlinuz-2.6.12.3test according to the rest of your post.

Bruce Hill · 08-06-2005, 06:46 AM

I really think I needed to add this quote, since I read so many threads where people followed some guys kernel compile guide, rather than the instructions that come with the kernel, and then post here that they can't boot their new kernel.

This is a quote from Linus Torvalds (he might know about compiling the Linux kernel):

Quote:

I would suggest that people who compile new kernels should:

- NOT do so in /usr/src. Leave whatever kernel (probably only the
header files) that the distribution came with there, but don't touch
it.

- compile the kernel in their own home directory, as their very own
selves. No need to be root to compile the kernel. You need to be root
to _install_ the kernel, but that's different.

- not have a single symbolic link in sight (except the one that the
kernel build itself sets up, namely the "linux/include/asm" symlink
that is only used for the internal kernel compile itself)

And yes, this is what I do. My /usr/src/linux still has the old 2.2.13
header files, even though I haven't run a 2.2.13 kernel in a _loong_
time. But those headers were what glibc was compiled against, so those
headers are what matches the library object files.

And this is actually what has been the suggested environment for at
least the last five years. I don't know why the symlink business keeps
on living on, like a bad zombie. Pretty much every distribution still
has that broken symlink, and people still remember that the linux
sources should go into "/usr/src/linux" even though that hasn't been
true in a _loong_ time.

Is there some documentation file that I've not updated and that people
are slavishly following outdated information in? I don't read the
documentation myself, so I'd never notice ;)

Linus

and this is the reference to it:

http://uwsg.iu.edu/hypermail/linux/k...07.3/0587.html

Maybe you will read it and learn, rkrishna, but most guys don't. :(

rkrishna · 08-06-2005, 07:10 AM

When i boot
boot: Slackware %name in lilo
Linux Slackware
BIOS.data check successfull
Uncompressing linux .......OK, booting the kernel
one page will scroll suddently within 2 sec %as usual

but suddently it iwll halt with
above lines and
Linux version 2.6.12.3test (root & ibmlinphysics)(gcc version 3.3.4)#2 fri Aug5 22

Quote:

I also notice that you issued
cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-2.6.5
which named your kernel image incorrectly.

that was a fault i changed in first post

Quote:

It should be vmlinuz-2.6.12.3test according to the rest of your post.

but it is not vmlinuz-2.6.12.3test but it is vmlinuz-2.6.12.3 only i dont understand why this test appears %i remember somewhere i added tht thing but dont know exactly

i compile it through
****************
from /usr/src

rm -f linux
ln -s linux-2.6.12.3 linux
cd /linux

cp /usr/src/linux-2.4.29/.config /usr/src/linux
make oldconfig
make
su -c "make modules_install"
make install

Bruce Hill · 08-06-2005, 07:29 AM

Okay, please forgive me if my words sound harsh. I think maybe next week I will post a 2.6 kernel build guide in Slackware. ;)

You now have 3 different names for your kernel in our posts:
2.6.12.3test
vmlinuz-2.6.5
linux-2.6.0

We need to find out which kernel source you downloaded.
Can you give the name of it? Is it linux-2.6.12.3.tar.bz2 ?

And one major problem I see is that you used your 2.4 kernel
.config file for a 2.6 kernel. You should not do that. The reason
to use an old .config file is to start the new kernel with the
same options as the old kernel which works. But you can't use
2.4 configuration for 2.6 kernels, because too much has changed.

At this point it would be best to relink your original kernel, and
remove the one you just built from /usr/src/

Please post name of the file you used as kernel source, whether
it is linux-2.6.12.3.tar.bz2 or some other one.

And please post the output of
"ls -al /usr/src/"
and also of
"ls -al /usr/src/linux"
and also of
"ls -al /boot/"
so we can see what you have now.

We will go from there.

rkrishna · 08-06-2005, 08:10 AM

linux-2.6.12.3.tar.bz2 this is the thing i downloaded and extracted to /usr/src/

ls -al /boot/
total 10323
drwxr-xr-x 3 root root 592 2005-08-06 16:39 .
drwxr-xr-x 19 root root 440 2005-08-05 19:38 ..
lrwxrwxrwx 1 root root 37 2005-05-09 21:07 README.initrd -> /usr/doc/mkinitrd-1.0.1/README.initrd
-rw-r--r-- 1 root root 971293 2005-08-05 22:52 System.map
-rw-r--r-- 1 root root 607998 2005-01-21 08:24 System.map-ide-2.4.29
-rw-r--r-- 1 root root 973166 2005-08-05 15:29 System.old
-rw-r--r-- 1 root root 512 2005-05-09 21:37 boot.1600
-rw-r--r-- 1 root root 168 2005-05-09 21:37 boot_message.txt
lrwxrwxrwx 1 root root 17 2005-05-09 21:06 config -> config-ide-2.4.29
-rw-r--r-- 1 root root 41731 2005-01-21 08:24 config-ide-2.4.29
-rw-r--r-- 1 root root 5032 2004-05-21 11:19 diag1.img
drwxr-xr-x 8 root root 304 2005-08-06 16:36 initrd-tree
-rw------- 1 root root 256541 2005-08-06 16:36 initrd.gz
-rw------- 1 root root 63488 2005-08-06 15:54 map
-rw-r--r-- 1 root root 1696730 2005-08-05 22:52 vmlinuz
-rw-r--r-- 1 root root 1696730 2005-08-06 15:52 vmlinuz-2.6.12.3
-rw-r--r-- 1 root root 1253760 2005-01-21 08:24 vmlinuz-ide-2.4.29
-rw-r--r-- 1 root root 1285372 2005-08-04 22:34 vmlinuz.1
-rw-r--r-- 1 root root 1677233 2005-08-05 15:29 vmlinuz.old

bash-3.00# ls -al /usr/src/linux
lrwxrwxrwx 1 root root 14 2005-08-05 12:33 /usr/src/linux -> linux-2.6.12.3

bash-3.00# ls -al /usr/src/
total 6
drwxrwx--- 6 root users 192 2005-08-05 12:33 .
drwxr-xr-x 21 root root 600 2005-08-05 22:55 ..
lrwxrwxrwx 1 root root 14 2005-08-05 12:33 linux -> linux-2.6.12.3
drwxr-xr-x 15 root root 816 2005-08-04 22:34 linux-2.4.29
drwxr-xr-x 19 root root 1248 2005-08-05 22:52 linux-2.6.12.3
drwxr-xr-x 7 root root 168 2003-10-29 10:08 rpm
drwxr-xr-x 2 root root 176 2005-01-21 02:31 speakup-2.4.29
b

i jsut copied the old .config as directed and run make oldconfig then make gconfig to edit all

rkrishna · 08-06-2005, 08:20 AM

Quote:

Okay, please forgive me if my words sound harsh. I think maybe next week I will post a 2.6 kernel build guide in Slackware.

hi tht is ok

here is my lilo.conf
# Linux bootable partition config begins
image = /boot/vmlinuz.1
root = /dev/hdc1
append="hda=ide-scsi"
label = Slackware.1
read-only
#
image = /boot/vmlinuz-2.6.12.3
root = /dev/hdc1
label = Slackware
read-only
#
image = /boot/vmlinuz.old
root = /dev/hdc1
append="hda=ide-scsi"
label = Slack.old
read-only
# Linux bootable partition config ends

Bruce Hill · 08-06-2005, 10:14 AM

This may sound like drastic measures to you, but I would:

1) su - (switch user to root and root's environment)
2) cd /usr/src
3) rm linux
4) ln -s /usr/src/linux /usr/src/linux-2.4.29
5) print or at least save your 2.6.12.3 .config file to read, but not to use in your system
6) rm -rf linux-2.6.12.3

Then make a directory for building kernels, since it sounds like
you are ready to do that on your system. From /home/<username>
"mkdir /home/<username>/build/"
and then copy linux-2.6.12.3.tar.bz2 into that directory from
wherever it is now; then untar it by issuing as a normal user
"tar -xvjf linux-2.6.12.3.tar.bz2" then "cd linux-2.6.12.3" and
now we're ready to start fresh.

This is why I told you to copy your 2.6.12.3 .config file, or to
print it. You don't want to use it to "make oldconfig" because
you made it after using a 2.4 .config, so it will not have the
correct 2.6 configuration. So just look at the choices you made
in either the printed version, or in a terminal if you want to
read it from your drive, but do not run "make oldconfig" and use
it.

Issue as a normal user "make gconfig" or "make xconfig" if you
have a preference. Now you can choose the support you picked
in the 2.6.12.3 .config file you saved. Be sure to look carefully for
anything you might have missed last time. After you are finished,
then you can save the new .config file you just made in
/home/<username>/build/linux-2.6.12.3/

Issue as a normal user "make" and after it finishes you will need
to issue "su" to switch to root to finish. Stay in the same directory,
there is no reason to cd to anywhere else. Now as root issue
"cp System.map /boot/System.map-2.6.12.3 ; ln -sf /boot/System.map-2.6.12.3 /boot/System.map"
and note that those two commands are run at one time, and that
the semi-colon (;) separates them. You can copy and paste that.

Issue "make modules_install" to install your modules. Then issue
"cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.12.3" to copy your
new kernel image to the place where your bootable kernel is found.

Now add that new kernel image to your bootloader, which I am
assuming is LiLO. Still in the same directory as root issue
"pico /etc/lilo.conf" (or use your favorite editor) and add this

Code:

	 image = /boot/vmlinuz-2.6.12.3
	   root = /dev/sda1  <-- put your / (root) partition here 
	   label = 2.6.12.3
	   read-only

after the line in LiLO that says
# Linux bootable partition config begins

Make sure you still have your 2.4.29 image in LiLO, so that you can
boot to it if your new kernel does not work. Now you can issue
"/sbin/lilo" and if there are no errors, close out all apps and reboot.

I did not tell you to remove the System.map files in /boot because I
don't know when you created them or which kernel they belong to.
You have System.map-ide-2.4.29 and now you will also have the new
System.map-2.6.12.3 and those will be found without a symlink.

I did not tell you to remove the vmlinuz files from /boot because you
have vmlinuz-ide-2.4.29 for your default kernel, and perhaps vmlinuz
for the 2.4.29 you compiled, and now you will have vmlinuz-2.6.12.3
which will be this new kernel image.

If you would like, before you do the above steps, post the /etc/lilo.conf
file you have now. We can help you edit it if you would like help.

Edit: Now that I have seen your /etc/lilo.conf you can omit the
steps in this post of editing /etc/lilo.conf and running /sbin/lilo because
your /etc/lilo.conf file is okay already.

Bruce Hill · 08-06-2005, 10:17 AM

Now that you have posted your /etc/lilo.conf I can tell you that you don't
need to edit your /etc/lilo.conf and you don't need to run /sbin/lilo because
you already have the correct entries in /etc/lilo.conf

gbonvehi · 08-06-2005, 11:39 AM

Quote:

Originally posted by Chinaman
... and you don't need to run /sbin/lilo because
you already have the correct entries in /etc/lilo.conf

Lilo must be run when you're adding or updating a kernel that's going to be loaded by it.

rkrishna · 08-06-2005, 01:04 PM

will b back soon was making menuconfig newly so very late

but some questions
why didnt we do make mrproper %not needed for newly unziped folder hi

in kernel 2.4.xx there were much more stufs like "make bzImage " and all but here nothing like tht

what all files will be created in boot while compiling new kernel
what about config-ide-2.xx, vmlinuz-ide-2.xx and system.map-ide %it was tehre pat made tht

wht about intrid.img actually pat described about tht in. README.initrid IN BOOT FOLDER
******Slackware initrd mini HOWTO***
i tried to make tht thing there was also error

i cant understand why there was a folder named 2.6.12.3test in /lib/modules/2.6.12.3test/
my image was uncompressing but suddently stopping???

will b back after this compilation

rkrishna · 08-06-2005, 02:48 PM

thank u Chinaman for the help will b back soon

Bruce Hill · 08-06-2005, 05:44 PM

Quote:

Originally posted by gbonvehi
Lilo must be run when you're adding or updating a kernel that's going to be loaded by it.

You know, he's right, and I stand corrected. I have recompiled a kernel to change one little thing, like the I/O scheduler specifically, and it booted right back into it. But I never realized it was the same kernel # but not the new compile.

I just rebuilt the kernel on workstation here to remove ACPI, and test what I posted. When I issued:

Code:

mingdao@james:~/build$ uname -a
Linux james 2.6.12.3 #2 Sun Jul 24 09:25:23 CST 2005 i686 AMD Athlon(TM) XP 2600+ AuthenticAMD GNU/Linux

I see that I'm still running the old kernel (today is )

So thank you for pointing out my error so graciously. The reason for this, I believe, is because:

Quote:

"Linux LILO: The program, lilo, which resides on /sbin/lilo is a program that is used to install a boot loader on a boot media such as a hard or floppy drive. If the kernel is modified, lilo must be rerun. The boot loader that lilo creates accesses a map of disk blocks that are in the kernel file."

So if you don't rerun /sbin/lilo it does not really write a new boot sector or map file.

Thanks for pointing out my error gbonvehi !

Bruce Hill · 08-06-2005, 06:42 PM

Quote:

Originally posted by rkrishna
will b back soon was making menuconfig newly so very late

but some questions
why didnt we do make mrproper %not needed for newly unziped folder hi;)
in kernel 2.4.xx there were much more stufs like "make bzImage " and all but here nothing like tht

Those steps are not necessary for 2.6.x ... read the ./linux-2.6.12.3/README file
and the ./linux-2.6.12.3/Makefile to see that make does these steps now.

Quote:

what all files will be created in boot while compiling new kernel
what about config-ide-2.xx, vmlinuz-ide-2.xx and system.map-ide %it was tehre pat made tht

Nothing is created in /boot while compiling the kernel. You will get the
System.map that is created in ./linux-2.6.12.3/ and the bzImage that is
created in ./linux-2.6.12.3/arch/i386/boot/ when you issue thse two
commands I gave you:
"cp System.map /boot/System.map-2.6.12.3 ; ln -sf /boot/System.map-2.6.12.3 /boot/System.map"
"cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.12.3"
previously.

Quote:

wht about intrid.img actually pat described about tht in. README.initrid IN BOOT FOLDER
******Slackware initrd mini HOWTO***
i tried to make tht thing there was also error

Pat has you make an initrd.img for his generic kernels because he does not have
support built into them for any filesystem except ext2; so for instance, if your /
partition is ReiserFS, as mine are, you can't boot his generic kernel. If you have
compiled support into your kernel for your / filesystem, you probably don't need
an initial ramdisk. From "man mkinitrd"

Quote:

DESCRIPTION
mkinitrd is used to build an initial ramdisk. An initial ramdisk is a very small Linux filesystem that is loaded into RAM and mounted as the
kernel boots (before the main root filesystem is mounted). The usual reason to use an initrd is because you need to load kernel modules before
mounting the root partition. Usually these modules are required to support the filesystem used by the root partition (ext3, reiserfs, xfs), or
perhaps the controller that the hard drive is attached to (SCSI, RAID, etc). Essentially, there are so many different options available in mod-
ern Linux kernels that it isn't practical to try to ship many different kernels to try to cover everyone's needs. It's a lot more flexible to
ship a generic kernel and a set of kernel modules for it.

Since you're not running a generic kernel, but are compiling a custom kernel, make
sure you include support (Y not M) for your / filesystem.

Quote:

i cant understand why there was a folder named 2.6.12.3test in /lib/modules/2.6.12.3test/

The only way I know of that you can do this is to edit the kernel Makefile.
Note that there is an additional EXTRAVERSION field. To prevent overwriting
any existing kernel modules on the system if you rebuild the same kernel version,
you change this EXTRAVERSION to something unique. When the final installation
steps are run, kernel module files will then get written to
/lib/modules/$VERSION.$PATCHLEVEL.$SUBLEVEL-$EXTRAVERSION.

So you must have edited ./linux-2.6.12.3/Makefile and changed
EXTRAVERSION = .3
to
EXTRAVERSION = .3test
which would then cause your module directory to have that name. You can
read in the kernel Makefile that make creates

Code:

# Objects we will link into vmlinux / subdirs we need to visit
init-y          := init/
drivers-y       := drivers/ sound/
net-y           := net/
libs-y          := lib/
core-y          := usr/

which you will find in ./linux-2.6.12.3/ after you run make, and then
"make modules_install" will install them at /lib/modules/`uname -r`/
for you all nice and tidy.

So, you have changed your EXTRAVERSION to .3test, and that is what
your modules were named. When unpack the source under your /home
directory, don't edit that Makefile unless you know why you are changing
what you edit.

Quote:

my image was uncompressing but suddently stopping???

I don't know either, without looking at your .config file, etc. Just do it the
way we've outlined here, and it should be okay. If you read DaOne's guide
again, skip down to that post by Jymbo, which adds some information that
is valuable.

rkrishna · 08-07-2005, 08:28 AM

every thing gone well as u suggested and now i can boot to my new kernel

but one problem as the system boots, my fonts are big, earlier it will become small after some time while booting (and i could c all the messaegsin one window)% Frame Buffer test Console
now my lilo part is like this

# VESA framebuffer console @ 1024x768x256
#vga = 773 %shoud i uncomment htis line
# Normal VGA console
vga = normal %comment this line
# VESA framebuffer console @ 1024x768x64k
# vga=791

wil it work if i uncommented #vga = 773 line and run lilo

Is the booting time of 2.6.xx is greater than 2.4, because while uncompressing the older imaeg it is like a flash but the new one it is slow i can c every line by line scroling.
%where can i c whatever modules are loded while booting or boot message %boot log file

Quote:

If you have
compiled support into your kernel for your / filesystem, you probably don't need
an initial ramdisk.

ok i will look for tht but, even then, the initrid image was not listed in the initial lilo.conf %teh generic kernel
i just gone thorough the intrid.read me by pat in /boot there he described how to make tht thing for diff file systems

from now onwards i will read each and every how to files ,

but i trusted, trust the LQ things %%%

Quote:

If you read DaOne's guide
again, skip down to that post by Jymbo,

s i had already gone thrugh tht one and saved tht, with one script too

thanking u for this much help and discussion, and expect more from next thread onwrds
%i am sitting in a pool of windows machine and everbody moking at me for using linux no help from this side, stil surviving
regards