uefi - Boot-Repair, no shimx64, boot-info supplied - Ask Ubuntu

i trying install pidgin on ubuntu 16.04 following instructions found on website, lots of dependencies; when didn’t work, logged out , shut down pc night. morning, ubuntu wouldn’t boot. (so can’t recover website was...)

after running boot-repair pendrive (which oddly works when plug in both boot-repair pendrive , ubuntu liveusb, , choose 2nd @ bbs), choice of boots @ gnu grub. attempts run ubuntu option result in black screen @ top of times following:

/dev/sda2: clean, {some big number}/{some big number} files, {some big number}/{some big number} blocks  [938323] libvirt-guests.sh[1226]: running guests on default uri: no running guests. 

(numbers between square brackets vary.)

(i may have shut down pc while virtual machine running in virt-manager; can’t remember.)

the other gnu grub choices are:

advanced options ubuntu (after “recovery mode”, no help) efi/ubuntu/fwupx64 (goes gnu grub) efi/ubuntu/mokmanager (i have no idea how work this) 

boot-repair tells me can reboot through shimx64.efi, option not show @ grub. also, aptio bios setup (2012) has no option enable or disable secure boot, i’ve read needed shimx64.efi show.

boot-repair info

i’m unsure how proceed. should go deeper “recovery mode”? should try other options inside boot-repair?

could here me fix it?

it looks should working. observations , comments:

• your boot repair output indicates have both bios , efi versions of grub installed, seem using efi version, , bios version broken. isn't problem, confusing. indicates previous bios-mode installation or attempt repair problem bios-mode tools.
• the shimx64.efi binary more-or-less required boot ubuntu secure boot, shimx64.efi can used boot or without secure boot enabled. efi boot manager entry boot shimx64.efi show ubuntu in boot menu. (some people have 2 ubuntu entries, 1 of launches shimx64.efi , other of launches grubx64.efi directly.) when launched, shimx64.efi launches grubx64.efi, presents boot menu , boots kernel.
• the fwup64 entry see launches firmware-updating tool. useful if download firmware update computer/motherboard manufacturer , install on esp -- , if computer's efi supports protocols used fwup64, not (yet). in other words, can ignore option.
• the mokmanager entry enables manages machine owner keys (moks), used shim enable third-party binaries , kernels launch. entry unlikely helpful in current situation, can ignore it.

there's slim chance problem being caused secure boot, might try disabling it. so, you'll need enter firmware setup utility (by hitting esc, enter, or function key after power on computer -- details vary 1 system can't provide exact instructions). how disable secure boot once you've entered setup utility varies 1 system another. examples, see this page of mine.

it's more problem caused further along boot process -- clearly, kernel loading, else failing. may related video drivers -- system running except x (gui) display. there's rather massive question , answers here on askubuntu type of problem, maybe you'll find useful there. related virtualization in way, given last message see; or perhaps random critical file has been damaged or missing.

i'm sorry not have better answer -- luck answer helpful in preventing going on wild goose chase concerning fwup64, mokmanager, or shim.