On 12/31/2013 07:18 PM, Chris Murphy wrote:
On Dec 31, 2013, at 4:39 PM, Robert Moskowitz <rgm@xxxxxxxxxxxxxxx> wrote:
On 12/31/2013 05:00 PM, bugzilla@xxxxxxxxxx wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1006304
In additional info, include computer model and firmware revision. And then
attach your program.log, anaconda-tb, and syslog.
How can I find out my firmware revision without rebooting into bios setup? Seems there is a command somewhere that shows this…
No, this is something that I'd expect only the firmware will show you somewhere in its setup menu.
Also include as attachments the current results of:
efibootmgr -v > efibootmgr.txt
ls /sys/firmware/efi/efivars/ > efivars.txt
I am currently running f20 i386 on this system (my Lenovo x120e). My f17 x86_64 drive got hosed and won't boot. So how am I suppose to get these outputs?
Boot any x86_64 Fedora media in EFI mode (not CSM-BIOS mode - this is a setting in your firmware, sometimes irritatingly called "disable UEFI" when the CSM is being used). If it's not a livecd, like netinst or dvd, you can ctrl-alt-f2 to get to a shell, and issue those commands. And hardwire ethernet typically works from all media out of the box without configuration so you can either fpaste them (save the URLs!) or you can scp them to another computer or stick them on a USB stick.
I am downloading the f20 x86_64 live iso right now; and it looks like a
liveDVD, not liveCD by its size. I will run all of this tomorrow (My
new years Holiday was some 3 months ago :) ).
I wouldn't try to reproduce until you get more information from kernel
maintainers on how to get the information they need.
Hope we can get this straightened out in the next week +. I would like to have my new SSD drive working in time for the IEEE 802 meeting Jan 19th. I am looking forward to more battery time.
I have no idea how to help because I don't know why the kernel and firmware aren't getting along well enough to write the necessary boot information to NVRAM. After you collect all of this information and post it, I'd check the manufacturer web site and see if they have newer firmware that what you currently have, and give that a shot.
At this point I'm mainly trying to poke kernel devs into getting us more information when there are these kinds of NVRAM modification failures. Right now we really don't get much info it seems.
Chris Murphy
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
