Hi, I've upgraded to Leap 42.2 a week ago and I'd like to share my experiences. It was 90% successful but I have two big pain points: 3D and hibernate. Both features have degraded slowly over the past months (it started with Leap 41.1, 13.2 was very stable for years). Newer kernels tend to be less stable. 4.1 worked pretty good, 4.7 didn't work at all. I used "zypper dup" to upgrade my distribution from Leap 41.1 and that worked well, despite the fact that the wiki wasn't updated for Leap 42.2. But the instructions for 13.x -> 42.1 were easy enough to understand, so I could translate them myself. First boot worked, display manager failed. I had some trouble downloading the correct NVIDIA driver. I have a ASUS GTX 1050 Ti, so I needed 375.20. When I had that, the display manager (sddm?) started working. There were a couple of updates, so I installed those. I'm using KDE. Clicking on "Logout" did nothing. journalctl reported that sddm-greeter was crashing. I tried again, same result. Yesterday, I installed updates again and sddm-greeter refused to work afterwards. I had to reboot manually from the console. This sucks. From my point of view, sddm seems to be more of a problem than anything else. Not being able to do anything from the UI leaves me helpless and frustrated. I understand that Mesa updates replace important 3D libraries and sddm needs them but this piece of software is so important that it should fall back to something useful when it can't use 3D. That said, after updates, a lot of KDE software, chrome and chromium started to act up until I reinstalled the NVIDIA drivers. The error messages were mostly useless (that's what the KDE error reporter told me) or I didn't get any message at all. I'm not sure what less educated users would do in my situation. Not being able to reboot after installing security patches shouldn't happen. It makes me wonder whether I really need those patches. I also have a lot of graphics garbage on the screen after resume from hibernate to disk. That started with Leap 42.1 some time in September, I think. Window frames, Flash web content and desktop icon texts are most vulnerable. My guess is that the KDE 3D code is broken somehow but I don't know how to find out what is happening. Frustrating again. Also, when this happens, I can't disable 3D effects in systemsettings5 since that crashes immediately when I try to open the effects. During hibernate, I get messages on the (text) console that "BUG: sleeping function called from invalid context at ../kernel/locking/rwsem.c:21" Out of 20 attempts to hibernate, 4 fail to resume with the message: "ACPI: Hardware changed while hibernated, success doubtful" Something in the kernel must be broken since my hardware didn't change. And there is another "BUG: scheduling while atomic: systemd-sleep/.../..." Please let me know if I can provide more information to track down these bugs. Regards, -- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/29/2016 11:38 AM, Aaron Digulla wrote:
Hi,
I've upgraded to Leap 42.2 a week ago and I'd like to share my experiences. It was 90% successful but I have two big pain points: 3D and hibernate. Both features have degraded slowly over the past months (it started with Leap 41.1, 13.2 was very stable for years). Newer kernels tend to be less stable. 4.1 worked pretty good, 4.7 didn't work at all.
I used "zypper dup" to upgrade my distribution from Leap 41.1 and that worked well, despite the fact that the wiki wasn't updated for Leap 42.2. But the instructions for 13.x -> 42.1 were easy enough to understand, so I could translate them myself.
First boot worked, display manager failed.
I had some trouble downloading the correct NVIDIA driver. I have a ASUS GTX 1050 Ti, so I needed 375.20. When I had that, the display manager (sddm?) started working.
There were a couple of updates, so I installed those. I'm using KDE. Clicking on "Logout" did nothing.
journalctl reported that sddm-greeter was crashing. I tried again, same result.
Yesterday, I installed updates again and sddm-greeter refused to work afterwards. I had to reboot manually from the console. This sucks. From my point of view, sddm seems to be more of a problem than anything else. Not being able to do anything from the UI leaves me helpless and frustrated. I understand that Mesa updates replace important 3D libraries and sddm needs them but this piece of software is so important that it should fall back to something useful when it can't use 3D.
That said, after updates, a lot of KDE software, chrome and chromium started to act up until I reinstalled the NVIDIA drivers. The error messages were mostly useless (that's what the KDE error reporter told me) or I didn't get any message at all.
I'm not sure what less educated users would do in my situation. Not being able to reboot after installing security patches shouldn't happen. It makes me wonder whether I really need those patches.
I also have a lot of graphics garbage on the screen after resume from hibernate to disk. That started with Leap 42.1 some time in September, I think. Window frames, Flash web content and desktop icon texts are most vulnerable. My guess is that the KDE 3D code is broken somehow but I don't know how to find out what is happening. Frustrating again.
Also, when this happens, I can't disable 3D effects in systemsettings5 since that crashes immediately when I try to open the effects.
During hibernate, I get messages on the (text) console that "BUG: sleeping function called from invalid context at ../kernel/locking/rwsem.c:21" Out of 20 attempts to hibernate, 4 fail to resume with the message: "ACPI: Hardware changed while hibernated, success doubtful" Something in the kernel must be broken since my hardware didn't change. And there is another "BUG: scheduling while atomic: systemd-sleep/.../..."
Please let me know if I can provide more information to track down these bugs.
Regards,
You are using the NVIDIA driver which is a big game changer. You have now modified openSUSE from its default state and installed a proprietary piece of software on the machine and are now having all sorts of graphics problems. I have been using sddm on multiple machines for quite a while now and have just about 0 issues, and not just only under openSUSE. My suggestion would be to focus on one issue that you need help with, not do a data dump of every single problem you had with 42.2 expecting someone here to step in and help you with everything you found wrong with 42.2 on your machine. Personally, I won't usually support anyone using the NVIDIA driver when they are having issues. It's because NVIDIA can program bugs (and do) into their drivers, then users come and ask openSUSE users to help them because of NVIDIA's unwillingness to work with the Linux community. We also don't support Chrome here. For that, you should contact Google or go to the Google help forums. openSUSE is not about the furthering of proprietary software, even if you have Non-OSS repos. Those repos are use at your own risk; if a user does decide to use them, the software installed from those repos comes with no support or guarantee that anything is going to work correctly. It other words, don't start playing around with the NVIDIA binary unless you really know what you're doing, and if you don't, then find the proper support channels where you can get answers. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 29.11.2016 21:00, sdm wrote:
On 11/29/2016 11:38 AM, Aaron Digulla wrote:
Hi,
I've upgraded to Leap 42.2 a week ago and I'd like to share my experiences. It was 90% successful but I have two big pain points: 3D and hibernate. Both features have degraded slowly over the past months (it started with Leap 41.1, 13.2 was very stable for years). Newer kernels tend to be less stable. 4.1 worked pretty good, 4.7 didn't work at all.
I used "zypper dup" to upgrade my distribution from Leap 41.1 and that worked well, despite the fact that the wiki wasn't updated for Leap 42.2. But the instructions for 13.x -> 42.1 were easy enough to understand, so I could translate them myself.
First boot worked, display manager failed.
I had some trouble downloading the correct NVIDIA driver. I have a ASUS GTX 1050 Ti, so I needed 375.20. When I had that, the display manager (sddm?) started working.
There were a couple of updates, so I installed those. I'm using KDE. Clicking on "Logout" did nothing.
journalctl reported that sddm-greeter was crashing. I tried again, same result.
Yesterday, I installed updates again and sddm-greeter refused to work afterwards. I had to reboot manually from the console. This sucks. From my point of view, sddm seems to be more of a problem than anything else. Not being able to do anything from the UI leaves me helpless and frustrated. I understand that Mesa updates replace important 3D libraries and sddm needs them but this piece of software is so important that it should fall back to something useful when it can't use 3D.
That said, after updates, a lot of KDE software, chrome and chromium started to act up until I reinstalled the NVIDIA drivers. The error messages were mostly useless (that's what the KDE error reporter told me) or I didn't get any message at all.
I'm not sure what less educated users would do in my situation. Not being able to reboot after installing security patches shouldn't happen. It makes me wonder whether I really need those patches.
I also have a lot of graphics garbage on the screen after resume from hibernate to disk. That started with Leap 42.1 some time in September, I think. Window frames, Flash web content and desktop icon texts are most vulnerable. My guess is that the KDE 3D code is broken somehow but I don't know how to find out what is happening. Frustrating again.
Also, when this happens, I can't disable 3D effects in systemsettings5 since that crashes immediately when I try to open the effects.
During hibernate, I get messages on the (text) console that "BUG: sleeping function called from invalid context at ../kernel/locking/rwsem.c:21" Out of 20 attempts to hibernate, 4 fail to resume with the message: "ACPI: Hardware changed while hibernated, success doubtful" Something in the kernel must be broken since my hardware didn't change. And there is another "BUG: scheduling while atomic: systemd-sleep/.../..."
Please let me know if I can provide more information to track down these bugs.
Regards,
You are using the NVIDIA driver which is a big game changer. You have now modified openSUSE from its default state and installed a proprietary piece of software on the machine and are now having all sorts of graphics problems. I have been using sddm on multiple machines for quite a while now and have just about 0 issues, and not just only under openSUSE.
I feel that the issue here is that you know that NVIDIA drivers cause problems and still, the software which comes with openSUSE doesn't install crash handlers which disable 3D when there is a problem. It's sad that NVIDIA doesn't listen to the community as much as you'd like but at the same time, I use 3D software like Blender and I play a lot of games on Steam and I need good 3D drivers. Nouveau is a heroic attempt but useless for me. Steam, for example, does install crash handlers. While it felt for me that KDE and the kernel get more brittle over the past 12 months, Steam got more and more stable. Maybe it's the games that I play :-) Regards, -- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-11-29 20:38, Aaron Digulla wrote:
During hibernate, I get messages on the (text) console that "BUG: sleeping function called from invalid context at ../kernel/locking/rwsem.c:21" Out of 20 attempts to hibernate, 4 fail to resume with the message: "ACPI: Hardware changed while hibernated, success doubtful" Something in the kernel must be broken since my hardware didn't change. And there is another "BUG: scheduling while atomic: systemd-sleep/.../..."
On one machine I got messsages about corrupted low memory, after hibernation. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2016-11-29 21:00, sdm wrote:
On 11/29/2016 11:38 AM, Aaron Digulla wrote:
My suggestion would be to focus on one issue that you need help with, not do a data dump of every single problem you had with 42.2 expecting someone here to step in and help you with everything you found wrong with 42.2 on your machine. Personally, I won't usually support anyone using the NVIDIA driver when they are having issues.
Unfortunately, the free alternative is not up to the task. Several applications do not work without the proprietary driver installed. Think Plasma, for instance. Think apps doing 3D. I do understand that Nouveau is very complicated to do without help from Nvidia (documentation), but as there is no hardware alternative to buy we users are forced to buy Nvidia or AMD graphics. Yes, there is Intel graphics, but they are not good enough (yet?) So please do not blame users when we are forced to use the proprietary drivers. It is not our fault. :-/ -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
29.11.2016 22:38, Aaron Digulla пишет: ...
I had some trouble downloading the correct NVIDIA driver. I have a ASUS GTX 1050 Ti, so I needed 375.20. When I had that, the display manager (sddm?) started working.
If you buy bleeding edge product requiring drivers released just a week ago, you are expected to know what you are doing. You could also wait until these drivers are available via normal nVidia openSUSE repository. ...
I'm not sure what less educated users would do in my situation.
Install drivers from repository and avoid these issues. ...
During hibernate, I get messages on the (text) console that "BUG: sleeping function called from invalid context at ../kernel/locking/rwsem.c:21"
That should be reported in bugzilla.
Out of 20 attempts to hibernate, 4 fail to resume with the message: "ACPI: Hardware changed while hibernated, success doubtful" Something in the kernel must be broken since my hardware didn't change.
Again this needs report in bugzilla.
And there is another "BUG: scheduling while atomic: systemd-sleep/.../..."
Same. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-11-30 04:36, Andrei Borzenkov wrote:
29.11.2016 22:38, Aaron Digulla пишет:
During hibernate, I get messages on the (text) console that "BUG: sleeping function called from invalid context at ../kernel/locking/rwsem.c:21"
That should be reported in bugzilla.
True, but he is using nvidia driver... it may be possibly not be investigated. It has happened before. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 30.11.2016 04:36, Andrei Borzenkov wrote:
During hibernate, I get messages on the (text) console that "BUG: sleeping function called from invalid context at ../kernel/locking/rwsem.c:21" That should be reported in bugzilla.
Thanks, I did: https://bugzilla.novell.com/show_bug.cgi?id=1014357
Out of 20 attempts to hibernate, 4 fail to resume with the message: "ACPI: Hardware changed while hibernated, success doubtful" Something in the kernel must be broken since my hardware didn't change. Again this needs report in bugzilla.
https://bugzilla.novell.com/show_bug.cgi?id=1014358
And there is another "BUG: scheduling while atomic: systemd-sleep/.../..."
Same.
I merged that into the first bug report because I suspect that they are related. Regards, -- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Aaron Digulla -
Andrei Borzenkov -
Carlos E. R. -
sdm