Debian Kernel Update 2.4 - 2.6 -> Problem

l-deep · 05-05-2006, 08:05 AM

hey folks, its my first post

ive googled and searched a lot on this prob, but couldnt get any further:

Code:

mamoru:/home/nb# apt-get install kernel-image-2.6.8-3-386
Reading package lists... Done
Building dependency tree... Done
kernel-image-2.6.8-3-386 is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
Setting up kernel-image-2.4.27-2-386 (2.4.27-12) ...
depmod: *** Unresolved symbols in /lib/modules/2.4.27-2-386/kernel/drivers/net/wireless/orinoco.o
depmod: *** Unresolved symbols in /lib/modules/2.4.27-2-386/kernel/fs/xfs/xfs.o
Using /usr/sbin/mkinitrd to build the ramdisk.
Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd /usr/sbin/mkinitrd.yaird /usr/sbin/mkinit                                                  ramfs.
/bin/bash: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file o                                                  r directory
Failed to create initrd image.
dpkg: error processing kernel-image-2.4.27-2-386 (--configure):
 subprocess post-installation script returned error exit status 2
Errors were encountered while processing:
 kernel-image-2.4.27-2-386
E: Sub-process /usr/bin/dpkg returned an error code (1)

i want to update my system kernel from 2.4 to 2.6 and get this error.. anyone has a hint ?

IBall · 05-05-2006, 08:09 AM

Welcome to LQ!

What is the output of "uname -a"?

I assume you are using Debian Sarge, which comes with either the 2.4.27 kernel, or 2.6.8. Since 2.6.8-3 is already installed, why is it trying to install 2.4.27? What is the command you entered to get that error?

--Ian

l-deep · 05-05-2006, 09:06 AM

Quote:

Originally Posted by IBall

Welcome to LQ!

What is the output of "uname -a"?

I assume you are using Debian Sarge, which comes with either the 2.4.27 kernel, or 2.6.8. Since 2.6.8-3 is already installed, why is it trying to install 2.4.27? What is the command you entered to get that error?

--Ian

yep, using sarge.

uname -a

mamoru:/home/nb# Linux mamoru 2.4.27-2-386 #1 Wed Nov 30 21:38:51 JST 2005 i686

i entered the following:

apt-get install kernel-image-2.6.8-3-386

thats what i got so far..

divukman · 05-05-2006, 09:36 AM

I-deep it seems that you already installed that version.

Code:

kernel-image-2.6.8-3-386 is already the newest version.

Try this: $ dpkg -l | grep kernel-image-2.6.8-3-386

l-deep · 05-05-2006, 09:38 AM

Quote:

Originally Posted by divukman

I-deep it seems that you already installed that version.

Code:

kernel-image-2.6.8-3-386 is already the newest version.

Try this: $ dpkg -l | grep kernel-image-2.6.8-3-386

Code:

mamoru:/home/nb# dpkg -l | grep kernel-image-2.6.8-3-386
ii  kernel-image-2.6.8-3-386  2.6.8-16sarge2             Linux kernel image for version 2.6.8 on 386.
mamoru:/home/nb#

l-deep · 05-05-2006, 10:43 AM

noone ? i could use some help here..

farslayer · 05-05-2006, 12:36 PM

so is the new kernel not listed in your grub conf ?
cat /boot/grub/menu.lst

if it's listed there you will need to reboot the system to switch to the new kernel.

not that it has anything to do with your problem, but if you are going to switch to the 2.6 kernel why not use the right one for your CPU ?

apt-get install kernel-image-2.6.8-3-686 I doubt that's a 386 machine you are installing on....

divukman · 05-05-2006, 02:17 PM

Quote:

Originally Posted by l-deep

noone ? i could use some help here..

ok, type this and get us the output:

$ cd /boot/grub
$ cat menu.lst

what you should have is something like this, but with your kernel version (2.6.8)

Code:

title           Debian GNU/Linux, kernel 2.6.16.14, MiTo
root            (hd0,0)
kernel          /vmlinuz-2.6.16.14 root=/dev/hda2 ro vga=0x31B
savedefault
boot

Of course, when you power up the computer and get grub, you should see the entry, in my case "Debian GNU/Linux, kernel 2.6.16.14, MiTo" and pick it from the list.

To go a bit further, you could (later) compile your own kernel, for instance, get the source from the kernel.org and follow instructions on http://www.debian.org/releases/stabl...h08s05.html.en .

It's quite simple and goes something like this:
"# make-kpkg clean" - to clean kernel source tree
"# make menuconfig" - to set up your configuration, I can give you mine and then you could make a few changes to reflect your own configuration
"# make-kpkg --revision=custom.2.6.16.14 kernel_image"

then you'd get a .deb package you could install with "#dpkg -i name_of_package.deb", by default Debian will take care of entries in /boot/grub/menu.lst for you.

_aXXe_ · 05-13-2006, 12:17 PM

Linux debian 2.4.27-2-386 #1 Wed Aug 17 09:33:35 UTC 2005 i686 GNU/Linux
debian:/home/chris# uname -m
i686
debian:/home/chris# apt-get install kernel-image-2.6.8-3-686
Reading Package Lists... Done
Building Dependency Tree... Done
Suggested packages:
kernel-doc-2.6.8 kernel-source-2.6.8
The following NEW packages will be installed:
kernel-image-2.6.8-3-686
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 15.5MB of archives.
After unpacking 45.2MB of additional disk space will be used.
Get:1 http://security.debian.org stable/updates/main kernel-image-2.6.8-3-686 2.6.8-16sarge2 [15.5MB]
Fetched 15.5MB in 5m17s (48.9kB/s)
Selecting previously deselected package kernel-image-2.6.8-3-686.
(Reading database ... 94262 files and directories currently installed.)
Unpacking kernel-image-2.6.8-3-686 (from .../kernel-image-2.6.8-3-686_2.6.8-16sarge2_i386.deb) ...
Setting up kernel-image-2.6.8-3-686 (2.6.8-16sarge2) ...
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.8-3-686
(Size: 1144kB)

Initial rootdisk image: /boot/initrd.img-2.6.8-3-686 (Size: 4528kB)

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]
Testing lilo.conf ...
Testing successful.
Installing the partition boot sector...
Installation successful.

debian:/home/chris#

Well I certainly hope this works. It's the third attempt to move to 2.6 from 2.4.27. Maybe now I'll be able to print and view the network.

Mark the date, if I don't show up in the forum again you know it blew up and I've gone back to XandrOS Desktop 3.0.2 Deluxe on my laptop.