mailing list: no reply Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.16.4 (3.16.4-2.fc22) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit
I have had AMD Radeon card for my last computer, but this one comes with a Nvidia GeForce Gt 705. I seem to remember this from long ago, I downloaded the NVIDIA-Linux.....run . are there any gotcha's or anything I need to know before I do this??
Paul, I recently went through the steps to install NVidia drivers for my Video card on F22-64. It resulted in the X screen not running, and it took awhile to troubleshoot by using console commands. Now I'm using the Nouveau drivers and I'm doing fine. If you need the special features of the proprietary driver, I would recommend using the dnf software packaging system in fedora. If things go wrong, you can roll back the install.
On 08/16/2015 01:35 PM, Gerard Teichman wrote:
I have had AMD Radeon card for my last computer, but this one comes with a Nvidia GeForce Gt 705. I seem to remember this from long ago, I downloaded the NVIDIA-Linux.....run . are there any gotcha's or anything I need to know before I do this??
Paul, I recently went through the steps to install NVidia drivers for my Video card on F22-64. It resulted in the X screen not running, and it took awhile to troubleshoot by using console commands. Now I'm using the Nouveau drivers and I'm doing fine. If you need the special features of the proprietary driver, I would recommend using the dnf software packaging system in fedora. If things go wrong, you can roll back the install.
thanks! I installed the akmod-nvidia package..
On Sun, 2015-08-16 at 14:37 -0400, Paul Cartwright wrote:
thanks! I installed the akmod-nvidia package..
This generally works, however be aware that there is currently an issue when updating your system via dnf. If a new kernel is installed, the akmod system will create a new kmod rpm and then try to install it. Quite often the installation will fail because the calling dnf command still holds a lock on the database, but you won't know this until you reboot your nice new kernel and suddenly the video doesn't work.
The workaround is to check /var/cache/akmods/nvidia/.last.log after a new kernel has been installed but before booting. If it shows an error (jump to the end of the file) you still have time to manually install the new rpm before rebooting.
poc
On 08/16/2015 12:50 PM, Patrick O'Callaghan wrote:
The workaround is to check/var/cache/akmods/nvidia/.last.log after a new kernel has been installed but before booting. If it shows an error (jump to the end of the file) you still have time to manually install the new rpm before rebooting.
Two things: first, doesn't akmod run at boot, which would mean that the lock is gone. Second, why not just use last /var/cache/akmods/nvidia/.last.log to go right to the part you need to see?
Am 16.08.2015 um 22:09 schrieb Joe Zeff:
On 08/16/2015 12:50 PM, Patrick O'Callaghan wrote:
The workaround is to check/var/cache/akmods/nvidia/.last.log after a new kernel has been installed but before booting. If it shows an error (jump to the end of the file) you still have time to manually install the new rpm before rebooting.
Two things: first, doesn't akmod run at boot, which would mean that the lock is gone. Second, why not just use last /var/cache/akmods/nvidia/.last.log to go right to the part you need to see?
For reasons I don't know this doesn't work after a kernel upgrade. What I have to do in this case: Konsole output sudo /usr/sbin/akmods --force and then rboot.
On Sun, 2015-08-16 at 13:09 -0700, Joe Zeff wrote:
On 08/16/2015 12:50 PM, Patrick O'Callaghan wrote:
The workaround is to check/var/cache/akmods/nvidia/.last.log after a new kernel has been installed but before booting. If it shows an error (jump to the end of the file) you still have time to manually install the new rpm before rebooting.
Two things: first, doesn't akmod run at boot, which would mean that the lock is gone.
I've no idea what it's supposed to do, I'm just reporting what it actually does.
Second, why not just use last /var/cache/akmods/nvidia/.last.log to > go right to the part you nee to see?
Sure, whatever.
poc
On 08/16/2015 02:21 PM, Patrick O'Callaghan wrote:
I've no idea what it's supposed to do, I'm just reporting what it actually does.
The various akmods run at boot, as a service. Specifically, akmod-nvidia checks to see if there's a kmod-nvidia for the current kernel. If there is, it exits; if not, it builds one and then exits. Yes, you can also use --force to make it build a new kmod before rebooting, but it shouldn't be needed.
On 08/17/15 03:50, Patrick O'Callaghan wrote:
On Sun, 2015-08-16 at 14:37 -0400, Paul Cartwright wrote:
thanks! I installed the akmod-nvidia package..
This generally works, however be aware that there is currently an issue when updating your system via dnf. If a new kernel is installed, the akmod system will create a new kmod rpm and then try to install it. Quite often the installation will fail because the calling dnf command still holds a lock on the database, but you won't know this until you reboot your nice new kernel and suddenly the video doesn't work.
The workaround is to check /var/cache/akmods/nvidia/.last.log after a new kernel has been installed but before booting. If it shows an error (jump to the end of the file) you still have time to manually install the new rpm before rebooting.
I was having this problem as well. But there were some recent changes and even though the rpm isn't getting installed during the "dnf update" phase as long as I have akmods-shutdown.service enabled the rpm gets rebuilt and installed during the reboot.
On Mon, 2015-08-17 at 04:58 +0800, Ed Greshko wrote:
On 08/17/15 03:50, Patrick O'Callaghan wrote:
On Sun, 2015-08-16 at 14:37 -0400, Paul Cartwright wrote:
thanks! I installed the akmod-nvidia package..
This generally works, however be aware that there is currently an issue when updating your system via dnf. If a new kernel is installed, the akmod system will create a new kmod rpm and then try to install it. Quite often the installation will fail because the calling dnf command still holds a lock on the database, but you won't know this until you reboot your nice new kernel and suddenly the video doesn't work.
The workaround is to check /var/cache/akmods/nvidia/.last.log after a new kernel has been installed but before booting. If it shows an error (jump to the end of the file) you still have time to manually install the new rpm before rebooting.
I was having this problem as well. But there were some recent changes and even though the rpm isn't getting installed during the "dnf update" phase as long as I have akmods-shutdown.service enabled the rpm gets rebuilt and installed during the reboot.
I do have it enabled and yet last time I still had to do the manual install. At any rate the log showed an error due to locking.
poc
On 08/17/15 05:19, Patrick O'Callaghan wrote:
On Mon, 2015-08-17 at 04:58 +0800, Ed Greshko wrote:
I was having this problem as well. But there were some recent changes and even though the rpm isn't getting installed during the "dnf update" phase as long as I have akmods-shutdown.service enabled the rpm gets rebuilt and installed during the reboot.
I do have it enabled and yet last time I still had to do the manual install. At any rate the log showed an error due to locking.
If you're still having problems then you probably would want to BZ it in rpmfusion. I think it is Richard Shaw that is doing work in this area and he has been very responsive.
On 08/16/2015 05:19 PM, Patrick O'Callaghan wrote:
I was having this problem as well. But there were some recent changes and even though the rpm isn't getting installed during the "dnf update" phase as long as I have akmods-shutdown.service enabled the rpm gets rebuilt and installed during the reboot.
I do have it enabled and yet last time I still had to do the manual install. At any rate the log showed an error due to locking.
poc
and thanks to everyone for the info! I am glad to see I am not alone, and others have figured it out..
so, it seems no one runs the NVIDIA-Linux-x86_64-352.30. https://a248.e.akamai.net/f/1437/8432/10/us.download.nvidia.com/XFree86/Linux-x86_64/352.30/NVIDIA-Linux-x86_64-352.30.run and everyone just uses dnf & akmod-nvidia.. I have yet to reboot after installing akmod-nvidia, but I do remember it pulled in 11 other packages, one was the kernel-devel..
On 08/16/2015 03:57 PM, Paul Cartwright wrote:
and everyone just uses dnf & akmod-nvidia..
Actually, I use both kmod and akmod on my desktop. This way, if there's a kmod ready, it saves a bit of time when I reboot; if not, akmod will take care of it.
On 08/16/2015 07:08 PM, Joe Zeff wrote:
and everyone just uses dnf & akmod-nvidia..
Actually, I use both kmod and akmod on my desktop. This way, if there's a kmod ready, it saves a bit of time when I reboot; if not, akmod will take care of it.
what? not sure I understand.. what is the difference between kmod & akmod...
On Sun, 2015-08-16 at 19:10 -0400, Paul Cartwright wrote:
On 08/16/2015 07:08 PM, Joe Zeff wrote:
and everyone just uses dnf & akmod-nvidia..
Actually, I use both kmod and akmod on my desktop. This way, if there's a kmod ready, it saves a bit of time when I reboot; if not, akmod will take care of it.
what? not sure I understand.. what is the difference between kmod & akmod...
kmod is the actual kernel module that gets loaded at boot time. akmod is the system for building a new version of it for each new kernel. Just to make it more confusing, you can also download and install kmod rpm's directly without using akmod, but that only works if they already exist in some repo (typically rpmfusion), which sometimes takes a while after a new kernel appears.
poc
On 08/16/2015 07:28 PM, Patrick O'Callaghan wrote:
what? not sure I understand.. what is the difference between kmod & akmod...
kmod is the actual kernel module that gets loaded at boot time. akmod is the system for building a new version of it for each new kernel. Just to make it more confusing, you can also download and install kmod rpm's directly without using akmod, but that only works if they already exist in some repo (typically rpmfusion), which sometimes takes a while after a new kernel appears.
poc
thank you! I don't think I want to wait for a kmod package, I'll go with akmod..
On 08/16/2015 03:50 PM, Patrick O'Callaghan wrote:
thanks! I installed the akmod-nvidia package..
This generally works, however be aware that there is currently an issue when updating your system via dnf. If a new kernel is installed, the akmod system will create a new kmod rpm and then try to install it. Quite often the installation will fail because the calling dnf command still holds a lock on the database, but you won't know this until you reboot your nice new kernel and suddenly the video doesn't work.
The workaround is to check /var/cache/akmods/nvidia/.last.log after a new kernel has been installed but before booting. If it shows an error (jump to the end of the file) you still have time to manually install the new rpm before rebooting.
I'll try to remember that:)
On Sun, Aug 16, 2015 at 08:50:19PM +0100, Patrick O'Callaghan wrote:
On Sun, 2015-08-16 at 14:37 -0400, Paul Cartwright wrote:
thanks! I installed the akmod-nvidia package..
This generally works, however be aware that there is currently an issue when updating your system via dnf. If a new kernel is installed, the akmod system will create a new kmod rpm and then try to install it. Quite often the installation will fail because the calling dnf command still holds a lock on the database, but you won't know this until you reboot your nice new kernel and suddenly the video doesn't work.
The workaround is to check /var/cache/akmods/nvidia/.last.log after a new kernel has been installed but before booting. If it shows an error (jump to the end of the file) you still have time to manually install the new rpm before rebooting.
When an nvidia card is present, the akmod-nvidia package is present, and a new kernel is installed, it is necessary to ensure that a new nvidia.ko module is created. One might expect that this would be a natural requirement of the dnf process, which would not terminate until that task had been accomplished.
Sadly, it is NOT. Until this is fixed, what I do to protect myself against a failed reboot is this:
1) Near the end of the dnf update, run top and watch for abnormally intense cpu activity AFTER dnf concludes, looking especially for instances of cc1, rpmbuild, and any other processes being run by user 'akmods'. These suggest that the building of nvidia.ko is underway. Do NOT reboot until this is done.
2) Look for the existence of the new module for the NEW kernel: find /lib/modules -name nvidia.ko Only if it exists, is it safe to reboot.
3) If not, try to build it manually (as root, of course): akmods or akmods --force
4) If this fails and an error message says why, the new kernel must NOT be used. Edit /boot/grub2/grub.cfg to change the default from 0 to 1. Wait for a solution.
On 08/17/2015 02:45 PM, David A. De Graaf wrote:
When an nvidia card is present, the akmod-nvidia package is present, and a new kernel is installed, it is necessary to ensure that a new nvidia.ko module is created. One might expect that this would be a natural requirement of the dnf process, which would not terminate until that task had been accomplished.
Sadly, it is NOT. Until this is fixed, what I do to protect myself against a failed reboot is this:
- Near the end of the dnf update, run top and watch for abnormally
intense cpu activity AFTER dnf concludes, looking especially for instances of cc1, rpmbuild, and any other processes being run by user 'akmods'. These suggest that the building of nvidia.ko is underway. Do NOT reboot until this is done.
- Look for the existence of the new module for the NEW kernel: find /lib/modules -name nvidia.ko
Only if it exists, is it safe to reboot.
I see the one for my current kernel:
/lib/modules/4.1.4-200.fc22.x86_64/extra/nvidia/nvidia.ko
- If not, try to build it manually (as root, of course): akmods
or akmods --force
I thought the /usr/sbin/akmods --force WAS the manual way.. what is another way?
- If this fails and an error message says why, the new kernel must
NOT be used. Edit /boot/grub2/grub.cfg to change the default from 0 to 1. Wait for a solution.
I have other kernel options, but I don't think any have the nvidia module. can I create a file for those?
On Mon, Aug 17, 2015 at 02:52:01PM -0400, Paul Cartwright wrote:
On 08/17/2015 02:45 PM, David A. De Graaf wrote:
When an nvidia card is present, the akmod-nvidia package is present, and a new kernel is installed, it is necessary to ensure that a new nvidia.ko module is created. One might expect that this would be a natural requirement of the dnf process, which would not terminate until that task had been accomplished.
Sadly, it is NOT. Until this is fixed, what I do to protect myself against a failed reboot is this:
- Near the end of the dnf update, run top and watch for abnormally
intense cpu activity AFTER dnf concludes, looking especially for instances of cc1, rpmbuild, and any other processes being run by user 'akmods'. These suggest that the building of nvidia.ko is underway. Do NOT reboot until this is done.
- Look for the existence of the new module for the NEW kernel: find /lib/modules -name nvidia.ko
Only if it exists, is it safe to reboot.
I see the one for my current kernel:
/lib/modules/4.1.4-200.fc22.x86_64/extra/nvidia/nvidia.ko
- If not, try to build it manually (as root, of course): akmods
or akmods --force
I thought the /usr/sbin/akmods --force WAS the manual way.. what is another way?
The only other way I know is the automatic way - which occurs after a dnf update or, I think, during boot if the nvidia.ko module is missing.
- If this fails and an error message says why, the new kernel must
NOT be used. Edit /boot/grub2/grub.cfg to change the default from 0 to 1. Wait for a solution.
I have other kernel options, but I don't think any have the nvidia module. can I create a file for those?
According to the akmods man page --kernels <kernel> -- build and install only for kernel <kernel> (formatted the same as 'uname -r' would produce) so something like this should work: akmods --force --kernels 4.1.3-200.fc22.x86_64
On 08/17/2015 12:21 PM, David A. De Graaf wrote:
The only other way I know is the automatic way - which occurs after a dnf update or, I think, during boot if the nvidia.ko module is missing.
Checking, there's both an akmods.service and an akmods-shutdown.service. I'm not sure why you want both, but I have the second one disabled and haven't ever had any problems. YMMV, of course.
On 08/17/2015 03:21 PM, David A. De Graaf wrote:
- If this fails and an error message says why, the new kernel must
NOT be used. Edit /boot/grub2/grub.cfg to change the default from 0 to 1. Wait for a solution.
I have other kernel options, but I don't think any have the nvidia module. can I create a file for those?
According to the akmods man page --kernels <kernel> -- build and install only for kernel <kernel> (formatted the same as 'uname -r' would produce) so something like this should work: akmods --force --kernels 4.1.3-200.fc22.x86_64
I GET THAT.. akmods --force --kernels 4.0.4-301.fc22.x86_64 Could not find files needed to compile modules for 4.0.4-301.fc22.x86_64 Are the development files for kernel 4.0.4-301.fc22.x86_64 or the appropriate kernel-devel package installed?
so I need to install the kernel devels for 4.0.4-301...
-
David A. De Graaf -
Ed Greshko -
Gerard Teichman -
Joe Zeff -
Klaus-Peter Schrage -
Patrick O'Callaghan -
Paul Cartwright