On Wed, 27 Aug 2025 at 20:56, Atiq Rahman <ati...@gmail.com> wrote:
> > I assume you did see “Booting..” text, then it cleared the screen and thats
> > it.
> Yep, I did see that (a few lines including booting) before it showed the
> cursor only screen. (photo: p1)
>
> > ok framebuffer get
> output on photo (p2)
Based on the photograph, it seems like your framebuffer base address
is 0x7a_1000_0000 which is above the 32-bit boundary. When you enable
"prom_debug" and "kbm_debug", there is some early boot code which
can't use a 64-bit address to write to the display. This ultimately
causes the writes to go off into space, and may collide with other
memory that upsets the boot process.
This is described in a ticket I'm working on at the moment for another
system that has this problem:
17548 early boot framebuffer reach exceeds grasp
https://www.illumos.org/issues/17548
https://code.illumos.org/c/illumos-gate/+/4350
Should hopefully be finished soon!
Cheers.
--
Joshua M. Clulow
http://blog.sysmgr.org
_______________________________________________
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev
