Re: new nvidia long term 346.35

--===============6968112996300085751==
Content-Type: multipart/alternative; boundary=001a113a3bf810a1bc050d07a9ee

--001a113a3bf810a1bc050d07a9ee
Content-Type: text/plain; charset=UTF-8

On Mon Jan 19 2015 at 12:39:50 PM Stephen Collier <[email protected]>
wrote:

> 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

--001a113a3bf810a1bc050d07a9ee
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">On Mon Jan 19 2015 at 12:39:50 PM Stephen Collie=
r &lt;<a href=3D"mailto:[email protected]">[email protected]</a>&=
gt; wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">On 19/01/2015 8:27 pm, mo.ucin=
a wrote:<br>
&gt; Hello Stephen,<br>
&gt;<br>
&gt; Can you please run a set of packages on this one when time permits .<b=
r>
&gt; On another topic I am on the rev 169 of the current 340.65 drivers for=
<br>
&gt; el7 64bit. I know that 170 had a small bug , which prompted the 171<br=
>
&gt; release . I tried the 171 but it gave me stuttered video on mythtv .<b=
r>
&gt; Have you tried it your self , is it working ok for you ? So I have<br>
&gt; fallen back to 169 for the time being .<br>
&gt;<br>
&gt; Best Regards<br>
&gt; Milorad<br>
&gt;<br>
Milorad,<br>
<br>
I&#39;m running 171 release on el6 x86_64 and f19 i386 which seem OK. There=
<br>
may be something different as they are created in a completely different<br=
>
way due to the creation on a vm now. I&#39;ll have a look and see if I can<=
br>
find any more differences between 169 and 171.<br>
<br>
On the 365 front it should be built automatically - I&#39;ll check the scri=
pt.<br></blockquote><div><br></div><div>I had issues with vpdau on the late=
st packages (.65) on el7 x86_64.=C2=A0 I had to move the files for vdpau ar=
ound to match what was in the .58 packages and move some symlinks to get ev=
erything working again.=C2=A0 My apologies but I didn&#39;t document exactl=
y what the issue was, was just trying to get the frontend running again and=
 didn&#39;t take good notes :( =C2=A0Sufficed to say, some of the vdpau rel=
ated files had changed locations, etc.=C2=A0 Other than vdpau, everything s=
eems to be running okay now.</div><div><br></div><div>Derek</div></div>

--001a113a3bf810a1bc050d07a9ee--


--===============6968112996300085751==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
atrpms-users mailing list
[email protected]
http://lists.atrpms.net/mailman/listinfo/atrpms-users
--===============6968112996300085751==--