Nvidia 460.39.4 hangs on upgrade

After doing that from TTY it says the module has already been built.
I am looking at how to manually install it.

That being said even if it works, there is something awefully wrong with my installation. From my other drive which did install stupid nvidia fine, I tried compiling kernel and I get the same behavior, it hogs down the system and the more I let it run, the worse it gets.

So fixing the nvidia will most probably not fix that massive slowdown on high CPU usage.
I am getting very close from a full fresh reinstall to see what happens.

I searched on how to see what mounted a file system (which process or user, etc.) and I found nada, so I cannot trace the mounting of / into /tmp/tmp.* every time I initiate a grubup.

No problem here. Post your inxi -Fxxxza maybe I overlooked.
Check BIOS uptodate. I am on Garuda i3wm

inxi -G                   
Graphics:  Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] driver: nvidia v: 460.39 
           Display: x11 server: X.Org 1.20.10 driver: loaded: nvidia resolution: 3840x2160~60Hz 
           OpenGL: renderer: GeForce GTX 1060 6GB/PCIe/SSE2 v: 4.6.0 NVIDIA 460.39
Kernel: 5.10.11-zen2-1-zen

Ok so I've installed nvidia with DKMS command.

Still no graphical interface after a reboot. I tried to install again and it says the module is already installed. Doing startx says there are no screen found.

I tried an autoinstall or reinstall nvidia, initiating those commands display no ouput and no error.
My xorg config file looks fine.

Like I said something's awfully wrong on my installation. loll

I think I'll try a full reinstall, now.

Yeah that's definately not impossible. I guess if on a full reinstall I get the same issues then maybe I should check on the BIOS. That would mean some package around Sunday has changed to require a BIOS update. Anything's possible...

I can post inxi, would it still be valuable at this time?

2 Likes

Just an idea maybe other check more than me.

Its terrible. I late in, do you try other kernel?

1 Like

@FGD: yes, post inxi output so we don't have to guess which kernel you use.

But here is the idea. You installed the kernel module via manual DKMS command successfully (the warnings are just that, nothing major to worry about). But you interrupted the update process because the automatic install was taking way too long. So it's my guess that your iniitrd was not produced for the new kernel, or is missing relevant modules to be loaded at boot. So look how to manually update the initrd image for the new kenel. I switched to an Arch based Linux just a week ago and haven't learned yet how to do it. Please search the Arch wiki, or maybe someone here will show you,

Yes I did try 2 other kernels but both of 'em don't boot into graphical, they hang at login to SDDM. I can TTY and I get the same error as above in my other post, which is no screen found. Funny isn't it... from a working snapshot, I install a kernel through Garuda's KDE System Settings list, twice, and both of 'em don't graphically log in.

This is my inxi, however I am now in my main subvolume, so the nvidia info may not be the one of 460.39, the kernel is the same, the SSD is an nvme here but my other drives are Crucial (you can see that in inxi) and versions like Fish, etc. may differ if they had an update since Sunday. If need be I can reboot into my other drive and reissue inxi.

