[SOLVED] cannot boot laptop, stuck with acer logo on screen, kubuntu 20.04
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
cannot boot laptop, stuck with acer logo on screen, kubuntu 20.04
Having issues getting to password field to open encrypted kubuntu 20.04, because acer logo is stuck on the screen. Tried other kernels but the issue persists, any advice on how to proceed?
Last edited by Chripcikas; 01-29-2021 at 03:38 AM.
Reason: grammar
Nothing happends when I do use "esc" and "function 2" key. Though I found out that last working kernel is 5.4.0-58-generic and that the later ones that worked before, don't now (meaning, they have current issue). Also when booting with 5.4.0-58-generic, I get "initramfs failed" message for few seconds before booting up.
Though that maybe I needed to clean up a bit so I did auto-remove and I got these errors:
Code:
sudo apt-get auto-remove
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
10 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up linux-image-5.4.0-60-generic (5.4.0-60.67) ...
Setting up initramfs-tools (0.136ubuntu6.3) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-firmware (1.187.9) ...
update-initramfs: Generating /boot/initrd.img-5.4.0-58-generic
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/kubuntu--vg-swap_1)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.4.0-58-generic with 1.
dpkg: error processing package linux-firmware (--configure):
installed linux-firmware package post-installation script subprocess returned error exit status 1
Setting up linux-image-5.4.0-65-generic (5.4.0-65.73) ...
I: /boot/initrd.img is now a symlink to initrd.img-5.4.0-65-generic
Setting up linux-image-5.4.0-64-generic (5.4.0-64.72) ...
I: /boot/initrd.img.old is now a symlink to initrd.img-5.4.0-64-generic
Setting up linux-image-5.4.0-62-generic (5.4.0-62.70) ...
Setting up linux-image-5.4.0-59-generic (5.4.0-59.65) ...
dpkg: dependency problems prevent configuration of linux-image-generic:
linux-image-generic depends on linux-firmware; however:
Package linux-firmware is not configured yet.
dpkg: error processing package linux-image-generic (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
No apport report written because the error message indicates its a followup error from a previous failure.
dpkg: dependency problems prevent configuration of linux-generic:
linux-generic depends on linux-image-generic (= 5.4.0.65.68); however:
Package linux-image-generic is not configured yet.
dpkg: error processing package linux-generic (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic-hwe-18.04:
linux-generic-hwe-18.04 depends on linux-generic; however:
Package linux-generic is not configured yet.
dpkg: error processing package linux-generic-hwe-18.04 (--configure):
dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
Processing triggers for linux-image-5.4.0-60-generic (5.4.0-60.67) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 5.4.0-60-generic
...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.0-60-generic
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/kubuntu--vg-swap_1)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.4.0-60-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-5.4.0-60-generic (--configure):
installed linux-image-5.4.0-60-generic package post-installation script subprocess returned error exit status 1
No apport report written because MaxReports is reached already
Processing triggers for initramfs-tools (0.136ubuntu6.3) ...
update-initramfs: Generating /boot/initrd.img-5.4.0-58-generic
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/kubuntu--vg-swap_1)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.4.0-58-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script subprocess returned error exit status 1
Processing triggers for linux-image-5.4.0-65-generic (5.4.0-65.73) ...
No apport report written because MaxReports is reached already
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 5.4.0-65-generic
...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.0-65-generic
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/kubuntu--vg-swap_1)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.4.0-65-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-5.4.0-65-generic (--configure):
installed linux-image-5.4.0-65-generic package post-installation script subprocess returned error exit status 1
No apport report written because MaxReports is reached already
Processing triggers for linux-image-5.4.0-64-generic (5.4.0-64.72) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 5.4.0-64-generic
...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.0-64-generic
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/kubuntu--vg-swap_1)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.4.0-64-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-5.4.0-64-generic (--configure):
installed linux-image-5.4.0-64-generic package post-installation script subprocess returned error exit status 1
No apport report written because MaxReports is reached already
Processing triggers for linux-image-5.4.0-62-generic (5.4.0-62.70) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 5.4.0-62-generic
...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.0-62-generic
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/kubuntu--vg-swap_1)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.4.0-62-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-5.4.0-62-generic (--configure):
installed linux-image-5.4.0-62-generic package post-installation script subprocess returned error exit status 1
No apport report written because MaxReports is reached already
Processing triggers for linux-image-5.4.0-59-generic (5.4.0-59.65) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 5.4.0-59-generic
...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.0-59-generic
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/kubuntu--vg-swap_1)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.4.0-59-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-5.4.0-59-generic (--configure):
installed linux-image-5.4.0-59-generic package post-installation script subprocess returned error exit status 1
No apport report written because MaxReports is reached already
Errors were encountered while processing:
linux-firmware
linux-image-generic
linux-generic
linux-generic-hwe-18.04
linux-image-5.4.0-60-generic
initramfs-tools
linux-image-5.4.0-65-generic
linux-image-5.4.0-64-generic
linux-image-5.4.0-62-generic
linux-image-5.4.0-59-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
Last edited by Chripcikas; 01-28-2021 at 10:55 PM.
Reason: additional info
Damn, you are right, but why didn't apt-autoremove work on removing old kernels? And why does the system add them all up like that? Could the upgrade from 18.04 to 20.04 be the cause?
There are different suggestions how to remove kernels manually, what is the safest way though? (ps. tried with muon package manager, got errors while doing that)
What am I doing wrong?
Code:
sudo apt purge linux-image-5.4.0-60-generic linux-modules-extra-5.4.0-60-generic linux-modules-5.4.0-60-generic
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
linux-image-5.4.0-60-generic* linux-modules-5.4.0-60-generic* linux-modules-extra-5.4.0-60-generic*
0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [J/n] j
Setting up linux-firmware (1.187.9) ...
update-initramfs: Generating /boot/initrd.img-5.4.0-58-generic
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/kubuntu--vg-swap_1)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.4.0-58-generic with 1.
dpkg: error processing package linux-firmware (--configure):
installed linux-firmware package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-generic:
linux-image-generic depends on linux-firmware; however:
Package linux-firmware is not configured yet.
dpkg: error processing package linux-image-generic (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic:
linux-generic depends on linux-image-generic (= 5.4.0.65.68); however:
Package linux-image-generic is not configured yet.
dpkg: error processing package linux-generic (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic-hwe-18.04:
linux-generic-hwe-18.04 depends on linux-generic; however:
Package linux-generic is not configured yet.
dpkg: error processing package linux-generic-hwe-18.04 (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
No apport report written because the error message indicates its a followup error from a previous failure.
No apport report written because MaxReports is reached already
Processing triggers for linux-image-5.4.0-64-generic (5.4.0-64.72) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 5.4.0-64-generic
...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.0-64-generic
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/kubuntu--vg-swap_1)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.4.0-64-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-5.4.0-64-generic (--configure):
installed linux-image-5.4.0-64-generic package post-installation script subprocess returned error exit status 1
No apport report written because MaxReports is reached already
Processing triggers for linux-image-5.4.0-62-generic (5.4.0-62.70) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 5.4.0-62-generic
...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.0-62-generic
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/kubuntu--vg-swap_1)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.4.0-62-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-5.4.0-62-generic (--configure):
installed linux-image-5.4.0-62-generic package post-installation script subprocess returned error exit status 1
No apport report written because MaxReports is reached already
Processing triggers for initramfs-tools (0.136ubuntu6.3) ...
update-initramfs: Generating /boot/initrd.img-5.4.0-58-generic
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/kubuntu--vg-swap_1)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.4.0-58-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script subprocess returned error exit status 1
No apport report written because MaxReports is reached already
Processing triggers for linux-image-5.4.0-65-generic (5.4.0-65.73) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 5.4.0-65-generic
...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.0-65-generic
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/kubuntu--vg-swap_1)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.4.0-65-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-5.4.0-65-generic (--configure):
installed linux-image-5.4.0-65-generic package post-installation script subprocess returned error exit status 1
No apport report written because MaxReports is reached already
Errors were encountered while processing:
linux-firmware
linux-image-generic
linux-generic
linux-generic-hwe-18.04
linux-image-5.4.0-64-generic
linux-image-5.4.0-62-generic
initramfs-tools
linux-image-5.4.0-65-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
Last edited by Chripcikas; 01-29-2021 at 01:52 AM.
Reason: additional info, tried to remove manually kernels
If you run the command in red above, you can easily copy/paste the package name into apt-get purge commands. In my example I would remove older kernel and headers highlighted in blue.
directory '/lib/modules/5.4.0-42-generic' not empty so not removed
There is likely a dkms folder in the directory quoted above with nvidia module that it won't remove so nothing to worry here. Can be deleted manually.
You started by removing kernel-headers which won't affect the /boot directory, boot contains the vmlinuz and initrd files which are taking up the space, they should disappear when purging the linux-image files. Every time you change bootable kernels the initrd for remaining kernels get rebuilt which requires extra disk space.
You can just go into the /boot directory and delete the initrd.img and vmlinuz files first which will create space so the next time you purge a kernel related package it will have room to create the files it's trying to create.
EDIT: Just make sure not to delete the running kernel's version files, but try purging the linux-image packages first.
The more of the parts of old kernels I've removed, the better it all got sorted out at the end. Now even the most current kernel runs without hickups and no more boot issues left.
Thank you very much!
It remains to be seen if kernels will keep piling up in the future with updates and if there is an easier solution to automate the process, where one only keep some of them and get rid of the rest. But that is for another post, I guess.
I think that recent releases of Ubuntu/Kubuntu etc. limit to keeping one kernel on updates which include a new kernel. In the past, this wasn't the case and I've seen cases where users had 20+ kernels. I would just check after updates to see if new kernels were added, the old ones removed.
I think that recent releases of Ubuntu/Kubuntu etc. limit to keeping one kernel on updates which include a new kernel. In the past, this wasn't the case and I've seen cases where users had 20+ kernels. I would just check after updates to see if new kernels were added, the old ones removed.
Not sure about that with Debian based distros. I use aptitude and it does tell (remind) me that the previous kernel version can be removed. The distros using dnf can set whatever amount of kernels to keep, Fedora, CentOS, OpenMadriva. I haven't looked hard bud not sure if that feature is available with Debian, if it is, it's not enabled by default.
Then there's the push to mimic Windows, update every day or the boogie man will get you. This strategy brought in "unattended-upgrades" which in turn conditions users into forgetting that updates are actually happening even if a pop-up shows up saying updates were applied. Next thing you know your sitting on a Gigabyte of dead kernel weight.
Anyway, since the OP's /boot is in it's own partition, suggests it is an LVM setup where you could have just expanded it to give room for another 1o+ kernels. Set up a script to boot a different kernel ever day of the month.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
