Monitor posts 'Input not supported' [SOLVED]

seth · 2024-01-04 09:58:57

"Xorg.n.log has no file or directory" has no file or directory *where*

ls /var/log/X*

@d.Alt, if the OP doesn't have xf86-video-vesa that's not gonna result in any "safe" graphics and I'm not sure KDE would work w/ the vesa graphics anyway.

Confused_Words · 2024-01-04 10:27:12

d.ALT wrote:

Please, in order to gather decent formatted outputs, reboot once into safe

I don't know how to let you see all of the Ispci -k command
I think it might actually go above the point I can see as well
because the top result is 00:14.0

the next command

cat /par/cmdline

BOOT_IMAGE=/boot/vmlinuz-linuz-lts root=/dev/mapper/volgroup0-lv_root rw loglevel=3 quiet

I thought cmdline was the command line
not sure how to boot into safe graphics
I don't see it on the grub menu

I wrote vga=771 and nomodest
in the grub edit thing

ls -aI ~/.local/share/

the first listing command does show my home menu

ls -aI ~/.config/

I'm guessing the next on is to go into the config

they both show the same thing

but this is where all my dolphin, steam, config, downloads and bash_logout/profiles/history and cache is

ls -aIR /etc/X11/

the next listing shows
a . a space then . .
xinit
xorg.conf.d

it said it couldn't find a nomodest command

cat /etc/mkinitcpio.conf

this has a lot
I can see Binary
Files
Hooks
Compression
Compression_options
Modules_decompress

# dmesg

dmesg: read kernel buffer failed: Operation not permitted

Confused_Words · 2024-01-04 10:29:30

seth wrote:

"Xorg.n.log has no file or directory" has no file or directory *where*
ls /var/log/X*

/var/log/Xorg.0.log
/var/log/Xorg.0.log.old

seth · 2024-01-04 10:44:54

There's your xorg log, FFS, post that.

Confused_Words · 2024-01-04 10:55:56

seth wrote:

There's your xorg log, FFS, post that.

how do I post this?

I tried to do

/var/log/Xorg.0.log | curl -F 'file=@-' 0x0.st

but it said permission denied
451 Unavailable for legal reasons

this thing is pretty long
so I can't just copy and paste it

seth · 2024-01-04 11:02:37

cat /var/log/Xorg.0.log | curl -F 'file=@-' 0x0.st

In case you've not understood that yourself by now, you're in no way shape or form able to run this system.

Confused_Words · 2024-01-04 11:06:57

seth wrote:

cat /var/log/Xorg.0.log | curl -F 'file=@-' 0x0.st

.

ah I had to use cat as well
curl is reading it right then I say the name

anyway it gave the link

http://0x0.st/H6VV.txt

seth · 2024-01-04 11:18:46

DISPLAY=:0 xrandr --output HDMI-1 --auto

Gets you a crtc config error?
What about any of

DISPLAY=:0 xrandr --output HDMI-1 --mode 0x48
DISPLAY=:0 xrandr --output HDMI-1 --mode 0x49
DISPLAY=:0 xrandr --output HDMI-1 --mode 0x4a
DISPLAY=:0 xrandr --output HDMI-1 --mode 0x4b
DISPLAY=:0 xrandr --output HDMI-1 --mode 0x4c
DISPLAY=:0 xrandr --output HDMI-1 --mode 0x4d

0x48 is actually the preferred mode and in case you've not yet figured, you can press the "up" key and edit the previous command instead of re-typing it again.

Confused_Words · 2024-01-04 11:22:42

seth wrote:

0x48 is actually the preferred mode and in case you've not yet figured, you can press the "up" key and edit the previous command instead of re-typing it again.

Yeah I already figured that one out
I think rebooting it might have put me back or something
because it shows

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

for all of those things

seth · 2024-01-04 11:23:43

Yes. You'll have to re-import the XAUTHORITY environment first.

Confused_Words · 2024-01-04 11:29:18

seth wrote:

Yes. You'll have to re-import the XAUTHORITY environment first.

why isn't pgrep kwin giving me any results
is it the same key?

I tried the same export but doesn't seem to have worked

it changed the auto to

Authorization required, but no authorization protocol specified

Can't open display :0

Last edited by Confused_Words (2024-01-04 11:32:26)

seth · 2024-01-04 11:31:42

Are you logged into a session w/ no output?

Confused_Words · 2024-01-04 11:34:24

seth wrote:

Are you logged into a session w/ no output?

I'm not quite sure
I think the file I sent didn't

wait what

I switched to tty2 and the GUI booted ??????

but what changed ???????

let me try restarting my system to see if it's permanent or not

oh wow it's still working
I guess the auto thing for some reason needed me to switch back to tty2 to start working again

But thanks man
Really helped me out
Like I'm a pretty clueless guy so thanks for putting up with me

Do I just change the title to and add a [Solved]
Or is there a tab I'm supposed to add it to ?

wait I think I did it

anyway thanks again
I really appreciate it

Last edited by Confused_Words (2024-01-04 11:53:37)

seth · 2024-01-04 15:55:05

but what changed ???????

Most likely that you deleted the kscreen config - and fudged the subsequent test (by not rebooting or so?)

Confused_Words · 2024-01-05 11:23:43

seth wrote:

Most likely that you deleted the kscreen config - and fudged the subsequent test (by not rebooting or so?)

This is very strange
I thought the issue was fixed so I tried TF2 again but then the same thing happened
so I followed this thread to fix it
but for some reason it didn't work
so I did all the steps again paying attention to when I said I rebooted and apparently that had an impact on it

I guess I'll stay clear of that game for now on

Arch Linux

#51 2024-01-04 09:58:57

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

#52 2024-01-04 10:27:12

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

#53 2024-01-04 10:29:30

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

#54 2024-01-04 10:44:54

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

#55 2024-01-04 10:55:56

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

#56 2024-01-04 11:02:37

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

#57 2024-01-04 11:06:57

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

#58 2024-01-04 11:18:46

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

#59 2024-01-04 11:22:42

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

#60 2024-01-04 11:23:43

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

#61 2024-01-04 11:29:18

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

#62 2024-01-04 11:31:42

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

#63 2024-01-04 11:34:24

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

#64 2024-01-04 15:55:05

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

#65 2024-01-05 11:23:43

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

Board footer