Bugzilla – Bug 1217486
Macbook 5/nouveau: SDDM only displays password field on a black screen
Last modified: 2023-11-26 17:32:43 UTC
Created attachment 870973 [details] dmsg output at the point of corruption SDDM displayed corrupt screen and the GUI first and when I managed to update the OS to current 20231122 it showed only the password input box.
Created attachment 870974 [details] output of hwinfo (hwinfo attached) Operating System: openSUSE Tumbleweed 20231122 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.6.2-1-default (64-bit) Graphics Platform: Wayland Processors: 2 × Intel® Core™2 Duo CPU P7350 @ 2.00GHz Memory: 7.5 GiB of RAM Graphics Processor: NVAC Manufacturer: Apple Inc. Product Name: MacBook5,1 System Version: 1.0
Created attachment 870975 [details] Photo of screen with SDDM only showing password input Photo of SDDM. Please disregard the red reflection.I am sorry for horrible quality because of lighting and I had to take it with a phone.
Smells like an issue with the graphics driver. Which snapshot did you use before the update to 20231122? Does it work if you boot with the "nomodeset" kernel option?
Created attachment 870979 [details] SDDM on nouveau driver displays the content from previous Desktop after reboot nomodeset appears to fix glitches and strange fullscreen very fast glitch happening right before reboot (hardware reset step)
Created attachment 870980 [details] KDE Panel shows glitches/unviewable with nouveau/wl So basically I cold booted macbook 5.1, SDDM looks fine and after login I see "animated" pixels with random colours looking like being effected by CPU/IO activity (will attach video). Strange thing is only "kde panel" has the glitches. I also notice the same glitch (random pixels) flashing fullscreen right before hardware reboots. The attached photo at https://bugzilla.opensuse.org/attachment.cgi?id=870979 displays a very strange issue as in the circle supposed to show account photo is filled with the part of the Desktop from previous boot. I think it is from the glitchy panel.
Yeah, pretty much graphics driver issues. Reassigning. Please also answer the question from comment 3: > Smells like an issue with the graphics driver. Which snapshot did you use before the update to 20231122?
nouveau driver in use. May work, unfortunately in many cases it's just unusable. Nothing we can address. Due to lack of documenation, ressources and expertise. Ok. If these issues also occur with generic framebuffer (option nomodeset), then this looks more like a hardware issue to me. Unfortunately nvidia themselves with their proprietary and open driver also don't support this GPU, probably because anyone using Linux on Macbook was never on the focus. Seems this GPU was never used on standard PC hardware.
(In reply to Fabian Vogt from comment #3) > Smells like an issue with the graphics driver. Which snapshot did you use > before the update to 20231122? I don't see the reporter claiming it worked before with any Linux system. @Ilgaz Do you see this graphics glitches also on MacOS?
(In reply to Stefan Dirsch from comment #8) > (In reply to Fabian Vogt from comment #3) > > Smells like an issue with the graphics driver. Which snapshot did you use > > before the update to 20231122? > > I don't see the reporter claiming it worked before with any Linux system. > an/ > @Ilgaz Do you see this graphics glitches also on MacOS? Sorry I had some problems. I don't see problems on Mint (Ubuntu 20 based) with Nvidia drivers. I never expected same performance, nouveau is 3x slower however it was fairly stable with plasma-wayland even accelerating videos. Another thing is, for example issue didn't appear today. Only "issue" I see on dmesg is "nouveau 0000:02:00.0: fifo: CACHE_ERROR - ch 3 [kwin_wayland[2827]] subc 0 mthd 0060 data beef0201" This issue started to appear way more often after 6.5 major version. I can't pinpoint the exact version. It was fine for years now with daily updated continuously used Tumbleweed.
Hmm. That would mean you had nvidia's proprietary driver running on Mint/Ubuntu and with nouveau driver with older kernels. Unfortunately for this GPU you would need 340.x legacy driver by nVidia. And it's more or less impossible to still get this built and running on a recent kernel 6.x like we use it for Tumbleweed. I guess on Mint/Ubuntu you had a pretty old kernel running.
(In reply to Stefan Dirsch from comment #10) > Hmm. That would mean you had nvidia's proprietary driver running on > Mint/Ubuntu > and with nouveau driver with older kernels. > > Unfortunately for this GPU you would need 340.x legacy driver by nVidia. And > it's more or less impossible to still get this built and running on a recent > kernel 6.x like we use it for Tumbleweed. I guess on Mint/Ubuntu you had a > pretty old kernel running. For example it has been 6 hours now at work, I even enabled kvantum themes and the only error I see on dmesg is several of these: nouveau 0000:02:00.0: fifo: CACHE_ERROR - ch 3 [kwin_wayland[2827]] subc 0 mthd 0060 data beef0201 No glitches at all. I have this idea like installing gnome-wayland pattern along with gdm and use it for 3-4 days. I suspect there is a weird thing going on with kde wayland. It could be triggering a previously unknown issue.
Ok. Meanwhile I figured out that this laptop is from 2008. This explains, why it's no longer supported by a recent nvidia driver. Feel free to report the issue upstream to nouveau driver developers. https://nouveau.freedesktop.org/Bugs.html
(In reply to Stefan Dirsch from comment #12) > Ok. Meanwhile I figured out that this laptop is from 2008. This explains, > why it's no longer supported by a recent nvidia driver. Feel free to report > the issue upstream to nouveau driver developers. > > https://nouveau.freedesktop.org/Bugs.html I didn't know there would be a issue with the laptop being produced in 2008 or I would say it. It is only the producing company which is a commercial entity abandoned it.Not "Linux" or KDE. I spent hours trying to pinpoint the issue since I use KDE since V1.1 and Wayland. This issue is triggered by a critical KDE subsystem. I am sorry for wasting my and your time.