Comment 74 for bug 1082418

Revision history for this message
aimwin (aimausy) wrote : Re: [Fujitsu Lifebook AH532] Ubuntu UEFI install locks out UEFI firmware (~bios) access

I have Lifebook LH532 and for almost 2 years not a problems with EFI boot
(installed ubuntu(&derivertives multi boots) more than 20 times)
until I upgrade 750GB (MSDOS) with new empty 1TB (was formated to MBR-MsDos)
and installed ubuntu 14.04.1 as only OS in 1TB and let ubuntu did that automatically, (1st choice installation)
it made 1TB as GPT and did UEFI installation.

Ubuntu 14.04.1 hacked and blocked firmware Bios,
no more F2 Bios option and F12 boot menu.

Yes I confirm as this bug and
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273060
-------------------------
I have upgrade ubuntu 14.04.1 installation to 14.10
reboot and try to do what
david6 (andrew-dowden) wrote on 2015-04-13:
said above.
Press <Esc>
produce only to interupt grub boot menu to grub> (grub promt)
So it is not workaround for me at the moment.

david6 please explain details of what your procedures and the end results please.

I have not tried fresh install Ubuntu 14.10
===================

>>>>>> My Fix and workaround.<<<<<<<<<<<

In short process.

1. Short circuit CL1 and CL2 as posts above, to get F12 boot menu.
2. Boot with live Ubuntu then convert GPT 1TB to MBR 1TB (using gdisk)
3. Install Ubuntu on one of the partition of MBR 1TB, (I made 6 partitions).

Result = multi boots ubuntu no more F12 boot menu wrecking.
Now I can install Windows and other Ubuntu derivertives, no issue on usb nor DVD boot choices.

Conclusion >>> Don't allow your harddisk to be made to GPT before ubuntu installations.
 if you are not 100% that your BIOS is compatible with Ubuntu GPT-UEFI installation.<<<<,

By forcing your harddisk to be MBR or MSdos format, before Ubuntu installation.
That prevent UBUNTU to be installed in GPT-UEFI that can wreck your Bios.

(And do not allow Ubuntu to install in the first choice, by UBUNTU's ways,
you must select the last option, choose your own ways of installations.)
----------------
I have not flash Bios since mine LifeBook was bought in Thailand and those above links are UK models.
So I did not dare to flash Bios yet.

But I can install the same Ubuntu 14.04.1 many times without wrecking F12 boot menu any longer.

----------------for newbies to ubuntu

So It is the GPT of the harddisk that force Ubuntu to install as UEFI mode and wreck Fujitsu Bios.
It is the "worst bug" (from user point of view) I found on Ubuntu for my life.

Ubuntu GURUs must do somethings.
This give bad names to ubuntu.

The computer technician quote $100 to fix my Bios.
=============

Propose simple problems reductions or preventive solutions (for under 2TB Disk).

1. During Installation, there must be warning message about making harddisk into GPT partition type with
" very prominent LETTERING " that this GPT and UEFI installation could wreck the Bios of your computer.
(Many computer's Bios are not compatible with UBUNTU UEFI installation and result in blocking further use of Bios,
and with samples models Fujitsu and many others.)
"Proceed with your own risk "
or
"Choose to do the MBR and Bios installation option." then safe old days of installations are done.

2. The installation process check the troblesome models of computers
and just force Bios-MBR installations for those troblesome machines in the only Bios-MBR lists.
But perhaps it should have the option of EXPERT MODE that can override this forced Bios-MBR installation.

=========
Propose alternative solution.

Request to the UBUNTU and Grup Gurus to do the Smart Grup "Auto Boot Menu"
Regardless of UEFI successful installations or not.
Grup will install an auto detect boot media and creat options for user to boot from the choices
as those provided by the Bios.

So we don't have to fix the bugs immediatly but user can carry on their other installation choices.

But the Bios will be wrecked still. So the previous proposals should be in placed as well.
=========

Thanks every one who try to help our communities.
And I hope the Guru will fix this bug soon.