On Mon, 27 May 2019 10:00:02 -0600
Chris Murphy <lists(a)colorremedies.com> wrote:
That you get GRUB from installation media tells me your computer is
presenting itself as having UEFI firmware, because on computers with
BIOS firmware the installation media will use isolinux as the
bootloader, not GRUB. If the firmware is UEFI, GPT partitioning is
required (same as Windows) by the installer. It's been this way since
forever, at least Fedora 18.
Yes, the firmware is UEFI. But, the hard drives have been in use with
older hardware that wasn't. My understanding is that it is difficult
and chancy to convert from legacy partitions to GPT partitioning. Is
that false?
I thought that I had done a direct install for Fedora 21. It was the
last time that the BFO option worked for direct install from the net
instead of using media. It worked great at that point, but has been
non-responsive for several versions of Fedora since, or I would be
using it still. But that was a long time ago, so I could be wrong. I
have been just replicating the existing Fedora, and then enabling
rawhide to upgrade. I suppose I could do that again, but I like a
fresh install every so often to get rid of cruft.
Most UEFI firmware today have a "legacy" option or
"uefi
enable/disable" option in firmware setup, that will cause a faux-BIOS
to be presented instead of UEFI. These days I'm not sure why you'd
want to use that, unless you have specific known UEFI firmware bugs
that aren't going to be fixed by the manufacturer and also don't have
work arounds in either GRUB or the kernel. So I don't really
understand why this system has an MBR partitioning scheme in the first
place (there are older hardware in the Windows 7 era that were UEFI
but shipped with the compatibility support module enabled to present
BIOS).
See above. The firmware must have that because when I first used this
MB it allowed me to re-use the old drives with MBR from the failed MB.
Anyway, you need to be looking in firmware setup for this. Probably.
I
have seen some computers with in-firmware boot manager that shows a
USB boot option with a UEFI prefix suggesting they will only boot in
UEFI mode from USB if you choose that option; and still another option
for the same USB device but without a UEFI prefix (or with a legacy
prefix) and that enables the CSM for that boot - it's not a persistent
setting. It's kindof a sneaky user interface convention.
I'll look at this. I suspect it will be present and will provide a
workaround. At some point I'll have to bite the bullet and switch.
I'll probably do it when I purchase a new hard drive. I'm using cd-rom
in a dvd drive now, but if I have to I can switch to USB.
Off topic:
Also, FYI, your mail server configuration asks other mail servers to
consider your forwarded emails as suspicious, so gmail users likely
don't see your emails at all. I found your post in spam. I don't know
for sure the proper way to fix it, but a discussion just happened on
devel@ about it. I'm inclined to think this is a Fedora mail server
misconfiguration and the poster's mail server's dmarc header should be
stripped and replaced with its own (i.e. verify the posted email is
valid per dmarc/dkim, then strip that header; and resign the message
for the list), but ya whatever.
Authentication-Results:
mx.google.com;
arc=fail (body hash mismatch);
spf=pass (
google.com: domain of
test-bounces(a)lists.fedoraproject.org designates 209.132.181.2 as
permitted sender) smtp.mailfrom=test-bounces(a)lists.fedoraproject.org;
dmarc=fail (p=REJECT sp=REJECT dis=QUARANTINE)
header.from=zoho.com
I just use a free mail provider,
zoho.com. I don't set the
parameters. I saw in an email message on one of the Fedora lists that
zoho.com had been compromised, and was considered untrusworthy. That
is probably why it is marked as such. Maybe I should switch to using
my ISP. I used to use a paid email provider, but they suffered an
intrusion that put them offline briefly, and I have been leery of
continuing with them.
Thanks for your help.