Yes it looks like that Nvidia made the 470 driver a new long service branch for soon-legacy cards, like the no-longer-supported 304, 340 and the 390 of which support will be dropped in autumn.
Will have to update the skunk installer for that, probably I get time somewhere end of June.
skunk The latest x11/nvidia-driver in ports is at 510.60.02, but there is a 515.48.07 (at least when I searched by my GT750 card specs). What's interesting is the comments in the port shows how to easily build for a different version:
make DISTVERSION=xxx.yy.zz -DNO_CHECKSUM
as long as it compiles. I think nvidia-driver may be built for "latest" pkgs, but not for quarterly, but this shows how trivial it is to "compile the driver but within the ports/pkg system".
Truly interesting find!
This could make work-around driver bugs easy, as they recently became visible in another thread, where the brand-new driver failed, but another one some slightly older .yy or .zz version worked fine.
You've been reading my posts on this thread you know I have that set. I don't have any USB flash drives plugged in, virtualbox is not running. Nothing is really running. I literally just logged in, started X, went into wm and brought up an xterm and suspended. You still didn't answer my original question if building with ACPI_PM support would help suspend/resume in succeeding. And what about all the processes being SIGSEGV'd ? What driver/software could possibly be conflicting? all I have loaded is nvidia kernel modules, (and linux.ko, linux_common.ko). Running icewm. A PS/2 keyboard and mouse. Pretty light setup. Suspend does work in other OSes.
I didn't make any experiments with ACPI PM support, just used the GENERIC defaults (except for
nooptions VESA
).
Regarding the PS/2 mouse, this has some bad implications. Any mouse event from the PS/2 mouse wakes up the computer. There seem to be some problems regarding shutting down PS/2 mouse events, as these can abort an ongoing suspend/resume sequence. Annoying also is that mice sometimes flip forth and back between coordinates, waking up the computer out of the blue.
Currently I am using a vintage serial/PS/2 Microsoft cordless wheel mouse, still with a ball. The only way to suspend reliably with this mouse is to use its switch on the bottom, to have it switch to the other radio channel to practically disconnect it. Other PS/2 (optical) mice can be used well only by putting it somewhere on something so that they are not lying on plain surface, and not giving events when they should not do.
This said, I strongly suggest using an USB mouse to avoid these problems.