Guide to 2.6 kernel upgrade/recompile

bcalder01 · 12-28-2004, 05:56 PM

I'll look 'em over ... thanks all.

makuyl · 12-29-2004, 07:08 AM

Quote:

Originally posted by bcalder01
Now this is strange ...
I downloaded kernel-image-2.6.8-1-686 & installed, using update-grub configured it into the bootloader. I was able to boot into the new kernel. Great. Now I've downloaded kernel-source-2.6.8, also via apt-get & untarred it in /usr/src. I've created a 'linux' symlink to it in /usr/src. I cd to the directory & issue 'make xconfig' or 'make menuconfig', and I get:

=======================================================================
root@gwlap:/usr/src/linux# cp /boot/config-2.6.8-1-686 .config
root@gwlap:/usr/src/linux# make xconfig
HOSTCC scripts/basic/fixdep
In file included from /usr/include/sys/socket.h:35,
from /usr/include/netinet/in.h:24,
from scripts/basic/fixdep.c:107:
/usr/include/bits/socket.h:305:24: asm/socket.h: No such file or directory
make[1]: *** [scripts/basic/fixdep] Error 1
make: *** [scripts_basic] Error 2
=======================================================================

... I have no idea what it's telling me. Has anyone seen this?

I'm using Debian sarge on a PIII Coppermine laptop. 2.4.22 & 2.4.24 recompiled just fine on it.

Do you have linux-kernel-headers installed?
If no, apt-get it
If yes, try changing line 305 of /usr/include/bits/socket.h from "#include <asm/socket.h>" to "#include </usr/src/linux/include/asm-i386/socket.h>

bcalder01 · 01-03-2005, 02:21 PM

Thank you. I had the kernel-specific headers, but they didn't work. I apt-getted linux-kernel-headers, and I'm rockin'.

NilsR · 01-09-2005, 07:35 PM

Quote:

Originally posted by m_yates
I think you should always add that line to fstab. I'm not sure if the line gets added automatically when you install a kernel image using apt-get from the Debian repository.

There is a Debian 2.6 kernel hoto here: http://www.desktop-linux.net/debkernel.htm It also mentions adding that line to fstab, and making the /sys directory with "mkdir /sys".

If anybody knows for sure that something different should be done, please let me know and I will correct the post that started this thread.

I found that /etc/init.d/mountvirtfs mounts /sys for you. This is said to be better than using a fstab /sys entry if you later want to boot a 2.4 kernel.

subaruwrx · 01-13-2005, 07:37 AM

Hi I encounter some error when compiling 2.6.10.

This is where the error started.

Quote:

In file included from drivers/char/drm/gamma_drv.c:40:

drivers/char/drm/drm_agpsupport.h: In function `gamma_agp_uninit':

drivers/char/drm/drm_agpsupport.h:431: warning: `inter_module_put' is deprecated (declared at include/linux/module.h:582)

In file included from drivers/char/drm/gamma_drv.c:42:

drivers/char/drm/gamma_context.h: In function `gamma_context_switch_complete':

drivers/char/drm/gamma_context.h:193: error: structure has no member named `next_buffer'

drivers/char/drm/gamma_context.h:193: error: structure has no member named `next_buffer'

In file included from drivers/char/drm/gamma_drv.c:44:

drivers/char/drm/gamma_old_dma.h: In function `gamma_clear_next_buffer':

drivers/char/drm/gamma_old_dma.h:40: error: structure has no member named `next_buffer'

drivers/char/drm/gamma_old_dma.h:41: error: structure has no member named `next_queue'

drivers/char/drm/gamma_old_dma.h:41: error: structure has no member named `next_queue'

drivers/char/drm/gamma_old_dma.h:41: error: structure has no member named `next_queue'

drivers/char/drm/gamma_old_dma.h:41: error: structure has no member named `next_queue'

drivers/char/drm/gamma_old_dma.h:41: error: structure has no member named `next_queue'

drivers/char/drm/gamma_old_dma.h:41: error: structure has no member named `next_queue'

drivers/char/drm/gamma_old_dma.h:42: error: structure has no member named `next_queue'

drivers/char/drm/gamma_old_dma.h:44: error: structure has no member named `next_queue'

In file included from drivers/char/drm/gamma_drv.c:46:

drivers/char/drm/drm_drv.h: In function `gamma_release':

