Hi Tobias,

As we got a new kernel with that (4.3.2 -> 4.3.3) you could try to bisect the commit introducing the problem. With this help it is more likely nouveau developers will fix this (report a bug at freedesktop)

thx for your answer, but I suspect the reason is the kernel, because I always used a kernel from the kernel stable repository and therefore had 4.3.3 much earlier than it appeared in Tumbleweed. That was necessary, because kernels before 4.3.x didn't really support my graphics card. My problem seems to stem from the plasma5 update from 5.4.3 to 5.5.1 which was part of the Tumbleweed snapshot 20151229. Since this snapshot the problem occurs.

Greetings,

Tobias

By. Michael.

On 09.01.2016 11:10, Michael Hirmke wrote:

...

Hi *,

starting with the last snapshot from 2015 and even with this latest snapshot I've "lost" my plasma5 desktop. After starting the system I get the sddm login screen. After that and before anything else is shown the nouveau driver is throwing an error and all I get is a black screen. I can't even switch to a text console then, but I can login in using ssh, so the system is still running.

These are the messages from the log regarding the nouveau driver:

kernel: fb: switching to nouveaufb from VESA VGA kernel: nouveau 0000:01:00.0: NVIDIA GM107 (117010a2) kernel: nouveau 0000:01:00.0: bios: version 82.07.32.00.eb kernel: nouveau 0000:01:00.0: fb: 2048 MiB GDDR5 kernel: nouveau 0000:01:00.0: DRM: VRAM: 2048 MiB kernel: nouveau 0000:01:00.0: DRM: GART: 1048576 MiB kernel: nouveau 0000:01:00.0: DRM: TMDS table version 2.0 kernel: nouveau 0000:01:00.0: DRM: DCB version 4.0 kernel: nouveau 0000:01:00.0: DRM: DCB outp 00: 02000f10 00000000 kernel: nouveau 0000:01:00.0: DRM: DCB outp 01: 01000f12 00020030 kernel: nouveau 0000:01:00.0: DRM: DCB outp 02: 02011f62 00020010 kernel: nouveau 0000:01:00.0: DRM: DCB outp 03: 08822fc6 04420010 kernel: nouveau 0000:01:00.0: DRM: DCB outp 04: 08022f82 00020010 kernel: nouveau 0000:01:00.0: DRM: DCB conn 00: 00010030 kernel: nouveau 0000:01:00.0: DRM: DCB conn 01: 00020161 kernel: nouveau 0000:01:00.0: DRM: DCB conn 02: 01000246 kernel: nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies kernel: nouveau 0000:01:00.0: DRM: allocated 2560x1440 fb: 0x60000, bo ffff88021409b000 kernel: fbcon: nouveaufb (fb0) is primary device kernel: nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device kernel: [drm] Initialized nouveau 1.3.0 20120801 for 0000:01:00.0 on minor 0 kernel: nouveau 0000:01:00.0: fifo: read fault at 0000011000 engine 07 [PBDMA0] client 06 [HOST] reason 00 [PDE] on channel -1 [007f851000 unknown] kernel: nouveau 0000:01:00.0: DRM: GPU lockup - switching to software fbcon kernel: nouveau 0000:01:00.0: X[4204]: failed to idle channel 0xcccc0000 [X[4204]] kernel: nouveau 0000:01:00.0: X[4204]: failed to idle channel 0xcccc0000 [X[4204]] kernel: nouveau 0000:01:00.0: X[4204]: failed to idle channel 0xcccc0000 [X[4204]] kernel: nouveau 0000:01:00.0: X[4204]: failed to idle channel 0xcccc0000 [X[4204]] kernel: nouveau 0000:01:00.0: X[4204]: failed to idle channel 0xcccc0000 [X[4204]] kernel: nouveau 0000:01:00.0: X[4204]: failed to idle channel 0xcccc0000 [X[4204]]

Is there anything I can do besides a bug report?

Thx and bye. Michael.

-- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Michael Hirmke <mh@mike.franken.de> [01-11-16 17:56]: [...]

there is something really strange going on. I tried to logon with a newly created account - and that worked without any problem, meaning I got a working plasma5 desktop. So I tried to move all of the configuration directories for my regular account out of the way, i.e. .kde4, .local, .config and so on. Nothing helped - I still got a black desktop. Then I renamed my .profile - and all of a sudden I got my desktop back. I tried to find out what part of the .profile would cause the problems, but I didn't succeed in this. I tried to comment out half of the commands in this file, then the other half. In both cases the crashes remained. Only without any .profile it works.

So I'm really running out of ideas.

Does anyone have a hint what I can do now?

You filed a bug as suggested? First thing might be to post the ".profile" that you believe is causing your problem. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

[...]

The .profile doesn't seem to be the real root of the problem. I commented out everything - after that the problem didn't occur any longer. I then reactivated one line at a time. At some point the crash occurred again. I then reactivated different lines than before - and again the crash happened after having activated about half of the .profile. I tried about ten combinations - and the crash always occurred random after activating the n-th line, whatever that line was.

Whats more: This .profile is used on *all* of my Linux systems and I never had any problems with it. It is used even on a Leap 42.1 with all the actual patches installed - and it works.

[...] problem solved with the latest snapshot. I don't know, though, which of the new packages solved it. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org