Kernel Compile Guide for 2.6.0

lokee · 12-22-2003, 07:13 AM

/dev/pts is no longer added by default, so you must select it (Device Drivers->FS->Pseudo FS)....
Unless you plan to never use a terminal.

beyondzero · 12-22-2003, 08:54 AM

Some excellent advice in the thread - got me up and running with the new kernel after I had a few problems first time round!

For my future reference I put together a quick guide from everyones advice and have posted it on my site - http://www.randomwire.com/articles.p...cle=kernel.php - hope it might be of help to someone else!

kc00l · 12-22-2003, 10:34 AM

I've read your compile guide for kernel 2.6.0, beyondzero.
That's a complete and quick guide to solve all those problems pointed out by a number of post in this forum.

I would suggest to put the kernel source tree in a home directory and then:

$su -c "ln -s /home/username/linux-2.6.0 /usr/src/linux"

This kind of procedure is even in the kernel source tree README

Quote:

INSTALLING the kernel:

- If you install the full sources, put the kernel tarball in a
directory where you have permissions (eg. your home directory) and
unpack it

Having the kernel source tree in your home directory has the following advantages:[list=1][*]Normal users stay root for a safe amount of time.[*]/usr directory doesn't grow too big in size.[*]Normal users can normally 'make xconfig' without the need of being root.[/list=1]

Feel free to add other advantages as indeed there are more.

beyondzero · 12-22-2003, 11:54 AM

Good advice, I've updated the guide with your suggestions

ZiGiE · 12-22-2003, 12:01 PM

Here's a little script I wrote and run everytime after I compile new kernel.
Note: You still need to edit lilo.conf and run lilo!!!

Code:

#!/bin/sh
BOOT=/boot ;

usage()
{
        echo "Usage: install_kernel <version>" 1>&2
        exit 1
}

if [ ! $# == 1 ]; then usage; fi

VERSION=$1 ;
cp -vi .config ${BOOT}/config-${VERSION} ;
cp -vi System.map ${BOOT}/System.map-${VERSION} ;
cp -vi arch/i386/boot/bzImage ${BOOT}/vmlinuz-${VERSION} ;

ln -siv ${BOOT}/config-${VERSION} ${BOOT}/config ;
ln -siv ${BOOT}/System.map-${VERSION} ${BOOT}/System.map ;
ln -siv ${BOOT}/vmlinuz-${VERSION} ${BOOT}/vmlinuz ;

So, after I compile my kernel like this:

Code:

cd /usr/src/linux
make mrproper
cp ~/kernelconfigs/.config .config
make menuconfig
make
su -c 'make modules_install'

I just run my script: su -c 'install_kernel 2.6.0', update my /etc/lilo.conf with something like this:

Code:

image = /boot/vmlinuz-2.6.0
  root = /dev/hda2
  label = Lin-2.6.0
  read-only

run su -c lilo and reboot.

tomdkat · 12-22-2003, 09:21 PM

Quote:

Originally posted by beyondzero
For my future reference I put together a quick guide from everyones advice and have posted it on my site - http://durham.randomwire.com/kernel.php - hope it might be of help to someone else!

How did you get the kernel built from the 2.6.0 sources without running into the problems described here:

http://www.linuxquestions.org/questi...hreadid=128144

The procedure you describe is basically the same procedure I've been following for years and I'm puzzled as to why I'm having problems with the "asm" directories and locating errno headers.

Thanks...

Peace...

kc00l · 12-23-2003, 05:22 AM

Quote:

Originally posted by ZiGiE
[B]Here's a little script I wrote and run everytime after I compile new kernel.
Note: You still need to edit lilo.conf and run lilo!!!
(snip)

Nice script, I'll save it in my ~

Oh, and why don't you put something in the second line to get some credit?

Code:

#!/bin/bash
# Install Kernel Script by ZiGiE from LQ-Slackware

IffikaS · 12-25-2003, 10:50 AM

i cant still hget rid of the blank screen problem ???
can someone help

tomdkat · 12-25-2003, 10:57 AM

Quote:

Originally posted by IffikaS
i cant still hget rid of the blank screen problem ???
can someone help

Ok, here is something I did. It's not elegant, but it works.

Boot your machine and let the blank screen appear and wait until the disk activity stops. Then login and _somehow_ get X started. On my system (Slackware 8), it boots to runlevel 3 which doesn't start X and I start X by manually switching to runlevel 4 (which is the way I just prefer to do things).

The main point is, boot the box and get X started. Once X is started login and open a shell window and edit your lilo.conf file and change the "vga =" line to "vga = ask". Save the file and reboot.

Now, when lilo starts it will prompt you for the video mode to use for the boot process.

Good luck!

Peace...

IffikaS · 12-25-2003, 11:30 AM

thank you it really helps, but still is there some way to get vga console working ? Has anyone got it or not

tomdkat · 12-25-2003, 12:44 PM

Quote:

Originally posted by IffikaS
thank you it really helps, but still is there some way to get vga console working ? Has anyone got it or not

I'm sure there is, but at this point having a low-res console is better than a blank screen.

If the "vga = ask" works for you, then you will at least NOT have a blank screen until you get your VGA frambuffer console issues worked out.

What kind of graphics card do you have and how do you have the kernel configured for framebuffer console support?

Peace...

IffikaS · 12-25-2003, 12:54 PM

Quote:

Originally posted by tomdkat
I'm sure there is, but at this point having a low-res console is better than a blank screen.

If the "vga = ask" works for you, then you will at least NOT have a blank screen until you get your VGA frambuffer console issues worked out.

What kind of graphics card do you have and how do you have the kernel configured for framebuffer console support?

Peace...

of course it's better than blank one. I have on of those Nvidia GeForce 2 MX 400 . there is no drivers ment for geforce but i enabled the riva - but it doesnt help

karthikrr · 12-25-2003, 01:01 PM

dont bother with riva... just enable only vesa...

IffikaS · 12-25-2003, 01:33 PM

ok but still - i have one major problem - i can't get my tv card working. It Leadtek winfast TV 2000 XP deluxe it ran very good with 2.4.23, but now it doesnt work .

I use tvtime and it says " Cannot open capture device /dev/video0 " ???

IffikaS · 12-25-2003, 01:36 PM

maybe the problem is that there is no option with kernel compiling because a i used to need this option:

Multimedia Devices -> Video For Linux -> V4L Information in the proc filesystem (Y)

But now there is no