#efibootmgr — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #efibootmgr, aggregated by home.social.
-
Folgendes funktioniert also tatsächlich: man erstellt sich im modernen im #UEFI Modus installierten Betriebssystem (zB LMDE7) ein Desktop Icon, das den Befehl sudo efibootmgr -n 001A und dann einen reboot ausführt. Dann fährt der Rechner wieder runter und startet Windows 7 im #MBR Modus. #efibootmgr listet auch die Hardware #GUID des SATA #controller Dies kann man sich mit #grep im Befehl greifen. Damit wird das resistent gegen Änderungen in der Nummerierung.
-
Beim #T470 werden diese Optionen beim Start nicht alle aufgelistet, sondern nur mit #efibootmgr . Es gibt dort Optionen wie NVMe0, ATA HDD0 und ATA HDD1. Während die ersten beiden die primäre SSD starten, spricht Boot001A ATA HDD1 die SATA SSD im WWAN Steckplatz an. Das ist aber der #Legacy #MBR Boot: das Startsystem wird direkt an den Hardwarecontroller verwiesen, der auf der SATA Platte den MBR Bootsektor findet und dann loslegt. Mit efibootmgr -n 001A kann man das für einen Reboot vorwählen.
-
In case you have an UEFI dual boot Linux / Windows machine and you accidentally booted the Windows recovery once and from then on Windows keeps directly starting without GRUB showing up before so you have to get into BIOS boot selection early, it might be simply because effing Windows changed the UEFI boot order. You can find out as root/sudo by the command
efibootmgr
That displays the BootOrder along with boot menu entries and some more, like for example
BootCurrent: 0000
Timeout: 3 seconds
BootOrder: 0001,0000,2001,2002
Boot0000* Linux
Boot0001* Windows Boot Manager
Boot2001* USB
Boot2002* UEFI ShellThis shows that Windows pushed itself first in BootOrder. A simple
efibootmgr --bootorder=0,1,2001,2002
throws it back to where it belongs.
-
In case you have an UEFI dual boot Linux / Windows machine and you accidentally booted the Windows recovery once and from then on Windows keeps directly starting without GRUB showing up before so you have to get into BIOS boot selection early, it might be simply because effing Windows changed the UEFI boot order. You can find out as root/sudo by the command
efibootmgr
That displays the BootOrder along with boot menu entries and some more, like for example
BootCurrent: 0000
Timeout: 3 seconds
BootOrder: 0001,0000,2001,2002
Boot0000* Linux
Boot0001* Windows Boot Manager
Boot2001* USB
Boot2002* UEFI ShellThis shows that Windows pushed itself first in BootOrder. A simple
efibootmgr --bootorder=0,1,2001,2002
throws it back to where it belongs.
-
In case you have an UEFI dual boot Linux / Windows machine and you accidentally booted the Windows recovery once and from then on Windows keeps directly starting without GRUB showing up before so you have to get into BIOS boot selection early, it might be simply because effing Windows changed the UEFI boot order. You can find out as root/sudo by the command
efibootmgr
That displays the BootOrder along with boot menu entries and some more, like for example
BootCurrent: 0000
Timeout: 3 seconds
BootOrder: 0001,0000,2001,2002
Boot0000* Linux
Boot0001* Windows Boot Manager
Boot2001* USB
Boot2002* UEFI ShellThis shows that Windows pushed itself first in BootOrder. A simple
efibootmgr --bootorder=0,1,2001,2002
throws it back to where it belongs.
-
In case you have an UEFI dual boot Linux / Windows machine and you accidentally booted the Windows recovery once and from then on Windows keeps directly starting without GRUB showing up before so you have to get into BIOS boot selection early, it might be simply because effing Windows changed the UEFI boot order. You can find out as root/sudo by the command
efibootmgr
That displays the BootOrder along with boot menu entries and some more, like for example
BootCurrent: 0000
Timeout: 3 seconds
BootOrder: 0001,0000,2001,2002
Boot0000* Linux
Boot0001* Windows Boot Manager
Boot2001* USB
Boot2002* UEFI ShellThis shows that Windows pushed itself first in BootOrder. A simple
efibootmgr --bootorder=0,1,2001,2002
throws it back to where it belongs.
-
In case you have an UEFI dual boot Linux / Windows machine and you accidentally booted the Windows recovery once and from then on Windows keeps directly starting without GRUB showing up before so you have to get into BIOS boot selection early, it might be simply because effing Windows changed the UEFI boot order. You can find out as root/sudo by the command
efibootmgr
That displays the BootOrder along with boot menu entries and some more, like for example
BootCurrent: 0000
Timeout: 3 seconds
BootOrder: 0001,0000,2001,2002
Boot0000* Linux
Boot0001* Windows Boot Manager
Boot2001* USB
Boot2002* UEFI ShellThis shows that Windows pushed itself first in BootOrder. A simple
efibootmgr --bootorder=0,1,2001,2002
throws it back to where it belongs.
-
Just showing off my #thinkpad x240’s startup times on #archlinux and I wanted to know if you guys got any better times. (I know somehow out there will have one.)
#limine had a timeout of 1 second and I used #efibootmgr to make my BIOS timeout 1 second as well.
#linux #challenge #computers #tech #technology #interesting #cool
-
Just showing off my #thinkpad x240’s startup times on #archlinux and I wanted to know if you guys got any better times. (I know somehow out there will have one.)
#limine had a timeout of 1 second and I used #efibootmgr to make my BIOS timeout 1 second as well.
#linux #challenge #computers #tech #technology #interesting #cool
-
Just showing off my #thinkpad x240’s startup times on #archlinux and I wanted to know if you guys got any better times. (I know somehow out there will have one.)
#limine had a timeout of 1 second and I used #efibootmgr to make my BIOS timeout 1 second as well.
#linux #challenge #computers #tech #technology #interesting #cool
-
Just showing off my #thinkpad x240’s startup times on #archlinux and I wanted to know if you guys got any better times. (I know somehow out there will have one.)
#limine had a timeout of 1 second and I used #efibootmgr to make my BIOS timeout 1 second as well.
#linux #challenge #computers #tech #technology #interesting #cool
-
Just showing off my #thinkpad x240’s startup times on #archlinux and I wanted to know if you guys got any better times. (I know somehow out there will have one.)
#limine had a timeout of 1 second and I used #efibootmgr to make my BIOS timeout 1 second as well.
#linux #challenge #computers #tech #technology #interesting #cool
-
Random Linux fix: machine would not obey changes to efibootmgr... kept on repopulating (old) grub entry. Fix was to delete the folder in /boot/efi manually. Also UEFI sucks. #Linux #efibootmgr #uefi
-
Random Linux fix: machine would not obey changes to efibootmgr... kept on repopulating (old) grub entry. Fix was to delete the folder in /boot/efi manually. Also UEFI sucks. #Linux #efibootmgr #uefi
-
Random Linux fix: machine would not obey changes to efibootmgr... kept on repopulating (old) grub entry. Fix was to delete the folder in /boot/efi manually. Also UEFI sucks. #Linux #efibootmgr #uefi
-
Random Linux fix: machine would not obey changes to efibootmgr... kept on repopulating (old) grub entry. Fix was to delete the folder in /boot/efi manually. Also UEFI sucks. #Linux #efibootmgr #uefi
-
Random Linux fix: machine would not obey changes to efibootmgr... kept on repopulating (old) grub entry. Fix was to delete the folder in /boot/efi manually. Also UEFI sucks. #Linux #efibootmgr #uefi
-
Woaaa, eh les devs de #efibootmgr.
C’est pas parce que vous touchez à des trucs bas-niveau qu’il faut que votre cli soit illisible et imbitable, eh. -
Woaaa, eh les devs de #efibootmgr.
C’est pas parce que vous touchez à des trucs bas-niveau qu’il faut que votre cli soit illisible et imbitable, eh. -
Woaaa, eh les devs de #efibootmgr.
C’est pas parce que vous touchez à des trucs bas-niveau qu’il faut que votre cli soit illisible et imbitable, eh. -
Woaaa, eh les devs de #efibootmgr.
C’est pas parce que vous touchez à des trucs bas-niveau qu’il faut que votre cli soit illisible et imbitable, eh. -
Dug my way into a deep rabbithole last night, while working on an A/B update system based on #RAUC .
Turns out #efibootmgr 18 changed its default output to be more verbose and broke the assumptions made by #RAUCPatching up a C codebase was not on my list of things for last night, but alas, here we are:
https://github.com/rauc/rauc/pull/1197 -
Dug my way into a deep rabbithole last night, while working on an A/B update system based on #RAUC .
Turns out #efibootmgr 18 changed its default output to be more verbose and broke the assumptions made by #RAUCPatching up a C codebase was not on my list of things for last night, but alas, here we are:
https://github.com/rauc/rauc/pull/1197 -
Dug my way into a deep rabbithole last night, while working on an A/B update system based on #RAUC .
Turns out #efibootmgr 18 changed its default output to be more verbose and broke the assumptions made by #RAUCPatching up a C codebase was not on my list of things for last night, but alas, here we are:
https://github.com/rauc/rauc/pull/1197 -
Dug my way into a deep rabbithole last night, while working on an A/B update system based on #RAUC .
Turns out #efibootmgr 18 changed its default output to be more verbose and broke the assumptions made by #RAUCPatching up a C codebase was not on my list of things for last night, but alas, here we are:
https://github.com/rauc/rauc/pull/1197 -
Dug my way into a deep rabbithole last night, while working on an A/B update system based on #RAUC .
Turns out #efibootmgr 18 changed its default output to be more verbose and broke the assumptions made by #RAUCPatching up a C codebase was not on my list of things for last night, but alas, here we are:
https://github.com/rauc/rauc/pull/1197 -
@ology @Moray
Right now I am attempting a desktop that I can sell not just use. Key issue is that Gnome is not easily modded. Kubuntu, on the other hand.... it's a distraction.Plan is to figure out UEFI using efibootmgr (dot exe). Add and remove distros fully-native with gparted. #efibootmgr needs a gui (badly).
I am starting with Alpine because they too are in the learning process.
-
@ology @Moray
Right now I am attempting a desktop that I can sell not just use. Key issue is that Gnome is not easily modded. Kubuntu, on the other hand.... it's a distraction.Plan is to figure out UEFI using efibootmgr (dot exe). Add and remove distros fully-native with gparted. #efibootmgr needs a gui (badly).
I am starting with Alpine because they too are in the learning process.
-
@ology @Moray
Right now I am attempting a desktop that I can sell not just use. Key issue is that Gnome is not easily modded. Kubuntu, on the other hand.... it's a distraction.Plan is to figure out UEFI using efibootmgr (dot exe). Add and remove distros fully-native with gparted. #efibootmgr needs a gui (badly).
I am starting with Alpine because they too are in the learning process.
-
@ology @Moray
Right now I am attempting a desktop that I can sell not just use. Key issue is that Gnome is not easily modded. Kubuntu, on the other hand.... it's a distraction.Plan is to figure out UEFI using efibootmgr (dot exe). Add and remove distros fully-native with gparted. #efibootmgr needs a gui (badly).
I am starting with Alpine because they too are in the learning process.
-
