Monitor posts 'Input not supported' [SOLVED]

Confused_Words · 2024-01-03 09:52:06

I was trying to play some TF2 on steam
then my monitor turned black and only displayed Input not supported
with the power button on my monitor flashing
(I only have 1 monitor)

I can use Ctrl + Alt F1-F4
to get to the tty screens

but if I switch back to the one with my GUI (KDE Plasma)
it returns the same message

I tried to use xrandr on the tty screen
but that only states Can't open display

I have tried rebooting my system
but after I get past the login screen

I can sometimes see my programs opening up from the previous session (for a couple second) or it sometimes skips that part
and goes straight back to the same screen

I'm not really sure how I'm meant to fix this

Last edited by Confused_Words (2024-01-04 11:50:18)

d.ALT · 2024-01-03 10:06:38

Please give us some more infos:

# lspci -nn

$ steam &> instance_steam.log

(paste online the content of instance_steam.log)

$ pacman -Qs mesa

Head_on_a_Stick · 2024-01-03 11:00:48

Confused_Words wrote:

I tried to use xrandr on the tty screen
but that only states Can't open display

Try

DISPLAY=:0 xrandr

EDIT: or other numbers for DISPLAY, if you can use TTY1 then the graphical desktop won't be on "0". Is this with a display manager?

Last edited by Head_on_a_Stick (2024-01-03 11:02:09)

Confused_Words · 2024-01-03 11:15:35

d.ALT wrote:

Please give us some more infos:
# lspci -nn
$ steam &> instance_steam.log
(paste online the content of instance_steam.log)
$ pacman -Qs mesa

Ispci -nn

gives

00:00.0 Host bridge [0600]: Advance Micro Devices, Inc. [AMD] Starship/Matisse Root Complex [1022:1480]
00:00.2 IOMMU [0806]: Advance Micro Devices, Inc. [AMD] Starship/Matisse IOMUU [1022:1481]
00:01.0 Host Bridge [0600]: Advance Micro devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
00:01.2 PCI bridge [0604]: Advance Micro devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483]
0:02.0 Host Bridge [0600]: Advance Micro devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
0:03.0 Host Bridge [0600]: Advance Micro devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
0:03.1 PCI bridge [0604]: Advance Micro devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1482]
0:04.0 Host Bridge [0600]: Advance Micro devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
0:05.0 Host Bridge [0600]: Advance Micro devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
0:07.0 Host Bridge [0600]: Advance Micro devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
0:07.1 PCI bridge [0604]: Advance Micro devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484]
0:08.0 Host Bridge [0600]: Advance Micro devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482]
0:08.1  PCI bridge [0604]: Advance Micro devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484]
0:14.0 SMBus [0c05] : Advance Micro devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61)
0:14.3 ISA bridge [0601]: Advance Micro devices, Inc.[AMD] FCH LPC Bridge [1022:790e] (rev 51)
0:18.0 Host Bridge [0600]: Advance Micro devices, Inc. [AMD] Matisse/Vermeer Data Fabric Device 18th; Function 0 [1022:1440]
0:18.1 Host Bridge [0600]: Advance Micro devices, Inc. [AMD] Matisse/Vermeer Data Fabric Device 18th; Function 1 [1022:1441]
0:18.2 Host Bridge [0600]: Advance Micro devices, Inc. [AMD] Matisse/Vermeer Data Fabric Device 18th; Function 2 [1022:1442]
0:18.3 Host Bridge [0600]: Advance Micro devices, Inc. [AMD] Matisse/Vermeer Data Fabric Device 18th; Function 3 [1022:1443]
0:18.4 Host Bridge [0600]: Advance Micro devices, Inc. [AMD] Matisse/Vermeer Data Fabric Device 18th; Function 4 [1022:1444]
0:18.5 Host Bridge [0600]: Advance Micro devices, Inc. [AMD] Matisse/Vermeer Data Fabric Device 18th; Function 5 [1022:1445]
0:18.6 Host Bridge [0600]: Advance Micro devices, Inc. [AMD] Matisse/Vermeer Data Fabric Device 18th; Function 6 [1022:1446]
0:18.7 Host Bridge [0600]: Advance Micro devices, Inc. [AMD] Matisse/Vermeer Data Fabric Device 18th; Function 7 [1022:1447]

