Op 6-6-2013 19:26, Adam Williamson schreef:Booted F19TC1 rescue in EFI mode.On Thu, 2013-06-06 at 10:34 -0500, Chris Adams wrote:Once upon a time, John Reiser <jreiser@xxxxxxxxxxxx> said:As a diagnostic, please run "efibootmgr --verbose" and post the output. This will show what fedora thinks is the boot order and parameters for EFI booting.That probably won't work for the original poster; installing from PXE will result in a system that boots from BIOS, and you can't see the EFI info from a BIOS boot.He could run it from a live UEFI boot or something, though. AJ, try that - boot a live image in UEFI mode and run the command jreiser suggested. The output of efibootmgr --verbose is: BootCurrent: 0007 Timeout: 1 seconds BootOrder: 0000,0007,0008,0005,0003,0006,0004 Boot0000* Windows Boot Manager HD(2,96800,31800,06701451-3ec2-4b01-8dac-17f25a3c6bd4)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}.................... Boot0003* SanDisk SDSSDH2256G BIOS(2,0,00)AMBO Boot0004* IBA GE Slot 00C8 v1381 BIOS(6,0,00)AMBO Boot0005* TSSTcorp CDDVDW SH-S223C BIOS(3,0,00)AMBO Boot0006* hp v135w 0.00 BIOS(2,0,00)AMBO Boot0007* UEFI: TSSTcorp CDDVDW SH-S223C ACPI(a0341d0,0)PCI(1f,2)03120a000200ffff0000CD-ROM(1,8309,2fac)AMBO Boot0008* UEFI: TSSTcorp CDDVDW SH-S223C ACPI(a0341d0,0)PCI(1f,2)03120a000200ffff0000Vendor(ba7c46d1-9c5e-4fc8-943d-1a491f23fe01,c2770200000277c222001d0000000000001d0008000000000800450c1f130000ec0200000100000101004665646f72612031392d544331207838365f3634202020202020202020202020)AMBO Boot000A* SanDisk SDSSDH2256G BIOS(2,0,00)AMBO Koos. |
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
