Re: Unable to UEFI boot 11.2 via pxeboot

2018-08-03 Thread Timo Völker
> On 3. Aug 2018, at 10:17, Toomas Soome  wrote:
> 
> 
> 
>> On 3 Aug 2018, at 10:28, Timo Völker  wrote:
>> 
>> Hi Toomas,
>> 
>> it seems your fix works here. Some of the error messages remain, but I was 
>> able to (pxe)boot without a USB stick plugged in.
>> 
>> https://ibb.co/g8Bkfe
>> 
>> Right after the moment from the screenshot, the FreeBSD boot manager showed 
>> up.
>> 
>> Thanks,
>> 
>> Timo
> 
> Ok, so far so good. As seen from the screen dump, some cleanup is required, I 
> do not think we should print about efipart_inithandles() in case of errno 2 - 
> thats perfectly normal case if there are no block devices. Update commited:)
> 
> rgds,
> toomas

It still works and it looks better with less error messages :-)

https://ibb.co/bVv9Oz

Thanks,

Timo

> 
>> 
>>> On 2. Aug 2018, at 14:45, Toomas Soome  wrote:
>>> 
>>> Could you check the current with 
>>> https://svnweb.freebsd.org/changeset/base/337131
>>> 
>>> thanks,
>>> toomas
>>> 
 On 2 Aug 2018, at 15:32, Toomas Soome  wrote:
 
 
 
> On 2 Aug 2018, at 15:08, Timo Völker  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
> 
> 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  
>> 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
>> 
>> 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
> 
 
>>> 
>> 
> 



smime.p7s
Description: S/MIME cryptographic signature


Re: Unable to UEFI boot 11.2 via pxeboot

2018-08-03 Thread Toomas Soome


> On 3 Aug 2018, at 10:28, Timo Völker  wrote:
> 
> Hi Toomas,
> 
> it seems your fix works here. Some of the error messages remain, but I was 
> able to (pxe)boot without a USB stick plugged in.
> 
> https://ibb.co/g8Bkfe
> 
> Right after the moment from the screenshot, the FreeBSD boot manager showed 
> up.
> 
> Thanks,
> 
> Timo

Ok, so far so good. As seen from the screen dump, some cleanup is required, I 
do not think we should print about efipart_inithandles() in case of errno 2 - 
thats perfectly normal case if there are no block devices. Update commited:)

rgds,
toomas


> 
>> On 2. Aug 2018, at 14:45, Toomas Soome  wrote:
>> 
>> Could you check the current with 
>> https://svnweb.freebsd.org/changeset/base/337131
>> 
>> thanks,
>> toomas
>> 
>>> On 2 Aug 2018, at 15:32, Toomas Soome  wrote:
>>> 
>>> 
>>> 
 On 2 Aug 2018, at 15:08, Timo Völker  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
 
 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  
> 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
> 
> 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
 
>>> 
>> 
> 

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: Unable to UEFI boot 11.2 via pxeboot

2018-08-03 Thread Timo Völker
Hi Toomas,

it seems your fix works here. Some of the error messages remain, but I was able 
to (pxe)boot without a USB stick plugged in.

https://ibb.co/g8Bkfe

Right after the moment from the screenshot, the FreeBSD boot manager showed up.

Thanks,

Timo

> On 2. Aug 2018, at 14:45, Toomas Soome  wrote:
> 
> Could you check the current with 
> https://svnweb.freebsd.org/changeset/base/337131
> 
> thanks,
> toomas
> 
>> On 2 Aug 2018, at 15:32, Toomas Soome  wrote:
>> 
>> 
>> 
>>> On 2 Aug 2018, at 15:08, Timo Völker  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
>>> 
>>> 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  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
 
 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
>>> 
>> 
> 



smime.p7s
Description: S/MIME cryptographic signature


Re: Unable to UEFI boot 11.2 via pxeboot

2018-08-02 Thread Toomas Soome


> On 2 Aug 2018, at 16:42, Kyle Evans  wrote:
> 
> On Thu, Aug 2, 2018 at 7:45 AM, Toomas Soome  wrote:
>>> On 2 Aug 2018, at 15:32, Toomas Soome  wrote:
>>> 
>>> 
>>> 
 On 2 Aug 2018, at 15:08, Timo Völker >>> > 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 
 
 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
>>> 
>> 
>> Could you check the current with 
>> https://svnweb.freebsd.org/changeset/base/337131 
>> 
>> 
>> thanks,
>> toomas
>> 
> 
> Hmm... that's less than great. Is this worth an MFC + 11.2 EN? I'd
> suspect it's not an entirely common case at all, but loader.efi is
> highly visible and actually updated in stable/11 (vs. soon-to-be
> thrown on ESP in head.
> 
> 

Once the fix is confirmed, I think it is worth MFC (I haven't checked 11 
source, however). I just want to be sure the provided patch will provide 
complete fix.

rgds,
toomas

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: Unable to UEFI boot 11.2 via pxeboot

2018-08-02 Thread Kyle Evans
On Thu, Aug 2, 2018 at 7:45 AM, Toomas Soome  wrote:
>> On 2 Aug 2018, at 15:32, Toomas Soome  wrote:
>>
>>
>>
>>> On 2 Aug 2018, at 15:08, Timo Völker >> > 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 
>>>
>>> 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
>>
>
> Could you check the current with 
> https://svnweb.freebsd.org/changeset/base/337131 
> 
>
> thanks,
> toomas
>

Hmm... that's less than great. Is this worth an MFC + 11.2 EN? I'd
suspect it's not an entirely common case at all, but loader.efi is
highly visible and actually updated in stable/11 (vs. soon-to-be
thrown on ESP in head.

Thanks,

Kyle Evans
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: Unable to UEFI boot 11.2 via pxeboot

2018-08-02 Thread Toomas Soome


> On 2 Aug 2018, at 15:08, Timo Völker  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
> 
> 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  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
>> 
>> 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
> 

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: Unable to UEFI boot 11.2 via pxeboot

2018-08-02 Thread Toomas Soome
Could you check the current with 
https://svnweb.freebsd.org/changeset/base/337131 


thanks,
toomas

> On 2 Aug 2018, at 15:32, Toomas Soome  wrote:
> 
> 
> 
>> On 2 Aug 2018, at 15:08, Timo Völker > > 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 
>> 
>> 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 >> > 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 
>>> 
>>> 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
>> 
> 

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: Unable to UEFI boot 11.2 via pxeboot

2018-08-02 Thread Timo Völker
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

Best regards

Timo

> On 31. Jul 2018, at 14:16, Timo Völker  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
> 
> 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



smime.p7s
Description: S/MIME cryptographic signature