bigpup wrote:/tmp/.nouveau_modeset_0 file is present.
/etc/modeprobe.d/nouveau.conf
At present has this:
Code: Select all
install nouveau \
[ -e /tmp/.nouveau_modeset_0 ] \
&& /sbin/modprobe --ignore-install nouveau modeset=0 $CMDLINE_OPTS \
|| ( [ -e /tmp/.nouveau_nomodeset ] \
&& /sbin/modprobe --ignore-install nouveau $CMDLINE_OPTS \
|| /sbin/modprobe --ignore-install nouveau modeset=1 $CMDLINE_OPTS )
What should I change in this code?
I am using the Vesa driver, after booting pfix=nox and using Xorgwizard to select Vesa. Did it make the changes you are talking about to this file?
That is my code that replaces the existing nouveau.conf file, to make it "smart". It is unrelated to Xorgwizard. It intercepts the loading of nouveau to choose the mode to set. But I think all of it is moot!
I have been experimenting on my PC that uses nouveau, adjusting the mode in both the boot parameter and in that config file -- but in "reverse". I verified that the auto_modeset package performs as expected, so can be trusted. My PC gets the black screen if the mode is 0 in the config file. If I leave the config file's mode at "1" but use boot parameter nouveau.modeset=0, all is well. I arrived at a conclusion about how this works.
Apparently, the boot parameter is in effect when nouveau is used initially, but the config-file modeset overrides that for the continuation of the use of nouveau. For my PC, I infer that the initial usage (whatever that actually is) works no matter how the mode is set, or not set at all. After that, it works only if the mode is "1".
I imagine that your PC is not so tolerant for the inital usage of nouveau, but once the mode is set to "1" by the (existing) config file, it works just fine. So, I think you are forced to use the nouveau.modeset parameter to get past the initial use of nouveau.
As I have no idea what is being done in the setup of the graphics drivers, this is about as far as I can go. Obviously, my auto_modeset package is useless, since it affects only what happens after the initial usage of nouveau. I hope this helps 01micko to focus on that initial phase to determine what it is that is affected by the boot argument, before the config file supercedes it.
Thank you, again, for reporting and working this issue.
Richard