Laptop: Acer E1-471 | BIOS: InsydeH20 v1.20 (pure legacy)

Successfully boot? Yes, no issue.
LVM and Full Disk Encryption? No.

Did you successfully boot into Solus? yes
Are you using LVM? yes
Are you using Full Disk Encryption? (If so, answer to #2 is yes as well) yes

great work! 🙂

Thanks all for your testing. I'll be doing a sync of grub2 and thunderbird (thanks @kyrios for the update) to stable shortly and marking this as resolved 🙂

    • [deleted]

    • Post #21

    Harvey Thanks for pointing it out!

      the weird thing about gettng this update last week is I haven't had my daily freezes, seizes, and multiple reboots since then. Not a coincidence.
      I have long had the opnion that my I/O, mobo, and old phenom were too easily taxed and obviously not in concert...and also suspected kernel issues with my apparatus, ergo hardware and software together. I have no kernel taint (there's a cool command to see this).
      I realize this was a grub fix applied to bios and kernel, but it's cleared up the crashes so far.
      Anyway, thank you all the same JoshStrobl for the update.

        davidjharder We use a CVE check tool that looks for potentially unpatched CVEs (though it is imperfect). Providing nopatch files means "ignore the CVE with this file name" and is typically used when there either is no patch, or in the case of grub and most other packages when we're using a git source / remote that has a HEAD^ that is at or ahead of when the CVE patches landed. Basically our way of telling the tool "we're smarter than you."