NetBSD Problem Report #58732
From www@netbsd.org Wed Oct 9 03:27:17 2024
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256
client-signature RSA-PSS (2048 bits) client-digest SHA256)
(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
by mollari.NetBSD.org (Postfix) with ESMTPS id 72DF31A923B
for <gnats-bugs@gnats.NetBSD.org>; Wed, 9 Oct 2024 03:27:17 +0000 (UTC)
Message-Id: <20241009032716.46B271A923D@mollari.NetBSD.org>
Date: Wed, 9 Oct 2024 03:27:16 +0000 (UTC)
From: bjzuber@icloud.com
Reply-To: bjzuber@icloud.com
To: gnats-bugs@NetBSD.org
Subject: i915drmkms black screen on boot
X-Send-Pr-Version: www-1.0
>Number: 58732
>Category: port-amd64
>Synopsis: i915drmkms black screen on boot
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: port-amd64-maintainer
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Oct 09 03:30:00 +0000 2024
>Last-Modified: Thu Oct 10 18:20:01 +0000 2024
>Originator: Bryan Zuber
>Release: 10.0
>Organization:
>Environment:
NetBSD chaos 10.0_STABLE NetBSD 10.0_STABLE (GENERIC) #0: Tue Oct 8 11:27:01 UTC 2024 mkrepro@mkrepro.NetBSD.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64
>Description:
Screen goes black during boot on ASUS Chromebox CN62 equipped with Intel i915 graphics and system is unusable.
userconf disable i915drmkms* allows system to boot, but if HDMI cable is unplugged, boot hangs and system does not respond, therefore cannot be used as a headless server.
>How-To-Repeat:
>Fix:
>Audit-Trail:
From: Rin Okuyama <rokuyama.rk@gmail.com>
To: gnats-bugs@netbsd.org, port-amd64-maintainer@netbsd.org,
gnats-admin@netbsd.org, netbsd-bugs@netbsd.org, bjzuber@icloud.com
Cc:
Subject: Re: port-amd64/58732: i915drmkms black screen on boot
Date: Wed, 9 Oct 2024 13:35:10 +0900
- Can you share /var/run/dmesg.boot for successful boot?
- What happens if additional `userconf disable acpivga*` for
bootloader?
Thanks,
rin
From: Bryan Zuber <bjzuber@icloud.com>
To: gnats-bugs@netbsd.org
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:
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003,
2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013,
2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023,
2024
The NetBSD Foundation, Inc. All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
NetBSD 10.0 (GENERIC) #0: Thu Mar 28 08:33:33 UTC 2024
mkrepro@mkrepro.NetBSD.org:/usr/src/sys/arch/amd64/compile/GENERIC
total memory = 1921 MB
avail memory = 1828 MB
timecounter: Timecounters tick every 10.000 msec
Kernelized RAIDframe activated
i915drmkms* disabled
timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
efi: systbl at pa 77df7018
mainbus0 (root)
ACPI: RSDP 0x0000000077E1C014 000024 (v02 COREv4)
ACPI: XSDT 0x0000000077E1B0E8 00006C (v01 COREv4 COREBOOT 00000000
01000013)
ACPI: FACP 0x0000000077E1A000 000114 (v06 COREv4 COREBOOT 00000000 CORE
20230628)
ACPI: DSDT 0x0000000077E16000 00357C (v02 COREv4 COREBOOT 20110725 INTL
20230628)
ACPI: FACS 0x0000000077E36240 000040
ACPI: SSDT 0x0000000077E15000 000EFC (v02 COREv4 COREBOOT 00000000 CORE
20230628)
ACPI: MCFG 0x0000000077E14000 00003C (v01 COREv4 COREBOOT 00000000 CORE
20230628)
ACPI: TCPA 0x0000000077E13000 000032 (v02 COREv4 COREBOOT 00000000 CORE
20230628)
ACPI: APIC 0x0000000077E12000 000062 (v03 COREv4 COREBOOT 00000000 CORE
20230628)
ACPI: HPET 0x0000000077E11000 000038 (v01 COREv4 COREBOOT 00000000 CORE
20230628)
ACPI: SSDT 0x0000000077E10000 00005C (v02 COREv4 SERIALIO 0000002B CORE
20230628)
ACPI: TCPA 0x0000000077E0F000 000032 (v02 INTEL EDK2 00000002
01000013)
ACPI: BGRT 0x0000000077E0E000 000038 (v01 INTEL EDK2 00000002
01000013)
ACPI: 3 ACPI AML tables successfully acquired and loaded
ioapic0 at mainbus0 apid 0: pa 0xfec00000, version 0x20, 40 pins
cpu0 at mainbus0 apid 0
cpu0: Use lfence to serialize rdtsc
cpu0: Intel(R) Celeron(R) 2955U @ 1.40GHz, id 0x40651
cpu0: node 0, package 0, core 0, smt 0
cpu1 at mainbus0 apid 2
cpu1: Intel(R) Celeron(R) 2955U @ 1.40GHz, id 0x40651
cpu1: node 0, package 0, core 1, smt 0
acpi0 at mainbus0: Intel ACPICA 20221020
acpi0: X/RSDT: OemId <COREv4,COREBOOT,00000000>, AslId < ,01000013>
acpi0: MCFG: segment 0, bus 0-63, address 0x00000000f0000000
acpi0: SCI interrupting at int 9
acpi0: fixed power button present
timecounter: Timecounter "ACPI-Safe" frequency 3579545 Hz quality 900
hpet0 at acpi0: high precision event timer (mem 0xfed00000-0xfed00400)
timecounter: Timecounter "hpet0" frequency 14318180 Hz quality 2000
FWH (INT0800) at acpi0 not configured
attimer1 at acpi0 (TIMR, PNP0100): io 0x40-0x43,0x50-0x53 irq 0
GPIO (INT33C7) at acpi0 not configured
com0 at acpi0 (COM1, PNP0501-1): io 0x3f8-0x3ff irq 4
com0: ns16550a, 16-byte FIFO
tpm0 at acpi0 (TPM, PNP0C31-2313387420): io 0xc31-0xc32 mem
0xfed40000-0xfed44fff
tpm0: device 0x000b15d1 rev 0x10
acpitz0 at acpi0 (THRM): cpu0 cpu1
acpitz0: active cooling level 0: 90.0C
acpitz0: active cooling level 1: 75.0C
acpitz0: active cooling level 2: 67.0C
acpitz0: active cooling level 3: 50.0C
acpitz0: active cooling level 4: 0.0C
acpitz0: levels: critical 100.0 C, passive 90.0 C
acpifan0 at acpi0 (FAN0, PNP0C0B-0): ACPI Fan
acpifan1 at acpi0 (FAN1, PNP0C0B-1): ACPI Fan
acpifan2 at acpi0 (FAN2, PNP0C0B-2): ACPI Fan
acpifan3 at acpi0 (FAN3, PNP0C0B-3): ACPI Fan
acpifan4 at acpi0 (FAN4, PNP0C0B-4): ACPI Fan
CTBL (BOOT0000) at acpi0 not configured
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
pchb0 at pci0 dev 0 function 0: Intel Core 4G (mobile) Host Bridge, DRAM
(rev. 0x09)
genfb0 at pci0 dev 2 function 0: Intel HD Graphics (GT1) (rev. 0x09)
genfb0: framebuffer at 0x80000000, size 1024x768, depth 32, stride 4096
genfb0: shadow framebuffer enabled, size 3072 KB
wsdisplay0 at genfb0 kbdmux 1: console (default, vt100 emulation)
wsmux1: connecting to wsdisplay0
drm at genfb0 not configured
hdaudio0 at pci0 dev 3 function 0: HD Audio Controller
hdaudio0: interrupting at msi0 vec 0
hdaudio0: HDA ver. 1.0, OSS 2, ISS 0, BSS 0, SDO 1, 64-bit
hdafg0 at hdaudio0: Intel HDMI/DP
hdafg0: DP00 8ch: Digital Out [Jack]
hdafg0: 8ch/0ch 48000Hz PCM16*
audio0 at hdafg0: playback
audio0: slinear_le:16 2ch 48000Hz, blk 1920 bytes (10ms) for playback
spkr0 at audio0: PC Speaker (synthesized)
wsbell at spkr0 not configured
Intel product 0a03 (miscellaneous DASP, revision 0x09) at pci0 dev 4
function 0 not configured
xhci0 at pci0 dev 20 function 0: Intel Core 4G (mobile) USB xHCI (rev. 0x04)
xhci0: 64-bit DMA
xhci0: interrupting at msi1 vec 0
xhci0: xHCI version 1.0
usb0 at xhci0: USB revision 3.0
usb1 at xhci0: USB revision 2.0
Intel Core 4G (mobile) MEI (miscellaneous communications, revision 0x04)
at pci0 dev 22 function 0 not configured
hdaudio1 at pci0 dev 27 function 0: HD Audio Controller
hdaudio1: interrupting at msi2 vec 0
hdaudio1: HDA ver. 1.0, OSS 4, ISS 4, BSS 0, SDO 1, 64-bit
hdafg1 at hdaudio1: Realtek product 0283
hdafg1: autoconfiguration error: pin 21 has wrong direction for 01
hdafg1: 0ch/0ch 44100Hz 48000Hz 96000Hz 192000Hz PCM16 PCM20 PCM24 AC3
PCM16*
audio1 at hdafg1: playback, capture, full duplex, independent
audio1: slinear_le:16 2ch 48000Hz, blk 1920 bytes (10ms) for playback
audio1: slinear_le:16 2ch 48000Hz, blk 1920 bytes (10ms) for recording
spkr1 at audio1: PC Speaker (synthesized)
wsbell at spkr1 not configured
ppb0 at pci0 dev 28 function 0: Intel Core 4G (mobile) PCIe (rev. 0xe4)
ppb0: PCI Express capability version 2 <Root Port of PCI-E Root Complex>
x1 @ 5.0GT/s
ppb0: link is x1 @ 2.5GT/s
pci1 at ppb0 bus 1
pci1: i/o space, memory space enabled, rd/line, wr/inv ok
re0 at pci1 dev 0 function 0: RealTek 8168/8111 PCIe Gigabit Ethernet
(rev. 0x0c)
re0: interrupting at msix3 vec 0
re0: RTL8168G/8111G (0x4c00)
re0: Ethernet address 2c:60:0c:b7:92:e4
re0: using 256 tx descriptors
rgephy0 at re0 phy 7: RTL8251 1000BASE-T media interface, rev. 0
rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, auto
ppb1 at pci0 dev 28 function 1: Intel Core 4G (mobile) PCIe (rev. 0xe4)
ppb1: PCI Express capability version 2 <Root Port of PCI-E Root Complex>
x1 @ 5.0GT/s
ppb1: link is x1 @ 2.5GT/s
pci2 at ppb1 bus 2
pci2: i/o space, memory space enabled, rd/line, wr/inv ok
Atheros Communications AR9462 Wireless LAN (miscellaneous network,
revision 0x01) at pci2 dev 0 function 0 not configured
ppb2 at pci0 dev 28 function 2: Intel Core 4G (mobile) PCIe (rev. 0xe4)
ppb2: PCI Express capability version 2 <Root Port of PCI-E Root Complex>
x2 @ 5.0GT/s
pci3 at ppb2 bus 3
pci3: i/o space, memory space enabled, rd/line, wr/inv ok
pcib0 at pci0 dev 31 function 0: Intel Core 4G (mobile) LPC (rev. 0x04)
ahcisata0 at pci0 dev 31 function 2: Intel Core 4G (mobile) SATA
Controller (AHCI) (rev. 0x04)
ahcisata0: 64-bit DMA
ahcisata0: AHCI revision 1.30, 2 ports, 32 slots, CAP
0xdf34ff01<PSC,SSC,PMD,SAM,ISS=0x3=Gen3,SCLO,SAL,SALP,SSS,SMPS,SNCQ,S64A>
ahcisata0: interrupting at msi4 vec 0
atabus0 at ahcisata0 channel 0
ichsmb0 at pci0 dev 31 function 3: Intel Core 4G (mobile) SMBus (rev. 0x04)
ichsmb0: interrupting at ioapic0 pin 18
iic0 at ichsmb0: I2C bus
Intel Core 4G (mobile) Thermal (miscellaneous DASP, revision 0x04) at
pci0 dev 31 function 6 not configured
isa0 at pcib0
pcppi0 at isa0 port 0x61
spkr2 at pcppi0: PC Speaker
wsbell at spkr2 not configured
midi0 at pcppi0: PC speaker
sysbeep0 at pcppi0
attimer1: attached to pcppi0
acpicpu0 at cpu0: ACPI CPU
acpicpu0: C1: FFH, lat 0 us, pow 1000 mW
acpicpu0: C2: FFH, lat 67 us, pow 900 mW
acpicpu0: C3: FFH, lat 148 us, pow 700 mW
acpicpu0: P0: FFH, lat 10 us, pow 15000 mW, 1400 MHz
acpicpu0: P1: FFH, lat 10 us, pow 12559 mW, 1200 MHz
acpicpu0: P2: FFH, lat 10 us, pow 10217 mW, 1000 MHz
acpicpu0: P3: FFH, lat 10 us, pow 7982 mW, 800 MHz
acpicpu0: T0: FFH, lat 1 us, pow 1000 mW, 100 %
acpicpu0: T1: FFH, lat 1 us, pow 940 mW, 94 %
acpicpu0: T2: FFH, lat 1 us, pow 880 mW, 88 %
acpicpu0: T3: FFH, lat 1 us, pow 820 mW, 82 %
acpicpu0: T4: FFH, lat 1 us, pow 760 mW, 75 %
acpicpu0: T5: FFH, lat 1 us, pow 700 mW, 69 %
acpicpu0: T6: FFH, lat 1 us, pow 640 mW, 63 %
acpicpu0: T7: FFH, lat 1 us, pow 580 mW, 57 %
acpicpu0: T8: FFH, lat 1 us, pow 520 mW, 50 %
acpicpu0: T9: FFH, lat 1 us, pow 460 mW, 44 %
acpicpu0: T10: FFH, lat 1 us, pow 400 mW, 38 %
acpicpu0: T11: FFH, lat 1 us, pow 340 mW, 32 %
acpicpu0: T12: FFH, lat 1 us, pow 280 mW, 25 %
acpicpu0: T13: FFH, lat 1 us, pow 220 mW, 19 %
acpicpu0: T14: FFH, lat 1 us, pow 160 mW, 13 %
coretemp0 at cpu0: thermal sensor, 1 C resolution, Tjmax=100
acpicpu1 at cpu1: ACPI CPU
coretemp1 at cpu1: thermal sensor, 1 C resolution, Tjmax=100
timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
timecounter: Timecounter "TSC" frequency 1396768000 Hz quality 3000
uhub0 at usb0: NetBSD (0x0000) xHCI root hub (0x0000), class 9/0, rev
3.00/1.00, addr 0
uhub0: 4 ports with 4 removable, self powered
uhub1 at usb1: NetBSD (0x0000) xHCI root hub (0x0000), class 9/0, rev
2.00/1.00, addr 0
uhub1: 8 ports with 8 removable, self powered
IPsec: Initialized Security Association Processing.
tpm0: read 8 bytes, expected 10
tpm0: deactivating entropy source
ahcisata0 port 0: device present, speed: 6.0Gb/s
uhidev0 at uhub1 port 3 configuration 1 interface 0
uhidev0: CHICONY (0x04f2) USB Keyboard (0x0833), rev 1.10/1.11, addr 1,
iclass 3/1
ukbd0 at uhidev0
wskbd0 at ukbd0: console keyboard, using wsdisplay0
uhidev1 at uhub1 port 3 configuration 1 interface 1
uhidev1: CHICONY (0x04f2) USB Keyboard (0x0833), rev 1.10/1.11, addr 1,
iclass 3/0
uhidev1: 3 report ids
uhid0 at uhidev1 reportid 1: input=1, output=0, feature=0
uhid1 at uhidev1 reportid 2: input=1, output=0, feature=0
uhid2 at uhidev1 reportid 3: input=3, output=0, feature=0
ubt0 at uhub1 port 4
ubt0: <2147483624><2147483520><2147483529> (0x04ca)
<2147483624><2147483520><2147483529> (0x3007), rev 1.10/0.01, addr 2
wd0 at atabus0 drive 0
wd0: <SanDisk SSD U110 16GB>
wd0: drive supports 1-sector PIO transfers, LBA48 addressing
wd0: 15272 MB, 31029 cyl, 16 head, 63 sec, 512 bytes/sect x 31277232 sectors
wd0: GPT GUID: ab842c07-d989-4572-92d4-3faa9f70399d
dk0 at wd0: "01b2d171-4276-47b4-b31c-a10f6a6c4070", 262144 blocks at 64,
type: msdos
dk1 at wd0: "999ca1ce-3017-4285-9778-07c83377f7a9", 28917824 blocks at
262208, type: ffs
dk2 at wd0: "f9eb9c83-fd6b-4782-bbcb-3cc9c6f3e038", 2097152 blocks at
29180032, type: swap
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6
(Ultra/133), NCQ (32 tags)
wd0(ahcisata0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6
(Ultra/133) (using DMA), NCQ (31 tags)
swwdog0: software watchdog initialized
WARNING: 1 error while detecting hardware; check system log.
boot device: wd0
root on dk1 dumps on dk2
root file system type: ffs
kern.module.path=/stand/amd64/10.0/modules
wsdisplay0: screen 1 added (default, vt100 emulation)
wsdisplay0: screen 2 added (default, vt100 emulation)
wsdisplay0: screen 3 added (default, vt100 emulation)
wsdisplay0: screen 4 added (default, vt100 emulation)
On 10/8/2024 11:40 PM, Rin Okuyama via gnats wrote:
> The following reply was made to PR port-amd64/58732; it has been noted by GNATS.
>
> From: Rin Okuyama <rokuyama.rk@gmail.com>
> To: gnats-bugs@netbsd.org, port-amd64-maintainer@netbsd.org,
> gnats-admin@netbsd.org, netbsd-bugs@netbsd.org, bjzuber@icloud.com
> Cc:
> Subject: Re: port-amd64/58732: i915drmkms black screen on boot
> Date: Wed, 9 Oct 2024 13:35:10 +0900
>
> - Can you share /var/run/dmesg.boot for successful boot?
> - What happens if additional `userconf disable acpivga*` for
> bootloader?
>
> Thanks,
> rin
>
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: port-amd64/58732: i915drmkms black screen on boot
Date: Wed, 9 Oct 2024 18:12:51 +0200
Can you try booting with the display connected but turned off?
That makes a difference for me in PR 56997 (black screen with "walking
morse code on top", obviously display output timing totally off when
booting normally, but working console when booting with display turned
off), I wonder if this is a similar effect.
Martin
From: Bryan Zuber <bjzuber@icloud.com>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: port-amd64/58732: i915drmkms black screen on boot
Date: Wed, 9 Oct 2024 11:32:23 -0500
Yes, it boots properly with the display plugged in but turned off.
On 10/9/2024 11:15 AM, Martin Husemann via gnats wrote:
> The following reply was made to PR port-amd64/58732; it has been noted by GNATS.
>
> From: Martin Husemann <martin@duskware.de>
> To: gnats-bugs@netbsd.org
> Cc:
> Subject: Re: port-amd64/58732: i915drmkms black screen on boot
> Date: Wed, 9 Oct 2024 18:12:51 +0200
>
> Can you try booting with the display connected but turned off?
>
> That makes a difference for me in PR 56997 (black screen with "walking
> morse code on top", obviously display output timing totally off when
> booting normally, but working console when booting with display turned
> off), I wonder if this is a similar effect.
>
> Martin
>
From: Rin Okuyama <rokuyama.rk@gmail.com>
To: gnats-bugs@netbsd.org, port-amd64-maintainer@netbsd.org,
gnats-admin@netbsd.org, netbsd-bugs@netbsd.org, bjzuber@icloud.com
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>
> To: gnats-bugs@netbsd.org
> 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
From: Bryan Zuber <bjzuber@icloud.com>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: port-amd64/58732: i915drmkms black screen on boot
Date: Thu, 10 Oct 2024 11:57:41 -0500
I have the latest version of the MrChromebox firmware and have tried a few d=
ifferent OSes on the device and observed that this issue with failing to boo=
t sans monitor only seems to occur on NetBSD and FreeBSD, but Alpine Linux a=
nd Debian have booted with no issues. In the case of FreeBSD, I can get it t=
o boot headlessly by adding `console=3D"nullconsole"` to loader.conf. Also, I=
noticed that the i915kms module is not enabled by default in FreeBSD, so th=
e headless boot problem might be a completely separate issue from the i915dr=
mkms black screen problem.
> On Oct 10, 2024, at 4:50=E2=80=AFAM, Rin Okuyama via gnats <gnats-admin@ne=
tbsd.org> wrote:
>=20
> =EF=BB=BFThe following reply was made to PR port-amd64/58732; it has been n=
oted by GNATS.
>=20
> From: Rin Okuyama <rokuyama.rk@gmail.com>
> To: gnats-bugs@netbsd.org, port-amd64-maintainer@netbsd.org,
> gnats-admin@netbsd.org, netbsd-bugs@netbsd.org, bjzuber@icloud.com
> Cc:
> Subject: Re: port-amd64/58732: i915drmkms black screen on boot
> Date: Thu, 10 Oct 2024 18:46:36 +0900
>=20
>> 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.
>>=20
>> From: Bryan Zuber <bjzuber@icloud.com>
>> To: gnats-bugs@netbsd.org
>> Cc:
>> Subject: Re: port-amd64/58732: i915drmkms black screen on boot
>> Date: Wed, 9 Oct 2024 10:21:50 -0500
>>=20
>> Adding `userconf=3Ddisable acpivga*` to /boot.cfg has no effect, the
>> device still hangs when booting without a monitor plugged in.
>>=20
>> Here is /var/run/dmesg.boot:
>=20
> Thank you for sharing your dmesg. There seems no support
> for acpivga(4). But,
>=20
>> com0 at acpi0 (COM1, PNP0501-1): io 0x3f8-0x3ff irq 4
>> com0: ns16550a, 16-byte FIFO
>=20
> this one is nice. I've found an interesting report:
>=20
> https://github.com/MrChromebox/firmware/issues/196
>=20
> 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.
>=20
> They also suggest (1) firmware update, or (2) fake display
> device for headless operation.
>=20
> Thanks,
> rin
>=20
(Contact us)
$NetBSD: query-full-pr,v 1.49 2026/05/14 01:52:41 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.
Home