kernel-packages team mailing list archive

[Satish <psatishchandra+oi@xxxxxxxxx>]

Here's what I did.

1. The laptop does not come with a OS pre-installed. So after opening the package, when I first switched it on, it prompted for a boot device. I instead restarted and entered the firmware (F2) and changed the Boot Order to look for CD/DVD first and then try the HDD.
2. I put in Ubuntu CD, restarted and installed.
3. On the partitioning options, I chose 'Something Else' and created around 7 partitions (GPT, obviously). Two 50GB partitions for Ubuntu and Mint (I planned to install Mint later), 10GB swap, two 100GB partitions for data (I usually install all s/w in one and put my user data in another) with the last partition taking the rest of space.
4. Ubuntu detected that my system supports EFI and prompted for separate /boot/EFI partition. I just choose Yes.
5. After installation, for a few weeks I did not try to get into firmware. Only when I put in the Mint CD, did I notice that I had no option to get into the firmware. Only Ubuntu's grub was loading. I then searched the web for problems and came across the bug 1082418. I subscribed myself.
6. Following some instructions there, I opened up the laptop and shorted a couple of pins to reset the NVRAM. This still did not let me into firmware but atleast the Boot Sequence menu was available (F12). I installed Mint OS using the CD and this too erased my firmware access including the Boot Sequence again.
7. Using the same shorting trick, I now used Fujitsu supplied FreeDOS USB image (that I burned to a USB device) to boot into FreeDOS and flashed the BIOS. This restored full access to firmware and I went in and changed the Boot Order again to try CD/DVD first.
8. Windows 8 Preview was out and I wanted to try it out. I burned a CD and installed Windows. This messed up my partitions (still working though) by creating a few more for Recovery and what not. Anyway, once inside Windows, I downloaded Fujitsu's BIOS Flash utlity to be able to flash my BIOS from Windows. 
8. Point to note is that installing Windows did not clear out my firmware access. It put an entry 'Windows Boot Loader' at the top of the boot order. Ubuntu was never able to do this - I guess the whole thing was failing when Ubuntu was trying to add its boot entry.

I upgraded to Ubuntu releases as they came out and everytime it wiped
out my firmware access. I installed Elementary OS as well replacing Mint
and this too exhibited the same behaviour.

I now have Windows 8.1 Preview but not for long (running out in a few
days) and I will not have an alternative to the shorting method then.
Although I did a couple of times, I honestly don't want to mess with
things by opening up the laptop.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1273060

Title:
  [Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware
  access

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  :~$ apt-cache policy grub-efi-amd64
  grub-efi-amd64:
    Installed: 2.00-22
    Candidate: 2.00-22

  EFI installation of Ubuntu clears out the boot entries in firmware leaving user with no option but boot Ubuntu. Pressing (F2) to enter BIOS Setup has no effect as does pressing (F12) for Boot Order.
  The only way to get back firmware access is to flash the bios using manufacturer provided utilities. Unfortunately Fujitsu doesn't provide a BIOS flash utility for Linux/Ubuntu. It is to be noted that installed Windows in EFI mode on the same system does not clear out firmware access but just adds the 'Windows Boot Loader' entry at the top of the boot sequence.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-5-generic 3.13.0-5.20 [modified: boot/vmlinuz-3.13.0-5-generic]
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  satish     1852 F.... pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jan 27 11:06:37 2014
  HibernationDevice: RESUME=UUID=c73dc7d0-4253-44fa-9589-d8c91c9cac13
  InstallationDate: Installed on 2014-01-26 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  MachineType: FUJITSU LIFEBOOK LH532
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic.efi.signed root=UUID=efd53305-1eac-42ba-b3f9-828b72cb5560 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-5-generic N/A
   linux-backports-modules-3.13.0-5-generic  N/A
   linux-firmware                            1.122
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2012
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.10
  dmi.board.name: FJNBB1E
  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:rnFJNBB1E:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK LH532
  dmi.sys.vendor: FUJITSU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273060/+subscriptions