Compile Kernel 2.6 under Debian Sarge

[falko]

This is a little bit different from compiling a kernel 2.6 on Debian Woody because Sarge uses grub as the boot loader (instead of lilo) and because module-init-tools, initrd-tools, procps are already installed. After all it's similar to http://www.howtoforge.com/howto_linux_kernel_2.6_compile_debian. This is how you do it:

apt-get install kernel-package libncurses5-dev fakeroot wget bzip2
cd /usr/src
wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.11.7.tar.bz2
tar xjf linux-2.6.11.7.tar.bz2
cd linux-2.6.11.7/
make menuconfig

It is normally a good idea to take the configuration of your existing (working!) kernel 2.6 as a starting point for the configuration of your new kernel. Usually the current kernel configuration is saved in a file under /boot, e.g. /boot/config-2.6.3. I will load this configuration and then do the changes I desire. If you do not have the config file of a working kernel 2.6 this one might help you: http://www.falkotimme.com/howtos/debian_kernel2.6_compile/config-2.6.8.1

make-kpkg clean
fakeroot make-kpkg --initrd --revision=custom.1.0 kernel_image

If the compilation stops with an error, run

make clean

and then re-run the previous commands starting with

make menuconfig

Go ahead with

cd ../
dpkg -i kernel-image-2.6.11.7_custom.1.0_i386.deb

This will install your new kernel (including a ramdisk) and also update grub. You can now reboot your system, and you should then have a new kernel. You can check that by running:
uname -a

[tylerdurden]

Nice walkthrough, thanks! :)

tyler

[floobit]

after running the apt-get update with these sources:
deb http://security.debian.org/ stable/updates main contrib non-free
deb http://secure-testing.debian.net/debian-secure-testing testing/security-updates main contrib non-free
deb http://http.us.debian.org/debian/ stable main contrib non-free
deb http://http.us.debian.org/debian/ testing main contrib non-free
deb http://http.us.debian.org/debian/ unstable main contrib non-free
deb http://debian.kcore.org/ ./

I started following the instructions. On the first line

apt-get install kernel-package ncurses-dev fakeroot wget bzip2
I encountered 2 errors. First, it informed me that:
Reading Package Lists...
Building Dependency Tree...
Package ncurses-dev is a virtual package provided by:
libncurses5-dev 5.4-9
You should explicitly select one to install.
and it installed none of the packages

so, I removed the ncurses-dev from the install list and tried again. this time, all packages were installed, but it prompted me for if I wanted to stop gdm before I installed glibc. This was slightly weird, because I logged in as "repair" from grub. also, I don't believe gdm was running, because ps -A yielded:

PID TTY TIME CMD
1 ? 00:00:00 init
2 ? 00:00:00 ksoftirqd/0
3 ? 00:00:00 events/0
4 ? 00:00:00 khelper
5 ? 00:00:00 kacpid
35 ? 00:00:00 kblockd/0
45 ? 00:00:00 pdflush
46 ? 00:00:00 pdflush
48 ? 00:00:00 aio/0
47 ? 00:00:00 kswapd0
184 ? 00:00:00 kseriod
293 ? 00:00:00 kjournald
346 ? 00:00:00 udevd
1452 ? 00:00:00 khubd
2731 ? 00:00:00 dhclient
2736 ? 00:00:00 portmap
3083 tty1 00:00:00 init
3101 tty1 00:00:00 bash
3497 tty1 00:00:00 ps

I chose to install glibc anyway, but can easily start over if I need to.

Thanks,
Dylan Evans

[falko]

after running the apt-get update with these sources:
deb http://security.debian.org/ stable/updates main contrib non-free
deb http://secure-testing.debian.net/debian-secure-testing testing/security-updates main contrib non-free
deb http://http.us.debian.org/debian/ stable main contrib non-free
deb http://http.us.debian.org/debian/ testing main contrib non-free
deb http://http.us.debian.org/debian/ unstable main contrib non-free
deb http://debian.kcore.org/ ./

I started following the instructions. On the first line

apt-get install kernel-package ncurses-dev fakeroot wget bzip2
I encountered 2 errors. First, it informed me that:
Reading Package Lists...
Building Dependency Tree...
Package ncurses-dev is a virtual package provided by:
libncurses5-dev 5.4-9
You should explicitly select one to install.
and it installed none of the packages

so, I removed the ncurses-dev from the install list and tried again. this time, all packages were installed, but it prompted me for if I wanted to stop gdm before I installed glibc. This was slightly weird, because I logged in as "repair" from grub. also, I don't believe gdm was running, because ps -A yielded:

PID TTY TIME CMD
1 ? 00:00:00 init
2 ? 00:00:00 ksoftirqd/0
3 ? 00:00:00 events/0
4 ? 00:00:00 khelper
5 ? 00:00:00 kacpid
35 ? 00:00:00 kblockd/0
45 ? 00:00:00 pdflush
46 ? 00:00:00 pdflush
48 ? 00:00:00 aio/0
47 ? 00:00:00 kswapd0
184 ? 00:00:00 kseriod
293 ? 00:00:00 kjournald
346 ? 00:00:00 udevd
1452 ? 00:00:00 khubd
2731 ? 00:00:00 dhclient
2736 ? 00:00:00 portmap
3083 tty1 00:00:00 init
3101 tty1 00:00:00 bash
3497 tty1 00:00:00 ps

I chose to install glibc anyway, but can easily start over if I need to.

Thanks,
Dylan Evans

Have you been successful in installing your new kernel, or did you encounter problems?

[floobit]

My kernel compiled completely with some warnings. When I rebooted, it gave me a
VFS: Cannot open root device "hdb1" or unknown block (0,0)
kernel panic: not syncing: unable to mount root fs on unknown-block(0,0)

I have two physical HDs, one 6.4 gig (primary slave) with / and a swap on it, and a 80 gig with windows and /home and a swap. I believe the ramdrive installed correctly (at least no errors popped up) and I used my earlier kernel as a start point, and it boots fine. Any ideas?

Dylan

[falko]

What's in /boot/grub/menu.1st?

[floobit]

title Debian GNU/Linux, kernel 2.6.13.4
root (hd1,0)
kernel /boot/vmlinuz-2.6.13.4 root=/dev/hdb1 ro
savedefault
boot

+ an identical (recovery mode)

and my vanilla kernel

Dylan

[falko]

I need to see the whole file, not just an excerpt.

[floobit]

# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 5

# Pretty colours
color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specifiv kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
# kopt=root=/dev/hdb1 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd1,0)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery mode) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## ## End Default Options ##

title Debian GNU/Linux, kernel 2.6.13.4
root (hd1,0)
kernel /boot/vmlinuz-2.6.13.4 root=/dev/hdb1 ro
savedefault
boot

title Debian GNU/Linux, kernel 2.6.13.4 (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.13.4 root=/dev/hdb1 ro single
savedefault
boot

title Debian GNU/Linux, kernel 2.6.8-2-k7
root (hd1,0)
kernel /boot/vmlinuz-2.6.8-2-k7 root=/dev/hdb1 ro
initrd /boot/initrd.img-2.6.8-2-k7
savedefault
boot

title Debian GNU/Linux, kernel 2.6.8-2-k7 (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.8-2-k7 root=/dev/hdb1 ro single
initrd /boot/initrd.img-2.6.8-2-k7
savedefault
boot

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/hda1
title Microsoft Windows XP Professional
root (hd0,0)
savedefault
makeactive
chainloader +1

[falko]

You have no initrd line for your new kernel. Maybe that causes the error.

[floobit]

I added a initrd line to my menu.lst, and it booted wonderfully - thanks a bunch! However, when compiling, I had installed the latest gcc (4.0) and g++, but it said it would use the earlier 3.3 version to compile the kernel. does this mean if I compile any modules (like the latest nvidia driver), they will use gcc/g++ 4.0, and won't be compatible with my kernel? Is there a way to check (to see if I'm wrong) which g++/gcc compiler I used?

Dylan

[falko]

does this mean if I compile any modules (like the latest nvidia driver), they will use gcc/g++ 4.0, and won't be compatible with my kernel?I don't think so. I'd try it.

[JL84]

I went through the whole process of upgrading to kernel 2.6 and I made sure that the initr-img was in the right place, but when I loaded with the new kernel 2.6 it gave me another error. The boot was trying to find /sbin/init/ and /dev/console/ where would those be entered in so that the kernel can load?

[Iwan]

Works great except I had to

apt-get install yaird

aswell ;)

