We can focus on the coreboot version that messed up the bios considered boot drive, but I think the more critical issue, at least now, (not that this is super critical to begin with) is that the scripts ability to reorder the boot drive doesn’t seem to work or stick at reboot.
I pulled the script yesterday using wget. Then ran it just to see if updating coreboot would fix it. It fixed a gummed up initramfs but did not fix the boot order.
I was wondering if there is just something I can run that would do that. I suppose I could just look at what the script is doing but want to be cautious as I’ve got my librem quite setup and don’t want to risk messing that up, again. Thanks for your help!
then throw the log on pastebin (eg) and link here. If cbmem gives an error, you may need to reboot and add the kernel parameter ‘iomem=relaxed’ to your grub kernel arguments
you’re the first to complain about this, so sounds like a corner case is being hit somewhere. The function is working for all the cases I tested, and for the vast majority of users, otherwise there’d be more complaints
Boot device is the 2.5 sata drive (Samsung 250gb SSD). There is however the NVM drive, and when I first got the laptop, PureOS was installed on it. I wanted to use the bigger drive, and let the NVM drive be the VM storage.
ok, looking at your bootorder file from the log, it’s showing:
which isn’t what you want. I just used the script to generate a bootorder file with the order that you want, which is:
and verified that the file output is correct. So I think the confusion comes from the fact that 1) you don’t have a NVMe drive, and 2) the m.2 SATA drive is your boot drive (the 250GB Samsung), not the 2.5" SATA (120GB Biwin SSD)