(f38; home workstation; dual monitor; using nvidia 4xx kmod and akmod from rpmfusion)
A short while ago, I did my weekly patches. After rebooting, only one monitor is displaying anything, and then with a large, wide font. I saw no indication of trouble during the "dnf upgrade". The boot messages go by fast, but I think I saw something about a missing module, and nouveau being used.
I'm not a sys.admin., and the display is very limited. What's the cause of these problems, and how do I fix things?
On 11/23/23 12:02, home user wrote:
(f38; home workstation; dual monitor; using nvidia 4xx kmod and akmod from rpmfusion)
A short while ago, I did my weekly patches. After rebooting, only one monitor is displaying anything, and then with a large, wide font. I saw no indication of trouble during the "dnf upgrade". The boot messages go by fast, but I think I saw something about a missing module, and nouveau being used.
I'm not a sys.admin., and the display is very limited. What's the cause of these problems, and how do I fix things?
Try running "sudo akmods" and see if there are any errors.
On 11/23/23 1:10 PM, Joe Zeff wrote:
On 11/23/2023 01:02 PM, home user wrote:
I'm not a sys.admin., and the display is very limited. What's the cause of these problems, and how do I fix things?
The first thing is probably to examine /var/log/boot.log to see if there are any clues there.
Using "grep", grepping for "kmod" and "ouveau", I see 29 lines of possible interest. But they have strange sequences of '^', '[', 'M', and 'K'. The file of matches is hard to read. How do I get those lines into an e-mail without those strange sequences?
On 11/23/23 1:43 PM, Samuel Sieb wrote:
On 11/23/23 12:02, home user wrote:
(f38; home workstation; dual monitor; using nvidia 4xx kmod and akmod from rpmfusion)
A short while ago, I did my weekly patches. After rebooting, only one monitor is displaying anything, and then with a large, wide font. I saw no indication of trouble during the "dnf upgrade". The boot messages go by fast, but I think I saw something about a missing module, and nouveau being used.
I'm not a sys.admin., and the display is very limited. What's the cause of these problems, and how do I fix things?
Try running "sudo akmods" and see if there are any errors.
I've rebooted to the previous kernel. Does that matter? Running under that older kernel, I get this: ----- -bash.1[~]: akmods Checking kmods exist for 6.5.10-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.10-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.
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.2[~]: ----- 1. Do I need to re-do this under the new kernel? 2. Should I do what the output above says?
On 11/23/23 12:52, home user wrote:
On 11/23/23 1:43 PM, Samuel Sieb wrote:
On 11/23/23 12:02, home user wrote:
(f38; home workstation; dual monitor; using nvidia 4xx kmod and akmod from rpmfusion)
A short while ago, I did my weekly patches. After rebooting, only one monitor is displaying anything, and then with a large, wide font. I saw no indication of trouble during the "dnf upgrade". The boot messages go by fast, but I think I saw something about a missing module, and nouveau being used.
I'm not a sys.admin., and the display is very limited. What's the cause of these problems, and how do I fix things?
Try running "sudo akmods" and see if there are any errors.
I've rebooted to the previous kernel. Does that matter? Running under that older kernel, I get this:
-bash.1[~]: akmods Checking kmods exist for 6.5.10-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.10-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.
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.2[~]:
- Do I need to re-do this under the new kernel?
I think it will compile against any kernels that need it. Which kernel are you running and which one do you need?
- 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.
On 23/11/2023 22:25, Samuel Sieb wrote:
On 11/23/23 12:52, home user wrote:
On 11/23/23 1:43 PM, Samuel Sieb wrote:
On 11/23/23 12:02, home user wrote:
(f38; home workstation; dual monitor; using nvidia 4xx kmod and akmod from rpmfusion)
A short while ago, I did my weekly patches. After rebooting, only one monitor is displaying anything, and then with a large, wide font. I saw no indication of trouble during the "dnf upgrade". The boot messages go by fast, but I think I saw something about a missing module, and nouveau being used.
I'm not a sys.admin., and the display is very limited. What's the cause of these problems, and how do I fix things?
Try running "sudo akmods" and see if there are any errors.
I've rebooted to the previous kernel. Does that matter? Running under that older kernel, I get this:
-bash.1[~]: akmods Checking kmods exist for 6.5.10-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.10-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.
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.2[~]:
- Do I need to re-do this under the new kernel?
I think it will compile against any kernels that need it. Which kernel are you running and which one do you need?
- 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.
I have just done the same kernel update with the same nvidia driver, and had no problem. Building the driver modules will go on long after dnf quits, if you don't try to boot immediately, and that seems to me to be a safer option than hoping it will complete during the reboot. But of course the log might reveal *why* your build failed... --
John P
On 11/23/23 1:43 PM, home user wrote:
On 11/23/23 1:10 PM, Joe Zeff wrote:
On 11/23/2023 01:02 PM, home user wrote:
I'm not a sys.admin., and the display is very limited. What's the cause of these problems, and how do I fix things?
The first thing is probably to examine /var/log/boot.log to see if there are any clues there.
Using "grep", grepping for "kmod" and "ouveau", I see 29 lines of possible interest. But they have strange sequences of '^', '[', 'M', and 'K'. The file of matches is hard to read. How do I get those lines into an e-mail without those strange sequences?
I have no idea how to remove the strange character sequences from the output, so here it is raw: ------ 352:[^[[0;32m OK ^[[0m] Stopped ^[[0;1;39mkmod-static-nodes.…reate List of Static Device Nodes. 364:[^[[0;32m OK ^[[0m] Created slice ^[[0;1;39msystem-akmod…[0m - Slice /system/akmods-keygen. 391: Starting ^[[0;1;39mkmod-static-nodes…ate List of Static Device Nodes... 410:[^[[0;32m OK ^[[0m] Finished ^[[0;1;39mkmod-static-nodes…reate List of Static Device Nodes. 499:[^[[0;32m OK ^[[0m] Reached target ^[[0;1;39makmods-keygen.target^[[0m. 500: Starting ^[[0;1;39makmods-shutdown.s…l new kmods from akmod packages... 501: Starting ^[[0;1;39makmods.service^[[0…l new kmods from akmod packages... 517:[^[[0;32m OK ^[[0m] Finished ^[[0;1;39makmods-shutdown.s…all new kmods from akmod packages. 548:^[M^M^[[K[ ^[[0;31m*^[[0;1;31m*^[[0m] (1 of 2) Job akmods.service/start running (26s / no limit) 549:^[M^M^[[K[ ^[[0;31m*^[[0m] (1 of 2) Job akmods.service/start running (27s / no limit) 550:^[M^M^[[K[ ^[[0;31m*^[[0;1;31m*^[[0m] (1 of 2) Job akmods.service/start running (27s / no limit) 554:^[M^M^[[K[^[[0;31m*^[[0;1;31m*^[[0m^[[0;31m* ^[[0m] (1 of 2) Job akmods.service/start running (29s / no limit) 555:^[M^M^[[K[^[[0;1;31m*^[[0m^[[0;31m* ^[[0m] (1 of 2) Job akmods.service/start running (30s / no limit) 556:^[M^M^[[K[^[[0m^[[0;31m* ^[[0m] (1 of 2) Job akmods.service/start running (30s / no limit) 560:^[M^M^[[K[ ^[[0;31m*^[[0;1;31m*^[[0m^[[0;31m* ^[[0m] (1 of 2) Job akmods.service/start running (32s / no limit) 561:^[M^M^[[K[ ^[[0;31m*^[[0;1;31m*^[[0m^[[0;31m*^[[0m] (1 of 2) Job akmods.service/start running (33s / no limit) 562:^[M^M^[[K[ ^[[0;31m*^[[0;1;31m*^[[0m] (1 of 2) Job akmods.service/start running (33s / no limit) 566:^[M^M^[[K[ ^[[0;31m*^[[0;1;31m*^[[0m^[[0;31m* ^[[0m] (1 of 2) Job akmods.service/start running (35s / no limit) 567:^[M^M^[[K[ ^[[0;31m*^[[0;1;31m*^[[0m^[[0;31m* ^[[0m] (1 of 2) Job akmods.service/start running (36s / no limit) 568:^[M^M^[[K[^[[0;31m*^[[0;1;31m*^[[0m^[[0;31m* ^[[0m] (1 of 2) Job akmods.service/start running (36s / no limit) 572:^[M^M^[[K[^[[0;31m*^[[0;1;31m*^[[0m^[[0;31m* ^[[0m] (1 of 2) Job akmods.service/start running (38s / no limit) 573:^[M^M^[[K[ ^[[0;31m*^[[0;1;31m*^[[0m^[[0;31m* ^[[0m] (1 of 2) Job akmods.service/start running (39s / no limit) 574:^[M^M^[[K[ ^[[0;31m*^[[0;1;31m*^[[0m^[[0;31m* ^[[0m] (1 of 2) Job akmods.service/start running (39s / no limit) 587:^[M^M^[[K[ ^[[0;31m*^[[0;1;31m*^[[0m] (1 of 2) Job akmods.service/start running (44s / no limit) 588:^[M^M^[[K[ ^[[0;31m*^[[0;1;31m*^[[0m^[[0;31m*^[[0m] (1 of 2) Job akmods.service/start running (45s / no limit)
603: Starting ^[[0;1;39mnvidia-fallback.s… nouveau as nvidia did not load... 604:[^[[0;32m OK ^[[0m] Finished ^[[0;1;39mnvidia-fallback.s…to nouveau as nvidia did not load. 904: Starting ^[[0;1;39mnvidia-fallback.s… nouveau as nvidia did not load... 905:[^[[0;32m OK ^[[0m] Finished ^[[0;1;39mnvidia-fallback.s…to nouveau as nvidia did not load. ------ By the way, the numbers at the beginning are line numbers produced by using "grep -n " on the log file. The first bunch of lines are the output of grepping for "kmod"; the last 4 grepping for "ouveau".
On 11/23/23 1:52 PM, home user wrote:
On 11/23/23 1:43 PM, Samuel Sieb wrote:
On 11/23/23 12:02, home user wrote:
(f38; home workstation; dual monitor; using nvidia 4xx kmod and akmod from rpmfusion)
A short while ago, I did my weekly patches. After rebooting, only one monitor is displaying anything, and then with a large, wide font. I saw no indication of trouble during the "dnf upgrade". The boot messages go by fast, but I think I saw something about a missing module, and nouveau being used.
I'm not a sys.admin., and the display is very limited. What's the cause of these problems, and how do I fix things?
Try running "sudo akmods" and see if there are any errors.
I've rebooted to the previous kernel. Does that matter? Running under that older kernel, I get this:
-bash.1[~]: akmods Checking kmods exist for 6.5.10-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.10-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.
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.2[~]:
- Do I need to re-do this under the new kernel?
- Should I do what the output above says?
--
In my earlier reply to Samuel, my questions were vague. I was intending to ask if it mattered whether I ran "akmods" with the new kernel or the older one. I booted back into the newest kernel (installed by the "dnf upgrade" run around midday today) and reran the "akmods". Here is the output: ------ -bash.1[~]: akmods 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.2[~]: ------ Before today's patches, the "dnf upgrade" handled everything, including the kernel and the nvidia-470xx. Also, I do not reboot after the "dnf upgrade" until about a minute after I see on ksysguard that the compiling of the driver is done. 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"? I hope y'all understand that I do not want to mess that up! In my earlier reply to Samuel, my questions were vague
On 11/23/23 3:25 PM, Samuel Sieb wrote:
On 11/23/23 12:52, home user wrote:
On 11/23/23 1:43 PM, Samuel Sieb wrote:
On 11/23/23 12:02, home user wrote:
(f38; home workstation; dual monitor; using nvidia 4xx kmod and akmod from rpmfusion)
A short while ago, I did my weekly patches. After rebooting, only one monitor is displaying anything, and then with a large, wide font. I saw no indication of trouble during the "dnf upgrade". The boot messages go by fast, but I think I saw something about a missing module, and nouveau being used.
I'm not a sys.admin., and the display is very limited. What's the cause of these problems, and how do I fix things?
Try running "sudo akmods" and see if there are any errors.
I've rebooted to the previous kernel. Does that matter? Running under that older kernel, I get this:
-bash.1[~]: akmods Checking kmods exist for 6.5.10-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.10-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.
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.2[~]:
- Do I need to re-do this under the new kernel?
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.
- 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"?
On 11/23/23 3:43 PM, John Pilkington wrote:
On 23/11/2023 22:25, Samuel Sieb wrote:
On 11/23/23 12:52, home user wrote:
On 11/23/23 1:43 PM, Samuel Sieb wrote:
On 11/23/23 12:02, home user wrote:
(f38; home workstation; dual monitor; using nvidia 4xx kmod and akmod from rpmfusion)
A short while ago, I did my weekly patches. After rebooting, only one monitor is displaying anything, and then with a large, wide font. I saw no indication of trouble during the "dnf upgrade". The boot messages go by fast, but I think I saw something about a missing module, and nouveau being used.
I'm not a sys.admin., and the display is very limited. What's the cause of these problems, and how do I fix things?
Try running "sudo akmods" and see if there are any errors.
I've rebooted to the previous kernel. Does that matter? Running under that older kernel, I get this:
-bash.1[~]: akmods Checking kmods exist for 6.5.10-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.10-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.
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.2[~]:
- Do I need to re-do this under the new kernel?
I think it will compile against any kernels that need it. Which kernel are you running and which one do you need?
- 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.
I have just done the same kernel update with the same nvidia driver, and had no problem. Building the driver modules will go on long after dnf quits, if you don't try to boot immediately, and that seems to me to be a safer option than hoping it will complete during the reboot. But of course the log might reveal *why* your build failed...
John P
After the dnf command completed, I did not reboot until about a minute after ksysguard showed the nvidia driver build was done (1% or less activity for all CPUs).
What additional logs are wanted?
On 23 Nov 2023, at 23:19, home user mattisonw@comcast.net wrote:
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"?
I expect that you rebooted before akmod finished compiling and installing the new nvidia drivers. Doing akmods —force should fix the problem.
FYI after a dnf update you can check to see if akmods is running with systemctl list-jobs If jobs are listed wait longer.
Barry
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.
- 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?
(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.
- 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[~]: ------
On 11/23/23 15:39, home user wrote:
-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
Where is the "6.5.12" kernel coming from, since you don't actually have it installed? Try dnf upgrading your kernel.
On 11/23/23 4:56 PM, Samuel Sieb wrote:
On 11/23/23 15:39, home user wrote:
Where is the "6.5.12" kernel coming from, since you don't actually have it installed? Try dnf upgrading your kernel.
------ -bash.12[~]: uname -a Linux coyote 6.5.12-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Nov 20 22:12:09 UTC 2023 x86_64 GNU/Linux -bash.13[~]: ------ The grub menu also showed 6.5.12 in the top line.
Do I need something more than "dnf --refresh upgrade", or will that be sufficient?
On 11/23/23 16:00, home user wrote:
On 11/23/23 4:56 PM, Samuel Sieb wrote:
On 11/23/23 15:39, home user wrote:
Where is the "6.5.12" kernel coming from, since you don't actually have it installed? Try dnf upgrading your kernel. --
-bash.12[~]: uname -a Linux coyote 6.5.12-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Nov 20 22:12:09 UTC 2023 x86_64 GNU/Linux
-bash.13[~]:
The grub menu also showed 6.5.12 in the top line.
What does "rpm -qf /boot/vmlinuz-6.5.12*" show?
Do I need something more than "dnf --refresh upgrade", or will that be sufficient?
That should be all you need.
On 11/23/23 5:04 PM, Samuel Sieb wrote:
On 11/23/23 16:00, home user wrote:
On 11/23/23 4:56 PM, Samuel Sieb wrote:
On 11/23/23 15:39, home user wrote:
Where is the "6.5.12" kernel coming from, since you don't actually have it installed? Try dnf upgrading your kernel.
-bash.12[~]: uname -a Linux coyote 6.5.12-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Nov 20 22:12:09 UTC 2023 x86_64 GNU/Linux
-bash.13[~]:
The grub menu also showed 6.5.12 in the top line.
What does "rpm -qf /boot/vmlinuz-6.5.12*" show?
Do I need something more than "dnf --refresh upgrade", or will that be sufficient?
That should be all you need.
------ -bash.13[~]: rpm -qf /boot/vmlinuz-6.5.12* file /boot/vmlinuz-6.5.12-200.fc38.x86_64 is not owned by any package -bash.14[~]: ------ I'll await your reply to that before proceeding with the "dnf --refresh upgrade".
On 11/23/23 16:07, home user wrote:
On 11/23/23 5:04 PM, Samuel Sieb wrote:
On 11/23/23 16:00, home user wrote:
On 11/23/23 4:56 PM, Samuel Sieb wrote:
On 11/23/23 15:39, home user wrote:
Where is the "6.5.12" kernel coming from, since you don't actually have it installed? Try dnf upgrading your kernel. --
-bash.12[~]: uname -a Linux coyote 6.5.12-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Nov 20 22:12:09 UTC 2023 x86_64 GNU/Linux
-bash.13[~]:
The grub menu also showed 6.5.12 in the top line.
What does "rpm -qf /boot/vmlinuz-6.5.12*" show?
Do I need something more than "dnf --refresh upgrade", or will that be sufficient?
That should be all you need.
-bash.13[~]: rpm -qf /boot/vmlinuz-6.5.12* file /boot/vmlinuz-6.5.12-200.fc38.x86_64 is not owned by any package -bash.14[~]:
I'm really curious how you managed to do that. Check your dnf history.
I'll await your reply to that before proceeding with the "dnf --refresh upgrade".
Go ahead and see what happens.
On 11/23/23 5:53 PM, Samuel Sieb wrote:
On 11/23/23 16:07, home user wrote:
On 11/23/23 5:04 PM, Samuel Sieb wrote:
On 11/23/23 16:00, home user wrote:
On 11/23/23 4:56 PM, Samuel Sieb wrote:
On 11/23/23 15:39, home user wrote:
Where is the "6.5.12" kernel coming from, since you don't actually have it installed? Try dnf upgrading your kernel.
-bash.12[~]: uname -a Linux coyote 6.5.12-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Nov 20 22:12:09 UTC 2023 x86_64 GNU/Linux
-bash.13[~]:
The grub menu also showed 6.5.12 in the top line.
What does "rpm -qf /boot/vmlinuz-6.5.12*" show?
Do I need something more than "dnf --refresh upgrade", or will that be sufficient?
That should be all you need.
-bash.13[~]: rpm -qf /boot/vmlinuz-6.5.12* file /boot/vmlinuz-6.5.12-200.fc38.x86_64 is not owned by any package -bash.14[~]:
I'm really curious how you managed to do that. Check your dnf history.
I'll await your reply to that before proceeding with the "dnf --refresh upgrade".
Go ahead and see what happens.
(sigh) ok, here we go... I rebooted and logged in as root. I did "dnf --refresh upgrade dnf"; that upgraded 7 packages. (none were upgraded by the mid-day upgrade) I did "dnf --refresh upgrade"... - 792 packages were upgraded, plus a few new installs and a few removals. - Only one package, something to do with caja, had trouble during the download phase. That download was successfully retried. - Update phase was long and slow, but I saw no problems. - Clean-up phase had a huge number of failures (warnings), mostly no such file or directory, mostly files with long names that looked they were hex numbers. - the akmod and mandb tasks ran for a while, then the screen went black. - I waited 15+ minutes, then shut off the power. - I powered up and booted; I saw no problems. - No problem logging in. Everything looks "normal" so far. Both monitors look fine. I did do a quick disk check (gsmartcontrol); no indication of trouble.
I would like to run a memory test. Does what Fedora offers now work? I recall from a previous thread that it does not. If it does, please remind me how to install it.
Today's (mountain time) entries from dnf history are: ID | Command line | Date and time | Action(s) | Altered -------------------------------------------------------------------------------- 1525 | -y install --disablerepo= | 2023-11-23 18:45 | Install | 1 1524 | --refresh upgrade | 2023-11-23 18:26 | C, E, I, O, U | 817 EE 1523 | --refresh upgrade dnf | 2023-11-23 18:20 | Upgrade | 7 E< 1522 | upgrade | 2023-11-23 12:25 | C, E, I, U | 83 > Before the 12:25 "upgrade", there was a "dnf --refresh upgrade dnf", but that resulted in "nothing to do".
I'm as much at a loss as you as to what really happened in the mid-day dnf commands. I'm also at a loss as to why the clean-up this evening had so many failures.
Well, so far, things look normal now. Is it worth pursuing this any further? By the way, current kernel: ----- -bash.2[~]: uname -a Linux coyote 6.5.12-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Nov 20 22:12:09 UTC 2023 x86_64 GNU/Linux -bash.3[~]: -----
--
On Thu, 2023-11-23 at 15:44 -0700, home user wrote:
I have no idea how to remove the strange character sequences from the output, so here it is raw:
352:[^[[0;32m OK ^[[0m] Stopped ^[[0;1;39mkmod-static-nodes.…reate List of Static Device Nodes. 364:[^[[0;32m OK ^[[0m] Created slice ^[[0;1;39msystem-akmod…[0m - Slice /system/akmods-keygen.
Just for information, those are ANSI escape code sequences. ANSI is used for things like colouring text, making things bold, cursor movement, etc.
0 reset to normal 1 bold 32 green etc
If you used "less -r /var/log/boot.log" you'd see them displayed using the colour codes to colour the display. And if you really wanted to, you could pipe them through something to strip them out, or use them without showing them, then copy and paste.
less -r /var/log/boot.log|grep ounted
[ OK ] Mounted POSIX Message Queue File System. [ OK ] Mounted Debug File System. [ OK ] Mounted FUSE Control File System. [ OK ] Mounted Huge Pages File System. [ OK ] Mounted NFSD configuration filesystem. [ OK ] Mounted /boot.
That showed up coloured on my terminal, but copy and pasting them into here just gave me the plain text view of them. And, for what it's worth, "grep ounted /var/log/boot.log" did exactly the same thing.
However, you can ignore them as not being important to what you're trying to work out at the moment.
On 11/23/23 19:00, home user wrote:
I'm as much at a loss as you as to what really happened in the mid-day dnf commands. I'm also at a loss as to why the clean-up this evening had so many failures.
It kind of sounds like the earlier upgrade failed somehow. You could check the logs from that time if you're really interested.
Well, so far, things look normal now. Is it worth pursuing this any further? By the way, current kernel:
Probably not worth the time since it's working now.
On 11/23/23 8:52 PM, Samuel Sieb wrote:
On 11/23/23 19:00, home user wrote:
I'm as much at a loss as you as to what really happened in the mid-day dnf commands. I'm also at a loss as to why the clean-up this evening had so many failures.
It kind of sounds like the earlier upgrade failed somehow. You could check the logs from that time if you're really interested.
Well, so far, things look normal now. Is it worth pursuing this any further? By the way, current kernel:
Probably not worth the time since it's working now.
I skimmed the logs; I saw no clues.
No idea what caused the original problem. But the re-do of the dnf commands does seem to have fixed things. I agree it's probably not worth further time and effort trying to diagnose the cause(s).
I've tagged this thread SOLVED. I thank everyone who tried to help.
Bill.
On 11/23/23 8:20 PM, Tim via users wrote:
On Thu, 2023-11-23 at 15:44 -0700, home user wrote:
I have no idea how to remove the strange character sequences from the output, so here it is raw:
352:[^[[0;32m OK ^[[0m] Stopped ^[[0;1;39mkmod-static-nodes.…reate List of Static Device Nodes. 364:[^[[0;32m OK ^[[0m] Created slice ^[[0;1;39msystem-akmod…[0m - Slice /system/akmods-keygen.
Just for information, those are ANSI escape code sequences. ANSI is used for things like colouring text, making things bold, cursor movement, etc.
0 reset to normal 1 bold 32 green etc
If you used "less -r /var/log/boot.log" you'd see them displayed using the colour codes to colour the display. And if you really wanted to, you could pipe them through something to strip them out, or use them without showing them, then copy and paste.
less -r /var/log/boot.log|grep ounted
[ OK ] Mounted POSIX Message Queue File System. [ OK ] Mounted Debug File System. [ OK ] Mounted FUSE Control File System. [ OK ] Mounted Huge Pages File System. [ OK ] Mounted NFSD configuration filesystem. [ OK ] Mounted /boot.
That showed up coloured on my terminal, but copy and pasting them into here just gave me the plain text view of them. And, for what it's worth, "grep ounted /var/log/boot.log" did exactly the same thing.
However, you can ignore them as not being important to what you're trying to work out at the moment.
ok. Thank-you.
On 11/23/23 8:00 PM, home user wrote:
I would like to run a memory test. Does what Fedora offers now work? I recall from a previous thread that it does not. If it does, please remind me how to install it.
It's memtest86+. It's on my work station, accessed during boot-up via the grub menu. It works. My work station's memory seems to be fine.
-
Barry -
home user -
Joe Zeff -
John Pilkington -
Samuel Sieb -
Tim