[Januss]

I went through the whole process of upgrading to kernel 2.6 and I made sure that the initr-img was in the right place, but when I loaded with the new kernel 2.6 it gave me another error. The boot was trying to find /sbin/init/ and /dev/console/ where would those be entered in so that the kernel can load?
Hi,
I had the same problem with my upgrade to 2.6.8.
At first the kernel didn't boot at all, but after i
did mkinitrd and added the initrd image to grub menu.lst I had the same results as you had written.
As it turned out, I forgot to compile ext3 support into the kernel, which is needed if you have ext3 as the root fs (/).

Hope this helps someone.

[stevendemetrius]

after running the apt-get update with these sources:
deb http://security.debian.org/ stable/updates main contrib non-free
deb http://secure-testing.debian.net/debian-secure-testing testing/security-updates main contrib non-free
deb http://http.us.debian.org/debian/ stable main contrib non-free
deb http://http.us.debian.org/debian/ testing main contrib non-free
deb http://http.us.debian.org/debian/ unstable main contrib non-free
deb http://debian.kcore.org/ ./

I started following the instructions. On the first line

apt-get install kernel-package ncurses-dev fakeroot wget bzip2
I encountered 2 errors. First, it informed me that:
Reading Package Lists...
Building Dependency Tree...
Package ncurses-dev is a virtual package provided by:
libncurses5-dev 5.4-9
You should explicitly select one to install.
and it installed none of the packages

so, I removed the ncurses-dev from the install list and tried again. this time, all packages were installed, but it prompted me for if I wanted to stop gdm before I installed glibc. This was slightly weird, because I logged in as "repair" from grub. also, I don't believe gdm was running, because ps -A yielded:

PID TTY TIME CMD
1 ? 00:00:00 init
2 ? 00:00:00 ksoftirqd/0
3 ? 00:00:00 events/0
4 ? 00:00:00 khelper
5 ? 00:00:00 kacpid
35 ? 00:00:00 kblockd/0
45 ? 00:00:00 pdflush
46 ? 00:00:00 pdflush
48 ? 00:00:00 aio/0
47 ? 00:00:00 kswapd0
184 ? 00:00:00 kseriod
293 ? 00:00:00 kjournald
346 ? 00:00:00 udevd
1452 ? 00:00:00 khubd
2731 ? 00:00:00 dhclient
2736 ? 00:00:00 portmap
3083 tty1 00:00:00 init
3101 tty1 00:00:00 bash
3497 tty1 00:00:00 ps

I chose to install glibc anyway, but can easily start over if I need to.

Thanks,
Dylan Evans


Check the command you typed. It should be "libncurses5-dev" not "ncurses-dev"

[stevendemetrius]

Do you know the type of file system on your boot drive? It must be complied in the kernel and *not* as a module. This is set in the kernel configuration.

If you boot file system is ext3 then when you configure the kernel then the ext3 file system must be marked to be compiled in the kernel.

[Flip]

Ill get this error,
Pivot_root: No such file or directory
/sbin/init: 432: cannot open dev/console: No such file
Kernel panic - not syncing: Attempted to kill init:

This is my /boot/grub/menu.lst


# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 20

# Pretty colours
color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specifiv kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
# kopt=root=/dev/hda1 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery mode) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## ## End Default Options ##

title Debian GNU/Linux, kernel 2.6.15.6
root (hd0,0)
kernel /boot/vmlinuz-2.6.15.6 root=/dev/hda1 ro
initrd /boot/initrd.img-2.6.15.6
savedefault
boot