Then it just seems to be my usbs and network and audio takes a while to write it out so I'll omit that since it probably isn't relevant

$ steam &> instance_steam.log

running on arch rolling 64-bit 
steam_runtime is enabled automatically 
steam runtime environment is up to date 

01/03 10:55:09 Int:Installing breakpad exception handler for appid(steam)/version(1702079146)/tid(3728)
scr/steamexe/updateeui_xwin.cpp (339) : Could not open connection to X
01/03 10:55:09 Int:Installing breakpad exception handler for appid(steam)/version(1702079146)/tid(3728)

(zenity:3730): GTA-Warning **: [color=blue]14:06:44.791[/color] : cannot open display:
assert_20240103105509_4.dmp[3733]: Uploading dump (out-of-process)
/tmp/dumps/assert_20240103105509_4.dmp
src/steamexe/maim.cpp (1223) : failed to initialize update status ui, or create initial window 

assert_20240103105509_4.dmp[3733]: Finished uploading minidump (out-of-process): success = yes
assert_20240103105509_4.dmp[3733]: response: CrashID=bp-399b8544-635-4b1a-b394-57b62240103
assert_20240103105509_4.dmp[3733]: file ' ' /tmp/dumps/assert_20240103105509_4.dmp' ' , upload yes: ' ' CrashID=bp-39b8544-6536-4b1a-b394-57b6d2240103

nothing else is after this but
had to Ctrl + C to get back to the command prompt

pacman -Qs mesa

local/glu 9.0.3-1
      Mesa OpenGl utility library 
local/lib32-mesa 1:23.1.7-1
      An open source implementation of the OpenGl specification (32-bit)
local/mesa 1:23.3.2-2
       An open source implementation of the OpenGl Specification
local/mesa-utils 9.0.0-2
       Essential Mesa Utilities 
local/vulkan-radeon 1:23.3.2-2
       Radeon's Vulkan mesa driver

wait I did steam $> instance_steam.log
by accident

steam & doesn't post anything
after I write that line
so I don't know what to do after that

Last edited by Confused_Words (2024-01-03 14:32:06)

Confused_Words · 2024-01-03 11:17:28

Head_on_a_Stick wrote:

Confused_Words wrote:
I tried to use xrandr on the tty screen
but that only states Can't open display
Try
DISPLAY=:0 xrandr
EDIT: or other numbers for DISPLAY, if you can use TTY1 then the graphical desktop won't be on "0". Is this with a display manager?

This just gives me a

Can't open display: (1-5)

depending on which number I put

Head_on_a_Stick · 2024-01-03 11:54:47

Did you try 7? I think that's what SDDM uses for the desktop. If you had answered my other question I could offer better advice.

Confused_Words · 2024-01-03 12:14:50

Head_on_a_Stick wrote:

Did you try 7? I think that's what SDDM uses for the desktop. If you had answered my other question I could offer better advice.

I guess the display manager would be the tty2 screen since that's the login and then that goes to my graphical environment

the tty1 screen
seems to be for the booting in process
and I can't type anything inside of it

display 7 didn't yield any different result
same with 6, 8, 9 and 10

seth · 2024-01-03 13:53:19

1. Please use [code][/code] tags. Edit your post #4 in this regard.
2. Running steam etc. w/o a display server is gonna fail
3. "my GUI (KDE Plasma)" : https://wiki.archlinux.org/title/KDE#Un … lution_set
4. "Can't open display: (1-5)" is certainly false, at least SDDM will run on :0, this is completely unrelated to the TTY, GDM starts a second X11 server, but that's very GDM specific
5. please don't stray random newlines into your post

Confused_Words · 2024-01-03 14:22:24

seth wrote:

1. Please use [code][/code] tags. Edit your post #4 in this regard.
2. Running steam etc. w/o a display server is gonna fail
3. "my GUI (KDE Plasma)" : https://wiki.archlinux.org/title/KDE#Un … lution_set
4. "Can't open display: (1-5)" is certainly false, at least SDDM will run on :0, this is completely unrelated to the TTY, GDM starts a second X11 server, but that's very GDM specific
5. please don't stray random newlines into your post

hopefully the quote tags help
don't know what other tags it would need
other than that one bit of blue text

ahh I didn't even see the invalid prompt when I did it for zero I must have overlooked it by mistake it says

