After 15 years of using Linux Mint it was time to move on.
Linux Mint is based on Ubuntu.
Ubuntu is driving 200 miles per hour towards a cliff.
I tried openSUSE Tumbleweed on a VirtualBox VM and liked it.
I installed openSUSE Tumbleweed on a Beelink SER8 miniPC.
After setting everything up I need help with a couple of issues.
MiniPC has 32GB DDR5 RAM, but I allocate 8GB to the GPU.
(1) I am stuck at 4K resolution, any attempts to change resolution result in a corrupted screen which goes back to 4K after 10 seconds. I use the KDE Plasma GUI to change the monitor resolution.
(2) At the lock screen, nothing is displayed on the screen. If I move the mouse cursor I can find the password box and type my password and press [Enter] to get back to a desktop.
(3) I want my screen to turn off and lock after a set time(which it does), but when I enter password and return to the desktop, all of my desktop icons are in different places.
(4) Only been at this a day, If I see more I’ll post to this forum.
I’ve been an nVidia GPU user for my lifetime, have no experience with AMDGPU.
Some other observations:
On Linux Steam, both “Black Mesa” and “DOOM”(2016) allowed resolution changing.
(“Xonotic” worked 100% as well)
Any help with these issues would be appreciated, thank you.
Is there anyway to fix this?
Or I have to wait on AMD to provide an update to the Linux Kernel?
(MiniPC is new, it was brought to market less than 6 months ago)
We found out yesterday that one needs the Packman repo active and the Mesa* packages installed from that repo. Do not mess with the commandline at this moment.
That looks to me more like a problem with the monitor then with the video-signal generated from the miniPC as it looks to me all pixels are present only the scaling is wrong. Likely you can correct it using the monitor settings.
I checked the monitor settings, they are basic with no options to adjust any scaling.
I am running HDMI now, I will try Display Port tomorrow when I wake up.
Monitor is this:
LG 24UD58-B Monitor 24" 4K Ultrafine (3840 x 2160) IPS Display, FreeSync, On-Screen Control, Screen Split 2.0, Game Mode, Black Stabilizer - Black
So if I understand things correctly, locking the computer works if it is done via a timeout but not if you initiate it manually? I never use it but when I manually lock the computer via Start → Power/Session → Lock I get the lock screen and have to type the password to get back.
Looking in the journal I am surprised it is working fine
Dec 22 09:12:05 kscreenlocker_greet[4674]: PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/security/pam_fprintd.so: cannot open shared object file: No such file >
Dec 22 09:12:05 kscreenlocker_greet[4674]: PAM adding faulty module: /usr/lib64/security/pam_fprintd.so
Dec 22 09:12:05 kscreenlocker_greet[4674]: PAM unable to dlopen(/usr/lib64/security/pam_pkcs11.so): /usr/lib64/security/pam_pkcs11.so: cannot open shared object file: No such file or>
Dec 22 09:12:05 kscreenlocker_greet[4674]: PAM adding faulty module: /usr/lib64/security/pam_pkcs11.so
Dec 22 09:12:08 kscreenlocker_greet[4674]: pam_kwallet5(kde-fingerprint:auth): pam_kwallet5: pam_sm_authenticate
Dec 22 09:12:08 kscreenlocker_greet[4674]: pam_kwallet5(kde:auth): pam_kwallet5: pam_sm_authenticate
Dec 22 09:12:08 kscreenlocker_greet[4674]: pam_kwallet5(kde-smartcard:auth): pam_kwallet5: pam_sm_authenticate
Dec 22 09:12:08 kscreenlocker_greet[4674]: pam_kwallet5(kde-fingerprint:auth): pam_kwallet5: Couldn't get password (it is empty)
Dec 22 09:12:08 kscreenlocker_greet[4674]: pam_kwallet5(kde-smartcard:auth): pam_kwallet5: Couldn't get password (it is empty)
Dec 22 09:12:08 kscreenlocker_greet[4674]: pam_kwallet5(kde:auth): pam_kwallet5: Couldn't get password (it is empty)
Dec 22 09:12:21 kscreenlocker_greet[4674]: pam_kwallet5(kde:setcred): pam_kwallet5: pam_sm_setcred
Dec 22 09:12:21 kwin_x11[2221]: kwin_core: XCB error: 152 (BadDamage), sequence: 54807, resource id: 10490763, major code: 143 (DAMAGE), minor code: 2 (Destroy)
Dec 22 09:12:21 kwin_x11[2221]: kwin_core: XCB error: 3 (BadWindow), sequence: 54808, resource id: 9437219, major code: 129 (SHAPE), minor code: 6 (Input)
Dec 22 09:12:21 kscreenlocker_greet[4674]: pam_kwallet5(kde-fingerprint:auth): pam_kwallet5: Empty or missing password, doing nothing
Dec 22 09:12:21 unix_chkpwd[4722]: password check failed for user (<user>)
Dec 22 09:12:21 kscreenlocker_greet[4674]: pam_unix(kde-fingerprint:auth): authentication failure; logname=<user> uid=1000 euid=1000 tty= ruser= rhost= user=<user>
Dec 22 09:12:21 kscreenlocker_greet[4674]: pam_kwallet5(kde-smartcard:auth): pam_kwallet5: Empty or missing password, doing nothing
Dec 22 09:12:21 unix_chkpwd[4723]: password check failed for user (<user>)
Dec 22 09:12:21 kscreenlocker_greet[4674]: pam_unix(kde-smartcard:auth): authentication failure; logname=<user> uid=1000 euid=1000 tty= ruser= rhost= user=<user>
I see only failures but in the end everything worked fine, my password was accepted directly.
Not sure how relevant this is because I have never had any sleep/wake issues, but there was a problem with icons and widgets being shuffled around for a couple of recent mesa versions. It is fixed now. Wait for a second opinion before doing what I suggest below.
Go to YaST > Software Repositories > Add > Community Repositories > Packman.
Then run sudo zypper dup --allow-vendor-change
I just did my first install this past monday and my desktop icons were getting reset on lock to the default sort as well. Until yesterday I think a KDE update in discover had fixed it but I can’t seem to find the patch note, and I’m not sure if the bug will happen again.
