Hi Wolfgang,
Am Montag, 21. November 2016, 19:30:00 schrieb Michael Hirmke:
1. No xorg.conf.d structure at all -> nouveau gets loaded, X is starting. Same behaviour with Leap 42.2 ad with Tumbleweed.
Have you checked that Xorg is really using nouveau? (in the Xorg log e.g)
yes, the log clearly shows this.
If nouveau fails to load, Xorg will fall back to a different driver, likely "modesetting" which will still use the nouveau kernel module.
I know, but this isn't the case here.
2. Tiny xorg.conf.d structure as shown below with a driver entry for nouveau, i.e. Driver "nouveau" -> X server is not starting with an entry "Unknown chipset: NV117" at the end of Xorg.0.log. Same behaviour with Leap 42.2 ad with Tumbleweed.
Well, apparently the nouveau Xorg driver doesn't support your chipset. As you told Xorg to use nouveau, it fails to start because nouveau cannot be loaded.
According to the nouveau page, NV117 is supported.
3. Tiny xorg.conf.d structure as shown below without a driver entry for nouveau -> X server is starting and one can logon via sddm, but a few program starts later, the nouveau driver is crashing with errors like "nouveau 0000:01:00.0: fifo: PBDMA0: 00040000 [PBENTRY] ch 15 [007e351000 X[1413]] subc 0 mthd 0000 data 00000000". This happens with Leap 42.2 only, not with Tumbleweed - with the exact same modules from kernel 4.8.9-1.
Tumbleweed has a newer kernel (and a newer nouveau kernel module), this may be the difference.
As I wrote - I use exactly the same kernel.
Kind Regards, Wolfgang
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org