Bonjour,
I updated my f24 this morning: a new kernel is provided and using the akmod-nvidia, X won't start....
I logged on console and tried startx but it failed with this message:
FATAL: nvidia module not found in /lib/modules/4.7.3.-200.fc24.x86_64
Of course, the nvidia module is in /lib/modules/4.7.3.-200.../extra/nvidia-340xx
Exactly like for the previous kernel (4.7.2)....
I copied the nvidia.ko in /lib/modules/4.7.3.-200.fc24.x86_64 but, startx failed with the same message which is a lack of honesty!
What happens?
Thank you.
On Wed, 14 Sep 2016 14:29:35 +0200 François Patte wrote:
I updated my f24 this morning: a new kernel is provided and using the akmod-nvidia, X won't start....
I updated to 4.7.3 on two systems today with akmod-nvidia from rpmfusion and both are working fine, so it isn't a probably everyone is having. My modules are in /lib/modules/4.7.3-200.fc24.x86_64/extra/nvidia/
-rw-r--r-- 1 root root 69224 Sep 14 07:16 nvidia-drm.ko -rw-r--r-- 1 root root 15672776 Sep 14 07:16 nvidia.ko -rw-r--r-- 1 root root 1046976 Sep 14 07:16 nvidia-modeset.ko -rw-r--r-- 1 root root 1279504 Sep 14 07:16 nvidia-uvm.ko
you could try running akmods --force to get it to rebuild, maybe something didn't work the first time.
On 09/14/16 20:29, François Patte wrote:
Bonjour,
I updated my f24 this morning: a new kernel is provided and using the akmod-nvidia, X won't start....
I logged on console and tried startx but it failed with this message:
FATAL: nvidia module not found in /lib/modules/4.7.3.-200.fc24.x86_64
Of course, the nvidia module is in /lib/modules/4.7.3.-200.../extra/nvidia-340xx
Exactly like for the previous kernel (4.7.2)....
I copied the nvidia.ko in /lib/modules/4.7.3.-200.fc24.x86_64 but, startx failed with the same message which is a lack of honesty!
What happens?
I just updated my laptop which also uses the nvidia-340xx drivers from rpmfusion.
It booted just fine. I use KDE and sddm as my display manager and it came up as expected.
Check /var/cache/akmods/akmods.log for any errors.
Le 14/09/2016 16:31, Ed Greshko a écrit :
On 09/14/16 20:29, François Patte wrote:
Bonjour,
I updated my f24 this morning: a new kernel is provided and using the akmod-nvidia, X won't start....
I logged on console and tried startx but it failed with this message:
FATAL: nvidia module not found in /lib/modules/4.7.3.-200.fc24.x86_64
Of course, the nvidia module is in /lib/modules/4.7.3.-200.../extra/nvidia-340xx
Exactly like for the previous kernel (4.7.2)....
I copied the nvidia.ko in /lib/modules/4.7.3.-200.fc24.x86_64 but, startx failed with the same message which is a lack of honesty!
What happens?
I just updated my laptop which also uses the nvidia-340xx drivers from rpmfusion.
It booted just fine. I use KDE and sddm as my display manager and it came up as expected.
Check /var/cache/akmods/akmods.log for any errors.
Thanks for answering. No errors in the log file. I tried to load the nvidia module using modprobe and the answer was the same: FATAL module nvidia not found (while it is in the right directory)....
So I run depmod -a and the problem is solved, but this does not explain why akmod did not run (or failed to run) depmod after building the module.
On Wed, Sep 14, 2016 at 10:39 AM, François Patte < francois.patte@mi.parisdescartes.fr> wrote:
Thanks for answering. No errors in the log file. I tried to load the nvidia module using modprobe and the answer was the same: FATAL module nvidia not found (while it is in the right directory)....
So I run depmod -a and the problem is solved, but this does not explain why akmod did not run (or failed to run) depmod after building the module.
The akmod utility doesn't run depmod. All it does is build the RPM based on the new kernel and installs the resultant RPM.
I've run into the occasional issue similar to yours. I haven't been able to figure out the cause but I would recommend you don't reboot too soon after a kernel update. Akmod has to install the RPM after the previous update is complete and the rpmdb lock removed. It may take longer than you think. If it gets stopped after a certain point the utility may think everything is done when the package scriptlets haven't been run yet. This is purely a guess though.
In my case, the fix for me was to remove the built RPMs and re-run akmod, I didn't even think to try running depmod.
Thanks, Richard
On 09/14/16 23:39, François Patte wrote:
Thanks for answering. No errors in the log file. I tried to load the nvidia module using modprobe and the answer was the same: FATAL module nvidia not found (while it is in the right directory)....
So I run depmod -a and the problem is solved, but this does not explain why akmod did not run (or failed to run) depmod after building the module.
In addition to what others have said, make sure you have both akmods-shutdown.service and akmods.service enabled. I've found that having both enabled will catch improperly installed kmods.
The one thing to realize is that, unfortunately, you don't get an indication they are running either at boot time or shutdown time. So, you may think you have have a hung system when they are doing their work.
On Thu, Sep 15, 2016 at 05:56:19AM +0800, Ed Greshko wrote:
On 09/14/16 23:39, François Patte wrote:
Thanks for answering. No errors in the log file. I tried to load the nvidia module using modprobe and the answer was the same: FATAL module nvidia not found (while it is in the right directory)....
So I run depmod -a and the problem is solved, but this does not explain why akmod did not run (or failed to run) depmod after building the module.
In addition to what others have said, make sure you have both akmods-shutdown.service and akmods.service enabled. I've found that having both enabled will catch improperly installed kmods.
The one thing to realize is that, unfortunately, you don't get an indication they are running either at boot time or shutdown time. So, you may think you have have a hung system when they are doing their work.
I've been fooled by that in the past, not with systemd, either, but on Centos 6, or so, when after a virtualbox update the system can take five mins during boot with a blank screen to do whatever it is doing with kmod and virtualbox.
Le 14/09/2016 23:56, Ed Greshko a écrit :
On 09/14/16 23:39, François Patte wrote:
Thanks for answering. No errors in the log file. I tried to load the nvidia module using modprobe and the answer was the same: FATAL module nvidia not found (while it is in the right directory)....
So I run depmod -a and the problem is solved, but this does not explain why akmod did not run (or failed to run) depmod after building the module.
In addition to what others have said, make sure you have both akmods-shutdown.service and akmods.service enabled.
Both are enabled. I suppose that it is the default state when you install akmods...
I've found that having both enabled will catch improperly installed kmods.
So? Do we have to disable one of them? And which one?
On 09/15/16 15:48, François Patte wrote:
Le 14/09/2016 23:56, Ed Greshko a écrit :
On 09/14/16 23:39, François Patte wrote:
Thanks for answering. No errors in the log file. I tried to load the nvidia module using modprobe and the answer was the same: FATAL module nvidia not found (while it is in the right directory)....
So I run depmod -a and the problem is solved, but this does not explain why akmod did not run (or failed to run) depmod after building the module.
In addition to what others have said, make sure you have both akmods-shutdown.service and akmods.service enabled.
Both are enabled. I suppose that it is the default state when you install akmods...
I've found that having both enabled will catch improperly installed kmods.
So? Do we have to disable one of them? And which one?
Ahhh.... I said "make sure you have both" enabled and I did mean *both*. So, I can't see why I would be seen as advocating to disable one.
Anyway, to repeat, there is no indication they are "running" and doing the needed depmod along the way. So, it is possible (and I've done it) to mess things up beyond their ability to recover. I don't know if that is what happened in your case....but since the solution for you was was to manually run "depmod -a" I would think it is a possibility.
On Thu, Sep 15, 2016 at 04:44:51PM +0800, Ed Greshko wrote:
On 09/15/16 15:48, François Patte wrote:
Le 14/09/2016 23:56, Ed Greshko a écrit :
In addition to what others have said, make sure you have both akmods-shutdown.service and akmods.service enabled.
...
I've found that having both enabled will catch improperly installed kmods.
Ed, I'm not having problems, but not having noticed those unit before I checked their status. Both are enabled and have run abd exited with status 0.
Is that the typical status for a running system?
Jon
On 09/16/16 06:15, Jon LaBadie wrote:
I'm not having problems, but not having noticed those unit before I checked their status. Both are enabled and have run abd exited with status 0.
Is that the typical status for a running system?
Yes, that is normal.
Both services are "Type=oneshot" so they run and then exit.
-
Ed Greshko -
François Patte -
Fred Smith -
Jon LaBadie -
Richard Shaw -
Tom Horsley