Trying to upgrade to nvidia-kernel with aptitude and got the error:
....
Unpacking nvidia-kernel-source (from .../nvidia-kernel-source_1.0.7174-3_i386.deb) ...
Selecting previously deselected package patchutils.
Unpacking patchutils (from .../patchutils_0.2.30-1_i386.deb) ...
Setting up dpatch (2.0.10) ...
Setting up kernel-image-2.4.27-2-386 (2.4.27-10sarge1) ...
/bin/bash: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or 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 9
....

Kind of worried that if I turn off the power, my machine won't boot,
so I tried to install a different non-nvidia kernel, but got the
same error. Will be able to reboot when I turn off the power,
or should I keep trying different aptitude loading of different
kernels until one installs without the error?
Any way to fix the error?

Thanks
J


_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Hi,

> Setting up kernel-image-2.4.27-2-386 (2.4.27-10sarge1) ...
> /bin/bash: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or 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 9
> ...
>

Check up if there's a symlink for /lib/libdl-2.3.2.so to
/lib/libdl.so.2. If not, create one.

> Kind of worried that if I turn off the power, my machine won't boot,
> so I tried to install a different non-nvidia kernel, but got the
> same error. Will be able to reboot when I turn off the power,
> or should I keep trying different aptitude loading of different
> kernels until one installs without the error?
> Any way to fix the error?

Since your boot loader (Grub) is not updated and you still retain your
old kernel, rebooting should not affect your system. It should reboot
into your current kernel.

Regards,

--
- Shashishekhar S
Consultant - Debian GNU/Linux
Remote Administration, Deployments
Mail Services, Tips and Tricks


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org