The current nvidia-drivers-180.60 ebuild has a 'sed' call which modifies the /etc/modprobe.d/nvidia.conf - but the call is wrong atm, as it looks for the wrong file A short grep revealed, that the issue exists for some other versions too (though not all): necoro@Zakarumiy nvidia-drivers % grep 169.07 * [...] nvidia-drivers-173.14.15.ebuild: -e 's:VIDEOGID:'${VIDEOGROUP}':' "${FILESDIR}"/nvidia-169.07 > \ nvidia-drivers-173.14.18.ebuild: -e 's:VIDEOGID:'${VIDEOGROUP}':' "${FILESDIR}"/nvidia-169.07 > \ nvidia-drivers-180.29.ebuild: -e 's:VIDEOGID:'${VIDEOGROUP}':' "${FILESDIR}"/nvidia-169.07 > \ nvidia-drivers-180.60.ebuild: -e 's:VIDEOGID:'${VIDEOGROUP}':' "${FILESDIR}"/nvidia-169.07 > \
Created attachment 194641 [details, diff] nvidia-drivers-180.60.ebuild.diff Fixing the wrong file-name
ive restored files/nvidia-169.07 instead as it isnt the same as files/nvidia not sure how Doug wants to go though
Yeah I screwed up. Mike fixed it.