On 08/03/2017 01:35 PM, Richard Shaw wrote: > On Thu, Aug 3, 2017 at 2:22 PM, Sherman Grunewagen <sugarwagon@xxxxxxx > <mailto:sugarwagon@xxxxxxx>> wrote: > > On 08/03/2017 10:48 AM, Richard Shaw wrote: > > Ok, for the same nvidia module and kernel version for me... > > Dependencies resolved. > ================================================================================ > Package Arch Version > Repository Size > ================================================================================ > Installing: > kmod-nvidia-4.11.12-200.fc25.x86_64 x86_64 2:375.66-3.fc25 > @commandline 6.1 M > > Transaction Summary > ================================================================================ > Install 1 Package > > Total size: 6.1 M > Installed size: 18 M > Downloading Packages: > Running transaction check > Waiting for process with pid 13941 to finish. > Transaction check succeeded. > Running transaction test > Transaction test succeeded. > Running transaction > Installing : > kmod-nvidia-4.11.12-200.fc25.x86_64-2:375.66-3.fc25.x86_6 1/1 > Verifying : > kmod-nvidia-4.11.12-200.fc25.x86_64-2:375.66-3.fc25.x86_6 1/1 > > Installed: > kmod-nvidia-4.11.12-200.fc25.x86_64.x86_64 2:375.66-3.fc25 > > > Is this from the akmods log or did you install the kmod-nvidia > module manually with dnf from > the rpmfusion repo (if that's even possible these days)? > > > Yes, they are still built but usually take a few days to push (it's > manual IIRC) so it could prevent you from using a new kernel for a > little while which is why I use akmods... > > > No errors during install of the package or during the build. > There must be something funky in your environment... > > Not that anything useful/needed should be in /usr/local/include > but what are the permissions on it? > > > > > [root@new_pons ~]# ls -l /usr/local | fgrep include > drwxr-x--- 3 root root 4096 Aug 3 09:15 include > > > Ok, there is a problem but I don't know if it's THE problem. Everyone > should have read and execute permissions otherwise a normal user won't > be able to access the directory (and you should never build software as > root!) > > I've included all the directories as you should check the others as well: > > $ ll /usr/local > total 40 > drwxr-xr-x. 2 root root 4096 Aug 1 17:45 bin > drwxr-xr-x. 2 root root 4096 Feb 3 2016 etc > drwxr-xr-x. 2 root root 4096 Feb 3 2016 games > drwxr-xr-x. 6 root root 4096 Feb 18 07:27 include > drwxr-xr-x. 7 root root 4096 Feb 18 07:27 lib > drwxr-xr-x. 2 root root 4096 Feb 3 2016 lib64 > drwxr-xr-x. 2 root root 4096 Feb 3 2016 libexec > drwxr-xr-x. 2 root root 4096 Feb 18 07:27 sbin > drwxr-xr-x. 12 root root 4096 Aug 1 17:45 share > drwxr-xr-x. 2 root root 4096 Feb 3 2016 src > > A "chmod 0755 /usr/local/include" should fix that particular error, but > like I said, there's no telling if that's the underlying problem. To be really complete, I'd suggest (as the root user): # chmod 755 /usr/local/include # find /usr/local/include -type d -exec chmod 755 \{\} \; # find /usr/local/include -type f -exec chmod 644 \{\} \; This would make /usr/local/include and all _directories_ under it mode "rwxr-xr-x". The last command would make all _files_ under /usr/local/include/* mode "rw-r--r--" (the files don't need execute privileges). ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - UNIX is actually quite user friendly. The problem is that it's - - just very picky of who its friends are! - ---------------------------------------------------------------------- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
