10:25 a.m.
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...
help?
11:18 a.m.
New subject: F38 install fails on a Lenovo x120e - Failed to set new efi
boot traget
On Mon, 2023-07-17 at 11:25 -0400, Robert Moskowitz 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...
Did the old system use EFI or BIOS?
Have you tried booting a live USB stick of F38 on the hardware?
poc
12:09 p.m.
On 7/17/23 12:18, Patrick O'Callaghan wrote:
On Mon, 2023-07-17 at 11:25 -0400, Robert Moskowitz 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...
Did the old system use EFI or BIOS?
Have you tried booting a live USB stick of F38 on the hardware?
It was EFI.
Perhaps this is the system where I had EFI problems and had to hack at
the EFI. hmm...
But if so, the other 120e with F24 did not need hacking.
11:58 a.m.
New subject: F38 install fails on a Lenovo x120e - Failed to set new efi boot traget
On 17 Jul 2023, at 16:26, Robert Moskowitz
<rgm(a)htt-consult.com> wrote:
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...
Is it a 64bit system or 32bit? Fedora needs 64bit now.
Barry
12:12 p.m.
It has the AMD E-350 duo core CPU which I am pretty sure is x64.
On 7/17/23 12:58, Barry wrote:
> On 17 Jul 2023, at 16:26, Robert Moskowitz <rgm(a)htt-consult.com> wrote:
>
> 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...
Is it a 64bit system or 32bit? Fedora needs 64bit now.
Barry
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)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
12:17 p.m.
New subject: F38 install fails on a Lenovo x120e - Failed to set new efi boot traget
On Mon, Jul 17, 2023 at 11:25 AM Robert Moskowitz <rgm(a)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
12:53 p.m.
Well I am going to have to boot off a liveCD.
I have F37 handy. Will try that now and download the F38 one.
Oh I was using the Netinstal. And it had problems with my ethernet. It
worked when I had booted F22 to check things out before then install.
So I had to use the wiFi.
On 7/17/23 13:17, Jeffrey Walton wrote:
On Mon, Jul 17, 2023 at 11:25 AM Robert Moskowitz
<rgm(a)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(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)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
12:55 p.m.
I just recalled. There was a /boot/efi partition on the old F22 setup.
But booting up F37 live now.
On 7/17/23 13:17, Jeffrey Walton wrote:
On Mon, Jul 17, 2023 at 11:25 AM Robert Moskowitz
<rgm(a)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(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)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
1:03 p.m.
New subject: F38 install fails on a Lenovo x120e - Failed to set new efi boot traget
On Mon, Jul 17, 2023 at 1:56 PM Robert Moskowitz <rgm(a)htt-consult.com> wrote:
I just recalled. There was a /boot/efi partition on the old F22 setup.
But booting up F37 live now.
If you haven't done so, now would be a good time to update the
laptop's firmware. Get on the latest version.
And the kernel docs have some info on UEFI:
https://www.google.com/search?q=efi+support+site:kernel.org .
https://www.kernel.org/doc/html/v5.9/x86/x86_64/uefi.html looks
interesting.
Jeff
1:10 p.m.
Well....
that command gets:
WARNING: UEFI firmware can not be updated in legacy BIOS mode
Then I get a url for fwupd...
Oh, the ethernet is working. Seems it got unplugged from the switch.
Ooops.
Anything else I should try before looking into firmware ver on this
box? Like how to find that out without rebooting and going into system
settings...
On 7/17/23 13:17, Jeffrey Walton wrote:
On Mon, Jul 17, 2023 at 11:25 AM Robert Moskowitz
<rgm(a)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(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)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
1:31 p.m.
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
<rgm(a)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(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)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
2:05 p.m.
New subject: F38 install fails on a Lenovo x120e - Failed to set new efi boot traget
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 <rgm(a)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 <rgm(a)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(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)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(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)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
2:40 p.m.
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 <rgm(a)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
<rgm(a)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(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)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(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)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(a)lists.fedoraproject.org
To unsubscribe send an email tousers-leave(a)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.fedora...
Do not reply to spam, report it:https://pagure.io/fedora-infrastructure/new_issue
4:29 p.m.
New subject: works fine - Re: F38 install fails on a Lenovo x120e - Failed to set
new efi boot traget
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 <rgm(a)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
> <rgm(a)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(a)lists.fedoraproject.org
> > To unsubscribe send an email to users-leave(a)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(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)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(a)lists.fedoraproject.org
> To unsubscribe send an email tousers-leave(a)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.fedora...
> Do not reply to spam, report it:https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
users mailing list --users(a)lists.fedoraproject.org
To unsubscribe send an email tousers-leave(a)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.fedora...
Do not reply to spam, report it:https://pagure.io/fedora-infrastructure/new_issue
5:58 a.m.
New subject: works fine - Re: F38 install fails on a Lenovo x120e - Failed to set new efi boot traget
On 17 Jul 2023 at 17:29, Robert Moskowitz wrote:
Date sent: Mon, 17 Jul 2023 17:29:17 -0400
Subject: works fine - Re: F38 install fails on a Lenovo x120e - Failed to set
new efi boot traget
From: Robert Moskowitz <rgm(a)htt-consult.com>
To: Community support for Fedora users <users(a)lists.fedoraproject.org>,
Roger Heflin <rogerheflin(a)gmail.com>
Copies to: noloader(a)gmail.com
Send reply to: Community support for Fedora users <users(a)lists.fedoraproject.org>
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!
Just to note. Was able to upgrade my Lenovo R60 to Fedora 38 via
dnf upgrade. Didn't see any reference to it have UEFI in bios, but
the install did make a efi directory in /boot?? First time I ran it,
got a failed message since it said it needed an additional 3M of
space in /boot. clean up some things, and removed the rescue
image kernel. Then it went thru dnf upgrade download, and then
the reboot.
Even added memtest86+ version 6.20 to it.
Have a little script I use to download the latest files from site.
There is work being done to get an rpm to handle it but latest one
in repos is 5.31 and doesn't work. The 6.20one is suppose to work,
but is in testing.
Script is simple to download the binary files from memtest86 site,
and put them in /boot and then manually makes a 20_memtest file.
Needs to run grub2-mkconfig to have it added to grub menu.
#!/usr/bin/bash
clear
mkdir -p /tmp/memtest
cd /tmp/memtest || exit
f=$(wget -O - https://memtest.org/ 2>/dev/null | grep -m1 binaries.zip | sed -e
's/.*<a href="//' -e 's/".*//')
if [ -z "$f" ]
then
echo "Unable to get pathname for binaries.zip" >&2
exit 1
fi
wget -nc https://memtest.org/"$f"
echo "$f"
zip=$(echo "$f" | cut -f4 -d/)
unzip -u "$zip"
boot=$(find / -maxdepth 2 -iname loader | sed 's_/loader__')
if [ -z "$boot" ]
then
boot="/boot";
fi
echo $boot
cp memtest64.* "$boot" -p -v
ver=$(echo "$zip" | cut -b10-13);
{
printf "# \x21/bin/sh\nexec tail -n +3 \$0\n# This file provides an easy way to add
custom menu entries. Simply type
the\n";
printf "# menu entries you want to add after this comment. Be careful not to
change\n# the 'exec tail' line above.\n"
;
printf "menuentry 'Memtest Legacy' {\n echo 'Loading memtest $ver for
BIOS BOOT SYSTEM'\n linux
/memtest64.bin\n}" ;
printf "\nmenuentry 'Memtest UEFI' {\n echo 'Loading memtest $ver for
UEFI BOOT SYSTEM'\n linux
/memtest64.efi\n}\n"; } >/etc/grub.d/20_memtest86+
chmod 755 /etc/grub.d/20_memtest86+
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
<rgm(a)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
<rgm(a)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_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE
0D0B996E09E65D802A503
> f8ba2887-9411-5c36-9cee-88995bb39731 ←
>UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE
0D0B996E09E65D802A503&ARCH_X64
>
> There may be other ways to determine if EFI is available.
>
> Jeff
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)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.or
g
> Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)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.or
g
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)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(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)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
+------------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor (Retired)
mailto:mikes@guam.net
mailto:msetzerii@gmail.com
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+
3:07 p.m.
New subject: F38 install fails on a Lenovo x120e - Failed to set new efi boot traget
On 17 Jul 2023 at 11:25, Robert Moskowitz wrote:
Date sent: Mon, 17 Jul 2023 11:25:31 -0400
To: Community support for Fedora users
<users(a)lists.fedoraproject.org>
From: Robert Moskowitz <rgm(a)htt-consult.com>
Subject: F38 install fails on a Lenovo x120e - Failed to set
new efi boot
traget
Send reply to: Community support for Fedora users
<users(a)lists.fedoraproject.org>
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".
Couple of question.
1. Did you let it run the media test on boot device befor the boot.
Don't know why, but a number of times I've had media that
worked before, but then fail to do an install for various reason.
Doing the media test will generally find an error. Redoing the
media will generally resolve the issue, and it will pass test and
install. So, would start with that.
2. I've got Fedora 37 running on a Lenovo R60, which I believe is
even older. It does have 4G of Ram, but only sees the 3.xG since
being so old. Machine original only had 1G new. Would also
probable do a memtest, but don't think Fedora boot has memtest
included? Memtest 6.20 does run on it.
My machine used dnf upgrade to 37, so didn't do a fresh install
with Fedora 37. Think it was clean installed with 36, and then
upgraded to 37.
Pulled it out and its bios is 2008, so definitely older. Booted up
fine, and running dnf update. Thought I had upgraded it to 38, but
it is at 37.
Machine does have a 700G disk (Clover CN-M750M disk).
Did find video that shows UEFI setup of x120e with with windows
7.
https://www.youtube.com/watch?v=mi7vKqPkdMY
So looks like it has UEFI, but didn't see any reference to UEFI on
my R60? If the UEFI install doesn't work, perhaps you could set
bios to legacy only and see if it will install in legacy setup..
Running the dnf upgrade on my R60 to see if it will upgrade to 38?
First computer was a 1963 IBM 1130 with punch cards back in
1975. So started with old machines that still were working.. High
School..
Good Luck. Have to see if my R60 will do Fedora 38.
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...
help?
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)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
+------------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor (Retired)
mailto:mikes@guam.net
mailto:msetzerii@gmail.com
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+
3:28 p.m.
On 7/17/23 16:07, Michael D. Setzer II wrote:
First computer was a 1963 IBM 1130 with punch cards back in
1975. So started with old machines that still were working.. High
School..
I started with a teletype 55 baudot to a GE MarkV in '66. Best I can
figure out was our school (Euclid OH) was the first and I was the only
junior, rest were seniors. Frankston and Bellovin were taking the
subway to CUNY that year, or that is what they both told me some decades
ago.
I had access to the school system's 1401 my senior year.
Still having fun. Meanwhile the install seems to be installing away...
As to memory, my main system is an x140e. The specs say 8Gb, but with
modern memory I have 16Gb and am pretty sure I could boost to 32Gb, but
don't really need that much. Look for my post about this on the Lenovo
help forum. You may be able to find memory cards to boost your system.
318
days inactive
319
days old
16 comments
6 participants
participants (6)
-
Barry -
Jeffrey Walton -
Michael D. Setzer II -
Patrick O'Callaghan -
Robert Moskowitz -
Roger Heflin