Recent kernel-nvidia -Problem with the fix?

Report Bugs, Issues and non- package Requests
Forum rules
Post Reply
Message
Author
User avatar
entropyfoe
Posts: 615
Joined: Thu Apr 19, 2007 11:42 am

Recent kernel-nvidia -Problem with the fix?

#1 Post by entropyfoe »

I have my daily work station, MX-23, had uptime >40 days, needed to reset some things, so I was going to reboot. Without thinking too much, I thought, why not do a synaptic upgrade, get all the latest goodies.
I did that, and rebooted to the black screen with the cursor.

So, today, I went to the forum, and saw bitjams, fix. So I booted out of my alternate partition, to the cursor, and did ALT F2, at the terminal typed the sudo dpkg-reconfigure nvidia-kernel-dkms

but got the error I don't have nvidia-kernel-dkms. So I did sudo apt-get install, said 5 newly installed...need to get 89.3 MB of archives, after this 137MB of additional disk space will be needed
E You don't have enough free disk space in var/cache/apt/archives/.

Now I an stuck, how to get around not having the reconfigure installed. I have options, see the below QSI. I am writing this from my p4, a testing MX23 partition, which sits next to the daily driver install p1=/, p2=swap, p3-/home.

So, I can see that root partition of the daily driver, and make changes.
My other thought is I can boot to a Live session USB. Can I run some type of repair on the daily driver's root partition p1 which is /
Or is there a way to roll back the kernel upgrade to the previous kernel?
What great MX tools can I resolve this?

Code: Select all

