Date: Thu, 5 Jul 2018 16:12:27 +0200 From: Linus Sundqvist <linus.sundqvist@loopia.se> To: Toomas Soome <tsoome@me.com> Cc: FreeBSD Current <freebsd-current@freebsd.org>, imp@freebsd.org Subject: Re: Unable to UEFI boot 11.2 ISO (latest 12.0 as well) Message-ID: <d8ee4dd5-5125-e6a3-3198-7e40ec75856a@loopia.se> In-Reply-To: <69DD5AC1-5FF8-4A6E-993B-F65070D484BF@me.com> References: <86482bdb-60bd-b573-1a98-e14928f4537e@loopia.se> <CBB5DAB8-D05C-4B17-8DD5-0D2EDFD8D41B@me.com> <b507e7cf-4c16-aa44-4452-1351bcd2e524@loopia.se> <1E09B50A-8E4F-4E1E-BBE2-61B1570376D3@me.com> <d51cbc72-977f-9083-90d9-fd1718e8a2bd@loopia.se> <3FB4F603-03A7-4D54-87EA-633C08D8C5E7@me.com> <aa47a1d4-64bb-5c57-8be7-203533eb6d16@loopia.se> <69DD5AC1-5FF8-4A6E-993B-F65070D484BF@me.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --xGtKGCtjITiexKEZkfF5wt11TQYfLiMM6 Content-Type: multipart/mixed; boundary="wpaqE5OcWeZy8bVfZYk0OVymZDV7JkjBc"; protected-headers="v1" From: Linus Sundqvist <linus.sundqvist@loopia.se> To: Toomas Soome <tsoome@me.com> Cc: FreeBSD Current <freebsd-current@freebsd.org>, imp@freebsd.org Message-ID: <d8ee4dd5-5125-e6a3-3198-7e40ec75856a@loopia.se> Subject: Re: Unable to UEFI boot 11.2 ISO (latest 12.0 as well) References: <86482bdb-60bd-b573-1a98-e14928f4537e@loopia.se> <CBB5DAB8-D05C-4B17-8DD5-0D2EDFD8D41B@me.com> <b507e7cf-4c16-aa44-4452-1351bcd2e524@loopia.se> <1E09B50A-8E4F-4E1E-BBE2-61B1570376D3@me.com> <d51cbc72-977f-9083-90d9-fd1718e8a2bd@loopia.se> <3FB4F603-03A7-4D54-87EA-633C08D8C5E7@me.com> <aa47a1d4-64bb-5c57-8be7-203533eb6d16@loopia.se> <69DD5AC1-5FF8-4A6E-993B-F65070D484BF@me.com> In-Reply-To: <69DD5AC1-5FF8-4A6E-993B-F65070D484BF@me.com> --wpaqE5OcWeZy8bVfZYk0OVymZDV7JkjBc Content-Type: text/plain; charset=utf-8 Content-Language: sv Content-Transfer-Encoding: quoted-printable I have no idea how to do that or where to begin, but if anyone would like= to assist with those steps I'll gladly run commands or a test ISO on one= of our Dell servers. Med v=C3=A4nlig h=C3=A4lsning/Best Regards Linus Sundqvist System Engineer, Loopia AB On 05/07/18 10:23, Toomas Soome wrote: >=20 >=20 >> On 5 Jul 2018, at 10:28, Linus Sundqvist <linus.sundqvist@loopia.se> w= rote: >> >> Here's the output, variable 'currdev' not found: >> https://imgur.com/LlBygfr <https://imgur.com/LlBygfr>; >=20 >=20 > Yes indeed, as you got the error, so the variable was not set at all. M= y suggestion would be to walk over the code in main.c, and to try to get = more debug printouts from that dell system=E2=80=A6 Im myself mostly offl= ine till next week. >=20 > rgds, > toomas >=20 >> >> And to answer Rodneys question from before, this is the emulated CD dr= ive from a Dell iDRAC (remote console thingy). >> >> Med v=C3=A4nlig h=C3=A4lsning/Best Regards >> Linus Sundqvist >> System Engineer, Loopia AB >> >> On 05/07/18 09:17, Toomas Soome wrote: >>> Could you check, show currdev from OK prompt before setting it. >>> >>> Somehow the boot device path is shown but we fail to recognize it (as= seen by error message). However, the lsdev -v does show the path, so the= efipart.c seems to do its work correctly. I feel, there should be some c= orner case in efi/loader/main.c where we detect the boot device. >>> >>> Rgds, >>> Toomas >>> >>> Sent from my iPhone >>> >>>> On 5 Jul 2018, at 09:32, Linus Sundqvist <linus.sundqvist@loopia.se>= wrote: >>>> >>>> Running these commands makes the boot menu show up, and then takes m= e to the BSD installer! >>>> >>>> Med v=C3=A4nlig h=C3=A4lsning/Best Regards >>>> Linus Sundqvist >>>> System Engineer, Loopia AB >>>> >>>>> On 04/07/18 16:50, Toomas Soome wrote: >>>>> set currdev=3Dcd1: >>>>> include /boot/loader.rc >>>>> >>>>> This should give menu/boot. >>>>> >>>>> Rgds, >>>>> Toomas >>>>> >>>>> Sent from my iPhone >>>>> >>>>>> On 4 Jul 2018, at 16:25, Linus Sundqvist <linus.sundqvist@loopia.s= e> wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> Sure, while using the 12.0 ISO here is lsdev -v and ls cd0: >>>>>> https://imgur.com/RmYpg7u >>>>>> >>>>>> and here is ls cd1: >>>>>> https://imgur.com/FPsixOw >>>>>> >>>>>> Med v=C3=A4nlig h=C3=A4lsning/Best Regards >>>>>> Linus Sundqvist >>>>>> System Engineer, Loopia AB >>>>>> >>>>>>> On 04/07/18 15:08, Toomas Soome wrote: >>>>>>> Can you post lsdev -v output? >>>>>>> >>>>>>> Also, could you try ls command? Like, ls cd0: =20 >>>>>>> >>>>>>> Rgds, >>>>>>> Toomas >>>>>>> >>>>>>> Sent from my iPhone >>>>>>> >>>>>>>> On 4 Jul 2018, at 12:28, Linus Sundqvist <linus.sundqvist@loopia= =2Ese> wrote: >>>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I'm unable to boot up the amd64 11.2 disk1 ISO as well as the la= test amd64 12.0 disk1 ISO (20180628) using UEFI on a Dell PowerEdge R430 = by getting this error: >>>>>>>> https://imgur.com/a/Idljfhm >>>>>>>> >>>>>>>> The bootonly ISOs seems to show the same error message. >>>>>>>> >>>>>>>> Changing the server to boot via BIOS loads the setup correctly, = however, I want to use UEFI on all our servers, which I have done before.= >>>>>>>> >>>>>>>> The 11.1 ISO boots without any trouble at all using both UEFI an= d BIOS. >>>>>>>> >>>>>>>> I was helped by koobs in #freebsd @ Freenode who asked me to sen= d an e-mail this way and linking to these commits as a reference: >>>>>>>> >>>>>>>> https://reviews.freebsd.org/D13784 >>>>>>>> https://svnweb.freebsd.org/base?view=3Drevision&revision=3D33241= 6 >>>>>>>> >>>>>>>> So far I've tried to UEFI boot the 11.2 ISO and 12.0 ISO with th= e following Dell PowerEdge models without success: >>>>>>>> >>>>>>>> R440 >>>>>>>> R630 >>>>>>>> R430 >>>>>>>> FC430 >>>>>>>> R330 >>>>>>>> R620 >>>>>>>> R420 >>>>>>>> R610 >>>>>>>> >>>>>>>> --=20 >>>>>>>> Med v=C3=A4nlig h=C3=A4lsning/Best Regards >>>>>>>> Linus Sundqvist >>>>>>>> System Engineer, Loopia AB >>>>>>>> >>>>>>> _______________________________________________ >>>>>>> freebsd-current@freebsd.org mailing list >>>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@fre= ebsd.org" >>>>>>> >>>>>> >>>>> _______________________________________________ >>>>> freebsd-current@freebsd.org mailing list >>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freeb= sd.org" >>>>> >>>> >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd= =2Eorg" >>> >> >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" >=20 --wpaqE5OcWeZy8bVfZYk0OVymZDV7JkjBc-- --xGtKGCtjITiexKEZkfF5wt11TQYfLiMM6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEu1yeyYo/yrdJFiO7y+MtoR6bkbkFAls+J0sACgkQy+MtoR6b kbmvFg//QqkGYoy9S5GEOIKBJSy8bNo6x2scp2t1tWK97aym/067frxrHUb28sQ+ CUOGuN2etHHAPCDb5u7BAswli8r1+zY311EWsJJqD++UVZjjZBvGgHMPLcQWttbH hUEh4NHo+9yTookQ6V/cin9Y75aRuBnid9TG5yC0GbHjYqrVv4NM5zdCSCike9nC Unamutut5YZD3AM4ZjwWVulZK0/2hNyPUG8/JrL8ysaf9pHYmaHGaD+rrEFo5RtW LHhGyZ1YDaEa5LpUdM2Bjnadwtx9OweXH+GRkDE5auUaY/Gc5QjAQjhP5PPQkUzT jY/aIQp3ATasLH9BlpH0cEiIUe9eAwJ8XZ9WcPGTQ5zGmhAUjHp4/rs1Kz5ZDyWM WMAuBRqhHsli2Oy91rPhRJkOV3qXkwZshP0SPw4E31bwjpvmDC/swZas9K0ICVT2 WW3h14cZyifvHf0EWKoZz+rkh94HsZrbtZdEQHQgyYZuvlsTpbkOA1XexZEsSjU5 b1JJYfHl7Q/9IYOX5nOX+LmUILL+kOc/9XmHKH5Hh08sdZ0SQPQrxOBFa2gAntpo NlKGbQXd9DgsmLz0TcgrPm/vEpnE3SO1/z2JcJ/Lpea/I6aAbuyRP0FioW1wnuJ7 781CEBPHc/PHvd9oXHR5iDPNLc1yuCNULmcszVnbonM6/XhIMmk= =rFSb -----END PGP SIGNATURE----- --xGtKGCtjITiexKEZkfF5wt11TQYfLiMM6--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d8ee4dd5-5125-e6a3-3198-7e40ec75856a>