1

I have an Asus UX32LN with the Haswell chipset and American Megatrends UEFI. Is it safe for me to use/install Ubuntu 17.10 ?

I have it installed already and it seems to work fine, but I'm worried about my EFI BIOS becoming corrupted. How do I know if it's corrupted and can I continue to use 17.10 safely on this laptop?

Nader Nooryani
  • 291
  • if it was a problem then it would already be to late. If it is running then there is no problem. As far as I know, the issue only affects Lenovo computers. The problem is with their EFI not Ubuntu per se. – ravery Dec 29 '17 at 12:41
  • One main issue with the bug you refer to is that (if you're affected) you are then no longer able to boot from a USB device (like an external CD or HDD). If you still can, then there should be no problem. See also https://askubuntu.com/q/984043/504066 and https://askubuntu.com/q/981878/504066. The first one also includes a solution. – PerlDuck Dec 29 '17 at 12:41
  • @ravery Affected computers are mainly Lenovos but also some (few) others, like Acer, Toshiba, Dell, Mediacom. No mention of Asus, though. – PerlDuck Dec 29 '17 at 12:47
  • @ravery I am able to install Ubuntu from a live-usb plus I tried toggling Secure Boot on/off with and saving, the change survives booting. So that would mean I have nothing to worry about? – Nader Nooryani Dec 29 '17 at 12:55
  • @NaderNooryani indeed. Plus your system itself is not on the affected systems. – Rinzwind Dec 29 '17 at 13:20

1 Answers1

2

Regardless of the bug ASUS is not on the affected list of systems. Besides all Lenovo's it also affects: 

Acer Aspire E5-771G
Acer Aspire ES1-111M-C1LE
Acer TravelMate B113
Toshiba Satellite S55T-B5233
Toshiba Satellite L50-B-1R7
Toshiba Satellite S50-B-13G
Dell Inspiron 15-3531
Mediacom Smartbook 14 Ultra M-SB14UC
Acer Aspire E3-111-C0UM

So you are fine.

For users using one of these systems: all direct downloads that have this bug have been revoked so you can not download the broken version anymore. If you have an old download download 17.10 again to make sure you deleted the bugged version.

Or skip 17.10 and stick with 17.04. There is not a lot in 17.10 that is that different over 17.04 anyways.

For people already affected see this notice in the bug report.

Rinzwind
  • 299,756