On 03/28/2018 07:23 AM, Carlos E. R. wrote:
Carlos (or anyone really), what executable did this come from? (1) It looks not good, and (2) I'm having much the same problem as you currently and suspect a missing boot loader is the problem.
On 03/20/2018 07:21 PM, Carlos E. R. wrote:
============================= Boot Info Summary: ===============================
=> No boot loader is installed in the MBR of /dev/sda. => ISOhybrid (Syslinux 4.05 and higher) is installed in the MBR of /dev/sdb.
sda1: __________________________________________________________________________ This information is created by a script, "bootinfoscript", currently
On 2018-03-28 06:16, ken wrote: maintained by Andrei Borzenkov.
su - cd ~/bin wget \ "https://github.com/arvidjaar/bootinfoscript/raw/master/bootinfoscript" bootinfoscript
It generates RESULTS.txt with a lot of useful information about the boot system.
However, in my case the problem was not missing boot loader (MBR not used with EFI loader), but that the EFI code is not signed or the signature is broken and the machine refuses to boot it, or that the code crashes. The symptom is that it does not boot and a blank screen (maybe related to the machine video being HDMI). I had to disable secure boot in the machine.
Thanks, Carlos, That script looks great. I'll probably be putting it to further use... but later. As said, I'm having similar boot problems with the same version, but didn't want to hijack your thread. So I'll just start a new one. But before I do even that, I've got another problem to fix first... which I've already posted. Hopefully I'll be back to the boot issue soon. :P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org