Invalid MIT-MAGIC-COOKIE-1 key
Can't open display :0

did I cut off some lines???
I don't really know which one those are
it's hard to tell with my phone

I'll read that article and
try to look up how to open files in tty

seth · 2024-01-03 14:25:50

*code* tags and no, you're just randomly hitting the enter key (most likely because of your phone)
SDDM exports the XAUTHORITY to a random position - did you check the link that tells you how to get rid of bogus ksreen settings?

Confused_Words · 2024-01-03 14:37:02

seth wrote:

*code* tags and no, you're just randomly hitting the enter key (most likely because of your phone)
SDDM exports the XAUTHORITY to a random position - did you check the link that tells you how to get rid of bogus ksreen settings?

I changed my quote to the code thing

I also CD into it but still not sure how to read the files

it says a string on units and then the output I can also CD into

the first string is

55047dfe3791849804ecb78ad82cf27d

CD of outputs

has a listing string of

2091265d3c8cd2a7548925eac7ded211

I can't use nano here so I'm not sure how I'm meant to
look at the output file

Confused_Words · 2024-01-03 14:37:34

Confused_Words wrote:

seth wrote:
*code* tags and no, you're just randomly hitting the enter key (most likely because of your phone)
SDDM exports the XAUTHORITY to a random position - did you check the link that tells you how to get rid of bogus ksreen settings?
I changed my quote to the code thing
I also CD into it but still not sure how to read the files
it says a string on units and then the output I can also CD into outputs
the first string is
55047dfe3791849804ecb78ad82cf27d
CD of outputs
has a listing string of
2091265d3c8cd2a7548925eac7ded211
I can't use nano here so I'm not sure how I'm meant to
look at the output file
wait I can use nano on that string
it says
{
"id": "2091265d3c8cd2a7548925eac7ded211",
"metadata": {
"fullname": "xrandr-Lenovo Group Limited-C22-25-U7615MRKX",
"name": "HDMI-1"
},
"mode":{
"refresh": 59.953335388183594,
"size":{
"height":576,
"width":1024
}
},
"overscan": 0,
"rgbrange": 0,
"rotation" :1,
"scale": 1,
"vrrpolicy":2
}

Last edited by Confused_Words (2024-01-03 14:48:06)

seth · 2024-01-03 14:42:39

Just delete all files in ~/.local/share/kscreen/

Confused_Words · 2024-01-03 14:49:39

seth wrote:

Just delete all files in ~/.local/share/kscreen/

with pacman -r then the path?

d.ALT · 2024-01-03 14:54:12

Confused_Words wrote:

seth wrote:
Just delete all files in ~/.local/share/kscreen/
with pacman -r then the path?

(? Why you should want do that?) No, just use:

