You are not logged in.
Hi,
My LG monitor does not display any output when connected on an X server or the tty.
In X.org, the monitor automatically comes as disabled when I login to Xfce, however, on the tty, the monitor does turn on, but shows a blank screen instead of the tty text. The monitor does work in (KDE) Wayland with no issues.
Also, I have noticed that after doing a system upgrade, the monitor started to show a blank screen on the tty as mentioned before, instead of just not powering on. Maybe a kernel / firmware upgrade caused this effect?
Things I have tried:
- Starting 'amdgpu' module early using kernel mode setting.
- Read EDID using 'read-edid' package, to try and figure out what's wrong.
Any help would be appreciated.
Offline
Please post an xorg log, https://wiki.archlinux.org/title/Xorg#General
Offline
Xorg.0.log
Xorg.0.log.old
Last edited by Pobodoo (2022-05-22 10:33:21)
Offline
Why are there no timestamps in the logs?
The .old log aborted from the fbdev driver, probably because the GPUs aren't initialized, https://wiki.archlinux.org/title/Kernel … _KMS_start
The xorg.0.log has
[ 8.168] (II) AMDGPU(G0): Monitor name: LG ULTRAGEAR
The output is attached to the second GPU, https://wiki.archlinux.org/title/PRIME#Reverse_PRIME
Offline
Why are there no timestamps in the logs?
I removed them when I was removing my hostname, because I thought it would be sensitive data?
You were right about it being plugged in to the discrete GPU on my laptop. Is there any reason why it only renders displays plugged into the primary GPU of the system in the tty / X.org? It works on Wayland just fine, so I was wondering what the issue was.
Offline
The monitor also still does not work on tty, but works on X.org now, when plugged in to the primary GPU. I've enable early KMS for the 'amdgpu' module, to no avail.
In the tty, the monitor resolution is detected by neofetch (2560 x 1440); I can tell because the font looks stretched on my primary laptop display (1920 x 1080). A blank screen is still shown on the monitor, however.
Offline
my hostname, because I thought it would be sensitive data?
"Embarrassing" at max, but removing the timestamps took the log out of context (they could be dated and therefore irrelevant) - don't do that.
If you feel like you've to obfuscate data (maybe don't name your host "idreamofkirbyeverynight"…) keep that to a minimum and make it obvious ("<myembarrassinghostnme>")
The link in #4 shows how to access outputs on the secondary GPU, you can activate and configure outputs on the TTY following https://raw.githubusercontent.com/torva … modedb.rst
Offline
"Embarrassing" at max,
Lol, yeah. Rest assured, I don't dream of Kirby every night...
you can activate and configure outputs on the TTY following
I have tried this method now, to no avail. The parameter I've been using is 'video={name of display}:2560x1440@165e', which hasn't worked. I even tried disabling the internal laptop display, but the external monitor is still left blank on the tty. I also tried taking the EDID file from '/sys/class/drm' to '/usr/lib/firmware' (as stated on the link you sent above) and loading it in early KMS, but that also didn't work.
Is there just something wrong with this monitor's framebuffer driver which is making it not work, or is it something else?
Offline
I've been using is 'video={name of display}:2560x1440@165e'
LITERALLY? "{name of display}" is wrong for sure.
Is there just something wrong with this monitor's framebuffer driver which is making it not work, or is it something else?
That's not a thing. Please post the system journal for the boot where you attempted the video parameter, an updated Xorg log, the output of "xrandr -q" and try to enable the output at a VESA timing (eg. "1024x768@60e")
Offline
LITERALLY? "{name of display}" is wrong for sure.
I replaced name of display with 'DP-1' or 'DP-2'.
Attempt at enabling VESA timing failed.
Please post the system journal for the boot where you attempted the video parameter
Last edited by Pobodoo (2022-05-22 10:34:06)
Offline
May 19 22:34:41 Sora kernel: [drm] forcing DP-2 connector on
But the output name is (likely) "DisplayPort-1-1" , check "ls /sys/class/drm/card*"
Sidebar:
#11 0x00007f954d7a7366 __assert_fail (libc.so.6 + 0x37366)
#12 0x000055ff1a7bbe59 n/a (Xorg + 0x9be59)
#13 0x00007f95408ee8cf glamor_init (libglamoregl.so + 0xd8cf)
#14 0x00007f954ca80261 n/a (modesetting_drv.so + 0xf261)
https://wiki.archlinux.org/title/Kernel … _KMS_start
Or, for lightdm you can also use
https://wiki.archlinux.org/title/LightD … TTY_output
Offline
Output of 'ls /sys/class/drm':
card0
card0-DP-1
card0-DP-2
card0-eDP-1
card0-HDMI-A-1
card1
card1-eDP-2
renderD128
renderD129
version
I think the monitor is named 'DP-2', because there were only two monitors enabled. The other one being 'eDP-2'. I've also previously tried 'DP-1', to no avail.
The monitor works in X.org, by the way, but just not in the tty. Is the tty run in an X server, or is it a framebuffer, because I'm confused as to why the X.org logs will help with the tty?
Offline
The xorg log is just a convenient way to get an oversight of the setup (though the amdgpu driver indeed relables the outputs and "DP-2" is correct)
Did you enable early kms?
This is the "wrong" card:
May 19 22:34:40 Sora kernel: amdgpu 0000:03:00.0: amdgpu: SMU is initialized successfully!
May 19 22:34:40 Sora kernel: [drm] Display Core initialized with v3.2.167!
May 19 22:34:40 Sora kernel: [drm] DMUB hardware initialized: version=0x0202000C
May 19 22:34:41 Sora kernel: [drm:dce110_edp_wait_for_hpd_ready [amdgpu]] *ERROR* dce110_edp_wait_for_hpd_ready: wait timed out!
May 19 22:34:41 Sora kernel: snd_hda_intel 0000:03:00.1: bound 0000:03:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
May 19 22:34:41 Sora kernel: [drm:dce110_edp_wait_for_hpd_ready [amdgpu]] *ERROR* dce110_edp_wait_for_hpd_ready: wait timed out!
May 19 22:34:41 Sora kernel: [drm:dce110_edp_wait_for_hpd_ready [amdgpu]] *ERROR* dce110_edp_wait_for_hpd_ready: wait timed out!
May 19 22:34:41 Sora kernel: [drm] forcing DP-2 connector on
And this one shows up *very* late
May 19 22:34:43 Sora kernel: [drm] Initialized amdgpu 3.44.0 20150101 for 0000:07:00.0 on minor 1
May 19 22:34:43 Sora kernel: fbcon: amdgpudrmfb (fb0) is primary device
Enable early KMS, disable the graphical.target and if that still doesn't get you the console output on the external screen, try to map fb0 to TTY1, https://raw.githubusercontent.com/torva … /fbcon.rst ("fbcon=map", https://aur.archlinux.org/packages/con2fbmap )
Offline
Sadly, none of the solutions worked, even with early KMS. I think I'm just gonna abandon trying to fix my monitor on tty, because it seems like either the tty does not like high resolutions, my configuration, or it just straight up is finicky with my particular monitor.
From what I've seen online, it seems other people also experience this and haven't found solutions. Maybe it will be fixed someday.
Offline
Sadly, none of the solutions worked, even with early KMS. I think I'm just gonna abandon trying to fix my monitor on tty, because it seems like either the tty does not like high resolutions, my configuration, or it just straight up is finicky with my particular monitor.
From what I've seen online, it seems other people also experience this and haven't found solutions. Maybe it will be fixed someday.
Just fixed it now! It seems adding the 'fbcon=map:1' kernel parameter set it so that it could display the tty on the second monitor! I still wish my BIOS had an option to use the second monitor as primary display by default. It would have fixed the problem a lot sooner.
Thanks for the help, though!
Offline
That would suggest the console is (still) run by the chip on 0000:03:00.0 ?
Offline
run by the chip on 0000:03:00.0 ?
What do you mean by this? Do you mean the integrated / discrete GPUs, or something else?
Offline
Check "lspic", but it's not the GPU the X11 server is running on.
Offline