On Tue, Dec 30, 2025 at 07:46:16AM +0100, Rafael Sadowski wrote: > On Mon Dec 29, 2025 at 06:17:16PM -0800, [email protected] wrote: > > I have the same machine and it works fine also, or at least it did last > > time I tried. > > Does it work if you ZZZ from the text console, right after boot? > > -ml > > Yes and no. Instead of getting stuck in the kernel boot I ends up in a > wired white artefact screen and then the only thing that helps is a hard > reset. >
I bet it's a combination of what kettenis mentioned (corrupt screen) *plus* the well known issue of the keyboard not resuming. Does a USB keyboard work in the failure mode above? Can you ssh into the machine on re0? > I also reset my BIOS settings to factory defaults. No changes except > that my OpenBSD EFI boot entry was gone. > > Perhaps something with the GPU: > > dmesg| grep amd > [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP > amdpmc0 at acpi0: PEP_ > amdpmc0: SMU program 0 version 76.93.0 > amdgpio0 at acpi0 GPIO uid 0 addr 0xfed81500/0x400 irq 7, 184 pins > amdgpu0 at pci6 dev 0 function 0 "ATI Hawk Point" rev 0xd0 > drm0 at amdgpu0 > amdgpu0: msi > amdgpu0: IP DISCOVERY GC 11.0.1 12 CU rev 0x0c > amdgpu0: 1920x1200, 32bpp > wsdisplay0 at amdgpu0 mux 1: console (std, vt100 emulation), using wskbd0 > There is one difference now that I look at it. Mine has this (and works): amdgpu0: IP DISCOVERY GC 11.0.1 12 CU rev 0x0c amdgpu0: 2880x1800, 32bpp jsg/kettenis - could the display resolution have anything to do with this?