$ cp -arv ~/.local/share/kscreen/ ~/.local/share/bkp__kscreen/
$ rm ~/.local/share/kscreen/*

Confused_Words · 2024-01-03 15:00:54

d.ALT wrote:

Confused_Words wrote:
seth wrote:
Just delete all files in ~/.local/share/kscreen/
with pacman -r then the path?
(? Why you should want do that?) No, just use:
$ cp -arv ~/.local/share/kscreen/ ~/.local/share/bkp__kscreen/
$ rm ~/.local/share/kscreen/*

the first thing worked

but the second line said it can't remove
because it's a directory

seth · 2024-01-03 15:04:24

"rm -rf", how the fuck did you install archlinux?

Confused_Words · 2024-01-03 15:07:27

seth wrote:

"rm -rf", how the fuck did you install archlinux?

oh yeah that worked
so I just reboot now right
and it should default to the right resolution ?

seth · 2024-01-03 15:08:51

You don't have to reboot, you can just login.
If kscreen was the cause, the outputs will work.

d.ALT · 2024-01-03 15:13:15

Confused_Words wrote:

d.ALT wrote:
Confused_Words wrote:
with pacman -r then the path?
(? Why you should want do that?) No, just use:
$ cp -arv ~/.local/share/kscreen/ ~/.local/share/bkp__kscreen/
$ rm ~/.local/share/kscreen/*
the first thing worked
but the second line said it can't remove
because it's a directory

? ...

~/.local/share/kscreen != ~/.local/share/kscreen/*

Aren't there files only beneath kscreen/?

Last edited by d.ALT (2024-01-03 15:14:25)

Confused_Words · 2024-01-03 15:13:56

seth wrote:

You don't have to reboot, you can just login.
If kscreen was the cause, the outputs will work.

It still says input not supported even after I rebooted

Confused_Words · 2024-01-03 15:15:27

d.ALT wrote:

Confused_Words wrote:
d.ALT wrote:
(? Why you should want do that?) No, just use:
$ cp -arv ~/.local/share/kscreen/ ~/.local/share/bkp__kscreen/
$ rm ~/.local/share/kscreen/*
the first thing worked
but the second line said it can't remove
because it's a directory
? ...
~/.local/share/kscreen != ~/.local/share/kscreen/*
Aren't there files only beneath kscreen/?

both of those do not exist
no file or directory

seth · 2024-01-03 15:19:59

Because you just deleted them
Stop full quoting, you're bloating the thread.

You do still get a GUI login screen?
Login, switch to tty3 (any console will do), login there, query the PID of kwin

pgrep kwin

Use that to get the XAUTHORITY environment

tr '\0' '\n' < /proc/$(pgrep kwin)/environ

export that in the current shell, query xrandr again.

Confused_Words · 2024-01-03 15:30:48

seth wrote:

Because you just deleted them
Stop full quoting, you're bloating the thread.

the pgrep kwin
gave me the

XAUTHORITY - /tmp/xauth_KNtzrQ

but posting the next line just gave me the same results as the pgrep kwin

I don't know what you mean by extort that either ?

seth · 2024-01-03 15:34:24

"export", literally.

export XAUTHORITY=/tmp/xauth_KNtzrQ # you cannot typo any of this!

pgrep would give you a number.

seth wrote:

how the fuck did you install archlinux?

Arch Linux

#1 2024-01-03 09:52:06

Monitor posts 'Input not supported' [SOLVED]

#2 2024-01-03 10:06:38

Re: Monitor posts 'Input not supported' [SOLVED]

#3 2024-01-03 11:00:48

Re: Monitor posts 'Input not supported' [SOLVED]

#4 2024-01-03 11:15:35

Re: Monitor posts 'Input not supported' [SOLVED]

#5 2024-01-03 11:17:28

Re: Monitor posts 'Input not supported' [SOLVED]

#6 2024-01-03 11:54:47

Re: Monitor posts 'Input not supported' [SOLVED]

#7 2024-01-03 12:14:50

Re: Monitor posts 'Input not supported' [SOLVED]

#8 2024-01-03 13:53:19

Re: Monitor posts 'Input not supported' [SOLVED]

#9 2024-01-03 14:22:24

Re: Monitor posts 'Input not supported' [SOLVED]

#10 2024-01-03 14:25:50

Re: Monitor posts 'Input not supported' [SOLVED]

#11 2024-01-03 14:37:02

Re: Monitor posts 'Input not supported' [SOLVED]

#12 2024-01-03 14:37:34

Re: Monitor posts 'Input not supported' [SOLVED]

#13 2024-01-03 14:42:39

Re: Monitor posts 'Input not supported' [SOLVED]

#14 2024-01-03 14:49:39

Re: Monitor posts 'Input not supported' [SOLVED]

#15 2024-01-03 14:54:12

Re: Monitor posts 'Input not supported' [SOLVED]

#16 2024-01-03 15:00:54

Re: Monitor posts 'Input not supported' [SOLVED]

#17 2024-01-03 15:04:24

Re: Monitor posts 'Input not supported' [SOLVED]

#18 2024-01-03 15:07:27

Re: Monitor posts 'Input not supported' [SOLVED]

#19 2024-01-03 15:08:51

Re: Monitor posts 'Input not supported' [SOLVED]

#20 2024-01-03 15:13:15

Re: Monitor posts 'Input not supported' [SOLVED]

#21 2024-01-03 15:13:56

Re: Monitor posts 'Input not supported' [SOLVED]

#22 2024-01-03 15:15:27

Re: Monitor posts 'Input not supported' [SOLVED]

#23 2024-01-03 15:19:59

Re: Monitor posts 'Input not supported' [SOLVED]

#24 2024-01-03 15:30:48

Re: Monitor posts 'Input not supported' [SOLVED]

#25 2024-01-03 15:34:24

Re: Monitor posts 'Input not supported' [SOLVED]

Board footer