Description of problem: EFI install Fedora-19-Alpha-RC1-x86_64-DVD.iso after "livecd-iso-to-disk --efi" onto USB flash memory. Default graphical install onto GPT disk which has no partitions. The following was filed automatically by anaconda: anaconda 19.16-1 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1666, in add_efi_boot_target raise BootLoaderError("failed to set new efi boot target") File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1671, in install self.add_efi_boot_target() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1690, in write self.install() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 2246, in writeBootLoader storage.bootloader.write() File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 141, in doInstall writeBootLoader(storage, payload, instClass, ksdata) File "/usr/lib64/python2.7/threading.py", line 504, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 141, in run threading.Thread.run(self, *args, **kwargs) BootLoaderError: failed to set new efi boot target Version-Release number of selected component: anaconda-19.16-1 Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: BOOT_IMAGE=/syslinux/vmlinuz inst.stage2=hd:UUID=3D8D-23F0 quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.9.0-0.rc4.git0.1.fc19.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 19-Alpha Truncated backtrace: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 141, in run threading.Thread.run(self, *args, **kwargs) File "/usr/lib64/python2.7/threading.py", line 504, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 141, in doInstall writeBootLoader(storage, payload, instClass, ksdata) File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 2246, in writeBootLoader storage.bootloader.write() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1690, in write self.install() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1671, in install self.add_efi_boot_target() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1666, in add_efi_boot_target raise BootLoaderError("failed to set new efi boot target") BootLoaderError: failed to set new efi boot target
Created attachment 732934 [details] File: anaconda.log
Created attachment 732935 [details] File: backtrace
Created attachment 732936 [details] File: environ
Created attachment 732937 [details] File: ifcfg.log
Created attachment 732938 [details] File: lsblk_output
Created attachment 732939 [details] File: nmcli_dev_list
Created attachment 732940 [details] File: packaging.log
Created attachment 732941 [details] File: program.log
Created attachment 732942 [details] File: storage.log
Created attachment 732943 [details] File: syslog
Created attachment 732944 [details] File: anaconda-tb
Related: https://bugzilla.redhat.com/show_bug.cgi?id=949761#c5 which is what "efibootmgr --verbose" reported _after_ two attempts (TC5 then RC1.)
Description of problem: EFI install to ASUS P8Z68-V/GEN3 with BIOS 3402 (May 2012). Version-Release number of selected component: anaconda-19.17-1 Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: BOOT_IMAGE=/syslinux/vmlinuz inst.stage2=hd:UUID=3D8D-23F0 executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.9.0-0.rc4.git0.1.fc19.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 19-Alpha Truncated backtrace: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 141, in run threading.Thread.run(self, *args, **kwargs) File "/usr/lib64/python2.7/threading.py", line 504, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 141, in doInstall writeBootLoader(storage, payload, instClass, ksdata) File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 2246, in writeBootLoader storage.bootloader.write() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1690, in write self.install() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1671, in install self.add_efi_boot_target() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1666, in add_efi_boot_target raise BootLoaderError("failed to set new efi boot target") BootLoaderError: failed to set new efi boot target
Probably same underlying cause as bug 947142 "write to /sys/firmware/efi/vars/new_var results in ENOSPC"
Description of problem: Trying to test the RC2 fix for UEFI. Not sure if fix is broken or if system needs garbage collection Version-Release number of selected component: anaconda-19.17-1 Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora\x2019-Alpha\x20x86_64 inst.updates=http://dlehman.fedorapeople.org/updates/updates-950510.0.img executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.9.0-0.rc4.git0.1.fc19.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 19-Alpha Truncated backtrace: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 141, in run threading.Thread.run(self, *args, **kwargs) File "/usr/lib64/python2.7/threading.py", line 504, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 141, in doInstall writeBootLoader(storage, payload, instClass, ksdata) File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 2246, in writeBootLoader storage.bootloader.write() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1690, in write self.install() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1671, in install self.add_efi_boot_target() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1666, in add_efi_boot_target raise BootLoaderError("failed to set new efi boot target") BootLoaderError: failed to set new efi boot target
Yes, this will be either https://bugzilla.redhat.com/show_bug.cgi?id=947142 or https://bugzilla.redhat.com/show_bug.cgi?id=949721 .
Description of problem: Installed Win8 on a blanc HD. It occupied 50% of disc space. Left 50Gb to install Fedora. Installed with UEFI boot method. On the notification ' Installing bootloader' This error occures. Version-Release number of selected component: anaconda-19.18-1 Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora\x2019-Alpha-TC6\x20x86_64 nomodeset executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.9.0-0.rc6.git2.1.fc19.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 19-Alpha-TC6 Truncated backtrace: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 141, in run threading.Thread.run(self, *args, **kwargs) File "/usr/lib64/python2.7/threading.py", line 504, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 141, in doInstall writeBootLoader(storage, payload, instClass, ksdata) File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 2249, in writeBootLoader storage.bootloader.write() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1692, in write self.install() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1673, in install self.add_efi_boot_target() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1668, in add_efi_boot_target raise BootLoaderError("failed to set new efi boot target") BootLoaderError: failed to set new efi boot target
Description of problem: UEFI install of F19-Alpha-RC3-x86_64 onto bare metal ASUS P8Z68-V/GEN3 with BIOS version 3402 of May 2012. Harddrive previously had successful UEFI install from TC6 onto 160GB disk with GPT label. I used parted to remove all partitions, then rebooted into UEFI mode, and chose default partitioning of whole disk using Standard Partitions. Version-Release number of selected component: anaconda-19.19-1 Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: BOOT_IMAGE=/syslinux/vmlinuz inst.stage2=hd:UUID=3D8D-23F0 quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.9.0-0.rc6.git2.3.fc19.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 19-Alpha Truncated backtrace: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 141, in run threading.Thread.run(self, *args, **kwargs) File "/usr/lib64/python2.7/threading.py", line 504, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 141, in doInstall writeBootLoader(storage, payload, instClass, ksdata) File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 2249, in writeBootLoader storage.bootloader.write() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1692, in write self.install() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1673, in install self.add_efi_boot_target() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1668, in add_efi_boot_target raise BootLoaderError("failed to set new efi boot target") BootLoaderError: failed to set new efi boot target
Created attachment 736169 [details] /tmp/anaconda-tb-XXXXXX A second attempt at UEFI install using RC3 also failed in the same way. This time I saved files from /tmp.
Created attachment 736170 [details] program.log
Created attachment 736171 [details] syslog
Created attachment 736173 [details] anaconda.log
Description of problem: Installed in UEFI Version-Release number of selected component: anaconda-19.19-1 Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora\x2019-Alpha\x20x86_64 nomodeset executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.9.0-0.rc6.git2.3.fc19.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 19-Alpha Truncated backtrace: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 141, in run threading.Thread.run(self, *args, **kwargs) File "/usr/lib64/python2.7/threading.py", line 504, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 141, in doInstall writeBootLoader(storage, payload, instClass, ksdata) File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 2249, in writeBootLoader storage.bootloader.write() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1692, in write self.install() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1673, in install self.add_efi_boot_target() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1668, in add_efi_boot_target raise BootLoaderError("failed to set new efi boot target") BootLoaderError: failed to set new efi boot target
Description of problem: Error looks like 949786 but errors looked different so might be helpful data. Version-Release number of selected component: anaconda-19.19-1 Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: BOOT_IMAGE=/syslinux/vmlinuz inst.stage2=hd:UUID=E134-A56E quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.9.0-0.rc6.git2.3.fc19.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 19-Alpha Truncated backtrace: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 141, in run threading.Thread.run(self, *args, **kwargs) File "/usr/lib64/python2.7/threading.py", line 504, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 141, in doInstall writeBootLoader(storage, payload, instClass, ksdata) File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 2249, in writeBootLoader storage.bootloader.write() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1692, in write self.install() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1673, in install self.add_efi_boot_target() File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1668, in add_efi_boot_target raise BootLoaderError("failed to set new efi boot target") BootLoaderError: failed to set new efi boot target
Updating the ASUS laptop (K52F) to BIOS 218 has fixed the problem with RC3 for me.
John: so, you have an ASUS, Smooge has an ASUS, and a firmware update fixed it for Smooge... http://www.asus.com/Motherboards/P8Z68V/#support_Download_8 indicates that a firmware version 3603 is available for your board. Could you possibly update your firmware and see if that resolves the issue? Thanks.
I do recommend trying the firmware update, as it may alleviate the symptom, but in any case this is the same problem as 947142. *** This bug has been marked as a duplicate of bug 947142 ***
Discussed at 2013-04-17 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-04-17/f19alpha-blocker-review-8.2013-04-17-16.00.log.txt . To try and give a 10,000ft summary: what we have here now is not really a bug exactly, but a problem with trying to handle the behaviours of various different UEFI implementations. UEFI firmwares have a small amount of NVRAM storage space. This is used for writing EFI boot manager entries to. We believe all the remaining reports here and in 947142 are cases where this space is 'full' when anaconda comes to write an EFI boot manager entry for the installation. In recent kernels, including those used in F19 builds, this space is considered 'full' when it's at 50% capacity. This is to avoid the serious bug in Samsung's UEFI implementation where systems become bricked if the NVRAM storage becomes more than 50% full. We think that the remaining 'broken' cases are those where the NVRAM is more than 50% full, but it is difficult to trigger garbage collection. anaconda now tries to clean out the NVRAM storage before writing the EFI boot manager entry, but effectively all it can really do is request that the firmware clean that space - if the firmware does not do garbage collection, the space will still appear occupied. So we're really not in a situation where we can simply 'fix a bug', but more of a 'damned if you do, damned if you don't' situation where we have to choose between not being installable on some systems and bricking some systems. We can twiddle with the workaround by only applying it to Samsung machines, or providing a kernel parameter to bypass it, but we're not sure it makes sense to hold up a Fedora Alpha release to make those tweaks especially based on the limited data we have. So we decided that for now the appropriate course of action is to go ahead and release Alpha with the current code: it's technically correct, there aren't "bugs" in it exactly. The function of an Alpha is to get wider feedback on this kind of thing, so that's what we'll do. We'll try and see how widespread this issue is with Alpha testers and how much trouble those who run into have in resolving it, and then we can consider whether we need to twiddle with the behaviour for Beta and/or Final. Therefore, this bug is rejected as a blocker for Alpha.
(In reply to comment #26) > John: so, you have an ASUS, Smooge has an ASUS, and a firmware update fixed > it for Smooge... > > http://www.asus.com/Motherboards/P8Z68V/#support_Download_8 > > indicates that a firmware version 3603 is available for your board. Could > you possibly update your firmware and see if that resolves the issue? Thanks. I found the correct file (has "GEN3" in its name; and yes, the files are different), but I'm going to wait before updating. I'd like to see any reports that arise from the actual Alpha release. There are some technical issues, too. Updating the BIOS imposes a new data layout in nvram, which apparently is where UEFI keeps its persistent data. So updating BIOS will clear all UEFI data. How does the UEFI data get rebuilt? If the system also is using UEFI Windows Boot Manager, then how well does "Recover your system" work (boot from Windows Install DVD), particularly if you had forced an install of Windows onto a GPT disk? (By default, Vista and Windows 7 require MBR, and decline to install on GPT.) Besides, before updating BIOS I will "clear CMOS" with the present BIOS, and see if Fedora 19 will install on that.
Update BIOS to ver. 218 fixed this problem for me. Asus Zenbook Prime UX31A.
"Clear CMOS" did not help. Updating BIOS to P8Z68-V-GEN3-ASUS-3603.ROM (Oct/Nov 2012), supposedly the most recent available BIOS, did not help. New kernel BUGs while handling nvram is continued at bug 962243.