12.01.2017 02:12, Carlos E. R. пишет:
Hi,
I have a small MSI Cubi N machine that I use as home server and multimedia server on my workroom, with Leap 42.1. I applied with yast a month worth of updated, which included a kernel, and rebooted.
It failed.
I got the MSI logo, then blank screen. I don't think it gets to grub.
If at the MSI logo I press "Del" I get the Bios configuration page. If I plug the installation USB, I can boot that one, theh choose "boot from hard disk", which works. The system is currently running.
The machine is UEFI.
It does not mean it cannot boot in legacy BIOS mode. Installation menu on UEFI does not offer "Boot from hard disk" as far as I remember, so it suggests you *do* boot in legacy BIOS. Do you have /sys/firmware/efi directory after boot? Does "efibootmgr -v" work?
How do I diagnose this?
You verify how your system is configured to boot.
I got some info:
Boot Info Script 0.75 [14 November 2016]
============================= Boot Info Summary: ===============================
=> No boot loader is installed in the MBR of /dev/sda. => libparted MBR boot code is installed in the MBR of /dev/sdb. => libparted MBR boot code is installed in the MBR of /dev/sdc.
sda1: __________________________________________________________________________
File system: vfat Boot sector type: FAT16 Boot sector info: No errors found in the Boot Parameter Block. Operating System: Boot files: /efi/boot/bootx64.efi /efi/boot/fallback.efi /efi/opensuse/MokManager.efi /efi/opensuse/grub.efi /efi/opensuse/grubx64.efi /efi/opensuse/shim.efi
I don't know if this is correct. No boot loader in MBR of sda? That's the boot disk.
How do you know? "Boot disk" is whatever BIOS is configured to boot from.
It is the only UEFI machine I have, so I can't compare.
It does not look like you boot in EFI mode.