Results 1 to 4 of 4

Thread: 2.6.30.7 error

  1. #1
    Member iceman_3233's Avatar
    Join Date
    Jan 2010
    Location
    Fort Washington
    Posts
    56

    Default 2.6.30.7 error

    Trying to update to the latest image and I keep on getting the following error. When I reboot Grub does not show the new image? Still shows 2.6.30.5. I checked the Grub menu lst and do not see the new image?

    dpkg -i --force-all linux-image-2.6.30.7_2.6.30.7-10.00.Custom_i386.deb
    (Reading database ... 200688 files and directories currently installed.)
    Preparing to replace linux-image-2.6.30.7 2.6.30.7-10.00.Custom (using linux-image-2.6.30.7_2.6.30.7-10.00.Custom_i386.deb) ...
    Done.
    Unpacking replacement linux-image-2.6.30.7 ...
    Running postrm hook script /sbin/update-grub.
    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 ... found: /boot/grub/splash.xpm.gz
    Found kernel: /boot/vmlinuz-2.6.30.7
    Found kernel: /boot/vmlinuz-2.6.30.5
    Found kernel: /boot/vmlinuz-2.6.29.4
    Found kernel: /boot/memtest86+.bin
    Updating /boot/grub/menu.lst ... done

    Setting up linux-image-2.6.30.7 (2.6.30.7-10.00.Custom) ...

    Hmm. There is a symbolic link /lib/modules/2.6.30.7/build
    However, I can not read it: No such file or directory
    Therefore, I am deleting /lib/modules/2.6.30.7/build


    Hmm. The package shipped with a symbolic link /lib/modules/2.6.30.7/source
    However, I can not read the target: No such file or directory
    Therefore, I am deleting /lib/modules/2.6.30.7/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.30.7-10.00.Custom was configured last, according to dpkg)
    Not updating image symbolic links since we are being updated/reinstalled
    (2.6.30.7-10.00.Custom was configured last, according to dpkg)
    Running postinst hook script update-grub.
    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 ... found: /boot/grub/splash.xpm.gz
    Found kernel: /boot/vmlinuz-2.6.30.7
    Found kernel: /boot/vmlinuz-2.6.30.5
    Found kernel: /boot/vmlinuz-2.6.29.4
    Found kernel: /boot/memtest86+.bin
    Updating /boot/grub/menu.lst ... done
    The enemy is no longer ignorance - It is vigilance

  2. #2
    My life is this forum Barry's Avatar
    Join Date
    Jan 2010
    Posts
    3,817

    Default

    I deleted /lib/modules/2.6.* first, then ran the installer. If the kernel shows up on /boot/ you can edit your menu.lst to put it first.

  3. #3
    Member iceman_3233's Avatar
    Join Date
    Jan 2010
    Location
    Fort Washington
    Posts
    56

    Default

    Thanks for the quick response Barry. Do I rm /lib/modules/2.6.30.7/build or /lib/modules/2.6.30.7/source?
    The enemy is no longer ignorance - It is vigilance

  4. #4
    My life is this forum Barry's Avatar
    Join Date
    Jan 2010
    Posts
    3,817

    Default

    Quote Originally Posted by iceman_3233 View Post
    Thanks for the quick response Barry. Do I rm /lib/modules/2.6.30.7/build or /lib/modules/2.6.30.7/source?
    I did a rm /lib/modules/2.6* . The installer will put back what it needs.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •