On Sat, Apr 09, 2016 at 01:15:58PM -0600, Chris Murphy wrote:
On Fri, Apr 8, 2016 at 9:51 PM, Andrei Borzenkov
wrote: 09.04.2016 00:16, Daniel Morris пишет:
On Fri, Apr 08, 2016 at 07:46:39PM +0300, Andrei Borzenkov wrote:
08.04.2016 19:23, Daniel Morris пишет:
But the net effect is the same.
Unfortunately you forgot to tell what happens when you boot.
It seems as though the step between EFI and grub2 is missing. Could anyone suggest where to look next?
Please show "efibootmgr -v" output and describe what happens when system boots.
chunk:~ # efibootmgr -v efibootmgr: EFI variables are not supported on this system.
You are booted in legacy BIOS mode.
What could be confusing things, is maybe he's booting from install or rescue media differently than the installed system? If the installed system's boot is broken, then he has to have some way to get around that and we don't know what that is. And we still don't know what *does* happen when the installed system fails to boot, just telling us it's broken is not helpful.
I wondered if the output of 'efibootmgr' might be misleading after booting from the tumbleweed DVD. But that also seems far too "far along" to explain why I can't get from BIOS to loading a kernel image.
There are some crazy firmwares out there that will default to CSM-BIOS mode boot from optical media. So the first thing is Daniel needs to tell us exactly how the boot fails from the *installed* system. And then he needs to make sure he's using a proper installation media for his rescue boot, made in the officially documented way. And then see what he gets for efibootmgr -v.
The system doesn't get to any stage of booting. The BIOS stops with a message along the lines of "No boot media found, insert a bootable image and press any key to continue" (sorry I don't have physical access to the machine for a couple of days, so I'm going from memory). Before going further, just to clarify, this is my main machine and has booted scores of times since making a clean install of tumbleweed on January 5th (to a fresh SSD). No other OS has been installed. I made no changes to the BIOS settings, the logs show it was using grub2-efi, I just simply applied many updates with zypper and powered off, oblivious to the fact that one of the bootloader writes failed. That's not to say the BIOS isn't doing its own thing, it did wierd things when I made the clean install, such as autoprobing every attached SATA drive and finding old MBR's on the fifth & sixth disks! I'm confident that I've ruled that out this time by disconnecting every SATA data cable except for the primary SSD! And then re-attaching the DVD drive cable to workaround by booting the image off the SSD. I couldn't think of a way to reduce the system further. I don't remember how I burned the DVD, probably from k3b, certainly using openSUSE-Tumbleweed-DVD-x86_64-Snapshot20160101-Media.iso, and I always check the md5sum. The machine is 64bit Intel. One other oddity I noticed was grub2-i386-pc is installed and wants to remove all other grub2 packages if I try to remove it. I was expecting grub2-x86_64-efi and grub2-i386-pc would be mutually exclusive. Daniel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org