I’m using 1680x1050x60hz. HDMI connection. I’ve tried a new 32" monitor and my older original 22" monitor. I’ve tried various resolutions & refresh rates.
Notice upper right corner seems chopped off, lines at the bottom of the screen which I am guessing belong at the top.
That actually looks like the new default background for Leap 15.5.
You are right, that the top seems chopped off. And those lines near the bottom of the screen might be a little too low, so perhaps something is chopped off at the bottom.
Install and run glmark2 and note the result. Then uninstall xf86-video-ati and xf86-video-all and restart Plasma or reboot. Run glmark2 again and compare result. I’m guessing the top will no longer be cut off, but the score will be lower.
Thank you. Also, I started playing with the plasma wallpaper settings and my selected wallpaper is ‘image’. Switching to other options shows that the display is probably ok and that the graphics at the bottom of the display are intentional. I’ll try your suggestions but at this point I am satisfied that the default image that was installed just confused me. All’s well that ends well.
Actually, glmark2 does not run. That said, merely changing the desktop wallpaper from an ‘image’ to a photo and back to the default ‘image’ caused the upper R corner to correct itself and move to what appears to be a better position. The colored lines on the bottom is what confused me, I thought they were an indication of a video driver issue.
Here is my glmark2 run:
glmark2
libGL error: MESA-LOADER: failed to open r600: /usr/lib64/dri/r600_dri.so: undefined symbol: amdgpu_query_video_caps_info (search paths /usr/lib64/dri, suffix _dri)
libGL error: failed to load driver: r600
libGL error: MESA-LOADER: failed to open swrast: /usr/lib64/dri/swrast_dri.so: undefined symbol: amdgpu_query_video_caps_info (search paths /usr/lib64/dri, suffix _dri)
libGL error: failed to load driver: swrast
Error: glXCreateNewContext failed
Error: CanvasGeneric: Invalid EGL state
Error: main: Could not initialize canvas
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 152 (GLX)
Minor opcode of failed request: 24 (X_GLXCreateNewContext)
Value in failed request: 0x0
Serial number of failed request: 43
Current serial number in output stream: 44
If I run it w/ sudo it outputs one line:
sudo glmark2
[sudo] password for root:
Error: main: Could not initialize canvas
Anyway, I’m now satisfied that there is nothing wrong and I’ll probably change my desktop wallpaper to a solid color.
Thanks for both of you for the quick reply. I was a bit freaked out when I first saw this.
Mine has both 64 & 32 bit files. Maybe I have a long forgotten 32bit app but who knows, I’ve been updating this box since OpenSuse v13.x.
I notice some of these files have a different build than you. The other thing is this Dell has an onboard Intel video card which I am not using (IIRC, disabled in bios) plus a plugin video card that I am using. It was configured this way by Dell.
Thanks for your suggestions.
Mine come 100% from standard repos. Yours are a mixture of standard (32bit) and Packman (64bit, except for demo-x). I think they should all come from the same repo, but it could be Packman’s are broken, or yours is lacking some dependency.
The other difference is I’m using the modesetting DIX. xf86-video-ati is not installed here, but I would address the Mesa difference first.
There’s also non-zero possibility the failure is specific to the difference in our Radeon models, or kernel-firmware-radeon is needed but not installed.
I use the above miniscript to help me ensure locked packages don’t interfere with progress by keeping obsolete packages installed, or blocking required new ones. I don’t think your locks should be causing a problem, but sometimes dependencies aren’t what a mere user would expect. Multiple Google fonts are hard requirements of multiple packages, though no specific font should ever be, so a roboto lockdown could easily cause interference unless choosing to “break” (the ego of) the requiring package(r). Some kernel-firmware-* have inexplicable interdependencies, so could also be blocking. So could libdrm_amdgpu1. Check what “System Packages” you have installed. After a fresh update, there should be none.
cat /usr/local/bin/zypseo
cat: /usr/local/bin/zypseo: No such file or directory
The zypper cmd gives me a long list but I don’t really know how to interpret it.
I just read a post about amdgpu firmware and it fixing a problem for the poster so I’ll go ahead and update those blocked packages, except the preempt packages.
