Restore MX snapshot to different hardware? [Solved]

[shmu26]

What happens if I use the MX snapshot tool to take a snapshot of my installed system -- MX Linux 23 KDE with AHS -- and then I buy a new computer with different hardware, and restore the snapshot onto it? Does it adjust to the new hardware and use the appropriate drivers and optimize performance? Or are there certain manual adjustments I need to make? Or is the whole idea not recommended?
I am on the automatically updating liquorix kernel.

Code: Select all

[CODE]Snapshot created on: 20240716_1911
System:
  Kernel: 6.9.9-1-liquorix-amd64 [6.9-8~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable BOOT_IMAGE=/boot/vmlinuz-6.9.9-1-liquorix-amd64 root=UUID=<filter> ro
    quiet splash
  Desktop: KDE Plasma v: 5.27.5 wm: kwin_wayland vt: 8 dm: SDDM Distro: MX-23.3_x64 Libretto
    August 26 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME B365M-A v: Rev X.0x serial: <superuser required>
    UEFI: American Megatrends v: 2208 date: 07/09/2021
Battery:
  ID-1: hidpp_battery_0 charge: 95% condition: N/A volts: 4.1 min: N/A model: Logitech G903
    LIGHTSPEED Wireless Gaming Mouse w/ HERO type: N/A serial: <filter> status: discharging
CPU:
  Info: model: Intel Core i7-9700 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: 0xD (13)
    microcode: 0xFC
  Topology: cpus: 1x cores: 8 smt: <unsupported> cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB
    L2: 2 MiB desc: 8x256 KiB L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 3000 min/max: N/A cores: 1: 3000 2: 3000 3: 3000 4: 3000 5: 3000 6: 3000
    7: 3000 8: 3000 bogomips: 48000
  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: Split huge pages
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  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: Enhanced 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: Enhanced / Automatic IBRS; IBPB: conditional; RSB filling;
    PBRSB-eIBRS: SW sequence; BHI: SW loop, KVM: SW loop
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: ASUSTeK driver: i915 v: kernel
    arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: HDMI-A-1,HDMI-A-2 empty: DP-1
    bus-ID: 00:02.0 chip-ID: 8086:3e98 class-ID: 0300
  Device-2: USB C Video Adaptor type: USB driver: N/A bus-ID: 1-3.1.1:7 chip-ID: 25a4:9321
    class-ID: 1100 serial: <filter>
  Device-3: Microdia USB Live camera type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-3.4:8
    chip-ID: 0c45:636b class-ID: 0102 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_wayland
    driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 d-rect: 3840x1080
    display-ID: 0
  Monitor-1: HDMI-A-1 pos: primary,left res: 1920x1080 size: N/A modes: N/A
  Monitor-2: HDMI-A-2 pos: right res: 1920x1080 size: N/A modes: N/A
  API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
    direct-render: Yes
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK driver: snd_hda_intel bus-ID: 1-3.4:8
    v: kernel chip-ID: 0c45:636b alternate: snd_soc_avs class-ID: 0102 bus-ID: 00:1f.3
    chip-ID: 8086:a2f0 serial: <filter> class-ID: 0403
  Device-2: Microdia USB Live camera type: USB driver: snd-usb-audio,uvcvideo
  API: ALSA v: k6.9.9-1-liquorix-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: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK PRIME B450M-A
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 03:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152 bus-ID: 2-3.1:7
    chip-ID: 0bda:8153 class-ID: 0000 serial: <filter>
  IF: eth1 state: down mac: <filter>
  IF-ID-1: virbr0 state: up speed: 10000 Mbps duplex: unknown mac: <filter>
  IF-ID-2: vnet0 state: unknown speed: 10000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb v: 0.8
    bus-ID: 1-9:4 chip-ID: 0a12:0001 class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0
    sub-v: 22bb hci-v: 4.0 rev: 22bb
  Info: acl-mtu: 310:10 sco-mtu: 64:8 link-policy: rswitch hold sniff park
    link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
    telephony
Drives:
  Local Storage: total: 2.26 TiB used: 1021.27 GiB (44.2%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37480G size: 447.13 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: K1B3 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Toshiba model: HDWD120 size: 1.82 TiB block-size:
    physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: ACF0
    scheme: GPT
Partition:
  ID-1: / raw-size: 44.46 GiB size: 43.46 GiB (97.75%) used: 15.96 GiB (36.7%) fs: ext4
    dev: /dev/sda7 maj-min: 8:7
  ID-2: /boot/efi raw-size: 100 MiB size: 98.4 MiB (98.42%) used: 48.4 MiB (49.1%) fs: vfat
    dev: /dev/sda1 maj-min: 8:1
Swap:
  Kernel: swappiness: 150 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 7.75 GiB used: 1.93 GiB (24.9%) priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 39.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2751 libs: 1474 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 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/google-chrome.list
    1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://it.mxrepo.com/mx/repo/ bookworm main non-free
    2: deb http://it.mxrepo.com/mx/repo/ bookworm ahs
  No active apt repos in: /etc/apt/sources.list.d/polychromatic.list
  Active apt repos in: /etc/apt/sources.list.d/teamviewer.list
    1: deb [signed-by=/usr/share/keyrings/teamviewer-keyring.gpg] https://linux.teamviewer.com/deb stable main
Info:
  Processes: 378 Uptime: 1d 3h 23m wakeups: 67 Memory: 15.49 GiB used: 10.21 GiB (65.9%)
  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: UEFI

[/code]

[Eadwine Rose]

It'll basically behave like a liveUSB. :)

[chrispop99]

I believe there may be problems if you have Nvidia graphics, have installed an Nvidia driver, and the new hardware doesn't use Nvidia. If that is the case, it's relatively easy to revert to the standard driver before you make the Snapshot.

This information might be outdated; someone will be along to confirm or deny this.

Otherwise, new hardware will be identified correctly.

Chris

[MXRobo]

As I understand, if that kernel will work with the new computer, and you don't do any modifications of the MX-Snapshot ISO, yes it should; however if you edit the MX-Snapshot exclusion file, then it may not work, see example from MX-21.3 Xfce exclusion file:

# This stops any video drivers from loading - safe option.
etc/X11/xorg.conf
etc/X11/xorg.conf.d/20-nvidia.conf
etc/X11/xorg.conf.d/20-intel.conf
etc/X11/xorg.conf.d/20-radeon.conf
etc/X11/xorg.conf.d/20-amd.conf

And MAYBE items from this link: viewtopic.php?p=783546#p783546
Particularly: * MX Cleanup : Remove unused wifi drivers

And this should be the same for both different types of snapshots, e.g. personal, for distribution.

And similar to what Eadwine said, it's an ISO, very similar to an official ISO that you would download.

[Adrian]

it's an ISO, very similar to an official ISO that you would download.

It's actually the tool we use to release "monthly updates", right now the July snapshot is set as the default download from Sourceforge. (It included about 170 package updates, and a new kernel version -- by the way the Snapshot tool let you choose what kernel is going to use for the Live USB)