quban
February 16, 2018, 11:05am
7
hey @max4 the qubes 3.2 not booting after initial install issue is not due to BIOS, it’s because the qubes installer didn’t install a boot loader. That’s what these posts are about:
Recently received my librem. I notice the same issue.
I used the same steps above except with:
GRUB_CMDLINE_XEN_DEFAULT=“console=none dom0_mem=2048M,max:2048M”
Therefore have static mem as recommended here:
https://wiki.xen.org/wiki/Xen_Project_Best_Practices
Also booting OK. . .
It seems that the Librems are shipped with coreboot with a SeaBIOS payload. Unfortunately, the Qubes OS installer doesn’t play too nicely with this configuration and installs properly but does not boot. On my Librem 13v2, I get
SeaBIOS (version rel-1.10.0-51-g7759d3a)
Booting from Hard Disk...
_
This is apparently a known issue: https://github.com/QubesOS/qubes-issues/issues/2553 . It looks like it’s been fixed for Qubes 4.0 (by simply disabling coreboot detection), but for now we’re stuck wi…
I had some issues booting my Librem13v2 q3.2 backups when restored to q4.0rc3, but I think that might have been due to either qubes 4 shortcuts working differently or the run mode of the vm (pv vs hvm) Building coreboot from source (official script) - #73 by Kyle_Rankin