[elrepo] Intel video on CentOS 6.4 - SOLVED!
Phil Perry
phil at elrepo.org
Sat Oct 5 09:39:09 EDT 2013
On 04/10/13 21:40, Andrey Zhunev wrote:
>
> Thursday, October 3, 2013, 7:10:27 AM, you wrote:
>
>
>> Thursday, October 3, 2013, 12:52:20 AM, you wrote:
>
>>> On Wed, Oct 2, 2013 at 12:11 PM, Andrey Zhunev <a-j at a-j.ru> wrote:
>>>> How do I know that the correct video driver is loaded?
>>>>
>>>> The reason for my question is the following lines in mythfrontend log:
>>>>
>>>> CoreContext mythrender_opengl.cpp:66 (Create) - OpenGL: Could not determine whether Sync to VBlank is enabled.
>>>> CoreContext mythrender_opengl.cpp:142 (IsRecommendedRenderer) - OpenGL: OpenGL is using software rendering.
>>>>
>>>> And VAAPI or OpenGL-based video playback ends up with a black screen.
>>>> Not sure if it's a mythtv misconfiguration, or something is wrong with
>>>> the video driver... I suspect the latter, but I'm out of ideas how I
>>>> could dig this further.
>>>>
>>>>
>>>> Xorg.0.log: http://pastebin.com/raw.php?i=EeYGyWuh
>
>>> Your X log file indicates that the intel driver is in use. Does lsmod
>>> show the i915 module?
>
>>> I cannot help with vaapi because I'm not familiar with it.
>
>> Yes:
>
>> # lsmod |grep i915
>> i915 537570 2
>> drm_kms_helper 40087 1 i915
>> drm 265638 3 i915,drm_kms_helper
>> i2c_algo_bit 5935 2 saa716x_tbs_dvb,i915
>> i2c_core 31084 20
>> i2c_i801,tbs6985fe,saa716x_tbs_dvb,tbs6991se,tbs6928fe,tbs6922fe,saa716x_core,tbs6618fe,tbs6991fe,tbs6982se,tbs6928se,tbs6985se,tbs6923fe,stv090x,tbs6680fe,tbs6982fe,i915,drm_kms_helper,drm,i2c_algo_bit
>> video 20674 1 i915
>
>
>> I guess it's working then...
>> Is there a way to forcibly set 'Sync to VBlank' to ON ?
>
>> I don't know why Myth could not determine its state, but I guess
>> that's the reason why it does not display video when configured to use
>> VAAPI or OpenGL.
>
>
>
> I found it! It was an old installation of NVidia proprietary driver,
> that did not get completely uninstalled. libGL.so was still linked to
> an NVidia library. I don't know why, and I have no idea why the proper
> link was not restored when I reinstalled the package. So I had to
> manually update the link, and everything just worked!
>
> The correct config is:
>
> # ls -l /usr/lib64/libGL*
> lrwxrwxrwx 1 root root 10 Oct 4 20:12 /usr/lib64/libGL.so -> libGL.so.1
> lrwxrwxrwx 1 root root 12 Oct 4 20:29 /usr/lib64/libGL.so.1 -> libGL.so.1.2
> -rwxr-xr-x 1 root root 543352 Feb 11 2013 /usr/lib64/libGL.so.1.2
> -rwxr-xr-x 1 root root 532864 Jun 3 22:22 /usr/lib64/libGL.so.1.2.0
> -rwxr-xr-x 1 root root 1056992 May 31 2012 /usr/lib64/libGL.so.295.53
> -rwxr-xr-x 1 root root 1057600 Nov 19 2012 /usr/lib64/libGL.so.295.75
> -rwxr-xr-x 1 root root 1078720 Aug 21 2012 /usr/lib64/libGL.so.304.37
> -rwxr-xr-x 1 root root 1078720 Nov 1 2012 /usr/lib64/libGL.so.304.60
> lrwxrwxrwx 1 root root 11 Oct 4 20:12 /usr/lib64/libGLU.so -> libGLU.so.1
> lrwxrwxrwx 1 root root 19 Oct 4 20:12 /usr/lib64/libGLU.so.1 -> libGLU.so.1.3.08005
> -rwxr-xr-x 1 root root 451544 Feb 11 2013 /usr/lib64/libGLU.so.1.3.08005
>
> Those *.295.53 - *.305.60 are old NVidia libraries that were not removed.
>
The above is an excellent example of why we recommend using the elrepo
packaged drivers for nvidia users. The nvidia proprietary installer does
some horrible things that can end up resulting in broken systems as
testified by your troubles.
Anyway, glad you got your issues resolved!
Phil
More information about the elrepo
mailing list