Thanks for the hint.
The commands I used to restore the entry were
efibootmgr -v -c -u -L Qubes -l /EFI/qubes/xen.efi -d /dev/sda1 -p 1
efibootmgr -o 0,1
Now I can boot Qubes using the UEFI boot manager again.
On 10/15/18 8:19 PM, 'awokd' via qubes-users wrote:
Stephan Marwedel:
I have
installation on device nvme0n1p2 and entered LUKS passphrase
- Got Shell
- Changes made to files still visible in /mnt/sysimage/boot/efi/EFI/qubes
- Ran the efibootmgr command as shown in the guide, but adjusted devicename. I
didn’t know whether I should add nvme0n1 or nvme0, or maybe even nvme0n1p
ir script,
running these commands helped me in a similar situation:
man efibootmgr
efibootmgr -c -L Qubes -l /EFI/qubes/xen.efi
(the -L is very much optional, the -l not so much :)
--
cheers,
Holger
--
You received this message because you are subscribed to the Google Groups
&qu
o after
> > Any suggestions?
>
> after you chrooted into the system as suggested by the repair script,
> running these commands helped me in a similar situation:
>
> man efibootmgr
> efibootmgr -c -L Qubes -l /EFI/qubes/xen.efi
>
> (the -L is very much optiona
It seems it ignores your mountpoint, you pass directly the hard disk and
EFI partition number (which should be the first) so in:
efibootmgr -v -c -u -L Qubes -l /EFI/qubes/xen.efi -d /dev/sda -p 1
"placeholder /mapbs /noexitboot"
You only have to worry abou
If that's internal disk, you should be able to configure UEFI to use
/boot/efi/EFI/qubes. In fact, installer should do that for you... You
can do that either in UEFI setup (some vendors have include it
somewhere near boot order setting), or using efibootmgr from within the
system. You want
-n 1)\" >> /etc/default/grub
# grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
# efibootmgr -c -d /dev/sda -p 1 -L "Fedora-Grub" -l
"\EFI\fedora\grubx64.efi"
Note: this will change your default EFI boot entry! You can change it
back with `efibootmgr -o`. Here's a
tions for editing the EFI boot listings (from the
> > documentation you linked me to) isn't working. When I go through the
> steps
> > with efibootmgr the new listing for Qubes ends up looking like this at
> the
> > end:
> >
> > p.l.a.c.e.h.o.l.d.e.r. ./.m.a.p.b.
Hi,
so here is a status :
Whatever I do with Qubes OS 3.2-rc3 the efibootmgr is not saved for long
I did this :
efibootmgr -v -c -u -L Qubes -l /EFI/qubes/xen.efi -d /dev/sda -p 1
"placeholder /mapbs /noexitboot"
So I can see the entry in the command
efibootmgr -v
I a reb
ble
to run efibootmgr directly while in legacy boot mode ("EFI variables are
not supported on this system") so in order to run efibootmgr, i booted a
separate Fedora 26 Live image which does boot in UEFI mode. However, even
with updated records, the result is the same: selecting those options fro
on after installing Qubes OS, I don't even get grub.- I
> tried the UEFI troubleshooting guide to no avail, although I was unable to
> run efibootmgr directly while in legacy boot mode ("EFI variables are not
> supported on this system") so in order to run efibootmgr, i boo
I just got my P52, and when I try and install qubes, there doesn't seem to be
an efi entry. I tried to boot into a live drive and add it in via efibootmgr,
but it keeps looping back to the lenovo boot menu.
--
You received this message because you are subscribed to the Google Groups
"
I finally got qubes 3.2.1 to install in UEFI mode, and the xen.cfg is there and
I can see the efi boot manager entry by using efibootmgr. However, there is no
boot option for qubes. What could be causing this?
Dell G7 15
--
You received this message because you are subscribed to the Google
seem small. Do the seem correct??
> Are there files missing?? Could maybe someone check these md5sums, please?
>
Probably the initramfs differ due different hardware or configuration.
vmlinuz image seems fine.
> (3) I could try the " efibootmgr " commands mentioned in UEFI
tro
oth Qubes-OS R4.0 RC1 and Qubes-OS R3.2 USB drives to
be able to boot into the rescue mode and use efibootmgr. the efibootmgr
is R4.0 RC1 does not like to play with the GPT formatted NVME drive I
have, and registers the boot record as an MBR drive.
Step 6: Use Fedora to dd Qubes-OS R3.2 to a USB dr
oth Qubes-OS R4.0 RC1 and Qubes-OS R3.2 USB drives to
be able to boot into the rescue mode and use efibootmgr. the efibootmgr
is R4.0 RC1 does not like to play with the GPT formatted NVME drive I
have, and registers the boot record as an MBR drive.
Step 6: Use Fedora to dd Qubes-OS R3.2 to a USB dr
.
How can one recover the UEFI boot environment of Qubes 4.0? I tried
using the Qubes installer but there is no shell access to run
grub-install or efibootmgr. Can I do it from the Archlinux drive or a
Fedora boot media?
Yes, Fedora boot media should work. Try searching this list for
"efibo
SATA ACPI mode, installation kernel
parameter nouveau.modeset=0. The efibootmgr fix doesn't work in rescue mode, I
think that's due to not loading the install via UEFI. efibootmgr will run fine
from another liveCD booted through UEFI but it doesn't seem to help.
--
You received this message b
ut running the
efibootmgr command, which doesn't run because there is no efivars kernel module.
I personally hate UEFI, but these newer systems leave you no choice -- you
CANNOT boot from an internal drive without it. Does anyone know how to resolve
this? I have a nice and very expensive bric
Thanks a lot!
In my case I loaded from Live USB Fedora and used the command:
efibootmgr -v -c -L Qubes -l /EFI/qubes/xen.efi -d /dev/nvme0n1p1
вторник, 22 сентября 2020 г. в 03:20:37 UTC+3, awokd:
> load...@gmail.com:
> > Hi everyone, need any help, because I am stuck.
> >
>
acy BIOS boot on both source &
>> destination. UEFI boot might need a command on the destination system to
>> add the new boot source, something like efibootmgr.
>>
>> --
>> - don't top post
>> Mailing list etiquette:
>> - trim quoted reply to only rel
On 1/30/21 6:14 PM, haa...@web.de wrote:
> root@debian:~# efibootmgr -v -c -u -L Qubes -l /EFI/qubes/xen.efi -d
> /dev/nvme0n1 -p 1 "placeholder /mapbs /noexitboot"
> efibootmgr: ** Warning ** : Boot0002 has same label Qubes
> BootCurrent: 0001
> Timeout: 0 secon
ies.
good.
So with nothing to lose I tried to fix the boot manually from a live USB
including creating /etc/default/grub but situation is no better.
I had similar problems recently. If it is UEFI (and I guess so),
efibootmgr is your friend (not preinstalled on debian-live, but you grab
it easily v
up and running is
> > greatly appreciated. It's a wonderful operating system and I'd love to
> > keep using it.
>
> Try booting recovery mode and recreating your UEFI boot entry with
> efibootmgr like
> https://groups.google.com/d/msg/qubes-users/3Z52efsCTg0/OI2LiPAMAQAJ
/ folder where xen.cfg is located, then
> modify the copied xen.cfg to choose a different kernel. Then add a new boot
> entry (which I can only select to boot from by entering BIOS btw), which will
> be set as default when added by this command:
>
> first see what we have:
> $sudo
n UEFI mode on after installing Qubes OS, I don't even get
> grub.
> - I tried the UEFI troubleshooting guide to no avail, although I was
> unable to run efibootmgr directly while in legacy boot mode ("EFI
> variables are not supported on this system") so in order to run
after installing Qubes OS, I don't even get grub.- I
> tried the UEFI troubleshooting guide to no avail, although I was unable to
> run efibootmgr directly while in legacy boot mode ("EFI variables are not
> supported on this system") so in order to run efibootmgr, i booted a
anything bootable and will boot it.
I had to use an additional Linux installation with a more recent kernel to set
the boot entry with efibootmgr. Maybe it works from Qubes if you update to the
4.9 kernel first.
Cheers,
Torsten
--
You received this message because you are subscribed
Qubes in the BIOS, Ubuntu will boot.
Result of efibootmgr command is:
BootCurrent:
Timeout: 1 seconds
BootOrder: 0002,,0005,0001,0007
Boot* ubuntu
Boot0001* Hard Drive
Boot0002* Qubes
Boot0005* CD/DVD Drive
Boot0007* Removable Drive
>From my understanding, it says that Qu
Qubes Recovery option were
> >>> unsuccessful. I did find a recommendation to use reFInd on the Qubes
> >>> website but the instructions are not sufficiently detailed for me to
> >>> follow them.
> >>>
> >>> Any assistance to help me
tly detailed for me to follow them.
>>>
>>> Any assistance to help me get my Qubes systems back up and running is
>>> greatly appreciated. It's a wonderful operating system and I'd love to
>>> keep using it.
>>
>> Try booting recovery mode and recreating yo
. everything went fine but I there was no boot option for it. Also,
I ended up with no xen.efi file, xen.cfg was empty, and I couldnt use
efibootmgr, "efi variables not supported" is the error I would get. The only
extra parameters I used were "nouveau.modeset=0 rd.driver.blacklist=nouveau
Jcarter:
I just got my P52, and when I try and install qubes, there doesn't seem to be
an efi entry. I tried to boot into a live drive and add it in via efibootmgr,
but it keeps looping back to the lenovo boot menu.
Have you seen
https://www.qubes-os.org/doc/uefi-troubleshooting/#boot-device
jonull...@gmail.com wrote on 2/6/19 8:43 PM:
Installing works in Legacy External device boot
->sh-4.3# efibootmgr
EFI variables are not supported on this system.
trying to allocate efivars, but cannot find it, and a few grubs directories.
From what i understand it's not necessary to
On Thursday, January 24, 2019 at 12:22:11 AM UTC-6, gunnar...@gmail.com wrote:
> I finally got qubes 3.2.1 to install in UEFI mode, and the xen.cfg is there
> and I can see the efi boot manager entry by using efibootmgr. However, there
> is no boot option for qubes. What could b
> Dual-booting is a pain. I did it for a while on one of my machines and
> Windows kept breaking GRUB every major update. When you add the below
> hard drive, you might have to regenerate your Qubes UEFI boot entry.
> Search this list for efibootmgr if that happens.
I dual boot
ed Qubes into the
> first "slot". I still have to install another Qubes instance into the second
> "slot" and make sure
> they both work. I'll follow up when I do.
The dual ESP approach seems to be working fine for me, but you do have to
manually fiddle around with
ou could make your own directories by copying the
>> files. e.g. /boot/efi/EFI/qubes{0,1}/, but when it updates (or you
>> reinstall one of them), they would both try to install to
>> /boot/efi/EFI/qubes/ again. And you'd have to manually change the path
>> each time with ef
cue
boot or from a Livecd and create a Qubes boot entry with efibootmgr.
--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots
--
You received this message because you are subscribed to th
es OS*, I couldn't.
> In BIOS my drive is visible like working device, but *in Boot Menu it does
> not exist anymore*.
Search this mailing list for "efibootmgr"- you should find an example
command on how to recreate your Qubes EFI boot menu entry.
--
- don't top post
Mailing l
UEFI boot might need a command on the destination system to
add the new boot source, something like efibootmgr.
--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots
--
You received this message because y
..." (2)).
> Installing anyway results in no Qubes boot option on reboot. (3)
> Running efibootmgr -v from a live usb reports a Qubes entry at VenHw (instead
> of a HD).
>
> The laptop I used also had a non-nvme disk, and accepting automatic
> partitioning put a new
3
Hmm, this actually may be a problem. I'm not sure what
status=8003 is, but if accessing efivars does not work,
efibootmgr would not work, so can't add Qubes entry. Does `efibootmgr
- -v` show anything?
Other than that, I also can't see anything interesting.
- --
Best Regards,
Mar
EFI firmware (replace /dev/sda with your disk name and -p
1 with /boot/efi partition number):
efibootmgr -v -c -u -L Qubes -l /EFI/qubes/xen.efi -d /dev/sda -p 1
"placeholder /mapbs /noexitboot"
-------
->sh-4.3# efibootmgr
EFI variables are not supported
Den torsdag 7 februari 2019 kl. 06:51:24 UTC+1 skrev awokd:
> jonull...@gmail.com wrote on 2/6/19 8:43 PM:
>
> > Installing works in Legacy External device boot
>
> > ->sh-4.3# efibootmgr
> > EFI variables are not supported on this system.
>
> > tryi
jonull...@gmail.com wrote on 2/9/19 6:32 PM:
Den torsdag 7 februari 2019 kl. 06:51:24 UTC+1 skrev awokd:
jonull...@gmail.com wrote on 2/6/19 8:43 PM:
Installing works in Legacy External device boot
->sh-4.3# efibootmgr
EFI variables are not supported on this system.
trying to alloc
(or you
> reinstall one of them), they would both try to install to
> /boot/efi/EFI/qubes/ again. And you'd have to manually change the path
> each time with efibootmgr.
This is partly what I need to do anyways on an older UEFI system. I
wrote a script that copies the updated files over t
52ab8 vmlinuz-5.10.8-1.qubes.x86_64
0834cc9a9bfbacb9cfc420f3b879bca7 vmlinuz-5.4.91-1.fc25.qubes.x86_64
Probably the initramfs differ due different hardware or configuration.
vmlinuz image seems fine.
> (3) I could try the " efibootmgr " commands mentioned in UEFI
troubleshooting, but
oot entry (which I can only select to boot from by entering BIOS btw),
> > which will be set as default when added by this command:
> >
> > first see what we have:
> > $sudo efibootmgr -v
> > then add one more (BIOS-visible) entry:
> > $ sudo efibootmgr -v -c
onfiguration
- --
For some reason the EFI entry generated by the Qubes installer doesn't
work, which is why we had to use the rEFInd live USB stick until now to
boot the machine. This can be fixed, by downloading the following
packets via rpmfind.net:
* efibootmgr-15-1.fc26.x86_64.rpm
*
s bios-vendor returns coreboot
syslog:
01:49:52,515 WARNING kernel:[ 223.240750] efivars: get_next_variable:
status=8003
Hmm, this actually may be a problem. I'm not sure what
status=8003 is, but if accessing efivars does not work, efibootmgr
would not work, so can't
t even get grub.
- I tried the UEFI troubleshooting guide to no avail, although I was
unable to run efibootmgr directly while in legacy boot mode ("EFI
variables are not supported on this system") so in order to run
efibootmgr, i booted a separate Fedora 26 Live image which does boot
i
up and running is
> > greatly appreciated. It's a wonderful operating system and I'd love to
> > keep using it.
>
> Try booting recovery mode and recreating your UEFI boot entry with
> efibootmgr like
> https://groups.google.com/d/msg/qubes-users/3Z52efsCTg0/OI2Li
nstead of BIOS/Legacy-Boot, then be extra careful. At
least in my anecdotal case, I've run into some efibootmgr issues with Qubes 4
release, when I tried to swap out various Qubes installs on my UEFI system.
For some reason or another, efibootmgr failed when I tried to fix a EFI boot
setting in t
However, after I update dom0, Qubes refuse to reboot. The boot is done to
> Ubuntu. Even when I choose to boot Qubes in the BIOS, Ubuntu will boot.
>
> Result of efibootmgr command is:
> BootCurrent:
> Timeout: 1 seconds
> BootOrder: 0002,,0005,0001,0007
> Boot* ub
Thanks a lot guys! It works again and I learned something new...
The Qubes 4.0 installation changed the EFI boot entry. With the following
command I fixed it:
"efibootmgr -v -c -L Qubes -l /EFI/qubes/xen.efi -d /dev/nvme0n1p1"
(With hint from awokd and
https://github.com/QubesOS/qu
es" in any config file, though. Bernhard
If that's internal disk, you should be able to configure UEFI to use
/boot/efi/EFI/qubes. In fact, installer should do that for you... You
can do that either in UEFI setup (some vendors have include it
somewhere near boot order setting), or using e
the
files. e.g. /boot/efi/EFI/qubes{0,1}/, but when it updates (or you
reinstall one of them), they would both try to install to
/boot/efi/EFI/qubes/ again. And you'd have to manually change the path
each time with efibootmgr.
My other thought is to give each instance its own EFI partition
-o /boot/efi/EFI/fedora/grub.cfg
# efibootmgr -c -d /dev/sda -p 1 -L "Fedora-Grub" -l
"\EFI\fedora\grubx64.efi"
Amendment: Actually, you might have to install grub2-efi-modules as well
and run grub2-install. I had the prebuilt
/boot/efi/EFI/fedora/grubx64.efi working w
the " efibootmgr " commands mentioned in UEFI
troubleshooting, but I do not understand them, and I am afraid to f*ck
it up even worse. If my harddrive-boot partition is mounted on /BOOT
instead of /boot , how would the command read, please??
It seems it ignores your mountpoint, you pas
me
> a bootable device ?
You need to configure UEFI firmware to launch xen.efi. It should be done
automatically by the installer, but maybe your UEFI BIOS is buggy (which
is unfortunately quite common case...). First check if you can do this
from BIOS builtin setup. If not, try using efibootmgr
on
> file in /etc which doesn't exist on my install and other files that don't
> exist on my setup. Any help would be appreciated, thanks
In case of UEFI, boot entries are configured in UEFI BIOS. See
efibootmgr tool, or BIOS builtin setup.
- --
Best Regards,
Marek Marczykowski-Góre
not see Qubes
but when I run "efibootmgr -v" from a live Ubuntu USB I can see an entry for
Qubes so I am not sure why the firmware does not see it and would not allow me
to boot it.
I even tried to remove Windows and just leave Qubes but I dont think Qubes
wiped the boot pa
oning does not appear to recognize an existing EFI partition on
an "nvme disk" (1) as an EFI partition (error message "No valid bootloader
target device found..." (2)).
Installing anyway results in no Qubes boot option on reboot. (3)
Running efibootmgr -v from a live usb reports a
but is 0 bytes in length so not
very usefull.
Do you have any suggestion of what could be the problem? Or how this can be
located?
If I run qubes repair I can use efibootmgr and I can also use the efivars file
system so it doesn't look related to that.
When I tried to verify my boot media
irectory doesn't contain xen.efi (just the one with the
> version in it) and the xen.cfg file is created but is 0 bytes in length so
> not very usefull.
>
> Do you have any suggestion of what could be the problem? Or how this can be
> located?
>
> If I run qubes r
c, except for the
> last step I made a rEFInd menuentry instead of using efibootmgr. I booted my
> menuentry, and the loading bar gets to the end, then nothing happens. I am
> using a late 2014 Mac mini, and the menuentry I am using is this:
>
> menuentry {
> #This is what
, but don't want to install
> everything anew.
Reinstall/restore might be fastest. If you want to try to fix it, search
this mailing list for "efibootmgr" assuming you have UEFI boot. Sounds
like something got corrupted. Reinstall GRUB if not using UEFI.
--
You received this message
;
> > The installation goes well. At that time, I can reboot directly to Qubes.
> >
> > However, after I update dom0, Qubes refuse to reboot. The boot is done to
> > Ubuntu. Even when I choose to boot Qubes in the BIOS, Ubuntu will boot.
> >
> > Result o
However, after I update dom0, Qubes refuse to reboot. The boot is done to
> Ubuntu. Even when I choose to boot Qubes in the BIOS, Ubuntu will boot.
>
> Result of efibootmgr command is:
> BootCurrent:
> Timeout: 1 seconds
> BootOrder: 0002,,0005,0001,0007
> Boot* ub
into the system even with legacy boot.
>
> I have followed most of the advice on this page:
> https://www.qubes-os.org/doc/uefi-troubleshooting/#a1-2
> But to no avail.
>
> Indeed my xen.cfg is empty but when i try populating and then running
> efibootmgr I get a
:
https://www.qubes-os.org/doc/uefi-troubleshooting/#a1-2
But to no avail.
Indeed my xen.cfg is empty but when i try populating and then running
efibootmgr I get an error "EFI variables not supported on this system" since I
installed in legacy mode.
I would really love to upgrade t
3.2, try to set that first
in your boot order. If EFI mode, you might have to boot into Qubes
recovery mode (possibly from the 3.2 DVD), then repair the EFI boot entry.
The command will be something like:
sudo efibootmgr -c -L Qubes32 -d /dev/sda -p 1 -l \\EFI\\qubes\\xen.efi
Note the "/de
cy mode boot for 3.2,
> try to set that first in your boot order. If EFI mode, you might
> have to boot into Qubes recovery mode (possibly from the 3.2 DVD),
> then repair the EFI boot entry. The command will be something
> like:
>
> sudo efibootmgr -c -L Qubes32 -d /dev/sda -
the UEFI boot environment of Qubes 4.0? I tried
using the Qubes installer but there is no shell access to run
grub-install or efibootmgr. Can I do it from the Archlinux drive or a
Fedora boot media?
Any hints are appreciated.
Regards,
Stephan
--
You received this message because you
/boot/efi/EFI/qubes to /boot/efi/EFI/BOOT with all the accompanying
instructions did not work. I did notice that the xen-*efi file was 0 length,
so I also followed the instructions on adding the entries (with the correct
file versions of course), but the last instruction talks about running the
lly creating boot entry (using another live distro) in EFI
firmware as mentioned in #4 of
https://www.qubes-os.org/doc/uefi-troubleshooting/#installation-finished-but-qubes-boot-option-is-missing-and-xencfg-is-empty
> efibootmgr -v -c -u -L Qubes -l /EFI/qubes/xen.efi -d /dev/sda -p 1
> &
t/efi/EFI/fedora/grub.cfg
# efibootmgr -c -d /dev/sda -p 1 -L "Fedora-Grub" -l
"\EFI\fedora\grubx64.efi"
Amendment: Actually, you might have to install grub2-efi-modules as well
and run grub2-install. I had the prebuilt
/boot/efi/EFI/fedora/grubx64.efi working when grub2-efi
Success! Fixed! It was EFI problem and efibootmgr help to fix it (from
UEFI troubleshooting)
On 2020-02-19 20:22, evas...@firemail.cc wrote:
Hello,
After I changed some BIOS settings to boot from flash card on my Qubes
system. Qubes never boot again even though I changed all back.
Strange
cy with the graphics card, the
basics are working.
Unfortunately, after installing completes without errors, the system will not
boot. Now, I believe the problem has to do with UEFI boot from nvme drive.
I've tried to troubleshoot following
https://www.qubes-os.org/doc/uefi-troubleshooting/. Th
csb2S9Q
> https://groups.google.com/d/topic/qubes-users/kBKABl9-A3g/discussion
In legacy mode, Qubes does not boot from the USB media. It tries but it
immediately reboots my laptop.
I did not try: efibootmgr -v -c -u -L Qubes -l /EFI/qubes/xen.efi -d /dev/sda
-p 1
I used the last option string.
ith those for Windows but when I reboot and press F12
> to select the boot device I only see the Windows bootmanager, I do not see
> Qubes but when I run "efibootmgr -v" from a live Ubuntu USB I can see an
> entry for Qubes so I am not sure why the firmware does not see it and w
creen.
>
> Any advice?
Currently you can't boot Qubes OS from grub2-efi (this is mostly Xen
limitation). So, if you need grub menu, you need to switch to legacy
mode.
Alternatively, check if your UEFI do not support boot menu itself - some
does. Then you can use efibootmgr (or UEFI buil
n be
> located?
>
> If I run qubes repair I can use efibootmgr and I can also use the efivars
> file system so it doesn't look related to that.
>
> When I tried to verify my boot media this failed but from the other posts it
> looks to me as this is standard for boot media cre
m talented users found. ;)
> > How to replace dom0? Or restore boot files?I've got a pretty fresh
> > complete backup on external USB drive, but don't want to install
> > everything anew.
>
> Reinstall/restore might be fastest. If you want to try to fix it, search
> this
to
> > > Ubuntu. Even when I choose to boot Qubes in the BIOS, Ubuntu will boot.
> > >
> > > Result of efibootmgr command is:
> > > BootCurrent:
> > > Timeout: 1 seconds
> > > BootOrder: 0002,,0005,0001,0007
> > > Boot* ubuntu
is the only
"fixed" disk on both laptop and workstation, that would be an easier
scenario because in that case there's only a single EFI partition. Might
have to rerun efibootmgr on the device not used for install. Hardware
behaviour with multiple EFI partitions seems to be
re not sufficiently detailed for me to follow them.
>
> Any assistance to help me get my Qubes systems back up and running is greatly
> appreciated. It's a wonderful operating system and I'd love to keep using it.
Try booting recovery mode and recreating your UEFI boot entry with
is a pain. I did it for a while on one of my machines and
Windows kept breaking GRUB every major update. When you add the below
hard drive, you might have to regenerate your Qubes UEFI boot entry.
Search this list for efibootmgr if that happens.
Unplugging my Windows install hard drive
ery entry (last entry)
3) select continue (oprion 1)
4) enter your key
5) hit enter (to get a shell)
6) chroot /mnt/sysimage
7) fdisk -l to find your efi dev (we assume it is /dev/sda1)
8) use efibootmgrt to fix your efi.
efibootmgr -c -d /dev/sda -p 1 -l \\EFI\\qubes\\xen.efi -L qubes
9) reboot
on len
launch xen.efi. It should be done
automatically by the installer, but maybe your UEFI BIOS is buggy (which
is unfortunately quite common case...). First check if you can do this
from BIOS builtin setup. If not, try using efibootmgr. Some hints here:
https://www.qubes-os.org/doc/uefi-troubleshooting/
t; on the boot partition along with those for Windows but when I reboot and
> press F12 to select the boot device I only see the Windows bootmanager, I
> do not see Qubes but when I run "efibootmgr -v" from a live Ubuntu USB I
> can see an entry for Qubes so I am not sure why the
rsion in it) and the xen.cfg file is created but is 0 bytes in length so
> not very usefull.
>
> Do you have any suggestion of what could be the problem? Or how this can be
> located?
>
> If I run qubes repair I can use efibootmgr and I can also use the efivars
> file system
oot option isn't added
2) The efi\qubes directory doesn't contain xen.efi (just the one with the
version in it) and the xen.cfg file is created but is 0 bytes in length so not
very usefull.
Do you have any suggestion of what could be the problem? Or how this can be
located?
If I run qubes repai
grub2. I just did a reinstall with it set
> > to BIOS, which is working fine for now.
>
> In UEFI mode grub is not used at all, xen.efi is loaded directly.
> Example line to configure EFI boot manager would be (assuming /dev/sda
> being the disk with Qubes installed):
> efibootmgr
m. I'm not sure what
status=8003 is, but if accessing efivars does not work, efibootmgr
would not work, so can't add Qubes entry. Does `efibootmgr
- -v` show anything?
Other than that, I also can't see anything interesting.
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things
t; But it shouldn't disable installing UEFI entries, only allow to have
> encrypted /boot (since grub in coreboot can handle it).
>
> Some relevant log entries:
>
> anaconda.log:
> 01:50:16,997 INFO anaconda: bootloader XenEFI on EFI platform
> 01:50:17,067 INFO anaconda: dmide
The boot option isn't added
> 2) The efi\qubes directory doesn't contain xen.efi (just the one with the
> version in it) and the xen.cfg file is created but is 0 bytes in length so
> not very usefull.
>
> Do you have any suggestion of what could be the problem? Or how this can b
system" (one of the same
commands found in your link you mention in your post). After it boots into
Qubes rescue system, then pick option nr. 1, then press enter as suggested on
the screen to enter shell (it will likely ask for your password), and write
this command below in the shel
th it, see if it's stable, and then make a decision whether you
feel comfortable with it or not.
Also another warning, ff you plan to install Qubes 4 while retaining QUbes 3.2.
on the same machine through UEFI/EFI. You'll clear the EFI entry in the
motherboard boot settings. At least i did not have muc
1 - 100 of 106 matches
Mail list logo
