Booting with the above version of nvidia-drivers results in an unusable system: no X server, and even my getty virtual consoles don't appear. (vt7 is 100% black, vt1 and vt2 are lighter black, as if the backlight is on). I can ssh in, but /var/log/Xorg.0.log shows nothing useful. Reverting to 460.91.03 solves the problem. This is a Dell m4800 laptop. The only useful info I can think to provide is: # lspci -vv|grep -4i nvid .... 01:00.0 VGA compatible controller: NVIDIA Corporation GK106GLM [Quadro K2100M] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GK106GLM [Quadro K2100M] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 -- Capabilities: [600 v1] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Capabilities: [900 v1] Secondary PCI Express LnkCtl3: LnkEquIntrruptEn- PerformEqu- LaneErrStat: 0 Kernel driver in use: nvidia Kernel modules: nouveau, nvidia_drm, nvidia Reproducible: Always
Please provide emerge --info.
Portage 3.0.20 (python 3.9.6-final-0, default/linux/amd64/17.1/hardened, gcc-10.3.0, glibc-2.33-r1, 5.10.52-gentoo-x86_64 x86_64) ================================================================= System uname: Linux-5.10.52-gentoo-x86_64-x86_64-Intel-R-_Core-TM-_i7-4810MQ_CPU_@_2.80GHz-with-glibc2.33 KiB Mem: 16331288 total, 10602188 free KiB Swap: 33554428 total, 33554428 free Timestamp of repository gentoo: Sat, 21 Aug 2021 07:00:01 +0000 Head commit of repository gentoo: 75bbb00268a3e8bec8f41ee842298d0368b48646 sh bash 5.1_p8 ld GNU ld (Gentoo 2.35.2 p1) 2.35.2 distcc 3.4 x86_64-pc-linux-gnu [disabled] app-shells/bash: 5.1_p8::gentoo dev-java/java-config: 2.3.1::gentoo dev-lang/perl: 5.34.0::gentoo dev-lang/python: 2.7.18_p11::gentoo, 3.9.6_p1::gentoo dev-lang/rust: 1.53.0::gentoo dev-util/cmake: 3.20.5::gentoo sys-apps/baselayout: 2.7::gentoo sys-apps/sandbox: 2.24::gentoo sys-devel/autoconf: 2.13-r1::gentoo, 2.69-r5::gentoo sys-devel/automake: 1.13.4-r2::gentoo, 1.16.3-r1::gentoo sys-devel/binutils: 2.35.2::gentoo, 2.36.1-r2::gentoo sys-devel/gcc: 10.3.0-r2::gentoo sys-devel/gcc-config: 2.4::gentoo sys-devel/libtool: 2.4.6-r6::gentoo sys-devel/make: 4.3::gentoo sys-kernel/linux-headers: 5.10::gentoo (virtual/os-headers) sys-libs/glibc: 2.33-r1::gentoo Repositories: gentoo location: /usr/portage sync-type: rsync sync-uri: rsync://gentoo.edsantiago.com/gentoo-portage priority: -1000 sync-rsync-verify-metamanifest: yes sync-rsync-verify-max-age: 24 sync-rsync-verify-jobs: 1 sync-rsync-extra-opts: esm-g-cpan location: /opt/gentoo/gcpan-overlay masters: gentoo priority: 0 ACCEPT_KEYWORDS="amd64" ACCEPT_LICENSE="@FREE LastPass" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=native -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/lib64/libreoffice/program/sofficerc /usr/share/gnupg/qualified.txt" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo" CXXFLAGS="-march=native -O2 -pipe" DISTDIR="/usr/portage/distfiles" EMERGE_DEFAULT_OPTS="--quiet-build" ENV_UNSET="CARGO_HOME DBUS_SESSION_BUS_ADDRESS DISPLAY GOBIN GOPATH PERL5LIB PERL5OPT PERLPREFIX PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR" FCFLAGS="-O2 -pipe" FEATURES="assume-digests binpkg-docompress binpkg-dostrip binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles ipc-sandbox merge-sync multilib-strict network-sandbox news parallel-fetch pid-sandbox preserve-libs protect-owned qa-unresolved-soname-deps sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr" FFLAGS="-O2 -pipe" GENTOO_MIRRORS="http://gentoo.edsantiago.com/ http://gentoo.osuosl.org/ http://mirrors.rit.edu/gentoo/ http://www.gtlib.gatech.edu/pub/gentoo" LANG="en_US.utf8" LDFLAGS="-Wl,-O1 -Wl,--as-needed" LINGUAS="en en_US" MAKEOPTS="-j6" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --exclude=/.git" PORTAGE_TMPDIR="/var/tmp" USE="X acl alsa amd64 bash-completion bluetooth bzip2 crypt cups curl dbus dvd dvdnav emacs exif fontconfig gdbm hardened hidpi iconv icu ipv6 jpeg kdrive lcms libglvnd libtirpc mmx mp3 multilib ncurses nls nptl opengl openmp pam pcre pdf perl pie png postscript pulseaudio readline sdl seccomp smp split-usr sse sse2 ssl ssp systemd theora tiff truetype udisks unicode vdpau vorbis webp x264 xattr xft xmp xnest xtpax xv zlib zsh-completion" ABI_X86="64" ADA_TARGET="gnat_2018" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="karbon sheets words" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="aes avx avx2 f16c fma3 mmx mmxext pclmul popcnt rdrand sse sse2 sse3 sse4_1 sse4_2 ssse3" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock greis isync itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 timing tsip tripmate tnt ublox ubx" INPUT_DEVICES="evdev synaptics" KERNEL="linux" L10N="en en_US" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" LUA_SINGLE_TARGET="lua5-1" LUA_TARGETS="lua5-1" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php7-3 php7-4" POSTGRES_TARGETS="postgres12 postgres13" PYTHON_SINGLE_TARGET="python3_9" PYTHON_TARGETS="python3_9" RUBY_TARGETS="ruby26" USERLAND="GNU" VIDEO_CARDS="nouveau nvidia" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq proto steal rawnat logmark ipmark dhcpmac delude chaos account" Unset: CC, CPPFLAGS, CTARGET, CXX, INSTALL_MASK, LC_ALL, PORTAGE_BINHOST, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, RUSTFLAGS
>/var/log/Xorg.0.log shows nothing useful Are you sure about that? My guess would be that you built modules for the wrong kernel (aka not the one you are booting), and the log (and dmesg) would mention something about API mismatch (may want to check the log timestamp too, sometime it's an outdated Xorg.0.log when you've started using ~/.local/share/xorg/Xorg.0.log at some point). Please check your `uname -a` to ensure it's the expected kernel too (look at timestamp). Don't readily know of any issue with the drivers itself that'd cause this and it's been stable for some time, this may be better suited for support channels[1] (difficult to help on bugzilla). [1] https://www.gentoo.org/support/
I'm sure that Xorg.0.log didn't show anything useful _to me_; there could easily have been something I missed. I was desperate because I had a nonworking system, and in my panic I neglected to preserve the log. I have made a note to try to recreate next weekend after my return from travel.
Created attachment 736168 [details] Xorg.0.log I unmasked nvidia-drivers-470.57.02, emerge'd it against current 5.10.52-gentoo-x86_64 kernel, and rebooted. As before, there is no XDM login box, only a dark black screen. When I press Ctrl-Alt-F1 the screen grows less black, like the backlight gets turned on, but nothing is visible (under a working nvidia-drivers I would see boot logs). Alt-F2, likewise no output (I expected a console login prompt). Attached is Xorg.0.log. Diff'ing against Xorg.0.log.old, I see only timestamp differences until the very very end. In the old log after "This device may have been added with another device file", I see: [ 35.878] (--) NVIDIA(GPU-0): Sharp (DFP-4): connected [ 35.878] (--) NVIDIA(GPU-0): Sharp (DFP-4): Internal DisplayPort [ 35.878] (--) NVIDIA(GPU-0): Sharp (DFP-4): 960.0 MHz maximum pixel clock [ 35.878] (--) NVIDIA(GPU-0): [ 48.487] (--) NVIDIA(GPU-0): CRT-0: disconnected [ 48.487] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock [ 48.487] (--) NVIDIA(GPU-0): [ 48.487] (--) NVIDIA(GPU-0): DFP-0: disconnected [ 48.487] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS [ 48.487] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock [ 48.487] (--) NVIDIA(GPU-0): [ 48.487] (--) NVIDIA(GPU-0): DFP-1: disconnected [ 48.487] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS [ 48.487] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock [ 48.487] (--) NVIDIA(GPU-0): [ 48.487] (--) NVIDIA(GPU-0): DFP-2: disconnected [ 48.487] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS [ 48.487] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock [ 48.487] (--) NVIDIA(GPU-0): [ 48.488] (--) NVIDIA(GPU-0): DFP-3: disconnected [ 48.488] (--) NVIDIA(GPU-0): DFP-3: Internal DisplayPort [ 48.488] (--) NVIDIA(GPU-0): DFP-3: 960.0 MHz maximum pixel clock [ 48.488] (--) NVIDIA(GPU-0): [ 48.488] (--) NVIDIA(GPU-0): Sharp (DFP-4): connected [ 48.488] (--) NVIDIA(GPU-0): Sharp (DFP-4): Internal DisplayPort [ 48.488] (--) NVIDIA(GPU-0): Sharp (DFP-4): 960.0 MHz maximum pixel clock [ 48.488] (--) NVIDIA(GPU-0): [ 48.488] (--) NVIDIA(GPU-0): DFP-5: disconnected [ 48.488] (--) NVIDIA(GPU-0): DFP-5: Internal DisplayPort [ 48.488] (--) NVIDIA(GPU-0): DFP-5: 960.0 MHz maximum pixel clock [ 48.488] (--) NVIDIA(GPU-0): [ 48.488] (--) NVIDIA(GPU-0): DFP-6: disconnected [ 48.488] (--) NVIDIA(GPU-0): DFP-6: Internal DisplayPort [ 48.488] (--) NVIDIA(GPU-0): DFP-6: 960.0 MHz maximum pixel clock [ 48.488] (--) NVIDIA(GPU-0): [ 48.489] (--) NVIDIA(GPU-0): CRT-0: disconnected [ 48.489] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock [ 48.489] (--) NVIDIA(GPU-0): [ 48.489] (--) NVIDIA(GPU-0): DFP-0: disconnected [ 48.489] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS [ 48.489] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock [ 48.489] (--) NVIDIA(GPU-0): [ 48.489] (--) NVIDIA(GPU-0): DFP-1: disconnected [ 48.489] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS [ 48.489] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock [ 48.489] (--) NVIDIA(GPU-0): [ 48.490] (--) NVIDIA(GPU-0): DFP-2: disconnected [ 48.490] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS [ 48.490] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock [ 48.490] (--) NVIDIA(GPU-0): [ 48.490] (--) NVIDIA(GPU-0): DFP-3: disconnected [ 48.490] (--) NVIDIA(GPU-0): DFP-3: Internal DisplayPort [ 48.490] (--) NVIDIA(GPU-0): DFP-3: 960.0 MHz maximum pixel clock [ 48.490] (--) NVIDIA(GPU-0): [ 48.490] (--) NVIDIA(GPU-0): Sharp (DFP-4): connected [ 48.490] (--) NVIDIA(GPU-0): Sharp (DFP-4): Internal DisplayPort [ 48.490] (--) NVIDIA(GPU-0): Sharp (DFP-4): 960.0 MHz maximum pixel clock [ 48.490] (--) NVIDIA(GPU-0): [ 48.490] (--) NVIDIA(GPU-0): DFP-5: disconnected [ 48.490] (--) NVIDIA(GPU-0): DFP-5: Internal DisplayPort [ 48.490] (--) NVIDIA(GPU-0): DFP-5: 960.0 MHz maximum pixel clock [ 48.490] (--) NVIDIA(GPU-0): [ 48.490] (--) NVIDIA(GPU-0): DFP-6: disconnected [ 48.490] (--) NVIDIA(GPU-0): DFP-6: Internal DisplayPort [ 48.490] (--) NVIDIA(GPU-0): DFP-6: 960.0 MHz maximum pixel clock [ 48.490] (--) NVIDIA(GPU-0): Again, this is a circa-2014 laptop, I'm wondering if nvidia simply dropped support for it?
Are you still able to ssh to it from another device? `dmesg` may have something of more interest. I doubt support was dropped, NVIDIA does make it clear when they drop support for a device and no such thing happened in 470 (albeit they announced it's the last branch to support kepler GPUs, so next one will), but regressions for less-tested hardware is plenty possible -- not that it's something I could do anything about, need to go upstream for that (currently 460.xx branch is still supported, so it'll be staying around if no real issues with it).
Yes, I can ssh; but laptop is up now (using 460.91.03), and here's what I can extract from `journalctl -b -2) with selective extraction ("nvidia" plus anything that looks relevant to my eye): Aug 26 14:33:34 d.edsantiago.com kernel: nvidia: loading out-of-tree module taints kernel. ... Aug 26 14:33:34 d.edsantiago.com kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 246 ... Aug 26 14:33:34 d.edsantiago.com systemd-udevd[2074]: Using default interface naming scheme 'v247'. Aug 26 14:33:34 d.edsantiago.com kernel: nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem ... Aug 26 14:33:34 d.edsantiago.com systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:dell_backlight... Aug 26 14:33:34 d.edsantiago.com kernel: Adding 33554428k swap on /dev/mapper/vg0-swap. Priority:-2 extents:1 across:33554428k SS Aug 26 14:33:34 d.edsantiago.com systemd[1]: Starting Load/Save Screen Backlight Brightness of leds:dell::kbd_backlight... ... Aug 26 14:33:34 d.edsantiago.com systemd[1]: Finished Load/Save Screen Backlight Brightness of backlight:dell_backlight. Aug 26 14:33:34 d.edsantiago.com systemd[1]: Finished Load/Save Screen Backlight Brightness of leds:dell::kbd_backlight. ... Aug 26 14:33:37 d.edsantiago.com kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 Aug 26 14:33:37 d.edsantiago.com kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 470.57.02 Tue Jul 13 16:06:24 UTC 2021 Aug 26 14:33:37 d.edsantiago.com kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver Aug 26 14:33:37 d.edsantiago.com kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0 ... Aug 26 14:33:44 d.edsantiago.com systemd[1]: Starting X-Window Display Manager... ... Aug 26 14:33:45 d.edsantiago.com kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000dc000-0x000dffff window] Aug 26 14:33:45 d.edsantiago.com kernel: caller _nv000722rm+0x1ad/0x200 [nvidia] mapping multiple BARs ... Aug 26 14:33:48 d.edsantiago.com systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:nvidia_0... Aug 26 14:33:48 d.edsantiago.com systemd[1]: Finished Load/Save Screen Backlight Brightness of backlight:nvidia_0. ... Aug 26 14:33:48 d.edsantiago.com systemd[1]: Started X-Window Display Manager. Aug 26 14:33:48 d.edsantiago.com systemd[1]: Reached target Graphical Interface. That's it. A few minutes after that I ssh in from another host, which I only did because my display was dead. As best I can tell, xdm thinks it's up. I wondered about 'Screen Backlight ... nvidia' but those lines also show up in my most recent (working) boot. So does 'resource sanity check' and 'mapping multiple BARs'. Logs look remarkably similar to my eye.
I was expecting something worse looking, but maybe backlight is suspicious considering there's bug #780126 that prevents setting backlight for some setups (not limited to gnome, and it's still not fixed from what I hear -- there's been a lot of threads on nvidia's linux forums about backlight lately), and in your case maybe it's just not turning it on. Not that I have a solution to offer if it's that beside waiting for nvidia to fix it and staying on 460.xx meanwhile.
May technically be a duplicate, but hard to confirm. Will keep this open for reference until it's fixed or some other solution is found.
Thanks for the pointer. Your hunch sounds plausible: Gnome somehow setting brightness to full-on, but it being full-off in my plain X11 setup. I'm not feeling deeply motivated to reboot, fiddle with xauth, and try xbacklight or vbetool; but if you think it could be useful, I'll try.
Problem still present in 470.63.01 I'm inclined to think that it is not the same problem as bug 780126, because: (via ssh): # ps auxww|grep xdm # export XAUTHORITY=/var/lib/xdm/authdir/authfiles/A\:0-Igs5WK # export DISPLAY=:0 [confirm via xset q & xdpyinfo] # xbacklight -set 80 (has no effect whatsoever; nor does 100) This is not too surprising, because (as mentioned in comment 0) VT1 and VT2 give the impression of backlight being turned on: although the display is completely black, with no characters or anything, the difference between VT7 (X11) and VT1/2 (consoles) is that the former is 100% dark, the latter have a faint glow suggesting backlight is on. FWIW, `vbetool dpms off` just hangs until I ^C it. `vbetool vbemode get` yields 330.
I have I think the same problem on a Thinkpad P53 (does not use Optimus). Any nvidia driver newer than 460.91.03 gives a black laptop screen (although thankfully my external monitor continues to work). # lspci -vv|grep -4i nvid Address: 00000000fee08000 Data: 4024 Kernel driver in use: e1000e Kernel modules: e1000e 01:00.0 VGA compatible controller: NVIDIA Corporation TU106GLM [Quadro RTX 3000 Mobile / Max-Q] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU106GLM [Quadro RTX 3000 Mobile / Max-Q] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 -- Capabilities: [bb0 v1] Physical Resizable BAR BAR 0: current size: 16MB, supported: 16MB BAR 1: current size: 256MB, supported: 64MB 128MB 256MB BAR 3: current size: 32MB, supported: 32MB Kernel driver in use: nvidia Kernel modules: nvidia_drm, nvidia
Today I tried 470.86-r2 and 470.94. Both are broken in the same way as initially reported here.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1df072f63f101fc09d4c668156a27f5755acda26 commit 1df072f63f101fc09d4c668156a27f5755acda26 Author: Ionen Wolkens <ionen@gentoo.org> AuthorDate: 2021-12-28 12:00:47 +0000 Commit: Ionen Wolkens <ionen@gentoo.org> CommitDate: 2021-12-28 13:12:31 +0000 x11-drivers/nvidia-drivers: sync 460.91.03 ebuild with others 460.91.03 is unfortunately known needed for (at least) a few laptop users, issues varying between not able to control backlight or not seeing anything displayed at all (bug #780126 and bug #809482, along with several threads on NVIDIA forums complaining about this). Can't be kept eternally given NVIDIA shows no sign of continued 460 support and it requires xorg-1.20 plus <=5.10 LTS kernels (unlike even the 390.xx branch) -- but, meanwhile, update ebuild to be like the others and easier to maintain. Fortunately no known security issues. Let's hope 470/495+ will receive fixes before removal is necessary (perhaps to cleanup old xorg or security concerns), feedback from users welcome to know when it works as expected or if anything else can do (own hardware is not affected, so can't test). Bug: https://bugs.gentoo.org/780126 Bug: https://bugs.gentoo.org/809482 Signed-off-by: Ionen Wolkens <ionen@gentoo.org> .../nvidia-drivers-460.91.03-r2.ebuild | 400 +++++++++++++++++++++ 1 file changed, 400 insertions(+)
Created attachment 765011 [details, diff] nvidia-drivers-460.91.03-r2.patch nvidia-drivers-470.103.01 does not work: same black-screen issue. nvidia-drivers-460 does not compile on kernels >5.10 Solution: 1) mask >=x11-drivers/nvidia-drivers-470 2) save attachment as /etc/portage/patches/x11-drivers/nvidia-drivers/nvidia-drivers-460.91.03-r2.patch This lets nvidia-drivers compile, and seems to work so far (gives me a usable X display). Can't update to xorg-server-21, but I will defer that problem. (FWIW, nouveau has never worked well for me: lots of pixel artifacts, and high CPU load. Some day I will be forced to upgrade. Again, I defer that).
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f6760422f09a51c212b201967a25ca8774b0d594 commit f6760422f09a51c212b201967a25ca8774b0d594 Author: Ionen Wolkens <ionen@gentoo.org> AuthorDate: 2022-03-02 09:16:27 +0000 Commit: Ionen Wolkens <ionen@gentoo.org> CommitDate: 2022-03-02 09:53:25 +0000 x11-drivers/nvidia-drivers: drop vulnerable 460.91.03-r2 460 branch was meant to be removed months ago but was kept due to known regressions affecting some users (bug #780126, bug #809482, and some other rumored issues). These regressions are not (fully) resolved but given NVIDIA no longer supports this branch, doesn't report if it's affected by vulnerabilities anymore (bug #832867, safe to say it most likely is), need patches for current stable kernel branch, and it relies on old Xorg ABI preventing future Xorg cleanups -- believe time to give it up. Users that /really/ need it are free to use a local overlay at their own risks, and may want to try IgnoreABI with xorg-21. Bug: https://bugs.gentoo.org/780126 Bug: https://bugs.gentoo.org/809482 Bug: https://bugs.gentoo.org/832867 Signed-off-by: Ionen Wolkens <ionen@gentoo.org> x11-drivers/nvidia-drivers/Manifest | 6 - .../nvidia-drivers-460.91.03-r2.ebuild | 411 --------------------- 2 files changed, 417 deletions(-)
Been a while and unfortunately don't think there's anything I can do here. Keeping a driver branch that's not supported by NVIDIA can't be done indefinitely (especially with security issues that I can't patch on a binary blob). Hope this will be resolved by NVIDIA at some point.