System:
  Kernel: 6.1.0-12-amd64 [6.1.52-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-12-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23_x64 Libretto July 24  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME X470-PRO v: Rev X.0x serial: <superuser required>
    UEFI-[Legacy]: American Megatrends v: 5204 date: 07/29/2019
CPU:
  Info: model: AMD Ryzen 5 3600X bits: 64 type: MT MCP arch: Zen 2 gen: 3 level: v3 note: check
    built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23) model-id: 0x71 (113) stepping: 0
    microcode: 0x8701013
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache: L1: 384 KiB
    desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB L3: 32 MiB desc: 2x16 MiB
  Speed (MHz): avg: 2198 high: 2200 min/max: 2200/4409 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 2200 2: 2194 3: 2200 4: 2200 5: 2197 6: 2200
    7: 2200 8: 2200 9: 2196 10: 2200 11: 2200 12: 2197 bogomips: 91033
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP protection
  Type: spec_rstack_overflow mitigation: safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP: always-on, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GK208B [GeForce GT 710] vendor: Micro-Star MSI driver: nvidia v: 470.199.02
    non-free: series: 470.xx+ status: legacy-active (EOL~2023/24) arch: Fermi 2 code: GF119/GK208
    process: TSMC 28nm built: 2010-16 pcie: gen: 2 speed: 5 GT/s lanes: 8 bus-ID: 09:00.0
    chip-ID: 10de:128b class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: nvidia
    gpu: nvidia display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.00x11.26") s-diag: 583mm (22.95")
  Monitor-1: HDMI-0 res: 1920x1080 hz: 60 dpi: 96 size: 509x286mm (20.04x11.26")
    diag: 584mm (22.99") modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 470.199.02 renderer: NVIDIA GeForce GT 710/PCIe/SSE2
    direct-render: Yes
Audio:
  Device-1: NVIDIA GK208 HDMI/DP Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie:
    gen: 2 speed: 5 GT/s lanes: 8 bus-ID: 09:00.1 chip-ID: 10de:0e0f class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0b:00.4 chip-ID: 1022:1487 class-ID: 0403
  API: ALSA v: k6.1.0-12-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 07:00.0 chip-ID: 8086:1539 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 1.25 TiB used: 678.65 GiB (52.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO Plus 250GB
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: 2B2QEXM7 temp: 34.9 C scheme: MBR
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 1B6Q scheme: MBR
  ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 840 PRO Series size: 119.24 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 5B0Q
    scheme: MBR
Partition:
  ID-1: / raw-size: 88.35 GiB size: 86.41 GiB (97.80%) used: 9.92 GiB (11.5%) fs: ext4
    dev: /dev/nvme0n1p4 maj-min: 259:4
Swap:
  Kernel: swappiness: 1 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 32.23 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p2 maj-min: 259:2
Sensors:
  System Temperatures: cpu: 42.0 C mobo: 30.0 C gpu: nvidia temp: 47 C
  Fan Speeds (RPM): cpu: 0 case-1: 0 case-2: 902 case-3: 786 gpu: nvidia fan: 50%
  Power: 12v: 12.16 5v: N/A 3.3v: N/A vbat: N/A
Repos:
  Packages: pm: dpkg pkgs: 2424 libs: 1341 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian/ bookworm-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security/ bookworm-security main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm main non-free
Info:
  Processes: 284 Uptime: 29m wakeups: 1 Memory: 31.26 GiB used: 1.77 GiB (5.7%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)
MX 23.5 on Asus PRIME X470-PRO
AMD Ryzen 3600X (12 threads @ 3.8 GHz)
32 Gig DDR4 3600 (Crucial CL 16)
Nvidia GeForce GT 710
Samsung 970 NVMe nvme0n1 P1-3=MX-23.5, P4=testing
Samsung 980 NVMe =1TB Data, plus 2TB WD =backups
on-board ethernet & sound
Top
User avatar
dolphin_oracle
Developer
Posts: 22248
Joined: Sun Dec 16, 2007 12:17 pm

Re: Recent kernel-nvidia -Problem with the fix?

#2 Post by dolphin_oracle »

looking at your drivers in use, the package would probably be

Code: Select all

nvidia-tesla-470-kernel-dkms
it could also be an incomplete update, so trying

Code: Select all

sudo dpkg --configure -a
should probably be first.

its odd for nvidia to go haywire without a kernel update. from the kernel you have in use, I don't see an update. Do you remember a kernel update?
Last edited by dolphin_oracle on Fri Jan 24, 2025 4:42 pm, edited 1 time in total.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Top
User avatar
Stevo
Developer
Posts: 14565
Joined: Fri Dec 15, 2006 7:07 pm

Re: Recent kernel-nvidia -Problem with the fix?

#3 Post by Stevo »

The kernel from Bookworm has had quite a few updates since 6.1.52; it's currently at 6.1.124!
MXPI = MX Package Installer
QSI = Quick System Info from menu
The MX Test repository is mostly backports; not the same as Debian testing
Top
User avatar
entropyfoe
Posts: 615
Joined: Thu Apr 19, 2007 11:42 am

Re: Recent kernel-nvidia -Problem with the fix?

#4 Post by entropyfoe »

d_o,

OK I tried the

Code: Select all

sudo dpkg --configure --a
but got an

Code: Select all

 error : need an action.
So, no progress so far.
Why would my
var/cache/apt/archives/

be too full, and why should this reconfigure be taking so many MB?
MX 23.5 on Asus PRIME X470-PRO
AMD Ryzen 3600X (12 threads @ 3.8 GHz)
32 Gig DDR4 3600 (Crucial CL 16)
Nvidia GeForce GT 710
Samsung 970 NVMe nvme0n1 P1-3=MX-23.5, P4=testing
Samsung 980 NVMe =1TB Data, plus 2TB WD =backups
on-board ethernet & sound
Top
User avatar
dolphin_oracle
Developer
Posts: 22248
Joined: Sun Dec 16, 2007 12:17 pm

Re: Recent kernel-nvidia -Problem with the fix?

#5 Post by dolphin_oracle »

Whoops

Should be -a.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Top
User avatar
entropyfoe
Posts: 615
Joined: Thu Apr 19, 2007 11:42 am

Re: Recent kernel-nvidia -Problem with the fix?

#6 Post by entropyfoe »

d_o,, thanks, even that -a did not work. But I took full advantage of my bullet proof machine. Over night I downloaded the 23.5 iso, and today I installed.

It was a 7 minute installation, then I spent another 15 minutes or so running the MX tools (nvidia installer, uip), my list of 12 things to tweak...

Now fully back where I was,, with a fresh 23.5.

ALL my data resides on a separate Data drive/partition.
When I reinstall I loose little if anything (maybe I didn't make a ff bookmarks back-up recently oh well. )

Not sure what happened in my "upgrade", but all is restored.
MX 23.5 on Asus PRIME X470-PRO
AMD Ryzen 3600X (12 threads @ 3.8 GHz)
32 Gig DDR4 3600 (Crucial CL 16)
Nvidia GeForce GT 710
Samsung 970 NVMe nvme0n1 P1-3=MX-23.5, P4=testing
Samsung 980 NVMe =1TB Data, plus 2TB WD =backups
on-board ethernet & sound
Top
User avatar
Stevo
Developer
Posts: 14565
Joined: Fri Dec 15, 2006 7:07 pm

Re: Recent kernel-nvidia -Problem with the fix?

#7 Post by Stevo »

Why would my
var/cache/apt/archives/

be too full, and why should this reconfigure be taking so many MB?
Nvidia drivers do take up a lot of space compared to the open ones.

You can use MX Cleanup to flush out caches, or "sudo apt clean" in the terminal to clean out the apt archive. MX Cleanup also can call on graphical tools that show you what's taking up the space.
MXPI = MX Package Installer
QSI = Quick System Info from menu
The MX Test repository is mostly backports; not the same as Debian testing
Top
Post Reply

Return to “Bugs and Non-Package Requests Forum”