| View previous topic :: View next topic |
| Author |
Message |
sleepingsun
Guru
Joined: 03 May 2006
Posts: 477
Location: Bosnia
|
 Posted: Sun Mar 02, 2025 2:12 pm Post subject: GeForce GT 730 problem with kernel 6.12 |
 |
|
Hi all kernel include 6.6.x this graphic card works after i compile new stable 6.12 kernel (gentoo-sources) i cant up graphic card and kde-meta gui also emerge drivers failed
last driver for this card is
| Code: | These are the packages that would be merged, in order:
Calculating dependencies... done!
Dependency resolution took 9.31 s (backtrack: 0/20).
[ebuild R ] x11-drivers/nvidia-drivers-470.256.02-r2:0/470::gentoo USE="X modules static-libs strip tools -dist-kernel -modules-compress -modules-sign -persistenced" ABI_X86="(64) -32" 0 KiB
Total: 1 package (1 reinstall), Size of downloads: 0 KiB
Would you like to merge these packages? [Yes/No] |
| Code: | | 18:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 730] (rev a1) |
Any chance for this card or its droped by gentoo ?
_________________
Gentoo is Rocks |
|
| Back to top |
|
 |
molletts
Tux's lil' helper
Joined: 16 Feb 2013
Posts: 133
|
| Posted: Sun Mar 02, 2025 5:16 pm Post subject: |
|
|
Hi,
It looks like the 470.x drivers were officially supported by Nvidia for kernels up to 6.6. Beyond that, you're on your own as far as they're concerned.
There appears to be an unofficial patch for kernel 6.12 which has been created by a user; you can get it from https://aur.archlinux.org/packages/nvidia-470xx-dkms along with the 6.10 patch which you'll also need. You may need some or all of the other patches too. If you stick them in /etc/portage/patches/x11-drivers/nvidia-drivers-470.256.02, they should be applied automatically when you emerge the drivers. Hopefully, you won't need to add any further patches for the lifetime of the 6.12 LTS kernel.
I use the equivalent 390.x patches to keep my GTX460 going, although I track the unstable kernel so I sometimes have to hold off updating to the latest until a new patch becomes available.
[edit - premature publication! got distracted then didn't finish typing...] |
|
| Back to top |
|
|
Josef.95
Advocate
Joined: 03 Sep 2007
Posts: 4702
Location: Germany
|
| Posted: Sun Mar 02, 2025 7:09 pm Post subject: Re: GeForce GT 730 problem with kernel 6.12 |
|
|
| sleepingsun wrote: |
[...]
Any chance for this card or its droped by gentoo ? |
The 470 driver is end of live by upstream,
not dropped by gentoo.
With this (hard masked) driver version, you should stay on stable 6.6 LTS Kernel.
| Code: | grep KERNEL_MAX x11-drivers/nvidia-drivers/nvidia-drivers-470.256.02-r2.ebuild
MODULES_KERNEL_MAX=6.6 |
|
|
| Back to top |
|
|
sleepingsun
Guru
Joined: 03 May 2006
Posts: 477
Location: Bosnia
|
| Posted: Mon Mar 03, 2025 9:24 am Post subject: |
|
|
| molletts wrote: | Hi,
It looks like the 470.x drivers were officially supported by Nvidia for kernels up to 6.6. Beyond that, you're on your own as far as they're concerned.
There appears to be an unofficial patch for kernel 6.12 which has been created by a user; you can get it from https://aur.archlinux.org/packages/nvidia-470xx-dkms along with the 6.10 patch which you'll also need. You may need some or all of the other patches too. If you stick them in /etc/portage/patches/x11-drivers/nvidia-drivers-470.256.02, they should be applied automatically when you emerge the drivers. Hopefully, you won't need to add any further patches for the lifetime of the 6.12 LTS kernel.
I use the equivalent 390.x patches to keep my GTX460 going, although I track the unstable kernel so I sometimes have to hold off updating to the latest until a new patch becomes available.
[edit - premature publication! got distracted then didn't finish typing...] |
Can you explain me as i have /etc/portage/patches/ folder i made x11-drivers and nvidia-drivers-470.256.02 manual folder and download from git there but nothing happen still can not emerge driver
_________________
Gentoo is Rocks |
|
| Back to top |
|
|
Ralphred
l33t
Joined: 31 Dec 2013
Posts: 742
|
| Posted: Mon Mar 03, 2025 4:06 pm Post subject: |
|
|
There are two things you need to do: - Expose the patches to the ebuild
- Update the ebuild so it doesn't limit you to "MODULES_KERNEL_MAX=6.6"
So copy kernel-6.10.patch to the patch directory you created (/etc/portage/patches/x11-drivers/nvidia-drivers-470.256.02/) as 0001-kernel-6.10.patch and copy kernel-6.12.patch as 0002-kernel-6.12.patch.
Next copy the gentoo ebuild and it's files to your local overlay | Code: | mkdir -p /var/db/repos/local/x11-drivers/nvidia-drivers/files
cp /var/db/repos/gentoo/x11-drivers/nvidia-drivers/nvidia-drivers-470.256.02-r2.ebuild /var/db/repos/local/x11-drivers/nvidia-drivers/nvidia-drivers-470.256.02-r3.ebuild <<note the revision increment
cp /var/db/repos/gentoo/x11-drivers/nvidia-drivers/files/* /var/db/repos/local/x11-drivers/nvidia-drivers/files/ |
Update the new local ebuild so it will allow compilation against your 6.12 kernel, with an editor, or just | Code: | | sed -i 's/MODULES_KERNEL_MAX=6.6/MODULES_KERNEL_MAX=6.12/' /var/db/repos/local/x11-drivers/nvidia-drivers/nvidia-drivers-470.256.02-r3.ebuild |
Then use the ebuild command to "digest" it | Code: | | ebuild /var/db/repos/local/x11-drivers/nvidia-drivers/nvidia-drivers-470.256.02-r3.ebuild digest |
If you have not used a local overlay before you'll need: | /etc/portage/repos.conf/local.conf: | [local]
location = /var/db/repos/local
priority = 10
masters = gentoo |
| /var/db/repos/local/metadata/layout.conf: | | masters = gentoo |
| /var/db/repos/local/profiles/repo_name: | | local |
Now if you emerge nvidia-drivers portage should want to install x11-drivers/nvidia-drivers-470.256.02-r3::local instead of x11-drivers/nvidia-drivers-470.256.02-r2::gentoo
I have no intention of teaching grandma to suck eggs with this post, I just thought it best to be thorough. |
|
| Back to top |
|
|
molletts
Tux's lil' helper
Joined: 16 Feb 2013
Posts: 133
|
| Posted: Mon Mar 03, 2025 7:08 pm Post subject: |
|
|
| Ralphred wrote: | There are two things you need to do: - Expose the patches to the ebuild
- Update the ebuild so it doesn't limit you to "MODULES_KERNEL_MAX=6.6"
|
It shouldn't be necessary to update the ebuild - I've never had to edit the 390 ebuild to change MODULES_KERNEL_MAX. It will simply warn you at emerge time that you're on your own if your kernel is higher than this value. |
|
| Back to top |
|
|
sleepingsun
Guru
Joined: 03 May 2006
Posts: 477
Location: Bosnia
|
| Posted: Mon Mar 03, 2025 7:43 pm Post subject: |
|
|
i do as you say and get this error
| Code: | [ebuild R ] x11-drivers/nvidia-drivers-470.256.02-r3:0/470::local USE="X modules static-libs strip tools -dist-kernel -modules-compress -modules-sign -persistenced" ABI_X86="(64) -32" 0 KiB
Total: 1 package (1 reinstall), Size of downloads: 0 KiB
Would you like to merge these packages? [Yes/No] yes
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) x11-drivers/nvidia-drivers-470.256.02-r3::local
* NVIDIA-Linux-x86_64-470.256.02.run BLAKE2B SHA512 size ;-) ... [ ok ]
* nvidia-installer-470.256.02.tar.bz2 BLAKE2B SHA512 size ;-) ... [ ok ]
* nvidia-modprobe-470.256.02.tar.bz2 BLAKE2B SHA512 size ;-) ... [ ok ]
* nvidia-persistenced-470.256.02.tar.bz2 BLAKE2B SHA512 size ;-) ... [ ok ]
* nvidia-settings-470.256.02.tar.bz2 BLAKE2B SHA512 size ;-) ... [ ok ]
* nvidia-xconfig-470.256.02.tar.bz2 BLAKE2B SHA512 size ;-) ... [ ok ]
* Determining the location of the kernel source code
* Found kernel source directory:
* /usr/src/linux
* Found sources for kernel version:
* 6.12.16-gentoo
* Checking for suitable kernel configuration options ... [ ok ]
* Preparing x86_64-pc-linux-gnu toolchain for kernel modules (override with KERNEL_CHOST) ...
* Toolchain picked for kernel modules (override with KERNEL_CC, _LD, ...): '/usr/bin/x86_64-pc-linux-gnu-gcc-14' '/usr/bin/x86_64-pc-linux-gnu-g++-14' '/usr/bin/x86_64-pc-linux-gnu-ld.bfd' '/usr/bin/x86_64-pc-linux-gnu-gcc-ar' '/usr/bin/x86_64-pc-linux-gnu-gcc-nm' '/usr/bin/x86_64-pc-linux-gnu-objcopy' '/usr/bin/x86_64-pc-linux-gnu-objdump' '/usr/bin/x86_64-pc-linux-gnu-readelf' '/usr/bin/x86_64-pc-linux-gnu-strip'
>>> Unpacking source...
>>> Unpacking NVIDIA-Linux-x86_64-470.256.02.run to /var/tmp/portage/x11-drivers/nvidia-drivers-470.256.02-r3/work
>>> Unpacking nvidia-installer-470.256.02.tar.bz2 to /var/tmp/portage/x11-drivers/nvidia-drivers-470.256.02-r3/work
>>> Unpacking nvidia-modprobe-470.256.02.tar.bz2 to /var/tmp/portage/x11-drivers/nvidia-drivers-470.256.02-r3/work
>>> Unpacking nvidia-persistenced-470.256.02.tar.bz2 to /var/tmp/portage/x11-drivers/nvidia-drivers-470.256.02-r3/work
>>> Unpacking nvidia-settings-470.256.02.tar.bz2 to /var/tmp/portage/x11-drivers/nvidia-drivers-470.256.02-r3/work
>>> Unpacking nvidia-xconfig-470.256.02.tar.bz2 to /var/tmp/portage/x11-drivers/nvidia-drivers-470.256.02-r3/work
>>> Source unpacked in /var/tmp/portage/x11-drivers/nvidia-drivers-470.256.02-r3/work
>>> Preparing source in /var/tmp/portage/x11-drivers/nvidia-drivers-470.256.02-r3/work ...
* Applying nvidia-drivers-470.141.03-clang15.patch ... [ ok ]
* Applying nvidia-modprobe-390.141-uvm-perms.patch ... [ ok ]
* Applying nvidia-settings-390.144-desktop.patch ... [ ok ]
* Applying nvidia-settings-390.144-no-gtk2.patch ... [ ok ]
* Applying nvidia-settings-390.144-raw-ldflags.patch ... [ ok ]
* =================================================================================================
* Applying user patches from /etc/portage/patches ...
* Applying 0001-kernel-6.10.patch ...
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -ruNb a/kernel/conftest.sh b/kernel/conftest.sh
|--- a/conftest.sh 2024-07-19 04:36:26.183701185 -0500
|+++ b/conftest.sh 2024-07-19 04:36:26.230366381 -0500
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 37
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -ruNb a/kernel/nvidia/nvidia.Kbuild b/kernel/nvidia/nvidia.Kbuild
|--- a/nvidia/nvidia.Kbuild 2022-10-12 04:29:57.000000000 -0500
|+++ b/nvidia/nvidia.Kbuild 2024-07-19 05:17:39.148448922 -0500
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 49
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -ruNb a/kernel/nvidia/os-mlock.c b/kernel/nvidia/os-mlock.c
|--- a/nvidia/os-mlock.c 2022-10-12 04:30:26.000000000 -0500
|+++ b/nvidia/os-mlock.c 2024-07-19 04:36:26.230366381 -0500
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored [ !! ]
* ERROR: x11-drivers/nvidia-drivers-470.256.02-r3::local failed (prepare phase):
* patch -p1 failed with /etc/portage/patches/x11-drivers/nvidia-drivers-470.256.02/0001-kernel-6.10.patch
*
* Call stack:
* ebuild.sh, line 136: Called src_prepare
* environment, line 3993: Called default
* phase-functions.sh, line 874: Called default_src_prepare
* phase-functions.sh, line 950: Called __eapi8_src_prepare
* environment, line 362: Called eapply_user
* environment, line 1834: Called eapply '/etc/portage/patches/x11-drivers/nvidia-drivers-470.256.02/0001-kernel-6.10.patch'
* environment, line 1794: Called _eapply_patch '/etc/portage/patches/x11-drivers/nvidia-drivers-470.256.02/0001-kernel-6.10.patch'
* environment, line 1732: Called __helpers_die 'patch -p1 failed with /etc/portage/patches/x11-drivers/nvidia-drivers-470.256.02/0001-kernel-6.10.patch'
* isolated-functions.sh, line 112: Called die
* The specific snippet of code:
* die "$@"
*
* If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-470.256.02-r3::local'`,
* the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-470.256.02-r3::local'`.
* The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-470.256.02-r3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-470.256.02-r3/temp/environment'.
* Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-470.256.02-r3/work'
* S: '/var/tmp/portage/x11-drivers/nvidia-drivers-470.256.02-r3/work'
>>> Failed to emerge x11-drivers/nvidia-drivers-470.256.02-r3, Log file:
>>> '/var/tmp/portage/x11-drivers/nvidia-drivers-470.256.02-r3/temp/build.log'
* Messages for package x11-drivers/nvidia-drivers-470.256.02-r3:
* ERROR: x11-drivers/nvidia-drivers-470.256.02-r3::local failed (prepare phase):
* patch -p1 failed with /etc/portage/patches/x11-drivers/nvidia-drivers-470.256.02/0001-kernel-6.10.patch
*
* Call stack:
* ebuild.sh, line 136: Called src_prepare
* environment, line 3993: Called default
* phase-functions.sh, line 874: Called default_src_prepare
* phase-functions.sh, line 950: Called __eapi8_src_prepare
* environment, line 362: Called eapply_user
* environment, line 1834: Called eapply '/etc/portage/patches/x11-drivers/nvidia-drivers-470.256.02/0001-kernel-6.10.patch'
* environment, line 1794: Called _eapply_patch '/etc/portage/patches/x11-drivers/nvidia-drivers-470.256.02/0001-kernel-6.10.patch'
* environment, line 1732: Called __helpers_die 'patch -p1 failed with /etc/portage/patches/x11-drivers/nvidia-drivers-470.256.02/0001-kernel-6.10.patch'
* isolated-functions.sh, line 112: Called die
* The specific snippet of code:
* die "$@"
*
* If you need support, post the output of `emerge --info '=x11-drivers/nvidia-drivers-470.256.02-r3::local'`,
* the complete build log and the output of `emerge -pqv '=x11-drivers/nvidia-drivers-470.256.02-r3::local'`.
* The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-470.256.02-r3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-470.256.02-r3/temp/environment'.
* Working directory: '/var/tmp/portage/x11-drivers/nvidia-drivers-470.256.02-r3/work'
* S: '/var/tmp/portage/x11-drivers/nvidia-drivers-470.256.02-r3/work' |
_________________
Gentoo is Rocks |
|
| Back to top |
|
|
Ionen
Developer
Joined: 06 Dec 2018
Posts: 2902
|
| Posted: Tue Mar 04, 2025 2:29 am Post subject: |
|
|
Note that the long-term-support kernel 6.6.x branch will still be supported until December 2026 and getting new releases (6.12 also drops support in 2026 unless it is extended).
And with old hardware you probably no major need for 6.12, I'd suggest just saving yourself headaches and keep using 6.6 (and ideally replace hardware before 2027 if not planning to use nouveau and if don't want to be on your own with this). |
|
| Back to top |
|
|
Ralphred
l33t
Joined: 31 Dec 2013
Posts: 742
|
| Posted: Tue Mar 04, 2025 5:23 am Post subject: |
|
|
| sleepingsun wrote: | | i do as you say and get this error |
I can't fix the patches, I don't have a kernel that will allow the ebuild to prepare.
You are best following Ionen's advice until someone fixes/packages them. |
|
| Back to top |
|
|
sleepingsun
Guru
Joined: 03 May 2006
Posts: 477
Location: Bosnia
|
| Posted: Tue Mar 04, 2025 12:35 pm Post subject: |
|
|
Ok is it safe to back on last gentoo-sources 6.6.x stable i have before ?
And is it same process as upgrade and how to set grub to load 6.6 or install kernel will be do automatic ?
I never before do it downgrade
Thank you
_________________
Gentoo is Rocks |
|
| Back to top |
|
|
|
Kernel & Hardware
