9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] displayport thinkpad x230 external monitor black screen
Date: Thu, 30 Mar 2023 13:47:04 -0400	[thread overview]
Message-ID: <4981F09E-D6AD-4E0D-96DF-43FEEEC7C10B@stanleylieber.com> (raw)
In-Reply-To: <77E481DAE27DCF5720BE14B37790E9A2@smtp.pobox.com>

On March 30, 2023 1:37:57 PM EDT, Romano <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.  I ran 'cat /dev/vgactl' "blind", when using the
>ultrawide LG external monitor to see if that yielded anything
>interesting, but didn't see it.  I then switched back to built-in LCD
>screen to capture the rc output, which I've attached to the end of this
>message.
>
>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
>
>Before go any further, I thought I'd ask on the list: has anyone had
>something similar happen, or know of where the problem might be?
>
># --- rc output when connecting to external monitor ---
>cpu% whatis modes
>fn modes {
>	@ {
>		rfork n; aux/realemu; aux/vga -m igfx -p
>	}
>}
>cpu% modes
>...
>edid mfr            LGD
>edid serialstr      
>edid name           
>edid product        728
>edid serial         0
>edid version        1.3
>edid mfrdate        2012.0
>edid size (cm)      28x16
>edid gamma          2.20
>edid vert (Hz)      0-0
>edid horz (Hz)      0-0
>edid pclkmax        0
>edid flags           digital standby suspend activeoff
>edid 1366x768@60Hz  
>		clock=75.2
>		shb=1414 ehb=1478 ht=1582
>		vrs=772 vre=779 vt=792
>		hsync=+ vsync=- 
>edid mfr            GSM
>edid serialstr      
>edid name           LG ULTRAWIDE
>edid product        23026
>edid serial         256914
>edid version        1.4
>edid mfrdate        2021.6
>edid size (cm)      80x34
>edid gamma          2.20
>edid vert (Hz)      56-75
>edid horz (Hz)      30000-90000
>edid pclkmax        240000000
>edid flags           digital standby
>edid 2560x1080@60Hz 
>		clock=185.58
>		shb=2624 ehb=2688 ht=2784
>		vrs=1083 vre=1093 vt=1111
>		hsync=- vsync=- 
>edid 1920x1080@60Hz 
>		clock=148.5
>		shb=2008 ehb=2052 ht=2200
>		vrs=1084 vre=1089 vt=1125
>		hsync=+ vsync=- 
>edid 640x480@60Hz   
>		clock=25.175
>		shb=656 ehb=752 ht=800
>		vrs=490 vre=492 vt=525
>		hsync=- vsync=- 
>edid 640x480@75Hz   
>		clock=31.5
>		shb=656 ehb=720 ht=840
>		vrs=481 vre=484 vt=500
>		hsync=- vsync=- 
>edid 800x600@60Hz   
>		clock=40
>		shb=840 ehb=968 ht=1056
>		vrs=601 vre=605 vt=628
>		hsync=+ vsync=+ 
>edid 800x600@75Hz   
>		clock=49.5
>		shb=816 ehb=896 ht=1056
>		vrs=601 vre=604 vt=625
>		hsync=+ vsync=+ 
>edid 1024x768@60Hz  
>		clock=65
>		shb=1048 ehb=1184 ht=1344
>		vrs=771 vre=777 vt=806
>		hsync=- vsync=- 
>edid 1024x768@75Hz  
>		clock=78.75
>		shb=1040 ehb=1136 ht=1312
>		vrs=769 vre=772 vt=800
>		hsync=+ vsync=+ 
>edid 1280x1024@75Hz 
>		clock=135
>		shb=1296 ehb=1440 ht=1688
>		vrs=1025 vre=1028 vt=1066
>		hsync=+ vsync=+ 
>cpu% whatis lcd
>fn lcd {
>	@ {
>		rfork n; aux/realemu; aux/vga -m igfx -l 1366x768
>	}
>}
>cpu% whatis lg
>fn lg {
>	@ {
>		rfork n; aux/realemu; aux/vga -m igfx -l 1920x1080
>	}
>}
>cpu% cat /dev/vgactl
>type igfx
>size 1376x768x32 x8r8g8b8
>actualsize 1366x768
>tilt none
>hwgc igfxhwgc
>hwaccel off
>hwblank on
>addr p 0xe0000000 v 0xfffffe80e0000000 size 0x4000000
>softscreen on
>cpu% lg
>cpu% cat /dev/vgactl
>type igfx
>size 1920x1080x32 x8r8g8b8
>tilt none
>hwgc igfxhwgc
>hwaccel off
>hwblank on
>addr p 0xe0000000 v 0xfffffe80e0000000 size 0x4000000
>softscreen on
>cpu% lcd
>cpu%
>
>

i do not have direct experience with the x230 vs displayport, but with my x301 vs displayport i needed to use an "active" adapter. this was years ago and i no longer have the hardware, but this might be a place to start.

sl

  reply	other threads:[~2023-03-30 17:48 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 [this message]
2023-04-03 22:27 ` qwx
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=4981F09E-D6AD-4E0D-96DF-43FEEEC7C10B@stanleylieber.com \
    --to=sl@stanleylieber.com \
    --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).