[Bug 280772] x11/nvidia-driver: Update to 550.107.02 with x11/linux-nvidia-libs and related DRM ports

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280772

--- Comment #5 from Chad Jacob Milios <milios@ccsys.com> ---
(In reply to Tomoaki AOKI from comment #4)

i tried patch #252707 as is first. it works well in so much as it is a drop in
replacement upgrade for the 550.54.14 i had. it runs glxgears and foobillard
under kde5 plasma after logging in with lightdm. i tested it for all of 25
seconds. LGTM

> Yes. You must specify which DISTVERSION to be wanted.

then i edited Makefile.version to 560.31.02 and ran make -C
/usr/ports/{x11/{nvidia-driver;linux-nvidia-libs};graphics/nvidia-drm-510-kmod}
{makesum;package;{de;re}install} then reboot and everything also works
beautifully fine immediately. i've been running for a couple days now on
560.31.02 flawlessly.

by flawlessly i mean my windowing system is dependable. i've been
underutilizing my 4090 for a couple of days like its 2012 integrated graphics
while i'm trying out this driver because i dont even know how i would go about
telling this thing to break a sweat under FreeBSD. the fans have comfortably
stayed literally off the whole time on my GPU when in FreeBSD no matter how
many glxgears windows i open and nvidia-smi says its using like 27 watts out of
480.

i must confess my 4090 typically hangs out sadly in pptdevs under the cruel
heel of Linux. i had used the drivers in ports before just to configure and
test out the capability but FreeBSD usually shows my host console through the
cpu/mobo graphics while some bhyve vm takes over the 4090.

i dont "game" so i dont even own a modern commercial game that i could load up
on wine-proton or something. i'm all ears if anyone has any ideas what i can
play with just to test out the card and drivers natively on FreeBSD. believe me
i will be right there to make sure the fans kick on right away too. it seems
that while there is no driver talking to the card yet it idles at a minimum fan
speed but when the driver gets ahold of it and sees that i dont have any real
work for it they go off off.

i am experimenting with emulators/libc6-shim and nvidia-smi does report CUDA
12.6 support using your new modded patch while it reported 12.4 in both current
ports and with the attached patch unmodded. (all using an rl9 compat)

the mere mention of CUDA where once was N/A is as far as i got. so far i havent
actually properly compiled nor configured any CUDA workloads using FreeBSD yet,
mostly for lack of trying for any more than seven minutes.

its my next off hours project. ive heard its been done using the NVidia CUDA
SDK, Linuxulator and FreeBSD native driver from ports. just no ones done UVM
yet, only GPU VRAM.

i am guessing the two new .ko's on the plist are for GSP's on prior hardware
generations and the GSP bits for Ada Lovelace are in the main .ko??

nvidia_gsp_{ga,tu}10x_fw.ko both do get installed, of course, but my first
instinct was to not call upon them in any way. According to kldstat, neither
did nvidia{-drm,,-modeset}.ko.

HOWEVER nvidia-smi -q indeed reports "GSP Firmware Version: 560.31.02". I don't
know how I'd go about actually testing what functions that rely on it
specifically.

in ALL [non-pptdev] configurations i've only ever simply added nvidia-drm to
rc.conf.local->kld_list and added Device.{Driver,BusID} to xorg.conf. (i.o.w. i
changed nothing config-wise from what i'd been using day to day out of the
ports tree)

now, while using the 560 driver for days kldstat does NOT list any
gsp_*_fw.ko's. does that track with what you're expecting? are they unneeded at
all or maybe i never used the feature that might auto-load one/both?

> Unfortunately, CUDA and UVM are not stated to be supported even on 560.31.02. At least, modules/components needed for them, which Linux version has, are not built on FreeBSD yet.

are these needed modules/components NVidia driver bits or FreeBSD kernel bits?
whose palms do i gotta grease? where can we start? what books do we gotta read?
lol

-- 
You are receiving this mail because:
You are the assignee for the bug.