Hm, it still uses nouveau which shouldn’t be possible if nouveau is blacklisted.
Try to recreate the initrd, maybe nouveau is still in there:
sudo /sbin/mkinitrd
If there are errors, please post them.
And/or try to add “nomodeset” to the kernel boot options, although this shouldn’t be necessary either if nouveau is blacklisted and not included in the initrd.
an extract from “messages” file : messages about the second start of the pc SUSE Paste
it’s interesting because we have also NVRM messages about nvidia and xorg server which dies and kdm which does not start.
Right. This doesn’t seem to be from the same boot…
The Xorg log is from Sun Dec 14 16:08:26 2014, whereas according to “messages”, KDM (and Xorg) has been started at 2014-12-14T17:59:16.781603+01:00 .
So X is not starting at all when you are using the nvidia driver?
Your Xorg log is useless then, it is from earlier boots, before nouveau was blacklisted apparently.
Does it work when you try to start Xorg manually in text mode?
I.e. “init 3” followed by “init 5”, or running “startx” (as root).
If X doesn’t even try to start, this does sound related to the latest change to the packages:
Xwrapper: bail out, if an existing module cannot be unloaded;
this can happen if a second Xsession starts
This is related to 904383 – nvidia version driver update fails (340.46 -> 340.58) it seems. Unloading the nvidia modules when starting X shall prevent the problem that nvidia doesn’t work on the first boot after the installation, AIUI.
Can you please post your /usr/bin/X.x11-video-nvidia-G03 ?
Try to change this:
# bail out, if an existing module cannot be unloaded
# this can happen if a second Xsession starts
/sbin/rmmod -v $m || exit 1
to just
/sbin/rmmod -v $m
in that file, i.e. remove the " || exit 1".
Maybe this would make X start successfully? I don’t see a point in exiting there anyway if unloading a kernel module fails.
an interesting thing : when switching to nouveau i forget to set to “no” “no_kms_in_initrd” the i get same black screen witha text line at the top .
That’s normal, and actually caused by plymouth. plymouth initializes the graphics display already, and is started from the initrd normally. If nouveau isn’t part of the initrd (i.e. when you have NO_KMS_IN_INITRD=“yes”), it cannot load nouveau and uses a generic driver instead. But this prevents nouveau from correctly initializing the graphics later on (and in particular loading the firmware if necessary) when it is actually loaded and causes problems. The same happens with other KMS drivers like radeon or intel.
i wonder if is a kms pb for the nvidia driver.
No. nvidia doesn’t use nor support KMS. But there should not be a problem if KMS is enabled, unless nouveau is loaded already.