drivers/char/drm/drm_drv.h:807: warning: implicit declaration of function `gamma_ctxbitmap_free'

In file included from drivers/char/drm/gamma_drv.c:58:

drivers/char/drm/drm_stub.h: In function `gamma_stub_putminor':

drivers/char/drm/drm_stub.h:148: warning: `inter_module_put' is deprecated (declared at include/linux/module.h:582)

drivers/char/drm/drm_stub.h:150: warning: `inter_module_unregister' is deprecated (declared at include/linux/module.h:578)

drivers/char/drm/drm_stub.h: In function `gamma_stub_register':

drivers/char/drm/drm_stub.h:206: warning: `inter_module_register' is deprecated (declared at include/linux/module.h:577)

drivers/char/drm/drm_stub.h:216: warning: `inter_module_unregister' is deprecated (declared at include/linux/module.h:578)

make[3]: *** [drivers/char/drm/gamma_drv.o] Error 1

make[2]: *** [drivers/char/drm] Error 2

make[1]: *** [drivers/char] Error 2

make: *** [drivers] Error 2

debian:/usr/src/linux-2.6.10#

Here is my .config file.

m_yates · 01-13-2005, 08:47 AM

I ran into this in another post, I'll re-post my answer here:

I had the same error trying to compile kernel 2.6.9. The bug page for it is here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=282964 The driver gamma_drv is broken. If you redo "make menuconfig", you can de-select the driver. After that, "make-kpkg clean" and then "make-kpkg --initrd --append-to-version=-debian kernel_image" It should work. Good luck!

subaruwrx · 01-13-2005, 09:15 AM

Quote:

Originally posted by m_yates
I ran into this in another post, I'll re-post my answer here:

I had the same error trying to compile kernel 2.6.9. The bug page for it is here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=282964 The driver gamma_drv is broken. If you redo "make menuconfig", you can de-select the driver. After that, "make-kpkg clean" and then "make-kpkg --initrd --append-to-version=-debian kernel_image" It should work. Good luck!

Whats the use of "make-kpkg clean" and "make-kpkg --initrd --append-to-version=-debian kernel_image"?

I'm compiling using the old traditional method, not the debian way.

m_yates · 01-13-2005, 09:53 AM

Quote:

Originally posted by subaruwrx
Whats the use of "make-kpkg clean" and "make-kpkg --initrd --append-to-version=-debian kernel_image"?

I'm compiling using the old traditional method, not the debian way.

because the "Debian way" is what I wrote at the start of this thread, so I assumed that is what you were following. You can compile the kernel either way. The issue is that your config file has you trying to compile a module that is broken. Just change your config file to get rid of the gamm_drv module, and you should be able to compile.

linx win · 01-14-2005, 03:00 PM

I installed kernel-image-2.6.10-1-686-smp and I want to creat a boot floppy disk but it is not giving me this option. What should I do?

This what I got:

A new kernel image has been installed, and usually that means
that some action has to be taken to make sure that the new
kernel image is used next time the machine boots. Usually,
this entails running a ``bootloader'' like SILO, loadlin, LILO,
ELILO, QUIK, VMELILO, ZIPL, or booting from a floppy. (Some
boot loader, like grub, for example, do not need to be run on
each new image install, so please ignore this if you are using
such a boot loader).

A new kernel image has been installed at /boot/vmlinuz-2.6.10-1-686-smp
(Size: 1259kB)

Initial rootdisk image: /boot/initrd.img-2.6.10-1-686-smp (Size: 4488kB)

Symbolic links, unless otherwise specified, can be found in /

LILO sets up your system to boot Linux directly from your hard
disk, without the need for booting from a boot floppy.

WARNING
If you are keeping another operating system or another version
of Linux on a separate disk partition, you should not have LILO
install a boot block now. Wait until you read the LILO documentation.
That is because installing a boot block now might make the other
system un-bootable. If you only want to run this version of Linux,
go ahead and install the boot block here. If it does not work, you
can still boot this system from a boot floppy.

You already have a LILO configuration in /etc/lilo.conf
Install a boot block using the existing /etc/lilo.conf? [Yes] n
Wipe out your old LILO configuration and make a new one? [No] y
Rotated `/etc/lilo.conf' at Fri Jan 14 23:46:42 EET 2005.
Do you wish to set up Linux to boot from the hard disk? [Yes] n

and stops here.

rjshirts · 01-21-2005, 10:34 AM

