#nvidia dropped a bunch of old GPUs support in new Beta Branch of driver 590.44.01.
It wouldn't hit #FreeBSD #ports tree as it's Beta, but I've posted HEADSUP for future upgrades at freebsd-ports ML.
https://lists.freebsd.org/archives/freebsd-ports/2025-December/008804.html
#nvidia dropped a bunch of old GPUs support in new Beta Branch of driver 590.44.01.
It wouldn't hit #FreeBSD #ports tree as it's Beta, but I've posted HEADSUP for future upgrades at freebsd-ports ML.
https://lists.freebsd.org/archives/freebsd-ports/2025-December/008804.html
⁂ Article
Introducing FLAVORS for OpenJDK on FreeBSD
A quick writeup of my thoughts around packaging OpenJDK for FreeBSD after adding FLAVORS to the OpenJDK 25 port:
Traditionally it's been possible to build OpenJDK for FreeBSD either as the full Java Development Kit (JDK), or as the slimmed down Jave Runtime Environment (JRE) via the FreeBSD ports system. This has been acheived by having two different ports, where the -jre port has been just a meta port that configures the main OpenJDK port for building the...
— https://kodeknekkeriet.net/en/blog/introducing-flavors-in-openjdk-freebsd/
I'd really like som input from the community on this, as I'm not entirely sure about what would be the best way to deal with this.
Thanks to the FreeBSD Foundation for sponsoring this project!
# FreeBSD # OpenJDK # ports # packaging
⁂ Article
Introducing FLAVORS for OpenJDK on FreeBSD
A quick writeup of my thoughts around packaging OpenJDK for FreeBSD after adding FLAVORS to the OpenJDK 25 port:
Traditionally it's been possible to build OpenJDK for FreeBSD either as the full Java Development Kit (JDK), or as the slimmed down Jave Runtime Environment (JRE) via the FreeBSD ports system. This has been acheived by having two different ports, where the -jre port has been just a meta port that configures the main OpenJDK port for building the...
— https://kodeknekkeriet.net/en/blog/introducing-flavors-in-openjdk-freebsd/
I'd really like som input from the community on this, as I'm not entirely sure about what would be the best way to deal with this.
Thanks to the FreeBSD Foundation for sponsoring this project!
# FreeBSD # OpenJDK # ports # packaging
My #FreeBSD #ports builder is testing a new version of LavinMQ, an AMQP-compliant message broker.
To build it we have a comical chain of history and languages:
- needs crystal which …
- needs ruby
- needs python
- needs rust
- needs perl
- needs docbook
- needs expat and libxml
- needs cmake
- needs lua53 and lua54
- needs autoconf and automake
- needs gmake and libtool
- needs git
- needs pkgconf
- needs meson
- needs ninja
- needs m4
- needs curl
- needs llvm14 and llvm20
- needs yaml
I started off with a nice formatted tree but it soon devolved into a complex graph of inter-twined dependencies... it's a wonder we can build software at all, when so many of these requirements can change at any time.
Version 580.105.08 of #nvidia GPU driver sets landed on main (aka latest) branch of #FreeBSD #ports tree.
https://cgit.freebsd.org/ports/commit/?id=2208426e57834d9a78c63632f2112091e9168665
Version 580.105.08 of #nvidia GPU driver sets landed on main (aka latest) branch of #FreeBSD #ports tree.
https://cgit.freebsd.org/ports/commit/?id=2208426e57834d9a78c63632f2112091e9168665
Found #nvidia GPU driver set for #FreeBSD 580.105.08 is released upstream.
https://www.nvidia.com/en-us/drivers/details/257494/
Working fine for me on my Quadro P1000 (notebook), stable/15 at commit fe38c6769b19.
So filed PR Bug 290813
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290813
and corresponding review D53596
https://reviews.freebsd.org/D53596
for upgrading #ports.
Found #nvidia GPU driver set for #FreeBSD 580.105.08 is released upstream.
https://www.nvidia.com/en-us/drivers/details/257494/
Working fine for me on my Quadro P1000 (notebook), stable/15 at commit fe38c6769b19.
So filed PR Bug 290813
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290813
and corresponding review D53596
https://reviews.freebsd.org/D53596
for upgrading #ports.
U.S. shipbuilders and port operators are facing the fallout of U.S. President Donald Trump’s campaign to wipe out the offshore wind industry, suffering lost government support, vanishing orders and an uncertain future. https://www.japantimes.co.jp/business/2025/10/23/markets/us-shipbuilders-ports-trump-wind/?utm_medium=Social&utm_source=mastodon #business #markets #ports #ships #shipping #wind #renewables #us #donaldtrump #trade #tariffs #republicans
As I've overlooked the existence of #FreeBSD #ports graphics/drm-latest-kmod (now at 6.9) until yesterday, there were no corresponding #nvidia ones.
Now I've filed Bug290262
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290262
and opened corresponding review D53128
https://reviews.freebsd.org/D53128
to add graphics/nvidia-drm-latest-kmod and graphics/nvidia-drm-latest-kmod-devel.
Now the review is accepted and waiting for land.
As I've overlooked the existence of #FreeBSD #ports graphics/drm-latest-kmod (now at 6.9) until yesterday, there were no corresponding #nvidia ones.
Now I've filed Bug290262
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290262
and opened corresponding review D53128
https://reviews.freebsd.org/D53128
to add graphics/nvidia-drm-latest-kmod and graphics/nvidia-drm-latest-kmod-devel.
Now the review is accepted and waiting for land.
Update for #nvidia #GPU #driver #ports on #FreeBSD to 580.95.05 landed as commit 7b1c88f42c7f4129bc96f405549f9e6b07bd6e3d.
https://cgit.freebsd.org/ports/commit/?id=7b1c88f42c7f4129bc96f405549f9e6b07bd6e3d
We were pending it as kmod pkg repo still didn't have nvidia things and bapt was looking into it, but as of this information
https://nvidia.custhelp.com/app/answers/detail/a_id/5703
the commit was done without waiting for the reply from bapt.
#FreeBSD is not entitled there, but as #FreeBSD native #drivers are known to shares most source codes with corresponding Linux versions, FreeBSD can be affected, too. So users of non-legacy versions of driver ports are strongly encouraged to upgrade.
With this reason, the commit is already merged into 2025Q4, as security fix is one of the branket approval by portmgr and secteam.
https://cgit.freebsd.org/ports/commit/?h=2025Q4&id=067be176997589baacd63c5e5db1981d3949cdb1
Note that oldest branch listed is 535.
Update for #nvidia #GPU #driver #ports on #FreeBSD to 580.95.05 landed as commit 7b1c88f42c7f4129bc96f405549f9e6b07bd6e3d.
https://cgit.freebsd.org/ports/commit/?id=7b1c88f42c7f4129bc96f405549f9e6b07bd6e3d
We were pending it as kmod pkg repo still didn't have nvidia things and bapt was looking into it, but as of this information
https://nvidia.custhelp.com/app/answers/detail/a_id/5703
the commit was done without waiting for the reply from bapt.
#FreeBSD is not entitled there, but as #FreeBSD native #drivers are known to shares most source codes with corresponding Linux versions, FreeBSD can be affected, too. So users of non-legacy versions of driver ports are strongly encouraged to upgrade.
With this reason, the commit is already merged into 2025Q4, as security fix is one of the branket approval by portmgr and secteam.
https://cgit.freebsd.org/ports/commit/?h=2025Q4&id=067be176997589baacd63c5e5db1981d3949cdb1
Note that oldest branch listed is 535.
Beware! Christos committed 9b26d309123abf0e90651298b131783ba7d9b945 on main branch of #FreeBSD #ports tree to ignore FreeBSD15 on audio/virtual_oss port and posted heads-up.
https://cgit.freebsd.org/ports/commit/?id=9b26d309123abf0e90651298b131783ba7d9b945
https://lists.freebsd.org/archives/freebsd-stable/2025-September/003305.html
And correlated virtual_oss codes are NOT YET MFC'ed into stable/15.
https://lists.freebsd.org/archives/freebsd-stable/2025-September/003306.html
Christos states he would MFC in 1 or 2 days,
https://lists.freebsd.org/archives/freebsd-stable/2025-September/003307.html
but it means if you upgrade ports including and after the above-mentioned commit on stable/15 including any of ALPHA snapshots before the MFCs are done, you'll lose virtual_oss functionalities.
So hold upgrades of ports/pkgs or `pkg lock audio/virtual_oss` would be wanted in the meantime.
Beware! Christos committed 9b26d309123abf0e90651298b131783ba7d9b945 on main branch of #FreeBSD #ports tree to ignore FreeBSD15 on audio/virtual_oss port and posted heads-up.
https://cgit.freebsd.org/ports/commit/?id=9b26d309123abf0e90651298b131783ba7d9b945
https://lists.freebsd.org/archives/freebsd-stable/2025-September/003305.html
And correlated virtual_oss codes are NOT YET MFC'ed into stable/15.
https://lists.freebsd.org/archives/freebsd-stable/2025-September/003306.html
Christos states he would MFC in 1 or 2 days,
https://lists.freebsd.org/archives/freebsd-stable/2025-September/003307.html
but it means if you upgrade ports including and after the above-mentioned commit on stable/15 including any of ALPHA snapshots before the MFCs are done, you'll lose virtual_oss functionalities.
So hold upgrades of ports/pkgs or `pkg lock audio/virtual_oss` would be wanted in the meantime.
I'm sooo proud of my first contribution to the #FreeBSD #Ports tree. Although it were only 3 characters. Although I don't understand what @dvl is apologizing for -- "I'm sorry, I did not mention this PR in the commit message."
The only things I needed was an account at bugs.freebsd.org and this short chapter from the Porters Handbook. Wish I had time for getting more involved.
https://docs.freebsd.org/en/books/porters-handbook/upgrading/#git-diff
I'm sooo proud of my first contribution to the #FreeBSD #Ports tree. Although it were only 3 characters. Although I don't understand what @dvl is apologizing for -- "I'm sorry, I did not mention this PR in the commit message."
The only things I needed was an account at bugs.freebsd.org and this short chapter from the Porters Handbook. Wish I had time for getting more involved.
https://docs.freebsd.org/en/books/porters-handbook/upgrading/#git-diff
For anyone struggling #X11 stopped working on #FreeBSD after upgrading main branch of #ports tree to commit 316774b85e4fc8858989a98da1a36075b6cbc8d2 and later with nvidia GPUs, reverting following commits and rebuild graphics/drm-[61|66]-kmod whichever you're using and corresponding graphics/nvidia-drm-[61|66]-kmod[-devel] you're using and reboot would help.
https://cgit.freebsd.org/ports/commit/?id=316774b85e4fc8858989a98da1a36075b6cbc8d2
https://cgit.freebsd.org/ports/commit/?id=09f1e5c29432d77a992f5f554f48986ef8674e9c
https://cgit.freebsd.org/ports/commit/?id=803213ed04ad14ea91a65cd48e6e8d6d610e3b98
https://cgit.freebsd.org/ports/commit/?id=ac934345a14f64a3e6f09bbde56f0dcacc8b3066
This issue is tracked at #FreeBSD Bugzilla.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289647
For anyone struggling #X11 stopped working on #FreeBSD after upgrading main branch of #ports tree to commit 316774b85e4fc8858989a98da1a36075b6cbc8d2 and later with nvidia GPUs, reverting following commits and rebuild graphics/drm-[61|66]-kmod whichever you're using and corresponding graphics/nvidia-drm-[61|66]-kmod[-devel] you're using and reboot would help.
https://cgit.freebsd.org/ports/commit/?id=316774b85e4fc8858989a98da1a36075b6cbc8d2
https://cgit.freebsd.org/ports/commit/?id=09f1e5c29432d77a992f5f554f48986ef8674e9c
https://cgit.freebsd.org/ports/commit/?id=803213ed04ad14ea91a65cd48e6e8d6d610e3b98
https://cgit.freebsd.org/ports/commit/?id=ac934345a14f64a3e6f09bbde56f0dcacc8b3066
This issue is tracked at #FreeBSD Bugzilla.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289647