(responding to both Barry and Samuel...
On 11/23/23 4:26 PM, Samuel Sieb wrote:
On 11/23/23 15:17, home user wrote:
On 11/23/23 3:25 PM, Samuel Sieb wrote:
I think it will compile against any kernels that need it. Which kernel are you running and which one do you need?
I'm wanting to use the kernel installed by today's patches: "6.5.12-200.fc38.x86_64".
The kernel before that was "6.5.10-200.fc38.x86_64".
When I sent the 1:52 (mountain time) message, I was running the 6.10 kernel; I'm now back to the new (6.12) kernel.
It was trying to compile for the one you wanted.
2. Should I do what the output above says?
Check the log to see why it's failing. It might be a kernel change that breaks the module. You could try forcing it and see what happens.
--
Here's the log that the akmods command referenced:
------
2023/11/23 15:45:40 akmods: Building RPM using the command '/sbin/akmodsbuild --kernels 6.5.12-200.fc38.x86_64 /usr/src/akmods/nvidia-470xx-kmod.latest'
warning: user mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
Installing /usr/src/akmods/nvidia-470xx-kmod.latest
Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1698796800
error: Failed build dependencies:
kernel-devel-uname-r = 6.5.12-200.fc38.x86_64 is needed by nvidia-470xx-kmod-3:470.223.02-1.fc38.x86_64
xorg-x11-drv-nvidia-470xx-kmodsrc >= 3:470.223.02 is needed by nvidia-470xx-kmod-3:470.223.02-1.fc38.x86_64
RPM build warnings:
user mockbuild does not exist - using root
user mockbuild does not exist - using root
2023/11/23 15:45:41 akmodsbuild: * Rebuilding /usr/src/akmods/nvidia-470xx-kmod.latest for kernel(s) 6.5.12-200.fc38.x86_64: warning: user mockbuild does not exist - using root
2023/11/23 15:45:41 akmodsbuild: warning: user mockbuild does not exist - using root
2023/11/23 15:45:41 akmodsbuild: Installing /usr/src/akmods/nvidia-470xx-kmod.latest
2023/11/23 15:45:41 akmodsbuild: Building target platforms: x86_64
2023/11/23 15:45:41 akmodsbuild: Building for target x86_64
2023/11/23 15:45:41 akmodsbuild: setting SOURCE_DATE_EPOCH=1698796800
2023/11/23 15:45:41 akmodsbuild: error: Failed build dependencies:
2023/11/23 15:45:41 akmodsbuild: kernel-devel-uname-r = 6.5.12-200.fc38.x86_64 is needed by nvidia-470xx-kmod-3:470.223.02-1.fc38.x86_64
2023/11/23 15:45:41 akmodsbuild: xorg-x11-drv-nvidia-470xx-kmodsrc >= 3:470.223.02 is needed by nvidia-470xx-kmod-3:470.223.02-1.fc38.x86_64
2023/11/23 15:45:41 akmodsbuild:
2023/11/23 15:45:41 akmodsbuild: RPM build warnings:
2023/11/23 15:45:41 akmodsbuild: user mockbuild does not exist - using root
2023/11/23 15:45:41 akmodsbuild: user mockbuild does not exist - using root
2023/11/23 15:45:41 akmodsbuild:
2023/11/23 15:45:41 akmods: Building rpms failed; see /var/cache/akmods/nvidia-470xx/470.223.02-1-for-6.5.12-200.fc38.x86_64.failed.log for details
------
If I do the "/usr/sbin/akmods --force" suggested by "akmods", will that mess up future handling of kernel and nvidia-470xx by "dnf upgrade"?
It won't mess up future builds, but I also don't think it will work for this time either. It says you're missing the devel package for the current kernel and I wonder why that is.
What does "rpm -qa | grep kernel" give you?
--
(Barry)
I'm certain the build was done. I knew that there was a command line way of checking for that, but I had forgotten what the command was. So I use the ksysguard displays (both the processes tab and the graphical display). Thank-you for reminding me what the command is for checking via command line.
(Samuel)
Here's the output:
------
-bash.8[~]: /usr/sbin/akmods --force
Checking kmods exist for 6.5.12-200.fc38.x86_64 [ OK ]
Building and installing nvidia-470xx-kmod [FAILED]
Building rpms failed; see /var/cache/akmods/nvidia-470xx/470.223.02-1-for-6.5.12-200.fc38.x86_64.failed.log for details
Hint: Some kmods were ignored or failed to build or install.
You can try to rebuild and install them by by calling
'/usr/sbin/akmods --force' as root.
-bash.9[~]: whoami
root
-bash.10[~]: rpm -qa | grep kernel
kernel-modules-core-6.4.15-100.fc37.x86_64
kernel-core-6.4.15-100.fc37.x86_64
kernel-modules-6.4.15-100.fc37.x86_64
kernel-devel-6.4.15-100.fc37.x86_64
kernel-6.4.15-100.fc37.x86_64
kernel-modules-core-6.5.5-100.fc37.x86_64
kernel-core-6.5.5-100.fc37.x86_64
kernel-modules-6.5.5-100.fc37.x86_64
kernel-devel-6.5.5-100.fc37.x86_64
kernel-6.5.5-100.fc37.x86_64
kernel-headers-6.5.4-200.fc38.x86_64
kernel-srpm-macros-1.0-19.fc38.noarch
kernel-tools-libs-6.5.4-200.fc38.x86_64
kernel-modules-core-6.5.5-200.fc38.x86_64
kernel-core-6.5.5-200.fc38.x86_64
libreport-plugin-kerneloops-2.17.11-1.fc38.x86_64
kernel-modules-6.5.5-200.fc38.x86_64
kernel-tools-6.5.4-200.fc38.x86_64
abrt-addon-kerneloops-2.17.1-1.fc38.x86_64
kernel-devel-6.5.5-200.fc38.x86_64
texlive-l3kernel-svn65299-65.fc38.noarch
kernel-devel-matched-6.5.5-200.fc38.x86_64
python3-ipykernel-6.17.1-2.fc38.noarch
python3-spyder-kernels-2.3.3-2.fc38.noarch
kernel-6.5.5-200.fc38.x86_64
-bash.11[~]:
------
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
