Re: Unable to UEFI boot 11.2 via pxeboot

From: Toomas Soome <tsoome_at_me.com>
Date: Thu, 02 Aug 2018 15:45:07 +0300
Could you check the current with https://svnweb.freebsd.org/changeset/base/337131 <https://svnweb.freebsd.org/changeset/base/337131>

thanks,
toomas

> On 2 Aug 2018, at 15:32, Toomas Soome <tsoome_at_me.com> wrote:
> 
> 
> 
>> On 2 Aug 2018, at 15:08, Timo Völker <timo.voelker_at_fh-muenster.de <mailto:timo.voelker_at_fh-muenster.de>> wrote:
>> 
>> It seems this issue is related to current as well. I did a quick test and got this output, while I tried to (pxe)boot FreeBSD current (without a USB stick plugged in)
>> 
>> https://ibb.co/no8Fve <https://ibb.co/no8Fve>
>> 
>> Best regards
>> 
>> Timo
> 
> the hint is about efipart_inithandles() returning 2, thats errno code for ENOENT. congratz, you have hit the corner case:D
> 
> Since efinet_dev is part of devsw, we can not skip the devswitch init with such error, we still need to walk the list. Let me see if I can provide quick fix.
> 
> rgds,
> toomas
> 
> 
>> 
>>> On 31. Jul 2018, at 14:16, Timo Völker <timo.voelker_at_fh-muenster.de <mailto:timo.voelker_at_fh-muenster.de>> wrote:
>>> 
>>> Hi,
>>> 
>>> I'm unable to boot up the amd64 11.2 via pxeboot using UEFI on a Dell PowerEdge R430. I get this output
>>> 
>>> https://ibb.co/h5ntuT <https://ibb.co/h5ntuT>
>>> 
>>> If I press a key to interrupt reboot, I get to the OK prompt. If I enter lsdev -v, it prints nothing more than "net devices:". The variable currdev is not set (show currdev prints variable 'currdev' not found). I configured pxeboot to be the one and only boot medium in BIOS setup. 
>>> 
>>> However, I found a workaround that works for me. If I put an (empty) USB stick in a USB port of the PowerEdge, it successfully boots via pxeboot (which is still the one and only configured boot medium). I then get this output
>>> 
>>> https://ibb.co/mU8SM8
>>> 
>>> With FreeBSD 11.1 pxeboot worked on the Dell PowerEdge R430, even without a USB stick plugged in. I couldn't test this with FreeBSD 12-current. Hope this helps anyway to find an open issue.
>>> 
>>> I found this thread which seems to be related.
>>> 
>>> https://lists.freebsd.org/pipermail/freebsd-current/2018-July/070082.html
>>> 
>>> Thanks,
>>> 
>>> Timo
>> 
> 
Received on Thu Aug 02 2018 - 10:45:35 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:17 UTC