Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am posting here because I have boot issues with every distro I tried, and they all give a similar error, so I think that this is a hardware (BIOS) issue?
A while back, I removed Windows, and installed a flavor of linux (don't remember). I have had boot issues-- boot delays, blank screens, no-booting-at-all, hardware lockups, etc since. I have been distro hopping to see if it is the distro's fault or not. It isn't. I have tried about 15 distros and they all get some sort of error. I have tried installing with/without secureboot, and in legacy (csm) mode. I couldn't install linux in uefi mode for the longest time until I reset my BIOS. Now it works but with errors. I would just be using legacy mode all this time to avoid all these troubles, but a few things don't work right in csm mode (acpi is one of them).
For the real issue: please check the picture attatched. This has been happening ever since I updated Fedora recently ( I've been using Fedora for some time, but with a huge boot delay and cpu lockups). Because of the error in the picture, I keep getting a new boot entry at every boot. Eventually, my computer wouldn't boot (tried fixing grub... grub wouldn't even load). So I installed OpenSUSE Leap recently to see if it was just Fedora since things update more often in Fedora-land. I deleted the 20+ Fedora entries via efibootmgr. Then I installed OpenSUSE. I still get the error from the picture, but at least now I don't have a long boot delay and cpu lockups like in Fedora. So I am happy that OpenSUSE works with this boot-entry issue. I came here for help to see if anyone knew what could be done before OpenSUSE doesn't boot anymore (from too many entries?) like Fedora did earlier.
FYI: I installed Fedora (from earlier) in UEFI mode with secureboot disabled. I currently only have OpenSUSE installed with secureboot enabled.
Has anyone had this issue? Is it because my MBR keeps looking for Windows even though it isn't there (one of those crappy dependent computers)? Is this an indication of a hardware issue? Can anyone help me fix this? Because I like OpenSUSE... it works. Thanks!
elias@opensuse:~> sudo dmidecode -t bios
root's password:
# dmidecode 2.12
# SMBIOS entry point at 0xb9898b98
SMBIOS 2.8 present.
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: TOSHIBA
Version: 5.10
Release Date: 08/10/2015
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 1024 kB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 5.10
Firmware Revision: 5.10
Handle 0x0019, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 2
en|US|iso8859-1
fr|FR|iso8859-1
Currently Installed Language: en|US|iso8859-1
How would that solve anything ?. I don't think the OP is worried about a delay of less than a second.
@Ererer, how did you remove Win ? - did you remove the directory from the EFI partition ?. Let's see what is in that partition (just a ls from Suse will do).
how did you remove Win ? - did you remove the directory from the EFI partition ?
Since that was quite some time ago... I do remember that I kept the efi partition, but that gave me errors as to "error reading from sector efx0 (or whatever is was) on hd1". So my computer was still looking for Windows after it was removed. This caused a big boot delay and sometimes non-boot of the distros I remember. Eventually I just wiped everything to try and fix it, but that was when I couldn't boot with uefi mode anymore.
I have to add this for reference: eventually I got tired of using the buggy csm mode (I had to use it just to boot and use my computer) so I wiped everything by installing Windows again (the tech preview for 10). I then "reset" (and updated) my BIOS from Windows. Then I removed Windows, completely wiped everything, and installed a distro. Now I have been able to boot with uefi mode enabled, but with errors, lockups, and non-boots here and there. At least I don't get the "error reading from sector efx0 (or whatever is was) on hd1" anymore...
Code:
This is from YAST:
Device: /dev/sda1
Size: 156.00 MiB
Encrypted: No
Device Path: pci-0000:00:13.0-ata-1.0-part1
Device ID 1: ata-TOSHIBA_MQ01ABF050_25BYCG4KT-part1
Device ID 2: scsi-0ATA_TOSHIBA_MQ01ABF0_25BYCG4KT-part1
Device ID 3: scsi-1ATA_TOSHIBA_MQ01ABF050_25BYCG4KT-part1
Device ID 4: scsi-35000039614383daa-part1
Device ID 5: scsi-SATA_TOSHIBA_MQ01ABF0_25BYCG4KT-part1
Device ID 6: scsi-SATA_TOSHIBA_MQ01ABF_25BYCG4KT-part1
Device ID 7: wwn-0x5000039614383daa-part1
FS ID: 0x103 EFI boot
File System:
File System: FAT
Mount Point: /boot/efi
Sorry I couldn't reply sooner... went on a tech-free vacation.
The error is gone now, and everything boots well. efibootmgr is normal; entries aren't added anymore for no reason! How I did it:
-Deleted duplicate entries in efibootmgr (except current one)
-Set boot order (efibootmgr -o 000C, OO16)
-Updated grub
Now everything works great. From me setting the boot order must have reset something. Also, I noticed that uefi: built in efi shell boots before opensuse (as seen below). That might have been the issue this whole time?
FYI: I don't get cpu lockups (boot delay) with opensuse, as I have with ome other distros. I will just assume that it is a kernel issue and be happy ;-) So... I'm sticking with Opensuse. I don't want to touch anything else. I'm pretty sure it's my favorite anyways ;-D
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
System BootOrder not Found
