[Fujitsu LIFEBOOK LH532] UEFI firmware becomes locked after installing Ubuntu in UEFI mode

[aimwin]

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418/comments/74

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CurrentDesktop: Unity
Date: Mon May 4 16:57:39 2015
InstallationDate: Installed on 2010-01-01 (1949 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: linux-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: rut 1480 F.... pulseaudio
                      rut 7079 F.... pulseaudio
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=d4bb392e-90ed-41a3-9d30-fa457fefb25b
InstallationDate: Installed on 2010-01-01 (1949 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: FUJITSU LIFEBOOK LH532
Package: linux (not installed)
ProcFB:
 0 inteldrmfb
 1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed root=UUID=e8258103-326b-4708-b64f-6306d0eb0a01 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-30-generic N/A
 linux-backports-modules-3.16.0-30-generic N/A
 linux-firmware 1.127.11
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: trusty
Uname: Linux 3.16.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 05/24/2012
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.10
dmi.board.name: FJNBB1F
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.10:bd05/24/2012:svnFUJITSU:pnLIFEBOOKLH532:pvr:rvnFUJITSU:rnFJNBB1F:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.name: LIFEBOOK LH532
dmi.sys.vendor: FUJITSU
---
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: rut 2207 F.... pulseaudio
DistroRelease: Ubuntu 15.04
HibernationDevice: RESUME=UUID=8fd2670c-4060-4d14-8f27-b9f806fe2ce7
InstallationDate: Installed on 2015-05-06 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: FUJITSU LIFEBOOK LH532
Package: linux (not installed)
ProcFB:
 0 inteldrmfb
 1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic.efi.signed root=UUID=3129a485-81a2-48ef-be95-ef9c9a57be3e ro quiet splash
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-15-generic N/A
 linux-backports-modules-3.19.0-15-generic N/A
 linux-firmware 1.143
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: vivid
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 3.19.0-15-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 05/24/2012
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.10
dmi.board.name: FJNBB1F
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.10:bd05/24/2012:svnFUJITSU:pnLIFEBOOKLH532:pvr:rvnFUJITSU:rnFJNBB1F:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.name: LIFEBOOK LH532
dmi.sys.vendor: FUJITSU

[penalvch (penalvch)]

aimwin, please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1451387

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

Dear Christopher.
I could redo the GPT-UEFI installation of Ubuntu 14.04.2
as it did wreck the F12 boot menu the second time.
I have now short circuit Cl1 and Cl2 twice now.

But I will do it only when you instruct me to do so.
I have to go out now be back in 4 - hours or so.

[aimwin (aimausy)]

http://support.ts.fujitsu.com/Download/ShowFiles.asp is for the following 2 series
LIFEBOOK LH532 (UMA) serial no. DQBAxxxxx
LIFEBOOK LH532/G22 serial no. YLKFxxxxx
UMA has latest updated version 1.1
G22 has latest 2.06

mine was bought in Thailand and the support site is
http://www.fujitsu-pc-asia.com/driversupport/selectioninterface/selection.html#
which has no bios update at all.

and my serial no. start with 57544B-xxxxxxxx.

On Wednesday, at the moment is a long holiday, I will contact fujitsu Thailand and see if they could help with the latest bios.
--------------------------------------------
for today at this moment.
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
Version 1.10
05/24/2012
--------------------------
I will look forward to get new updated bios installed.
And I will follow your instructions.
Thanks

[penalvch (penalvch)]

aimwin, to see if this is addressed via Ubuntu (versus BIOS bug), could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

[aimwin (aimausy)]

Christopher,
I had a long chat with Fujitsu Technician who fix somany LH532 in Thailand, which sold with no OS and Ubuntu destroy Bios.
Unfortunately the Warranty has expired and there for they don't need to support them any longer.
They delete the Bios files for the reason they don't want to have anything to do with that problems any longer.
 And warn that even in Thailand they sold a few models.
The Bios is for preinstall Widows OS will be different than Bios version with no OS,
even though they have the "same version no."/

If you have the wrong version burn into the Bios Chip, you will have a dead main board,
and they did have the dead ones before they learn that.

With those problems, Fujitsu decide to remove Bios download from the public websites,
at least for Asia-Pacific region, and I could not find them for the US and Canada also.
And we are left in Cold.

The technician has opinion that it was Ubuntu that Block the use of F2 and F12 functions.
So who ever wrote those parts of the Ubuntu installaion routine, should revise what they have done.
You cannot blame Fujitsu, these robust notebook, did not break and UBUNTU hack into their Bios and stuff it up.

He also warn that Fujitsu will not honour any warranty if it found their Bios is tampered with.
And they stop selling the non OS notebook, only preinstalled window 8 with GPT partitions only.
And If we change that to MBR and installed other OS, Fujitsu Technician said that will also void the warranty.

It means If I bought new Fujitsu ( I am about to do that) we will be risking void the warranty,
and the Fujitsu Technicians confirm, they are not supplied with Bios for new models at all.
(The main factory don't want them to mess up the mainboard again while under Warranty.)
So they could not help us fix the Bios problems any longer.

He also confirmed that by removing CMOS batteries for LH 532 .
I will reset only the date, not the Bios settings.
And only the CL1 AND CL2 short circuit is the only way to get the F12 BACK.

Now I hope those Kernel or grup or iNSTALLATION team GURUs will try to fgure out.
How to unblock the work that they hack into Fujitsu Bios or their UEFI manipulation.

=============

I will reformat MBR 1TB and install 15.04 as you instructed.
I will later do GPT 1TB, it may be 2 days now before I could finish all these testiong, since holiday is over in Thailand today.

Thanks.

[aimwin (aimausy)]

Christopher
I use ubuntu 15.04 Daily build
1. After installing on MBR-1TB works fine and still intact my fixed F12 Boot Menu
2. Use Gpart to convert the hdd to GPT partition type, empty though.
3. After installing on GPT-UEFI 1TB, Ubuntu loaded fine,
    >>>> BUT F12 Boot Menu disappear again and F2 is still missing as before <<<<

So not yet fix.
What to do next. I am still in the disaster mode, no Bios F2 nor F12 Boot Menu

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[aimwin (aimausy)]

apport information

[penalvch (penalvch)]

aimwin, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results.

[aimwin (aimausy)]

Christopher
Please confirm that,
I just use the current installed Ubuntu 15.04 (with current Wrecked Bios that cannot access both F2 Bios Setup nor F12 boot menu)
and just use these .deb to update Kernel using ubuntu software center,
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc2-vivid/
linux-headers-4.1.0-040100rc2-generic_4.1.0-040100rc2.201505032335_amd64.deb

Thank you

[aimwin (aimausy)]

Christopher
1st question
So what we hope, so call bug fixed is " after installation of the upstream Kernel and reboot",
>>>the F2 and F12 will be available to user immediately,<<<<<

2nd question.
Do you know which software is responsible for UEFI installation part?
I suspect if the problems of fastboot was turned on or Bios hacked or whatever to effect the F2 and F12 boot menu fuction,
we should try that installation software.

Sorry I don't have the knowledge of The kernel UEFI, if The access of the Bios is part of the Kernel.?
But I saw grub was installed in the "Bios" EEPROM or some kind of memory on board for UEFI boot soft ware.

Since I remove Hard Disk and found Grub menu instead of the Bios.

And the F2 and F12 are not there any longer.

So please help identify the software that modify the UEFI-Grub as well. the issue may lie there.
I will help test those new versions of these software and see if it will wreck the bios.

Thank You

[penalvch (penalvch)]

aimwinm before testing the latest mainline kernel (now 4.1-rc2), you would need to perform the WORKAROUND of shorting the CMOS so that F2 and F12 are back.

The expectation is when they are back, booting either the mainline kernel or default Ubuntu kernel does not cause the disappearance of F2/F12 (i.e. BIOS bug).

If so, then this may still be pursued on the linux side of things for a code WORKAROUND, while such a BIOS bug is addressed by the vendor.

[aimwin (aimausy)]

Christopher
Sorry for need more clarification.

1. Which version of usb boot Ubuntu distribution I should use as base kernel, before update mainline kernel?
Currently I have 15.04 dailybuid, and 14.04.2 LTS. (on mobile so can't download more new distribution at the moment)
Or if you want particular base version, please send the link.

2. The usb boot ubuntu is Read Only, how do I make new mainline kernel to be install on to the usb boot ubuntu.
I did try to install .deb but it has error and said not enough space also some error saying read only directory.
So I recreated the usb 15.04 dailybuild to test again.

Thanks

[aimwin (aimausy)]

ubuntu@ubuntu:~$ ls
Desktop Documents Downloads Music Pictures Public Templates Videos
ubuntu@ubuntu:~$ cd Downloads
ubuntu@ubuntu:~/Downloads$ ls
linux-headers-4.1.0-040100rc2-generic_4.1.0-040100rc2.201505032335_amd64.deb
linux-image-4.1.0-040100rc2-generic_4.1.0-040100rc2.201505032335_amd64.deb
ubuntu@ubuntu:~/Downloads$ sudo dpkg -i *.deb
Selecting previously unselected package linux-headers-4.1.0-040100rc2-generic.
(Reading database ... 177841 files and directories currently installed.)
Preparing to unpack linux-headers-4.1.0-040100rc2-generic_4.1.0-040100rc2.201505032335_amd64.deb ...
Unpacking linux-headers-4.1.0-040100rc2-generic (4.1.0-040100rc2.201505032335) ...
Selecting previously unselected package linux-image-4.1.0-040100rc2-generic.
Preparing to unpack linux-image-4.1.0-040100rc2-generic_4.1.0-040100rc2.201505032335_amd64.deb ...
Done.
Unpacking linux-image-4.1.0-040100rc2-generic (4.1.0-040100rc2.201505032335) ...
dpkg: dependency problems prevent configuration of linux-headers-4.1.0-040100rc2-generic:
 linux-headers-4.1.0-040100rc2-generic depends on linux-headers-4.1.0-040100rc2; however:
  Package linux-headers-4.1.0-040100rc2 is not installed.

dpkg: error processing package linux-headers-4.1.0-040100rc2-generic (--install):
 dependency problems - leaving unconfigured
Setting up linux-image-4.1.0-040100rc2-generic (4.1.0-040100rc2.201505032335) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
The link /initrd.img is a dangling linkto /boot/initrd.img-3.19.0-15-generic
The link /vmlinuz is a dangling linkto /boot/vmlinuz-3.19.0-15-generic
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.1.0-040100rc2-generic /boot/vmlinuz-4.1.0-040100rc2-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.1.0-040100rc2-generic /boot/vmlinuz-4.1.0-040100rc2-generic
update-initramfs: Generating /boot/initrd.img-4.1.0-040100rc2-generic
cryptsetup: WARNING: failed to detect canonical device of overlay
cryptsetup: WARNING: could not determine root device from /etc/fstab
ln: failed to create symbolic link ‘/root/lib/systemd/system/cdrom.mount’: No such file or directory
run-parts: executing /etc/kernel/postinst.d/pm-utils 4.1.0-040100rc2-generic /boot/vmlinuz-4.1.0-040100rc2-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.1.0-040100rc2-generic /boot/vmlinuz-4.1.0-040100rc2-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.1.0-040100rc2-generic /boot/vmlinuz-4.1.0-040100rc2-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.1.0-040100rc2-generic /boot/vmlinuz-4.1.0-040100rc2-generic
Errors were encountered while processing:
 linux-headers-4.1.0-040100rc2-generic
ubuntu@ubuntu:~/Downloads$

[aimwin (aimausy)]

Christopher
The above error using Ubuntu 15.04 dailybuild ISO from the link you gave in earlier post.
I may do the wrong procedure or I have to choose earlier mainline kernel or what should I do?

[aimwin (aimausy)]

I create 15.04 release desktop (not daily built)
and copy
linux-image-4.1.0-040100rc3-generic_4.1.0-040100rc3.201505102036_amd64.deb
linux-headers-4.1.0-040100rc3-generic_4.1.0-040100rc3.201505102036_amd64.deb
and execute the following command according to
https://wiki.ubuntu.com/Kernel/MainlineBuilds?action=show&redirect=KernelMainlineBuilds

ubuntu@ubuntu:~$ sudo dpkg -i *.deb
Selecting previously unselected package linux-headers-4.1.0-040100rc3-generic.
(Reading database ... 177841 files and directories currently installed.)
Preparing to unpack linux-headers-4.1.0-040100rc3-generic_4.1.0-040100rc3.201505102036_amd64.deb ...
Unpacking linux-headers-4.1.0-040100rc3-generic (4.1.0-040100rc3.201505102036) ...
Selecting previously unselected package linux-image-4.1.0-040100rc3-generic.
Preparing to unpack linux-image-4.1.0-040100rc3-generic_4.1.0-040100rc3.201505102036_amd64.deb ...
Done.
Unpacking linux-image-4.1.0-040100rc3-generic (4.1.0-040100rc3.201505102036) ...
dpkg: dependency problems prevent configuration of linux-headers-4.1.0-040100rc3-generic:
 linux-headers-4.1.0-040100rc3-generic depends on linux-headers-4.1.0-040100rc3; however:
  Package linux-headers-4.1.0-040100rc3 is not installed.

dpkg: error processing package linux-headers-4.1.0-040100rc3-generic (--install):
 dependency problems - leaving unconfigured
Setting up linux-image-4.1.0-040100rc3-generic (4.1.0-040100rc3.201505102036) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
The link /initrd.img is a dangling linkto /boot/initrd.img-3.19.0-15-generic
The link /vmlinuz is a dangling linkto /boot/vmlinuz-3.19.0-15-generic
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.1.0-040100rc3-generic /boot/vmlinuz-4.1.0-040100rc3-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.1.0-040100rc3-generic /boot/vmlinuz-4.1.0-040100rc3-generic
update-initramfs: Generating /boot/initrd.img-4.1.0-040100rc3-generic
cryptsetup: WARNING: failed to detect canonical device of overlay
cryptsetup: WARNING: could not determine root device from /etc/fstab
ln: failed to create symbolic link ‘/root/lib/systemd/system/cdrom.mount’: No such file or directory
run-parts: executing /etc/kernel/postinst.d/pm-utils 4.1.0-040100rc3-generic /boot/vmlinuz-4.1.0-040100rc3-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.1.0-040100rc3-generic /boot/vmlinuz-4.1.0-040100rc3-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.1.0-040100rc3-generic /boot/vmlinuz-4.1.0-040100rc3-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.1.0-040100rc3-generic /boot/vmlinuz-4.1.0-040100rc3-generic
Errors were encountered while processing:
 linux-headers-4.1.0-040100rc3-generic
ubuntu@ubuntu:~$

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Abdul Rehman (abdulrehman3)]

I have fujitsu lifebook ah532 of serial YLKVxxxxx,
want to install ubuntu 15.04 without messing anything,
I have access to Boot menu and Bios,
Currently Running Windows 10 Pro,
Hard disk partitions are GPT based.
Bios version 1.09

Hardware specs
Intel Core-i7 3612qm
4 GB DDR3 RAM
Intel HD 4000m

[aimwin (aimausy)]

As far as I know from Fujitsu staffs in Thailand,
Fujitsu is no longer support UBUNTU on the note books.
And they have erase all the files involved and
said they cannot support the out side warranty products.

Your notebook model has problems too.
May be if it will lock out, like others? WARNING????
But some one find a way to fix it but not that easy.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418
http://ubuntuforums.org/showthread.php?t=2086602&page=3&p=12371918#post12371918

Your AH532 is different version of the notebook.
It has bios for download.
So it has better chance to re flash bios
http://support.ts.fujitsu.com/productselect.asp?ParentsNavIDs=109754^109756&IDNR=&lng=EN
http://support.ts.fujitsu.com/Download/Index.asp

My LH532 serial no. has no bios download so I got stuck with no F2 Bios setup only F2 to boot menu still.

[Abdul Rehman (abdulrehman3)]

aimwin thank you, But I have Installed ubuntu 14.04.3 LTS, shorted CL1 and CL2 several times after installation now F12 is not working again,
But I have a solution in mind, I have installed rEFInd boot manager in my efi partition, I will install hiren's boot cd in usb with grub loader to flash my bios, I will share my experience with that. Your problem is different than mine, but it would be helpful for others.
I have already managed to boot live ubuntu usb without F12 boot menu, just added menu entries in grub.

[aimwin (aimausy)]

Thanks Abdul,
Hope you find another way to work around or solve the problems.

[Abdul Rehman (abdulrehman3)]

My workaround, no need to short CL1 and CL2:

1. Install Ubuntu in a normal way, ( I installed UEFI based Ubuntu, in GPT partition table hdd, didn't try MBR)

2. After installation restart your computer and boot to newly installed ubuntu

3. Download fujitsu flash bios from fujitsu website (I used Admin pack bios v1.09 for fujitsu AH532) and extract it to any fat32 or ntfs based partition or usb

4. http://www.rodsbooks.com/refind/ install rEFInd boot manager

5. Uncomment line "scanfor internal,external,optical,manual" search for this line and just remove '#' from /EFI/refind/refind.conf

6. Install and Run Boot-Repair with recommended option

7. Restart your system

8. Now your menu must be rEFInd boot manager if not then copy it from /EFI/refind/ to /EFI/BOOT/ and rename refind_x64.efi
to bootx64.efi

9. When you are at rEFind boot manager Insert Windows Installation DVD, I used windows 7 home basic that came with fujitsu

10. Press escape several times to refresh rEFInd, after that it will show cd-rom icon select that

11. After loading windows installation, select language then Select "repair your computer", wait for searching of preinstalled OSes then select first option click next and then select command prompt

12. In command prompt give path to your bios flash executable

You are done

If after restart only grub> basic is showing
follow these steps

i. grub> set root=(hdX,gptY) <enter>
ii. grub> linux /vmlinuz set root=/dev/sdaY <enter>
iii. grub> initrd /initrd.img <enter>
iv. grub> boot <enter>

replace X with your harddisk number
replace Y with your newly installed ubuntu partition
once you are in ubuntu
v. goto /EFI/Boot/ just delete bootx64.efi and copy refind_x64.efi from /EFI/refind/ and rename refind_x64.efi to bootx64.efi
this situation will only occur if you skip step 8.

Every time you update your grub or if it is re installed automatically by software updater you have to follow step 9 to step 11 to
re flash your bios.

I only have ubuntu in my system
I think, BIOS flash would be easy if you have dual-boot

[Abdul Rehman (abdulrehman3)]

aimwin

BIOS Admin Pack - LIFEBOOK LH532/G22

   File: FTS_BIOSAdminPackLIFEBOOKLH532G22_110_1074082.zip
   Version: 1.10
   Date: 24/05/2012
   Size: 7.45 MB

I have found bios with same version and date mentioned in your post.

http://support.ts.fujitsu.com/download/Showdescription.asp?SoftwareGUID=9E1761D4-4B55-4394-A21E-0F850DC5CD39

[penalvch (penalvch)]

aimwin, as per http://support.ts.fujitsu.com/Download/ShowFiles.asp an update to your computer's buggy and outdated BIOS is available (2.07). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything?

If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible, and the information above is provided, then please mark this report Status Confirmed. Otherwise, please mark this as Invalid.

Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Gaurav Dhiman (gauravd-chd)]

Even I am facing something similar. I have Fujitsu laptop (Model: LH532). It had Windows OS. After installing Ubuntu 18.04.1 from USB drive, on restart, laptop just shows "ubuntu" options in boot menu (not showing original BIOS, some new screen). Original BIOS screen does not appear. On selecting "ubuntu" and hitting enter key, nothing happens, so I am stuck with no options to start laptop. Below are the steps that I took.

1. Created bootable USB stick with https://rufus.akeo.ie/ (as recommended on Ubuntu site).
2. Rebooted the laptop.
3. Entered BIOS to change boot order so that USB is checked before HDD. Saved BIOS settings and restarted the laptop.
4. On re-start, options to try or install ubuntu were shown. Selected "try ..." option.
5. System started with Ubuntu (from USB).
6. Selected "Install Ubuntu" application icon when system started.
7. Went through normal question shown in ubuntu installation wizard.
8 Selected option to customize partitions, as I wanted to remove windows and partition it into two - one for / and another for /home.
9. Deleted the partition on which Windows was installed (C:\) and divided that into two partitions. One to install root (/) filesystem and another to install /home.
10. Ubnutu installation started, but after some time got an error "Installer crashed" as Grub could not be installed.
11. Tried to close the installation window, but nothing happened.
12. Restarted the system and again booted from USB.
13. This time I selected "Install ubuntu" option without booting ubuntu from USB in trial mode.
14. Answered installation questions.
15. This selected default option (showing reinstall Ubuntu 18.04.1) -- It was already showing that 18.04.1 is installed in the partition that I selected in earlier install (that failed).
16. Installation completed without any error. System asked to restart to start using Ubnutu installation.
17. Restarted the system.
18. On restart, I am shown a new screen (not the original BIOS or Boot options). Refer video https://www.youtube.com/watch?v=4ZkhsKc29Zg. This new screen (BIOS kind of screen) have two tabs - "Boot Menu" and "Application Menu". Under Boot Menu tab, only option available is "ubuntu" which is by default selected. On hitting enter, it tries to do something, but within second it comes back to same screen.

Problem: I am stuck with this new BIOS kind of screen with "ubuntu" as only option and that option does not boot system. I have no option to start the system or enter the original BIOS (which is not even visible anymore). Its kind of very strange that machine's BIOS got updated on installing Ubnutu.

[Gaurav Dhiman (gauravd-chd)]

This saved my life. Followed the instructions in below link to reset the BIOS and things worked fine thereafter to load Ubuntu
https://ubuntuforums.org/showthread.php?t=2257720

[melki (matawak)]

Is it here specifically for ubuntu only?

[Tim Schumacher (timschumi)]

I tracked this down to a bunch of edge-cases in Fujitsu's UEFI implementation, the Linux kernel, and efibootmgr.

The method of restoring access by doing a CMOS-reset (shorting the CL1_CL2 test point) and flashing the BIOS [1] was already known, but I also created a tool [2] that is supposed to restore all relevant settings from within a running Linux installation. Please do make note of the list of supported configurations and of the disclaimer.

A proper kernel-side fix is pending, but it will take some time to land in mainline Linux, linux-stable and the Ubuntu kernel tree respectively.

[1] https://support.ts.fujitsu.com/
[2] https://github.com/timschumi/ah532-biostools/