title Debian GNU/Linux, kernel 2.6.15.6 (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.15.6 root=/dev/hda1 ro single
initrd /boot/initrd.img-2.6.15.6
savedefault
boot

title Debian GNU/Linux, kernel 2.6.11.7
root (hd0,0)
kernel /boot/vmlinuz-2.6.11.7 root=/dev/hda1 ro
initrd /boot/initrd.img-2.6.11.7
savedefault
boot

title Debian GNU/Linux, kernel 2.6.11.7 (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.11.7 root=/dev/hda1 ro single
initrd /boot/initrd.img-2.6.11.7
savedefault
boot

title Debian GNU/Linux, kernel 2.4.27-2-386
root (hd0,0)
kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hda1 ro
initrd /boot/initrd.img-2.4.27-2-386
savedefault
boot

title Debian GNU/Linux, kernel 2.4.27-2-386 (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hda1 ro single
initrd /boot/initrd.img-2.4.27-2-386
savedefault
boot

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root



Can you help me?

[falko]

Can you post your /etc/fstab here?

[Flip]

This is my /etc/fstab


# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/hda1 / ext3 defaults,errors=remount-ro 0 1
/dev/hda5 none swap sw 0 0
/dev/hdc /media/cdrom0 iso9660 ro,user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
/dev/hdb1 /home ext3 defaults,errors=remount-ro 0 1

[falko]

/etc/fstab and /boot/grub/menu.lst look ok...

[Flip]

Ok I thinks thats ok then. You don't have any onther idea's?:confused:

[falko]

Not really...

[Flip]

OK, thats not so nice than. Could the problem been solved if I give you acces to my server? Hopefully you find something;(

[falko]

This would be professional support then, and I'd have to charge you for that. If you're interested, please PM me.

[Flip]

No, than I'm not interested. Thanks anyway

[Layn]

Hello Flip,
Have you add support for your file system? and ide support, i think you you have a problem with something about disc (ide, filesystem...)
If you add this support as module, then you can to put this modules into the /etc/mkinitrd/modules.


...Layn.

[Flip]

I don't know exactly

[falko]

You can check the kernel config file in /boot to see what is enabled and what isn't.

[Flip]

Here you can find my config file:
http://attic.flipeend.nl/config-2.6.15.6

[falko]

And which file system do you use? Please post your /etc/fstab here.

[Flip]

I had already done that in this post

http://www.howtoforge.com/forums/showpost.php?p=18755&postcount=20

[falko]

So you're using ext3, and ext3 is enabled as a module in your kernel.
Did you create a ramdisk or put the ext3 driver into /etc/mkinitrd/modules, as Layn suggested?

[Wraithfire]

Ok so I've been following this post now for about 5 days or so i guess. I seem to be having the exact same problem that Flip is. Following your initial instructions back at top, i finished with the same error message as Flip and i noticed as you pointed out falko that the initrd line was missing from /boot/grub/menu.lst So after editing that, i rebooted and got an error of unable to mount root unknown block (3,1) instead of (0,0). So it seems that maybe Layn is correct about the ext3 driver since i also enabled ext3 support in the make menuconfig. So how do I go about adding the ext3 driver into /etc/mkinitrd/modules file? Also, if i followed your instructions exactly falko, would that have created a ramdisk?

[falko]

So how do I go about adding the ext3 driver into /etc/mkinitrd/modules file?
Can you post the output of updatedb
locate ext | grep -i "/lib"?

Also, if i followed your instructions exactly falko, would that have created a ramdisk?Yes, that's right.

[Wraithfire]

OMFG I am such a noob :(
I got the system to boot up fine following your directions, I added ext3 to /etc/mkinitrd/modules. I had noticed from one of your earlier posts that the initrd line was missing from /boot/grub/menu.lst for Debian GNU/Linux, kernel 2.6.16 Default. So what i was doing was adding initrd /boot/initrd.img-2.6.16 to that section for Default and Default (Recovery). Then I just now noticed that /boot/initrd.img-2.6.16 was already on Debian GNU/Linux, kernel 2.6.16 a little bit farther down in the file. The difference between the 2 is that the second is not (Default), and they are listed the same way in the boot menu. So i left the initrd line out of the (Default) section, selected that at boot up menu and it loaded up great, version 2.6.16 So I guess I was pointing grub to a different kernel image then i should have?

[sbovisjb1]

Yes i quite agree...
also if you want to install custom dependincies, just create files(in the apt-get shell directory)that describes the location and the keys of updates... that way when ever you want to update anything you can have the files you want.

[chief_officer]

Hello,

I tried to update my kernel to 2.6.16.1 yesterday. I have downloaded the kernel to /usr/src and untar'ed it and then finished the menuconfig. When I typed

/usr/src/linux.2.6.16.1#make-kpkg clean


I get the following error message:

make:*** No rule to make target `kpkg-clean'. Stop.


Meantime, when I type

/usr/src/linux.2.6.16.1# fakeroot make-kpkg --initrd --revision=custom.1.0 kernel-image-2.6.16.1-custom_1.0.deb


I get the following error message:

Error: Unknown target kernel-image-2.6.16.1-custom_1.0.deb use --targets to display help on valid targets

I am following your tutorials from the following to update my kernel:
http://www.falkotimme.com/howtos/debian_kernel2.6_compile/index.php
http://www.howtoforge.com/forums/showthread.php?t=21

and also from official debian site:
http://www.debian.org/releases/sarge/i386/ch08s05.html.en

I did a fresh install of Debian Sarge on my Toshiba Satellite Pro 6100 [didn't do dist-upgrade]. And yes, I have never compiled a kernel before.

Regards,
Chief

[falko]

Please try to follow this: http://www.howtoforge.com/forums/showthread.php?t=21 to the letter. Maybe you made a typo somewhere or some other mistake.

[coolvik]

Hi,

thanks for the guide!

I've downloaded the 2.6.16.1 kernel and made the configuration.

Everything seems to work fine until I boot the system with the new kernel. It hangs almost at the end.

I've a Dual Xenon EM64t system. And thats why I want to use this later kernel version, becouse the regualr 2.6.8 em64t smp kernels don't work either.


Anyone with experiences in this?

[falko]

Do you see any error message?

[coolvik]

Hi,

yes I do.


when booting up this is written right before it stops:

mkdir: cannot create directory '/devfs/VG': Read-only file system
mount: unknown filesystem type 'devfs'
Unable to find volume group 'VG'
unmount: /dev: not mounted
unmount: devfs: not mounted
mount: unknown filesystem type 'devfs'
JFS: nTxBlock = 8192, nTxLock = 65536
unmount: devfs: not mounted
pivot_root: No such file or directory
/sbin/init: 432: cannot open /dev/console: No such file
Kernel panic - not syncing: Attempted to kill init!


And after that it hangs, I've to reset the server.

[falko]

I've fond this link: http://lists.debian.org/debian-amd64/2005/10/msg00848.html

[coolvik]

Hi,

thanks for the reply.

I just want to say that this is the first time I've compiled a kernel.

I tried what was suggested as in: http://lists.debian.org/debian-amd64/2005/10/msg00854.html

But I get the same error message when booting up.

Edit: Im not using AMD64 version of Debian.

[unkn0wn]

i flllow the instructions i remote recompile 2.6.14 with grsec but achine dont respond :)

but i can ping it.
i think 2.6 change run level to some other mode with minimal network?

your ideas?

ok
i check there is no error (on first look) system is booting corectly
i log on machnine (not remote) normaly but sshd is notstarted simple there is no services?? i try /etc/initd.d/ssh but there is no output??? just back me to prompt

[falko]

i check there is no error (on first look) system is booting corectly
i log on machnine (not remote) normaly but sshd is notstarted simple there is no services?? i try /etc/initd.d/ssh but there is no output??? just back me to prompt
Anything in the logs? Any errors in the output of dmesg?

[unkn0wn]

i compile it again with same steps.
but i put in /etc/fstab /sys sysfs and now its working :)

[Jamesk5]

I've got a problem - I'm new to debian, and did an apt-get upgrade to upgrade stuff that needed to be done.
It upgraded the kernel, and now I can't boot - I've got the same error as some others, where it wont find /dev/hda1.
Here's a copy of my menu.lst
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not change this entry to 'saved' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 5

# Pretty colours
color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=/dev/hda1 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery mode) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## ## End Default Options ##

title Debian GNU/Linux, kernel 2.6.15-1-486
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-1-486 root=/dev/hda1 ro
initrd /boot/initrd.img-2.6.15-1-486
savedefault
boot

title Debian GNU/Linux, kernel 2.6.15-1-486 (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-1-486 root=/dev/hda1 ro single
initrd /boot/initrd.img-2.6.15-1-486
savedefault
boot

### END DEBIAN AUTOMAGIC KERNELS LIST


This is probably going to make me sound like a real n00b, but I haven't changed the initrd from the .img-2.6.15......... to 16, because there is no img file in /boot for the new kernel.
Any advice?? Like I said, I can't boot into debia, so I'm in pretty unfamilular territory now, except for a trusty knoppix boot disk.

[falko]

This is probably going to make me sound like a real n00b, but I haven't changed the initrd from the .img-2.6.15......... to 16, because there is no img file in /boot for the new kernel.

I don't see a 2.6.16 kernel in your menu.lst...
Anyway, you can create a ramdisk like this:

cd /boot/
mkinitrd -o /boot/initrd.img-2.6.8.1 2.6.8.1(this example is for a 2.6.8.1 kernel, adjust it to your needs).

[Jamesk5]

I don't see a 2.6.16 kernel in your menu.lst...
Anyway, you can create a ramdisk like this:

cd /boot/
mkinitrd -o /boot/initrd.img-2.6.8.1 2.6.8.1(this example is for a 2.6.8.1 kernel, adjust it to your needs).


Can I make a RAM disk outside of being in Debian - If so, will knoppix work, and do I just use the usual bash prompt?
Also, what kernel number should I use, I'm not sure what it updated to - is there any way I can find out in system logs or something??

Thanks heaps!

[falko]

Can I make a RAM disk outside of being in Debian - If so, will knoppix work, and do I just use the usual bash prompt?
You should make it on the system where you installed the new kernel.

Also, what kernel number should I use, I'm not sure what it updated to - is there any way I can find out in system logs or something??

Have a look at the /boot directory - you should find your new kernel there.

[Jamesk5]

Have a look at the /boot directory - you should find your new kernel there.

What am I looking for in the /boot directory of the drive that holds Debian (As I said, I can't boot into Debian therefor I have to mount the drive in a knoppix session to see the contents of the drive)

In the /boot directory I have:
System.map-2.6.15-1-486
vmlinuz-2.6.15-1-486
config-2.6.15-1-486
initrd.img-2.6.15-1-486
grub/

My /boot/grub/menu.lst points to the /boot/initrd..... (initrd) and /boot/vmlinux..... (kernel) files and yet still wont boot.

[falko]

You only have a 2.6.15-1 kernel in /boot, but there's already an initrd.img for it...

[nrundle]

I installed Debian 3.1r2 today and wanted to upgrade the kernel (2.4.27) to (2.6.8). Tried a kernel image from the Debian dist with the resulting error


pivot_root: No such file or directory
/sbin/init: 432: cannot open dev/console: No such file
Kernel panic: Attempted to kill init!


I tried following your walkthrough to compiling a kernel. I even loaded my config for 2.4.27 to start from and it comes up with same error. Some output I noticed just prior to the error looks like this:


RAMDISK: cramfs filesystem found at block 0
RAMDISK: Loading 3580 blocks [1 disk] into ram disk... done.
VFS: Mounted root (cramfs filesystem) readonly.
Freeing unused kernel memory: 204k freed
initrd-tools: 0.1.81.1
NET: Registered protocol family 1
SCSI subsystem initialized
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebux=xx
ide0: I/O resource 0x1F0-0x1F7 not free.
ide0: ports already in use, skipping probe
hdc: SONY DVD+/-RW DW-Q58A, ATAPI CD/DVD-ROM drive
Using anticipatory io scheduler
ide1 at 0x170-0x177,0x376 on irq 15


It appears like it can't find the primary hd when loading the 2.6.8 kernel, but works fine under 2.4.27.

Any ideas what I need to do differently?

[falko]

I installed Debian 3.1r2 today and wanted to upgrade the kernel (2.4.27) to (2.6.8).
Why don't you install Sarge with a 2.6.8 kernel right from the beginning? When you boot from the install CD, type linux26 at the boot prompt, and Debian will be installed with kernel 2.6.8.

[nrundle]

Ok I tried installing with linux26 and think I've come to the real problem. During the installation I get this error:


No partitionable media were found.

Please check that a hard disk is attached to this machine.

An excerpt from the syslog (during installation) reveals this:

hw-detect: Missing module 'b44'.
hw-detect: Missing module 'ipw2200'.
hw-detect: Missing module 'ide-mod'.
hw-detect: Missing module 'ide-probe-mod'.
hw-detect: Missing module 'ide-detect'.
hw-detect: Missing module 'ide-floppy'.
...
kernel: ide0: I/O resource 0x1F0-0x1F7 not free.
kernel: ide0: ports already in use, skipping probe


Any ideas why it won't seem to detect my hd properly under 2.6.8 but it works fine with 2.4.27?

[falko]

Is it some kind of exotic hard disk?
Make sure it's connected properly.

[nrundle]

No this is not 'some kind of exotic' hard disk. It is a Hitachi HTS541060G9AT00 60 GB Ultra-ATA laptop hard drive. In a Dell Inspiron 6000. Like I said before, it loads up fine using kernel 2.4.27, but I need at least 2.6.8. I read somewhere the the 2.6 kernels went to ide-core instead of the ide-mod, ide-probe-mod and all that. I see that the ide-core module loads fine but it still doesn't explain why the I/O resource for the ide0 is busy when trying to detect hardware.

I am not sure what else to try. I've tried passing boot parameters such as hd=116280/16/63 to describe the CHS of the hd.

[nrundle]

There must be a bug in the 2.6.8 kernel. I downloaded and compiled the 2.8.16.11 kernel and it loaded up fine. Searching the internet I found a lot of people had the same problem with the Dell Inspiron 6000 and the 2.6.8 kernel.

[nithin]

hi,
Is there a way to compile just the updated files ? I know that in the vanilla kernel, doing a make compiles just the updated files and builds the kernel. However, under my sarge, doing a:

fakeroot make-kpkg --initrd --revision=custom.1.0 kernel_image

does not have the same behaviour.

- Nithin

[falko]

I don't know if this works... :confused:

[thctlo]

Well I think i can give the solution for this problem.

http://www.van-belle.nl/?Debian_howtos:4_-_the_packages:4.0_-_the_kernel
here are the steps your missing.

[Qrup]

Hi,

I've followed this guide completely. I'ts the first time I'm doing this, so I can't fugure out what I'm doing wrong.
When selecting "Load an Alternate Configuration File" under "make menuconfig" I'm getting alot of warnings. Here are some of them:

/usr/src/config-2.6.8-2-386:13:warning: trying to assign nonexistent symbol CLEAN_COMPILE
/usr/src/config-2.6.8-2-386:48:warning: trying to assign nonexistent symbol OBSOLETE_MODPARM
/usr/src/config-2.6.8-2-386:84:warning: trying to assign nonexistent symbol X86_EMU486
/usr/src/config-2.6.8-2-386:120:warning: trying to assign nonexistent symbol PM_DISK
/usr/src/config-2.6.8-2-386:126:warning: trying to assign nonexistent symbol ACPI_BOOT
/usr/src/config-2.6.8-2-386:127:warning: trying to assign nonexistent symbol ACPI_INTERPRETER
/usr/src/config-2.6.8-2-386:139:warning: trying to assign nonexistent symbol ACPI_BUS
/usr/src/config-2.6.8-2-386:142:warning: trying to assign nonexistent symbol ACPI_PCI
/usr/src/config-2.6.8-2-386:162:warning: trying to assign nonexistent symbol CPU_FREQ_PROC_INTF
/usr/src/config-2.6.8-2-386:168:warning: trying to assign nonexistent symbol CPU_FREQ_24_API
/usr/src/config-2.6.8-2-386:203:warning: trying to assign nonexistent symbol PCI_LEGACY_PROC
/usr/src/config-2.6.8-2-386:204:warning: trying to assign nonexistent symbol PCI_NAMES
/usr/src/config-2.6.8-2-386:307:warning: trying to assign nonexistent symbol MTD_CFI_AMDSTD_RETRY
/usr/src/config-2.6.8-2-386:327:warning: trying to assign nonexistent symbol MTD_ELAN_104NC
/usr/src/config-2.6.8-2-386:350:warning: trying to assign nonexistent symbol MTD_BLKMTD
/usr/src/config-2.6.8-2-386:379:warning: trying to assign nonexistent symbol PARPORT_PC_CML1
/usr/src/config-2.6.8-2-386:384:warning: trying to assign nonexistent symbol PARPORT_OTHER
/usr/src/config-2.6.8-2-386:470:warning: trying to assign nonexistent symbol IDE_TASKFILE_IO
/usr/src/config-2.6.8-2-386:478:warning: symbol value 'm' invalid for BLK_DEV_IDEPNP


Now.. I don't think that any of this went ok and I don't know what to configure in the menusystem. I guess I need to specify what modules I need..??

Anyway I proceed with the guide, but when all is done I can see that the kernel seems not to be installed properly. It is not in the Grub menu. I tried to alter the menu.1st file. It now has these menu items:

title Debian GNU/Linux, kernel 2.6.17
root (hd0,0)
kernel /boot/vmlinuz-2.6.17 root=/dev/hda1 ro
initrd /boot/initrd.img-2.6.17
savedefault
boot

title Debian GNU/Linux, kernel 2.6.17 (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.17 root=/dev/hda1 ro single
initrd /boot/initrd.img-2.6.17
savedefault
boot

title Debian GNU/Linux, kernel 2.6.8-2-386
root (hd0,0)
kernel /boot/vmlinuz-2.6.8-2-386 root=/dev/hda1 ro
initrd /boot/initrd.img-2.6.8-2-386
savedefault
boot

title Debian GNU/Linux, kernel 2.6.8-2-386 (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.8-2-386 root=/dev/hda1 ro single
initrd /boot/initrd.img-2.6.8-2-386
savedefault
boot


I also needed to generate the "initrd.img-2.6.8-2-386" file, since it was not created during my walkthrough of the guide. Was it supposed to be created?

I hope what I told can help you help me... I an puzzled :confused:

/Qrup

[falko]

/usr/src/config-2.6.8-2-386:13:warning: trying to assign nonexistent symbol CLEAN_COMPILE
/usr/src/config-2.6.8-2-386:48:warning: trying to assign nonexistent symbol OBSOLETE_MODPARM
/usr/src/config-2.6.8-2-386:84:warning: trying to assign nonexistent symbol X86_EMU486
/usr/src/config-2.6.8-2-386:120:warning: trying to assign nonexistent symbol PM_DISK
/usr/src/config-2.6.8-2-386:126:warning: trying to assign nonexistent symbol ACPI_BOOT
/usr/src/config-2.6.8-2-386:127:warning: trying to assign nonexistent symbol ACPI_INTERPRETER
/usr/src/config-2.6.8-2-386:139:warning: trying to assign nonexistent symbol ACPI_BUS
/usr/src/config-2.6.8-2-386:142:warning: trying to assign nonexistent symbol ACPI_PCI
/usr/src/config-2.6.8-2-386:162:warning: trying to assign nonexistent symbol CPU_FREQ_PROC_INTF
/usr/src/config-2.6.8-2-386:168:warning: trying to assign nonexistent symbol CPU_FREQ_24_API
/usr/src/config-2.6.8-2-386:203:warning: trying to assign nonexistent symbol PCI_LEGACY_PROC
/usr/src/config-2.6.8-2-386:204:warning: trying to assign nonexistent symbol PCI_NAMES
/usr/src/config-2.6.8-2-386:307:warning: trying to assign nonexistent symbol MTD_CFI_AMDSTD_RETRY
/usr/src/config-2.6.8-2-386:327:warning: trying to assign nonexistent symbol MTD_ELAN_104NC
/usr/src/config-2.6.8-2-386:350:warning: trying to assign nonexistent symbol MTD_BLKMTD
/usr/src/config-2.6.8-2-386:379:warning: trying to assign nonexistent symbol PARPORT_PC_CML1
/usr/src/config-2.6.8-2-386:384:warning: trying to assign nonexistent symbol PARPORT_OTHER
/usr/src/config-2.6.8-2-386:470:warning: trying to assign nonexistent symbol IDE_TASKFILE_IO
/usr/src/config-2.6.8-2-386:478:warning: symbol value 'm' invalid for BLK_DEV_IDEPNP
These are just warnings, I'd try to go on.


I also needed to generate the "initrd.img-2.6.8-2-386" file, since it was not created during my walkthrough of the guide. Was it supposed to be created?
Why do you want to create an initrd for 2.6.8 when you install a 2.6.17 kernel? :confused:

What's the output of ls -la /boot?

[Qrup]

Thanks for the reply..

I copied "initrd.img-2.6.8-2-386" in by misatke.. I ment "initrd.img-2.6.17"

The output of "ls -la /boot" is:
totalt 12388
drwxr-xr-x 3 root root 4096 2006-06-19 11:39 .
drwxr-xr-x 21 root root 4096 2006-06-19 09:14 ..
-rw-r--r-- 1 root root 63867 2006-06-19 11:00 config-2.6.17
-rw-r--r-- 1 root root 55809 2005-08-16 14:41 config-2.6.8-2-386
drwxr-xr-x 2 root root 4096 2006-06-19 11:39 grub
-rw-r--r-- 1 root root 4317184 2006-06-19 12:19 initrd.img-2.6.17
-rw-r--r-- 1 root root 4317184 2006-05-01 11:37 initrd.img-2.6.8-2-386
-rw-r--r-- 1 root root 713448 2006-06-19 11:32 System.map-2.6.17
-rw-r--r-- 1 root root 865767 2005-08-16 17:14 System.map-2.6.8-2-386
-rw-r--r-- 1 root root 1182291 2006-06-19 11:32 vmlinuz-2.6.17
-rw-r--r-- 1 root root 1097554 2005-08-16 17:14 vmlinuz-2.6.8-2-386
darth:~#


Is there something I did not do, that I should have done.. maby something about modules or HW drivers or something?
I can see that the kernel 2.6.17 is not included in the Grub bootloader.

/Qrup

[falko]

The output looks ok. The lines you added to menu.lst, too. Have you tried to reboot?

[Qrup]

yes, several times... when ever I tried something new. I have tried to load make menuconfig a couple of times, because I thought that was where my problem was. After installation of the kernel I have rebooted.

You write, "It is normally a good idea to take the configuration of your existing (working!) kernel 2.6 as a starting point for the configuration of your new kernel.". But if I get all the previouly metioned Warnings.. does it still accept my configuration?

I've heard talking about exotic HDDs somewhere. Well, I have an onboard raid system.. whish I'm not using. I have an IDE controller.. which I assume 2.6.17 is familiar with. I have several HDDs, but no scsi,, just IDE.

fstab:

# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/hda1 / ext3 defaults,errors=remount-ro,usrquota,grpquota 0 1
/dev/hda5 none swap sw 0 0
/dev/hdc /media/cdrom0 iso9660 ro,user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
/dev/hde1 /mnt/musik auto defaults 0 0
/dev/hdf1 /mnt/film auto defaults 0 0
/dev/hdh1 /mnt/misc auto defaults 0 0
/dev/hdd1 /mnt/hdd auto defaults 0 0


I really need to learn how to make a kernel. I'm planning to compile cool'n'quiet into the kernel.. and later MythTV, so u see it's very urgent :)

[falko]

You write, "It is normally a good idea to take the configuration of your existing (working!) kernel 2.6 as a starting point for the configuration of your new kernel.". But if I get all the previouly metioned Warnings.. does it still accept my configuration?
A lot of things have changed from 2.6.8 to 2.6.17, so it's possible that your old configuration is a problem, but I'm not sure... :confused:

[nowsurfing]

The last post is right that is what causes the error to solve it just mek the folowwing


system@user# cd /boot/
system@user/boot/# mkinitrd -o /boot/initrd.img-yourkernelvesion
system@user/boot/# update-grub

that should sove the problem

[nowsurfing]

I did evryting, and as I didnt want bad surprises y used my old config file with some adittions however I got another error mesage at boot time:

modprobe:FATAL: Could not load /lib/modules/2.6.17.1/modules.dep: No such a file or directory
modprobe:FATAL: Could not load /lib/modules/2.6.17.1/modules.dep: No such a file or directory
modprobe:FATAL: Could not load /lib/modules/2.6.17.1/modules.dep: No such a file or directory

umount: devfs: not mounted
pivot_root: No such a file or directory
/sbin/init: 432: cannot open dev/console:No such a file
Kernel panic - not syncing : Attemped to kill init!


Im guessing that the problem is of devfs, causethe file /lib/modules/2.6.17.1/modules.dep is in there and is fine, any idea?

[falko]

I did evryting, and as I didnt want bad surprises y used my old config file with some adittions however I got another error mesage at boot time:

modprobe:FATAL: Could not load /lib/modules/2.6.17.1/modules.dep: No such a file or directory
modprobe:FATAL: Could not load /lib/modules/2.6.17.1/modules.dep: No such a file or directory
modprobe:FATAL: Could not load /lib/modules/2.6.17.1/modules.dep: No such a file or directory

umount: devfs: not mounted
pivot_root: No such a file or directory
/sbin/init: 432: cannot open dev/console:No such a file
Kernel panic - not syncing : Attemped to kill init!


Im guessing that the problem is of devfs, causethe file /lib/modules/2.6.17.1/modules.dep is in there and is fine, any idea?
Do you use Xen? Because I know this error only from a Xen virtual machine...

[Qrup]

The last post is right that is what causes the error to solve it just mek the folowwing


that should sove the problem


I also tried doing this, but that didn't seem to solve my problem. Everything seems to go as planned.. the only thing is that Grub is not being updated with the new kernel. The 'update-grub' writes the changes to the 'menu.lst', but they are not shown when I reboot.

I tried following Digital Hermit's site suggestions, but it is now quite up_to_date. The result was the same as when I followed Falko's guide. I did the following:
apt-get install libncurses5-dev

Got the kernel from kernel.org using links

Unpacked it in /usr/src

Made a symbolic link to the dir ln -s linux-[kernel version] linux

Went into the Dir. cd linux

make menuconfig

make

make bzImage

make modules

make modules_install

cp arch/i386/boot/bzImage /boot/bzImage-2.6.17
cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.17
cp System.map /boot/System.map-2.6.17
ln -s /boot/System.map-2.6.17 /boot/System.map

mkinitrd -o /boot/initrd-2.6.17.img 2.6.17

update-grub

Any suggestions as to what I should do to see the new kernel will be much appreciated.

[falko]

What does your menu.lst look like now?

[Qrup]

It looks exactly like this:

# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 5

# Pretty colours
color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specifiv kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
# kopt=root=/dev/hda1 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery mode) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## ## End Default Options ##

title Debian GNU/Linux, kernel 2.6.17
root (hd0,0)
kernel /boot/vmlinuz-2.6.17 root=/dev/hda1 ro
initrd /boot/initrd.img-2.6.17
savedefault
boot

title Debian GNU/Linux, kernel 2.6.17 (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.17 root=/dev/hda1 ro single
initrd /boot/initrd.img-2.6.17
savedefault
boot

title Debian GNU/Linux, kernel 2.6.8-2-386
root (hd0,0)
kernel /boot/vmlinuz-2.6.8-2-386 root=/dev/hda1 ro
initrd /boot/initrd.img-2.6.8-2-386
savedefault
boot

title Debian GNU/Linux, kernel 2.6.8-2-386 (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.8-2-386 root=/dev/hda1 ro single
initrd /boot/initrd.img-2.6.8-2-386
savedefault
boot

### END DEBIAN AUTOMAGIC KERNELS LIST

[falko]

Hm, looks ok... :confused:

[marclar]

I tryed to compile new kernel too..

Everything went fine till this command:
fakeroot make-kpkg --initrd --revision=custom.1.0 kernel_image

After an hour of procesing it finished like this:

LD [M] net/xfrm/xfrm_user.ko
CC net/unix/unix.mod.o
LD [M] net/unix/unix.ko
CC net/wanrouter/wanrouter.mod.o
LD [M] net/wanrouter/wanrouter.ko
CC net/x25/x25.mod.o
LD [M] net/x25/x25.ko
CC net/xfrm/xfrm_user.mod.o
LD [M] net/xfrm/xfrm_user.ko
CC sound/soundcore.mod.o
LD [M] sound/soundcore.ko
make[1]: Leaving directory `/usr/src/linux-2.6.11.7'
COLUMNS=150 dpkg -l 'gcc*' perl dpkg 'libc6*' binutils ldso make dpkg-dev |\
awk '$1 ~ /[hi]i/ { printf("%s-%s\n", $2, $3) }' > debian/buildinfo
awk: relocation error: awk: symbol _dl_catch_error, version GLIBC_PRIVATE not de fined in file ld-linux.so.2 with link time reference
make: *** [debian/stamp-build-kernel] Error 127


I have noo idea what that could mean. I tryed twice, but it's the same..
I left the kernel config default..

[Erik Tromp]

Crap - it is all crap ;)

Downloaded the Linux 2.6.11.7 tarball as you indicated. Next step is to unpack it. Here is what happened:

root@DefaultNode:/usr/src# tar -xjf linux-2.6.11.7.tar.bz2

bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)

It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.

You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.

tar: Read 1376 bytes from linux-2.6.11.7.tar.bz2
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now

What? The tarball is corrupted??

I check my file system (enough space), my RAM (enough), my bzip2 version, my common sense... all seemed to be fine (although not so sure about the latter).

So I made a far fetch and downloaded kernel version 2.6.17.4, which happens to be the most recent one:

root@DefaultNode:/usr/src# wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.17.4.tar.bz2
--15:02:47-- http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.17.4.tar.bz2
=> `linux-2.6.17.4.tar.bz2'
Resolving www.kernel.org... 204.152.191.37, 204.152.191.5
Connecting to www.kernel.org[204.152.191.37]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 41,273,436 [application/x-bzip2]

100%[================================================== ==========================>] 41,273,436 408.93K/s ETA 00:00

15:04:27 (407.63 KB/s) - `linux-2.6.17.4.tar.bz2' saved [41273436/41273436]



And, guess what:

root@DefaultNode:/usr/src# tar -xjf linux-2.6.17.4.tar.bz2
root@DefaultNode:/usr/src# ls
linux-2.6.11.7.tar.bz2 linux-2.6.17.4 linux-2.6.17.4.tar.bz2


No problem.

Apparently the Linux 2.6.11.7 tarball from www.kernel.org is corrupted....

Well, who cares.

Off-topic: this is the Open Source / Gnu / Linux desease. As soon as you try to use it, guess what... it doesn't work. For no apparent reason whatsoever.

[falko]

Apparently the Linux 2.6.11.7 tarball from www.kernel.org is corrupted....

No, it's fine. I guess something went wrong with your download. Just download it again. :)

[Erik Tromp]

Beats me! I had already downloaded the kernel image, because I had figured out that the download might have failed. That didn't do much good then.

But this morning, a new and fresh download unzipped and untarred fine!

So I started the compilation. All wen well until after about 15 minutes:

...
CC [M] drivers/char/drm/drm_sysfs.o
CC [M] drivers/char/drm/gamma_drv.o
drivers/char/drm/gamma_drv.c:33:19: gamma.h: No such file or directory
In file included from drivers/char/drm/gamma_drv.c:37:
drivers/char/drm/gamma_drv.h:66: error: `DRM' declared as function returning a function
...

However, even if I use the recent 2.6.17.4 kernel, which *did* compile, the following happens after reboot:

...
umount: devfs: not mounted
mount: unknown filesystem type 'devfs'
umount: devfs: not mounted
pivot_root: No such a file or directory
/sbin/init: 432: cannot open dev/console:No such a file
Kernel panic - not syncing : Attemped to kill init!

Anyway, never mind, I think compiling a kernel is just too complicated for a simple person like me.

Thanks anyway.

[falko]

Anyway, never mind, I think compiling a kernel is just too complicated for a simple person like me.
Yes, it took me a whole week until my first kernel worked the way I wanted it... :)

[dansaycool]

Hi, i have followed this guide (which was supurb btw thankyu so much:) ) and have succesfully installed kernel-2.6.17.4 on my debian system. But now am wondering how one goes about instaling the kernel headers for it.
My problems all start when i bought a Netgear WG311 Wireless PCI Card, im following a guide for it i found

http://acx100.sourceforge.net/wiki/Distribution_list/Debian

Found out in the sys requriments page you need at least a kernel of 2.6.10 which i had 2.6.8,

http://acx100.sourceforge.net/wiki/ACX#System_requirements

so i followed this guide and installed the latest kernel at the time. But it also says it needs the kernel header files installed which i cant find out how to compile or install. Ive tried installing the module-assistant and using the "prepare" feature which should install the correct kernel headers, but its unable to find any for the kenerl.
Does anyone know what to do or where to go on from here lol
Many thanks dan :)

[falko]

If you compiled your kernel from the sources, then all header files are already on the system. If you installed a Debian kernel image, then you need to install the appropriate kernel-header package with apt-get. You can search for the appropriate package with apt-cache search kernel

[dansaycool]

ahh thanks, so because i followed this guide i don't need to install the header files lol thanks again for all your help
ta dan

[falko]

so because i followed this guide i don't need to install the header files
Yes, right.

[tom]

I'm not able to install a new xen kernel on debian sarge.
This maschine I have:
vendor_id : AuthenticAMD
cpu family : 15
model : 47
model name : AMD Athlon(tm) 64 Processor 3200+
stepping : 2

I've downloaded with apt this files and xen xen-tools etc.

With this xen-kerneln I've tried to boot:
linux-image-2.6.17-2-xen-k7 - Linux 2.6.17 image on AMD K7
linux-image-2.6.16-2-xen-k7 - Linux kernel 2.6.16 image on AMD K7 machines
linux-image-2.6.16-1-xen-k7 - Linux kernel 2.6.16 image on AMD K7 machines


But


After the grub bootpromt grub is boot in xen but nearly 10 secounds later the bootpromt is arising again. Now I can see nothing after the bootpromt because it's no console there while booting dom0. I don't know why the bootprozess is interrupted and I cant see any hints because it is nothing to see.

What should I do?

[falko]

I've had this problem once myself. All I could do was to compile another kernel.
What's the output of uname -m?

[tom]

I've had this problem once myself. All I could do was to compile another kernel.
What's the output of uname -m?
i686

I thoght i686 is standing for intel prozessors???


What have you changed in your kernel?
Do you still have your config file?
I've use this:http://www.howtoforge.com/perfect_setup_xen3_debian_p3 to compile an new kernel. But make oldconfig and make menuconfig does'nt work:

x:/usr/src/xen-3.0.2-2/linux-2.6.16.23-xen# make oldconfig
Makefile:439: /usr/src/xen-3.0.2-2/linux-2.6.16.23-xen/arch/xen/Makefile: No such file or directory
make: *** No rule to make target `/usr/src/xen-3.0.2-2/linux-2.6.16.23-xen/arch/xen/Makefile'. Stop.



Do you have a hint to get the seriell console showing something during the boot prozess?

Even I'm using software raid (raid1). Do you thing it could depence on it. Maybe xen does'nt support software raid.

Another prob while installing the linux-image-2.6.17-2-xen-k7 arrised. An script configured grubs menue.list during the installations prozess. After rebooting grub could'nt boot anything and even was'nt able to show the bootmenu.

Now I can't boot anyting even not the usual kernel. The only way to boot is booting external. Grub is installed on both raid devices and both raid devices are working well. I've no idea how I can fix that.

[falko]

I've use this:http://www.howtoforge.com/perfect_setup_xen3_debian_p3 to compile an new kernel. But make oldconfig and make menuconfig does'nt work:

The Xen tutorial was written for Xen 3.0.1, not 3.0.2. Things have changed in 3.0.2... :(

[miro]

im doing every this like you say and still im getting this error

Debian:/usr/src/linux-2.6.11.7# cd ../
Debian:/usr/src# dpkg -i kernel-image-2.6.11.7_custom.1.0_i386.deb
dpkg: error processing kernel-image-2.6.11.7_custom.1.0_i386.deb (--install):
cannot access archive: No such file or directory
Errors were encountered while processing:
kernel-image-2.6.11.7_custom.1.0_i386.deb
Debian:/usr/src#

[falko]

What's the output of ls -l /usr/src?

[jineesh]

hi
i tried to compile kernel 2.6.18. All working fine upto the command
fakeroot make-kpkg --revision=custom.1.0 kernel_image
after one hour process it shows an error and quits. the error is as follows.

COLUMNS=150 dpkg -l 'gcc*' perl dpkg 'libc6*' binutils ldso make dpkg-dev |\
awk '$1 ~ /[hi]i/ { printf("%s-%s\n", $2, $3) }' > debian/buildinfo
awk: relocation error: awk: symbol _dl_catch_error, version GLIBC_PRIVATE not de fined in file ld-linux.so.2 with link time reference
make: *** [debian/stamp-build-kernel] Error 127


thanks jineesh

[falko]

I think you need to install glibc-devel.

[jineesh]

hi
Thank you for your response.
But i dont know how to install glibc-devel. i m new to linux.
Plz help me.

[falko]

Which distribution do you use? If it's Debian, you can search for the appropriate package like this:
apt-cache search glibcOnce you have found the right packahe you can install it:
apt-get install package

[jineesh]

hi
sorry to inform you that still it shows the same error. I installed glibc pakages as you said. :confused: :confused: :confused:
jineesh

[falko]

You can try this:
apt-get install build-essential

[tino097]

hello

im quite new to Linux, and i followed instructions, but i use config file given in the first post and change nothing there cause im not sure what need to do.

during the re-compiling of kernel i didnt get error messages, but after rebooting i recived this mesage during booting :

cs8900: no cs8900 or cs89200 detected. Be sure to disable PnP with Setup

so if someone can give me instructions what to do and where to change this settings

thanks

[tino097]

i solve the problem above but now my USB mosue wont work

any ideas where to look ?

[falko]

Please try this tutorial instead: http://www.howtoforge.com/kernel_compilation_debian
It's newer.

[ikkem]

Hi....
I have a question....
I was trying to compile kernel source 2.6.19.20 on debian etch but iptables module does not seem to load or iptables has to be compiled againts the kernel source (I guess) but I could not find any info on google or clusty...
Has much changed regarding the compilation with the release of 2.6.19.20

thanks in advance....

[falko]

Did you enable iptables during make menuconfig?

[ikkem]

hi....:)
yes I did enable iptables at first I thought I overlooked it but it is enabled....

[falko]

There must be a config file for your new kernel in the /boot directory. What's the output of grep -i iptables /boot/kernel_config?

[ikkem]

There must be a config file for your new kernel in the /boot directory. What's the output of grep -i iptables /boot/kernel_config?

hi....:)

the output is:

# grep -i iptables /boot/config-2.6.20.1-raysun3
CONFIG_IP_NF_IPTABLES=y
CONFIG_IP6_NF_IPTABLES=m


this time I got it working I did not make a symlink to linux instead I cd into /usr/src/linux-2.6.20.1 and I followed your how to
at my first and second attempt the system kept hanging on boottime and after it booted I could not connect to the net...
thanks for reacting....

[ikkem]

I am not able to run shorewall anymore.
Do I have to compile iptables against the new kernel? part of the output of shorewall show capabilities:

# shorewall show capabilities
NAT: Not available
Packet Mangling: Not available


Looked on google/clusty but I could not find a how to compile iptables against a kernel for debian/ubuntu....

thanks in advance....

[falko]

Did you use an old, working kernel configuration for configuring your new kernel? Or did you configure your new kernel from scratch?

[ikkem]

Hi....:)
I used an old working kernel configuration I used the 2.6.8....configuration and then I enabled xtables... during menuconfig...

[falko]

What's the output of which iptables and modprobe iptables?

[ikkem]

the out is:
# which iptables
/usr/local/sbin/iptables


# modprobe iptables
FATAL: Module iptables not found.


I am trying to compile iptables against the kernel I installed iptables-1.3.7 now I am going to compile the kernel hopefully it will work
is there a debian/ubuntu way for this?
thanks in advance....

[ikkem]

I finally got it working I compiled iptables against the kernel(2.6.20.3)....
here is the how to:

to patch the kernel you will need to download iptables and patch-o-matic


apt-get remove iptables ipchains --purge


cd /usr/src
iptables source - wget -c http://ftp.netfilter.org/pub/iptables/iptables-1.3.7.tar.bz2
patch-o-matic - wget -c http://ftp.netfilter.org/pub/patch-o-matic-ng/snapshot/patch-o-matic-ng-20070322.tar.bz2
Linux kernel source - wget -c http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.20.3.tar.bz2


unpack the downloaded files:

tar xjf patch-o-matic-ng-20070322.tar.bz2
tar xjf iptables-1.3.7.tar.bz2
tar xjf linux-2.6.20.3.tar.bz2


First you need to run the make menuconfig command to
preconfigure the kernel otherwise *PATCHING WILL FAIL* change into the
linux-2.6.20.3 directory and run the make menuconfig command


apt-get install kernel-package libncurses5-dev fakeroot wget bzip2 build-essential udev
cd /usr/src/linux-2.6.20.3
make clean && make mrproper
cp /boot/config-`uname -r` ./.config
make menuconfig



exit and save the config file. Now you will need to go into the patch-o-matic directory

cd /usr/src/patch-o-matic-ng-20070322
# KERNEL_DIR=/usr/src/linux-2.6.20.3 ./runme extras


Once you issue that command you will be prompt with the following


Hey! IPTABLES_DIR is not set.
Where is your iptables source code directory? [/usr/src/iptables]/usr/src/iptables-1.3.7



Once that is done you will be prompt for which patches you would like to apply, they also give you a little description on
what each patch does.

Once you have finished selecting which patches you want installed you will need to compile your iptables so you will
need to do the following in the iptables source directory.


cd /usr/src/iptables-1.3.7
make KERNEL_DIR=/usr/src/linux-2.6.20.3
make install KERNEL_DIR=/usr/src/linux-2.6.20.3
make clean


your iptables have been compiled now you can start compiling your kernel so you can issue the following in the kernel source directory


cd /usr/src/linux-2.6.20.3
make-kpkg clean
make-kpkg --initrd kernel_image kernel_headers


after the kernel build the kernel can be found in the /usr/src directory

cd /usr/src
dpkg -i *deb


Create A Ramdisk

apt-get install libhtml-template-perl libparse-recdescent-perl
cd /tmp
wget http://downloads.howtoforge.com/files/yaird_0.0.12-8bpo1_i386.deb
dpkg -i yaird_0.0.12-8bpo1_i386.deb

nano -w /boot/config-2.6.20.3-raysun1
[....]
# CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
[....]


create ramdisk
mkinitrd.yaird -o /boot/initrd.img-2.6.20.3-raysun1 2.6.20.3-raysun1

update grub
update-grub

reboot system
shutdown -r now


hope it helps....:)

