dolphin_oracle's respins (updated June 23, 2024)
- dolphin_oracle
- Developer
- Posts: 22245
- Joined: Sun Dec 16, 2007 12:17 pm
Re: dolphin_oracle's respins (updated June 23, 2024)
Updated 23.4 systemd-only respin is up. Link in first post.
the sysvinit-only spin might get updated, I haven't decided yet.
the sysvinit-only spin might get updated, I haven't decided yet.
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.
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
- a_freed_man
- Posts: 160
- Joined: Tue Nov 03, 2020 11:25 am
os-prober fails to detect Windows
I hate to admit it, but I'm trying to setup a dual boot system with MX and Windows 10 and MX doesn't detect Windows.
I'm using Dolphin's systemd only respin, which I know from previous posts has a few things omitted. However, it does have the os-prober script. There are comments in grub.cfg for it but nothing in between. I ran os-prober from the command line and it prints a single line with Windows 10 ESP:
It was a real PITA getting both op systems installed to dual boot. I used to do it all the time but frankly it's been many years since I have (Windows 7 days) and it was much easier then. gparted's resize corrupted the Windows partition so had to start over after many attempts to fix the install failed.
Now I can boot either OS if I use the BIOS hot key to select what to boot, but grub is not the default boot loader and if it is selected from the BIOS menu it doesn't include Windows as I expected.
So how can this be resolved? I want grup to be the default boot loader with an entry for the Windows boot manager.
ANSWER: edit /etc/default/grub and uncomment this line: GRUB_DISABLE_OS_PROBER=false and run sudo update-grub. That gets the Wndows menu entry added to the grub menu. To get grub the default boot loader probably requires BCDEdit or interacting with Windows to set Windows Boot Manager options.
Another issue I have is when I run MX updater it can't rebuild modules for the 2 kernel versions installed, one of which doesn't even show up in the mx package installer:
I don't see a way to only install kernel hearders so compiles can succeed, aside from installing specific kernel versions. When I install kernel 6.5.0.1 from the package manager it complains when it tries to [also] rebuild 6.1 modules.
So what should I do to resolve that issue? I would be OK with removing the 6.1 kernel, but the package manager doesn't show it as installed (nor did it show the running 6.5 kernel as installed either, until I ran the mx updater).
I'm using Dolphin's systemd only respin, which I know from previous posts has a few things omitted. However, it does have the os-prober script. There are comments in grub.cfg for it but nothing in between. I ran os-prober from the command line and it prints a single line with Windows 10 ESP:
Code: Select all
/dev/nvme0n1p2@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
Now I can boot either OS if I use the BIOS hot key to select what to boot, but grub is not the default boot loader and if it is selected from the BIOS menu it doesn't include Windows as I expected.
So how can this be resolved? I want grup to be the default boot loader with an entry for the Windows boot manager.
ANSWER: edit /etc/default/grub and uncomment this line: GRUB_DISABLE_OS_PROBER=false and run sudo update-grub. That gets the Wndows menu entry added to the grub menu. To get grub the default boot loader probably requires BCDEdit or interacting with Windows to set Windows Boot Manager options.
Another issue I have is when I run MX updater it can't rebuild modules for the 2 kernel versions installed, one of which doesn't even show up in the mx package installer:
Code: Select all
Error! Your kernel headers for kernel 6.1.0-28-amd64 cannot be found at /lib/modules/6.1.0-28-amd64/build
or /lib/modules/6.1.0-28-amd64/source.
Please install the linux-headers-6.1.0-28-amd64 package or use the --kernelsourcedir option to tell DKMS
where it's located.
So what should I do to resolve that issue? I would be OK with removing the 6.1 kernel, but the package manager doesn't show it as installed (nor did it show the running 6.5 kernel as installed either, until I ran the mx updater).
Code: Select all
Snapshot created on: 20231002_0747
System:
Kernel: 6.5.0-1mx-ahs-amd64 [6.5.3-1~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1mx-ahs-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-systemd-only-respin October 02 2023 base: Debian
GNU/Linux 12 (bookworm)
Machine:
Type: Desktop Mobo: MSI model: B250M BAZOOKA (MS-7A70) v: 1.0 serial: <superuser required>
UEFI: American Megatrends v: 1.70 date: 07/03/2018
CPU:
Info: model: Intel Core i5-7400 bits: 64 type: MCP arch: Kaby Lake gen: core 7 level: v3
note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 9
microcode: 0xF8
Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB
L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB
Speed (MHz): avg: 3300 min/max: 800/3500 scaling: driver: intel_pstate governor: powersave
cores: 1: 3300 2: 3300 3: 3300 4: 3300 bogomips: 24000
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling mitigation: Microcode
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
Type: mds mitigation: Clear CPU buffers; SMT disabled
Type: meltdown mitigation: PTI
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled
Type: retbleed mitigation: IBRS
Type: spec_rstack_overflow status: Not affected
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: IBRS, IBPB: conditional, STIBP: disabled, RSB filling,
PBRSB-eIBRS: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel HD Graphics 630 vendor: Micro-Star MSI driver: i915 v: kernel arch: Gen-9.5
process: Intel 14nm built: 2016-20 ports: active: HDMI-A-1 empty: DP-1,HDMI-A-2,HDMI-A-3
bus-ID: 00:02.0 chip-ID: 8086:5912 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 423x238mm (16.65x9.37") s-diag: 485mm (19.11")
Monitor-1: HDMI-A-1 mapped: HDMI-1 model: LG (GoldStar) 32 FHD serial: <filter> built: 2017
res: 1600x900 hz: 60 dpi: 58 gamma: 1.2 size: 698x392mm (27.48x15.43") diag: 801mm (31.5")
ratio: 16:9 modes: max: 1920x1080 min: 640x480
API: OpenGL v: 4.6 Mesa 24.2.8-1mx23ahs renderer: Mesa Intel HD Graphics 630 (KBL GT2)
direct-render: Yes
Audio:
Device-1: Intel 200 Series PCH HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
bus-ID: 00:1f.3 chip-ID: 8086:a2f0 class-ID: 0403
API: ALSA v: k6.5.0-1mx-ahs-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: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 02:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
IF-ID-1: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
Drives:
Local Storage: total: 465.76 GiB used: 57.08 GiB (12.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 960 EVO 500GB size: 465.76 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 2B7QCXE7 temp: 36.9 C scheme: GPT
Partition:
ID-1: / raw-size: 78.12 GiB size: 76.35 GiB (97.73%) used: 17.06 GiB (22.3%) fs: ext4
dev: /dev/nvme0n1p6 maj-min: 259:6
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%) used: 25.6 MiB (26.7%) fs: vfat
dev: /dev/nvme0n1p2 maj-min: 259:2
ID-3: /home raw-size: 223.3 GiB size: 218.74 GiB (97.96%) used: 5.77 GiB (2.6%) fs: ext4
dev: /dev/nvme0n1p7 maj-min: 259:7
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 16.6 GiB used: 256 KiB (0.0%) priority: -2
dev: /dev/nvme0n1p5 maj-min: 259:5
Sensors:
System Temperatures: cpu: 47.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: 2507 pm: dpkg pkgs: 2492 libs: 1317 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
pkgs: 0 pm: flatpak pkgs: 15
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
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 non-free-firmware
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 non-free-firmware
3: deb http://deb.debian.org/debian/ bookworm-backports main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/librewolf.list
1: deb [arch=amd64] http://deb.librewolf.net/ bookworm main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm ahs
Active apt repos in: /etc/apt/sources.list.d/tailscale.list
1: deb [signed-by=/usr/share/keyrings/tailscale-archive-keyring.gpg] https://pkgs.tailscale.com/stable/debian bookworm main
Active apt repos in: /etc/apt/sources.list.d/vscodium.list
1: deb [ signed-by=/usr/share/keyrings/vscodium-archive-keyring.gpg ] https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs/ vscodium main
Info:
Processes: 296 Uptime: 29m wakeups: 1 Memory: 7.65 GiB used: 2.31 GiB (30.2%) Init: systemd
v: 252 target: graphical (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: UEFI
- dolphin_oracle
- Developer
- Posts: 22245
- Joined: Sun Dec 16, 2007 12:17 pm
Re: dolphin_oracle's respins (updated June 23, 2024)
the headers for the 6.1.0-28 kernel are still in repo.
should do it.
it may be that the 6.1 kenrel is partially installed. removing the 6.1 kernel would do it if you aren't using it.
Code: Select all
sudo apt install linux-headers-6.1.0-28-amd64
it may be that the 6.1 kenrel is partially installed. removing the 6.1 kernel would do it if you aren't using it.
Code: Select all
sudo apt purge linux-image-6.1.0-28-amd64
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.
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
- a_freed_man
- Posts: 160
- Joined: Tue Nov 03, 2020 11:25 am
Re: dolphin_oracle's respins (updated June 23, 2024)
Thanx, that cleaned things up nicely.
- a_freed_man
- Posts: 160
- Joined: Tue Nov 03, 2020 11:25 am
Re: dolphin_oracle's respins (updated June 23, 2024)
However, when I ran the update today it still wants the 6.1 kernel headers, despite purging 6.1 from my system. I ran the update-initram -U (iirc the name of the cmd to do that) so it wasn't in the initram or in /boot. What else might be bring in a dependency of an old kernel version? 6.1 isn't even listed in the mx-package installer, and the only 1 I have selected there and configured to boot is 6.5.10.
I believe the solution is that there were references in /lib/modules/6.1.0-* causing packages to remain.
An apt-get autoremove AND an rm -rf /lib/modules/6.1.0-* appears to have resolved the problem, but until the next update is required I am not sure. Odd thing is the fill color of the open box update icon in the task bar disappeared when I ran the autoremove and rm -rf, but clicking that icon now runs the Synaptic package manager which I don't recall it doing before. May be b/c I only clicked it when updates were available?
No builds or references to 6.1.0* kernel headers were needed in the updates I just did, so the autoremove AND an rm -rf /lib/modules/6.1.0-* has indeed resolved the problem.
I believe the solution is that there were references in /lib/modules/6.1.0-* causing packages to remain.
An apt-get autoremove AND an rm -rf /lib/modules/6.1.0-* appears to have resolved the problem, but until the next update is required I am not sure. Odd thing is the fill color of the open box update icon in the task bar disappeared when I ran the autoremove and rm -rf, but clicking that icon now runs the Synaptic package manager which I don't recall it doing before. May be b/c I only clicked it when updates were available?
No builds or references to 6.1.0* kernel headers were needed in the updates I just did, so the autoremove AND an rm -rf /lib/modules/6.1.0-* has indeed resolved the problem.
- a_freed_man
- Posts: 160
- Joined: Tue Nov 03, 2020 11:25 am
Re: dolphin_oracle's respins (updated June 23, 2024)
I'm using a brand new i9 system today, and having difficulties getting the nvidia drivers loaded. Here's my current QSI:
I first tried to use the latest 6.5 kernel and the 5.3.5 nvidia drivers from Debian backports. That failed after several attempts, now I've purged the 6.5 from the system b/c every time I tried to do an update it continued to attempt to build dkms modules for 6.5 kernel but complained there were no headers installed, yet there were.
Seems I'm now seeing same thing for 6.1 headers.
The MX Package Installer says:
# lsmod | grep -i nouveau
# lsmod | grep -i nvidia
Both return nothing. Hhowever if you look at the QSI you will see the nouveau driver in the Graphics section, depite there being at least 2 files in /etc/modules.d/ to blacklist it, possibly b/c of an issue with Debian 535 nvidia driver?
I may try to install the packages I downloaded directly from nvidia for v550 and 570, but I need to uninstall the Debian 535 drivers first as .run scripts from nvidia fail unless I do. It also highly suggests I use the Debian drivers, so am exhausting my options with that approach first.
Why the dkms fails to build or find the headers for whatever kernel version I am using seems odd to me, especially with the default kernel which I installed from MX Pkg Mgr.
UPDATE:
/etc/modules-load.d/nvidia.conf--> /etc/alternatives/glx--nvidia-load.conf
Code: Select all
Snapshot created on: 20231002_0747
System:
Kernel: 6.1.0-33-amd64 [6.1.133-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/vmlinuz-6.1.0-33-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-systemd-only-respin October 02 2023 base: Debian
GNU/Linux 12 (bookworm)
Machine:
Type: Desktop System: CyberPowerPC product: GamingPC v: -CF serial: <superuser required>
Mobo: Gigabyte model: B760M C V2 v: x.x serial: <superuser required> UEFI: American Megatrends
LLC. v: F4 date: 09/27/2024
CPU:
Info: model: Intel Core i9-14900F bits: 64 type: MST AMCP arch: Raptor Lake gen: core 14
level: v3 note: check built: 2022+ process: Intel 7 (10nm) family: 6 model-id: 0xB7 (183)
stepping: 1 microcode: 0x12C
Topology: cpus: 1x cores: 24 mt: 8 tpc: 2 st: 16 threads: 32 smt: enabled cache: L1: 2.1 MiB
desc: d-16x32 KiB, 8x48 KiB; i-8x32 KiB, 16x64 KiB L2: 32 MiB desc: 8x2 MiB, 4x4 MiB L3: 36 MiB
desc: 1x36 MiB
Speed (MHz): avg: 808 high: 1062 min/max: 800/5500:5800:4300 scaling: driver: intel_pstate
governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 1062 6: 800 7: 800 8: 800 9: 800
10: 800 11: 800 12: 800 13: 800 14: 800 15: 800 16: 800 17: 800 18: 800 19: 800 20: 800 21: 800
22: 800 23: 800 24: 800 25: 800 26: 800 27: 800 28: 800 29: 800 30: 800 31: 800 32: 800
bogomips: 127795
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
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: reg_file_data_sampling mitigation: Clear Register File
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Not affected
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: Enhanced / Automatic IBRS; IBPB: conditional; RSB filling;
PBRSB-eIBRS: SW sequence; BHI: BHI_DIS_S
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GB203 [GeForce RTX 5070 Ti] vendor: Micro-Star MSI driver: N/A alternate: nvidia
non-free: N/A status: unknown device ID pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 5
speed: 32 GT/s bus-ID: 01:00.0 chip-ID: 10de:2c05 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
loaded: nouveau,vesa unloaded: fbdev,modesetting alternate: nv dri: swrast gpu: N/A
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: default res: 1920x1080 hz: 77 size: N/A modes: N/A
API: OpenGL v: 4.5 Mesa 24.2.8-1mx23ahs renderer: llvmpipe (LLVM 15.0.6 256 bits)
direct-render: Yes
Audio:
Device-1: Intel Raptor Lake High Definition Audio vendor: Gigabyte driver: snd_hda_intel
v: kernel alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:7a50 class-ID: 0403
Device-2: NVIDIA driver: snd_hda_intel v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16
link-max: gen: 5 speed: 32 GT/s bus-ID: 01:00.1 chip-ID: 10de:22e9 class-ID: 0403
API: ALSA v: k6.1.0-33-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: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet vendor: Gigabyte
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 4000 bus-ID: 04:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Realtek driver: N/A pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 05:00.0
chip-ID: 10ec:b851 class-ID: 0280
IF-ID-1: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
Bluetooth:
Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 1-14:7
chip-ID: 0bda:b850 class-ID: e001 serial: <filter>
Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block:
hardware: no software: yes address: <filter>
Info: acl-mtu: 0:0 sco-mtu: 0:0 link-mode: peripheral accept
Drives:
Local Storage: total: 1.82 TiB used: 22.81 GiB (1.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: A-Data model: LEGEND 800 GOLD size: 1.82 TiB
block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 1.2.P.45 temp: 49.9 C scheme: GPT
Partition:
ID-1: / raw-size: 102.54 GiB size: 100.37 GiB (97.88%) used: 16.26 GiB (16.2%) fs: ext4
dev: /dev/nvme0n1p4 maj-min: 259:4
ID-2: /boot raw-size: 1.07 GiB size: 1.02 GiB (95.27%) used: 104.7 MiB (10.0%) fs: ext4
dev: /dev/nvme0n1p2 maj-min: 259:2
ID-3: /boot/efi raw-size: 100 MiB size: 98.4 MiB (98.45%) used: 274 KiB (0.3%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:1
ID-4: /home raw-size: 1.7 TiB size: 1.67 TiB (98.37%) used: 6.44 GiB (0.4%) fs: ext4
dev: /dev/nvme0n1p5 maj-min: 259:5
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 16.11 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
System Temperatures: cpu: 38.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: 2565 pm: dpkg pkgs: 2550 libs: 1343 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
pkgs: 0 pm: flatpak pkgs: 15
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
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 non-free-firmware
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 non-free-firmware
3: deb http://deb.debian.org/debian/ bookworm-backports main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/librewolf.list
1: deb [arch=amd64] http://deb.librewolf.net/ bookworm main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bookworm ahs
Active apt repos in: /etc/apt/sources.list.d/tailscale.list
1: deb [signed-by=/usr/share/keyrings/tailscale-archive-keyring.gpg] https://pkgs.tailscale.com/stable/debian bookworm main
Active apt repos in: /etc/apt/sources.list.d/vscodium.list
1: deb [ signed-by=/usr/share/keyrings/vscodium-archive-keyring.gpg ] https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs/ vscodium main
Info:
Processes: 493 Uptime: 11m wakeups: 0 Memory: 31.18 GiB used: 2.28 GiB (7.3%) Init: systemd
v: 252 target: graphical (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: UEFI
Seems I'm now seeing same thing for 6.1 headers.
The MX Package Installer says:
Code: Select all
Module build for kernel 6.1.0-33-amd64 was skipped since the
kernel headers for this kernel do not seem to be installed.
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.
# lsmod | grep -i nvidia
Both return nothing. Hhowever if you look at the QSI you will see the nouveau driver in the Graphics section, depite there being at least 2 files in /etc/modules.d/ to blacklist it, possibly b/c of an issue with Debian 535 nvidia driver?
I may try to install the packages I downloaded directly from nvidia for v550 and 570, but I need to uninstall the Debian 535 drivers first as .run scripts from nvidia fail unless I do. It also highly suggests I use the Debian drivers, so am exhausting my options with that approach first.
Why the dkms fails to build or find the headers for whatever kernel version I am using seems odd to me, especially with the default kernel which I installed from MX Pkg Mgr.
UPDATE:
/etc/modules-load.d/nvidia.conf--> /etc/alternatives/glx--nvidia-load.conf
Code: Select all
# ls -ls /etc/alternatives/glx
glx/ glx--libglxserver_nvidia.so
glx--libEGL.so.1-x86_64-linux-gnu glx--libnvidia-cfg.so.1-x86_64-linux-gnu
glx--libEGL.so-x86_64-linux-gnu glx--nvidia-blacklists-nouveau.conf
glx--libGLESv1_CM.so.1-x86_64-linux-gnu glx--nvidia-bug-report.sh
glx--libGLESv2.so.2-x86_64-linux-gnu glx--nvidia-drm-outputclass.conf
glx--libGL.so.1-x86_64-linux-gnu glx--nvidia_drv.so
glx--libGL.so-x86_64-linux-gnu glx--nvidia-load.conf
glx--libGLX_indirect.so.0-x86_64-linux-gnu glx--nvidia-modprobe.conf
- EeyoreTheDonkey
- Posts: 1
- Joined: Thu Feb 06, 2025 7:56 pm
Re: dolphin_oracle's respins (updated June 23, 2024)
You might try purging and reinstalling dkms
- a_freed_man
- Posts: 160
- Joined: Tue Nov 03, 2020 11:25 am
Re: dolphin_oracle's respins (updated June 23, 2024)
That failed miserably with tons of errors. I am winning to try such drastic suggestions b/c I can restore from a backup, which is probably necessary after this.
Code: Select all
The following packages were automatically installed and are no longer required:
libcudadebugger1 libegl-nvidia0 libgles-nvidia1 libgles-nvidia2 libgles1 libnvidia-allocator1
libnvidia-api1 libnvidia-egl-wayland1 libnvidia-fbc1 libnvidia-ngx1 libnvidia-opticalflow1
libnvoptix1 nvidia-driver-bin nvidia-driver-libs nvidia-egl-common nvidia-egl-icd nvidia-powerd
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
broadcom-sta-dkms* dkms* nvidia-driver* nvidia-driver-full* nvidia-kernel-dkms* rtl8812au-dkms*
rtl8821ce-dkms* rtl8821cu-dkms*
0 upgraded, 0 newly installed, 8 to remove and 0 not upgraded.
After this operation, 189 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 391751 files and directories currently installed.)
Removing broadcom-sta-dkms (6.30.223.271-26~mx23ahs) ...
/usr/sbin/dkms.mx remove -m broadcom-sta -v 6.30.223.271 --all
Module broadcom-sta-6.30.223.271 for kernel 6.1.0-33-amd64 (x86_64).
Before uninstall, this module version was ACTIVE on this kernel.
wl.ko:
- Uninstallation
- Module was not found within /lib/modules/6.1.0-33-amd64/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod...
Deleting module broadcom-sta-6.30.223.271 completely from the DKMS tree.
Removing rtl8821ce-dkms (5.5.2.1+git20240526-0~mx23) ...
grep: /lib/modules/6.1.0-33-amd64/build/.config: No such file or directory
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)
/usr/sbin/dkms.mx remove -m rtl8821ce -v 5.5.2.1+git20240526 --all
grep: /lib/modules/6.1.0-33-amd64/build/.config: No such file or directory
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)
grep: /lib/modules/6.1.0-33-amd64/build/.config: No such file or directory
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20240526/source/dkms.conf)
Module rtl8821ce-5.5.2.1+git20240526 for kernel 6.1.0-33-amd64 (x86_64).
Before uninstall, this module version was ACTIVE on this kernel.
rtl8821ce.ko:
- Uninstallation
- Module was not found within /lib/modules/6.1.0-33-amd64/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod...
Deleting module rtl8821ce-5.5.2.1+git20240526 completely from the DKMS tree.
Removing rtl8821cu-dkms (5.12.0+git20230215-1~mx23+3) ...
/usr/sbin/dkms.mx remove -m rtl8821cu -v 5.12.0 --all
Error! The module/version combo: rtl8821cu-5.12.0 is not located in the DKMS tree.
dpkg: error processing package rtl8821cu-dkms (--remove):
installed rtl8821cu-dkms package pre-removal script subprocess returned error exit status 3
dpkg: too many errors, stopping
Errors were encountered while processing:
rtl8821cu-dkms
Processing was halted because there were too many errors.
- dolphin_oracle
- Developer
- Posts: 22245
- Joined: Sun Dec 16, 2007 12:17 pm
Re: dolphin_oracle's respins (updated June 23, 2024)
lets check a few things just to cover the bases
Code: Select all
apt policy linux-image-6.1.0-33-amd64
apt policy linux-headers-6.1.0-33-amd64
apt policy mx-system
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.
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
- a_freed_man
- Posts: 160
- Joined: Tue Nov 03, 2020 11:25 am
Re: dolphin_oracle's respins (updated June 23, 2024)
I managed to get Nvidia driver version 5.7.0 installed and working after a 12 hr session of troubleshooting / investigation with the help of chatGPT. The build / install of that driver (which I obtained directly from Nvidia; I'll have to review but IIRC I chose the open, not proprietary version) succeeded EXCEPT the dkms portions. That took place under kernel version 6.1.0.28. Today without thinking I updated, which required ~213 packages. It updated the kernel to 6.1.0.33. I have not yet rebooted.
I spent most of yesterday trying to build/install Nvidia driver version 5.5.0 after giving up trying to make the 5.3.5 version from Debian backports work. One of the major frustrations that took much time to resolve, was how to fully blacklist nouveau from the initramfs image. chatGPT took 2 tries to get a hook script right that finally accomplished that. Even with the -Z and other options for the Nvidia .run script, that script always failed and inspecting the initramfs showed nouveau still present, even after several attempts to blacklist it.
Once the hooks script was working and nouveau.ko was removed from initramfs, the Nvidia 5.5.0 script should have worked, but it didn't!
I decided since my GPU was the latest generation driver v5.5.0 might not be adequate, so I ran the 5.7.0 Nvidia script which succeeded, except for DKMS. At least the driver was installed and nvidia-smi was happy.
Now it's a matter of figuring out why the DKMS build fails.
-- END OF BACKSTORY --
Dolphin, here is the answer to your policy questions for the current -33 and previous -28 kernels:
I spent most of yesterday trying to build/install Nvidia driver version 5.5.0 after giving up trying to make the 5.3.5 version from Debian backports work. One of the major frustrations that took much time to resolve, was how to fully blacklist nouveau from the initramfs image. chatGPT took 2 tries to get a hook script right that finally accomplished that. Even with the -Z and other options for the Nvidia .run script, that script always failed and inspecting the initramfs showed nouveau still present, even after several attempts to blacklist it.
Once the hooks script was working and nouveau.ko was removed from initramfs, the Nvidia 5.5.0 script should have worked, but it didn't!
I decided since my GPU was the latest generation driver v5.5.0 might not be adequate, so I ran the 5.7.0 Nvidia script which succeeded, except for DKMS. At least the driver was installed and nvidia-smi was happy.
Now it's a matter of figuring out why the DKMS build fails.
-- END OF BACKSTORY --
Dolphin, here is the answer to your policy questions for the current -33 and previous -28 kernels:
Code: Select all
# apt policy linux-image-6.1.0-33-amd64
linux-image-6.1.0-33-amd64:
Installed: 6.1.133-1
Candidate: 6.1.133-1
Version table:
*** 6.1.133-1 500
500 http://security.debian.org/debian-security bookworm-security/main amd64 Packages
100 /var/lib/dpkg/status
# apt policy linux-headers-6.1.0-33-amd64
linux-headers-6.1.0-33-amd64:
Installed: 6.1.133-1
Candidate: 6.1.133-1
Version table:
*** 6.1.133-1 500
500 http://security.debian.org/debian-security bookworm-security/main amd64 Packages
100 /var/lib/dpkg/status
# apt policy mx-system
mx-system:
Installed: 23.10.02mx23
Candidate: 23.10.02mx23
Version table:
*** 23.10.02mx23 100
100 /var/lib/dpkg/status
# apt policy linux-image-6.1.0-28-amd64
linux-image-6.1.0-28-amd64:
Installed: 6.1.119-1
Candidate: 6.1.119-1
Version table:
*** 6.1.119-1 500
500 http://security.debian.org/debian-security bookworm-security/main amd64 Packages
100 /var/lib/dpkg/status
# apt policy linux-headers-6.1.0-28-amd64
linux-headers-6.1.0-28-amd64:
Installed: 6.1.119-1
Candidate: 6.1.119-1
Version table:
*** 6.1.119-1 500
500 http://security.debian.org/debian-security bookworm-security/main amd64 Packages
100 /var/lib/dpkg/status