12:19 p.m.
(f-38; stand-alone work station; nvidia graphics card; dual monitor;
kmod 4xx driver)
I just finished doing a "dnf upgrade" as a prerequisite step to
upgrading from f-38 to f-39.
There were no hints of any problems. The kernel and the graphics driver
were replaced during this "dnf upgrade".
The akmods did finish before I rebooted.
The shutdown took 5 minutes because it ran akmods (a second time?!).
During the boot-up, there was a message that it was failing back to nouveau.
The display is not working properly; only one monitor is being used and
everything is oversized in the display.
I am not comfortable proceeding with the f-38 to f-39 upgrade with the
work station in this condition.
Important: I have only one old kernel. I have no rescue kernel.
How do I get this workstation working properly?
12:27 p.m.
On 4/11/24 12:19, home user wrote:
(f-38; stand-alone work station; nvidia graphics card; dual monitor;
kmod 4xx driver)
I just finished doing a "dnf upgrade" as a prerequisite step to
upgrading from f-38 to f-39.
There were no hints of any problems. The kernel and the graphics driver
were replaced during this "dnf upgrade".
The akmods did finish before I rebooted.
The shutdown took 5 minutes because it ran akmods (a second time?!).
During the boot-up, there was a message that it was failing back to
nouveau.
The display is not working properly; only one monitor is being used and
everything is oversized in the display.
I am not comfortable proceeding with the f-38 to f-39 upgrade with the
work station in this condition.
Important: I have only one old kernel. I have no rescue kernel.
How do I get this workstation working properly?
I just ran into that exact same issue on RHEL 9 instead of Fedora.
I wound up uninstalling all the RPMFusion packages and reinstalling
them, but it didn't help. I waited til all the gcc and depmod and xz
processes completed, it ain't my first rodeo. Still no joy.
I finally just nuked all the RPMFusion packages and downloaded the
drivers directly from https://www.nvidia.com/download/index.aspx and ran
the installer from there. It works fine again. I hate to do it, because
I really prefer the RPMs, but I *had* to get back to work and my desktop
was toast. Three of my four monitors weren't working.
Sorry I don't have better advice, but I feel like something went south
in the RPMFusion packages.
--
Thomas
1:09 p.m.
On Thu, Apr 11, 2024, at 10:19 AM, home user wrote:
(f-38; stand-alone work station; nvidia graphics card; dual monitor;
kmod 4xx driver)
I just finished doing a "dnf upgrade" as a prerequisite step to
upgrading from f-38 to f-39.
There were no hints of any problems. The kernel and the graphics driver
were replaced during this "dnf upgrade".
The akmods did finish before I rebooted.
The shutdown took 5 minutes because it ran akmods (a second time?!).
[snip]
The process running akmods might have finished, but you should not reboot unless it
actually created a module. I use a shell alias I call "kerncheck", which does
the below. You might want to see what this shows you:
ls -ltr /lib/modules/*/extra;echo;ls -ltr /lib/modules;echo;echo -n "Currently booted
to: ";uname -r;echo
If there is no module showing for the new kernel then it clearly can not load. You then
look at the error logs. I don't have Nvidia currently and can't remember where you
find those logs.
1:34 p.m.
On Thu, 11 Apr 2024 11:09:26 -0700
Doug Herr wrote:
I don't have Nvidia currently and can't remember where you
find those logs.
/var/log/akmod/akmod.log
If it doesn't say something about "Success" near the end, then it
didn't
build correctly.
I usually do a tail -f on that file when running dnf update so I can watch
the build process and only reboot after the new module is installed.
2:12 p.m.
On Thu, Apr 11, 2024 at 2:35 PM Tom Horsley <horsley1953(a)gmail.com> wrote:
On Thu, 11 Apr 2024 11:09:26 -0700
Doug Herr wrote:
> I don't have Nvidia currently and can't remember where you find those logs.
/var/log/akmod/akmod.log
If it doesn't say something about "Success" near the end, then it
didn't
build correctly.
I usually do a tail -f on that file when running dnf update so I can watch
the build process and only reboot after the new module is installed.
Forgive my ignorance, I don't use RPMFusion....
When something does not (can not?) build correctly, can you just boot
to an earlier kernel until the problems with the current kernel
modules are fixed? Or does rebuilding akmod break past kernels?
Jeff
2:29 p.m.
On Thu, 11 Apr 2024 15:12:08 -0400
Jeffrey Walton wrote:
When something does not (can not?) build correctly, can you just
boot
to an earlier kernel until the problems with the current kernel
modules are fixed? Or does rebuilding akmod break past kernels?
I've certainly just booted old kernels and had that work. Under
some conditions, I've seen it rebuild the previous kernel module
as well as the new kernel, so I don't know if that would always work,
but it has worked for me in the past.
3:01 p.m.
On 4/11/24 12:34, Tom Horsley wrote:
On Thu, 11 Apr 2024 11:09:26 -0700
Doug Herr wrote:
> I don't have Nvidia currently and can't remember where you find those logs.
/var/log/akmod/akmod.log
If it doesn't say something about "Success" near the end, then it
didn't
build correctly.
I usually do a tail -f on that file when running dnf update so I can watch
the build process and only reboot after the new module is installed.
--
------
bash.15[~]: cd /var/log/akmod
bash: cd: /var/log/akmod: No such file or directory
bash.16[~]: cd /var/log
bash.17[log]: ls a*
akmods:
akmods.log akmods.log-20230801 akmods.log-20231201
akmods.log-20240401
akmods.log-20230501 akmods.log-20230901 akmods.log-20240101
akmods.log-20230601 akmods.log-20231001 akmods.log-20240201
akmods.log-20230701 akmods.log-20231101 akmods.log-20240301
apt:
atop:
audit:
audit.log audit.log.1 audit.log.2 audit.log.3 audit.log.4
bash.18[log]: cd akmods
bash.19[akmods]: vi akmods.log
------
(there was no "Successful" in today's entries)
I tried the command suggested in that log file.
------
bash.24[~]: /usr/sbin/akmods --force
Checking kmods exist for 6.8.4-100.fc38.x86_64 [ OK ]
Building and installing nvidia-470xx-kmod [FAILED]
Building rpms failed; see
/var/cache/akmods/nvidia-470xx/470.223.02-2-for-6.8.4-100.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.25[~]:
------
3:35 p.m.
home user wrote:
I tried the command suggested in that log file.
------
bash.24[~]: /usr/sbin/akmods --force
Checking kmods exist for 6.8.4-100.fc38.x86_64 [ OK ]
Building and installing nvidia-470xx-kmod [FAILED]
Building rpms failed; see
/var/cache/akmods/nvidia-470xx/470.223.02-2-for-6.8.4-100.fc38.x86_64.failed.log
for details
The nvidia 470xx driver packages are orphaned at RPM Fusion.
Someone will need to step up and maintain them there, update
them yourself locally, or swtich to the upstream Nvidia
driver downloads.
I can tell you that building the 2 or 3 nvidia 470xx packages¹
works well for the later 6.7 and current 6.8 kernels.
Though for anyone unfamiliar with using fedpkg/rfpkg or
building rpms in general, it may be easier to just switch to
the stuff Nvidia provides directly.
¹ xorg-x11-drv-nvidia-470xx, nvidia-settings-470xx,
nvidia-470xx-kmod. The settings package may not be
required, I forget. It needs to be updated to match the
others if it's installed.
--
Todd
5:34 p.m.
On 4/11/24 13:01, home user wrote:
I tried the command suggested in that log file.
------
bash.24[~]: /usr/sbin/akmods --force
Checking kmods exist for 6.8.4-100.fc38.x86_64 [ OK ]
Building and installing nvidia-470xx-kmod [FAILED]
Building rpms failed; see
/var/cache/akmods/nvidia-470xx/470.223.02-2-for-6.8.4-100.fc38.x86_64.failed.log for
details
So what's in that log?
5:40 p.m.
On 4/11/24 4:34 PM, Samuel Sieb wrote:
On 4/11/24 13:01, home user wrote:
> I tried the command suggested in that log file.
>
> ------
> bash.24[~]: /usr/sbin/akmods --force
> Checking kmods exist for 6.8.4-100.fc38.x86_64 [ OK ]
> Building and installing nvidia-470xx-kmod [FAILED]
> Building rpms failed; see
/var/cache/akmods/nvidia-470xx/470.223.02-2-for-6.8.4-100.fc38.x86_64.failed.log for
details
So what's in that log?
That's a 906-line file, many of those lines are v-e-r-y long. I could not make any
real sense of it. Shall I put it on the google drive? If yes, how do I get the
non-displayable characters removed or converted?
5:45 p.m.
On 4/11/24 15:40, home user wrote:
On 4/11/24 4:34 PM, Samuel Sieb wrote:
> On 4/11/24 13:01, home user wrote:
>> I tried the command suggested in that log file.
>>
>> ------
>> bash.24[~]: /usr/sbin/akmods --force
>> Checking kmods exist for 6.8.4-100.fc38.x86_64 [ OK ]
>> Building and installing nvidia-470xx-kmod [FAILED]
>> Building rpms failed; see
>> /var/cache/akmods/nvidia-470xx/470.223.02-2-for-6.8.4-100.fc38.x86_64.failed.log
for details
>
> So what's in that log?
That's a 906-line file, many of those lines are v-e-r-y long. I could
not make any real sense of it. Shall I put it on the google drive? If
yes, how do I get the non-displayable characters removed or converted?
I don't know what's in it, so if you're ok with sharing the contents,
you can upload it. Don't worry about the characters.
But paste the last page of it here. That should contain enough
information to work from.
6:05 p.m.
On 4/11/24 4:45 PM, Samuel Sieb wrote:
On 4/11/24 15:40, home user wrote:
> On 4/11/24 4:34 PM, Samuel Sieb wrote:
>> On 4/11/24 13:01, home user wrote:
>>> I tried the command suggested in that log file.
>>>
>>> ------
>>> bash.24[~]: /usr/sbin/akmods --force
>>> Checking kmods exist for 6.8.4-100.fc38.x86_64 [ OK ]
>>> Building and installing nvidia-470xx-kmod [FAILED]
>>> Building rpms failed; see
/var/cache/akmods/nvidia-470xx/470.223.02-2-for-6.8.4-100.fc38.x86_64.failed.log for
details
>>
>> So what's in that log?
>
> That's a 906-line file, many of those lines are v-e-r-y long. I could not make
any real sense of it. Shall I put it on the google drive? If yes, how do I get the
non-displayable characters removed or converted?
I don't know what's in it, so if you're ok with sharing the contents, you can
upload it. Don't worry about the characters.
But paste the last page of it here. That should contain enough information to work
from.
Here's the link:
"https://drive.google.com/file/d/1FebhplV-N6_jV7A9O1ogqCb9tB6g0FJ5/view?usp=sharing".
Here's the bottom, ohhhh, 60 lines...
----------
2024/04/11 14:11:57 akmodsbuild: gcc
-Wp,-MMD,/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-modeset/.nvidia-modeset-linux.o.d
-nostdinc -I./arch/x86/include -I./arch/x86/include/generated -I./include
-I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi
-I./include/generated/uapi -include ./include/linux/compiler-version.h -include
./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__
-fmacro-prefix-map=./= -std=gnu11 -fshort-wchar -funsigned-char -fno-common -fno-PIE
-fno-strict-aliasing -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx
-fcf-protection=branch -fno-jump-tables -m64 -falign-jumps=1 -falign-loops=1 -mno-80387
-mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic
-mno-red-zone -mcmodel=kernel -Wno-sign-compare -fno-asynchronous-unwind-tables
-mindirect-branch=thunk-extern -mindirect-branch-register -mindirect-branch-cs-prefix
-mfunction-return=thunk-extern -fno-jump-tables -mharden-sls=all
-fpatchable-function-entry=16,16 -fno-delete-null-pointer-checks -O2
-fno-allow-store-data-races -fstack-protector-strong -ftrivial-auto-var-init=zero
-fno-stack-clash-protection -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY
-falign-functions=16 -fstrict-flex-arrays=3 -fno-strict-overflow -fno-stack-check
-fconserve-stack -Wall -Wundef -Werror=implicit-function-declaration -Werror=implicit-int
-Werror=return-type -Werror=strict-prototypes -Wno-format-security -Wno-trigraphs
-Wno-frame-address -Wno-address-of-packed-member -Wmissing-declarations
-Wmissing-prototypes -Wframe-larger-than=2048 -Wno-main -Wno-unused-but-set-variable
-Wno-unused-const-variable -Wno-dangling-pointer -Wvla -Wno-pointer-sign
-Wcast-function-type -Wno-stringop-overflow -Wno-array-bounds -Wno-alloc-size-larger-than
-Wimplicit-fallthrough=5 -Werror=date-time -Werror=incompatible-pointer-types
-Werror=designated-init -Wenum-conversion -Wno-unused-but-set-variable
-Wno-unused-const-variable -Wno-restrict -Wno-packed-not-aligned -Wno-format-overflow
-Wno-format-truncation -Wno-stringop-truncation -Wno-missing-field-initializers
-Wno-type-limits -Wno-shift-negative-value -Wno-maybe-uninitialized -Wno-sign-compare -g
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/common/inc
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64
-Wall -MD -Wno-cast-qual -Wno-error -Wno-format-extra-args -D__KERNEL__ -DMODULE -DNVRM
-DNV_VERSION_STRING=\"470.223.02\" -Wno-unused-function -Wuninitialized
-fno-strict-aliasing -mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -Werror=undef
-DNV_SPECTRE_V2=0 -DNV_KERNEL_INTERFACE_LAYER
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-modeset
-UDEBUG -U_DEBUG -DNDEBUG -DNV_BUILD_MODULE_INSTANCES=0 -DMODULE
-DKBUILD_BASENAME='"nvidia_modeset_linux"'
-DKBUILD_MODNAME='"nvidia_modeset"'
-D__KBUILD_MODNAME=kmod_nvidia_modeset -c -o
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-modeset/nvidia-modeset-linux.o
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-modeset/nvidia-modeset-linux.c
2024/04/11 14:11:57 akmodsbuild: # CC [M]
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-modeset/nv-kthread-q.o
2024/04/11 14:11:57 akmodsbuild: gcc
-Wp,-MMD,/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-modeset/.nv-kthread-q.o.d
-nostdinc -I./arch/x86/include -I./arch/x86/include/generated -I./include
-I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi
-I./include/generated/uapi -include ./include/linux/compiler-version.h -include
./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__
-fmacro-prefix-map=./= -std=gnu11 -fshort-wchar -funsigned-char -fno-common -fno-PIE
-fno-strict-aliasing -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx
-fcf-protection=branch -fno-jump-tables -m64 -falign-jumps=1 -falign-loops=1 -mno-80387
-mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic
-mno-red-zone -mcmodel=kernel -Wno-sign-compare -fno-asynchronous-unwind-tables
-mindirect-branch=thunk-extern -mindirect-branch-register -mindirect-branch-cs-prefix
-mfunction-return=thunk-extern -fno-jump-tables -mharden-sls=all
-fpatchable-function-entry=16,16 -fno-delete-null-pointer-checks -O2
-fno-allow-store-data-races -fstack-protector-strong -ftrivial-auto-var-init=zero
-fno-stack-clash-protection -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY
-falign-functions=16 -fstrict-flex-arrays=3 -fno-strict-overflow -fno-stack-check
-fconserve-stack -Wall -Wundef -Werror=implicit-function-declaration -Werror=implicit-int
-Werror=return-type -Werror=strict-prototypes -Wno-format-security -Wno-trigraphs
-Wno-frame-address -Wno-address-of-packed-member -Wmissing-declarations
-Wmissing-prototypes -Wframe-larger-than=2048 -Wno-main -Wno-unused-but-set-variable
-Wno-unused-const-variable -Wno-dangling-pointer -Wvla -Wno-pointer-sign
-Wcast-function-type -Wno-stringop-overflow -Wno-array-bounds -Wno-alloc-size-larger-than
-Wimplicit-fallthrough=5 -Werror=date-time -Werror=incompatible-pointer-types
-Werror=designated-init -Wenum-conversion -Wno-unused-but-set-variable
-Wno-unused-const-variable -Wno-restrict -Wno-packed-not-aligned -Wno-format-overflow
-Wno-format-truncation -Wno-stringop-truncation -Wno-missing-field-initializers
-Wno-type-limits -Wno-shift-negative-value -Wno-maybe-uninitialized -Wno-sign-compare -g
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/common/inc
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64
-Wall -MD -Wno-cast-qual -Wno-error -Wno-format-extra-args -D__KERNEL__ -DMODULE -DNVRM
-DNV_VERSION_STRING=\"470.223.02\" -Wno-unused-function -Wuninitialized
-fno-strict-aliasing -mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -Werror=undef
-DNV_SPECTRE_V2=0 -DNV_KERNEL_INTERFACE_LAYER
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-modeset
-UDEBUG -U_DEBUG -DNDEBUG -DNV_BUILD_MODULE_INSTANCES=0 -DMODULE
-DKBUILD_BASENAME='"nv_kthread_q"'
-DKBUILD_MODNAME='"nvidia_modeset"'
-D__KBUILD_MODNAME=kmod_nvidia_modeset -c -o
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-modeset/nv-kthread-q.o
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-modeset/nv-kthread-q.c
2024/04/11 14:11:57 akmodsbuild: # CC [M]
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm.o
2024/04/11 14:11:57 akmodsbuild: gcc
-Wp,-MMD,/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/.nvidia-drm.o.d
-nostdinc -I./arch/x86/include -I./arch/x86/include/generated -I./include
-I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi
-I./include/generated/uapi -include ./include/linux/compiler-version.h -include
./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__
-fmacro-prefix-map=./= -std=gnu11 -fshort-wchar -funsigned-char -fno-common -fno-PIE
-fno-strict-aliasing -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx
-fcf-protection=branch -fno-jump-tables -m64 -falign-jumps=1 -falign-loops=1 -mno-80387
-mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic
-mno-red-zone -mcmodel=kernel -Wno-sign-compare -fno-asynchronous-unwind-tables
-mindirect-branch=thunk-extern -mindirect-branch-register -mindirect-branch-cs-prefix
-mfunction-return=thunk-extern -fno-jump-tables -mharden-sls=all
-fpatchable-function-entry=16,16 -fno-delete-null-pointer-checks -O2
-fno-allow-store-data-races -fstack-protector-strong -ftrivial-auto-var-init=zero
-fno-stack-clash-protection -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY
-falign-functions=16 -fstrict-flex-arrays=3 -fno-strict-overflow -fno-stack-check
-fconserve-stack -Wall -Wundef -Werror=implicit-function-declaration -Werror=implicit-int
-Werror=return-type -Werror=strict-prototypes -Wno-format-security -Wno-trigraphs
-Wno-frame-address -Wno-address-of-packed-member -Wmissing-declarations
-Wmissing-prototypes -Wframe-larger-than=2048 -Wno-main -Wno-unused-but-set-variable
-Wno-unused-const-variable -Wno-dangling-pointer -Wvla -Wno-pointer-sign
-Wcast-function-type -Wno-stringop-overflow -Wno-array-bounds -Wno-alloc-size-larger-than
-Wimplicit-fallthrough=5 -Werror=date-time -Werror=incompatible-pointer-types
-Werror=designated-init -Wenum-conversion -Wno-unused-but-set-variable
-Wno-unused-const-variable -Wno-restrict -Wno-packed-not-aligned -Wno-format-overflow
-Wno-format-truncation -Wno-stringop-truncation -Wno-missing-field-initializers
-Wno-type-limits -Wno-shift-negative-value -Wno-maybe-uninitialized -Wno-sign-compare -g
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/common/inc
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64
-Wall -MD -Wno-cast-qual -Wno-error -Wno-format-extra-args -D__KERNEL__ -DMODULE -DNVRM
-DNV_VERSION_STRING=\"470.223.02\" -Wno-unused-function -Wuninitialized
-fno-strict-aliasing -mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -Werror=undef
-DNV_SPECTRE_V2=0 -DNV_KERNEL_INTERFACE_LAYER
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm
-UDEBUG -U_DEBUG -DNDEBUG -DNV_BUILD_MODULE_INSTANCES=0 -DMODULE
-DKBUILD_BASENAME='"nvidia_drm"'
-DKBUILD_MODNAME='"nvidia_drm"' -D__KBUILD_MODNAME=kmod_nvidia_drm -c -o
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm.o
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm.c
2024/04/11 14:11:57 akmodsbuild: # CC [M]
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-drv.o
2024/04/11 14:11:57 akmodsbuild: gcc
-Wp,-MMD,/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/.nvidia-drm-drv.o.d
-nostdinc -I./arch/x86/include -I./arch/x86/include/generated -I./include
-I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi
-I./include/generated/uapi -include ./include/linux/compiler-version.h -include
./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__
-fmacro-prefix-map=./= -std=gnu11 -fshort-wchar -funsigned-char -fno-common -fno-PIE
-fno-strict-aliasing -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx
-fcf-protection=branch -fno-jump-tables -m64 -falign-jumps=1 -falign-loops=1 -mno-80387
-mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic
-mno-red-zone -mcmodel=kernel -Wno-sign-compare -fno-asynchronous-unwind-tables
-mindirect-branch=thunk-extern -mindirect-branch-register -mindirect-branch-cs-prefix
-mfunction-return=thunk-extern -fno-jump-tables -mharden-sls=all
-fpatchable-function-entry=16,16 -fno-delete-null-pointer-checks -O2
-fno-allow-store-data-races -fstack-protector-strong -ftrivial-auto-var-init=zero
-fno-stack-clash-protection -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY
-falign-functions=16 -fstrict-flex-arrays=3 -fno-strict-overflow -fno-stack-check
-fconserve-stack -Wall -Wundef -Werror=implicit-function-declaration -Werror=implicit-int
-Werror=return-type -Werror=strict-prototypes -Wno-format-security -Wno-trigraphs
-Wno-frame-address -Wno-address-of-packed-member -Wmissing-declarations
-Wmissing-prototypes -Wframe-larger-than=2048 -Wno-main -Wno-unused-but-set-variable
-Wno-unused-const-variable -Wno-dangling-pointer -Wvla -Wno-pointer-sign
-Wcast-function-type -Wno-stringop-overflow -Wno-array-bounds -Wno-alloc-size-larger-than
-Wimplicit-fallthrough=5 -Werror=date-time -Werror=incompatible-pointer-types
-Werror=designated-init -Wenum-conversion -Wno-unused-but-set-variable
-Wno-unused-const-variable -Wno-restrict -Wno-packed-not-aligned -Wno-format-overflow
-Wno-format-truncation -Wno-stringop-truncation -Wno-missing-field-initializers
-Wno-type-limits -Wno-shift-negative-value -Wno-maybe-uninitialized -Wno-sign-compare -g
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/common/inc
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64
-Wall -MD -Wno-cast-qual -Wno-error -Wno-format-extra-args -D__KERNEL__ -DMODULE -DNVRM
-DNV_VERSION_STRING=\"470.223.02\" -Wno-unused-function -Wuninitialized
-fno-strict-aliasing -mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -Werror=undef
-DNV_SPECTRE_V2=0 -DNV_KERNEL_INTERFACE_LAYER
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm
-UDEBUG -U_DEBUG -DNDEBUG -DNV_BUILD_MODULE_INSTANCES=0 -DMODULE
-DKBUILD_BASENAME='"nvidia_drm_drv"'
-DKBUILD_MODNAME='"nvidia_drm"' -D__KBUILD_MODNAME=kmod_nvidia_drm -c -o
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-drv.o
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-drv.c
2024/04/11 14:11:57 akmodsbuild: # CC [M]
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-utils.o
2024/04/11 14:11:57 akmodsbuild: gcc
-Wp,-MMD,/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/.nvidia-drm-utils.o.d
-nostdinc -I./arch/x86/include -I./arch/x86/include/generated -I./include
-I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi
-I./include/generated/uapi -include ./include/linux/compiler-version.h -include
./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__
-fmacro-prefix-map=./= -std=gnu11 -fshort-wchar -funsigned-char -fno-common -fno-PIE
-fno-strict-aliasing -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx
-fcf-protection=branch -fno-jump-tables -m64 -falign-jumps=1 -falign-loops=1 -mno-80387
-mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic
-mno-red-zone -mcmodel=kernel -Wno-sign-compare -fno-asynchronous-unwind-tables
-mindirect-branch=thunk-extern -mindirect-branch-register -mindirect-branch-cs-prefix
-mfunction-return=thunk-extern -fno-jump-tables -mharden-sls=all
-fpatchable-function-entry=16,16 -fno-delete-null-pointer-checks -O2
-fno-allow-store-data-races -fstack-protector-strong -ftrivial-auto-var-init=zero
-fno-stack-clash-protection -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY
-falign-functions=16 -fstrict-flex-arrays=3 -fno-strict-overflow -fno-stack-check
-fconserve-stack -Wall -Wundef -Werror=implicit-function-declaration -Werror=implicit-int
-Werror=return-type -Werror=strict-prototypes -Wno-format-security -Wno-trigraphs
-Wno-frame-address -Wno-address-of-packed-member -Wmissing-declarations
-Wmissing-prototypes -Wframe-larger-than=2048 -Wno-main -Wno-unused-but-set-variable
-Wno-unused-const-variable -Wno-dangling-pointer -Wvla -Wno-pointer-sign
-Wcast-function-type -Wno-stringop-overflow -Wno-array-bounds -Wno-alloc-size-larger-than
-Wimplicit-fallthrough=5 -Werror=date-time -Werror=incompatible-pointer-types
-Werror=designated-init -Wenum-conversion -Wno-unused-but-set-variable
-Wno-unused-const-variable -Wno-restrict -Wno-packed-not-aligned -Wno-format-overflow
-Wno-format-truncation -Wno-stringop-truncation -Wno-missing-field-initializers
-Wno-type-limits -Wno-shift-negative-value -Wno-maybe-uninitialized -Wno-sign-compare -g
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/common/inc
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64
-Wall -MD -Wno-cast-qual -Wno-error -Wno-format-extra-args -D__KERNEL__ -DMODULE -DNVRM
-DNV_VERSION_STRING=\"470.223.02\" -Wno-unused-function -Wuninitialized
-fno-strict-aliasing -mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -Werror=undef
-DNV_SPECTRE_V2=0 -DNV_KERNEL_INTERFACE_LAYER
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm
-UDEBUG -U_DEBUG -DNDEBUG -DNV_BUILD_MODULE_INSTANCES=0 -DMODULE
-DKBUILD_BASENAME='"nvidia_drm_utils"'
-DKBUILD_MODNAME='"nvidia_drm"' -D__KBUILD_MODNAME=kmod_nvidia_drm -c -o
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-utils.o
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-utils.c
2024/04/11 14:11:57 akmodsbuild:
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-modeset/nvidia-modeset-linux.c:1166:24:
warning: no previous prototype for 'nvkms_open_common' [-Wmissing-prototypes]
2024/04/11 14:11:57 akmodsbuild: 1166 | struct nvkms_per_open *nvkms_open_common(enum
NvKmsClientType type,
2024/04/11 14:11:57 akmodsbuild: | ^~~~~~~~~~~~~~~~~
2024/04/11 14:11:57 akmodsbuild:
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-modeset/nvidia-modeset-linux.c:1218:6:
warning: no previous prototype for 'nvkms_close_common' [-Wmissing-prototypes]
2024/04/11 14:11:57 akmodsbuild: 1218 | void nvkms_close_common(struct nvkms_per_open
*popen)
2024/04/11 14:11:57 akmodsbuild: | ^~~~~~~~~~~~~~~~~~
2024/04/11 14:11:57 akmodsbuild:
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-modeset/nvidia-modeset-linux.c:1281:5:
warning: no previous prototype for 'nvkms_ioctl_common' [-Wmissing-prototypes]
2024/04/11 14:11:57 akmodsbuild: 1281 | int nvkms_ioctl_common
2024/04/11 14:11:57 akmodsbuild: | ^~~~~~~~~~~~~~~~~~
2024/04/11 14:11:57 akmodsbuild: # CC [M]
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-crtc.o
2024/04/11 14:11:57 akmodsbuild: gcc
-Wp,-MMD,/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/.nvidia-drm-crtc.o.d
-nostdinc -I./arch/x86/include -I./arch/x86/include/generated -I./include
-I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi
-I./include/generated/uapi -include ./include/linux/compiler-version.h -include
./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__
-fmacro-prefix-map=./= -std=gnu11 -fshort-wchar -funsigned-char -fno-common -fno-PIE
-fno-strict-aliasing -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx
-fcf-protection=branch -fno-jump-tables -m64 -falign-jumps=1 -falign-loops=1 -mno-80387
-mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic
-mno-red-zone -mcmodel=kernel -Wno-sign-compare -fno-asynchronous-unwind-tables
-mindirect-branch=thunk-extern -mindirect-branch-register -mindirect-branch-cs-prefix
-mfunction-return=thunk-extern -fno-jump-tables -mharden-sls=all
-fpatchable-function-entry=16,16 -fno-delete-null-pointer-checks -O2
-fno-allow-store-data-races -fstack-protector-strong -ftrivial-auto-var-init=zero
-fno-stack-clash-protection -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY
-falign-functions=16 -fstrict-flex-arrays=3 -fno-strict-overflow -fno-stack-check
-fconserve-stack -Wall -Wundef -Werror=implicit-function-declaration -Werror=implicit-int
-Werror=return-type -Werror=strict-prototypes -Wno-format-security -Wno-trigraphs
-Wno-frame-address -Wno-address-of-packed-member -Wmissing-declarations
-Wmissing-prototypes -Wframe-larger-than=2048 -Wno-main -Wno-unused-but-set-variable
-Wno-unused-const-variable -Wno-dangling-pointer -Wvla -Wno-pointer-sign
-Wcast-function-type -Wno-stringop-overflow -Wno-array-bounds -Wno-alloc-size-larger-than
-Wimplicit-fallthrough=5 -Werror=date-time -Werror=incompatible-pointer-types
-Werror=designated-init -Wenum-conversion -Wno-unused-but-set-variable
-Wno-unused-const-variable -Wno-restrict -Wno-packed-not-aligned -Wno-format-overflow
-Wno-format-truncation -Wno-stringop-truncation -Wno-missing-field-initializers
-Wno-type-limits -Wno-shift-negative-value -Wno-maybe-uninitialized -Wno-sign-compare -g
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/common/inc
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64
-Wall -MD -Wno-cast-qual -Wno-error -Wno-format-extra-args -D__KERNEL__ -DMODULE -DNVRM
-DNV_VERSION_STRING=\"470.223.02\" -Wno-unused-function -Wuninitialized
-fno-strict-aliasing -mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -Werror=undef
-DNV_SPECTRE_V2=0 -DNV_KERNEL_INTERFACE_LAYER
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm
-UDEBUG -U_DEBUG -DNDEBUG -DNV_BUILD_MODULE_INSTANCES=0 -DMODULE
-DKBUILD_BASENAME='"nvidia_drm_crtc"'
-DKBUILD_MODNAME='"nvidia_drm"' -D__KBUILD_MODNAME=kmod_nvidia_drm -c -o
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-crtc.o
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-crtc.c
2024/04/11 14:11:57 akmodsbuild: # CC [M]
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-encoder.o
2024/04/11 14:11:57 akmodsbuild: gcc
-Wp,-MMD,/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/.nvidia-drm-encoder.o.d
-nostdinc -I./arch/x86/include -I./arch/x86/include/generated -I./include
-I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi
-I./include/generated/uapi -include ./include/linux/compiler-version.h -include
./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__
-fmacro-prefix-map=./= -std=gnu11 -fshort-wchar -funsigned-char -fno-common -fno-PIE
-fno-strict-aliasing -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx
-fcf-protection=branch -fno-jump-tables -m64 -falign-jumps=1 -falign-loops=1 -mno-80387
-mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic
-mno-red-zone -mcmodel=kernel -Wno-sign-compare -fno-asynchronous-unwind-tables
-mindirect-branch=thunk-extern -mindirect-branch-register -mindirect-branch-cs-prefix
-mfunction-return=thunk-extern -fno-jump-tables -mharden-sls=all
-fpatchable-function-entry=16,16 -fno-delete-null-pointer-checks -O2
-fno-allow-store-data-races -fstack-protector-strong -ftrivial-auto-var-init=zero
-fno-stack-clash-protection -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY
-falign-functions=16 -fstrict-flex-arrays=3 -fno-strict-overflow -fno-stack-check
-fconserve-stack -Wall -Wundef -Werror=implicit-function-declaration -Werror=implicit-int
-Werror=return-type -Werror=strict-prototypes -Wno-format-security -Wno-trigraphs
-Wno-frame-address -Wno-address-of-packed-member -Wmissing-declarations
-Wmissing-prototypes -Wframe-larger-than=2048 -Wno-main -Wno-unused-but-set-variable
-Wno-unused-const-variable -Wno-dangling-pointer -Wvla -Wno-pointer-sign
-Wcast-function-type -Wno-stringop-overflow -Wno-array-bounds -Wno-alloc-size-larger-than
-Wimplicit-fallthrough=5 -Werror=date-time -Werror=incompatible-pointer-types
-Werror=designated-init -Wenum-conversion -Wno-unused-but-set-variable
-Wno-unused-const-variable -Wno-restrict -Wno-packed-not-aligned -Wno-format-overflow
-Wno-format-truncation -Wno-stringop-truncation -Wno-missing-field-initializers
-Wno-type-limits -Wno-shift-negative-value -Wno-maybe-uninitialized -Wno-sign-compare -g
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/common/inc
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64
-Wall -MD -Wno-cast-qual -Wno-error -Wno-format-extra-args -D__KERNEL__ -DMODULE -DNVRM
-DNV_VERSION_STRING=\"470.223.02\" -Wno-unused-function -Wuninitialized
-fno-strict-aliasing -mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -Werror=undef
-DNV_SPECTRE_V2=0 -DNV_KERNEL_INTERFACE_LAYER
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm
-UDEBUG -U_DEBUG -DNDEBUG -DNV_BUILD_MODULE_INSTANCES=0 -DMODULE
-DKBUILD_BASENAME='"nvidia_drm_encoder"'
-DKBUILD_MODNAME='"nvidia_drm"' -D__KBUILD_MODNAME=kmod_nvidia_drm -c -o
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-encoder.o
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-encoder.c
2024/04/11 14:11:57 akmodsbuild: # CC [M]
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-connector.o
2024/04/11 14:11:57 akmodsbuild: gcc
-Wp,-MMD,/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/.nvidia-drm-connector.o.d
-nostdinc -I./arch/x86/include -I./arch/x86/include/generated -I./include
-I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi
-I./include/generated/uapi -include ./include/linux/compiler-version.h -include
./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__
-fmacro-prefix-map=./= -std=gnu11 -fshort-wchar -funsigned-char -fno-common -fno-PIE
-fno-strict-aliasing -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx
-fcf-protection=branch -fno-jump-tables -m64 -falign-jumps=1 -falign-loops=1 -mno-80387
-mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic
-mno-red-zone -mcmodel=kernel -Wno-sign-compare -fno-asynchronous-unwind-tables
-mindirect-branch=thunk-extern -mindirect-branch-register -mindirect-branch-cs-prefix
-mfunction-return=thunk-extern -fno-jump-tables -mharden-sls=all
-fpatchable-function-entry=16,16 -fno-delete-null-pointer-checks -O2
-fno-allow-store-data-races -fstack-protector-strong -ftrivial-auto-var-init=zero
-fno-stack-clash-protection -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY
-falign-functions=16 -fstrict-flex-arrays=3 -fno-strict-overflow -fno-stack-check
-fconserve-stack -Wall -Wundef -Werror=implicit-function-declaration -Werror=implicit-int
-Werror=return-type -Werror=strict-prototypes -Wno-format-security -Wno-trigraphs
-Wno-frame-address -Wno-address-of-packed-member -Wmissing-declarations
-Wmissing-prototypes -Wframe-larger-than=2048 -Wno-main -Wno-unused-but-set-variable
-Wno-unused-const-variable -Wno-dangling-pointer -Wvla -Wno-pointer-sign
-Wcast-function-type -Wno-stringop-overflow -Wno-array-bounds -Wno-alloc-size-larger-than
-Wimplicit-fallthrough=5 -Werror=date-time -Werror=incompatible-pointer-types
-Werror=designated-init -Wenum-conversion -Wno-unused-but-set-variable
-Wno-unused-const-variable -Wno-restrict -Wno-packed-not-aligned -Wno-format-overflow
-Wno-format-truncation -Wno-stringop-truncation -Wno-missing-field-initializers
-Wno-type-limits -Wno-shift-negative-value -Wno-maybe-uninitialized -Wno-sign-compare -g
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/common/inc
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64
-Wall -MD -Wno-cast-qual -Wno-error -Wno-format-extra-args -D__KERNEL__ -DMODULE -DNVRM
-DNV_VERSION_STRING=\"470.223.02\" -Wno-unused-function -Wuninitialized
-fno-strict-aliasing -mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -Werror=undef
-DNV_SPECTRE_V2=0 -DNV_KERNEL_INTERFACE_LAYER
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm
-UDEBUG -U_DEBUG -DNDEBUG -DNV_BUILD_MODULE_INSTANCES=0 -DMODULE
-DKBUILD_BASENAME='"nvidia_drm_connector"'
-DKBUILD_MODNAME='"nvidia_drm"' -D__KBUILD_MODNAME=kmod_nvidia_drm -c -o
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-connector.o
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-connector.c
2024/04/11 14:11:57 akmodsbuild: # CC [M]
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-gem.o
2024/04/11 14:11:57 akmodsbuild: gcc
-Wp,-MMD,/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/.nvidia-drm-gem.o.d
-nostdinc -I./arch/x86/include -I./arch/x86/include/generated -I./include
-I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi
-I./include/generated/uapi -include ./include/linux/compiler-version.h -include
./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__
-fmacro-prefix-map=./= -std=gnu11 -fshort-wchar -funsigned-char -fno-common -fno-PIE
-fno-strict-aliasing -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx
-fcf-protection=branch -fno-jump-tables -m64 -falign-jumps=1 -falign-loops=1 -mno-80387
-mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic
-mno-red-zone -mcmodel=kernel -Wno-sign-compare -fno-asynchronous-unwind-tables
-mindirect-branch=thunk-extern -mindirect-branch-register -mindirect-branch-cs-prefix
-mfunction-return=thunk-extern -fno-jump-tables -mharden-sls=all
-fpatchable-function-entry=16,16 -fno-delete-null-pointer-checks -O2
-fno-allow-store-data-races -fstack-protector-strong -ftrivial-auto-var-init=zero
-fno-stack-clash-protection -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY
-falign-functions=16 -fstrict-flex-arrays=3 -fno-strict-overflow -fno-stack-check
-fconserve-stack -Wall -Wundef -Werror=implicit-function-declaration -Werror=implicit-int
-Werror=return-type -Werror=strict-prototypes -Wno-format-security -Wno-trigraphs
-Wno-frame-address -Wno-address-of-packed-member -Wmissing-declarations
-Wmissing-prototypes -Wframe-larger-than=2048 -Wno-main -Wno-unused-but-set-variable
-Wno-unused-const-variable -Wno-dangling-pointer -Wvla -Wno-pointer-sign
-Wcast-function-type -Wno-stringop-overflow -Wno-array-bounds -Wno-alloc-size-larger-than
-Wimplicit-fallthrough=5 -Werror=date-time -Werror=incompatible-pointer-types
-Werror=designated-init -Wenum-conversion -Wno-unused-but-set-variable
-Wno-unused-const-variable -Wno-restrict -Wno-packed-not-aligned -Wno-format-overflow
-Wno-format-truncation -Wno-stringop-truncation -Wno-missing-field-initializers
-Wno-type-limits -Wno-shift-negative-value -Wno-maybe-uninitialized -Wno-sign-compare -g
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/common/inc
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64
-Wall -MD -Wno-cast-qual -Wno-error -Wno-format-extra-args -D__KERNEL__ -DMODULE -DNVRM
-DNV_VERSION_STRING=\"470.223.02\" -Wno-unused-function -Wuninitialized
-fno-strict-aliasing -mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -Werror=undef
-DNV_SPECTRE_V2=0 -DNV_KERNEL_INTERFACE_LAYER
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm
-UDEBUG -U_DEBUG -DNDEBUG -DNV_BUILD_MODULE_INSTANCES=0 -DMODULE
-DKBUILD_BASENAME='"nvidia_drm_gem"'
-DKBUILD_MODNAME='"nvidia_drm"' -D__KBUILD_MODNAME=kmod_nvidia_drm -c -o
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-gem.o
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-gem.c
2024/04/11 14:11:57 akmodsbuild: # CC [M]
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-fb.o
2024/04/11 14:11:57 akmodsbuild: gcc
-Wp,-MMD,/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/.nvidia-drm-fb.o.d
-nostdinc -I./arch/x86/include -I./arch/x86/include/generated -I./include
-I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi
-I./include/generated/uapi -include ./include/linux/compiler-version.h -include
./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__
-fmacro-prefix-map=./= -std=gnu11 -fshort-wchar -funsigned-char -fno-common -fno-PIE
-fno-strict-aliasing -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx
-fcf-protection=branch -fno-jump-tables -m64 -falign-jumps=1 -falign-loops=1 -mno-80387
-mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic
-mno-red-zone -mcmodel=kernel -Wno-sign-compare -fno-asynchronous-unwind-tables
-mindirect-branch=thunk-extern -mindirect-branch-register -mindirect-branch-cs-prefix
-mfunction-return=thunk-extern -fno-jump-tables -mharden-sls=all
-fpatchable-function-entry=16,16 -fno-delete-null-pointer-checks -O2
-fno-allow-store-data-races -fstack-protector-strong -ftrivial-auto-var-init=zero
-fno-stack-clash-protection -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY
-falign-functions=16 -fstrict-flex-arrays=3 -fno-strict-overflow -fno-stack-check
-fconserve-stack -Wall -Wundef -Werror=implicit-function-declaration -Werror=implicit-int
-Werror=return-type -Werror=strict-prototypes -Wno-format-security -Wno-trigraphs
-Wno-frame-address -Wno-address-of-packed-member -Wmissing-declarations
-Wmissing-prototypes -Wframe-larger-than=2048 -Wno-main -Wno-unused-but-set-variable
-Wno-unused-const-variable -Wno-dangling-pointer -Wvla -Wno-pointer-sign
-Wcast-function-type -Wno-stringop-overflow -Wno-array-bounds -Wno-alloc-size-larger-than
-Wimplicit-fallthrough=5 -Werror=date-time -Werror=incompatible-pointer-types
-Werror=designated-init -Wenum-conversion -Wno-unused-but-set-variable
-Wno-unused-const-variable -Wno-restrict -Wno-packed-not-aligned -Wno-format-overflow
-Wno-format-truncation -Wno-stringop-truncation -Wno-missing-field-initializers
-Wno-type-limits -Wno-shift-negative-value -Wno-maybe-uninitialized -Wno-sign-compare -g
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/common/inc
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64
-Wall -MD -Wno-cast-qual -Wno-error -Wno-format-extra-args -D__KERNEL__ -DMODULE -DNVRM
-DNV_VERSION_STRING=\"470.223.02\" -Wno-unused-function -Wuninitialized
-fno-strict-aliasing -mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -Werror=undef
-DNV_SPECTRE_V2=0 -DNV_KERNEL_INTERFACE_LAYER
-I/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm
-UDEBUG -U_DEBUG -DNDEBUG -DNV_BUILD_MODULE_INSTANCES=0 -DMODULE
-DKBUILD_BASENAME='"nvidia_drm_fb"'
-DKBUILD_MODNAME='"nvidia_drm"' -D__KBUILD_MODNAME=kmod_nvidia_drm -c -o
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-fb.o
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-fb.c
2024/04/11 14:11:57 akmodsbuild: In file included from
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-drv.c:60:
2024/04/11 14:11:57 akmodsbuild:
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-drv.c:748:40:
error: 'DRM_UNLOCKED' undeclared here (not in a function); did you mean
'VM_LOCKED'?
2024/04/11 14:11:57 akmodsbuild: 748 |
DRM_RENDER_ALLOW|DRM_UNLOCKED),
2024/04/11 14:11:57 akmodsbuild: |
^~~~~~~~~~~~
2024/04/11 14:11:57 akmodsbuild: ./include/drm/drm_ioctl.h:155:26: note: in definition of
macro 'DRM_IOCTL_DEF_DRV'
2024/04/11 14:11:57 akmodsbuild: 155 | .flags = _flags,
\
2024/04/11 14:11:57 akmodsbuild: | ^~~~~~
2024/04/11 14:11:57 akmodsbuild: make[3]: *** [scripts/Makefile.build:243:
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-drv.o]
Error 1
2024/04/11 14:11:57 akmodsbuild: make[3]: *** Waiting for unfinished jobs....
2024/04/11 14:11:57 akmodsbuild:
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-crtc.c:
In function 'plane_req_config_update':
2024/04/11 14:11:57 akmodsbuild:
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-crtc.c:89:9:
warning: unused variable 'ret' [-Wunused-variable]
2024/04/11 14:11:57 akmodsbuild: 89 | int ret = 0;
2024/04/11 14:11:57 akmodsbuild: | ^~~
2024/04/11 14:11:57 akmodsbuild:
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-crtc.c:
In function 'nv_drm_plane_atomic_set_property':
2024/04/11 14:11:57 akmodsbuild:
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-crtc.c:371:32:
warning: unused variable 'nv_drm_plane_state' [-Wunused-variable]
2024/04/11 14:11:57 akmodsbuild: 371 | struct nv_drm_plane_state *nv_drm_plane_state
=
2024/04/11 14:11:57 akmodsbuild: |
^~~~~~~~~~~~~~~~~~
2024/04/11 14:11:57 akmodsbuild: make[2]: ***
[/usr/src/kernels/6.8.4-100.fc38.x86_64/Makefile:1939:
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64]
Error 2
2024/04/11 14:11:57 akmodsbuild: make[1]: *** [Makefile:252: __sub-make] Error 2
2024/04/11 14:11:57 akmodsbuild: make[1]: Leaving directory
'/usr/src/kernels/6.8.4-100.fc38.x86_64'
2024/04/11 14:11:57 akmodsbuild: make: *** [Makefile:80: modules] Error 2
2024/04/11 14:11:57 akmodsbuild: error: Bad exit status from /var/tmp/rpm-tmp.0iu6mP
(%build)
2024/04/11 14:11:57 akmodsbuild:
2024/04/11 14:11:57 akmodsbuild: RPM build warnings:
2024/04/11 14:11:57 akmodsbuild: user mockbuild does not exist - using root
2024/04/11 14:11:57 akmodsbuild: user mockbuild does not exist - using root
2024/04/11 14:11:57 akmodsbuild: user mockbuild does not exist - using root
2024/04/11 14:11:57 akmodsbuild:
2024/04/11 14:11:57 akmodsbuild: RPM build errors:
2024/04/11 14:11:57 akmodsbuild: Bad exit status from /var/tmp/rpm-tmp.0iu6mP
(%build)
2024/04/11 14:11:57 akmodsbuild:
2024/04/11 14:11:57 akmods: Building rpms failed; see
/var/cache/akmods/nvidia-470xx/470.223.02-2-for-6.8.4-100.fc38.x86_64.failed.log for
details
----------
6:31 p.m.
On 4/11/24 16:05, home user wrote:
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-drv.c:748:40:
error: 'DRM_UNLOCKED' undeclared here (not in a function); did you mean
'VM_LOCKED'?
There has been a kernel change of some sort. The driver needs to be
updated to match the kernel.
You will not get this driver to build on any newer kernels.
6:36 p.m.
On 4/11/24 5:31 PM, Samuel Sieb wrote:
On 4/11/24 16:05, home user wrote:
>
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-drv.c:748:40:
error: 'DRM_UNLOCKED' undeclared here (not in a function); did you mean
'VM_LOCKED'?
There has been a kernel change of some sort. The driver needs to be updated to match the
kernel.
You will not get this driver to build on any newer kernels.
--
So realistically, my only practical choice is what Todd suggested, "to just switch to
the stuff Nvidia provides directly"?
6:39 p.m.
On 4/11/24 16:36, home user wrote:
On 4/11/24 5:31 PM, Samuel Sieb wrote:
> On 4/11/24 16:05, home user wrote:
>>
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-drv.c:748:40:
error: 'DRM_UNLOCKED' undeclared here (not in a function); did you mean
'VM_LOCKED'?
>
> There has been a kernel change of some sort. The driver needs to be
> updated to match the kernel.
>
> You will not get this driver to build on any newer kernels.
> --
So realistically, my only practical choice is what Todd suggested, "to
just switch to the stuff Nvidia provides directly"?
Unless there's a hope of the rpmfusion package getting updated, it looks
like it. I'm not really familiar with akmods, but maybe you could just
update the source somehow.
6:52 p.m.
On 4/11/24 5:39 PM, Samuel Sieb wrote:
On 4/11/24 16:36, home user wrote:
> On 4/11/24 5:31 PM, Samuel Sieb wrote:
>> On 4/11/24 16:05, home user wrote:
>>>
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-drv.c:748:40:
error: 'DRM_UNLOCKED' undeclared here (not in a function); did you mean
'VM_LOCKED'?
>>
>> There has been a kernel change of some sort. The driver needs to be updated to
match the kernel.
>>
>> You will not get this driver to build on any newer kernels.
>> --
>
> So realistically, my only practical choice is what Todd suggested, "to just
switch to the stuff Nvidia provides directly"?
Unless there's a hope of the rpmfusion package getting updated, it looks like it.
I'm not really familiar with akmods, but maybe you could just update the source
somehow.
I'm not a systems administrator. I need someone to step me through the full switch in
detail.
Reminders:
This is a dual boot (Fedora-38 and windows-7) stand-alone work station; it's 11 years
old.
I have only one old kernel, and no rescue kernel.
The graphics card is an nvidia GeForce GTX 660.
(anything else?)
7:06 p.m.
On Thu, 11 Apr 2024 17:52:10 -0600
home user wrote:
kmod_build_6.8.4-100.fc38.x86_64
Possibly relevant, but I don't know what it means for sure:
My system gets regular updates. I've never had a yadda-yadda-100 kernel,
all mine are -200. Currently I'm running 6.8.4-200.fc39.x86_64, all the
kernels in my old fedora 38 partition are also -200, not -100.
8 p.m.
On Thu, Apr 11, 2024 at 8:06 PM Tom Horsley <horsley1953(a)gmail.com> wrote:
On Thu, 11 Apr 2024 17:52:10 -0600
home user wrote:
> kmod_build_6.8.4-100.fc38.x86_64
Possibly relevant, but I don't know what it means for sure:
My system gets regular updates. I've never had a yadda-yadda-100 kernel,
all mine are -200. Currently I'm running 6.8.4-200.fc39.x86_64, all the
kernels in my old fedora 38 partition are also -200, not -100.
Contrary data point - my fc38 systems all have "-100" kernels and they
get dnf updates every week. Wouldn't think it is relevant, but just
in case, I build using the server-netinstall iso and have it install
KDE.
OTOH, my lone fc39 system has "-200" kernels.
8:49 p.m.
On 4/11/24 7:00 PM, Go Canes wrote:
On Thu, Apr 11, 2024 at 8:06 PM Tom Horsley
<horsley1953(a)gmail.com> wrote:
>
> On Thu, 11 Apr 2024 17:52:10 -0600
> home user wrote:
>
>> kmod_build_6.8.4-100.fc38.x86_64
>
> Possibly relevant, but I don't know what it means for sure:
>
> My system gets regular updates. I've never had a yadda-yadda-100 kernel,
> all mine are -200. Currently I'm running 6.8.4-200.fc39.x86_64, all the
> kernels in my old fedora 38 partition are also -200, not -100.
Contrary data point - my fc38 systems all have "-100" kernels and they
get dnf updates every week. Wouldn't think it is relevant, but just
in case, I build using the server-netinstall iso and have it install
KDE.
OTOH, my lone fc39 system has "-200" kernels.
--
I checked my dnf logs. It seems the last time there was a -200 kernel (or anything else
with a -200 in the name/version) on this workstation was mid-December 2023.
What does the -100 vs. -200 signify?
8:51 p.m.
On 4/11/24 18:49, home user wrote:
On 4/11/24 7:00 PM, Go Canes wrote:
> On Thu, Apr 11, 2024 at 8:06 PM Tom Horsley <horsley1953(a)gmail.com>
> wrote:
>>
>> On Thu, 11 Apr 2024 17:52:10 -0600
>> home user wrote:
>>
>>> kmod_build_6.8.4-100.fc38.x86_64
>>
>> Possibly relevant, but I don't know what it means for sure:
>>
>> My system gets regular updates. I've never had a yadda-yadda-100 kernel,
>> all mine are -200. Currently I'm running 6.8.4-200.fc39.x86_64, all the
>> kernels in my old fedora 38 partition are also -200, not -100.
>
> Contrary data point - my fc38 systems all have "-100" kernels and they
> get dnf updates every week. Wouldn't think it is relevant, but just
> in case, I build using the server-netinstall iso and have it install
> KDE.
>
> OTOH, my lone fc39 system has "-200" kernels.
> --
I checked my dnf logs. It seems the last time there was a -200 kernel
(or anything else with a -200 in the name/version) on this workstation
was mid-December 2023.
What does the -100 vs. -200 signify?
If I remember correctly, it's just a special numbering system between
releases to make upgrades work correctly.
9:19 p.m.
home user composed on 2024-04-11 19:49 (UTC-0600):
What does the -100 vs. -200 signify?
From observation, not reading any doc:
A fresh Fedora release gets -300, moving the prior release to -200, and the prior
to prior release to -100. After the prior-prior's support ends, there is only
current, prior, and rawhide. At some later point, next release gets branched from
Rawhide. I think it's at or before branching that prior gets switched from -200 to
-100, and current gets switched from -300 to -200. So, latest/current, with next
imminent, is F39 is -200 and F38 is -100, with F40 about to be released with -300.
Does it actually have any more meaning? I haven't been able to spot anything more
than at upgrade time, allowing the same version of kernel to be installed twice,
first within the old release, then again from upgrading to the new release.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
5:05 p.m.
On 12 Apr 2024, at 01:06, Tom Horsley <horsley1953(a)gmail.com>
wrote:
My system gets regular updates. I've never had a yadda-yadda-100 kernel,
all mine are -200. Currently I'm running 6.8.4-200.fc39.x86_64, all the
kernels in my old fedora 38 partition are also -200, not -100.
The -NNN is the version that is provided by the kernel team.
At latest builds are:
kernel-6.8.5-101.fc38
kernel-6.8.5-201.fc39
kernel-6.8.5-301.fc40
I think the idea is that upgrade from f38 to f39 will pull in a new kernel
and like wise for a f39 to f40 upgrade.
I think it's numbered for next (f40), current (f39) and previous (f38) fedora
releases.
Barry
6:58 a.m.
On 12/04/2024 00:52, home user wrote:
On 4/11/24 5:39 PM, Samuel Sieb wrote:
> On 4/11/24 16:36, home user wrote:
>> On 4/11/24 5:31 PM, Samuel Sieb wrote:
>>> On 4/11/24 16:05, home user wrote:
>>>>
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-drv.c:748:40:
error: 'DRM_UNLOCKED' undeclared here (not in a function); did you mean
'VM_LOCKED'?
>>>
>>> There has been a kernel change of some sort. The driver needs to be
>>> updated to match the kernel.
>>>
>>> You will not get this driver to build on any newer kernels.
>>> --
>>
>> So realistically, my only practical choice is what Todd suggested,
>> "to just switch to the stuff Nvidia provides directly"?
>
> Unless there's a hope of the rpmfusion package getting updated, it
> looks like it. I'm not really familiar with akmods, but maybe you
> could just update the source somehow.
I'm not a systems administrator. I need someone to step me through the
full switch in detail.
Reminders:
This is a dual boot (Fedora-38 and windows-7) stand-alone work station;
it's 11 years old.
I have only one old kernel, and no rescue kernel.
The graphics card is an nvidia GeForce GTX 660.
(anything else?)
I have two systems affected by this, and have posted about it on the
rpmfusion and fedora-kde lists. I'm having trouble accessing the
rpmfusion archive, so maybe a comment here is in order.
Both systems have GeForce GT 710 cards. This is low-spec, not for
gamers, and I've been using the rpmfusion 470xx drivers for years. I
upgraded from F38 to F39 around 2 weeks ago.
AIUI we are moving from X11 graphics towards Wayland, which the nvidia
driver will not support; but nouveau might. So I've been trying it.
On one box it's working acceptably, with VGA nad HDMI screens.
Single-boot F39.
The other box is dual-boot with Windows 10. I can boot into Fedora only
with 'nomodeset', when I get a single screen HDMI 800x600 which seems
fine but limited. I can run MythTV frontend with --geometry
720x504+40+20, and mythleanfront on an Android tv.
The biggest worry is getting past a frozen boot, so I don't want to make
any recommendations. I have removed all the *nvidia* rpms except
nvidia-gpu-firmware, and installed nouveau-firmware from the
rpmfusion-nonfree-tainted repo.
Maybe the rpmfusion team will make the old system work soon, or maybe
the even-older but just-updated 340xx driver would work. I'll try
living with what I have for now.
HTH
John P
6:47 a.m.
On 12/04/2024 12:58, John Pilkington wrote:
On 12/04/2024 00:52, home user wrote:
> On 4/11/24 5:39 PM, Samuel Sieb wrote:
>> On 4/11/24 16:36, home user wrote:
>>> On 4/11/24 5:31 PM, Samuel Sieb wrote:
>>>> On 4/11/24 16:05, home user wrote:
>>>>>
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-drv.c:748:40:
error: 'DRM_UNLOCKED' undeclared here (not in a function); did you mean
'VM_LOCKED'?
>>>>
>>>> There has been a kernel change of some sort. The driver needs to
>>>> be updated to match the kernel.
>>>>
>>>> You will not get this driver to build on any newer kernels.
>>>> --
>>>
>>> So realistically, my only practical choice is what Todd suggested,
>>> "to just switch to the stuff Nvidia provides directly"?
>>
>> Unless there's a hope of the rpmfusion package getting updated, it
>> looks like it. I'm not really familiar with akmods, but maybe you
>> could just update the source somehow.
>
> I'm not a systems administrator. I need someone to step me through
> the full switch in detail.
> Reminders:
> This is a dual boot (Fedora-38 and windows-7) stand-alone work
> station; it's 11 years old.
> I have only one old kernel, and no rescue kernel.
> The graphics card is an nvidia GeForce GTX 660.
> (anything else?)
I have two systems affected by this, and have posted about it on the
rpmfusion and fedora-kde lists. I'm having trouble accessing the
rpmfusion archive, so maybe a comment here is in order.
Both systems have GeForce GT 710 cards. This is low-spec, not for
gamers, and I've been using the rpmfusion 470xx drivers for years. I
upgraded from F38 to F39 around 2 weeks ago.
AIUI we are moving from X11 graphics towards Wayland, which the nvidia
driver will not support; but nouveau might. So I've been trying it.
On one box it's working acceptably, with VGA nad HDMI screens.
Single-boot F39.
The other box is dual-boot with Windows 10. I can boot into Fedora only
with 'nomodeset', when I get a single screen HDMI 800x600 which seems
fine but limited. I can run MythTV frontend with --geometry
720x504+40+20
The biggest worry is getting past a frozen boot, so I don't want to make
any recommendations. I have removed all the *nvidia* rpms except
nvidia-gpu-firmware, and installed nouveau-firmware from the
rpmfusion-nonfree-tainted repo.
Maybe the rpmfusion team will make the old system work soon, or maybe
the even-older but just-updated 340xx driver would work. I'll try
living with what I have for now.
After kernel and firmware updates today the behaviour of both systems,
using nouveau, seems essentially unchanged from the report above.
kernel now is 6.8.5-201.fc39.x86-64
If the 'nomodeset' is edited out in grub, a reboot of the dual-boot box
still hangs almost immediately.
I've removed the claim that mythleanfront works with mythbackend on the
dual-boot box. I think that was mistaken, and a local permissions issue.
HTH
John P
9:29 a.m.
On 14 Apr 2024 at 12:47, John Pilkington wrote:
Date sent: Sun, 14 Apr 2024 12:47:57 +0100
Subject: Re: crippling nvidia display issue.
From: John Pilkington <johnpilk222(a)gmail.com>
To: users(a)lists.fedoraproject.org
Send reply to: Community support for Fedora users
<users(a)lists.fedoraproject.org>
On 12/04/2024 12:58, John Pilkington wrote:
> On 12/04/2024 00:52, home user wrote:
>> On 4/11/24 5:39 PM, Samuel Sieb wrote:
>>> On 4/11/24 16:36, home user wrote:
>>>> On 4/11/24 5:31 PM, Samuel Sieb wrote:
>>>>> On 4/11/24 16:05, home user wrote:
>>>>>>
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-drv.c:748:40:
error: 'DRM_UNLOCKED' undeclared here (not in a function); did you mean
'VM_LOCKED'?
>>>>>
>>>>> There has been a kernel change of some sort. The driver needs to
>>>>> be updated to match the kernel.
>>>>>
>>>>> You will not get this driver to build on any newer kernels.
>>>>> --
>>>>
>>>> So realistically, my only practical choice is what Todd suggested,
>>>> "to just switch to the stuff Nvidia provides directly"?
>>>
>>> Unless there's a hope of the rpmfusion package getting updated, it
>>> looks like it. I'm not really familiar with akmods, but maybe you
>>> could just update the source somehow.
>>
>> I'm not a systems administrator. I need someone to step me through
>> the full switch in detail.
>> Reminders:
>> This is a dual boot (Fedora-38 and windows-7) stand-alone work
>> station; it's 11 years old.
>> I have only one old kernel, and no rescue kernel.
>> The graphics card is an nvidia GeForce GTX 660.
>> (anything else?)
>
> I have two systems affected by this, and have posted about it on the
> rpmfusion and fedora-kde lists. I'm having trouble accessing the
> rpmfusion archive, so maybe a comment here is in order.
>
> Both systems have GeForce GT 710 cards. This is low-spec, not for
> gamers, and I've been using the rpmfusion 470xx drivers for years. I
> upgraded from F38 to F39 around 2 weeks ago.
>
> AIUI we are moving from X11 graphics towards Wayland, which the nvidia
> driver will not support; but nouveau might. So I've been trying it.
>
> On one box it's working acceptably, with VGA nad HDMI screens.
> Single-boot F39.
>
> The other box is dual-boot with Windows 10. I can boot into Fedora only
> with 'nomodeset', when I get a single screen HDMI 800x600 which seems
> fine but limited. I can run MythTV frontend with --geometry
> 720x504+40+20
>
> The biggest worry is getting past a frozen boot, so I don't want to make
> any recommendations. I have removed all the *nvidia* rpms except
> nvidia-gpu-firmware, and installed nouveau-firmware from the
> rpmfusion-nonfree-tainted repo.
>
> Maybe the rpmfusion team will make the old system work soon, or maybe
> the even-older but just-updated 340xx driver would work. I'll try
> living with what I have for now.
After kernel and firmware updates today the behaviour of both systems,
using nouveau, seems essentially unchanged from the report above.
kernel now is 6.8.5-201.fc39.x86-64
If the 'nomodeset' is edited out in grub, a reboot of the dual-boot box
still hangs almost immediately.
I've removed the claim that mythleanfront works with mythbackend on the
dual-boot box. I think that was mistaken, and a local permissions issue.
>
> HTH
>
> John P
>
>
>
--
Just as an additional note. I have an older Acer notebook that has
an NVIDIA GT 650M that had been working fine with the
rpmfusion driver. Have BOINC using its GPU for a project.
After recent kernel upgrade, I noticed it was no longer working.
Tried reinstalling the rpm and it fails to build, so goes to fallback
of noveum? driver. Went to NVIDIA site, and downloaded what I
believe was the correct driver for the GT 650M, but it also fails to
build? Currently 17 timezones away from machine. In GMT -0700,
while machine is in GMT +1000, so accessing remotely via
TurboVNC. So, not sure if this is a kernel issue, or the driver issue,
but seems neither rpmfusiong or nvidia's driver will work any
longer? I've got other machines that have new nvidia cards, and
they are working with a different rpmfusing nvidia rpm.
Perhaps I'm missing something. Thanks. Otherwise machines fully
updated with no issues.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
+------------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor (Retired)
mailto:mikes@guam.net
mailto:msetzerii@gmail.com
mailto:msetzerii@gmx.com
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+
10:22 a.m.
On 15 Apr 2024 at 0:29, Michael D. Setzer II via user wrote:
To: Community support for Fedora users
<users(a)lists.fedoraproject.org>
Date sent: Mon, 15 Apr 2024 00:29:38 +1000
Subject: Re: crippling nvidia display issue.
Priority: normal
Send reply to: mikes(a)guam.net, Community support for Fedora
users <users(a)lists.fedoraproject.org>
From: "Michael D. Setzer II via users"
<users(a)lists.fedoraproject.org>
Copies to: "Michael D. Setzer II" <mikes(a)guam.net>
On 14 Apr 2024 at 12:47, John Pilkington wrote:
Date sent: Sun, 14 Apr 2024 12:47:57 +0100
Subject: Re: crippling nvidia display issue.
From: John Pilkington <johnpilk222(a)gmail.com>
To: users(a)lists.fedoraproject.org
Send reply to: Community support for Fedora users
<users(a)lists.fedoraproject.org>
> On 12/04/2024 12:58, John Pilkington wrote:
> > On 12/04/2024 00:52, home user wrote:
> >> On 4/11/24 5:39 PM, Samuel Sieb wrote:
> >>> On 4/11/24 16:36, home user wrote:
> >>>> On 4/11/24 5:31 PM, Samuel Sieb wrote:
> >>>>> On 4/11/24 16:05, home user wrote:
> >>>>>>
/tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-drv.c:748:40:
error: 'DRM_UNLOCKED' undeclared here (not in a function); did you mean
'VM_LOCKED'?
> >>>>>
> >>>>> There has been a kernel change of some sort. The driver needs
to
> >>>>> be updated to match the kernel.
> >>>>>
> >>>>> You will not get this driver to build on any newer kernels.
> >>>>> --
> >>>>
> >>>> So realistically, my only practical choice is what Todd suggested,
> >>>> "to just switch to the stuff Nvidia provides directly"?
> >>>
> >>> Unless there's a hope of the rpmfusion package getting updated, it
> >>> looks like it. I'm not really familiar with akmods, but maybe you
> >>> could just update the source somehow.
> >>
> >> I'm not a systems administrator. I need someone to step me through
> >> the full switch in detail.
> >> Reminders:
> >> This is a dual boot (Fedora-38 and windows-7) stand-alone work
> >> station; it's 11 years old.
> >> I have only one old kernel, and no rescue kernel.
> >> The graphics card is an nvidia GeForce GTX 660.
> >> (anything else?)
> >
> > I have two systems affected by this, and have posted about it on the
> > rpmfusion and fedora-kde lists. I'm having trouble accessing the
> > rpmfusion archive, so maybe a comment here is in order.
> >
> > Both systems have GeForce GT 710 cards. This is low-spec, not for
> > gamers, and I've been using the rpmfusion 470xx drivers for years. I
> > upgraded from F38 to F39 around 2 weeks ago.
> >
> > AIUI we are moving from X11 graphics towards Wayland, which the nvidia
> > driver will not support; but nouveau might. So I've been trying it.
> >
> > On one box it's working acceptably, with VGA nad HDMI screens.
> > Single-boot F39.
> >
> > The other box is dual-boot with Windows 10. I can boot into Fedora only
> > with 'nomodeset', when I get a single screen HDMI 800x600 which seems
> > fine but limited. I can run MythTV frontend with --geometry
> > 720x504+40+20
> >
> > The biggest worry is getting past a frozen boot, so I don't want to make
> > any recommendations. I have removed all the *nvidia* rpms except
> > nvidia-gpu-firmware, and installed nouveau-firmware from the
> > rpmfusion-nonfree-tainted repo.
> >
> > Maybe the rpmfusion team will make the old system work soon, or maybe
> > the even-older but just-updated 340xx driver would work. I'll try
> > living with what I have for now.
>
> After kernel and firmware updates today the behaviour of both systems,
> using nouveau, seems essentially unchanged from the report above.
> kernel now is 6.8.5-201.fc39.x86-64
>
> If the 'nomodeset' is edited out in grub, a reboot of the dual-boot box
> still hangs almost immediately.
>
> I've removed the claim that mythleanfront works with mythbackend on the
> dual-boot box. I think that was mistaken, and a local permissions issue.
> >
> > HTH
> >
> > John P
> >
> >
> >
> --
Just as an additional note. I have an older Acer notebook that has
an NVIDIA GT 650M that had been working fine with the
rpmfusion driver. Have BOINC using its GPU for a project.
After recent kernel upgrade, I noticed it was no longer working.
Tried reinstalling the rpm and it fails to build, so goes to fallback
of noveum? driver. Went to NVIDIA site, and downloaded what I
believe was the correct driver for the GT 650M, but it also fails to
build? Currently 17 timezones away from machine. In GMT -0700,
while machine is in GMT +1000, so accessing remotely via
TurboVNC. So, not sure if this is a kernel issue, or the driver issue,
but seems neither rpmfusiong or nvidia's driver will work any
longer? I've got other machines that have new nvidia cards, and
they are working with a different rpmfusing nvidia rpm.
Perhaps I'm missing something. Thanks. Otherwise machines fully
updated with no issues.
Was looking around, and found this info in
/var/cache/akmods/nvidia-470xx
Appears that it was working with 6.7.11 kernel but is now failing
with 6.8.x
26183873 Apr 2 12:52
kmod-nvidia-470xx-6.7.11-200.fc39.x86_64-470.223.02-2.fc39.x86_
64.rpm
14360178 Apr 2 12:52
470.223.02-2-for-6.7.11-200.fc39.x86_64.log
614649 Apr 10 15:32
470.223.02-2-for-6.8.4-200.fc39.x86_64.failed.log
616385 Apr 15 01:02
470.223.02-2-for-6.8.5-201.fc39.x86_64.failed.log
Thanks.
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> 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@lists.fedoraproject.org
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
+------------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor (Retired)
mailto:mikes@guam.net
mailto:msetzerii@gmail.com
mailto:msetzerii@gmx.com
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+
--
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
+------------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor (Retired)
mailto:mikes@guam.net
mailto:msetzerii@gmail.com
mailto:msetzerii@gmx.com
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+
12:50 p.m.
On 14/04/2024 16:22, Michael D. Setzer II via users wrote:
On 15 Apr 2024 at 0:29, Michael D. Setzer II via user wrote:
>
> Just as an additional note. I have an older Acer notebook that has
> an NVIDIA GT 650M that had been working fine with the
> rpmfusion driver. Have BOINC using its GPU for a project.
> After recent kernel upgrade, I noticed it was no longer working.
> Tried reinstalling the rpm and it fails to build, so goes to fallback
> of noveum? driver. Went to NVIDIA site, and downloaded what I
> believe was the correct driver for the GT 650M, but it also fails to
> build? Currently 17 timezones away from machine. In GMT -0700,
> while machine is in GMT +1000, so accessing remotely via
> TurboVNC. So, not sure if this is a kernel issue, or the driver issue,
> but seems neither rpmfusiong or nvidia's driver will work any
> longer? I've got other machines that have new nvidia cards, and
> they are working with a different rpmfusing nvidia rpm.
>
> Perhaps I'm missing something. Thanks. Otherwise machines fully
> updated with no issues.
>
>
Was looking around, and found this info in
/var/cache/akmods/nvidia-470xx
Appears that it was working with 6.7.11 kernel but is now failing
with 6.8.x
26183873 Apr 2 12:52
kmod-nvidia-470xx-6.7.11-200.fc39.x86_64-470.223.02-2.fc39.x86_
64.rpm
14360178 Apr 2 12:52
470.223.02-2-for-6.7.11-200.fc39.x86_64.log
614649 Apr 10 15:32
470.223.02-2-for-6.8.4-200.fc39.x86_64.failed.log
616385 Apr 15 01:02
470.223.02-2-for-6.8.5-201.fc39.x86_64.failed.log
Thanks.
I've dropped the initial posts in this thread.. When I posted on the
rpmfusion list, on 9 April, Sergio's response was:
a fix for nvidia 340x was posted today ,
for Fedora 40 we don't have these kmod nvidias because it fail to build
with gcc14 .
Please someone which have these graphics try fix it ASAP
Thank you
So one difficulty is probably a lack of rpmfusion devs with the affected
hardware...
John P
7:21 p.m.
On 14 Apr 2024 at 18:50, John Pilkington wrote:
Date sent: Sun, 14 Apr 2024 18:50:40 +0100
Subject: Re: crippling nvidia display issue.
To: users(a)lists.fedoraproject.org
From: John Pilkington <johnpilk222(a)gmail.com>
Send reply to: Community support for Fedora users
<users(a)lists.fedoraproject.org>
On 14/04/2024 16:22, Michael D. Setzer II via users wrote:
> On 15 Apr 2024 at 0:29, Michael D. Setzer II via user wrote:
>>
>> Just as an additional note. I have an older Acer notebook that has
>> an NVIDIA GT 650M that had been working fine with the
>> rpmfusion driver. Have BOINC using its GPU for a project.
>> After recent kernel upgrade, I noticed it was no longer working.
>> Tried reinstalling the rpm and it fails to build, so goes to fallback
>> of noveum? driver. Went to NVIDIA site, and downloaded what I
>> believe was the correct driver for the GT 650M, but it also fails to
>> build? Currently 17 timezones away from machine. In GMT -0700,
>> while machine is in GMT +1000, so accessing remotely via
>> TurboVNC. So, not sure if this is a kernel issue, or the driver issue,
>> but seems neither rpmfusiong or nvidia's driver will work any
>> longer? I've got other machines that have new nvidia cards, and
>> they are working with a different rpmfusing nvidia rpm.
>>
>> Perhaps I'm missing something. Thanks. Otherwise machines fully
>> updated with no issues.
>>
>>
>
> Was looking around, and found this info in
> /var/cache/akmods/nvidia-470xx
>
> Appears that it was working with 6.7.11 kernel but is now failing
> with 6.8.x
>
> 26183873 Apr 2 12:52
> kmod-nvidia-470xx-6.7.11-200.fc39.x86_64-470.223.02-2.fc39.x86_
> 64.rpm
> 14360178 Apr 2 12:52
> 470.223.02-2-for-6.7.11-200.fc39.x86_64.log
> 614649 Apr 10 15:32
> 470.223.02-2-for-6.8.4-200.fc39.x86_64.failed.log
> 616385 Apr 15 01:02
> 470.223.02-2-for-6.8.5-201.fc39.x86_64.failed.log
>
> Thanks.
I've dropped the initial posts in this thread.. When I posted on the
rpmfusion list, on 9 April, Sergio's response was:
Just an update. Used grubby to set the default kernel to 6.7.11,
and ran akmods, so not BOINC sees the nvidia and is able to use
the GPU...
26183873 Apr 2 12:52
kmod-nvidia-470xx-6.7.11-200.fc39.x86_64-470.223.02-2.fc39.x86_
64.rpm
14360178 Apr 2 12:52
470.223.02-2-for-6.7.11-200.fc39.x86_64.log
614649 Apr 10 15:32
470.223.02-2-for-6.8.4-200.fc39.x86_64.failed.log
616385 Apr 15 01:02
470.223.02-2-for-6.8.5-201.fc39.x86_64.failed.log
Now Acer notebook is running 6.7.11 kernel that works with the
rpmfusing nvidia.
uname -a
Linux kevinacer.dyndns.org 6.7.11-200.fc39.x86_64 #1 SMP
PREEMPT_DYNAMIC Wed Mar 27 16:50:39 UTC 2024 x86_64
GNU/Linux
$ cat /tmp/BOINC-output | grep GPU
15-Apr-2024 08:54:02 [---] CUDA: NVIDIA GPU 0: NVIDIA GeForce
GT 650M (driver version 470.99, CUDA version 11.4, compute
capability 3.0, 2000MB, 2000MB available, 730 GFLOPS peak)
15-Apr-2024 08:54:02 [---] OpenCL: NVIDIA GPU 0: NVIDIA
GeForce GT 650M (driver version 470.223.02, device version
OpenCL 3.0 CUDA, 2000MB, 2000MB available, 730 GFLOPS
peak)
So, not sure why it works with 6.7.x but not with 6.8.x.
Have seen that Busybox also had an issue with some options no
longer working with 6.8.x kernels. Said the 6.8.x dropped some
things that cause the app to tail to build.
>
> a fix for nvidia 340x was posted today ,
> for Fedora 40 we don't have these kmod nvidias because it fail to build
> with gcc14 .
>
> Please someone which have these graphics try fix it ASAP
>
> Thank you
So one difficulty is probably a lack of rpmfusion devs with the affected
hardware...
John P
--
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
+------------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor (Retired)
mailto:mikes@guam.net
mailto:msetzerii@gmail.com
mailto:msetzerii@gmx.com
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+
12:18 a.m.
On 4/14/24 17:21, Michael D. Setzer II via users wrote:
So, not sure why it works with 6.7.x but not with 6.8.x.
Something changed in the kernel and the NVidia driver needs to be
changed to work with it. The driver is out of tree so it doesn't get
fixed by the people making the change like the in tree drivers would.
2:48 p.m.
On 4/11/24 12:09, Doug Herr wrote:
On Thu, Apr 11, 2024, at 10:19 AM, home user wrote:
> (f-38; stand-alone work station; nvidia graphics card; dual monitor;
> kmod 4xx driver)
>
> I just finished doing a "dnf upgrade" as a prerequisite step to
> upgrading from f-38 to f-39.
> There were no hints of any problems. The kernel and the graphics driver
> were replaced during this "dnf upgrade".
> The akmods did finish before I rebooted.
> The shutdown took 5 minutes because it ran akmods (a second time?!).
[snip]
The process running akmods might have finished, but you should not reboot unless it
actually created a module. I use a shell alias I call "kerncheck", which does
the below. You might want to see what this shows you:
ls -ltr /lib/modules/*/extra;echo;ls -ltr /lib/modules;echo;echo -n "Currently
booted to: ";uname -r;echo
If there is no module showing for the new kernel then it clearly can not load. You then
look at the error logs. I don't have Nvidia currently and can't remember where you
find those logs.
bash.14[~]:
bash.14[~]: ls -ltr /lib/modules/*/extra;echo;ls -ltr
/lib/modules;echo;echo -n "Currently booted to: ";uname -r;echo
/lib/modules/6.2.10-200.fc37.x86_64/extra:
total 4
drwxr-xr-x. 2 root root 4096 Apr 20 2023 nvidia-470xx
/lib/modules/6.2.12-200.fc37.x86_64/extra:
total 4
drwxr-xr-x. 2 root root 4096 Apr 27 2023 nvidia-470xx
/lib/modules/6.5.8-200.fc38.x86_64/extra:
total 4
drwxr-xr-x. 2 root root 4096 Nov 9 14:18 nvidia-470xx
/lib/modules/6.5.10-200.fc38.x86_64/extra:
total 4
drwxr-xr-x. 2 root root 4096 Nov 9 14:17 nvidia-470xx
/lib/modules/6.7.11-100.fc38.x86_64/extra:
total 4
drwxr-xr-x. 2 root root 4096 Apr 4 13:20 nvidia-470xx
total 196
[... snip ...]
drwxr-xr-x. 8 root root 4096 Nov 9 14:17 6.5.10-200.fc38.x86_64
drwxr-xr-x. 8 root root 4096 Nov 9 14:19 6.5.8-200.fc38.x86_64
drwxr-xr-x. 8 root root 4096 Apr 4 13:20 6.7.11-100.fc38.x86_64
drwxr-xr-x. 7 root root 4096 Apr 11 10:38 6.8.4-100.fc38.x86_64
Currently booted to: 6.8.4-100.fc38.x86_64
bash.15[~]:
5:20 p.m.
On 4/11/24 11:19 AM, home user wrote:
(f-38; stand-alone work station; nvidia graphics card; dual monitor;
kmod 4xx driver)
I just finished doing a "dnf upgrade" as a prerequisite step to upgrading from
f-38 to f-39.
There were no hints of any problems. The kernel and the graphics driver were replaced
during this "dnf upgrade".
The akmods did finish before I rebooted.
The shutdown took 5 minutes because it ran akmods (a second time?!).
During the boot-up, there was a message that it was failing back to nouveau.
The display is not working properly; only one monitor is being used and everything is
oversized in the display.
I am not comfortable proceeding with the f-38 to f-39 upgrade with the work station in
this condition.
Important: I have only one old kernel. I have no rescue kernel.
How do I get this workstation working properly?
--
I looked at the dnf logs. Something caught my attention. I put the file on the google
drive as "dnflog.txt". It does not show properly in google's preview, but
you should be able to download it and view it with vim. There are
"non-printing" characters; I don't know how to fix or remove those. Here is
the link:
"https://drive.google.com/file/d/1SqsMZcQQm2HhCL6_7ipoeONmTJRuC1hP/view?usp=sharing".
In that log file, comparing last week's patches with this morning's patches...
=====
(last week, April 04)
start at line 3 (dnf --refresh upgrade dnf)
lines 24-33... accessing rpmfusion.
end at line 104 (dnf --refresh upgrade dnf)
-----
start at line 105 (dnf upgrade)
lines 122-129...accessing rpmfusion.
lines 135-139...kernel 6.7.11 updates.
lines 266-270...kernel 6.7.9 erasings.
line 271...kmod-nvidia-470xx-6.7.9-100.fc38.x86_64.x86_64 3:470.223.02-2.fc38 will be
erased.
lines 279-283...installing kernel 6.7.11.
lines 349-353...removing kernel 6.7.9.
lines 354-355...removing dependent package kmod-nvidia-470xx-6.7.9-100.fc38.x86_64
3:470.223.02-2.fc38.
lines 445-449...installed kernel 6.7.11.
lines 450-454...removed kernel 6.7.9.
line 455...removed kmod-nvidia-470xx-6.7.9-100.fc38.x86_64-3:470.223.02-2.fc38.x86_64.
lines 540-569...installed kmod-nvidia-470xx-6.7.11-100.fc38.x86_64x86_64
3:470.223.02-2.fc38.
end at line 571 (dnf upgrade)
=====
(this morning, April 11)
start at line 572 (dnf --refresh upgrade dnf)
lines 593-603...accessing rpmfusion. notice "curl error" in line 603.
end at line 615 (dnf --refresh upgrade dnf)
-----
start at line 616 (dnf upgrade)
lines 633-640...accessing rpmfusion.
lines 646-650...kernel 6.8.4 updates.
lines 731-735...kernel 6.7.10 erasings.
line 736...kmod-nvidia-470xx-6.7.10-100.fc38.x86_64.x86_64 3:470.223.02-2.fc38 will be
erased.
lines 744-748...installing kernel 6.8.4.
lines 791-795...removing kernel 6.7.10.
lines 796-797...removing dependent package kmod-nvidia-470xx-6.7.10-100.fc38.x86_64
3:470.223.02-2.fc38.
lines 884-888...installed kernel 6.8.4.
lines 889-893...removed kernel 6.7.10.
line 894...removed kmod-nvidia-470xx-6.7.10-100.fc38.x86_64-3:470.223.02-2.fc38.x86_64
end at line 942 (dnf upgrade)
=====
This morning's run has the curl error.
This morning's run has nothing corresponding to last week's lines 540-569.
Beyond that, I'm stumped.
I hope this helps someone to help me.
2:02 p.m.
On 4/11/24 11:19 AM, home user wrote:
After a few days of being seriously side-tracked, I can try to get back to this.
Those who explained the kernel numbering: thank-you.
(f-38; stand-alone work station; nvidia graphics card; dual monitor;
kmod 4xx driver)
I just finished doing a "dnf upgrade" as a prerequisite step to upgrading from
f-38 to f-39.
There were no hints of any problems. The kernel and the graphics driver were replaced
during this "dnf upgrade".
The akmods did finish before I rebooted.
The shutdown took 5 minutes because it ran akmods (a second time?!).
During the boot-up, there was a message that it was failing back to nouveau.
The display is not working properly; only one monitor is being used and everything is
oversized in the display.
I am not comfortable proceeding with the f-38 to f-39 upgrade with the work station in
this condition.
Important: I have only one old kernel. I have no rescue kernel.
How do I get this workstation working properly?
A. nvidia's proprietary drivers.
There's....
1.
(Thomas)
I finally just nuked all the RPMFusion packages and downloaded the
drivers directly from https://www.nvidia.com/download/index.aspx and ran
the installer from there. It works fine again.
(Todd)
I can tell you that building the 2 or 3 nvidia 470xx packages
works well for the later 6.7 and current 6.8 kernels.
and there's....
2.
(John)
AIUI we are moving from X11 graphics towards Wayland, which the
nvidia driver will not support...
(Michael)
So, not sure if this is a kernel issue, or the driver issue,
but seems neither rpmfusiong or nvidia's driver will work any
longer?
These seem to me to be inconsistent with each other. What am I missing?
B. nvidia and Fedora.
From posts in this thread, I gather that
1. nvidia users can no longer use Fedora, and
2. Fedora users can no longer use nvidia.
Is this correct?
3:33 p.m.
On 4/15/24 14:02, home user wrote:
On 4/11/24 11:19 AM, home user wrote:
<snip>
There's....
1.
(Thomas)
> I finally just nuked all the RPMFusion packages and downloaded the
> drivers directly from https://www.nvidia.com/download/index.aspx and
> ran the installer from there. It works fine again.
(Todd)
> I can tell you that building the 2 or 3 nvidia 470xx packages
> works well for the later 6.7 and current 6.8 kernels.
and there's....
2.
(John)
> AIUI we are moving from X11 graphics towards Wayland, which the nvidia
> driver will not support...
(Michael)
> So, not sure if this is a kernel issue, or the driver issue, but seems
> neither rpmfusiong or nvidia's driver will work any longer?
These seem to me to be inconsistent with each other. What am I missing?
B. nvidia and Fedora.
From posts in this thread, I gather that
1. nvidia users can no longer use Fedora, and
That's not AT ALL what I said. I was able to use the NVidia drivers from
NVidia's web site just fine. Others mentioned they did the same.
2. Fedora users can no longer use nvidia.
Again, I didn't see ANYTHING that intimated that.
Is this correct?
Nope. I've been using Linux since 1995. NVidia drivers have ALWAYS been
problematic. RPMFusion has done amazing work trying to make it less
onerous, but often times NVidia makes changes that catch third parties
like RPMFusion unawares. I *feel* like this is just another case of
this. It stinks, but it's not the end of the world. Either wait til this
gets fixed by the volunteer developers at RPMFusion (and be cool to
them, most are working out of love for the community), or install the
NVidia drivers from NVidia web site. You'll be fine.
--
Thomas
3:54 p.m.
On 15/04/2024 20:02, home user wrote:
On 4/11/24 11:19 AM, home user wrote:
After a few days of being seriously side-tracked, I can try to get back
to this.
Those who explained the kernel numbering: thank-you.
> (f-38; stand-alone work station; nvidia graphics card; dual monitor;
> kmod 4xx driver)
>
> I just finished doing a "dnf upgrade" as a prerequisite step to
> upgrading from f-38 to f-39.
> There were no hints of any problems. The kernel and the graphics
> driver were replaced during this "dnf upgrade".
> The akmods did finish before I rebooted.
> The shutdown took 5 minutes because it ran akmods (a second time?!).
> During the boot-up, there was a message that it was failing back to
> nouveau.
> The display is not working properly; only one monitor is being used
> and everything is oversized in the display.
> I am not comfortable proceeding with the f-38 to f-39 upgrade with the
> work station in this condition.
>
> Important: I have only one old kernel. I have no rescue kernel.
>
> How do I get this workstation working properly?
A. nvidia's proprietary drivers.
There's....
1.
(Thomas)
> I finally just nuked all the RPMFusion packages and downloaded the
> drivers directly from https://www.nvidia.com/download/index.aspx and
> ran the installer from there. It works fine again.
(Todd)
> I can tell you that building the 2 or 3 nvidia 470xx packages
> works well for the later 6.7 and current 6.8 kernels.
and there's....
2.
(John)
> AIUI we are moving from X11 graphics towards Wayland, which the nvidia
> driver will not support...
(Michael)
> So, not sure if this is a kernel issue, or the driver issue, but seems
> neither rpmfusiong or nvidia's driver will work any longer?
These seem to me to be inconsistent with each other. What am I missing?
B. nvidia and Fedora.
From posts in this thread, I gather that
1. nvidia users can no longer use Fedora, and
2. Fedora users can no longer use nvidia.
Is this correct?
I don't think your summaries are correct. But although technical fixes
may exist for the immediate problems the situation at rpmfusion looks
more difficult. See this Bugzilla and in particular Comment 5.
https://bugzilla.rpmfusion.org/show_bug.cgi?id=6904
John P
9:13 p.m.
New subject: crippling nvidia display issue. [SOLVED]
On 4/11/24 11:19 AM, home user wrote:
(f-38; stand-alone work station; nvidia graphics card; dual monitor;
kmod 4xx driver)
I just finished doing a "dnf upgrade" as a prerequisite step to upgrading from
f-38 to f-39.
There were no hints of any problems. The kernel and the graphics driver were replaced
during this "dnf upgrade".
The akmods did finish before I rebooted.
The shutdown took 5 minutes because it ran akmods (a second time?!).
During the boot-up, there was a message that it was failing back to nouveau.
The display is not working properly; only one monitor is being used and everything is
oversized in the display.
I am not comfortable proceeding with the f-38 to f-39 upgrade with the work station in
this condition.
Important: I have only one old kernel. I have no rescue kernel.
How do I get this workstation working properly?
--
Thanks to the new RPM fusion nvidia-470xx driver,
and it being reported in this list on April 24,
and great off-line help,
this problem was solved this past weekend.
I was able to do the f-38 to f-39 upgrade today.
More likely than not, it was the smoothest full upgrade of the 22(?) I've done.
Thank-you to all who helped or tried to help.
3:23 a.m.
New subject: crippling nvidia display issue. [SOLVED]
What kernel are you using?
On Mon, Apr 29, 2024, 21:15 home user <mattisonw(a)comcast.net> wrote:
On 4/11/24 11:19 AM, home user wrote:
> (f-38; stand-alone work station; nvidia graphics card; dual monitor;
kmod 4xx driver)
>
> I just finished doing a "dnf upgrade" as a prerequisite step to
upgrading from f-38 to f-39.
> There were no hints of any problems. The kernel and the graphics driver
were replaced during this "dnf upgrade".
> The akmods did finish before I rebooted.
> The shutdown took 5 minutes because it ran akmods (a second time?!).
> During the boot-up, there was a message that it was failing back to
nouveau.
> The display is not working properly; only one monitor is being used and
everything is oversized in the display.
> I am not comfortable proceeding with the f-38 to f-39 upgrade with the
work station in this condition.
>
> Important: I have only one old kernel. I have no rescue kernel.
>
> How do I get this workstation working properly?
> --
Thanks to the new RPM fusion nvidia-470xx driver,
and it being reported in this list on April 24,
and great off-line help,
this problem was solved this past weekend.
I was able to do the f-38 to f-39 upgrade today.
More likely than not, it was the smoothest full upgrade of the 22(?) I've
done.
Thank-you to all who helped or tried to help.
--
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
11:11 a.m.
New subject: crippling nvidia display issue. [SOLVED]
On 4/30/24 2:23 AM, Javier Perez wrote:
What kernel are you using?
The bad patching ("dnf upgrade" early this month) was from 6.7.11-100.fc38x86_64
to 6.8.4-100.fc38x86_64.
The good patching Saturday was from 6.7.11-100.fc38x86_64 to 6.8.7-100.fc38x86_64.
The full upgrade ("dnf system-upgrade download --releasever=39" and "dnf
system-upgrade reboot, Saturday)
was from 6.8.7-100.fc38x86_64 to 6.8.7-200.fc39.x86_64.
Bill.
17
days inactive
36
days old
36 comments
13 participants
participants (13)
-
Barry Scott -
Doug Herr -
Felix Miata -
Go Canes -
home user -
Javier Perez -
Jeffrey Walton -
John Pilkington -
Michael D. Setzer II -
Samuel Sieb -
Thomas Cameron -
Todd Zullinger -
Tom Horsley