Due to a late change to the DRM KBI, the 14.2-RELEASE versions of the Nvidia-drm-kmod modules do not load on 14.3-RELEASE -- they error out with "link_elf_obj: symbol linux_kfree_async undefined" when loaded. No 14.3-RELEASE versions have appeared in the FreeBSD-kmods repository, thus breaking Wayland compositors. It's been broken for 2+ months now. Please build and post 14.3-RELEASE builds of the Nvidia-drm-kmod packages to the FreeBSD-kmods repository so Wayland and other nvidia-drm consumers will run again on 14.3-RELEASE.
(In reply to Doug White from comment #0) Can't you upgrade it with below? # pkg upgrade -r FreeBSD-kmods Now kmod ports are provided per-minor-version basis and definition of the repo is defined in /etc/pkg/FreeBSD.conf (in default case for *-Release, points to quarterly, while others like main [aka -Current] and stable/* points to latest). You can see the source of the file with links below. For quarterly: https://cgit.freebsd.org/src/tree/usr.sbin/pkg/FreeBSD.conf.quarterly?h=releng/14.3 For latest: https://cgit.freebsd.org/src/tree/usr.sbin/pkg/FreeBSD.conf.latest?h=releng/14.3
(In reply to Tomoaki AOKI from comment #1) nvidia-drm-kmod doesn't seem to be part of the FreeBSD-kmods repo or perhaps it doesn't get built for some other reason? but nevertheless nvidia-drm-61-kmod and nvidia-drm-515-kmod for 14.3 release doesn't seem to be provided by pkg, only nvidia-drm-515-kmod-570.169.1402000_3 and nvidia-drm-61-kmod-570.169.1402000_2, no such thing as nvidia-drm-61-kmod-570.169.1403000_2 or nvidia-drm-515-kmod-570.169.1402000_3 and yes this is what pkg says on a 14.3 RELEASE system not 14.2
(In reply to polyduekes from comment #2) I'm not using FreeBSD-kmods repo, but building from ports locally, so not sure whether the build is ongoing (not yet finished) or somehow crashed. Another thing to mention would be that your computer is actually on 14.3 or not if your computer is upgraded from 14.2 to 14.3. If the upgrade is in somehow inconsistent state, pkg missingly recognized it as 14.2. Anyway, building from ports locally would help, if your 14.3 installation is in consistent state and you have src tree which is consistent with your running kernel. If your installation is consistent, 3 versions shown by `freebsd-version -kru` should show exactly same version string. The 1st line shows the version of installed kernel, the 2nd line shows the version of running kernel, and the 3rd line shows the version of the userland. If the 2nd line alone shows older version, you should try restarting your computer. If the 1st and 3rd line differs except "-p?" part, your installation is in inconsistent state. ("-p?" can be mismatched even if actually sane, because patch releases provided by freebsd-update are sometimes kernel only or userland only, which confuses users.)
(In reply to Tomoaki AOKI from comment #3) my installation of 14.3 is consistent since pkg install drm-61-kmod installs the 140300 version, and the freebsd-kmods repo is in the pkg conf file and freebsd-version -kru shows 14.3-RELEASE 14.3-RELEASE 14.3-RELEASE-p1 so i am pretty sure there is some sort of problem happening with nvidia-drm-kmod regarding 14.3 pkg build if you don't believe me then i assume it's super easy for you to check yourself
(In reply to polyduekes from comment #4) I'm not administrating the repo (no authority for it), so do not know what's going on. And I'm not yourself, so I don't know what the your computer's state is, unless sufficient info is provided by you. I didn't know your 14.3 is sane until you provided the output of `freebsd-version -kru`. Unrelated with "believe or not", simply "unknown to me". The kmod repo is started providing at 14.2, quite new service, so there could be some rough edges. So if there's some trouble on the repo and you're in hurry, building yourself using ports would be the way to go, as it was the only way for anyone using kmod ports on any releases other than oldest-supported-release of the same major version. And FYI: I've filed Bug 288300 which updates x11/nvidia-driver and friends to latest Production Branch of driver 570.172.08 yesterday. But it would not land to quarterly (currently 2025Q3), as it does not contain security fix. Corresponding review D51407 is accepted by one of the reviewers and waiting to be committed.
(In reply to Tomoaki AOKI from comment #5) sorry if i offended you, that's wasn't what i was trying to say, what i was trying to say is that in case it still seems as if it is an user error, you can check with pkg yourself, about ports, i don't think every end user prefers or has the experince for compiling a driver from src, we wouldn't have pkg if that was the case, and yes i know that freebsd-kmods repo is new, i was just chiming in here as someone who also experience the same as that of the OP's experience
(In reply to polyduekes from comment #6) I don't think you're offending me, and as x11/nvidia-driver, x11/linux-nvidia-libs, graphics/nvidia-drm-61-kmod and graphics/nvidia-drm-kmod at 570.169 built and ran fine on my stable/14 environment both on poudriere and bare-metal (using ports-mgmt/pkg_replace and plain make). So as 575.64.03 (-devel variant) and upcoming 570.172.08. So I thought there could be possibilities. 1. kmod repo is somehow failing or delaying builds 2. your environment is somehow in insane state For 1., as I'm on stable/14, trying fetching pkg for 14.3 could be hazardous if I missingly installed instead of fetching (human make mistakes!). So it's not my option. So I wanted to know 2. first, as I didn't know about it until you replied on Comment 4. I'm not offending you, too. I've once tried to browse the kmod repo, but the same as regular repo, listing acutal directories with web browsers was rejected.
There are no nvidia-drm-*-kmod packages in pkg.FreeBSD.org/${ABI}/kmods_latest_3 that I have found. I assume some manual action is required for packages to be published there as the standard port build environment is 14.2 at the moment. On the other hand, drm-61-kmod is in FreeBSD-kmods, so whoever maintains that port knows who to talk to ;) # pkg search drm-61 drm-61-kmod-6.1.128.1402000_5 DRM drivers modules nvidia-drm-61-kmod-570.169.1402000_2 NVIDIA DRM Kernel Module nvidia-drm-61-kmod-devel-575.64.03.1402000_2 NVIDIA DRM Kernel Module drm-61-kmod-6.1.128.1403000_5 DRM drivers modules I'm not at home to check the machine in question, it was freebsd-update'd from 14.2 to 14.3 and AFAIK that was successful. I ran into some weird problem trying to build the nvidia-drm-kmod port last time. I'll try that again to get graphics going in the short term, but that's not the long term solution I reported this bug to address.
(In reply to Doug White from comment #8) In my experience, a clean install of # pkg ins nvidia-drm-kmod at the moment (using 'latest' on 14.3-RELEASE) installs the correct 14.3 versions; one should have: # pkg query -x '[%R] %n %v' 'drm(-|-.*-)kmod' | column -t [FreeBSD-kmods] drm-61-kmod 6.1.128.1403000_5 [FreeBSD] nvidia-drm-61-kmod 570.172.08.1402000_2 [FreeBSD] nvidia-drm-kmod 570.172.08 Note: a clean install meaning that there weren't ANY packages allready installed that the command # pkg ins nvidia-drm-kmod installs. However, it could be that there are some packages allready installed wrt to this particular pkg-install command; for example from a transition from 14.2-RELEASE to 14.3-RELEASE. Then, as mentioned in comment #1, using pkg upgrade -r FreeBSD-kmods, should work. The following command sequence shows this: [0-0] # date -u; pkg -v; freebsd-version -kru Sun Jul 27 08:31:42 UTC 2025 2.2.1 14.3-RELEASE 14.3-RELEASE 14.3-RELEASE-p1 [1-0] # pkg query -x '[%R] %n %v' 'drm(-|-.*-)kmod' | column -t [FreeBSD] drm-61-kmod 6.1.128.1402000_5 [FreeBSD] nvidia-drm-61-kmod 570.172.08.1402000_2 [FreeBSD] nvidia-drm-kmod 570.172.08 [2-0] # pkg upgrade -r FreeBSD-kmods Updating FreeBSD-kmods repository catalogue... FreeBSD-kmods repository is up to date. FreeBSD-kmods is up to date. Checking for upgrades (7 candidates): 100% Processing candidates (7 candidates): 100% The following 7 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: drm-61-kmod: 6.1.128.1402000_5 -> 6.1.128.1403000_5 [FreeBSD-kmods] gpu-firmware-amd-kmod-green-sardine: 20230625.1402000_2 -> 20230625.1403000_2 [FreeBSD-kmods] gpu-firmware-amd-kmod-yellow-carp: 20230625.1402000_2 -> 20230625.1403000_2 [FreeBSD-kmods] gpu-firmware-intel-kmod-kabylake: 20230625.1402000 -> 20230625.1403000 [FreeBSD-kmods] gpu-firmware-radeon-kmod-tahiti: 20220511.1402000 -> 20220511.1403000 [FreeBSD-kmods] gpu-firmware-radeon-kmod-verde: 20220511.1402000 -> 20220511.1403000 [FreeBSD-kmods] wifi-firmware-iwlwifi-kmod-22000: 20241017.1402000_2 -> 20241017.1403000_2 [FreeBSD-kmods] Number of packages to be upgraded: 7 3 MiB to be downloaded. Proceed with this action? [y/N]: y [1/6] Fetching wifi-firmware-iwlwifi-kmod-22000-20241017.1403000_2.pkg: 100% 779 KiB 798.0kB/s 00:01 [2/6] Fetching gpu-firmware-amd-kmod-green-sardine-20230625.1403000_2.pkg: 100% 463 KiB 473.6kB/s 00:01 [3/6] Fetching gpu-firmware-radeon-kmod-tahiti-20220511.1403000.pkg: 100% 254 KiB 260.4kB/s 00:01 [4/6] Fetching gpu-firmware-intel-kmod-kabylake-20230625.1403000.pkg: 100% 298 KiB 304.9kB/s 00:01 [5/6] Fetching gpu-firmware-amd-kmod-yellow-carp-20230625.1403000_2.pkg: 100% 723 KiB 740.5kB/s 00:01 [6/6] Fetching gpu-firmware-radeon-kmod-verde-20220511.1403000.pkg: 100% 86 KiB 88.5kB/s 00:01 Checking integrity... done (0 conflicting) [1/7] Upgrading drm-61-kmod from 6.1.128.1402000_5 to 6.1.128.1403000_5... [1/7] Extracting drm-61-kmod-6.1.128.1403000_5: 100% [2/7] Upgrading gpu-firmware-amd-kmod-green-sardine from 20230625.1402000_2 to 20230625.1403000_2... [2/7] Extracting gpu-firmware-amd-kmod-green-sardine-20230625.1403000_2: 100% [3/7] Upgrading gpu-firmware-amd-kmod-yellow-carp from 20230625.1402000_2 to 20230625.1403000_2... [3/7] Extracting gpu-firmware-amd-kmod-yellow-carp-20230625.1403000_2: 100% [4/7] Upgrading gpu-firmware-intel-kmod-kabylake from 20230625.1402000 to 20230625.1403000... [4/7] Extracting gpu-firmware-intel-kmod-kabylake-20230625.1403000: 100% [5/7] Upgrading gpu-firmware-radeon-kmod-tahiti from 20220511.1402000 to 20220511.1403000... [5/7] Extracting gpu-firmware-radeon-kmod-tahiti-20220511.1403000: 100% [6/7] Upgrading gpu-firmware-radeon-kmod-verde from 20220511.1402000 to 20220511.1403000... [6/7] Extracting gpu-firmware-radeon-kmod-verde-20220511.1403000: 100% [7/7] Upgrading wifi-firmware-iwlwifi-kmod-22000 from 20241017.1402000_2 to 20241017.1403000_2... [7/7] Extracting wifi-firmware-iwlwifi-kmod-22000-20241017.1403000_2: 100% [3-0] # pkg query -x '[%R] %n %v' 'drm(-|-.*-)kmod' | column -t [FreeBSD-kmods] drm-61-kmod 6.1.128.1403000_5 [FreeBSD] nvidia-drm-61-kmod 570.172.08.1402000_2 [FreeBSD] nvidia-drm-kmod 570.172.08 [4-0] # Currently, pkg(8), pkg-upgrade(8) and pkg-version(8) are unable to work with multiple repositories in all cases (for example bug #283755 and bug #285197). In my experience, using both - FreeBSD - FreeBSD-kmods as a pratical work-around, a two-step upgrade process works: # pkg upgrade -r FreeBSD # pkg upgrade -r FreeBSD-kmods
(In reply to Eric from comment #9) Cannot find nvidia-related pkg for 14.3 in your procedure (log). I'm now asking if some work is needed or not with mentioning this PR. https://lists.freebsd.org/archives/freebsd-ports/2025-July/008178.html I'm working on splitting kmod parts of x11/nvidia-driver* into corresponding brand-new x11/nvidia-kmod* and switching dependency of x11/nvidia-driver[-devel] to corresponding x11/nvidia-kmod* in graphics/nvidia-drm-*-kmod[-devel]. But as it introduces additional complexities on maintaining, which could affect mistakes on updating, I don't want it to be landed unless it is really, really mandatory. So waiting for reply.
(In reply to Tomoaki AOKI from comment #10) You're right, the pkg query should have been: [10-0] % pkg query -x '[%R] %n %v' 'drm.*-kmod$|nvidia' | column -t [FreeBSD-kmods] drm-61-kmod 6.1.128.1403000_5 [FreeBSD] nvidia-driver 570.172.08.1402000 [FreeBSD] nvidia-drm-61-kmod 570.172.08.1402000_2 [FreeBSD] nvidia-drm-kmod 570.172.08 [11-0] % QUOTE_BEGIN But as it introduces additional complexities on maintaining, which could affect mistakes on updating, I don't want it to be landed unless it is really, really mandatory. So waiting for reply. QUOTE_END I quite agree. However, is there any indication that the proprietary Nvidia part(s), IIRC: the blob, is in need of a FreeBSD minor-version specific (i.e. kernel specific) build? AFAIK, the Nvidia drivers do not use the Linux KPI shim layer and are therefore not likely to be (much less) 'kernel-sensitive' over various minor versions of the same major version (~ FreeBSD major branche).
(In reply to Eric from comment #11) STRIKE AFAIK, the Nvidia drivers do not use the Linux KPI shim layer and are therefore not likely to be (much less) 'kernel-sensitive' over various minor versions of the same major version (~ FreeBSD major branche). /STRIKE Should have been: AFAIK, the Nvidia drivers do not use the Linux KPI shim layer and are therefore not likely to be 'kernel-sensitive'* over various minor versions of the same major version (~ FreeBSD major branche). * at least: much less 'kernel sensitive' compared to the drm-510|515|61-kmod versions that do rely on the Linux KPI shim layer.
(In reply to Eric from comment #12) Yes, x11/nvidia-driver* doen't use LinuxKPI at all, and AFAIK, blob parts of the drivers are not sensitive with kernel versions (shared within all supported versions including main branch of src). I'm not a nvidia insider, but my understanding (and my experiences indicate) is that all kernel-version-dependent codes are provided as source codes in upstream driver tarballs. OTOH, graphics/nvidia-drm-*-kmod[-devel] is linked with codes from corresponding graphics/drm-*-kmod and requires LinuxKPI, thus, quite fragile on kernel updates just as graphics/drm-*-kmod do. This is unavoidable.
(In reply to Tomoaki AOKI from comment #10) drm-kmod - is a meta package; it is not in FreeBSD-kmods drm-515|61-kmod - are packages without any dependecies; they are in the FreeBSD-kmods, in addition to FreeBSD graphics/nvidia-drm-kmod - is a meta package graphics/nvidia-drm-515-kmod - has a dependency graphics/nvidia-drm-61-kmod - has a dependency CFT: repository for kernel modules https://lists.freebsd.org/archives/freebsd-ports/2024-December/006997.html mentions: Because of the way we are building and because we want to be able to ship quickly updates on those kernel modules, there are other limitation which have been added: Only kernel modules without any build and run dependencies are being built, which means most of them but not all. END_QUOTE If that still holds, then, I imagine, it is not likely that any Nvidia driver will end up in the FreeBSD-kmods repository. Returning to the initial and mentioned problems as to the graphics drivers using pkg(8): (1) getting the right graphics drivers, especially those matched to a specific kernel, wrt the stable/14 branch, the releng/14.2|3 branch; (2) given having installed the appropriate drivers and running problems. ad (1) Given the inability of pkg and companions to work with multiple repositories in all cases and using the two-step upgrade procedure wrt the FreeBSD and the FreeBSD-kmods repository (not ideal); is there any particular need to have any Nvidia driver in the FreeBSD-kmods repository? ad (2) This probably resolves to my earlier question: is there any need to have Nvidia drivers, containing proprietary Nvidia code ('blob' code) build specifically to - stable/14 - releng/14.2 - releng/14.3
(In reply to Eric from comment #14) So if even kmod-to-kmod dependencies is NOT allowed, we have no way to fix this, except still-not-finished x11/nvidia-kmod*, which are splitted-out kmod only part of x11/nvidia-driver*. graphics/nvidia-drm-*-kmod mutually depends on kmod part of x11/nvidia-driver[-devel] and corresponding graphics/drm-*-kmod. It cannot run without modules provided by them, and building and installing the exact same kmods on this is quite silly mess. So RUN_DEPENDS to 2 kmod ports (if x11/nvidia-kmod is splitted from x11/nvidia-driver) should be considered mandatory and should be allowed. So, if the limitations are mutually as such and cannot modify, this PR should be closed with "WONTFIX". OTOH, x11/nvidia-driver is fixable, with additional mess on updates.
Created attachment 262521 [details] WIP patch for splitting out kmod part of x11/nvidia-driver* Disclosing WIP patch to offer what we can do, under testing by myself. This patch *splits out *.ko from x11/nvidia-driver[-304|-340|-390|470|-devel] into corresponding x11/nvidia-kmod[-304|-340|-390|470|-devel], *switch dependency of graphics/nvidia-drm-*-kmod upon x11/nvidia-driver[-devel] to upon newly introduced x11/nvidia-kmod[-devel], *make x11/nvidia-driver[-304|-340|-390|470|-devel] depend upon newly introduced x11/nvidia-kmod[-304|-340|-390|470|-devel], *and hook x11/nvidia-kmod[-304|-340|-390|470|-devel] to build. Currently, tested build and package for x11/nvidia-driver x11/nvidia-driver-devel x11/nvidia-kmod x11/nvidia-kmod-devel graphics/nvidia-drm-61-kmod graphics/nvidia-drm-61-kmod-devel and additionally installing and running -devel variants on stable/14, amd64 at commit 823b81ac9c75f4c86b8e85e12bf1f0219ae59608. Note that x11/nvidia-driver* needs to be deinstalled before start. And known and (as per requirements) unfixable regression would be graphics/nvidia-drm-*-kmod no longer pulls in x11/nvidia-driver[-devel], that become non-kmod only part, thus, don't work without explicitly installing x11/nvidia-driver[-devel]. kmod part should be pulled in. Possible workaround would be making metaport graphics/nvidia-drm-kmod[-devel] to depend on corresponding x11/nvidia-driver[-devel]. UPDATING and pkg-message[.in] are not yet touched, as this is currently unknown to be accepted by admins of kmod builder. If this approach is acceptable for admins of kmod builder, I'll open review for this, with UPDATING and (if accepted) workarounds in metaport. (Need tests, though).
(In reply to Tomoaki AOKI from comment #16) If this approach is not acceptable, please close this with "WONTFIX", as this is the only possible (as far as I can think of currently) thing to offer. *Moving files/, Makefile.common and Makefile.version from x11/nvidia-driver into x11/nvidia-kmod is acceptable for me, if admins of kmod builder really need to do so. In the case, I'll file another PR without touching graphics/nvidia-drm-*-kmod. This way, I think x11/nvidia-kmod* alone is acceptable for admins of builder, as it does not have *_DEPENDS line. Would be better than nothing.
Created attachment 262997 [details] Updated patch to split kmod parts from x11/nvidia-driver* Tested further and turned out that previous WIP patch doesn't work for legacy versions. Updated patch to support all in-tree variants. I think this version would be ready to be reviewed once this approach is accepted by bapt@ and/or any other admins of kmod builders.
Created attachment 262998 [details] Candidate for UPDATING part of the patch. Uploaded separately. Even if the contents are fine, date needs to be updated with actual commit date.
Created attachment 263079 [details] Updated patch to split kmod parts from x11/nvidia-driver* (Chase 580.76.05) Update patch to chase upgrade of x11/nvidia-driver[-devel], x11/linux-nviia-libs[-devel] and graphics/nvidia-drm*-kmod[-devel] ports to 580.76.05. Note that currently Production Branch has superior version than NFB upstream, -devel branches on ports are also bumped to 580.76.05 with regard to the updating policy noted at commit ports c7cde11f842b33bb36b85b91400bec795430c421.
Created attachment 263124 [details] Patch to split kmod parts from x11/nvidia-driver* for 2025Q3 As the state of ports tree are different between main and 2025Q3 and patch for main does not apply to 2025Q3, created patch for 2025Q3 (except UPDATING part). This is based on the latest version for main and modified to be applicable to 2025Q3.
(In reply to Tomoaki AOKI from comment #7) > … directories with web browsers was rejected. That's bug 247998 (not a bug). I added a link to a workaround.
Created attachment 263266 [details] Update patch for latest to fix non-root build of x11/nvidia-kmod* ports. Fix non-root builds (typically on poudriere) of x11/nvidia-kmod* by adding uidfix to USES line.
Created attachment 263267 [details] Update patch to fix non-root build of x11/nvidia-kmod* ports. (2025Q3) Fix non-root builds (typically on poudriere) of x11/nvidia-kmod* by adding uidfix to USES line.
Opened review D52178 for this.
Created attachment 263443 [details] Updated patch for main (aka latest): Rebase for 580.82.07. Updated patch for main (aka latest) branch of ports tree to chase upgrades to 580.82.07 driver sets. No other changes intended (except missing PORTREVISION bump for graphics/nvidia-drm-kmod). Patch for 2025Q3 is untouched, as 580.82.07 wouldn't land on 2025Q3.
Created attachment 264110 [details] Updated patch for main (aka latest): Rebase after commit ports 971606f3493fbbc77c156ab84243ab952d89a81b. Rebased patch for main (aka latest) branch of ports tree to chase upgrades to fix Bug 289647 (commit ports 971606f3493fbbc77c156ab84243ab952d89a81b). Now includes UPDATING part. No other changes intended.
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=f4e907a492584bc31f9f3aa100a98a4e918dc7f4 commit f4e907a492584bc31f9f3aa100a98a4e918dc7f4 Author: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> AuthorDate: 2025-10-01 06:04:33 +0000 Commit: Kevin Bowling <kbowling@FreeBSD.org> CommitDate: 2025-10-01 06:07:31 +0000 x11/nvidia-driver: Split kmod into x11/nvidia-kmod Split out kmod part of x11/nvidia-driver into x11/nvidia-kmod, including slave ports, to allow FreeBSD-kmods repo builders building nvidia-related kmod ports. In this update, * split out *.ko from x11/nvidia-driver[-304|-340|-390|470|-devel] into corresponding x11/nvidia-kmod[-304|-340|-390|470|-devel], * switch dependency of graphics/nvidia-drm-*-kmod upon x11/nvidia-driver[-devel] to newly introduced x11/nvidia-kmod[-devel], * make x11/nvidia-driver[-304|-340|-390|470|-devel] depend upon newly introduced x11/nvidia-kmod[-304|-340|-390|470|-devel], * bump consumers directly depending upon x11/nvidia-driver* as of dependency switches, * and hook x11/nvidia-kmod[-304|-340|-390|470|-devel] to build. Note that upgrading x11/nvidia-driver* from monolithic version requires deinstallation of x11/nvidia-driver* before starting, as both previous version of x11/nvidia-driver* and newly introduced x11/nvidia-kmod* installs *.ko into same place. PR: 288314 Approved by: bapt (kmod repo) Differential Revision: https://reviews.freebsd.org/D52178 UPDATING | 10 ++ graphics/nvidia-drm-510-kmod-devel/Makefile | 2 +- graphics/nvidia-drm-510-kmod/Makefile | 2 +- graphics/nvidia-drm-515-kmod-devel/Makefile | 2 +- graphics/nvidia-drm-515-kmod/Makefile | 2 +- graphics/nvidia-drm-61-kmod-devel/Makefile | 2 +- graphics/nvidia-drm-61-kmod/Makefile | 2 +- graphics/nvidia-drm-66-kmod-devel/Makefile | 2 +- graphics/nvidia-drm-66-kmod/Makefile | 2 +- graphics/nvidia-drm-kmod-devel/Makefile | 2 +- graphics/nvidia-drm-kmod/Makefile | 3 + graphics/nvidia-drm-kmod/Makefile.common | 2 +- x11/Makefile | 6 + x11/nvidia-driver-304/Makefile | 2 +- x11/nvidia-driver-340/Makefile | 2 +- x11/nvidia-driver-390/Makefile | 2 +- x11/nvidia-driver-470/Makefile | 2 +- x11/nvidia-driver-devel/Makefile | 2 +- x11/nvidia-driver/Makefile | 177 ++------------------ x11/nvidia-driver/pkg-plist | 4 - x11/nvidia-kmod-304/Makefile (new) | 8 + x11/nvidia-kmod-340/Makefile (new) | 8 + x11/nvidia-kmod-390/Makefile (new) | 8 + x11/nvidia-kmod-470/Makefile (new) | 8 + x11/nvidia-kmod-devel/Makefile (new) | 8 + x11/nvidia-kmod/Makefile (new) | 243 ++++++++++++++++++++++++++++ x11/nvidia-kmod/pkg-descr (new) | 3 + x11/nvidia-kmod/pkg-plist (new) | 4 + 28 files changed, 336 insertions(+), 184 deletions(-)