You could try to boot the kernel installed using:
https://www.supergrubdisk.org/super-grub2-disk/
On 1/30/21 11:28 AM, donoban wrote:
Hi,
On 1/30/21 8:43 AM, haa...@web.de wrote:
I am surprised by the sizes -- files seem small. Do the seem correct??
Are there files missing?? Could maybe someo
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 about /dev/sda
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 seconds
> BootOrder: ,0001
> Boot0001
Gesendet: Samstag, 30. Januar 2021 um 10:28 Uhr
Von: "donoban"
An: qubes-users@googlegroups.com
Betreff: Re: [qubes-users] HELP! after update dom0 "no bootable device found"
Hi,
On 1/30/21 8:43 AM, haa...@web.de wrote:
> I am surprised by the sizes -- files
Hi,
On 1/30/21 8:43 AM, haa...@web.de wrote:
> I am surprised by the sizes -- files seem small. Do the seem correct??
> Are there files missing?? Could maybe someone check these md5sums, please?
>
> 1ff66a646f443da650caca5a71d14dc9 initramfs-5.10.11-1.fc25.qubes.x86_64.img
> 0ed0b625599395686c
The main line is in the title. I did a dom0 upgrade that installed kernel-latest. After reboot I got the freaky message
"No bootable device found, press F1... F2 .. F5.." -- it does not really say where it comes from, but it sounds like a BIOS message.
I have no idea where to start, so I give
