Which NVIDIA GPU for tear-free Xorg/dwm

J

jb82

Hi guys,
I bet FreeBSD would be 10x more prevalent, if there was a nicely maintained up-to-date (!) page listing fully supported hardware. My question:

Which of not-so-dated NVIDIA GPUs like 3060, or 4060, or whatever do you use without any hiccups as you daily driver?
Xorg/dwm, Firefox and bunch of st terminals is my setup. I use compton/picom because I like fading and tearfree.

Moreover, do you need Full Composition Pipeline enabled to prevent tearing? No wayland please.
 
pciconf -lv describes mine as GP108 [GeForce GT 1030] and it works fine for me, dwm, (occasional openbox, and, although you specifically said you don't care, Wayland's dwm and labwc (dwl and openbox equivalents). I don't do anything special, I installed the driver and kmod and I do run linux as a service, so I guess it's using that.
 
My old Quadro P1000 (notebook) in my ThinkPad P52 is working fine on X11 (Mate with Compiz, login with CUI ans manually startx).
Otherwise, I'm not maintaining nvidia driver ports.

Wayland is problematic for me, but it's NOT GPU-related, but Japanese input support of Wayland itself is fatally broken at least for me.

If you want recent GPUs, track latest (aka main) branch of ports tree rather than quarterly (currently 2025Q3). Quarterly wouldn't accept updates other than security fixes and build fixes, thus, delays 3 months at maximum.

Unfortunately, cutting edge RTX 50xx series is known to have some issues (multiple PRs, some has workaround [config and/or patch], but some does not). You'll find some threads here and PRs on Bugzilla.

And currently, FreeBSD-kmods repo does NOT have nvidia driver related pkgs as of restriction of the pkg builder. Attempts to fix this situation is under review now. If you're using 14.3, build locally from ports for now.
 
i have p620 ( pascal ) - fine, used 3070Ti - fine, used Titan V ( Volta ) fine. heck, even unsuported AMD Radeon Pro W5500 has no tears.
 
T-Aoki, I have Japanese working fairly well with labwc. (Though not as well with dwl). Using alacritty terminal and firefox--it works in both of those. https://srobb.net/jpninpt.html#wayland

Actually, I just doublechecked. I have it working in firefox and alacritty terminal, but not in QT apps. And definitely not as easy as it is in X.
 
scottro said:
T-Aoki, I have Japanese working fairly well with labwc. (Though not as well with dwl). Using alacritty terminal and firefox--it works in both of those. https://srobb.net/jpninpt.html#wayland

Actually, I just doublechecked. I have it working in firefox and alacritty terminal, but not in QT apps. And definitely not as easy as it is in X.
Click to expand...
Interesting!
In my quite old memory, in ancient days, configuring Japanese input environment was difficult on X11. And slowly improved to current easy state.

If I recall correctly, the first Unix-like and non-proprietary OS that pre-configured Japanese inputs, editing and browsing was Vine Linux.

I think Wayland, too, need much more years to be like current X11, which is silly. Why didn't them succeeded the experiences on X11 as-is?! Quite silly.
And if the difficulties depends on compositor, it's silly, of course.

On X11, bare minimum usabilities for Japanese input is done by xim, and toolkits like Gtk, Qt and Japanese input frameworks like fcitx and scim provides additional conveniences over it. Why can't Wayland do the same?

I can't stop thinking that Wayland guys (at least initially) intentionally ignored these.
 
drhowarddrfine said:
I'm not sure. That one says Unix Driver "Archive" which, to me, implies older product drivers while the one I showed let's you select drivers by product.
Click to expand...
But this site is where I regularly look for updates and start working on nvidia driver ports. And as far as I know, there are no actual delays of availability, at least for produnction branch.

Latest drivers from production, new feature, beta and legacy branches are listed there and convenient.
 
T-Aoki, yes, it used to be a real pain. First scim-kinput, then ibus-anthy, I think. I remember on my Japanese in Linux/BSD site I had a tarball for scim and probably one for kinput2. But it's gotten extremely easy, IMO. And I remember Vine Linux and my wife getting annoyed as I'd call her over to ask what something on the screen meant.
In RedHat's Wayland Gnome default server with GUI, Japanese is pretty simple, you basically add it in the keyboard screen and it works with both GTK and QT, I think. (Now I feel like I have to test it.) That's with ibus. So, I'm sure it's not that hard to do.
 
T-Aoki I just tested with an Alma (RH clone) VM. Ibus-anthy can be installed, and once it's there one can use Japanese easily with a terminal, firefox and libreoffice, which were all that I tested. Charlie_ I think I might have tried Plamo at the time too, back then, (the early 2000's) I used Japanese more and it was more important to me to get a Linux with working Japanese. These days, I seldom have need of it.
 
Oh, Plamo...
I've never tried that as I didn't have spare drive / partition to install it at the moment I noticed its existence.
 
FYI:
Found latest production branch of nvidia driver set 580.82.07 is released yesterday (JST), just after post #6.
Tried and looks working without unknown new issues on X11, so filed PR 289261 and opened corresponding review D52352 for it.
 
You must log in or register to reply here.
Back
Top