[elrepo] kmod-nvidia: display not found

Todd And Margo Chester toddandmargo at gmail.com
Mon Mar 26 03:03:46 EDT 2012


On 03/25/2012 04:20 AM, Phil Perry wrote:
> On 25/03/12 03:13, Todd And Margo Chester wrote:
>> On 03/24/2012 04:59 PM, Phil Perry wrote:
>>> Please try renaming the file above to /etc/X11/xorg.conf
>>
>> Hi Phil,
>>
>> Wow.  You called it.
>>
>> When I first went to "init 3", I made a link
>>
>>        ln -s /etc/X11/XF86Config /etc/X11/xorg.conf
>>
>> After I installed the kmod-nvidia drivers, I recheck
>> the /etc/X11 directory:
>>
>> #ls -al /etc/X11
>> total 56
>> drwxr-xr-x.   6 root root  4096 Mar 24 18:45 .
>> drwxr-xr-x. 125 root root 12288 Mar 24 18:45 ..
>> drwxr-xr-x.   2 root root  4096 Jul 20  2011 applnk
>> drwxr-xr-x.   2 root root  4096 Jul 20  2011 fontpath.d
>> -rwxr-xr-x.   1 root root  1328 Dec 10 15:19 prefdm
>> -rw-r--r--.   1 root root  1479 Mar 24 18:45 XF86Config
>> -rw-r--r--.   1 root root  1479 Mar 24 18:45 XF86Config.backup
>> -rw-r--r--.   1 root root  1722 Mar 24 18:45 XF86Config.backup-nvidia
>> drwxr-xr-x.   4 root root  4096 Nov 26 16:29 xinit
>> -rw-r--r--.   1 root root   547 Nov 24  2010 Xmodmap
>> drwxr-xr-x.   2 root root  4096 Dec 15 06:44 xorg.conf.d
>> lrwxrwxrwx.   1 root root    19 Mar 24 18:22 xorg.conf.elreposave ->
>> /etc/X11/XF86Config
>> -rw-r--r--.   1 root root   493 Nov 24  2010 Xresources
>>
>> You will notice that my "xorg.conf" link got renamed
>> "xorg.conf.elreposave" and a new "xorg.conf" was never
>> recreated.
>>
>> Me thinks that
>>         # nvidia-xconfig
>>           Using X configuration file: "/etc/X11/xorg.conf".
>>           Backed up file '/etc/X11/xorg.conf' as \
>>                '/etc/X11/xorg.conf.backup'
>>           New X configuration file written to '/etc/X11/xorg.conf'
>>
>> was never called by the post install scripts as there
>> was no xorg.conf.
>>
>> Renaming the link "/etc/X11/xorg.conf.backup" to "/etc/X11/xorg.conf"
>> and rebooting fixed the problem.
>>
>> Question: does ELRepo have a bug tracker?  Or is reporting the
>> bug here enough?
>>
>> Thank you so much.  This problem about drove me nuts!
>>
>> -T
>>
>>
>
> Well, that got to the bottom of that.
>
> I don't believe there is a bug in the elrepo packaging of the nvidia
> drivers, but rather for some reason nvidia-xconfig doesn't seem to
> recognise that you have X.org and thinks your X server is XFree86. That
> is why nvidia-xconfig has created /etc/X11/XF86Config instead of
> /etc/X11/xorg.conf (or did you manualy create this?)
>
> Here's the relevant entry from the manpage:
>
> The system X configuration file is found and read into memory. If no
> configuration file can be found, nvidia-xconfig generates one from
> scratch using default settings; in this case, nvidia-xconfig  will
> automatically determine the name of the X configuration file to create:
> /etc/X11/xorg.conf if the X server in use is X.org or
> /etc/X11/XF86Config if the X server in use is XFree86.
>
> The elrepo package, in the %post install script, checks for the
> existence of  /etc/X11/xorg.conf and if it exists then backs it up as
> /etc/X11/xorg.conf.elreposave. We then run nvidia-xconfig to generate a
> new clean default /etc/X11/xorg.conf file. In your case it does look
> like nvidia-xconfig generated /etc/X11/XF86Config instead.
>
> If you can demonstrate this behaviour on a new clean install of SL6
> (with a fully functional X Server installed) then you have a case to
> report a bug.

Hi Phil,

The plot thickens.

/usr/bin/nvidia-xconfig does work correctly as root from the
command prompt.

I took a look at the post install script:

     # Check if xorg.conf exists, if it does, backup and remove [BugID # 
0000127]
     [ -f /etc/X11/xorg.conf ] && \
       mv /etc/X11/xorg.conf /etc/X11/xorg.conf.elreposave &>/dev/null

Okay, we got to this point as I found my xorg.conf renamed to elreposave

     # xorg.conf now shouldn't exist so create it
     [ ! -f /etc/X11/xorg.conf ] && /usr/bin/nvidia-xconfig &>/dev/null

But this did not work.  A new xorg.conf was not created.  nvidia-xconfig
should have been called as there was no xorg.conf

So, the 64 thousand dollar question is why did nvidia-xconfig works
from the command prompt but not from the post install script?  I do
believe nvidia-xconfig does not think I am using xorg when run from
the post install script and does think it when I run it from the
command prompt.

And, nvidia-xconfig is a binary file, so I can not see what it is
doing to determine if I am using xorg or not.

The new driver is running circles around nouveau.  Thank you
so much for the help!

-T







More information about the elrepo mailing list