Re: port-amd64/58732: i915drmkms black screen on boot

["Rin Okuyama via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR port-amd64/58732; it has been noted by GNATS.

From: Rin Okuyama <rokuyama.rk%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost, port-amd64-maintainer%netbsd.org@localhost,
 gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, bjzuber%icloud.com@localhost
Cc: 
Subject: Re: port-amd64/58732: i915drmkms black screen on boot
Date: Thu, 10 Oct 2024 18:46:36 +0900

 On 2024/10/10 0:25, Bryan Zuber via gnats wrote:
 > The following reply was made to PR port-amd64/58732; it has been noted by GNATS.
 > 
 > From: Bryan Zuber <bjzuber%icloud.com@localhost>
 > To: gnats-bugs%netbsd.org@localhost
 > Cc:
 > Subject: Re: port-amd64/58732: i915drmkms black screen on boot
 > Date: Wed, 9 Oct 2024 10:21:50 -0500
 > 
 >   Adding `userconf=disable acpivga*` to /boot.cfg has no effect, the
 >   device still hangs when booting without a monitor plugged in.
 >   
 >   Here is /var/run/dmesg.boot:
 
 Thank you for sharing your dmesg. There seems no support
 for acpivga(4). But,
 
 >   com0 at acpi0 (COM1, PNP0501-1): io 0x3f8-0x3ff irq 4
 >   com0: ns16550a, 16-byte FIFO
 
 this one is nice. I've found an interesting report:
 
 https://github.com/MrChromebox/firmware/issues/196
 
 It seems when `Suzy-Q` (aka `CCD`) cable is plugged into
 one of the USB ports, it works as USB tty device. Then,
 `consdev com0,115200` command to our bootloader enables
 serial console. If possible, this would be really helpful
 for debugging.
 
 They also suggest (1) firmware update, or (2) fake display
 device for headless operation.
 
 Thanks,
 rin