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@xxxxxxxxxxxxxxx>
To: Community support for Fedora users <users@xxxxxxxxxxxxxxxxxxxxxxx>,
Roger Heflin <rogerheflin@xxxxxxxxx>
Copies to: noloader@xxxxxxxxx
Send reply to: Community support for Fedora users <users@xxxxxxxxxxxxxxxxxxxxxxx>
>
> 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@xxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxxxxxx
> > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> > 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@xxxxxxxxxxxxxxxxxxxxxx
> g
> > Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> 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@xxxxxxxxxxxxxxxxxxxxxx
> g
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
>
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> 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@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
>
>
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> 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@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
>
>
+------------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor (Retired)
mailto:mikes@xxxxxxxx
mailto:msetzerii@xxxxxxxxx
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
