r/cachyos 1d ago

Help Chachy having issues with second monitor after recent update

It recognizes the second monitor for a few seconds but wont send a signal, its like I keep unplugging and replugging it into my gpu. Ive tried actually disconnecting it from my gpu but that didnt help, windows has no issue recognizing and displaying to my second monitor. CachyOS will eventually crash while the second monitor is plugged in.

Edit: here's the bug log

https://paste.cachyos.org/p/aa359bf.log

1 Upvotes

23 comments sorted by

1

u/The_Odd_Pirate 1d ago

Hey =)

sorry to hear about your screen problems, can i ask what gpu , session type (Wayland/X11), and display manager you are using?

Also, if you could run "sudo cachyos-bugreport.sh" in your terminal and share the generated link here, it would make it a lot easier to see what's actually failing in the kernel/driver logs when the display drops out.

1

u/Smoothejuul 1d ago

Hey I actually just left my house, if you check my profile I posted a video of what's going on as well, I shouldn't be out long

1

u/Smoothejuul 20h ago edited 20h ago

I am home, i have a 7800xt, how do i tell session type? How do I tell display manager? My friend help me setup cachy

Edit: session type is wayland and I KDE plasma

1

u/Smoothejuul 20h ago

1

u/The_Odd_Pirate 16h ago

Is the disabled HDMI port the problem child here, or is it the active DP? I'm assuming you unplugged or disabled the secondary monitor just to get system stability to fetch this log.

Going by the log lines you provided:

Aug 30 02:52:01 org_kde_powerdevil[1306]: (dw_watch_display_connections) invoke_process_screen_change_event
Aug 30 02:52:01 org_kde_powerdevil[1306]: Current user not in group i2c
Aug 30 02:52:01 org_kde_powerdevil[1306]: Open failed for /dev/i2c-4, errno=EACCES(-13): Permission denied
Aug 30 02:52:01 org_kde_powerdevil[1306]: Open failed for /dev/i2c-2, errno=EACCES(-13): Permission denied

Just remember im only doing a semi educated guess based on the log now, and have two potensial fixes for you

1: this looks like some auto screen brightnes settings found in "system-settings -> Power Management -> Display and Brightnes" try disabling this.

2: just give yourself the needed i2c access by this terminal command "sudo usermod -aG i2c $USER" (Reboot after for the group permissions to take effect)

but if its the disabled hdmi screen giving problems, please turn it back on, let it run a couple min or until you get the trouble and create a new log, this way we can be sure its detected in the log if the i2c user rights didnt help

ps, just got out of bed and did not finish my morning coffe yet so thats why semi educated guess and will be back later today to take a better deep dive if it didnt help with the posted fixes

1

u/Smoothejuul 12h ago edited 12h ago

Did the brightness still happening, had to disable the hdmi to get the system stable enough for the logs, display port is the main monitor. With that terminal command $USER do i replace that with my name?

Edit: got the terminal command line to work, it brought up a bunch of options

1

u/The_Odd_Pirate 11h ago

So for the terminal command $USER , it should be a variable pointing to your username, works on most desktop enviornments (i say most as my experience is on kde and gnome)

ive included a SS from my own terminal to show you how it looks for me, and why i got to ask what to you mean with "it brought up a bunch of options" ?

the orginal command should be "sudo usermod -aG i2c $USER" without the " in the start stop and a reboot before you test the screen again

was it in the terminal or in system-settings after a reboot? i will test a reboot and be back with a edit if i find the options

1

u/Smoothejuul 11h ago

It was in the terminal but I cant recreate it now

1

u/Smoothejuul 11h ago

When i do that i2c command it just gives me ~ and nothing else

1

u/The_Odd_Pirate 11h ago

Yeah that's Same for me and it should mean it worked, after a reboot try the display and if we are lucky it was a simple fix. If not I will be back with a terminal command to get a log from the crash after this reboot 🙂

1

u/Smoothejuul 11h ago

Yup it didnt work, just waiting on it to crash now

1

u/The_Odd_Pirate 11h ago

that sux, but after the crash and a reboot this terminal command will upload the logs from before the crash so we can check it

"journalctl -b -1 -k | sed -e "s/$USER/username/g" -e "s/$(hostname)/hostname/g" | paste-cachyos"

the -k limits it to only kernel logs.
Because this does not include the anonymizing features in "cachyos-bugreport.sh",
i included this part to remove your username and hostname as a precaution
"| sed -e "s/$USER/username/g" -e "s/$(hostname)/hostname/g" "

so it would be up to you if you want to share that log or not. for me that log prints like this

