On Thu, 2022-08-18 at 23:14 -0400, Patrick Shanahan wrote:
* Masaru Nomiya
[08-18-22 23:11]: Hello,
In the Message;
Subject : Re: TW: boot problem kernel 5.18.9-2 and higher Message-ID : <20220819025112.GI22216@wahoo.no-ip.org> Date & Time: Thu, 18 Aug 2022 22:51:12 -0400
[PS] == Patrick Shanahan
has written: [...] PS> > Is there a configuration file in /etc/modprobe.d that contains any of PS> > the following? PS> > PS> > 1. blacklist nouveau PS> > PS> > 2. blacklist nouveau PS> > options nouveau modeset=0
PS> I have nowhere to look now as I am currently and for the last several PS> years using rpm to update my nvidia drivers.
How about this;
/usr/lib/modprobe.d/nvidia-default.conf
the three system I currently have with nvidia all show: > cat /usr/lib/modprobe.d/nvidia-default.conf blacklist nouveau
I had some derivation of G04/G05 installed EARLY on for the Dell which has an Intel iGPU and nvidia T1000. Either due to my misunderstanding or an actual problem (I didn't recognize), I had little to no success with the RPM version of nvidia drivers ~ so I ditched them for .run installs (which I also sign and have secure boot enabled since the laptop is also for use with Windows 11; at worst, sometimes I have to enter the bitlocker recovery key when I boot windows, but I don't lose sleep over it). I don't really care about using the iGPU or switching between them, my goal was to just use the T1000 via the laptop screen (so no external display plugged in as I'd generally ssh to it or use Xpra). My main issue, which had persisted for at least 6mos, was that it'd boot to a black screen (on what I assume was vt7). Using the .run always worked fine (w/o X11 running of course) and I'd `sudo systemctl restart display-manager.service` and be greeted with a lightdm login screen. But subsequent reboots always yielded a black screen. That was solved with a CTRL+ALT+F4, login, `sudo modprobe nvidia_drm` and `sudo systemctl restart display-manager.service` ; Very simple, but I wanted to know why it was always the case. I don't use any extra boot parameters and have these ACTIVE files in: /etc/modprobe.d -- $ /bin/cat nvidia-installer-disable-nouveau.conf # generated by nvidia-installer blacklist nouveau options nouveau modeset=0 $ /bin/cat 50-nvidia-smb.conf options nvidia_drm modeset=1 /usr/lib/modprobe.d -- $ /bin/cat nvidia-installer-disable-nouveau.conf # generated by nvidia-installer blacklist nouveau options nouveau modeset=0 /usr/lib/modules-load.d -- $ /bin/cat nvidia_drm.conf nvidia_drm The '/etc/modules-load.d' directory is empty. The 'prime-select' service always fails to start at boot, but `sudo prime-select get-current` returns 'nvidia': $ sudo prime-select get-current Driver configured: nvidia NVIDIA modules are loaded I also had next to no luck following what bbswitch was actually doing and at one point it'd just completely disable the NVIDIA card; so I've disabled '/usr/lib/modules-load.d/bbswitch.conf' by renaming '.conf' to 'DOTconf'. I see these nvidia related messages after boot through dmesg: $ dmesg | grep -i nvidia [ 30.338461] audit: type=1400 audit(1660917198.283:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=792 comm="apparmor_parser" [ 30.339146] audit: type=1400 audit(1660917198.283:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=792 comm="apparmor_parser" [ 42.359200] nvidia: loading out-of-tree module taints kernel. [ 42.359653] nvidia: module license 'NVIDIA' taints kernel. [ 42.370739] nvidia: module verification failed: signature and/or required key missing - tainting kernel [ 42.437506] nvidia-nvlink: Nvlink Core is being initialized, major device number 237 [ 42.438514] nvidia 0000:01:00.0: enabling device (0000 -> 0003) [ 42.486075] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 [ 44.789252] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 515.65.01 Wed Jul 20 13:43:59 UTC 2022 [ 45.731149] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver [ 46.310497] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0 And these for i915: $ dmesg | grep -i i915 [ 2.413937] i915 0000:00:02.0: [drm] VT-d active for gfx access [ 2.497787] i915 0000:00:02.0: vgaarb: deactivate vga console [ 2.497815] i915 0000:00:02.0: [drm] Transparent Hugepage mode 'huge=within_size' [ 2.519429] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 2.520378] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [ 2.627659] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 1 [ 2.645536] fbcon: i915drmfb (fb0) is primary device [ 3.800019] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device [ 37.275611] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 41.460005] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) Now at [re]boot I'm greeted with lightdm consistently. -- ~ Scott Bradnick |- Windows Subsystem for Linux (WSL) Developer |-- Tumbleweed: |--- Dell Precision 5540 [NVIDIA Quadro T1000] (x86_64) |--- O-DROID H2+ [UHD Graphics 600] (x86_64) |--- IceWhale ZimaBoard 832 [Intel HD Graphics 500] (x86_64) |--- 2x Raspberry Pi 4 Model B Rev 1.2 (aarch64) |--- 1x Raspberry Pi 3 Model B Rev 1.2 (aarch64) |--- WinBook TW100 (x86_64) https://keys.openpgp.org/ :: DBC5AA9A2D2BAEBC