Solved NVIDIA Packages in Quarterly REPOs are un-fit for installation on FreeBSD 15.1 (Use Latest REPOs)

[drsnx60]

HI,

First of all can we assume the switch to 2026Q4 REPOs are now completed ?
This repo " pkg+https://pkg.freebsd.org/FreeBSD:15:amd64/quarterly" has not changed since monday 5/10.
I assume that means that the switch to 2026Q4 is completed.

To List all kmod's in Quarterly

Run : # pkg search -r FreeBSD-ports kmod

They are stamped with 1500068 for version 15.0 of FreeBSD

then look at repository "pkg+https://pkg.freebsd.org/FreeBSD:15:amd64/kmods_quarterly_1"

Run : # pkg search -r FreeBSD-ports-kmods kmod

They are stamped with 1501000 for version 15.1 of FreeBSD

QUESTION: Quarterly REPO still supports FreeBSD 15.0 is this a mistake ? as we passed the EOL date for 15.0 ?


NOW to the Point :

The NVIDIA set of packages are these , they need to be supplied for the same Freebsd version and the same Nvidia Version.

Nvidia-driver version 595.84 presumably for FreeBSD 15.0 availble in Quarterly REPO
Nvidia-kmod Version 595.104 for FreeBSD 15.1 available on kmods-quaterly_1 REPO
Nvidia-drm-612-kmod Version 595.104 for FreeBSD 15.1 available on kmods-quaterly_1 REPO

This is a Mix of Nvidia version and a mix of FreeBSD versions and is unusable , causes Kernel Panics, ABI mismatch aso.

The LATEST REPOS are consistent with the above three packages available in version 595.104 for Freebsd 15.1.
Switch to the LATEST REPOs as soon as you have installed FreeBSD 15.1 to avoid this issue.

 

[SirDice]

I assume that means that the switch to 2026Q4 is completed.

Quarterly built was started on Tue, 06 Oct 2026 01:03:43 GMT and took almost 88 hours to complete. It certainly wasn't "complete" the day before the built actually started.

https://pkg-status.freebsd.org/builds?jailname=151amd64

 

[mer]

Run : # pkg search -r FreeBSD-ports kmod

They are stamped with 1500068 for version 15.0 of FreeBSD

then look at repository "pkg+https://pkg.freebsd.org/FreeBSD:15:amd64/kmods_quarterly_1"

Run : # pkg search -r FreeBSD-ports-kmods kmod

They are stamped with 1501000 for version 15.1 of FreeBSD

I look at this differently.
Your commands are both looking at Quarterly, making your title a bit misleading.

The problem is your commands are looking at two different repos:
FreeBSD-ports
FreeBSD-ports-kmod

I would imagine at some point, the nvidia kmods that are actually in FreeBSD-ports will go away, so a generic "pkg search" with all repos enabled will probably return what is in FreeBSD-ports-kmods.
I think this shows what T-Aoki has been trying to explain with the nvidia kmod build being broken in freebsd-ports-kmod. I could be wrong, but the data seems to fit what has been said.

in fact, on my 15.1 system shows both versions,
pkg search kmod | grep -i nvidia
nvidia-drm-515-kmod-595.84.1500068_1 NVIDIA DRM Kernel Module
nvidia-drm-515-kmod-580-580.173.02.1500068_1 NVIDIA DRM Kernel Module
nvidia-drm-515-kmod-devel-610.43.02.1500068_1 NVIDIA DRM Kernel Module
nvidia-drm-61-kmod-595.84.1500068_1 NVIDIA DRM Kernel Module
nvidia-drm-61-kmod-580-580.173.02.1500068_1 NVIDIA DRM Kernel Module
nvidia-drm-61-kmod-devel-610.43.02.1500068_1 NVIDIA DRM Kernel Module
nvidia-drm-66-kmod-595.84.1500068_1 NVIDIA DRM Kernel Module
nvidia-drm-66-kmod-580-580.173.02.1500068_1 NVIDIA DRM Kernel Module
nvidia-drm-66-kmod-devel-610.43.02.1500068_1 NVIDIA DRM Kernel Module
nvidia-drm-kmod-595.84 NVIDIA DRM kernel module
nvidia-drm-kmod-580-580.173.02 NVIDIA DRM kernel module
nvidia-drm-kmod-devel-610.43.02 NVIDIA DRM kernel module
nvidia-kmod-595.84.1500068 NVIDIA graphics driver kernel module
nvidia-kmod-304-304.137.1500068 NVIDIA graphics driver kernel module
nvidia-kmod-340-340.108.1500068 NVIDIA graphics driver kernel module
nvidia-kmod-390-390.157.1500068 NVIDIA graphics driver kernel module
nvidia-kmod-470-470.256.02.1500068 NVIDIA graphics driver kernel module
nvidia-kmod-580-580.173.02.1500068 NVIDIA graphics driver kernel module
nvidia-kmod-devel-610.43.02.1500068 NVIDIA graphics driver kernel module
nvidia-drm-515-kmod-595.104.02.1501000 NVIDIA DRM Kernel Module
nvidia-drm-61-kmod-595.104.02.1501000 NVIDIA DRM Kernel Module
nvidia-drm-612-kmod-595.104.02.1501000 NVIDIA DRM Kernel Module
nvidia-drm-66-kmod-595.104.02.1501000 NVIDIA DRM Kernel Module
nvidia-drm-latest-kmod-595.104.02.1501000 NVIDIA DRM Kernel Module
nvidia-kmod-595.104.02.1501000 NVIDIA graphics driver kernel module

 

