Re: [ATrpms-users] new nvidia long term 346.35

[mo.ucina]

Hello Guys, I just loaded nvidia-graphics346.35-346.35-172.el7.x86_64 and can not boot into graphic mode at all . There may be some other things in there as well . I am going to fall back to 169 . Best Regards Milorad On 20/01/15 09:41, Stephen Collier wrote: Thanks I'll make the changes. Stephen Sent from my Samsung GALAXY S4 on the Telstra 4G network <div>-------- Original message --------</div><div>From: NullDev <nullde...@gmail.com> </div><div>Date:20/01/2015 8:26 AM (GMT+10:00) </div><div>To: "User discussion about ATrpms.net" <atrpms-users@atrpms.net> </div><div>Subject: Re: [ATrpms-users] new nvidia long term 346.35 </div><div> </div>I had similar issues.  I ended up creating 2 symlinks and the problem went away: /usr/lib64/vdpau/libvdpau_nvidia.so.1 -> ../nvidia-graphics-343.36/vdpau/libvdpau_nvidia.so.1 and /usr/lib64/vdpau/libvdpau_nvidia.so -> libvdpau_nvidia.so.1 Derek Burt Monday, January 19, 2015 4:03 PM judi...@bigpond.net.au On 19/01/2015 8:27 pm, mo.ucina wrote: Hello Stephen, Can you please run a set of packages on this one when time permits . On another topic I am on the rev 169 of the current 340.65 drivers for el7 64bit. I know that 170 had a small bug , which prompted the 171 release . I tried the 171 but it gave me stuttered video on mythtv . Have you tried it your self , is it working ok for you ? So I have fallen back to 169 for the time being . Best Regards Milorad Milorad, I'm running 171 release on el6 x86_64 and f19 i386 which seem OK. There may be something different as they are created in a completely different way due to the creation on a vm now. I'll have a look and see if I can find any more differences between 169 and 171. On the 365 front it should be built automatically - I'll check the script. I had issues with vpdau on the latest packages (.65) on el7 x86_64.  I had to move the files for vdpau around to match what was in the .58 packages and move some symlinks to get everything working again.  My apologies but I didn't document exactly what the issue was, was just trying to get the frontend running again and didn't take good notes :(  Sufficed to say, some of the vdpau related files had changed locations, etc.  Other than vdpau, everything seems to be running okay now. Derek _______________________________________________ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users Thanks I'll make the changes. Stephen Sent from my Samsung GALAXY S4 on the Telstra 4G network -------- Original message -------- From: NullDev Date:20/01/2015 8:26 AM (GMT+10:00) To: "User discussion about ATrpms.net" Subject: Re: [ATrpms-users] new nvidia long term 346.35 I had similar issues.  I ended up creating 2 symlinks and the problem went away: /usr/lib64/vdpau/libvdpau_nvidia.so.1 -> ../nvidia-graphics-343.36/vdpau/libvdpau_nvidia.so.1 and /usr/lib64/vdpau/libvdpau_nvidia.so -> libvdpau_nvidia.so.1 Derek Burt Monday, January 19, 2015 4:03 PM judi...@bigpond.net.au On 19/01/2015 8:27 pm, mo.ucina wrote: > Hello Stephen, > > Can you please run a set of packages on this one when time permits . > On another topic I am on the rev 169 of the current 340.65 drivers for > el7 64bit. I know that 170 had a small bug , which prompted the 171 > release . I tried the 171 but it gave me stuttered video on mythtv . > Have you tried it your self , is it working ok for you ? So I have > fallen back to 169 for the time being . > > Best Regards > Milorad > Milorad, I'm running 171 release on el6 x86_64 and f19 i386 which seem OK. There may be something different as they are created in a completely different way due to the creation on a vm now. I'll have a look and see if I can find any more differences between 169 and 171. On the 365 front it should be built automatically - I'll check the script. I had issues with vpdau on the latest packages (.65) on el7 x86_64.  I had to move the files for vdpau around to match what was in the .58 packages and move some symlinks to get everything working again.  My apologies but I didn't document exactly what the issue was, was just trying to get the frontend running again and didn't take good notes :(  Sufficed to say, some of the vdpau related files had changed locations, etc.  Other than vdpau, everything seems to be running okay now. Derek _______________________________________________ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users _______________________________________________ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users

_______________________________________________
atrpms-users mailing list
atrpms-users@atrpms.net
http://lists.atrpms.net/mailman/listinfo/atrpms-users