Bricked my laptop after BIOS update

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?

root@akashubuntu-Aspire-V3-571G:/home/akashubuntu# efibootmgr -v
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,0000,0004,0003,0001
Boot0000* Windows Boot Manager  HD(2,c8800,96000,580a97ae-421d-46e0-b74d-2d959c130884)File(\EFI\Microsoft\Boot\bootmgfw.efi)RC
Boot0001* HDD:  HD(2,c8800,96000,580a97ae-421d-46e0-b74d-2d959c130884)File(\EFI\ubuntu\grubx64.efi)RC
Boot0002* Windows Boot Manager  HD(2,c8800,96000,580a97ae-421d-46e0-b74d-2d959c130884)File(\EFI\opensuse\grubx64.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...a................                                                                                    
Boot0003* Fedora        ACPI(a0341d0,0)PCI(1f,2)03120a00000000000000HD(2,c8800,96000,580a97ae-421d-46e0-b74d-2d959c130884)File(\EFI\fedora\shim.efi)..
Boot0004* Fedora        ACPI(a0341d0,0)PCI(1f,2)03120a00000000000000HD(2,c8800,96000,580a97ae-421d-46e0-b74d-2d959c130884)File(\EFI\fedora\shim.efi)..
Boot0005* BRCM MBA Slot 0200 v15.0.11   BIOS(80,500,00)................a........ ..E............ .............................
Boot0006* WDC WD7500BPVT-22HXZT3                BIOS(2,500,00)................-.h.......h.A.h........................................
Boot0007* HL-DT-ST DVDRAM GT70N                 BIOS(3,500,00)................-.v.......v.A.v....#...................................

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.

On 2014-10-17 07:36, vish 99 wrote:

> 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?

Most of the time, simply because the application you want to run is not
in the path of the user that calls sudo. It is in the path of the user
(root, normally) that is used /after/ sudo succeeds.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

That’s hard to say. It might depend on your UEFI firmware.

On one of my two UEFI computers, the firmware is very aggressive in deleting boot entries – too aggressive, so that sometimes Windows is the only one left (mostly because Windows is very aggressive about putting its boot entry back if it disappears).

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.

Unlikely. Normally, opensuse install will remove entries containing the string or word “opensuse” (and then recreate them for the current install).