new powerdevil 6.3 still disables my Endeavour OS operation. Long ago made mention of this bug on the kde website.
On this one machine, powerdevil disables Cachy and Endeavour OS. Oddly, KDE plasma on openSUSE Tumbleweed, and Arco linux operate okay on this machine
Perhaps a grub setting is different ? I have not mucked about with grub customizer for several years. I have rEFInd booting my different partitions.
Don’t use grub customizer you’ll only regret it eventually. I’m not sure why powerdevil would disable CachyOS and EndeavourOS. What do you mean disables it? Using refind too? I’m not sure what you are asking? If you are going to have multiple linux distro’s booting and want to use grub then you should let EndeavourOS grub control the boot of all others. It requires you to uncomment os-prober in the default grub file on EOS and then run the update grub command on EOS. Don’t allow other OS installed to control the boot or change it when you update them.
Edit That requires you to disable os-prober on them and only use EOS for booting.
With powerdevil, starting with version 6.2 and up, the Plasma desktop shows for a few brief seconds and then the screen goes black and seems to reboot the monitor. I can enter the terminal with CTL-ALT-F2 (or F3 I forget which)
I have spent far too much time mucking about with grub customizer and rEFInd has worked well for me. I am leery of trying your suggestion, but it has merit. I do like to have multiple partitions with different distros available for when one get broken with an update. I am used to Arch variants but for the infrequent update caused disruptions. I considered switching the DE to XFCE, Gnome, or Cinnamon. Plasma is what I am used to.
That openSUSE tumbleweed and Arco work fine with powerdevil 6.2 and up, my guess is that it is a combination of my hardware and grub that something is failing. Grub is the boot variant I chose over systemD. Powerdevil also breaks my one systemD boot distro. I am assuming Grub is somewhat differing with the various distros.
Might want to check on the Arch forums: https://bbs.archlinux.org/. There are multiple topics on basically the same issue. Can you post the results of inxi -Gaz?
Is your hardware a laptop? I have power devil and have no issues on Kde.
CPU: 8-core AMD Ryzen 7 7700 (-MT MCP-) speed/min/max: 3017/400/5389 MHz
Kernel: 6.13.2-arch1-1 x86_64 Up: 29m Mem: 9.03/15.36 GiB (58.8%)
Storage: 1.39 TiB (7.5% used) Procs: 399 Shell: Bash inxi: 3.3.37
The bug is present on just this one PC and not all distros. Cannot troubleshoot without experiencing the bug? (and without deep knowledge of Linux)
Cannot (easily) turn a ground vehicle into a flying vehicle…
You didn’t post the output of the command asked.
[gary@LegionEndv ~]$ inxi -Gaz
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 23 [Radeon RX 6600/6600
XT/6600M] vendor: Lenovo driver: amdgpu v: kernel arch: RDNA-2
code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4
speed: 16 GT/s lanes: 16 ports: active: HDMI-A-1 empty: DP-1, DP-2, DP-3,
Writeback-1 bus-ID: 03:00.0 chip-ID: 1002:73ff class-ID: 0300
Device-2: Microsoft LifeCam HD-3000 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-10:7
chip-ID: 045e:0810 class-ID: 0102
Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.5
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu display-ID: 0
Monitor-1: HDMI-A-1 model: Samsung Odyssey G5 serial: built: 2023
res: mode: 2560x1440 hz: 60 scale: 100% (1) dpi: 93 gamma: 1.2
size: 698x393mm (27.48x15.47") diag: 806mm (31.7") ratio: 16:9 modes:
max: 2560x1440 min: 720x400
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
wayland: drv: radeonsi x11: drv: radeonsi
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.3.4-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6600 (radeonsi navi23
LLVM 19.1.7 DRM 3.59 6.13.2-arch1-1) device-ID: 1002:73ff memory: 7.81 GiB
unified: no display-ID: :1.0
API: Vulkan Message: No Vulkan data available.
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,
kscreen-doctor, xfce4-display-settings wl: wayland-info
x11: xdpyinfo, xprop, xrandr
@garybean, using the “preformatted text” option here in the forum makes things cleaner and easier to view when you want to share terminal output.
It would look like this:
[gary@LegionEndv ~]$ inxi -Gaz
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 23 [Radeon RX 6600/6600
XT/6600M] vendor: Lenovo driver: amdgpu v: kernel arch: RDNA-2
code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4
speed: 16 GT/s lanes: 16 ports: active: HDMI-A-1 empty: DP-1, DP-2, DP-3,
Writeback-1 bus-ID: 03:00.0 chip-ID: 1002:73ff class-ID: 0300
Device-2: Microsoft LifeCam HD-3000 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-10:7
chip-ID: 045e:0810 class-ID: 0102
Display: wayland server: [X.org](http://X.org) v: 1.21.1.15 with: Xwayland v: 24.1.5
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu display-ID: 0
Monitor-1: HDMI-A-1 model: Samsung Odyssey G5 serial: built: 2023
res: mode: 2560x1440 hz: 60 scale: 100% (1) dpi: 93 gamma: 1.2
size: 698x393mm (27.48x15.47") diag: 806mm (31.7") ratio: 16:9 modes:
max: 2560x1440 min: 720x400
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
wayland: drv: radeonsi x11: drv: radeonsi
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.3.4-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6600 (radeonsi navi23
LLVM 19.1.7 DRM 3.59 6.13.2-arch1-1) device-ID: 1002:73ff memory: 7.81 GiB
unified: no display-ID: :1.0
API: Vulkan Message: No Vulkan data available.
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,
kscreen-doctor, xfce4-display-settings wl: wayland-info
x11: xdpyinfo, xprop, xrandr
I don’t see anything out of the ordinary. I found this link for the same issue with CachyOS: https://discuss.cachyos.org/t/wayland-black-screen-after-login/6431.
Did you ever try an X11 session?