...the github page but also how the configuration files are commented. apart from me being silly and not realizing that the linux-drivers for nvidia needs to be installed it basically worked right away.
Unfortunately modifying the ollama container to instead run llama-cpp is tad tricker. It...
It was all needed to make it work on my specific configuration. What you are waging a crusade over is horrifying. It isn't horrorific for my FreeBSD where I'm running a kernel 16.0 that allows me to run qemu + bhyve. I validated all the code there, and getting it to work required some exotic...
...1000 lines with regular expressions and completely un needed code
so much abuse of cat i should call the rscpa
downloading and building the nvidia driver
adding in a dockerfile and compose.yaml into a script
defeats the whole point of podman
building a frankenstein os in a container
with...
The uvm_ioctl_override.c / dummy-uvm.so stopped working after the Nvidia 535 diver
I see it was updated on the Dec 4, 2024.
I had to switched back to linux just before that,
and only came back to Freebsd a couple of months ago
Someone on reddit messaged me about my Davinci Resolve project...
my first pc was not vintage to be honest but i love it and still own it to this day but sadly it shows its age :(
Dell Precision T3400
Core 2 quad
4 GB of DRR2 RAM
128MB nvidia card ( i do NOT miss this card at all)
600 GB western digital hdd
i used it as my only and main machine till 2025
Thanks for this, honestly brings a smile :) I personally don't find many greater complements than those relating to workflow and process, be they technical or business. Moreover, as well as continuity of operations it increases productivity a great deal, especially in a new context, when you can...
...vs baremetal:
1. For KVM VirtIO graphics: On FreeBSD 14/15, the standard KMS driver stack (drm-kmod) is primarily for physical GPUs (Intel/AMD/Nvidia). Inside KVM with VirtIO-GPU, FreeBSD typically uses the EFI GOP framebuffer via the vt(4) driver (vt_vga). Make sure you have kern.vty=vt in...
2026Q3 has 595.84, latest has 595.99.02. In case you were wondering where the difference came from.
https://cgit.freebsd.org/ports/tree/x11/nvidia-driver/Makefile.version?h=2026Q3
https://cgit.freebsd.org/ports/tree/x11/nvidia-driver/Makefile.version?h=main
...Alain for showing that I had older libdrm installed ,
now updated to version 2.4.134.1
-------------------
pkg info | egrep "nvidia|drm"
drm-612-kmod-6.12.85.1501502_1 Direct Rendering Manager (DRM) GPU drivers
drm-kmod-20260508 Direct Rendering Manager (DRM) GPU...
Status-Report : Nvidia driver 595:99.02.150102 appears to be more stable than its predessesor 595.91 . With 595.91 I had kernel panics when trying to use DRM-612. With 595.99 DRM-612 starts and works again. ( using a desktop based on i7-11700K...
Well, I figured the easiest way would be to upgrade the linux-nvidia-libs to 595.99.02 since FreeBSD Ports Search lists it.
However after doing the below I am confused.
git pull
git status
On branch main
Your branch is up to date with 'origin/main'.
ls x11/linux-nvidia-libs*...
looks like you have a mismatch between the driver version and the libraries
you could try updating and reinstalling the drivers
maybe something like this
sudo pkg update
sudo pkg upgrade linux-nvidia-libs nvidia-driver
and rebooting
No, it's in the container.
I have rebuilt base x11 and ollama but still same.
Logs now say this:
sudo podman-compose logs -f
chmod: changing permissions of '/run/user/1001-writeable': Operation not permitted
chown: cannot read directory '/run/user/1001-writeable': Permission denied
/grandpa
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
