On 1 February 2013 12:22, Namikaze Minato lloydsen...@gmail.com wrote:
I'll just go back to legacy boot for now.
If you have information on how to correct that, feel
free to tell me what I should do and I'll try. MY searches however did not
help.
I unsubscribed from the mailing list, if you
News from me again.
I tried a fresh install with secure boot from the DVD. That works well
i.e. I can boot on the livecd and install fedora but I encountered two
problems:
1) Computer won't boot automatically. I have to go each time in the
boot menu, choose to boot from EFI file (instead of the
On 18 January 2013 21:39, Adam Williamson awill...@redhat.com wrote:
Are you sure you tried a dd written stick?
Yes. But maybe my USB key failed me at that time...
Images written with liveusb-creator are not UEFI bootable, this is known.
Well, I didn't hear about that, where is that written
Images written with liveusb-creator are not UEFI bootable, this is
known.
Well, I didn't hear about that, where is that written (no offense, of
course)? At least not on the download page or tutorial on how to use
the iso
On Thu, 2013-01-24 at 07:00 -0500, Kamil Paral wrote:
Images written with liveusb-creator are not UEFI bootable, this is
known.
Well, I didn't hear about that, where is that written (no offense, of
course)? At least not on the download page or tutorial on how to use
the iso
On Wed, 2013-01-16 at 17:35 +0100, Namikaze Minato wrote:
Trying to boot Fedora 18 Live Desktop on an EFI machine HP
(Probook 4540s) regardless of SecureBoot status results in the
following warnings until starting the rescue shell:
It is working by disabling SecureBoot *and* enabling
-18-x86_64-Live-Desktop.is does not exist.
dracut-initqueue[265]: Warning: /dev/mapper/live-rw does not exist.
There is no Fedora-18-x86_64-Live-Desktop.is label while in
the rescue shell, and there is no /dev/sdb either.
I tried to boot from an USB drive created using either liveusb-creator
or dd
Trying to boot Fedora 18 Live Desktop on an EFI machine HP
(Probook 4540s) regardless of SecureBoot status results in the
following warnings until starting the rescue shell:
It is working by disabling SecureBoot *and* enabling legacy boot.
But the question still stands: Why doesn't it boot
