From: qwx@sciops.net
To: 9front@9front.org
Subject: Re: [9front] displayport thinkpad x230 external monitor black screen
Date: Tue, 04 Apr 2023 00:27:09 +0200 [thread overview]
Message-ID: <7439E8B219466B30F6E6BB8B134493D2@wopr.sciops.net> (raw)
In-Reply-To: <77E481DAE27DCF5720BE14B37790E9A2@smtp.pobox.com>
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
next prev parent reply other threads:[~2023-04-03 22:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 17:37 Romano
2023-03-30 17:47 ` Stanley Lieber
2023-04-03 22:27 ` qwx [this message]
2023-04-04 22:39 ` igor
2023-04-04 22:43 ` sl
2023-04-05 7:01 ` qwx
2023-04-09 6:59 ` unobe
2023-04-09 21:26 qwx
2023-04-09 22:42 ` sirjofri
2023-04-11 21:33 ` Steve Simon
2023-04-12 22:13 ` unobe
2023-04-11 21:32 ` Roberto E. Vargas Caballero
2023-04-17 7:53 ` qwx
2023-04-19 20:50 ` unobe
2023-04-20 23:40 ` qwx
2023-04-24 18:52 ` qwx
2023-04-26 3:32 ` unobe
2023-04-30 3:12 ` qwx
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7439E8B219466B30F6E6BB8B134493D2@wopr.sciops.net \
--to=qwx@sciops.net \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).