LINUX LITE 7.2 FINAL RELEASED - SEE RELEASE ANNOUNCEMENTS SECTION FOR DETAILS


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Broken packages linux kernel
#11
Ok then. Try:


Code:
sudo apt-get remove --purge linux-image-extra-4.4.0-78-generic -y
sudo apt-get autoremove
sudo update-grub
[color=rgb(17, 17, 17)][/color]
https://unlockforus.com

Sorry for seeming stupid and preferring Linux - I just don't know any better.

[Image: AGxgqJ6.png]
Reply
#12
here's the readout... logged out, logged in, still no update

me:~$ sudo apt-get remove --purge linux-image-extra-4.4.0-78-generic -y
[sudo] password for me:
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
linux-image-generic : Depends: linux-image-4.4.0-78-generic but it is not going to be installed
Depends: linux-image-extra-4.4.0-78-generic but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
me:~$ sudo apt-get autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
linux-image-extra-4.4.0-78-generic : Depends: linux-image-4.4.0-78-generic but it is not installed
linux-image-generic : Depends: linux-image-4.4.0-78-generic but it is not installed
E: Unmet dependencies. Try using -f.
me:~$ sudo update-grub
Generating grub configuration file ...
Found background: /boot/grub_linux_lite.png
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
Found background image: /boot/grub_linux_lite.png
Found linux image: /boot/vmlinuz-4.4.0-75-generic
Found initrd image: /boot/initrd.img-4.4.0-75-generic
Found linux image: /boot/vmlinuz-4.4.0-72-generic
Found initrd image: /boot/initrd.img-4.4.0-72-generic
Found linux image: /boot/vmlinuz-4.4.0-71-generic
Found initrd image: /boot/initrd.img-4.4.0-71-generic
Found linux image: /boot/vmlinuz-4.4.0-67-generic
Found initrd image: /boot/initrd.img-4.4.0-67-generic
Found linux image: /boot/vmlinuz-4.4.0-66-generic
Found initrd image: /boot/initrd.img-4.4.0-66-generic
Found linux image: /boot/vmlinuz-4.4.0-64-generic
Found initrd image: /boot/initrd.img-4.4.0-64-generic
Found linux image: /boot/vmlinuz-4.4.0-63-generic
Found initrd image: /boot/initrd.img-4.4.0-63-generic
Found linux image: /boot/vmlinuz-4.4.0-62-generic
Found initrd image: /boot/initrd.img-4.4.0-62-generic
Found linux image: /boot/vmlinuz-4.4.0-59-generic
Found initrd image: /boot/initrd.img-4.4.0-59-generic
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
done
Reply
#13
Ok amigo. The problem is that you've ran out of space in your /boot because of all the installed images and apt cannot fix it... at least not in its current state because we can't force the install yet.

Here is what we will do next. We will use dpgk instead. This is a little drastic and can be dangerous at times but it is what will help us this time around. From what you have posted, you are currently running kernel 4.4.0-75-generic.

So, we will delete some of those kernels images you are not using to free up some space first... from Terminal:

Code:
sudo dpkg --force-all -P linux-image-4.4.0-62-generic
sudo dpkg --force-all -P linux-image-4.4.0-63-generic
sudo dpkg --force-all -P linux-image-4.4.0-64-generic
sudo dpkg --force-all -P linux-image-4.4.0-66-generic

That should go trough without errors. Then, since some space has been recovered at this point, you will fix the umet dependencies:

Code:
sudo apt-get -f autoremove

The above should force the removal of dependencies this time around.

Finally, clean up:

Code:
sudo apt-get autoclean
sudo apt-get autoremove
sudo apt-get update
sudo apt-get upgrade

Let us know.
https://unlockforus.com

Sorry for seeming stupid and preferring Linux - I just don't know any better.

[Image: AGxgqJ6.png]
Reply
#14
No broken packages showing.  I'll go through stuff tomorrow and verify. Thx and blessings to ya ralphy.
Reply
#15
That's great [member=4822]amigo[/member] , you're awesome! Smile

To recover some more space and prevent this from happening again any time soon, I'd use Lite Tweaks now that no broken packages are showing to remove old kernels in the system that are not longer being used. Usually, I leave no more than 1 or 2 previous kernels in the system. You could do the same if that fits your needs.

All the best!
https://unlockforus.com

Sorry for seeming stupid and preferring Linux - I just don't know any better.

[Image: AGxgqJ6.png]
Reply


Forum Jump:


Users browsing this thread: 5 Guest(s)