Hello,

I was messing around a bit and tried to update my kernel from 2.4.23 / 2.4.22 to 2.6.2....

now i have some questions about it:

1. Is it easier to use the precompiled binary e.g. kernel-image-2.6.2-1-686-smp to install then recompiling?

2. When i am installing the new kernel (dpkg) it seems that the old kernel is throwing more error messages than before. the old kernel will have problems locating some modules even they're still there.

3. when running a make-kpkg clean i wont be able to compile the kernel with this tool. i have to start a single "make" and cancel it. then make-kpkg will work again. is this due a mistake in configuration?

4. mouse behaviour is different all the time i am trying a new upgrade. sometimes i do not have a mouse (all options about ps/2 enabled) other times the mouse will go crazy due double entries in XF86-Config-4.... what do i have to take care when upgrading?

5. is there a good FAQ/Upgrade information around for debian? i havent found anything like this.

6. how do i get a current list of my current chipsets (USB, Board, PCI, Kernel, IDE or whatever and so on) and how to know the correct module for it? is there an translation list or smth like this?
lspci, lsmod?? what about isdn / usb and such?


Thanks for help.

This should get you started.

http://www.desktop-linux.net/debkernel.htm

thanks this looks great. even patches are explained...

but: on this page they are not using --append_to_version and --initrd options for make_kpkg??? modules_image is missing, too (modules wont be installed???)

and what about system.map?? do i have to include it into lilo.conf somehow?

am i able to use 2.4.23 kerlen AND 2.6.2 kernel with boot menu?

initrd seems to miss completely? do i need it? or will it work w/o

thanks for information :-)

I don't use initrd. It is a option under device->block devices.
System.map is part of the make-pkg process.
It is not only possible to have both the 2.4.x and 2.6.x in the same menu but have different distros listed from diffenent partitiions, ie.

default=Linux2.6

image=/boot/vmlinuz
vga=773
label=Linux2.6
read-only

image=/boot/vmlinuz.old
vga=791
append="hdc=scsi hdd=scsi apm=power-off nomce"
label=Linux2.4
read-only

image=/slack/vmlinuz
root=/dev/hda3
label=Slack2.6
read-only

image=/slack/vmlinuz.old
vga=791
append="hdc=scsi hdd=scsi nosmp apm=off apci=off"
root=/dev/hda3
label=Slack2.4
read-only

But personally I use the following, I do it the normal way. It is all up to you.:

For building the 2.6 kernel

Take and read the following:

http://www.linux.org.uk/~davej/docs/...loween-2.6.txt

You need to get the module-init-tools.

cp linux-2.6.2.tar.gz /usr/src
tar jfx linux-2.6.2.tar.gz
ln -sf linux-2.6.2 linux
cd linux

Use lspci -v to help select your hardware. This will be helpful for configuring the 2.6 kernel.

make mrproper
make menuconfig
make
make modules_install
make install

Then modify you lilo.conf or grub.txt

make install installs vmlinuz into the boot directory along with System.map
It creates a symbolic link to you old vmlinuz -> vmlinuz.old and System.old

All you need to do is add entry for the old vmlinuz. I use lilo.conf

This is mine....

image=/boot/vmlinuz
label=Linux2.6
read-only

** This would be you redhat config. **
image=/boot/vmlinuz.old
vga=791
append="hdc=scsi hdd=scsi apm=power-off nomce"
label=Linux2.4
read-only

If you are using lilo, issue lilo -v or modify you menu.lst for grub.

Hope this helps. The more people use 2.6 the better.

thanks for answer.

ive read that you can specify a map within lilo config. if you wont specify the map lilo will use /boot/map as standard.
make-kpkg wont install lilo (it will mess it up when installing with dpkg)

what is system.map for? and is it the thing mentioned in lilo.conf manual? (man lilo.conf)
within your examples you aren't using a system.map.