I got the error again when the install got to that point.  I told it to ignore and continue installing.

I have a usable system.

I did notice on boot an option to edit the EFI firmware.  I selected that and got an error that cannot boot into the EFI editor.

But that is ok.  the system is working!

On 7/17/23 15:40, Robert Moskowitz wrote:
I was getting ready to try again.

I pulled the CD drive and tried to get into bios setup, but was not fast enough and it started booting F38!

It got as far as a things like

[Failed] Failed to start systemd-login.service - User Login Management.

then a bunch more and hung.

So I am going to do the install again, keep the drive partitions I set up and ignore the EFI warning and see how it goes...

On 7/17/23 15:05, Roger Heflin wrote:
Yes, some did have efi back then.  i have some fm2 mbs that did. There will be an option in the bios to enable efi if it does.  efi dates to early itanium systems in 2002.  it was so bad it took years to make it to x86 systems. very little was in the classic bios menu and most config was in a mess of a poorly documented command line.

On Mon, Jul 17, 2023, 4:02 PM Robert Moskowitz <r...@htt-consult.com> wrote:

    Bios ver is "current", ver 1.17 dated 11/7/2012!

    Did we have EFI back then?

    Oh, F37 live CD booted fine.

    On 7/17/23 13:17, Jeffrey Walton wrote:
    > On Mon, Jul 17, 2023 at 11:25 AM Robert Moskowitz
    <r...@htt-consult.com> wrote:
    >> this system had F22 on it.
    >>
    >> I just went through all the steps to blow away the old
    partitions and
    >> install F38.
    >>
    >> It tried for maybe an hour with the spindizzy on "Installing
    boot loader".
    >>
    >> If finally came back with a dialog box with an error of:
    >>
    >> The following error occurred while installing the boot
    loader.  The
    >> system will not be bootable.  Would you like to ignore this
    and continue
    >> with the installation?
    >>
    >> Failed to set new efi boot target.  This is most likely a
    kernel or
    >> firmware bug.
    >>
    >> No|Yes
    >>
    >> What should I do at this point.  It IS an old system that has
    had a
    >> number of ver of Fedora on it.  It was booting F22 just fine,
    it seemed
    >> but now it is all gone...
    > You can check if the system provides EFI variables using
    fwupdmgr. It
    > will look something like:
    >
    > $ sudo fwupdmgr get-devices 2>&1 | grep -i -E 'UEFI|BIOS'
    >    │   Summary:            UEFI ESRT device
    >    └─UEFI dbx:
    >          Summary:          UEFI revocation database
    >          Vendor:           UEFI:Linux Foundation
    >          GUIDs: c6682ade-b5ec-57c4-b687-676351208742 ←
    >
    UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503
    > f8ba2887-9411-5c36-9cee-88995bb39731 ←
    >
    
UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503&ARCH_X64
    >
    > There may be other ways to determine if EFI is available.
    >
    > Jeff
    > _______________________________________________
    > users mailing list -- users@lists.fedoraproject.org
    > To unsubscribe send an email to users-le...@lists.fedoraproject.org
    > Fedora Code of Conduct:
    https://docs.fedoraproject.org/en-US/project/code-of-conduct/
    > List Guidelines:
    https://fedoraproject.org/wiki/Mailing_list_guidelines
    > List Archives:
    https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
    > Do not reply to spam, report it:
    https://pagure.io/fedora-infrastructure/new_issue
    _______________________________________________
    users mailing list -- users@lists.fedoraproject.org
    To unsubscribe send an email to users-le...@lists.fedoraproject.org
    Fedora Code of Conduct:
    https://docs.fedoraproject.org/en-US/project/code-of-conduct/
    List Guidelines:
    https://fedoraproject.org/wiki/Mailing_list_guidelines
    List Archives:
    https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
    Do not reply to spam, report it:
    https://pagure.io/fedora-infrastructure/new_issue


_______________________________________________
users mailing list --users@lists.fedoraproject.org
To unsubscribe send an email tousers-le...@lists.fedoraproject.org
Fedora Code of 
Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
List 
Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report 
it:https://pagure.io/fedora-infrastructure/new_issue


_______________________________________________
users mailing list --users@lists.fedoraproject.org
To unsubscribe send an email tousers-le...@lists.fedoraproject.org
Fedora Code of 
Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
List 
Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report 
it:https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to