Clarifications- why I installed in boot-secure off mode and why I had set BIOS password
My system didn’t allow other boot-loaders to load except windows. May be my system was hard coded for booting with windows.
I knew that Boot-Repair of Ubuntu could solve such kind of problems and Boot-Repair asks secure-boot turned off in order to work properly. And to turn off secure boot I had to set BIOS password. (ps- I could only turn off secureboot after setting BIOS password)
But as ppa is blocked by university internet proxy settings, so I could not use secure-boot. So I ultimately used
Okay, you finally have provided the “efibootmgr” output. It does not look as if secure-boot is enabled in opensuse. Either that, or your system won’t list it because it is neither Windows nor fedora.
Again, check the content of “/boot/efi/EFI/opensuse”.
It doesn’t says ‘UEFI’ disabled. It says secure-boot disabled. P.S. I disabled secure-boot just now in order to let my system boot.
Disable is option for secure-boot. (See to the left of disabled)
Again, secure-boot is option for Boot mode. Boot mode can either be UEFI or Legacy (BIOS) (see to the left of UEFI)
That’s what I did first. It showed that it’s a typo. See output.
akashopensuse@linux-ull4:~> install-shim
If 'install-shim' is not a typo you can use command-not-found to lookup the package that contains it, like this:
cnf install-shim
akashopensuse@linux-ull4:~> cnf install-shim
install-shim: command not found
akashopensuse@linux-ull4:~> /usr/sbin/install-shim
bash: /usr/sbin/install-shim: No such file or directory
akashopensuse@linux-ull4:~> cd /usr/sbin/install-shim
bash: cd: /usr/sbin/install-shim: No such file or directory
Probably it is typo, it’s shim-install not install-shim.
But, again something happened don’t know what.
/usr/sbin/shim-install
which: no grub2-probe in (/usr/lib64/mpi/gcc/openmpi/bin:/home/akashopensuse/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/opt/cross/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin)
Now I’m thinking if openSUSE boot-loader is made default boot-loader. What will happen if openSUSE will call windows boot-loader. Will windows boot-loader call the openSUSE boot-loader again.
. Also I’m thinking of removing Fedora. So, how do I restore EFI to factory conditions. I would later upgrade to 13.3. I won’t format the partition of openSUSE.
In the MBR days fixmbr from bootrec.exe could be used used to reset MBR to factory conditions. Is there any utility to reset EFI to factory conditions.
to become root. With that “-” argument, the root shell should have “/usr/sbin” on its path. And then it should work (assuming that “/usr/sbin/grub2-probe” exists).
Or, if your firmware can allow you to boot opensuse directly, then you won’t need that at all.
Now I’m thinking if openSUSE boot-loader is made default boot-loader. What will happen if openSUSE will call windows boot-loader. Will windows boot-loader call the openSUSE boot-loader again.
It doesn’t actually work that way. When you make that change to Windows, it (windows) tells your UEFI firmware to call opensuse directly from the firmware. When you use the Windows entry in the grub2-efi boot menu, that starts up Windows the way it would otherwise have started.
However, it is best not to have that “bcdedit” setting if you don’t need it. Windows updates can sometimes be confused by it.
Also I’m thinking of removing Fedora. So, how do I restore EFI to factory conditions.
The “shim-install” should add the UEFI boot entry for opensuse-secureboot, and that will work even when secure-boot is disabled in BIOS.
You can remove the “Fedora” boot entry, with the command (as root)
# efibootmgr -b 3 -B
# efibootmgr -b 4 -B
This assumes that entries 3 and 4 are for Fedora. First run
# efibootmgr -v
to check those numbers.
In the MBR days fixmbr from bootrec.exe could be used used to reset MBR to factory conditions. Is there any utility to reset EFI to factory conditions.
There’s no equivalent, and no need for an equivalent with EFI.
What “fixmbr” did, was to replace the boot code in the MBR. For UEFI, the bootcode is in the firmware and in the operating system directories in the EFI partition.
> I’m not able to find install-shim
>
> Code:
> --------------------
> sudo ls -R / | grep install-shim
> ls: cannot open directory /run/user/1000/gvfs: Permission denied
> ls: cannot open directory /var/run/user/1000/gvfs: Permission denied
> --------------------
Don’t use sudo, forget it.
Instead, in the terminal, type “su -” (the dash is crucial) and enter
the root password when requested. Then you run all those maintenance
tasks that need being root.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
If you come from Ubuntu you need to understand sudo works different in openSUSE. sudo does not by default give you a complete root environment. So you should use su - (note the dash) to become root. Then you will have the full root environment and paths. You can also use the full path to files to run root commands using sudo. What is different is the paths
On 2014-10-16 07:06, arvidjaar wrote:
>
> robin_listas;2669579 Wrote:
>>
>>> sudo ls -R / | grep install-shim
>>> ls: cannot open directory /run/user/1000/gvfs: Permission denied
>> Don’t use sudo, forget it.
>>
>
> Huh? Now please explain how sudo differs from su in this case.
Not in the ls -R case in particular. The OP was using sudo for
everything, and some failed as expected.
Of course that not su nor sudo will make any difference regarding the
gvfs directories. We all know that.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Great to know. And yes I used to use ‘sudo’ everywhere. Half of the the time if worked, half the time the time it didn’t. And I was always perplexed why?
Just realized. Why isn’t ubuntu shown in these results - in fact I’m posting here by using ubuntu only. Also I installed and removed kubuntu very long ago. I’m sure kubuntu is also present in EFI as I didn’t remove it.
Is it possible that while updating ubuntu/opensuse might have detected root of kubuntu is not present so delete the entry of kubunu from EFI.