You are not logged in.
I don't know what's going on, I restarted my system after typing sudo pacman -syu and found that my monitor was split into three interfaces,Then after I tried to uninstall my nvidia driver, my plasma booted up fine, but I had the problem after reinstalling nvidia, and finally I set my monitor refresh rate to 60hz and the system was back to normal.I suspect that my sudo pacman -syu command upgraded the nvidia-utils package,Is there a way for me to turn the 240hz refresh rate back on
Last edited by leessmin (2024-05-04 05:18:35)
Offline
Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
Did you maybe update from plasma 5 to plasma 6 and are now defaulting to wayland (where the previous default session type was X11)?
Does the issue exist w/ plasma/X11?
If so, please also post your Xorg log, https://wiki.archlinux.org/title/Xorg#General and the output of "xrandr -q"
Generally see https://wiki.archlinux.org/title/KDE#Un … lution_set and https://wiki.archlinux.org/title/Variable_refresh_rat
Offline
Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
Please post your complete system journal for the boot:sudo journalctl -b | curl -F 'file=@-' 0x0.st
Did you maybe update from plasma 5 to plasma 6 and are now defaulting to wayland (where the previous default session type was X11)?
Does the issue exist w/ plasma/X11?
If so, please also post your Xorg log, https://wiki.archlinux.org/title/Xorg#General and the output of "xrandr -q"Generally see https://wiki.archlinux.org/title/KDE#Un … lution_set and https://wiki.archlinux.org/title/Variable_refresh_rat
I am sorry that this is the first time I have published my question, and I do not follow the rules of arch linux. I am very sorry, and I apologize to you again,
I passed the order you gave me,This URL is generated.
http://0x0.st/XHK2.txt
I installed the system after plasma6, and then I've been using wayland, and I promise I haven't used x11,
I guess it has nothing to do with x11 and wayland, because I saw that systemd-backlight@backlight:nvidia_0.service failed to start when I looked at system-boot
Offline
seth wrote:Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
Please post your complete system journal for the boot:sudo journalctl -b | curl -F 'file=@-' 0x0.st
Did you maybe update from plasma 5 to plasma 6 and are now defaulting to wayland (where the previous default session type was X11)?
Does the issue exist w/ plasma/X11?
If so, please also post your Xorg log, https://wiki.archlinux.org/title/Xorg#General and the output of "xrandr -q"Generally see https://wiki.archlinux.org/title/KDE#Un … lution_set and https://wiki.archlinux.org/title/Variable_refresh_rat
I am sorry that this is the first time I have published my question, and I do not follow the rules of arch linux. I am very sorry, and I apologize to you again,
I passed the order you gave me,This URL is generated.http://0x0.st/XHK2.txt
I installed the system after plasma6, and then I've been using wayland, and I promise I haven't used x11,
I guess it has nothing to do with x11 and wayland, because I saw that systemd-backlight@backlight:nvidia_0.service failed to start when I looked at system-boot
In my experiments, the x11 also had this problem,Here is the output of my xrandr-q
Screen 0: minimum 16 x 16, current 2560 x 1600, maximum 32767 x 32767
eDP-1 connected primary 2560x1600+0+0 (normal left inverted right x axis y axis) 350mm x 220mm
2560x1600 59.99*+
2048x1536 59.95
1920x1440 59.97
1600x1200 59.87
1440x1080 59.99
1400x1050 59.98
1280x1024 59.89
1280x960 59.94
1152x864 59.96
1024x768 59.92
800x600 59.86
640x480 59.38
320x240 59.52
1920x1200 59.88
1680x1050 59.95
1440x900 59.89
1280x800 59.81
1152x720 59.97
960x600 59.63
928x580 59.88
800x500 59.50
768x480 59.90
720x480 59.71
640x400 59.95
320x200 58.96
2560x1440 59.96
2048x1152 59.90
1920x1080 59.96
1600x900 59.95
1368x768 59.88
1280x720 59.86
1024x576 59.90
864x486 59.92
720x400 59.55
640x350 59.77
Offline
4月 24 20:46:59 r97945hx systemd-logind[861]: /boot/loader/entries/arch.conf:2: Field 'nvidia_drm.modeset=1' without value, ignoring line.
4月 24 20:46:50 r97945hx kernel: [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on minor 0
4月 24 20:47:03 r97945hx kwin_wayland_wrapper[1433]: MESA-LOADER: failed to open simpledrm: /usr/lib/dri/simpledrm_dri.so: 无法打开共享目标文件: 没有那个文件或目录 (search paths /usr/lib/dri, suffix _dri)
4月 24 20:46:54 r97945hx kernel: amdgpu 0000:06:00.0: [drm] Cannot find any crtc or sizes
4月 24 20:46:50 r97945hx kernel: NVRM: Xid (PCI:0000:01:00): 62, pid='<unknown>', name=<unknown>, 20262044 2027f08e 2027df5c 2022ec3e 20281296 2022adbe 00000000 00000000
So there's
1. the simpledrm device because of a bogus bootloader entry.
2. The amdgpu device with no outputs attached.
3. the nvidia GPU w/ an XID and pot. w/o modesetting support
4月 24 20:47:03 r97945hx kwin_wayland[1433]: kwin_core: parsing edid failed
4月 24 20:47:03 r97945hx kwin_wayland[1433]: kwin_wayland_drm: Couldn't parse EDID for connector DrmConnector(id=91, gpu=KWin::DrmGpu(0x59e9d8494170), name="eDP-1-未知", connection="Connected", countMode=2)
Please post your /boot/loader/entries/arch.conf but I guess you just added that as a new line instead of appending it to the options?
I am sorry that this is the first time I have published my question, and I do not follow the rules of arch linux. I am very sorry, and I apologize to you again
Calm down, you're not gonna be eaten alive (at least that's what I've to say according to my prob… wait, I better shouldn't talk about that!)
It's just that vaguely describing a problem doesn't really allow anyone to help you - and there's a sticky about that because it happens more often
Edit: more rules
Please don't post full quotes, you're bloating the thread.
And also please don't bump the thread - rather edit your previous post unless somebody has already replied.
Last edited by seth (2024-04-24 13:22:34)
Offline
It's worth mentioning that every time I tried to turn on 240hz, my monitor would become like this and it wouldn't work at all.http://0x0.st/XHKJ.jpg
Offline
4月 24 20:46:59 r97945hx systemd-logind[861]: /boot/loader/entries/arch.conf:2: Field 'nvidia_drm.modeset=1' without value, ignoring line.
4月 24 20:46:50 r97945hx kernel: [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on minor 0 4月 24 20:47:03 r97945hx kwin_wayland_wrapper[1433]: MESA-LOADER: failed to open simpledrm: /usr/lib/dri/simpledrm_dri.so: 无法打开共享目标文件: 没有那个文件或目录 (search paths /usr/lib/dri, suffix _dri)
4月 24 20:46:54 r97945hx kernel: amdgpu 0000:06:00.0: [drm] Cannot find any crtc or sizes
4月 24 20:46:50 r97945hx kernel: NVRM: Xid (PCI:0000:01:00): 62, pid='<unknown>', name=<unknown>, 20262044 2027f08e 2027df5c 2022ec3e 20281296 2022adbe 00000000 00000000
So there's
1. the simpledrm device because of a bogus bootloader entry.
2. The amdgpu device with no outputs attached.
3. the nvidia GPU w/ an XID and pot. w/o modesetting support4月 24 20:47:03 r97945hx kwin_wayland[1433]: kwin_core: parsing edid failed 4月 24 20:47:03 r97945hx kwin_wayland[1433]: kwin_wayland_drm: Couldn't parse EDID for connector DrmConnector(id=91, gpu=KWin::DrmGpu(0x59e9d8494170), name="eDP-1-未知", connection="Connected", countMode=2)
Please post your /boot/loader/entries/arch.conf but I guess you just added that as a new line instead of appending it to the options?
I am sorry that this is the first time I have published my question, and I do not follow the rules of arch linux. I am very sorry, and I apologize to you again
Calm down, you're not gonna be eaten alive (at least that's what I've to say according to my prob… wait, I better shouldn't talk about that!)
It's just that vaguely describing a problem doesn't really allow anyone to help you - and there's a sticky about that because it happens more oftenEdit: more rules
Please don't post full quotes, you're bloating the thread.
And also please don't bump the thread - rather edit your previous post unless somebody has already replied.
I input the /boot/loader/entries/arch.conf,I got the following
nvidia_drm.modeset=1
Regarding the amd gpu, I remember that I had turned off the amd gpu in the bios and used nvidia to connect the display directly,I need to check with the bios
Last edited by leessmin (2024-04-24 13:28:26)
Offline
Please don't post full quotes, you're bloating the thread.
That's not a legal line in that file and also the error says it's line #2 - what is line one?
Do not paraphrase, post the actual file contents.
Offline
seth wrote:Please don't post full quotes, you're bloating the thread.
That's not a legal line in that file and also the error says it's line #2 - what is line one?
Do not paraphrase, post the actual file contents.
It's the only sentence in the file, and I seem to be the idiot who added it
Offline
seth wrote:Please don't post full quotes, you're bloating the thread.
That's not a legal line in that file and also the error says it's line #2 - what is line one?
Do not paraphrase, post the actual file contents.
I have deleted the contents of this file, but this problem still exists,
By the way, it's worth mentioning that I used a command that someone recommended to me a few days before this problem arose, and I don't know if this command is the root cause of this problem
options nvidia NVreg_RegistryDwords="PowerMizerEnable=0x1; PerfLevelSrc=0x2222; PowerMizerLevel=0x3; PowerMizerDefault=0x3; PowerMizerDefaultAC=0x3"
Last edited by leessmin (2024-04-24 13:38:20)
Offline
Please don't post full quotes, you're bloating the thread.
And also please don't bump the thread - rather edit your previous post unless somebody has already replied.
Nobody told you to delete that file - you'll have to enable nvidia_drm.modeset=1, but correctly.
https://wiki.archlinux.org/title/Kernel … stemd-boot
tail -n1000 /boot/loader/entries/*
Offline
seth wrote:Please don't post full quotes, you're bloating the thread.
And also please don't bump the thread - rather edit your previous post unless somebody has already replied.Nobody told you to delete that file - you'll have to enable nvidia_drm.modeset=1, but correctly.
https://wiki.archlinux.org/title/Kernel … stemd-boottail -n1000 /boot/loader/entries/*
I got the following
r97945hx# strace -f -tt -o /tmp/backlight.strace /usr/lib/systemd/systemd-backlight load backlight:nvidia_0
zsh: command not found: strace
r97945hx# tail -n1000 /boot/loader/entries/*
==> /boot/loader/entries/2024-03-18_06-07-26_linux.conf <==
# Created by: archinstall
# Created on: 2024-03-18_06-07-26
title Arch Linux (linux)
linux /vmlinuz-linux
initrd /amd-ucode.img
initrd /initramfs-linux.img
options root=PARTUUID=18e9dfc7-5080-448e-ae76-078ad2d9c5fe zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs
==> /boot/loader/entries/2024-03-18_06-07-26_linux-fallback.conf <==
# Created by: archinstall
# Created on: 2024-03-18_06-07-26
title Arch Linux (linux-fallback)
linux /vmlinuz-linux
initrd /amd-ucode.img
initrd /initramfs-linux-fallback.img
options root=PARTUUID=18e9dfc7-5080-448e-ae76-078ad2d9c5fe zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs
==> /boot/loader/entries/arch.conf <==
Offline
seth wrote:Please don't post full quotes, you're bloating the thread.
And also please don't bump the thread - rather edit your previous post unless somebody has already replied.
Don't stretch it.
Edit those files and append "nvidia_drm.modeset=1" to the "options" line
Offline
seth wrote:seth wrote:Please don't post full quotes, you're bloating the thread.
And also please don't bump the thread - rather edit your previous post unless somebody has already replied.Nobody told you to delete that file - you'll have to enable nvidia_drm.modeset=1, but correctly.
https://wiki.archlinux.org/title/Kernel … stemd-boottail -n1000 /boot/loader/entries/*
I got the following
r97945hx# strace -f -tt -o /tmp/backlight.strace /usr/lib/systemd/systemd-backlight load backlight:nvidia_0 zsh: command not found: strace r97945hx# tail -n1000 /boot/loader/entries/* ==> /boot/loader/entries/2024-03-18_06-07-26_linux.conf <== # Created by: archinstall # Created on: 2024-03-18_06-07-26 title Arch Linux (linux) linux /vmlinuz-linux initrd /amd-ucode.img initrd /initramfs-linux.img options root=PARTUUID=18e9dfc7-5080-448e-ae76-078ad2d9c5fe zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs ==> /boot/loader/entries/2024-03-18_06-07-26_linux-fallback.conf <== # Created by: archinstall # Created on: 2024-03-18_06-07-26 title Arch Linux (linux-fallback) linux /vmlinuz-linux initrd /amd-ucode.img initrd /initramfs-linux-fallback.img options root=PARTUUID=18e9dfc7-5080-448e-ae76-078ad2d9c5fe zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs ==> /boot/loader/entries/arch.conf <==
strace -f -tt -o /tmp/backlight.strace /usr/lib/systemd/systemd-backlight load backlight:nvidia_0 output
nvidia_0: Failed to write system 'brightness' attribute: Permission denied
It seems to be caused by no permission, do I need to use chmod +x to test it?
Last edited by leessmin (2024-04-24 13:43:47)
Offline
Don't stretch it.
I'm out.
Offline
seth wrote:Don't stretch it.
I'm out.
wuwuwu
Offline
I'm sorry. I just learned that I can't use quote to reply him. Please forgive me for being a newbie
Offline
You can quote. But don't quote the full content of long posts. Sometimes it's useful to quote a specific part of a post you are replying to, but not the full post. On it's own this is a very minor etiquette violation, but I suspect seth was most bothered by the fact that you just kept doing it, even after being asked not to many times.
Note that you also post multiple times in sequence even when no one else has commented. This too is a very minor etiquette violation here - but again you were asked not to do this, and you just kept doing it. If English is not your first language, perhaps there is a lack of understanding resulting in these errors - but it looks like you are just ignoring guidelines on how to post properly here. This is easy to perceive as rude.
We welcome newbies, but we do expect that you take as much time reading and understanding our responses as we take in writing them. But I believe seth still gave you the solution. Did you edit your boot loader entries? If so, can we see what's in them now (the same `tail ...` command)?
Last edited by Trilby (2024-04-24 15:05:35)
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
thank Trilby for reminding me,When I use the translation quotes are always translated as a synonym for price,That I did not understand seth's warning, and for that I am deeply sorry.I reinstalled my arch linux when I knew there was no way out, but the problem persisted. So now I think there are only two possibilities: one is the problem caused by a problem in one of the two packages, nvidia or Nvidia-utils.As I recall correctly, it appeared after I updated nvidia-utils.Here is my neofeatch
leessmin@r97945hx
OS: Arch Linux x86_64
Host: Jiaolong Series MRID6 1
Kernel: 6.8.7-arch1-1
Uptime: 7 mins
Packages: 721 (pacman)
Shell: bash 5.2.26
Resolution: 2560x1600
DE: Plasma 6.0.4
WM: KWin
Theme: Breeze-Dark [GTK2], Breeze [GTK3]
Icons: breeze-dark [GTK2/3]
Terminal: konsole
CPU: AMD Ryzen 9 7945HX with Radeon Graphics (32) @ 5.461GHz
GPU: NVIDIA GeForce RTX 4060 Max-Q / Mobile
GPU: AMD ATI 06:00.0 Raphael
Memory: 2339MiB / 31258MiB
Offline
nvidia bugs me every day.:(
Offline
https://www.deepl.com/translator#zh/
Please post an updated system journal since you've created a completely new situation.
Offline
This is what I get when I run
sudo journalctl -b | curl -F 'file=@-' 0x0.st
This is what I get http://0x0.st/XHZz.txt
Offline
Status quo ante, except you're now running X11 - but you still get
4月 25 00:39:24 r97945hx kwin_x11[1245]: kwin_core: parsing edid failed
cat /sys/module/nvidia_drm/parameters/modeset
Then check for
grep options /boot/loader/entries/*
again and append "nvidia_drm.modeset=1" to those lines (not as an extra line!), report back with an udpated journal and the impact on your problem.
Offline
[leessmin@r97945hx ~]$ sudo cat /sys/module/nvidia_drm/parameters/modeset
[sudo] leessmin 的密码:
Y
[leessmin@r97945hx ~]$ grep options /boot/loader/entries/*
/boot/loader/entries/2024-04-24_14-41-49_linux.conf:options root=PARTUUID=8dd000c4-c801-47b2-ba31-dc6854303bd8 zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs
/boot/loader/entries/2024-04-24_14-41-49_linux-fallback.conf:options root=PARTUUID=8dd000c4-c801-47b2-ba31-dc6854303bd8 zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs
I added nvidia_drm.modeset=1 to the end of the /boot/loader/entries/2024-04-24_14-41-49_linux.conf file
Final log output
http://0x0.st/XHZK.txt
Offline
Modesetting is enabled, simpledrm device gone, edid parsing failure remains
xrandr -q
for OUT in /sys/class/drm/card*; do echo $OUT; edid-decode $OUT/edid; echo "================="; done
You'll need https://aur.archlinux.org/packages/edid-decode-git for the latter.
Offline