On Thu, Aug 3, 2017 at 10:00 AM, Sherman Grunewagen <sugarwagon@xxxxxxx> wrote:
On 08/03/2017 05:22 AM, Richard Shaw wrote:
On Wed, Aug 2, 2017 at 11:59 PM, Sherman Grunewagen <sugarwagon@xxxxxxx <mailto:sugarwagon@xxxxxxx>> 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,
Richard
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
