For the record, Mark Kettenis' patch below fixed the boot stuck problem
on my Intel NUC Kit NUC7PJYH mini server, see the following email thread:
Thanks a lot for this.
> Hi Mark,
> on my Lenovo V130 the patch works.
on my Lenovo V130 the patch works. Now I'm able to boot the current
kernel again, without the need to remove the radeon and amdgpu driver
Thanks and best regards,
On 10/27/20 1:40 PM, Mark Kettenis wrote:
Please don't have technical discussions on misc@; some developers,
like me, only read it sporadically. The tech@ list is a much better
The problem with your approach is that you allocate memory at a fixed
address, and we can't be sure that memory is available. We may have
On Sun, Jul 05, 2020 at 09:32:47PM -0700, Kastus Shchuka wrote:
> On Sat, Jul 04, 2020 at 11:09:54AM +, Michael Baehr wrote:
> > Kastus Shchuka wrote:
> > “I installed 2020-07-03 snapshot on ASRock J4105M system and I am not able
> > to boot it.
> > Boot stops at the line
> > entry
In my case replacing bootx64.efi with new one compiled with
aforementioned patch took off.
ODROID-H2 could boot kernel from latest snapshot.
Part of dmesg:
boot> boot bsd
booting hd0a:bsd: 14464328+3175440+344096+0+872448
entry point at 0x1001000
with the patch the kernel loads and doesn't stop at "entry point at
0x1001000". But the kernel stops with a "Stopped at
gfx_v9_0_wait_reg_mem+0x307: int $3"
So for my machine the patch is the right direction but not the solution
:( I've tried the boot with the current snapshot
On Sat, Jul 04, 2020 at 11:09:54AM +, Michael Baehr wrote:
> Kastus Shchuka wrote:
> “I installed 2020-07-03 snapshot on ASRock J4105M system and I am not able to
> boot it.
> Boot stops at the line
> entry point at 0x1001000
> If I try bsd.rd kernel, it boots just fine. After this
Mail list logo