System: Kernel: 5.10.12-116-tkg-bmq x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: intel_pstate=passive BOOT_IMAGE=/@/boot/vmlinuz-linux-tkg-bmq
root=UUID=27cfff44-6eda-4ada-8ae8-e7b01a8e8acd rw [email protected] quiet splash rd.udev.log_priority=3
vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1 it87.force_id=0x8686 loglevel=3
Desktop: KDE Plasma 5.20.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 dm: SDDM Distro: Garuda Linux
Machine: Type: Desktop System: Gigabyte product: X570 AORUS ELITE v: -CF serial:
Mobo: Gigabyte model: X570 AORUS ELITE v: x.x serial: UEFI [Legacy]: American Megatrends v: F11
date: 12/06/2019
Battery: Device-1: hidpp_battery_0 model: Logitech Wireless Illuminated Keyboard K800 serial:
charge: 55% (should be ignored) rechargeable: yes status: Discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Mouse MX Master serial: charge: 10% (should be ignored)
rechargeable: yes status: Discharging
CPU: Info: 8-Core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 2 family: 17 (23) model-id: 71 (113)
stepping: N/A microcode: 8701013 L2 cache: 4 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 115090
Speed: 2192 MHz min/max: 2200/3600 MHz boost: disabled Core speeds (MHz): 1: 2192 2: 2195 3: 2187 4: 2186 5: 2195
6: 2190 7: 2189 8: 2192 9: 2193 10: 2186 11: 2195 12: 2194 13: 2194 14: 2194 15: 2191 16: 2196
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: NVIDIA TU117 [GeForce GTX 1650] vendor: Gigabyte driver: nvidia v: 460.32.03
alternate: nouveau,nvidia_drm bus ID: 08:00.0 chip ID: 10de:1f82
Display: x11 server: [X.Org](http://X.Org) 1.20.10 compositor: kwin_x11 driver: loaded: nvidia display ID: :0 screens: 1
Screen-1: 0 s-res: 3840x2160 s-dpi: 139 s-size: 702x392mm (27.6x15.4") s-diag: 804mm (31.7")
Monitor-1: DP-0 res: 3840x2160 hz: 60 dpi: 140 size: 697x392mm (27.4x15.4") diag: 800mm (31.5")
OpenGL: renderer: GeForce GTX 1650/PCIe/SSE2 v: 4.6.0 NVIDIA 460.32.03 direct render: Yes
Audio: Device-1: NVIDIA vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 08:00.1 chip ID: 10de:10fa
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
bus ID: 0a:00.4 chip ID: 1022:1487
Sound Server: ALSA v: k5.10.12-116-tkg-bmq
Network: Device-1: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel port: f000 bus ID: 04:00.0
chip ID: 8086:1539
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac:
IF-ID-1: nordlynx state: unknown speed: N/A duplex: N/A mac: N/A
Drives: Local Storage: total: 2.73 TiB used: 770.74 GiB (27.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB block size:
physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 serial: rev: 1B2QGXA7 temp: 32.9 C
ID-2: /dev/sda maj-min: 8:0 vendor: Crucial model: CT1000MX500SSD1 size: 931.51 GiB block size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s serial: rev: 023
ID-3: /dev/sdb maj-min: 8:16 vendor: Crucial model: CT1000MX500SSD1 size: 931.51 GiB block size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s serial: rev: 023
Partition: ID-1: / raw size: 146.48 GiB size: 146.48 GiB (100.00%) used: 81.29 GiB (55.5%) fs: btrfs dev: /dev/nvme0n1p1
maj-min: 259:1
ID-2: /home raw size: 146.48 GiB size: 146.48 GiB (100.00%) used: 81.29 GiB (55.5%) fs: btrfs dev: /dev/nvme0n1p1
maj-min: 259:1
ID-3: /var/log raw size: 146.48 GiB size: 146.48 GiB (100.00%) used: 81.29 GiB (55.5%) fs: btrfs
dev: /dev/nvme0n1p1 maj-min: 259:1
ID-4: /var/tmp raw size: 146.48 GiB size: 146.48 GiB (100.00%) used: 81.29 GiB (55.5%) fs: btrfs
dev: /dev/nvme0n1p1 maj-min: 259:1
Swap: Kernel: swappiness: 10 (default 60) cache pressure: 75 (default 100)
ID-1: swap-1 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram0
ID-2: swap-2 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram1
ID-3: swap-3 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram2
ID-4: swap-4 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram3
ID-5: swap-5 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram4
ID-6: swap-6 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram5
ID-7: swap-7 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram6
ID-8: swap-8 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram7
ID-9: swap-9 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram8
ID-10: swap-10 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram9
ID-11: swap-11 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram10
ID-12: swap-12 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram11
ID-13: swap-13 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram12
ID-14: swap-14 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram13
ID-15: swap-15 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram14
ID-16: swap-16 type: zram size: 1001 MiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram15
Sensors: System Temperatures: cpu: 28.0 C mobo: 23.0 C gpu: nvidia temp: 32 C
Fan Speeds (RPM): cpu: 744 fan-1: 903 fan-3: 813 fan-4: 0 fan-5: 776 gpu: nvidia fan: 28%
Power: 12v: N/A 5v: N/A 3.3v: N/A vbat: 3.22
Info: Processes: 352 Uptime: 10m wakeups: 7 Memory: 15.64 GiB used: 4.83 GiB (30.9%) Init: systemd v: 247 Compilers:
gcc: 10.2.0 Packages: pacman: 1240 lib: 290 Shell: fish v: 3.1.2 running in: yakuake inxi: 3.2.02

Sorry guys I have yet to learn to post to PrivateBin, I'd prefer that for sure, I think I need to install something to get access to it. GitHub - PrivateBin/PrivateBin: A minimalist, open source online pastebin where the server has zero knowledge of pasted data. Data is encrypted/decrypted in the browser using 256 bits AES.

@tnt , ok I can try that initrd update. Let's say I succeed. In what ways would that be better than my pacman upgrade that worked no issue (nothing on the terminal showing errors) and to which I can reboot with success? I mean, if I can manually update that initrd and login graphically to my snapshot after manually installing nvidia drivers, what would be my gain compared to my other drive which did all that automatically and is booting fine?

Just trying to understand where I am going before I try something. If I do boot into that snapshot, then I'll face the same massive slow down and the /tmp/tmp.* that grubup is mounting every time. So my point is I wonder if should invest more time into manually installing/updating nvidia/initrd...

Read wiki "Reporting bugs", I edit your post. Short terminal outputs you can post here.
I admire your tenacity to solve the problem, you can become a great *Arch user :slight_smile:

*Garuda Linux :wink:

1 Like

Thank you @SGS. :slight_smile:

Wiki "Reporting bugs" will tell me how to paste longer terminal outputs? Ok nice.

That being said, I will try a full reinstall tonight on my 3rd drive (test drive) and if I do get, after a full upgrade, the same issues, then well, BIOS update and if still same issues, then well, maybe another Garuda edition. I'll do as much as I can to isolate the context in which this is happening. As of now, there is nothing clear that tells what could be causing this... nvidia, kernel, zram, Garuda package, etc... so it's sort of shooting in the dark.

I'll back up at a higher level (full fresh install) and try to use the "funnel" technique. I cannot imagine myself not running D460nized... I need it.

2 Likes

Yes and no, I mean

  • If you include terminal outputs in your post please use the proper output format in your post. Using "~" 3 times above and "~" 3 times below the text block will provide a readable, raw look.
    :wink:
1 Like

@FGD every time you update kernel and modules, the following things must happen in order:

  1. kernel and/or modules packages are unpacked on the system
  2. any additional compilation steps are performed (e.g. dkms)
  3. the initramfs (sorry! it's not initrd but initramfs, search for the correct term) is created from the kernel modules - this is a compressed image containing essential modules for use during boot.
  4. the grub configuration is updated to use the new kernel and initramfs.

Since you interrupted the update process, I am guessing several of the latter steps were interrupted and/or not performed correctly. So you need to perform them by hand. That's the direction you are going. The idea is to perform the same steps that the update was performing, but by doing them by hand you do not loose visibility and can figure out the exact point of failure.

If you do not want to go through all this and just need to use your system, you may try to repeat the update process now that the nvidia module has been installed. With that behind you, the update may succeed, but you will not learn why it failed in the first place. Your decision entirely.

2 Likes

Sorry that this happened to you. Just to let you know. I just went through this very update. It took way longer than any other update and all cores were running 100% during the install of the dkms packages. I was hesitant as I had been reading this thread before the update. I have rebooted and all is running great!

1 Like

Ok I understand @tnt

The reason why I was saying this is on my primary subvolume, which has not had any attempt to update since Sunday, I do have that weird /tmp/tmp.* mounting thing when I initiate grubup. So even my primary installation is broken somewhere.

Assuming that mounting issue has something to do with my other issues... that is just an assumption.

I need to perform more tests and gather more data.

Which yields me to think I have something else already broken on my installation, then... Thank you, you're the 2nd one confirming it worked.

Just out of curiosity, if you grubup, do you see at the end something similar to

umount: /tmp/tmp.cVm8VJ9MLC: target is busy.

?

grubup
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/garuda/theme.txt
Found linux image: /boot/vmlinuz-linux-tkg-pds-skylake
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-tkg-pds-skylake.img
Found fallback initrd image(s) in /boot: initramfs-linux-tkg-pds-skylake-fallback.img
Found linux image: /boot/vmlinuz-linux-lts-tkg-pds
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-lts-tkg-pds.img
Found fallback initrd image(s) in /boot: initramfs-linux-lts-tkg-pds-fallback.img
Found Windows Boot Manager on /dev/[email protected]/EFI/Microsoft/Boot/bootmgfw.efi
Detecting snapshots ...
Info: Separate boot partition not detected
Found snapshot: 2021-02-02 15:37:14 | timeshift-btrfs/snapshots/2021-02-02_15-37-14/@
Found snapshot: 2021-02-02 15:00:01 | timeshift-btrfs/snapshots/2021-02-02_15-00-01/@
Found snapshot: 2021-02-02 14:00:01 | timeshift-btrfs/snapshots/2021-02-02_14-00-01/@
Found snapshot: 2021-02-02 13:00:01 | timeshift-btrfs/snapshots/2021-02-02_13-00-01/@
Found snapshot: 2021-02-02 12:00:01 | timeshift-btrfs/snapshots/2021-02-02_12-00-01/@
Found snapshot: 2021-02-01 12:42:39 | timeshift-btrfs/snapshots/2021-02-01_12-42-39/@
Found snapshot: 2021-02-01 12:20:25 | timeshift-btrfs/snapshots/2021-02-01_12-20-25/@
Found snapshot: 2021-02-01 09:27:44 | timeshift-btrfs/snapshots/2021-02-01_09-27-44/@
Found snapshot: 2021-02-01 09:00:02 | timeshift-btrfs/snapshots/2021-02-01_09-00-02/@
Found snapshot: 2021-01-29 08:36:28 | timeshift-btrfs/snapshots/2021-01-29_08-36-28/@
umount: /tmp/tmp.nhqW9wmhao: target is busy.

@waeking Holly ****!!! loll Ok so as Dragon mentioned it may be related to grub-btrfs. I have to advise Antynea, he is not aware as of this morning.

I cannot ask you to try to compile a custom kernel and see if it your machine almost freezes, but yeah I have good hopes now.

I know what to do next... many things to try, tnx for all the ideas, time to get to Garuda-work. :slight_smile:

I just downgraded and upgraded my grub acording to dr460nf1r3. All is well and there were not errors. No umounts. I think using grubup is a bad idea.

1 Like

You mean grub-btrfs?

No, grub-btrfs is needed.

We use sudo update-grub. My first time I read about that grubup :smiley: