Installation 'halts' at boot after initialising UEFI framebuffer

[Nacho Lariguet]

I am still unable to boot in UEFI mode even with this patch.

first time was on 4.8 (picture 1), then on 5.0, then on 5.2
every one of them a no-go

now that I've seen this patch I tried the daily image for 2019-03-20
setting the loader tunables as described:

sc.probe_early=1 (A)
machdep.hack_efifb_probe_early=1 (B) (updated bug report # 3167)

I did try each one and both of them; the difference being:

+ with (A):
- the server goes to picture 3 (EFI framebuffer information)
- and panics on picture 4 (panic: alst_radix_free: freeing free block)

+ with (B):
- the server hangs (?) on picture 3 (EFI framebuffer information)

Tried this on Dell PowerEdge R710/R610 servers (UEFI 2.1)
last available firmware installed: 6.6.0

Note the difference between picture 0 (last year panic on 4.8) and
picture 4 (today's panic)

And of course selecting BIOS instead of UEFI in boot options works.

On 1/9/19, Michael Neumann <mneumann at ntecs.de> wrote:
> On Mon, Jan 07, 2019 at 03:56:52PM +0000, cbz wrote:
>> On Mon, 7 Jan 2019 at 15:38, Michael Neumann <mneumann at ntecs.de> wrote:
>> > Yes, I had a similar issue. I think what you are seeing is similar to
>> > this:
>> >
>> > https://www.dragonflybsd.org/~mneumann/IMG_20181126_181023.jpg
>>
>> I get a similar screen - so yes I'd say it's stopping at the same
>> point in the build cycle.
>>
>> > I have a patch below that works for me. You need to apply it to
>> > /usr/src
>> > ( cd /usr/src && patch -p1 < patch-fb-machdep.c) recompile and
>> > reinstall
>> > the kernel. Let us know if you have trouble with the patching
>> > procedure.
>> >
>> > https://www.dragonflybsd.org/~mneumann/patch-fb-machdep.c
>> >
>> > You need to set the loader tunable "sc.probe_early=1" before booting in
>> > the boot loader.
>>
>> I'm doing an initial install - on the first machine I have to run
>> dragonflybsd so don't have an environment on which I could rebuild the
>> install media.  So I assume my options are to install Linux or
>> similar, put dragonflybsd in a VM and then use that to rebuild the
>> kernel in the install media?
>
> Or, I will commit the patch above and then you wait a day and download
> a daily snapshot of the image. I think that would be easier for you.
>
> If you are not in a hurry, please wait a bit :)
>
> Regards,
>
>   Michael
>
>


-- 
nacho Lariguet
lariguet at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1.jpeg
Type: image/jpeg
Size: 1707289 bytes
Desc: not available
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20190324/53bf5e96/attachment-0001.jpeg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2.png
Type: image/png
Size: 792829 bytes
Desc: not available
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20190324/53bf5e96/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 3.png
Type: image/png
Size: 738629 bytes
Desc: not available
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20190324/53bf5e96/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 4.png
Type: image/png
Size: 780310 bytes
Desc: not available
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20190324/53bf5e96/attachment-0005.png>