From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=0.2 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED
	autolearn=no autolearn_force=no version=3.4.4
Received: (qmail 19967 invoked from network); 3 Apr 2023 22:29:07 -0000
Received: from 9front.inri.net (168.235.81.73)
  by inbox.vuxu.org with ESMTPUTF8; 3 Apr 2023 22:29:07 -0000
Received: from wopr.sciops.net ([216.126.196.60]) by 9front; Mon Apr  3 18:27:16 -0400 2023
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sciops.net; s=20210706;
	t=1680560733;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:  in-reply-to:in-reply-to;
	bh=geJ9hTHL8xJo7xf0MpYufXIHRyy+niz1YVoRqDA9pbI=;
	b=gtODLvbAURwfFB8oZfzZw/GZGfp8UqaWdc/Udk0ebO0eJbbdgdE7BJ4YvZF9nDz1i0+lhJ
	EsfSGLIcDQmF4+Xxpfoe7Tjqahu2dYTJpYZwdhYqTd7Hupcq7TAjkMa4a4aVtrUROzjJyj
	5Rbs5Vc7XyB+FWoOifO+RsUxuHlBUcs=
Received: 
	by wopr.sciops.net (OpenSMTPD) with ESMTPSA id bb68e7a6 (TLSv1.2:ECDHE-RSA-CHACHA20-POLY1305:256:NO)
	for <9front@9front.org>;
	Mon, 3 Apr 2023 15:25:33 -0700 (PDT)
Message-ID: <7439E8B219466B30F6E6BB8B134493D2@wopr.sciops.net>
Date: Tue, 04 Apr 2023 00:27:09 +0200
From: qwx@sciops.net
To: 9front@9front.org
In-Reply-To: <77E481DAE27DCF5720BE14B37790E9A2@smtp.pobox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: content-driven NoSQL SOAP over XMPP deep-learning software 
Subject: Re: [9front] displayport thinkpad x230 external monitor black screen
Reply-To: 9front@9front.org
Precedence: bulk

On Thu Mar 30 19:37:16 +0200 2023, unobe@cpan.org wrote:
> I have a TP x230 that has a displayport and vga socket.  I have an
> adapter from vga-to-hdmi (wиth а USB dongle for power) that works with
> an ultrawide LG, but the largest mode via VGA is 1920x1080.  Using the
> displayport to connect to the monitor shows a 2560x1080 mode, along
> with the same modes that are shown with the VGA adapter.  However,
> when trying to use any mode with the displayport directly, I just get
> a black screen.

Displayport not working is unfortunately a frequent issue for
sandybridge (x220) and above, possibly even from earlier generations.
I don't know what the issue is, it could be a lot of things, but
checking for a regression is a very good idea.  iirc x230 is among the
first models that were worked on.

> I reviewed the log for changes to igfx to see if I could pin down the commit
> that might be related, and the best I could come up with is 
>   6f63752d84254b470322fc028dce1c79f7443e3b
> back in May 2017 (almost 6 years ago). I reverted
> /sys/src/9/pc/vgaigfx.c to that commit to see
> if it would build, but unsurprisingly, it does not:
> 
> vgaigfx.c:18 structure not fully declared Pcidev
> vgaigfx.c:68 structure not fully declared Pcidev
> warning: vgaigfx.c:61 used and not set: gtt 
> vgaigfx.c:92 structure not fully declared Pcidev
> vgaigfx.c:92 structure not fully declared Pcidev
> vgaigfx.c:95 structure not fully declared Pcidev
> vgaigfx.c:95 structure not fully declared Pcidev
> vgaigfx.c:161 structure not fully declared Pcidev
> vgaigfx.c:214 name not declared: arrow

You won't get far by reverting just this one file, a lot of
system-wide changes have happened since; you'll have to also revert
the rest of the changes elsewhere.  I'd also go earlier and revert to
21570a47195d90b1dc2a3634d8042929543599d3.  Perhaps just use a separate
tree or something.

Hope this helps,
qwx