[drsnx60]

Quarterly built was started on Tue, 06 Oct 2026 01:03:43 GMT and took almost 88 hours to complete. It certainly wasn't "complete" the day before the built actually started.

https://pkg-status.freebsd.org/builds?jailname=151amd64

Its good that the build has finished. The Pkg Mirrors are still having a date stamp of Oct 05 on Quarterly .
So the New contents has not been replicated to the mirrors.
This probably explains the Issues we are seeing .

 

[drsnx60]

I look at this differently.
Your commands are both looking at Quarterly, making your title a bit misleading.

The problem is your commands are looking at two different repos:
FreeBSD-ports
FreeBSD-ports-kmod

I would imagine at some point, the nvidia kmods that are actually in FreeBSD-ports will go away, so a generic "pkg search" with all repos enabled will probably return what is in FreeBSD-ports-kmods.
I think this shows what T-Aoki has been trying to explain with the nvidia kmod build being broken in freebsd-ports-kmod. I could be wrong, but the data seems to fit what has been said.

in fact, on my 15.1 system shows both versions,
pkg search kmod | grep -i nvidia
nvidia-drm-515-kmod-595.84.1500068_1 NVIDIA DRM Kernel Module
nvidia-drm-515-kmod-580-580.173.02.1500068_1 NVIDIA DRM Kernel Module
nvidia-drm-515-kmod-devel-610.43.02.1500068_1 NVIDIA DRM Kernel Module
nvidia-drm-61-kmod-595.84.1500068_1 NVIDIA DRM Kernel Module
nvidia-drm-61-kmod-580-580.173.02.1500068_1 NVIDIA DRM Kernel Module
nvidia-drm-61-kmod-devel-610.43.02.1500068_1 NVIDIA DRM Kernel Module
nvidia-drm-66-kmod-595.84.1500068_1 NVIDIA DRM Kernel Module
nvidia-drm-66-kmod-580-580.173.02.1500068_1 NVIDIA DRM Kernel Module
nvidia-drm-66-kmod-devel-610.43.02.1500068_1 NVIDIA DRM Kernel Module
nvidia-drm-kmod-595.84 NVIDIA DRM kernel module
nvidia-drm-kmod-580-580.173.02 NVIDIA DRM kernel module
nvidia-drm-kmod-devel-610.43.02 NVIDIA DRM kernel module
nvidia-kmod-595.84.1500068 NVIDIA graphics driver kernel module
nvidia-kmod-304-304.137.1500068 NVIDIA graphics driver kernel module
nvidia-kmod-340-340.108.1500068 NVIDIA graphics driver kernel module
nvidia-kmod-390-390.157.1500068 NVIDIA graphics driver kernel module
nvidia-kmod-470-470.256.02.1500068 NVIDIA graphics driver kernel module
nvidia-kmod-580-580.173.02.1500068 NVIDIA graphics driver kernel module
nvidia-kmod-devel-610.43.02.1500068 NVIDIA graphics driver kernel module
nvidia-drm-515-kmod-595.104.02.1501000 NVIDIA DRM Kernel Module
nvidia-drm-61-kmod-595.104.02.1501000 NVIDIA DRM Kernel Module
nvidia-drm-612-kmod-595.104.02.1501000 NVIDIA DRM Kernel Module
nvidia-drm-66-kmod-595.104.02.1501000 NVIDIA DRM Kernel Module
nvidia-drm-latest-kmod-595.104.02.1501000 NVIDIA DRM Kernel Module
nvidia-kmod-595.104.02.1501000 NVIDIA graphics driver kernel module