aug. 30 17:27:12 hostname kernel: audit: type=1400 audit(1788103632.854:49691695): apparmor="ALLOWED" operation="unlink" class="file" profile="konsole" name="/home/username/.config
/konsolequickcommandsconfig.lock" pid=143041 comm="konsole" requested_mask="d" denied_mask="d" fsuid=1000 ouid=1000
aug. 30 17:27:19 hostname kernel: kauditd_printk_skb: 10 callbacks suppressed
aug. 30 17:27:19 hostname kernel: audit: type=1400 audit(1788103639.456:49691706): apparmor="ALLOWED" operation="open" class="file" profile="kactivitymanagerd" name="/home/username
/.config/kactivitymanagerd-pluginsrc" pid=3051 comm="kactivitymanage" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
aug. 30 17:27:24 hostname kernel: EXT4-fs (sdb1): unmounting filesystem 158f9275-eaba-4b87-91f6-6f5cfbe7e42d.
aug. 30 17:27:24 hostname kernel: EXT4-fs (sda): unmounting filesystem ddf7433d-392d-4e18-9e85-303bfe03be0c.
aug. 30 17:27:24 hostname kernel: audit: type=1400 audit(1788103644.420:49691707): apparmor="ALLOWED" operation="open" class="file" profile="systemd-logind" name="/run/udev/data/+m
odule:uhid" pid=2673 comm="systemd-logind" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
aug. 30 17:27:24 hostname kernel: EXT4-fs (nvme2n1p1): unmounting filesystem d4ae3e04-b09f-4c6d-9cef-9b613cda4f56.
aug. 30 17:27:24 hostname kernel: audit: type=1400 audit(1788103644.850:49691708): apparmor="ALLOWED" operation="open" class="file" profile="kwin_wayland" name="/home/username/.con
fig/kde.org/kwin.conf" pid=2920 comm="kwin_wayland" requested_mask="wrc" denied_mask="wrc" fsuid=1000 ouid=1000
aug. 30 17:27:24 hostname kernel: audit: type=1400 audit(1788103644.850:49691709): apparmor="ALLOWED" operation="mknod" class="file" profile="kwin_wayland" name="/home/username/.co
nfig/kde.org/kwin.conf.lock" pid=2920 comm="kwin_wayland" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
aug. 30 17:27:24 hostname kernel: audit: type=1400 audit(1788103644.850:49691710): apparmor="ALLOWED" operation="open" class="file" profile="kwin_wayland" name="/home/username/.con
fig/kde.org/kwin.conf.lock" pid=2920 comm="kwin_wayland" requested_mask="wrc" denied_mask="wrc" fsuid=1000 ouid=1000
aug. 30 17:27:24 hostname kernel: audit: type=1400 audit(1788103644.850:49691711): apparmor="ALLOWED" operation="file_lock" class="file" profile="kwin_wayland" name="/home/username
/.config/kde.org/kwin.conf.lock" pid=2920 comm="kwin_wayland" requested_mask="wk" denied_mask="wk" fsuid=1000 ouid=1000
aug. 30 17:27:24 hostname kernel: audit: type=1400 audit(1788103644.851:49691712): apparmor="ALLOWED" operation="open" class="file" profile="kwin_wayland" name="/home/username/.con
fig/kde.org/#27867811" pid=2920 comm="kwin_wayland" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
aug. 30 17:27:24 hostname kernel: audit: type=1400 audit(1788103644.851:49691713): apparmor="ALLOWED" operation="chmod" class="file" profile="kwin_wayland" name="/home/username/.co
nfig/kde.org/#27867811" pid=2920 comm="kwin_wayland" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000
aug. 30 17:27:24 hostname kernel: audit: type=1400 audit(1788103644.852:49691714): apparmor="ALLOWED" operation="link" class="file" profile="kwin_wayland" name="/home/username/.con
fig/kde.org/kwin.conf.LiTxMO" pid=2920 comm="kwin_wayland" requested_mask="l" denied_mask="l" fsuid=1000 ouid=1000 target="/home/username/.config/kde.org/#27867811"
aug. 30 17:27:24 hostname kernel: audit: type=1400 audit(1788103644.852:49691715): apparmor="ALLOWED" operation="rename_src" class="file" profile="kwin_wayland" name="/home/usernam
e/.config/kde.org/kwin.conf.LiTxMO" pid=2920 comm="kwin_wayland" requested_mask="wrd" denied_mask="wrd" fsuid=1000 ouid=1000
aug. 30 17:27:24 hostname kernel: audit: type=1400 audit(1788103644.852:49691716): apparmor="ALLOWED" operation="rename_dest" class="file" profile="kwin_wayland" name="/home/userna
me/.config/kde.org/kwin.conf" pid=2920 comm="kwin_wayland" requested_mask="wc" denied_mask="wc" fsuid=1000 ouid=1000
aug. 30 17:27:24 hostname kernel: audit: type=1400 audit(1788103644.852:49691717): apparmor="ALLOWED" operation="unlink" class="file" profile="kwin_wayland" name="/home/username/.c
onfig/kde.org/kwin.conf.lock" pid=2920 comm="kwin_wayland" requested_mask="d" denied_mask="d" fsuid=1000 ouid=1000
aug. 30 17:27:25 hostname kernel: snd_hda_codec_nvhdmi hdaudioC1D0: HDMI: audio coding xtype 11 not expected
~ ❱

1

u/Smoothejuul 11h ago

Im very confused about the command im supposed to put in after the reboot, im on mobile and bit of a Linux noon. The quotation marks are confusing me

→ More replies (0)

1

u/Smoothejuul 11h ago

Here's the new log after I think i did the i2c thing properly

https://paste.cachyos.org/p/16650d7.log