About vendor lock and UEFI boot on fedora

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Hello everyone, I wanted to raise an issue that continues, regarding how manufacturers implement the UEFI system on their computers, and how it affects users.

In particular, I mean as some companies like Acer, make their laptops recognize only the UEFI boot, if and only if the parent folder is called "Windows Boot Manager".

This brought me a lot of headaches, particularly because using the "legacy bios", the laptop had problems with power management (not turned off, restarted, suspended, etc). https://bugzilla.redhat.com/show_bug.cgi?id=1213216

Initially unaware of the situation, but much searching I found the solution. Now my question is: is that the user experience is expected in fedora?

Unfortunately, the distribution can not do much about it, unless you can document these situations.

In the last week, trying to enable ZSWAP in my system, I realized that it is not possible to update the grub after editing the file etc/default/grub with the command /boot/efi/EFI/Windows\ Boot\ Manager/grub.cfg (modifying the target route). I had to create a file in another location and then replace the existing one.

Under these circumstances, the GRUB2 automatic update work?

They will searching the web several cases, particularly with ACER and ASUS laptops. My focus is on this issue, as several of these laptops (Aspire E 11 "ES1-111M-C6NR) were donated to a high school with aspirations to use Linux (fedora) on those computers.

Cheers

--
Bastián Díaz
https://telegram.me/diazbastian
--
desktop mailing list
desktop@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/desktop




[Index of Archives]     [Fedora Users]     [Fedora KDE]     [Fedora Announce]     [Fedora Docs]     [Fedora Config]     [PAM]     [Red Hat Development]     [Red Hat 9]     [Gimp]     [Yosemite News]

  Powered by Linux