If this is nvidia-drivers-580.126.09-r1 (note the -r1), then (like 590.x) it stopped passing fbdev=0 to override the upstream's default (the real default is fbdev=1), this can be reverted to the previous behaviour (aka, it's not "forced") by editing /etc/modprobe.d/nvidia.conf if needed which is fine as long as you do not enable a conflicting device like CONFIG_DRM_SIMPLEDRM in your kernel which doing so would *require* fbdev=1 if it gets used (in the future dist-kernels may enable SIMPLEDRM by default like e.g. fedora does, and that's why we're re-enabling fbdev=1 -- as long as it's not prebuilt gentoo-kernel-bin, you can always opt-out though)
Unsure if there's anything you can do to keep it enabled and reduce the resolution though, afaik if possible nvidia inherits the mode set by the kernel if any (may it be FB_EFI or DRM_SIMPLEDRM) which itself has a mode generally inherited from grub/efi or whatnot that typically is your native resolution -- but I haven't really experimented with fbdev=1. Know it can be quirky at times, esp. with multi-monitor setups and/or large resolutions and it's not really configurable at the moment that I'm aware of.
For the record, the ebuild prints a one-time warning about flipping fbdev when upgrading to that version, albeit many may not have noticed:
Code: Select all
if ver_replacing -lt 580.126.09-r1; then
elog "\n>=nvidia-drivers-580.126.09-r1 changes some defaults that may or may"
elog "not need attention:"
elog "1. nvidia-drm.modeset=1 is now default regardless of USE=wayland"
elog "2. nvidia-drm.fbdev=1 is now also tentatively default to match upstream"
elog "See ${EROOT}/etc/modprobe.d/nvidia.conf to modify settings if needed,"
elog "fbdev=1 *could* cause issues for the console display with some setups."
fi
If this is not -r1 but rather than the stable -r0 version (we do plan to stabilize -r1 soon'ish), then I'd assume it's something that changed in the kernel rather than nvidia given it "shouldn't" be changing the console then.