OK, here's the scoop. I have a Pentium I with 96 mb of ram that I'm trying to upgrade from kernel 2.4 to 2.6.8.1, but it keeps crapping out during the compile. I've eliminated all the modules, etc... that have caused problems in the past (I think), but now I'm getting a new message.
When it finishes compiling the modules, this is what I found when I showed up for work today:

.......(list of modules)
LD [M] security/root_plug.ko
make[1]: leaving directory '/usr/src/linux-2.6.8.1'
COLUMNS =150 dpkg -l 'gcc*' perl dpkg 'libc6*' binutils ldso make dpkg-dev l\
awk '$1 == "ii" { printf("%s-%s\n", $2, $3) }' > debian/buildinfo
/bin/sh: debian/buildinfo: No such file or directory
make: *** [stamp-build] Error 1
debian:/usr/src/linux-2.6.8.1#

Ideas? Why would I be left with my prompt? This is the first time that I've tried to compile a kernel, so I really know little above nothing about this whole process. I found this website http://www.falkotimme.com/howtos/deb...pile/index.php and I've been trying to follow the directions to the letter (heck, I even tried using his 2.6.8.1 config file to see if that would make a difference, it didn't), but it still isn't working.
I think I'll print off the guide from the first post here, and see if that makes any difference. I just don't want to make clean if there is something I can do to save the hours of compiling that I just spent.
Thanks a million for all your help,

Jonathan

weeee · 01-22-2005, 07:15 AM

i think that you need a better box for 2.6 kernel

Oh Cisco · 02-09-2005, 10:37 AM

With this post and a learning curve, I was able to successfully recompile my first kernel and get the debian logo to show up during boot. Thank you, m_yates

The only thing that is strange, is that the logo disappears about 3/4 of the way thru. It disappears about the time the boot gets to the starting portmap daemon or starting the fonts.

Is this normal to happen and can something be done to let the logo stay during the entire boot?

m_yates · 02-09-2005, 10:43 AM

Mine disappears too. I think it is normal for it to scroll up at the end.

R00ts · 03-11-2005, 11:16 PM

Here's something strange. I just built a custom 2.6.8 kernel for my new AMD64 machine and after I tried to boot into I got:

Code:

VFS: cannot open root device "hda1" or unknown-block(0,0)
Lease append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)

Oh the joys of kernel panic. So I checked my /boot/grub/menu.lst file. And found the following. (i386 is the Debian installer build, amd64-k8
is the Debian image kernel [which refuses to run startx for some reason], and harima is the custom kernel I just built)

Code:

title           Debian GNU/Linux, kernel 2.6.8-harima
root            (hd0,0)
kernel          /boot/vmlinuz-2.6.8-harima root=/dev/hda1 ro
savedefault
boot

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

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

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

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

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

Hmm, root is set right, but there's no initrd! Well this is weird!? So I did an ls of /boot:

Code:

roots@harima:/$ ls /boot
config-2.6.8-10-amd64-k8      System.map-2.6.8-10-amd64-k8
config-2.6.8-1-386            System.map-2.6.8-1-386
config-2.6.8-harima           System.map-2.6.8-harima
grub                          vmlinuz-2.6.8-10-amd64-k8
initrd.img-2.6.8-10-amd64-k8  vmlinuz-2.6.8-1-386
initrd.img-2.6.8-1-386        vmlinuz-2.6.8-harima

There's no initrd.....

Any clues as to what could be wrong? I'm almost sure I specified the "--initrd" flag when compiling the kernel. Could it be something else???

>>>EDIT<<<

Hmm, looks like I didn't after all. I purged my kernel, ran make-kpkg clean, and rebuilt it this time being sure to include the flag and this time I got a prompt warning me about initrd that I don't remember getting before. So I guess I really did forget.

I'm re-compiling now so hopefully it will work. If it doesn't, I'll be back

Krugger · 03-30-2005, 05:30 PM

I am currently with a 2.4.18 kernel and I am trying to upgrade the system to a 2.6.11.6 vanilla kernel. My problem is similar as the checkroot.sh script fails as there are no /dev/hda* in /dev. I can overcome this by doing a ln -sf to /dev/ide/.../part*, but there are other things that are broken too, like the serial ttyS* and probably more stuff. How to solve this?

Is it the use of devfs instead of udev? or why aren't the links created? The links don't seem to be created by and script in the init.d directory for the 2.4.18 kernel.