A number of peoples had installation issues this week because the situation listed in your reply above.
there are 1501000 KMODS , but there is no nvidia-driver for 595.104.
As the New Quarterly build finished last night. The situation may be resolved on Monday when the
PKG mirrors has been synced.

 

[drsnx60]

Finally the Quarterly 2026Q4 REPO has been pushed to the Mirrors .
lets hope the installation issues will diminish in numbers now.

 

[SirDice]

You can turn off the FreeBSD-ports-kmods repository too, it's really only useful during the three month transition period when both X.Y and X.Y+1 need to be supported. All packages in the FreeBSD-ports (for 15) are now built for 15.1, including all the kmod packages.

 

[drhowarddrfine]

SirDice By "turn off" do you mean remove that part in FreeBSD.conf?

 

[mer]

SirDice By "turn off" do you mean remove that part in FreeBSD.conf?

I'm not trying to speak for him, but I think there is a field for each repo that says "enabled" or "disabled", so flipping the state should be sufficient.

 

[drhowarddrfine]

I'm having an issue where I stared at an update for a kms wanting to upgrade. I did it and am now regretting it. At least I think that's why I'm having an issue with chromium (at least) and maybe my mouse now hanging.

 

[T-Aoki]

I'm not trying to speak for him, but I think there is a field for each repo that says "enabled" or "disabled", so flipping the state should be sufficient.

Or force repository with pkg upgrade -r FreeBSD-ports (add -n for dry-run).

 

[T-Aoki]

and maybe my mouse now hanging

It may be a different issue.

Does your keyboard (if it's connected via USB, not PS/2) hang, too?
I'm having issue that ALL USB-attached devices suddenly stop working when

1. playing sound (music by audacious, video by vlc and/or smplayer, YouTuve on firefox, ...) via uaudio
2. firefox is running
3. USB mouse (actually a trackball, though) cursor is moving

Currently doesn't happen if any of the above is NOT applicable.
Confirming device tree, all USB devices are recognized under xhci1 for me.

And as the affected computer (currently Minisforum MS-01) doesn't have any PS/2 port nor serial port, this mean what can be done LOCALLY is just forcibully power-cycle. But fortunately, everything others are fine.

This means, if I configure the affected PC to enable SSH access, I can SSH into it from another computer (fortunately, I still have ThinkPad P52).

And devctl reset xhci1 via SSH helps in my case (usually take minutes, 20sec at best and 20minutes at worst, currently).

 

[drhowarddrfine]

T-Aoki I'm not clear of the timeline. I upgraded the kms driver a couple of days ago (thinking I should have investigated first) and also Chromium before and after that. Chromium works for a while, then freezes. The PS/2 mouse, through an adapter, used to stop working, too, to the point where I thought it was broken and I switched to a wireless mouse but that stopped working, too. Switched back to the PS/2 mouse and it is working fine now but I can't click on anything in chromium.

Like you, Firefox works fine.

 

[drhowarddrfine]

T-Aoki One more note: eventually chromium can be restarted from the command line (I'm on i3wm) as I just now did but it takes some amount of time such as maybe five or ten minutes.

 

[drhowarddrfine]

Now I have two chrome pids running that I can't kill. Both are at 100%

 

[drsnx60]

You can turn off the FreeBSD-ports-kmods repository too, it's really only useful during the three month transition period when both X.Y and X.Y+1 need to be supported. All packages in the FreeBSD-ports (for 15) are now built for 15.1, including all the kmod packages.

Last week we had the following situation:

Quarterly Repo Had Nvidia-driver + Nvidia Kmod for 15.0 ( eg 1500068 ) version 595.84
Kmod quarterly_1 had Nvidia Kmod for 15.1 version 595.104.

Nvidia-driver 595.104 and Nvidia-Kmod 595.104 for 15.1 was only available in Latest REPO.

Now: the Newbie comes along who wants to try out FreeBSD for the first time. system is default configured for Quarterly REPO.
He will soon give up as he is missing the knowledge to navigate the REPOS and which files to edit to get there.

Whith upcomming 15.2, the System must be pre-configured so that a Desktop will be installable without intimate system knowledge.