[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273060
@Chirstopher,
I noticed that you removed the 'latest-bios-1.10' tag again - can you explain
why?
The Fujitsu support site lists 1.10 as the latest BIOS available for my model
LH532 (UMA) - Serial No. DQBAxx
There are some updates to the other model LH532/G22 and all the
accompanying docs
** Tags removed: latest-bios-1.10
** Tags added: bios-outdated-2.09
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273060
Title:
[Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware
Christopher, system is not bootable any longer, so I cannot run those commands
nor update BIOS if one was available.
In any case, BIOS being the latest, there's nothing to add to the report.
I shall set the report to 'Confirmed'. Let me know otherwise.
--
You received this bug notification
** Tags removed: bios-outdated-2.07
** Tags added: latest-bios-1.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273060
Title:
[Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware
Satish, 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
To summarise, there are at least two other related bug reports (which should
add motivation given the wider impact of the issue):
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1471380
--
You received this bug notification
This bug is high risk! It's effectively bricked a Dell Latitude E6540
:-(
My theory is that, somehow, the update caused a change to the firmware
NVRAM settings and boot entries for UEFI, and the Dell code can't handle
something unexpected. And after I've entered BIOS password, the firmware
code
@Chistopher, thanks, the problem is now that my A15 bios can't even
enter setup mode or boot anything, so I'm not sure how to try flash the
most recent A16 version from (released just a month ago)? Searched the
laptop's manual, and no indication of any jumpers to clear/reset NVRAM
:-(
I agree and
Jean-Pierre van Riel, the exact same thing happened to me. I was under the
impression that my motherboard gave out and was planning to take it to the
service centre.
However I did not update Ubuntu; I rarely boot into Ubuntu these days - have
been using Elementary. And I also have Windows 10
*** This bug is a duplicate of bug 1082418 ***
https://bugs.launchpad.net/bugs/1082418
Jean-Pierre van Riel, given you have an outdated BIOS, you would want to update
that first to see if this is resolved for your computer model. If you find an
issue on the latest BIOS, then it will help
@Christopher, my laptop model is LH532 (UMA) - the latest BIOS version is 1.10
and this is what the bug report has.
The one you mention (ver 2.07) is for the other model LH532/G22.
I am unable to restore the 'latest-bios-1.10' tag (laptop being bricked I'm
accessing this page from my mobile).
Please look at my post in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418/comments/74
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
More info...
I updated and now the kernel version is 3.15.0-6-generic and
efibootmgr's 0.7.0
Now when I run just efibootmgr, I get the following message
satish@LH532:~$ efibootmgr
show_boot_order(): No such file or directory
Looking at efibootmgr.c, it looks like the efi_get_variable() might
I just checked on 14.04 (kernel 3.13.0-031300-generic) with efibootmgr
version 0.6.1
The bug still exists; I created an boot loader entry and it wiped out
access to firmware. I was not able to boot to CD/DVD or USB to restore
it and had to open up to short the pins.
** Changed in: linux (Ubuntu)
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is
Satish for your information, utopic has a new upstream version of
efibootmgr included. It might be worth checking if that is fixing your
problem as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273060
Title:
[Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware
Devs,
Any chance this bug might get a little attention? It makes my pc practically
un-usable.
Everytime I run efibootmgr with the -c option to create a boot
entry, it erases all existing ones. Only the last entry added from
efibootmgr persists - even the device select entries like Boot from USB,
** Tags removed: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273060
Title:
[Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware
access
To manage notifications about
** Tags added: quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273060
Title:
[Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware
access
To manage notifications about this
Satish, thank you for providing the requested information. Just to
clarify, could you please provide a click-for-click on what you did when
you were installing it?
For example, you had a Windows 7/8 UEFI partition installed first, put
CD in, Install Ubuntu, Install Ubuntu alongside them, etc.
--
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
Satish, so to clarify, you personally with your hardware (not someone
else with different hardware on another report) experienced it from
Quantal through Trusty?
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of
Yes, that's correct. I just didn't report it earlier because I assumed
that any fix for the 1082418 bug would essentially fix mine too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273060
Title:
Did this issue also happen with prior releases, such as Saucy or did
this issue just start happening in Trusty?
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This issue was present in prior releases too. I faced it in Quantal and then
Saucy too. The original bug report is here -
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418
The reporter of that bug is no longer active to perform tests and since the bug
affects me too, I was trying to
27 matches
Mail list logo
