On 08/03/2017 08:33 AM, Richard Shaw wrote:
On Thu, Aug 3, 2017 at 10:00 AM, Sherman Grunewagen <sugarwa...@gmx.com <mailto:sugarwa...@gmx.com>> wrote:On 08/03/2017 05:22 AM, Richard Shaw wrote: On Wed, Aug 2, 2017 at 11:59 PM, Sherman Grunewagen <sugarwa...@gmx.com <mailto:sugarwa...@gmx.com> <mailto:sugarwa...@gmx.com <mailto:sugarwa...@gmx.com>>> wrote: After updating my F25 installation (which included installing kernel-10-11-12-200) I can no longer boot X (w/ startx). rpm -qa | fgrep kmod-nvidia-4.11.12 returns kmod-nvidia-4.11.12-200.fc25.x86_64-375.66-3.fc25.x86_64 so the kernel module gets built and installed. But I see Aug 2 21:41:11 pons kernel: nvidia: Unknown symbol mcount (err 0) in /var/log/messages which I've not seen before. I removed the module with dnf and rebuilt it with akmods (which again produced the "unknown symbol" message, and X still won't boot. Is anyone else having this problem? Suggestions for a fix? Are you using akmods? Yes. I followed the rpmfusion framework instructions when I installed F25 and all has worked till now. This typically occurs due to an API change in the kernel happens from time to time and it may take nvidia a little while to fix. Should I expect everyone else using the nvidia / rpmfusion to be having the same problem? If so, I'm surprised to see no complaints other than mine. I searched the web but there was nothing recent with the "unknown symbol (err 0)" error. Well, I mention that because that's the most typical reason the akmod build fails but it looks like yours succeeded. I doubt this is the reason but a google search showed the same error when a kernel module was compiled with a different version of GCC than the kernel itself but that seems unlikely... Try booting the previous kernel and see if that works. It does. I'm running on it now. If the API has changed, shouldn't I expect all later kernels (including F26) to cause the nvidia driver to fail to load? Also, I wonder why it built successfully. (Not questioning you so much as trying to understand.) To check to see if it was a transient error, you could try removing the kmod-nvidia package from /var/cache/akmods/nvidia/ and rerunning akmods. I was never able to figure out the problem but there was a period where the akmods run would complete but the installed package wasn't quite right and rebuilding the kmod fixed it...
Thanks for your continuing help, Richard! Is what I did at the start (see OP) equivalent? I used dnf to remove kmod-nvidia and then rebuilt by calling akmods from the commandline. Anyway I'll try what you suggest and report back in a sec ... tick, tick. Ok. Removing the akmod-nvidia with dnf _does_not_ remove the rpm and log in /var/cache/akmods/nvidia/. So I did the "dnf erase", removed the entries for the 10.11.12 kernel version in /var/cache/akmods/nvidia/, and rebuilt with "akmods". This appears at the bottome of the log after a "successful" build: 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 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 depmod: WARNING: /lib/modules/4.11.12-200.fc25.x86_64/extra/nvidia/nvidia-modeset.ko needs unknown symbol mcount depmod: WARNING: /lib/modules/4.11.12-200.fc25.x86_64/extra/nvidia/nvidia-drm.ko needs unknown symbol mcount depmod: WARNING: /lib/modules/4.11.12-200.fc25.x86_64/extra/nvidia/nvidia-uvm.ko needs unknown symbol mcount depmod: WARNING: /lib/modules/4.11.12-200.fc25.x86_64/extra/nvidia/nvidia.ko needs unknown symbol mcount 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 Complete! 2017/08/03 09:13:21 akmods: Successful. --------- And, of course, X won't boot. Looking for errors in the build log, I found this mystery: 2017/08/03 09:13:14 akmodsbuild: cc1: error: /usr/local/include: Permission denied 2017/08/03 09:13:14 akmodsbuild: cc1: error: /usr/local/include: Permission denied 2017/08/03 09:13:14 akmodsbuild: ./scripts/gcc-version.sh: line 31: printf: #: invalid number 2017/08/03 09:13:14 akmodsbuild: ./scripts/gcc-version.sh: line 31: printf: #: invalid number 2017/08/03 09:13:14 akmodsbuild: /bin/sh: line 0: [: too many arguments Except for these lines, this log and those for the other kmod-nvidia builds for earlier kernels look virtually identical. I can't fathom how Permission would be denied. I ran the akmods as root! -Sherman _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
