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.
mint@mint:~$ sudo efibootmgr
BootCurrent: 0002
Timeout: 0 seconds
No BootOrder is set; firmware will attempt recovery
Boot0000* Network Adapter (IPv4 UEFI)
Boot0001* Network Adapter (IPv6 UEFI)
Boot0002* USB Hard Drive (UEFI) - SanDisk (SanDisk)
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot3001* Internal Hard Disk or Solid State Disk
Even after clean install in my internal HDD EFI fails to load and cant see any installed OS. Can anyone help me out?
Thank you
What is your system? I had a asus a while back that would do this, efibootmgr would not work with the system bios, I would have to go into bios by using esc/f-key to get into system bios settings and change the boot order.
Open a terminal and post the output of
Sir, since i had BIOS and because of that my EFI partition was not bootable i suppose,so just switched the EFI partition to BIOS /boot in mint-installation. The system booted though, after running sudo apt update and sudo apt upgrade the system now is stuck in "log in" , when i enter password and error prompts ": unable to launch 'cinnamon-session-cinnamon' X session --- 'cinnamon-session-cinnamon' not found; falling back to default session."
Back to log in session
Can't find way to GRUB to force boot with vmlinuz, initrid.img ...
Or is there any other way??
to get the grub menu hold down the shift key when you first boot, and should be able to select different kernel.
to get to a terminal at the grub menu press e for edit and add text to end of line that begins with Linux or after booting into system alt-ctrl-f1 should give you a terminal.
Thank you Sir, was thinking of resetting my userid and repos.but running install mint-meta-cinnamon worked.
however, i got this error:
Unpacking ubuntu-minimal (1.417.3) over (1.417.2) ...
Setting up grub-efi-amd64-signed (1.93.14+2.02-2ubuntu8.13) ...
Installing for x86_64-efi platform.
Could not prepare Boot variable: No space left on device
grub-install: error: efibootmgr failed to register the boot entry: Input/output error.
dpkg: error processing package grub-efi-amd64-signed (--configure):
installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
Setting up ubuntu-minimal (1.417.3) ...
dpkg: dependency problems prevent configuration of shim-signed:
shim-signed depends on grub-efi-amd64-signed; however:
Package grub-efi-amd64-signed is not configured yet.
dpkg: error processing package shim-signed (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
Errors were encountered while processing:
grub-efi-amd64-signed
shim-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Quite annoying since everything seems well but such error is inevitable. Any suggestion or two?
Last edited by lonstt0ner; 08-01-2019 at 05:25 AM.
secure boot, legacy boot were set to disable before the installation.
Well everything seems to run smoothly for now , just:grub-efi-amd64-signed
shim-signed
are not bring updated.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.