Question about ahs  [Solved]

Message
Author
NewLinuxBro
Posts: 6
Joined: Thu Mar 20, 2025 4:04 pm

Question about ahs

#1 Post by NewLinuxBro »

Hi everyone, new user to Linux and MX. I've been on MX for about a month now and my experience has been really good with it so far. I just had a question though if it would be better for me to be on the ahs version instead of the default version given my gpu is a RTX2080 for newer nvidia drivers, and if so do I need to do a new install with the i ahs so or can I do that from my current version?

Code: Select all

System:
  Kernel: 6.1.0-32-amd64 [6.1.129-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-32-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7
    dm: LightDM v: 1.32.0 Distro: MX-23.5_x64 Libretto Jan 12  2025 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop System: Gigabyte product: Z390 AORUS PRO WIFI v: N/A serial: <superuser required>
  Mobo: Gigabyte model: Z390 AORUS PRO WIFI-CF v: x.x serial: <superuser required>
    UEFI-[Legacy]: American Megatrends v: F7 date: 12/04/2018
Battery:
  Device-1: ps-controller-battery-4c:b9:9b:1c:25:e2 model: N/A serial: N/A charge: N/A
    status: charging
CPU:
  Info: model: Intel Core i5-9600K bits: 64 type: MCP arch: Coffee Lake gen: core 9 level: v3
    note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 0xC (12)
    microcode: 0xF8
  Topology: cpus: 1x cores: 6 smt: <unsupported> cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB
    L2: 1.5 MiB desc: 6x256 KiB L3: 9 MiB desc: 1x9 MiB
  Speed (MHz): avg: 800 min/max: 800/4600 scaling: driver: intel_pstate governor: powersave
    cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 bogomips: 44398
  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 status: Not affected
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown status: Not affected
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled
  Type: reg_file_data_sampling status: Not affected
  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; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: NVIDIA TU104 [GeForce RTX 2080 Rev. A] vendor: Gigabyte driver: nvidia v: 535.216.01
    non-free: 530.xx+ status: current (as of 2023-03) arch: Turing code: TUxxx process: TSMC 12nm FF
    built: 2018-22 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:1e87
    class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.20.0 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa alternate: nv gpu: nvidia display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 6400x1440 s-dpi: 96 s-size: 1694x382mm (66.69x15.04")
    s-diag: 1737mm (68.37")
  Monitor-1: DP-2 pos: primary,top-center res: 2560x1440 dpi: 109 size: 598x336mm (23.54x13.23")
    diag: 686mm (27.01") modes: N/A
  Monitor-2: DP-4 pos: bottom-r res: 1920x1080 hz: 60 dpi: 92 size: 531x299mm (20.91x11.77")
    diag: 609mm (23.99") modes: N/A
  Monitor-3: HDMI-0 pos: bottom-l res: 1920x1080 hz: 60 dpi: 119 size: 410x230mm (16.14x9.06")
    diag: 470mm (18.51") modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 535.216.01 renderer: NVIDIA GeForce RTX 2080/PCIe/SSE2
    direct-render: Yes
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Gigabyte driver: snd_hda_intel v: kernel
    bus-ID: 1-13.4:11 alternate: snd_soc_skl,snd_sof_pci_intel_cnl chip-ID: 8888:1234 class-ID: 0300
    bus-ID: 00:1f.3 chip-ID: 8086:a348 serial: <filter> class-ID: 0403
  Device-2: NVIDIA TU104 HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:10f8 class-ID: 0403
  Device-3: CMTECK type: USB driver: snd-usb-audio
  Device-4: Sony DualSense wireless controller (PS5) type: USB
    driver: playstation,snd-usb-audio,usbhid bus-ID: 1-6:3 chip-ID: 054c:0ce6 class-ID: 0300
  API: ALSA v: k6.1.0-32-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 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 Cannon Lake PCH CNVi WiFi driver: iwlwifi v: kernel modules: wl bus-ID: 00:14.3
    chip-ID: 8086:a370 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  Device-2: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: kernel port: N/A
    bus-ID: 00:1f.6 chip-ID: 8086:15bc class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-3: Sony DualSense wireless controller (PS5) type: USB
    driver: playstation,snd-usb-audio,usbhid bus-ID: 1-6:3 chip-ID: 054c:0ce6 class-ID: 0300
Bluetooth:
  Device-1: Broadcom BCM20702A0 Bluetooth 4.0 type: USB driver: btusb v: 0.8 bus-ID: 1-13.2:10
    chip-ID: 0a5c:21e8 class-ID: fe01 serial: <filter>
  Report: hciconfig ID: hci1 rfk-id: 2 state: up address: <filter> bt-v: 2.1 lmp-v: 4.1
    sub-v: 220e hci-v: 4.1 rev: 16e4
  Info: acl-mtu: 1021:8 sco-mtu: 64:1 link-policy: rswitch sniff link-mode: peripheral accept
    service-classes: rendering, capturing, object transfer, audio, telephony
  Device-2: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) type: USB driver: btusb v: 0.8
    bus-ID: 1-14:8 chip-ID: 8087:0aaa class-ID: e001
  Report: ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 3.0 lmp-v: 5.1 sub-v: 100
    hci-v: 5.1 rev: 100
  Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
    service-classes: rendering, capturing, object transfer, audio, telephony
Drives:
  Local Storage: total: 2.96 TiB used: 154.36 GiB (5.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000DM003-1CH162 size: 931.51 GiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: CC47 scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: CC43 scheme: MBR
  ID-3: /dev/sdc maj-min: 8:32 vendor: SanDisk model: SDSSDHP256G size: 238.47 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 6RL scheme: MBR
  ID-4: /dev/sdd maj-min: 8:48 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: 2B6Q
    scheme: MBR
Partition:
  ID-1: / raw-size: 35.73 GiB size: 34.88 GiB (97.60%) used: 21.6 GiB (61.9%) fs: ext4
    dev: /dev/sdc2 maj-min: 8:34
  ID-2: /home raw-size: 202.49 GiB size: 198.25 GiB (97.91%) used: 132.76 GiB (67.0%) fs: ext4
    dev: /dev/sdc3 maj-min: 8:35
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 4 GiB used: 174.8 MiB (4.3%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 29.0 C pch: 31.0 C mobo: N/A gpu: nvidia temp: 47 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Repos:
  Packages: 2702 pm: dpkg pkgs: 2688 libs: 1500 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 14
  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 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
  Active apt repos in: /etc/apt/sources.list.d/home:strycore.list
    1: deb http://download.opensuse.org/repositories/home:/strycore/Debian_12/ /
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/winehq-bookworm.sources
    1: deb [arch=amd64 i386] https://dl.winehq.org/wine-builds/debian bookworm main
Info:
  Processes: 283 Uptime: 2h 44m wakeups: 2 Memory: 15.55 GiB used: 5.16 GiB (33.1%) 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)

User avatar
CharlesV
Global Moderator
Posts: 7628
Joined: Sun Jul 07, 2019 5:11 pm

Re: Question about ahs  [Solved]

#2 Post by CharlesV »

Welcome in!

You can just turn on the ahs repo. Go to MX Repo Manager, change to the individual sources tab and under mx list, check the third one (and in ahs) Apply, then make sure to do

Code: Select all

 sudo apt update

in a terminal window before you attempt to do any updates. You should see a bunch of updates show up, and then your all good to go.

Personally... before anything to do with the OS.. I make sure to do a timeshift so you can rollback if needed.
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!

NewLinuxBro
Posts: 6
Joined: Thu Mar 20, 2025 4:04 pm

Re: Question about ahs

#3 Post by NewLinuxBro »

I did take a timeshift before updating, thank you for the quick response!

User avatar
CharlesV
Global Moderator
Posts: 7628
Joined: Sun Jul 07, 2019 5:11 pm

Re: Question about ahs

#4 Post by CharlesV »

Glad I could help. If this resolves your question, then Please mark as solved using the check mark on the top right of the post that resolved it.
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!

User avatar
Stevo
Developer
Posts: 14711
Joined: Fri Dec 15, 2006 7:07 pm

Re: Question about ahs

#5 Post by Stevo »

We usually have the updates on DKMS drivers like Nvidia in AHS because those are required for them to build on the newer AHS kernels. If you stick with the stock Debian kernels, you can have AHS anyway, since they are backwards-compatible. Often Debian will also update Nvidia drivers in stable or their backports just for the security fixes, so those might be duplicates of some AHS packages.
MXPI = MX Package Installer
QSI = Quick System Info from menu
The MX Test repository is mostly backports; not the same as Debian testing

Post Reply

Return to “General”