source:
http://www.linux-noob.com/forums/index.php?showtopic=2182&hl=
http://www.howtoforge.com/kernel_compilation_debian

[boom84]

maybe you could help me i have some troubles with compiling debian kernel 2.6.18.3. as i read the flip has the same problem with sbin/init cannot open dev/console. we tried to do it in differnt way but did not help.

thanks

[boom84]

haloo anybody here?

[boom84]

hello so i am here....

[martinfst]

Bumping a post every 30 minutes is not going to help you. Personally I think this is abusive. You're adding a vague question to the end of a long thread and the entry before yours is giving a solution. I suggest you start a new thread in which you explain what exactly is your problem. Expect you need to wait around 1-2 days. If you need quicker answers, consider paid support and/or hiring someone.

[boom84]

ok i already did

[sayad]

maybe you could help me i have some troubles with compiling debian kernel 2.6.18.3. as i read the flip has the same problem with sbin/init cannot open dev/console. we tried to do it in differnt way but did not help.

thanks

Hey i need help with the same thing...i have had the same kinda trouble...

thanks.




--
Webkinz Recipes (http://www.thewebkinzblog.com)

[shae marks]

I have problem and I do not know how to solve it myself. Last weekend I tried ( I said tried ) to recompile kernel on my Debian Sarge machine, but I encountered some problems.

After compilation and rebooting my macnine and choosing new kernel to boot I got error as follows:
modprobe: FATAL: Could not load /lib/modules/2.6.15.4/modules.dep : No such file or directory
umount devfs: not mounted
pivot_root: No such file or directory
/sbin/init:432 cannot open dev/console
kernel panic-Not syncing: Attempted to kill init

I really do not what to do in order to compile kernel, I have many manuals, and I read them as you can see I made procedure of compilation on right way ( Tell me if I am wrong ) but still I cannot solve above mentioned errors.

Please show me what I did wrong and what I should correct in order to make my 2.6.15.4 works.

Thank you in advance

The procedure I used to compile kernel and files I got after cmpilation is as follows.

I run make-kpkg kernel-image and after 20 minutes
DeusEtMachine:/usr/src# ls -l
total 52228
-rw-r--r-- 1 root src 13558552 2006-03-19 17:33 kernel-image-2.6.15.4_10.00.Custom_i386.deb
drwxrwxrwx 21 root root 4096 2006-03-19 17:44 linux-2.6.15.4
-rwx------ 1 root src 39846379 2006-03-18 16:11 linux-2.6.15.4.tar.bz2
DeusEtMachine:/usr/src#

In /lib/modules I have

DeusEtMachine:/lib/modules# ls -l
total 8
drwxr-xr-x 3 root root 4096 2006-03-19 17:34 2.6.15.4
drwxr-xr-x 5 root root 4096 2006-02-25 10:11 2.6.8-2-386
DeusEtMachine:/lib/modules#

In /lib/modules/2.6.15.4 there are next files

DeusEtMachine:/lib/modules/2.6.15.4# ls -l
total 1008
lrwxrwxrwx 1 root root 23 2006-03-19 17:34 build -> /usr/src/linux-2.6.15.4
drwxr-xr-x 10 root root 4096 2006-03-19 17:34 kernel
-rw-r--r-- 1 root root 201018 2006-03-19 17:34 modules.alias
-rw-r--r-- 1 root root 69 2006-03-19 17:34 modules.ccwmap
-rw-r--r-- 1 root root 212744 2006-03-19 17:34 modules.dep
-rw-r--r-- 1 root root 813 2006-03-19 17:34 modules.ieee1394map
-rw-r--r-- 1 root root 394 2006-03-19 17:34 modules.inputmap
-rw-r--r-- 1 root root 21025 2006-03-19 17:34 modules.isapnpmap
-rw-r--r-- 1 root root 182827 2006-03-19 17:34 modules.pcimap
-rw-r--r-- 1 root root 98846 2006-03-19 17:34 modules.symbols
-rw-r--r-- 1 root root 264449 2006-03-19 17:34 modules.usbmap
lrwxrwxrwx 1 root root 23 2006-03-19 17:34 source -> /usr/src/linux-2.6.15.4
DeusEtMachine:/lib/modules/2.6.15.4#

In /boot/ I have as follows

DeusEtMachine:/boot# ls -l
total 12964
-rw-r--r-- 1 root root 63903 2006-03-04 15:51 config-2.6.15.4
-rw-r--r-- 1 root root 55809 2005-05-19 10:38 config-2.6.8-2-386
drwxr-xr-x 2 root root 4096 2006-03-19 17:38 grub
-rw-r--r-- 1 root root 4317184 2006-03-19 17:35 initrd.img-2.6.15.4
-rw-r--r-- 1 root root 4317184 2006-02-25 10:35 initrd.img-2.6.8-2-386
-rw-r--r-- 1 root root 814523 2006-03-19 17:33 System.map-2.6.15.4
-rw-r--r-- 1 root root 865733 2005-05-19 11:26 System.map-2.6.8-2-386
-rw-r--r-- 1 root root 1680929 2006-03-19 17:33 vmlinuz-2.6.15.4
-rw-r--r-- 1 root root 1097419 2005-05-19 11:25 vmlinuz-2.6.8-2-386
DeusEtMachine:/boot#

In /grub/menu.lst I have the next output
title Debian GNU/Linux, kernel 2.6.15.4
root (hd0,1)
kernel /boot/vmlinuz-2.6.15.4 root=/dev/hda2 ro
initrd /boot/initrd.img-2.6.15.4
savedefault
boot

title Debian GNU/Linux, kernel 2.6.15.4 (recovery mode)
root (hd0,1)
kernel /boot/vmlinuz-2.6.15.4 root=/dev/hda2 ro single
initrd /boot/initrd.img-2.6.15.4
savedefault
boot

title Debian GNU/Linux, kernel 2.6.8-2-386
root (hd0,1)
kernel /boot/vmlinuz-2.6.8-2-386 root=/dev/hda2 ro
initrd /boot/initrd.img-2.6.8-2-386
savedefault
boot

title Debian GNU/Linux, kernel 2.6.8-2-386 (recovery mode)
root (hd0,1)
kernel /boot/vmlinuz-2.6.8-2-386 root=/dev/hda2 ro single
initrd /boot/initrd.img-2.6.8-2-386
savedefault
boot

[matey]

I have seen this happen in Grub many times where it (for some strange reasons) changes the (hd 0,0) to (hd 1,0) or another form of it.
I even had a server with hd 2,0 in the menu.lst file which changed itself to hd0,0 after an upgrade! then no boot!

so always make backup copy of your (Working) menu.lst file BEFORE doing any updates/upgrades or recompiling kernel.
2 cents worth from a noob!