Mailing List Archive

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.

Cheers
Stephen

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

On Mon Jan 19 2015 at 12:39:50 PM Stephen Collier <judithc@bigpond.net.au>
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

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 <mailto:derekburt@gmail.com>
> Monday, January 19, 2015 4:03 PM
> judithc@bigpond.net.au <mailto:judithc@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

<div>-------- Original message --------</div><div>From: NullDev <nulldev42@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
judithc@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

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 <nulldev42@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 judithc@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"]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 judithc@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"]http://lists.atrpms.net/mailman/listinfo/atrpms-users

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

Here is the errors from the log :

Jan 20 14:14:17 htpc gdm: Child process 1100 was already dead.
Jan 20 14:14:17 htpc gdm: GLib-GObject: g_object_ref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:17 htpc gdm: GLib-GObject: g_object_unref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:17 htpc systemd: Started Wait for Plymouth Boot Screen to Quit.
Jan 20 14:14:17 htpc dbus-daemon: dbus[1037]: [system] Rejected send
message, 1 matched rules; type="method_call", sender=":1.5" (uid=0
pid=1049 comm="/usr/sbin/gdm ")
interface="org.freedesktop.DBus.Properties" member="GetAll" error
name="(unset)" requested_reply="0" destination=":1.13" (uid=0 pid=2949
comm="/usr/libexec/gdm-simple-slave --display-id /org/gn")
Jan 20 14:14:17 htpc dbus[1037]: [system] Rejected send message, 1
matched rules; type="method_call", sender=":1.5" (uid=0 pid=1049
comm="/usr/sbin/gdm ") interface="org.freedesktop.DBus.Properties"
member="GetAll" error name="(unset)" requested_reply="0"
destination=":1.13" (uid=0 pid=2949 comm="/usr/libexec/gdm-simple-slave
--display-id /org/gn")
Jan 20 14:14:18 htpc gdm: Child process 2954 was already dead.
Jan 20 14:14:18 htpc gdm: GLib-GObject: g_object_ref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:18 htpc gdm: GLib-GObject: g_object_unref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:18 htpc gdm: GdmDisplay: display lasted 0.052607 seconds
Jan 20 14:14:18 htpc dbus-daemon: dbus[1037]: [system] Rejected send
message, 1 matched rules; type="method_call", sender=":1.5" (uid=0
pid=1049 comm="/usr/sbin/gdm ")
interface="org.freedesktop.DBus.Properties" member="GetAll" error
name="(unset)" requested_reply="0" destination=":1.14" (uid=0 pid=2955
comm="/usr/libexec/gdm-simple-slave --display-id /org/gn")
Jan 20 14:14:18 htpc dbus[1037]: [system] Rejected send message, 1
matched rules; type="method_call", sender=":1.5" (uid=0 pid=1049
comm="/usr/sbin/gdm ") interface="org.freedesktop.DBus.Properties"
member="GetAll" error name="(unset)" requested_reply="0"
destination=":1.14" (uid=0 pid=2955 comm="/usr/libexec/gdm-simple-slave
--display-id /org/gn")
Jan 20 14:14:18 htpc gdm: Child process 2960 was already dead.
Jan 20 14:14:18 htpc gdm: GLib-GObject: g_object_ref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:18 htpc gdm: GLib-GObject: g_object_unref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:18 htpc gdm: GdmDisplay: display lasted 0.051834 seconds
Jan 20 14:14:18 htpc avahi-daemon[988]: Registering new address record
for fe80::5246:5dff:fe50:b5ca on enp5s0.*.
Jan 20 14:14:18 htpc dbus-daemon: dbus[1037]: [system] Rejected send
message, 1 matched rules; type="method_call", sender=":1.5" (uid=0
pid=1049 comm="/usr/sbin/gdm ")
interface="org.freedesktop.DBus.Properties" member="GetAll" error
name="(unset)" requested_reply="0" destination=":1.15" (uid=0 pid=2961
comm="/usr/libexec/gdm-simple-slave --display-id /org/gn")
Jan 20 14:14:18 htpc dbus[1037]: [system] Rejected send message, 1
matched rules; type="method_call", sender=":1.5" (uid=0 pid=1049
comm="/usr/sbin/gdm ") interface="org.freedesktop.DBus.Properties"
member="GetAll" error name="(unset)" requested_reply="0"
destination=":1.15" (uid=0 pid=2961 comm="/usr/libexec/gdm-simple-slave
--display-id /org/gn")
Jan 20 14:14:18 htpc gdm: Child process 2966 was already dead.
Jan 20 14:14:18 htpc gdm: GLib-GObject: g_object_ref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:18 htpc gdm: GLib-GObject: g_object_unref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:18 htpc gdm: GdmDisplay: display lasted 0.257969 seconds
Jan 20 14:14:18 htpc dbus-daemon: dbus[1037]: [system] Rejected send
message, 1 matched rules; type="method_call", sender=":1.5" (uid=0
pid=1049 comm="/usr/sbin/gdm ")
interface="org.freedesktop.DBus.Properties" member="GetAll" error
name="(unset)" requested_reply="0" destination=":1.16" (uid=0 pid=2967
comm="/usr/libexec/gdm-simple-slave --display-id /org/gn")
Jan 20 14:14:18 htpc dbus[1037]: [system] Rejected send message, 1
matched rules; type="method_call", sender=":1.5" (uid=0 pid=1049
comm="/usr/sbin/gdm ") interface="org.freedesktop.DBus.Properties"
member="GetAll" error name="(unset)" requested_reply="0"
destination=":1.16" (uid=0 pid=2967 comm="/usr/libexec/gdm-simple-slave
--display-id /org/gn")
Jan 20 14:14:18 htpc gdm: Child process 2972 was already dead.
Jan 20 14:14:18 htpc gdm: GLib-GObject: g_object_ref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:18 htpc gdm: GLib-GObject: g_object_unref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:18 htpc gdm: GdmDisplay: display lasted 0.052946 seconds
Jan 20 14:14:18 htpc dbus-daemon: dbus[1037]: [system] Rejected send
message, 1 matched rules; type="method_call", sender=":1.5" (uid=0
pid=1049 comm="/usr/sbin/gdm ")
interface="org.freedesktop.DBus.Properties" member="GetAll" error
name="(unset)" requested_reply="0" destination=":1.17" (uid=0 pid=2974
comm="/usr/libexec/gdm-simple-slave --display-id /org/gn")
Jan 20 14:14:18 htpc dbus[1037]: [system] Rejected send message, 1
matched rules; type="method_call", sender=":1.5" (uid=0 pid=1049
comm="/usr/sbin/gdm ") interface="org.freedesktop.DBus.Properties"
member="GetAll" error name="(unset)" requested_reply="0"
destination=":1.17" (uid=0 pid=2974 comm="/usr/libexec/gdm-simple-slave
--display-id /org/gn")
Jan 20 14:14:18 htpc gdm: Child process 2979 was already dead.
Jan 20 14:14:18 htpc gdm: GLib-GObject: g_object_ref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:18 htpc gdm: GLib-GObject: g_object_unref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:18 htpc gdm: GdmDisplay: display lasted 0.266998 seconds
Jan 20 14:14:18 htpc dbus-daemon: dbus[1037]: [system] Rejected send
message, 1 matched rules; type="method_call", sender=":1.5" (uid=0
pid=1049 comm="/usr/sbin/gdm ")
interface="org.freedesktop.DBus.Properties" member="GetAll" error
name="(unset)" requested_reply="0" destination=":1.18" (uid=0 pid=2988
comm="/usr/libexec/gdm-simple-slave --display-id /org/gn")
Jan 20 14:14:18 htpc dbus[1037]: [system] Rejected send message, 1
matched rules; type="method_call", sender=":1.5" (uid=0 pid=1049
comm="/usr/sbin/gdm ") interface="org.freedesktop.DBus.Properties"
member="GetAll" error name="(unset)" requested_reply="0"
destination=":1.18" (uid=0 pid=2988 comm="/usr/libexec/gdm-simple-slave
--display-id /org/gn")
Jan 20 14:14:18 htpc NetworkManager[983]: <info> Policy set 'enp5s0'
(enp5s0) as default for IPv4 routing and DNS.
Jan 20 14:14:18 htpc gdm: Child process 2993 was already dead.
Jan 20 14:14:18 htpc gdm: GLib-GObject: g_object_ref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:18 htpc gdm: GLib-GObject: g_object_unref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:18 htpc gdm: GdmDisplay: display lasted 0.051764 seconds
Jan 20 14:14:18 htpc gdm: GdmLocalDisplayFactory: maximum number of X
display failures reached: check X server log for errors



On 20/01/15 14:17, mo.ucina wrote:
> 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<nulldev42@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
>> judithc@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 <mailto:derekburt@gmail.com>
>>> Monday, January 19, 2015 4:03 PM
>>> judithc@bigpond.net.au <mailto:judithc@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

The 365 version was automatically built. It does not have any of the vdpau fixes applied. Originally nvidia stated that it was only going to work on very new chips and the 200 series was going legacy on a legacy 340 series drivers. I couldn't find anything in release notes. 

I'll check more closely. 

Cheers
Stephen

Sent from my Samsung GALAXY S4 on the Telstra 4G network

<div>-------- Original message --------</div><div>From: "mo.ucina" <mo.ucina@gmail.com> </div><div>Date:20/01/2015 2:17 PM (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>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:

Check what /var/log/Xorg.0.log shows 

It should show more informative information. 

Cheers
Stephen



Sent from my Samsung GALAXY S4 on the Telstra 4G network

<div>-------- Original message --------</div><div>From: "mo.ucina" <mo.ucina@gmail.com> </div><div>Date:20/01/2015 3:08 PM (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>Here is the errors from the log :

Jan 20 14:14:17 htpc gdm: Child process 1100 was already dead.
Jan 20 14:14:17 htpc gdm: GLib-GObject: g_object_ref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:17 htpc gdm: GLib-GObject: g_object_unref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:17 htpc systemd: Started Wait for Plymouth Boot Screen to Quit.
Jan 20 14:14:17 htpc dbus-daemon: dbus[1037]: [system] Rejected send
message, 1 matched rules; type="method_call", sender=":1.5" (uid=0
pid=1049 comm="/usr/sbin/gdm ")
interface="org.freedesktop.DBus.Properties" member="GetAll" error
name="(unset)" requested_reply="0" destination=":1.13" (uid=0 pid=2949
comm="/usr/libexec/gdm-simple-slave --display-id /org/gn")
Jan 20 14:14:17 htpc dbus[1037]: [system] Rejected send message, 1
matched rules; type="method_call", sender=":1.5" (uid=0 pid=1049
comm="/usr/sbin/gdm ") interface="org.freedesktop.DBus.Properties"
member="GetAll" error name="(unset)" requested_reply="0"
destination=":1.13" (uid=0 pid=2949 comm="/usr/libexec/gdm-simple-slave
--display-id /org/gn")
Jan 20 14:14:18 htpc gdm: Child process 2954 was already dead.
Jan 20 14:14:18 htpc gdm: GLib-GObject: g_object_ref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:18 htpc gdm: GLib-GObject: g_object_unref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:18 htpc gdm: GdmDisplay: display lasted 0.052607 seconds
Jan 20 14:14:18 htpc dbus-daemon: dbus[1037]: [system] Rejected send
message, 1 matched rules; type="method_call", sender=":1.5" (uid=0
pid=1049 comm="/usr/sbin/gdm ")
interface="org.freedesktop.DBus.Properties" member="GetAll" error
name="(unset)" requested_reply="0" destination=":1.14" (uid=0 pid=2955
comm="/usr/libexec/gdm-simple-slave --display-id /org/gn")
Jan 20 14:14:18 htpc dbus[1037]: [system] Rejected send message, 1
matched rules; type="method_call", sender=":1.5" (uid=0 pid=1049
comm="/usr/sbin/gdm ") interface="org.freedesktop.DBus.Properties"
member="GetAll" error name="(unset)" requested_reply="0"
destination=":1.14" (uid=0 pid=2955 comm="/usr/libexec/gdm-simple-slave
--display-id /org/gn")
Jan 20 14:14:18 htpc gdm: Child process 2960 was already dead.
Jan 20 14:14:18 htpc gdm: GLib-GObject: g_object_ref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:18 htpc gdm: GLib-GObject: g_object_unref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:18 htpc gdm: GdmDisplay: display lasted 0.051834 seconds
Jan 20 14:14:18 htpc avahi-daemon[988]: Registering new address record
for fe80::5246:5dff:fe50:b5ca on enp5s0.*.
Jan 20 14:14:18 htpc dbus-daemon: dbus[1037]: [system] Rejected send
message, 1 matched rules; type="method_call", sender=":1.5" (uid=0
pid=1049 comm="/usr/sbin/gdm ")
interface="org.freedesktop.DBus.Properties" member="GetAll" error
name="(unset)" requested_reply="0" destination=":1.15" (uid=0 pid=2961
comm="/usr/libexec/gdm-simple-slave --display-id /org/gn")
Jan 20 14:14:18 htpc dbus[1037]: [system] Rejected send message, 1
matched rules; type="method_call", sender=":1.5" (uid=0 pid=1049
comm="/usr/sbin/gdm ") interface="org.freedesktop.DBus.Properties"
member="GetAll" error name="(unset)" requested_reply="0"
destination=":1.15" (uid=0 pid=2961 comm="/usr/libexec/gdm-simple-slave
--display-id /org/gn")
Jan 20 14:14:18 htpc gdm: Child process 2966 was already dead.
Jan 20 14:14:18 htpc gdm: GLib-GObject: g_object_ref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:18 htpc gdm: GLib-GObject: g_object_unref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:18 htpc gdm: GdmDisplay: display lasted 0.257969 seconds
Jan 20 14:14:18 htpc dbus-daemon: dbus[1037]: [system] Rejected send
message, 1 matched rules; type="method_call", sender=":1.5" (uid=0
pid=1049 comm="/usr/sbin/gdm ")
interface="org.freedesktop.DBus.Properties" member="GetAll" error
name="(unset)" requested_reply="0" destination=":1.16" (uid=0 pid=2967
comm="/usr/libexec/gdm-simple-slave --display-id /org/gn")
Jan 20 14:14:18 htpc dbus[1037]: [system] Rejected send message, 1
matched rules; type="method_call", sender=":1.5" (uid=0 pid=1049
comm="/usr/sbin/gdm ") interface="org.freedesktop.DBus.Properties"
member="GetAll" error name="(unset)" requested_reply="0"
destination=":1.16" (uid=0 pid=2967 comm="/usr/libexec/gdm-simple-slave
--display-id /org/gn")
Jan 20 14:14:18 htpc gdm: Child process 2972 was already dead.
Jan 20 14:14:18 htpc gdm: GLib-GObject: g_object_ref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:18 htpc gdm: GLib-GObject: g_object_unref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:18 htpc gdm: GdmDisplay: display lasted 0.052946 seconds
Jan 20 14:14:18 htpc dbus-daemon: dbus[1037]: [system] Rejected send
message, 1 matched rules; type="method_call", sender=":1.5" (uid=0
pid=1049 comm="/usr/sbin/gdm ")
interface="org.freedesktop.DBus.Properties" member="GetAll" error
name="(unset)" requested_reply="0" destination=":1.17" (uid=0 pid=2974
comm="/usr/libexec/gdm-simple-slave --display-id /org/gn")
Jan 20 14:14:18 htpc dbus[1037]: [system] Rejected send message, 1
matched rules; type="method_call", sender=":1.5" (uid=0 pid=1049
comm="/usr/sbin/gdm ") interface="org.freedesktop.DBus.Properties"
member="GetAll" error name="(unset)" requested_reply="0"
destination=":1.17" (uid=0 pid=2974 comm="/usr/libexec/gdm-simple-slave
--display-id /org/gn")
Jan 20 14:14:18 htpc gdm: Child process 2979 was already dead.
Jan 20 14:14:18 htpc gdm: GLib-GObject: g_object_ref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:18 htpc gdm: GLib-GObject: g_object_unref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:18 htpc gdm: GdmDisplay: display lasted 0.266998 seconds
Jan 20 14:14:18 htpc dbus-daemon: dbus[1037]: [system] Rejected send
message, 1 matched rules; type="method_call", sender=":1.5" (uid=0
pid=1049 comm="/usr/sbin/gdm ")
interface="org.freedesktop.DBus.Properties" member="GetAll" error
name="(unset)" requested_reply="0" destination=":1.18" (uid=0 pid=2988
comm="/usr/libexec/gdm-simple-slave --display-id /org/gn")
Jan 20 14:14:18 htpc dbus[1037]: [system] Rejected send message, 1
matched rules; type="method_call", sender=":1.5" (uid=0 pid=1049
comm="/usr/sbin/gdm ") interface="org.freedesktop.DBus.Properties"
member="GetAll" error name="(unset)" requested_reply="0"
destination=":1.18" (uid=0 pid=2988 comm="/usr/libexec/gdm-simple-slave
--display-id /org/gn")
Jan 20 14:14:18 htpc NetworkManager[983]: <info> Policy set 'enp5s0'
(enp5s0) as default for IPv4 routing and DNS.
Jan 20 14:14:18 htpc gdm: Child process 2993 was already dead.
Jan 20 14:14:18 htpc gdm: GLib-GObject: g_object_ref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:18 htpc gdm: GLib-GObject: g_object_unref: assertion
`object->ref_count > 0' failed
Jan 20 14:14:18 htpc gdm: GdmDisplay: display lasted 0.051764 seconds
Jan 20 14:14:18 htpc gdm: GdmLocalDisplayFactory: maximum number of X
display failures reached: check X server log for errors



On 20/01/15 14:17, mo.ucina wrote:
> 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<nulldev42@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
>> judithc@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 <mailto:derekburt@gmail.com>
>>> Monday, January 19, 2015 4:03 PM
>>> judithc@bigpond.net.au <mailto:judithc@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

On 20/01/2015 2:17 pm, mo.ucina wrote:
> 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<nulldev42@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
>> judithc@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 <mailto:derekburt@gmail.com>
>>> Monday, January 19, 2015 4:03 PM
>>> judithc@bigpond.net.au <mailto:judithc@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
I'm looking at 346.35 at the moment as it has some issues with el6
requiring gtk3. I should have some resolution over the next day.

the linking problems should be fixed by running nvidia-graphics-switch

Cheers
Stephen

> Stephen Collier <mailto:judithc@bigpond.net.au>
> Wednesday, January 21, 2015 1:40 AM
> I'm looking at 346.35 at the moment as it has some issues with el6
> requiring gtk3. I should have some resolution over the next day.
>
> the linking problems should be fixed by running nvidia-graphics-switch
>
> Cheers
> Stephen
> _______________________________________________
> atrpms-users mailing list
> atrpms-users@atrpms.net
> http://lists.atrpms.net/mailman/listinfo/atrpms-users
> mo.ucina <mailto:mo.ucina@gmail.com>
> Monday, January 19, 2015 10:17 PM
> 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:
>
> _______________________________________________
> atrpms-users mailing list
> atrpms-users@atrpms.net
> http://lists.atrpms.net/mailman/listinfo/atrpms-users
> Stephen Collier <mailto:judithc@bigpond.net.au>
> Monday, January 19, 2015 5:41 PM
> 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
> <nulldev42@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
> judithc@bigpond.net.au
> 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

For whatever reason, "nvidia-graphics-switch" works on my centos6 box,
but fails on my centos7 box with the following error. Perhaps it is
related?

# nvidia-graphics-switch 343.36

Traceback (most recent call last):
File "/usr/lib64/nvidia-graphics-helpers/nvidia-config-x.py", line 6,
in <module>
import xf86config
ImportError: No module named xf86config

I've looked and either I'm blind (highly likely) or that module isn't
available for centos7.

On 21/01/2015 12:56, NullDev wrote:
>
>
>> Stephen Collier <mailto:judithc@bigpond.net.au>
>> Wednesday, January 21, 2015 1:40 AM
>> I'm looking at 346.35 at the moment as it has some issues with el6
>> requiring gtk3. I should have some resolution over the next day.
>>
>> the linking problems should be fixed by running nvidia-graphics-switch
>>
>> Cheers
>> Stephen
>> _______________________________________________
>> atrpms-users mailing list
>> atrpms-users@atrpms.net
>> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>> mo.ucina <mailto:mo.ucina@gmail.com>
>> Monday, January 19, 2015 10:17 PM
>> 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:
>>
>> _______________________________________________
>> atrpms-users mailing list
>> atrpms-users@atrpms.net
>> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>> Stephen Collier <mailto:judithc@bigpond.net.au>
>> Monday, January 19, 2015 5:41 PM
>> 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
>> <nulldev42@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
>> judithc@bigpond.net.au
>> 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
>
> For whatever reason, "nvidia-graphics-switch" works on my centos6 box,
> but fails on my centos7 box with the following error. Perhaps it is
> related?
>
> # nvidia-graphics-switch 343.36
>
> Traceback (most recent call last):
> File "/usr/lib64/nvidia-graphics-helpers/nvidia-config-x.py", line
> 6, in <module>
> import xf86config
> ImportError: No module named xf86config
>
> I've looked and either I'm blind (highly likely) or that module isn't
> available for centos7.
>
This error has been around for ages:

http://lists.atrpms.net/pipermail/atrpms-users/2013-June/013739.html

It would be nice to get it sorted, I have no idea how but I have great
faith in Stephen :)

Dunc

Duncan Brown wrote:
> On 21/01/2015 12:56, NullDev wrote:
>>
>>
>>> Stephen Collier <mailto:judithc@bigpond.net.au>
>>> Wednesday, January 21, 2015 1:40 AM
>>> I'm looking at 346.35 at the moment as it has some issues with el6
>>> requiring gtk3. I should have some resolution over the next day.
>>>
>>> the linking problems should be fixed by running nvidia-graphics-switch
>>>
>>> Cheers
>>> Stephen
>>> _______________________________________________
>>> atrpms-users mailing list
>>> atrpms-users@atrpms.net
>>> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>>> mo.ucina <mailto:mo.ucina@gmail.com>
>>> Monday, January 19, 2015 10:17 PM
>>> 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:
>>>
>>> _______________________________________________
>>> atrpms-users mailing list
>>> atrpms-users@atrpms.net
>>> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>>> Stephen Collier <mailto:judithc@bigpond.net.au>
>>> Monday, January 19, 2015 5:41 PM
>>> 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
>>> <nulldev42@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
>>> judithc@bigpond.net.au
>>> 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
>>
>> For whatever reason, "nvidia-graphics-switch" works on my centos6 box,
>> but fails on my centos7 box with the following error. Perhaps it is
>> related?
>>
>> # nvidia-graphics-switch 343.36
>>
>> Traceback (most recent call last):
>> File "/usr/lib64/nvidia-graphics-helpers/nvidia-config-x.py", line
>> 6, in <module>
>> import xf86config
>> ImportError: No module named xf86config
>>
>> I've looked and either I'm blind (highly likely) or that module isn't
>> available for centos7.
>>
> This error has been around for ages:
>
> http://lists.atrpms.net/pipermail/atrpms-users/2013-June/013739.html
>
> It would be nice to get it sorted, I have no idea how but I have great
> faith in Stephen :)
>
> Dunc

I've only recently (as in the last month or so) started getting this
error on this box. I'm fairly religious about updating and have run
nvidia-graphics-switch on the centos7 box successfully in the past.
Perhaps it was fixed but was broken again?

I'd be more than happy to provide log info if that would be helpful.

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

On 21/01/2015 13:43, NullDev wrote:
> Duncan Brown wrote:
>> This error has been around for ages:
>>
>> http://lists.atrpms.net/pipermail/atrpms-users/2013-June/013739.html
>>
>> It would be nice to get it sorted, I have no idea how but I have great
>> faith in Stephen :)
>>
>> Dunc
>
> I've only recently (as in the last month or so) started getting this
> error on this box. I'm fairly religious about updating and have run
> nvidia-graphics-switch on the centos7 box successfully in the past.
> Perhaps it was fixed but was broken again?
>
> I'd be more than happy to provide log info if that would be helpful.
>
> _______________________________________________
> atrpms-users mailing list
> atrpms-users@atrpms.net
> http://lists.atrpms.net/mailman/listinfo/atrpms-users
The package that contains nvidia-graphics-switch hasnt been updated in
years

Not sure how it could have ever been fixed in el7





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

If I remember well, it is a python script.

It is not really difficult to rewrite ...

The problem is that I am using intel graphics 4000, and several apple
computers, and gave up nvidia.
For day to day work it is more than enough for me.

I only have one 8500 card at work. Therefore, it is difficult to test
anything.





On Wed, Jan 21, 2015 at 12:03 PM, Duncan Brown <atrpms@duncb.co.uk> wrote:

> On 21/01/2015 13:43, NullDev wrote:
>
>> Duncan Brown wrote:
>>
>>> This error has been around for ages:
>>>
>>> http://lists.atrpms.net/pipermail/atrpms-users/2013-June/013739.html
>>>
>>> It would be nice to get it sorted, I have no idea how but I have great
>>> faith in Stephen :)
>>>
>>> Dunc
>>>
>>
>> I've only recently (as in the last month or so) started getting this
>> error on this box. I'm fairly religious about updating and have run
>> nvidia-graphics-switch on the centos7 box successfully in the past. Perhaps
>> it was fixed but was broken again?
>>
>> I'd be more than happy to provide log info if that would be helpful.
>>
>> _______________________________________________
>> atrpms-users mailing list
>> atrpms-users@atrpms.net
>> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>>
> The package that contains nvidia-graphics-switch hasnt been updated in
> years
>
> Not sure how it could have ever been fixed in el7
>
>
>
>
>
>
> _______________________________________________
> atrpms-users mailing list
> atrpms-users@atrpms.net
> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>



--
Paulo Roma Cavalcanti
LCG - UFRJ

On 22/01/2015 1:03 AM, Duncan Brown wrote:
> On 21/01/2015 13:43, NullDev wrote:
>> Duncan Brown wrote:
>>> This error has been around for ages:
>>>
>>> http://lists.atrpms.net/pipermail/atrpms-users/2013-June/013739.html
>>>
>>> It would be nice to get it sorted, I have no idea how but I have great
>>> faith in Stephen :)
>>>
>>> Dunc
>>
>> I've only recently (as in the last month or so) started getting this
>> error on this box. I'm fairly religious about updating and have run
>> nvidia-graphics-switch on the centos7 box successfully in the past.
>> Perhaps it was fixed but was broken again?
>>
>> I'd be more than happy to provide log info if that would be helpful.
>>
>> _______________________________________________
>> atrpms-users mailing list
>> atrpms-users@atrpms.net
>> http://lists.atrpms.net/mailman/listinfo/atrpms-users
> The package that contains nvidia-graphics-switch hasnt been updated in
> years
>
> Not sure how it could have ever been fixed in el7
>
>
>
>
>
> _______________________________________________
> atrpms-users mailing list
> atrpms-users@atrpms.net
> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>
Yes something from /var/log/Xorg.0.log would be great. I have been
looking at nvidia-graphics-switch to make some changes. The problem with
the linking directly in the rpm is that it will stop multiple versions
from being installed.


Cheers
Stephen

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

On 22/01/2015 1:24 AM, Paulo Cavalcanti wrote:
> If I remember well, it is a python script.
>
> It is not really difficult to rewrite ...
>
> The problem is that I am using intel graphics 4000, and several apple
> computers, and gave up nvidia.
> For day to day work it is more than enough for me.
>
> I only have one 8500 card at work. Therefore, it is difficult to test
> anything.
>
>
>
>
>
> On Wed, Jan 21, 2015 at 12:03 PM, Duncan Brown <atrpms@duncb.co.uk
> <mailto:atrpms@duncb.co.uk>> wrote:
>
> On 21/01/2015 13:43, NullDev wrote:
>
> Duncan Brown wrote:
>
> This error has been around for ages:
>
> http://lists.atrpms.net/pipermail/atrpms-users/2013-June/013739.html
>
> It would be nice to get it sorted, I have no idea how but
> I have great
> faith in Stephen :)
>
> Dunc
>
>
> I've only recently (as in the last month or so) started
> getting this error on this box. I'm fairly religious about
> updating and have run nvidia-graphics-switch on the centos7
> box successfully in the past. Perhaps it was fixed but was
> broken again?
>
> I'd be more than happy to provide log info if that would be
> helpful.
>
> _______________________________________________
> atrpms-users mailing list
> atrpms-users@atrpms.net <mailto:atrpms-users@atrpms.net>
> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>
> The package that contains nvidia-graphics-switch hasnt been
> updated in years
>
> Not sure how it could have ever been fixed in el7
>
>
>
>
>
>
> _______________________________________________
> atrpms-users mailing list
> atrpms-users@atrpms.net <mailto:atrpms-users@atrpms.net>
> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>
>
>
>
> --
> Paulo Roma Cavalcanti
> LCG - UFRJ
>
>
> _______________________________________________
> atrpms-users mailing list
> atrpms-users@atrpms.net
> http://lists.atrpms.net/mailman/listinfo/atrpms-users
Paulo,

yes it is a python script - I hadn't realised there was a problem with
el7 and nvidia-graphics-switch.

Stephen

On 22/01/2015 12:43 am, NullDev wrote:
> Duncan Brown wrote:
>> On 21/01/2015 12:56, NullDev wrote:
>>>
>>>
>>>> Stephen Collier <mailto:judithc@bigpond.net.au>
>>>> Wednesday, January 21, 2015 1:40 AM
>>>> I'm looking at 346.35 at the moment as it has some issues with el6
>>>> requiring gtk3. I should have some resolution over the next day.
>>>>
>>>> the linking problems should be fixed by running nvidia-graphics-switch
>>>>
>>>> Cheers
>>>> Stephen
>>>> _______________________________________________
>>>> atrpms-users mailing list
>>>> atrpms-users@atrpms.net
>>>> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>>>> mo.ucina <mailto:mo.ucina@gmail.com>
>>>> Monday, January 19, 2015 10:17 PM
>>>> 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:
>>>>
>>>> _______________________________________________
>>>> atrpms-users mailing list
>>>> atrpms-users@atrpms.net
>>>> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>>>> Stephen Collier <mailto:judithc@bigpond.net.au>
>>>> Monday, January 19, 2015 5:41 PM
>>>> 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
>>>> <nulldev42@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
>>>> judithc@bigpond.net.au
>>>> 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
>>>
>>> For whatever reason, "nvidia-graphics-switch" works on my centos6 box,
>>> but fails on my centos7 box with the following error. Perhaps it is
>>> related?
>>>
>>> # nvidia-graphics-switch 343.36
>>>
>>> Traceback (most recent call last):
>>> File "/usr/lib64/nvidia-graphics-helpers/nvidia-config-x.py", line
>>> 6, in <module>
>>> import xf86config
>>> ImportError: No module named xf86config
>>>
>>> I've looked and either I'm blind (highly likely) or that module isn't
>>> available for centos7.
>>>
>> This error has been around for ages:
>>
>> http://lists.atrpms.net/pipermail/atrpms-users/2013-June/013739.html
>>
>> It would be nice to get it sorted, I have no idea how but I have great
>> faith in Stephen :)
>>
>> Dunc
>
> I've only recently (as in the last month or so) started getting this
> error on this box. I'm fairly religious about updating and have run
> nvidia-graphics-switch on the centos7 box successfully in the past.
> Perhaps it was fixed but was broken again?
>
> I'd be more than happy to provide log info if that would be helpful.
>
> _______________________________________________
> atrpms-users mailing list
> atrpms-users@atrpms.net
> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>
xf86config has not been available since f19 I think from memory. It is
not strictly required but nvidia-graphics-switch provides some important
linking. I'll fix it put it the repo. I won't be able to do it until
sometime next week.

Cheers
Stephen

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

On 23/01/2015 5:36 AM, Stephen Collier wrote:
> On 22/01/2015 12:43 am, NullDev wrote:
>> Duncan Brown wrote:
>>> On 21/01/2015 12:56, NullDev wrote:
>>>>
>>>>
>>>>> Stephen Collier <mailto:judithc@bigpond.net.au>
>>>>> Wednesday, January 21, 2015 1:40 AM
>>>>> I'm looking at 346.35 at the moment as it has some issues with el6
>>>>> requiring gtk3. I should have some resolution over the next day.
>>>>>
>>>>> the linking problems should be fixed by running
>>>>> nvidia-graphics-switch
>>>>>
>>>>> Cheers
>>>>> Stephen
>>>>> _______________________________________________
>>>>> atrpms-users mailing list
>>>>> atrpms-users@atrpms.net
>>>>> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>>>>> mo.ucina <mailto:mo.ucina@gmail.com>
>>>>> Monday, January 19, 2015 10:17 PM
>>>>> 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:
>>>>>
>>>>> _______________________________________________
>>>>> atrpms-users mailing list
>>>>> atrpms-users@atrpms.net
>>>>> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>>>>> Stephen Collier <mailto:judithc@bigpond.net.au>
>>>>> Monday, January 19, 2015 5:41 PM
>>>>> 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
>>>>> <nulldev42@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
>>>>> judithc@bigpond.net.au
>>>>> 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
>>>>
>>>> For whatever reason, "nvidia-graphics-switch" works on my centos6 box,
>>>> but fails on my centos7 box with the following error. Perhaps it is
>>>> related?
>>>>
>>>> # nvidia-graphics-switch 343.36
>>>>
>>>> Traceback (most recent call last):
>>>> File "/usr/lib64/nvidia-graphics-helpers/nvidia-config-x.py", line
>>>> 6, in <module>
>>>> import xf86config
>>>> ImportError: No module named xf86config
>>>>
>>>> I've looked and either I'm blind (highly likely) or that module isn't
>>>> available for centos7.
>>>>
>>> This error has been around for ages:
>>>
>>> http://lists.atrpms.net/pipermail/atrpms-users/2013-June/013739.html
>>>
>>> It would be nice to get it sorted, I have no idea how but I have great
>>> faith in Stephen :)
>>>
>>> Dunc
>>
>> I've only recently (as in the last month or so) started getting this
>> error on this box. I'm fairly religious about updating and have run
>> nvidia-graphics-switch on the centos7 box successfully in the past.
>> Perhaps it was fixed but was broken again?
>>
>> I'd be more than happy to provide log info if that would be helpful.
>>
>> _______________________________________________
>> atrpms-users mailing list
>> atrpms-users@atrpms.net
>> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>>
> xf86config has not been available since f19 I think from memory. It is
> not strictly required but nvidia-graphics-switch provides some
> important linking. I'll fix it put it the repo. I won't be able to do
> it until sometime next week.
>
> Cheers
> Stephen
>
> _______________________________________________
> atrpms-users mailing list
> atrpms-users@atrpms.net
> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>
The build system is now fixed for links and is now building. I've added
nvidia-graphics-legacy-340 for cards that are not supported by 346
drivers. 346 drivers do not support el6 until I overcome a dependency.
nvidia-graphics-switch will be fixed in a later release.

Cheers
Stephen

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

Stephen Collier wrote:
> On 23/01/2015 5:36 AM, Stephen Collier wrote:
>> On 22/01/2015 12:43 am, NullDev wrote:
>>> Duncan Brown wrote:
>>>> On 21/01/2015 12:56, NullDev wrote:
>>>>>
>>>>>
>>>>>> Stephen Collier <mailto:judithc@bigpond.net.au>
>>>>>> Wednesday, January 21, 2015 1:40 AM
>>>>>> I'm looking at 346.35 at the moment as it has some issues with el6
>>>>>> requiring gtk3. I should have some resolution over the next day.
>>>>>>
>>>>>> the linking problems should be fixed by running
>>>>>> nvidia-graphics-switch
>>>>>>
>>>>>> Cheers
>>>>>> Stephen
>>>>>> _______________________________________________
>>>>>> atrpms-users mailing list
>>>>>> atrpms-users@atrpms.net
>>>>>> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>>>>>> mo.ucina <mailto:mo.ucina@gmail.com>
>>>>>> Monday, January 19, 2015 10:17 PM
>>>>>> 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:
>>>>>>
>>>>>> _______________________________________________
>>>>>> atrpms-users mailing list
>>>>>> atrpms-users@atrpms.net
>>>>>> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>>>>>> Stephen Collier <mailto:judithc@bigpond.net.au>
>>>>>> Monday, January 19, 2015 5:41 PM
>>>>>> 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
>>>>>> <nulldev42@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
>>>>>> judithc@bigpond.net.au
>>>>>> 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
>>>>>
>>>>> For whatever reason, "nvidia-graphics-switch" works on my centos6 box,
>>>>> but fails on my centos7 box with the following error. Perhaps it is
>>>>> related?
>>>>>
>>>>> # nvidia-graphics-switch 343.36
>>>>>
>>>>> Traceback (most recent call last):
>>>>> File "/usr/lib64/nvidia-graphics-helpers/nvidia-config-x.py", line
>>>>> 6, in <module>
>>>>> import xf86config
>>>>> ImportError: No module named xf86config
>>>>>
>>>>> I've looked and either I'm blind (highly likely) or that module isn't
>>>>> available for centos7.
>>>>>
>>>> This error has been around for ages:
>>>>
>>>> http://lists.atrpms.net/pipermail/atrpms-users/2013-June/013739.html
>>>>
>>>> It would be nice to get it sorted, I have no idea how but I have great
>>>> faith in Stephen :)
>>>>
>>>> Dunc
>>>
>>> I've only recently (as in the last month or so) started getting this
>>> error on this box. I'm fairly religious about updating and have run
>>> nvidia-graphics-switch on the centos7 box successfully in the past.
>>> Perhaps it was fixed but was broken again?
>>>
>>> I'd be more than happy to provide log info if that would be helpful.
>>>
>>> _______________________________________________
>>> atrpms-users mailing list
>>> atrpms-users@atrpms.net
>>> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>>>
>> xf86config has not been available since f19 I think from memory. It is
>> not strictly required but nvidia-graphics-switch provides some
>> important linking. I'll fix it put it the repo. I won't be able to do
>> it until sometime next week.
>>
>> Cheers
>> Stephen
>>
>> _______________________________________________
>> atrpms-users mailing list
>> atrpms-users@atrpms.net
>> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>>
> The build system is now fixed for links and is now building. I've added
> nvidia-graphics-legacy-340 for cards that are not supported by 346
> drivers. 346 drivers do not support el6 until I overcome a dependency.
> nvidia-graphics-switch will be fixed in a later release.
>
> Cheers
> Stephen
>
> _______________________________________________
> atrpms-users mailing list
> atrpms-users@atrpms.net
> http://lists.atrpms.net/mailman/listinfo/atrpms-users

As always, thank you for your work on these drivers!

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

Hello Guys,

Just tried the new rev 173 drivers , and still no good . I am not
getting to graphics screen still . This is the error from syslog :

[ 19.001] (II) LoadModule: "nvidia"
[ 19.001] (WW) Warning, couldn't open module nvidia
[ 19.001] (II) UnloadModule: "nvidia"
[ 19.001] (II) Unloading nvidia
[ 19.001] (EE) Failed to load module "nvidia" (module does not exist, 0)
[ 19.001] (EE) No drivers available.
[ 19.001] (EE)
Fatal server error:
[ 19.001] (EE) no screens found(EE)
[ 19.001] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 19.002] (EE) Please also check the log file at
"/var/log/Xorg.0.log" for additional information.
[ 19.002] (EE)


Maybe we need more links in there . Where is the module supposed to be ?

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

On 29/01/15 23:04, mo.ucina wrote:
> Hello Guys,
>
> Just tried the new rev 173 drivers , and still no good . I am not
> getting to graphics screen still . This is the error from syslog :
>
> [ 19.001] (II) LoadModule: "nvidia"
> [ 19.001] (WW) Warning, couldn't open module nvidia
> [ 19.001] (II) UnloadModule: "nvidia"
> [ 19.001] (II) Unloading nvidia
> [ 19.001] (EE) Failed to load module "nvidia" (module does not
> exist, 0)
> [ 19.001] (EE) No drivers available.
> [ 19.001] (EE)
> Fatal server error:
> [ 19.001] (EE) no screens found(EE)
> [ 19.001] (EE)
> Please consult the The X.Org Foundation support
> at http://wiki.x.org
> for help.
> [ 19.002] (EE) Please also check the log file at
> "/var/log/Xorg.0.log" for additional information.
> [ 19.002] (EE)
>
>
> Maybe we need more links in there . Where is the module supposed to be ?
Missing in el7 this one as well :

root@htpc /usr/lib64/xorg/modules/drivers # ln -s
nvidia-graphics-346.35/nvidia_drv-346.35.so nvidia_drv.so

Best regards
Milorad

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

Make sure your card is supported by the driver. I tried it on my ion2 device and it gave no error but gave what you have. I went to the 340 version and all good. Let me know if your card is supported and I'll look further as I don't have a card I can easily test. 

Cheers
Stephen


Sent from my Samsung GALAXY S4 on the Telstra 4G network

<div>-------- Original message --------</div><div>From: "mo.ucina" <mo.ucina@gmail.com> </div><div>Date:30/01/2015 12:38 AM (GMT+10:00) </div><div>To: "User discussion about ATrpms.net" <atrpms-users@atrpms.net>,Collier Family <judithc@bigpond.net.au> </div><div>Subject: Re: [ATrpms-users] new nvidia long term 346.35 </div><div>
</div>
On 29/01/15 23:04, mo.ucina wrote:
> Hello Guys,
>
> Just tried the new rev 173 drivers , and still no good . I am not
> getting to graphics screen still . This is the error from syslog :
>
> [    19.001] (II) LoadModule: "nvidia"
> [    19.001] (WW) Warning, couldn't open module nvidia
> [    19.001] (II) UnloadModule: "nvidia"
> [    19.001] (II) Unloading nvidia
> [    19.001] (EE) Failed to load module "nvidia" (module does not
> exist, 0)
> [    19.001] (EE) No drivers available.
> [    19.001] (EE)
> Fatal server error:
> [    19.001] (EE) no screens found(EE)
> [    19.001] (EE)
> Please consult the The X.Org Foundation support
>      at http://wiki.x.org
>  for help.
> [    19.002] (EE) Please also check the log file at
> "/var/log/Xorg.0.log" for additional information.
> [    19.002] (EE)
>
>
> Maybe we need more links in there . Where is the module supposed to be ?
Missing in el7 this one as well :

root@htpc /usr/lib64/xorg/modules/drivers # ln -s
nvidia-graphics-346.35/nvidia_drv-346.35.so nvidia_drv.so

Best regards
Milorad

On 30/01/2015 11:24 AM, OM Ugarcina wrote:
> Hi Stephen,
>
> My card is Gtx-750 . And I am now using the rev 173 drivers of 346.35
> , they are working well however I had to put in that link to
> nvidia_drv.so to make it work .
>
> Best Regards
>
> O&M Ugarcina
>
> On 30 Jan 2015, at 8:32 am, Stephen Collier <judithc@bigpond.net.au
> <mailto:judithc@bigpond.net.au>> wrote:
>
>> Make sure your card is supported by the driver. I tried it on my ion2
>> device and it gave no error but gave what you have. I went to the 340
>> version and all good. Let me know if your card is supported and I'll
>> look further as I don't have a card I can easily test.
>>
>> Cheers
>> Stephen
>>
>>
>> Sent from my Samsung GALAXY S4 on the Telstra 4G network
>>
>>
>> -------- Original message --------
>> From: "mo.ucina"
>> Date:30/01/2015 12:38 AM (GMT+10:00)
>> To: "User discussion about ATrpms.net <http://ATrpms.net>" ,Collier
>> Family
>> Subject: Re: [ATrpms-users] new nvidia long term 346.35
>>
>>
>> On 29/01/15 23:04, mo.ucina wrote:
>> > Hello Guys,
>> >
>> > Just tried the new rev 173 drivers , and still no good . I am not
>> > getting to graphics screen still . This is the error from syslog :
>> >
>> > [ 19.001] (II) LoadModule: "nvidia"
>> > [ 19.001] (WW) Warning, couldn't open module nvidia
>> > [ 19.001] (II) UnloadModule: "nvidia"
>> > [ 19.001] (II) Unloading nvidia
>> > [ 19.001] (EE) Failed to load module "nvidia" (module does not
>> > exist, 0)
>> > [ 19.001] (EE) No drivers available.
>> > [ 19.001] (EE)
>> > Fatal server error:
>> > [ 19.001] (EE) no screens found(EE)
>> > [ 19.001] (EE)
>> > Please consult the The X.Org <http://X.Org> Foundation support
>> > at http://wiki.x.org
>> > for help.
>> > [ 19.002] (EE) Please also check the log file at
>> > "/var/log/Xorg.0.log" for additional information.
>> > [ 19.002] (EE)
>> >
>> >
>> > Maybe we need more links in there . Where is the module supposed to
>> be ?
>> Missing in el7 this one as well :
>>
>> root@htpc /usr/lib64/xorg/modules/drivers # ln -s
>> nvidia-graphics-346.35/nvidia_drv-346.35.so nvidia_drv.so
>>
>> Best regards
>> Milorad
Sorry for the delay. Unfortunately my home internet has been dead for a
week. Finally fixed. I'm first going to see if I can get pyxfconfig
compiled for all versions - if there are too many showstoppers I'll
change nvidia-graphics-switch to work without it.

Cheers
Stephen