[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Cannot update kernel



On Mon, Jan 28, 2008 at 08:02:51PM +0200, Dotan Cohen wrote:
> On Debian Etch on a white box AMD machine with 1GB RAM, I cannot
> update the system. This is what I get:
> 
> myhome:/home/zeev# apt-get update
...
> Hit http://ftp.de.debian.org etch/non-free Packages
> Fetched 6861kB in 1m33s (73.1kB/s)
> E: dpkg was interrupted, you must manually run 'dpkg --configure -a'
> to correct
>                                       the problem.
> myhome:/home/zeev# dpkg --configure -a

okay, this looks like it succeeded, so I'm not sure why you went
through all the dpkg manual stuff, but okay.
...

The apt-get below looks like it succeeded, so I'm not sure what the
problem is here. initrd got built, grub got updated. Looks successful
to me. 

> myhome:/home/zeev# apt-get -f install
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following extra packages will be installed:
>   linux-image-2.6.18-5-486
> Suggested packages:
>   linux-doc-2.6.18
> The following packages will be upgraded:
>   linux-image-2.6.18-5-486
> 1 upgraded, 0 newly installed, 0 to remove and 607 not upgraded.
> 1 not fully installed or removed.
> Need to get 0B/16.2MB of archives.
> After unpacking 1896kB of additional disk space will be used.
> Do you want to continue [Y/n]? y
> Preconfiguring packages ...
> (Reading database ... 70759 files and directories currently installed.)
> Preparing to replace linux-image-2.6.18-5-486 2.6.18.dfsg.1-13 (using
> .../linux-image-2.6.18-5-486_2.6.18.dfsg.1-17_i386.deb) ...
> The directory /lib/modules/2.6.18-5-486 still exists. Continuing as directed.
> Done.
> Unpacking replacement linux-image-2.6.18-5-486 ...
> Running postrm hook script /sbin/update-grub.
> You shouldn't call /sbin/update-grub. Please call /usr/sbin/update-grub instead!
> 
> Searching for GRUB installation directory ... found: /boot/grub
> Searching for default file ... found: /boot/grub/default
> Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
> Searching for splash image ... none found, skipping ...
> Found kernel: /boot/vmlinuz-2.6.18-5-486
> Updating /boot/grub/menu.lst ... done
> 
> Setting up linux-image-2.6.18-5-486 (2.6.18.dfsg.1-17) ...
> 
>  Hmm. The package shipped with a symbolic link /lib/modules/2.6.18-5-486/source
>  However, I can not read the target: No such file or directory
>  Therefore, I am deleting /lib/modules/2.6.18-5-486/source
> 
> Running depmod.
> Finding valid ramdisk creators.
> Using mkinitramfs-kpkg to build the ramdisk.
> Not updating initrd symbolic links since we are being updated/reinstalled
> (2.6.18.dfsg.1-13 was configured last, according to dpkg)
> Not updating image symbolic links since we are being updated/reinstalled
> (2.6.18.dfsg.1-13 was configured last, according to dpkg)
> Running postinst hook script /sbin/update-grub.
> You shouldn't call /sbin/update-grub. Please call /usr/sbin/update-grub instead!
> 
> Searching for GRUB installation directory ... found: /boot/grub
> Searching for default file ... found: /boot/grub/default
> Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
> Searching for splash image ... none found, skipping ...
> Found kernel: /boot/vmlinuz-2.6.18-5-486
> Updating /boot/grub/menu.lst ... done
> 
> myhome:/home/zeev#
> 

I guess you should check the contents of /boot to confirm it's all
okay, but I don't see any problems here. 

A

Attachment: signature.asc
Description: Digital signature


Reply to: