Satish, thank you for your comment. So your hardware and problem may be
tracked, could you please file a new report with Ubuntu by executing the
following in a terminal while booted into a Ubuntu repository kernel (not a
mainline one) via:
ubuntu-bug linux
For more on this, please read the offi
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: satish 1976 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=c73dc7d0-4253-44fa-9589-d8c91c9cac13
InstallationDate: Instal
Christopher, as required, I installed latest build from Ubuntu daily-
live/current images and this wiped out my UEFI firmware access. This
confirms that the bug exists on the latest kernel too.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notifica
Christopher, I can do the test on the latest kernel but not right away.
Downloading nearly 1GB of that cdimage would burn out my volume cap and
I need it for work. I will give it a shot probably near the end of the
month (closer to my volume cap reset date).
--
You received this bug notification
viking777, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/curre
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082418
Title:
Ubuntu UEFI install locks out UEFI firmware (~bios) access
To manage noti
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: satish 1876 F pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=c73dc7d0-4253-44fa-9589-d8c91c9cac13
InstallationDate: Installed on 2013-03-23 (2
** Package changed: grub2 (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082418
Title:
Ubuntu UEFI install loc
Apologize for the delay..
The efivars error exists even when I have 'efibootmgr' running ok. There was an
update that locked out my firmware again. efibootmgr returns nothing (I guess
because the boot entry/order setting in NVRAM has been erased and is empty). I
created a new entry for refind an
[Expired for grub2 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: grub2 (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/1082418
T
You need to boot in efi mode to use efibootmgr. In other words, reset
your bios to factory defaults, and get it to boot from the install cd in
efi mode.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
grub-efi isn't installed; there's only grub-pc. No matter what I try,
efibootmgr refuses to give me any output.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082418
Title:
Ubuntu UEFI install locks
Can you run efibootmgr before trying to install grub-efi ( after getting
the system back to a working state ), and make sure that it works
correctly at that point, without this error in dmesg? If so, it looks
like there may be a bug in the kernel, or at least, a bug in your bios
that the kernel mi
Ok.
The dmesg output (searching for EFI) is attached. The following is something I
see in the dmesg output.
efivars: get_next_variable: status=8002
For some reason, the 'efibootmgr' command doesn't show any output. It
simply returns; I even tried running the Termi
Most likely what is happening is that the EFI boot variables are somehow
getting messed up, and your bios is buggy and goes off the deep end when
this happens. After installing grub-pc, check dmesg for any EFI related
errors, and run sudo efibootmgr and post the output please.
** Changed in: gru
Some more info in the hope it helps the developers to make sense of this
issue:-
I managed to restore the "Boot via CD/DVD" option by shorting the said
CL1 and CL2 pins. However this did not restore my BIOS/UEFI firmware
access. I was just able to use the 'Boot via CD/DVD' and 'Boot via USB
HDD' o
Yes, that has been my guess as well. I kept the battery but did not
switch the system on. Shall do it the next time I try it.
I looked for the CMOS battery too but I assume Fujitsu soldered it and hid it
away. Also the CL1 CL2 pins weren't under the RAM area in my laptop, they were
adjacent to i
Satish the only thing I might add to this is that in my experience, when
you do the 'shorting' of the cl1 cl2 pins the machine must have power
available, it is no good doing it with the battery removed it wont work,
in fact the machine has to be switched on. (see my post dated
"2012/11/21 18:38" on
I concur. This issue is pretty serious.
Unlike viking777, I used 'Something Else' option during partitioning to
create different partitions, keeping one for installing Mint later.
Little did I know that my Ubuntu install will lock me out of BIOS. Now I
can't get my laptop to boot from the Mint DVD
** No longer affects: ubiquity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082418
Title:
Ubuntu UEFI install locks out UEFI firmware (~bios) access
To manage notifications about this bug go to:
Fujitsu Lifebook AH552/SL - (x|K)Ubuntu 12.10 - the same shit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082418
Title:
Ubuntu UEFI install locks out UEFI firmware (~bios) access
To manage notif
The same thing happened with my new Lifebook AH552SL and Ubuntu 12.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082418
Title:
Ubuntu UEFI install locks out UEFI firmware (~bios) access
To man
Ah, thank you again YannUbuntu.
That is not the answer then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082418
Title:
Ubuntu UEFI install locks out UEFI firmware (~bios) access
To manage notif
These 4 files were created by Boot-Repair (see
http://ubuntuforums.org/showpost.php?p=12379441&postcount=637 ).
I don't think they cause the bug, but to be sure you can delete them, either
via command lines or via the Advanced option --> "Restore EFI backups" option
of Boot-Repair.
--
You rece
I am not at all familiar with Uefi workings, so the following comment is
neither a solution nor even a theory, simply a question for others that
are familiar with Uefi to consider.
I see that in my /boot/efi folder I have the following files:
ls -l /boot/efi/EFI/Microsoft/Boot/
total 480
-rwxr-xr
That is a shame morlock, it seemed like a much easier solution all
round.
Well done for finding it even if it doesn't work!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082418
Title:
Ubuntu UEFI
Oh my ... please forget the whole NVRAM backup idea for now. It doesn't
even work for me anymore. It worked *flawlessly* and *repeteadly*
yesterday night (I could just copy the binary dumps around and make
nothing work, only the boot menu and both menus). The difference
yesterday was that after I h
morlock, thank you very much for this work.
I have tried all three of your nvram dumps on my machine and none of
them make any difference to its behaviour. In other words f2 settings
menu and f12 boot choices continue to be available at all times even
when in running your 'nvram_fucked_up' state.
** Summary changed:
- Ubuntu Uefi install locks out bios access
+ Ubuntu UEFI install locks out UEFI firmware (~bios) access
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082418
Title:
Ubuntu UEFI
29 matches
Mail list logo
