MX-23 RC3 (Xfce) Feedback thread

Forum rules
Locked
Message
Author
User avatar
fehlix
Developer
Posts: 12608
Joined: Wed Apr 11, 2018 5:09 pm

Re: MX-23 RC3 (Xfce) Feedback thread

#51 Post by fehlix »

dolphin_oracle wrote: ↑Tue Jul 25, 2023 11:57 am
pbear wrote: ↑Tue Jul 25, 2023 11:37 am
dolphin_oracle wrote: ↑Tue Jul 25, 2023 9:04 am a btrfs snapshot will fail if there is an active swapfile. apparently.
Wasn't accommodating Timeshift+btrfs the reason for switching from /swapfile to /swap/swap? That's what I recall someone (@AK-47?) saying a few days ago. If it still doesn't work - which would be a bug in Timeshift not MX - I'd suggest going back to the default /swapfile. Not an issue for me personally, as I'm fine making the change manually during installation. In fact, most of my systems use a swap partition (more efficient because they're multi-boot). Just seems to me it would be easier for users in general to have what they're likely to see described in articles on the internet. Again, a suggestion, not a bug.
its a "feature" of btrfs snapshots, not really timeshift. the scenario of having an active swapfile on the partition to be snapshoted is just not supported by the btrfs file system tools. You *might* be able to put swap on a subvolume, never tried that.

I also just use a traditional swap partition.
having swapfile on a @swap subvolume is build into the latest installer:
Here adding a /@swap subvolume and next screen selecting swapfile:
minstall-luks-btrfs-efi.jpg
Makes timeshift work but currently only on systemd booted system b/c of the mentioned lsblk-issue, not providing fstype and uuid of the luks-encryped partition, when booting with sysvinit.
You do not have the required permissions to view the files attached to this post.
Top
User avatar
doodstecsonhere
Posts: 86
Joined: Sat Jun 17, 2023 10:44 am

Re: MX-23 RC3 (Xfce) Feedback thread

#52 Post by doodstecsonhere »

dolphin_oracle wrote: ↑Tue Jul 25, 2023 9:04 am a btrfs snapshot will fail if there is an active swapfile. apparently.
Thanks for the clue, @dolphin_oracle . (y) Timeshift snapshots in btrfs is now working, but I had to not make a swap file and/or swap partition.

I MX snapshot-ed, then reinstalled into a new btrfs files system from ext4.

My QSI:

Code: Select all

Snapshot created on: 20230725_2233
System:
  Kernel: 6.3.0-2mx-ahs-amd64 [6.3.11-1~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.3.0-2mx-ahs-amd64 root=UUID=<filter> ro
    rootflags=subvol=@ quiet splash init=/lib/systemd/systemd
  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 25  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Laptop System: SAMSUNG product: 535U3C v: P01RAG serial: <superuser required> Chassis:
    type: 9 serial: <superuser required>
  Mobo: SAMSUNG model: SAMSUNG_NP1234567890 v: SEC_SW_REVISION_1234567890ABCD
    serial: <superuser required> BIOS: American Megatrends v: P01RAG.N43.120612.LEO date: 06/12/2012
Battery:
  ID-1: BAT1 charge: 21.1 Wh (77.0%) condition: 27.4/45.1 Wh (60.7%) volts: 7.7 min: 7.4
    model: SAMSUNG Electronics type: Li-ion serial: N/A status: not charging
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse PID:003f serial: N/A
    charge: 70% (should be ignored) rechargeable: yes status: discharging
  Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard PID:0055 serial: N/A
    charge: 55% (should be ignored) rechargeable: yes status: discharging
  Device-3: hidpp_battery_2 model: Logitech Wireless Keyboard K270 serial: <filter>
    charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
  Info: model: AMD A6-4455M APU with Radeon HD Graphics bits: 64 type: MT MCP arch: Piledriver
    level: v2 built: 2012-13 process: GF 32nm family: 0x15 (21) model-id: 0x10 (16) stepping: 1
    microcode: 0x6001119
  Topology: cpus: 1x cores: 2 smt: enabled cache: L1: 96 KiB desc: d-2x16 KiB; i-1x64 KiB
    L2: 2 MiB desc: 1x2 MiB
  Speed (MHz): avg: 1749 high: 1797 min/max: 1300/2100 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 1702 2: 1797 bogomips: 8383
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  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 vulnerable
  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, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not
    affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Trinity [Radeon HD 7500G] vendor: Samsung Co driver: radeon v: kernel
    alternate: amdgpu arch: TeraScale-3 code: Northern Islands process: TSMC 32nm built: 2010-13
    ports: active: HDMI-A-1,LVDS-1 empty: VGA-1 bus-ID: 00:01.0 chip-ID: 1002:990a class-ID: 0300
  Device-2: Z-Star Micro Vega USB 2.0 Camera. type: USB driver: snd-usb-audio,uvcvideo
    bus-ID: 1-5.2:4 chip-ID: 0ac8:c40a class-ID: 0102
  Device-3: Silicon Motion WebCam SC-13HDL11431N type: USB driver: uvcvideo bus-ID: 2-2:3
    chip-ID: 2232:1018 class-ID: 0e02
  Display: x11 server: X.Org v: 1.21.1.7 compositors: 1: xfwm v: 4.18.0 2: Compton v: 1 driver:
    X: loaded: radeon unloaded: fbdev,modesetting,vesa dri: r600 gpu: radeon display-ID: :0.0
    screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99") s-diag: 414mm (16.31")
  Monitor-1: HDMI-A-1 mapped: HDMI-0 pos: primary model: TV Monitor built: 2018 res: 1366x768
    hz: 60 dpi: 60 gamma: 1.2 size: 575x323mm (22.64x12.72") modes: max: 1366x768 min: 720x400
  Monitor-2: LVDS-1 mapped: LVDS model: Seiko Epson 0x3246 built: 2011 res: 1366x768 hz: 60
    dpi: 118 gamma: 1.2 size: 293x165mm (11.54x6.5") diag: 336mm (13.2") ratio: 16:9 modes:
    max: 1366x768 min: 640x480
  API: OpenGL v: 4.5 Mesa 22.3.6 renderer: AMD ARUBA (DRM 2.50.0 / 6.3.0-2mx-ahs-amd64 LLVM
    15.0.6) direct-render: Yes
Audio:
  Device-1: AMD Trinity HDMI Audio vendor: Samsung Co driver: snd_hda_intel bus-ID: 1-5.2:4
    v: kernel chip-ID: 0ac8:c40a bus-ID: 00:01.1 class-ID: 0102 chip-ID: 1002:9902 class-ID: 0403
  Device-2: AMD FCH Azalia vendor: Samsung Co driver: snd_hda_intel v: kernel bus-ID: 00:14.2
    chip-ID: 1022:780d class-ID: 0403
  Device-3: Z-Star Micro Vega USB 2.0 Camera. type: USB driver: snd-usb-audio,uvcvideo
  API: ALSA v: k6.3.0-2mx-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: Samsung Co driver: r8169
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 01:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: Qualcomm Atheros AR9462 Wireless Network Adapter vendor: Samsung Co driver: ath9k
    v: kernel modules: wl pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 168c:0034
    class-ID: 0280
  IF: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: Qualcomm Atheros AR3012 Bluetooth 4.0 type: USB driver: btusb v: 0.8 bus-ID: 5-1:2
    chip-ID: 0cf3:3004 class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 3 state: down bt-service: enabled,running rfk-block:
    hardware: no software: no address: <filter>
  Info: acl-mtu: 1022:8 sco-mtu: 183:5 link-policy: rswitch hold sniff
    link-mode: peripheral accept
Drives:
  Local Storage: total: 140.44 GiB used: 6.73 GiB (4.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: SanDisk model: SDSSDA120G size: 111.79 GiB block-size:
    physical: 512 B logical: 512 B speed: 3.0 Gb/s type: SSD serial: <filter> rev: 70RL scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: USB 3.2Gen1 size: 28.65 GiB
    block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 111.79 GiB size: 111.79 GiB (100.00%) used: 6.73 GiB (6.0%) fs: btrfs
    dev: /dev/sda1 maj-min: 8:1
  ID-2: /home raw-size: 111.79 GiB size: 111.79 GiB (100.00%) used: 6.73 GiB (6.0%) fs: btrfs
    dev: /dev/sda1 maj-min: 8:1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 71.9 C mobo: N/A gpu: radeon temp: 60.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2331 libs: 1216 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/megasync.list
    1: deb [signed-by=/usr/share/keyrings/meganz-archive-keyring.gpg] https://mega.nz/linux/repo/Debian_testing/ ./
  Active apt repos in: /etc/apt/sources.list.d/microsoft-edge.list
    1: deb [arch=amd64] https://packages.microsoft.com/repos/edge/ stable main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirror.rise.ph/mxlinux-pkg/mx/repo/ bookworm main non-free
    2: deb http://mirror.rise.ph/mxlinux-pkg/mx/repo/ bookworm ahs
  Active apt repos in: /etc/apt/sources.list.d/spotify.list
    1: deb http://repository.spotify.com stable non-free
  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: 238 Uptime: 30m wakeups: 7 Memory: 7.23 GiB used: 1.72 GiB (23.8%) 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: BIOS (legacy, CSM, MBR)
I've attached screenshots of a mini walkthrough of how I did my current install from the partition part of the installer all the way to a successful Timeshift snapshot.
You do not have the required permissions to view the files attached to this post.
Top
User avatar
doodstecsonhere
Posts: 86
Joined: Sat Jun 17, 2023 10:44 am

Re: MX-23 RC3 (Xfce) Feedback thread

#53 Post by doodstecsonhere »

doodstecsonhere wrote: ↑Wed Jul 26, 2023 1:41 am
dolphin_oracle wrote: ↑Tue Jul 25, 2023 9:04 am a btrfs snapshot will fail if there is an active swapfile. apparently.
Thanks for the clue, @dolphin_oracle . (y) Timeshift snapshots in btrfs is now working, but I had to not make a swap file and/or swap partition.

I MX snapshot-ed, then reinstalled into a new btrfs files system from ext4.

My QSI:

Code: Select all

Snapshot created on: 20230725_2233
System:
  Kernel: 6.3.0-2mx-ahs-amd64 [6.3.11-1~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.3.0-2mx-ahs-amd64 root=UUID=<filter> ro
    rootflags=subvol=@ quiet splash init=/lib/systemd/systemd
  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 25  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Laptop System: SAMSUNG product: 535U3C v: P01RAG serial: <superuser required> Chassis:
    type: 9 serial: <superuser required>
  Mobo: SAMSUNG model: SAMSUNG_NP1234567890 v: SEC_SW_REVISION_1234567890ABCD
    serial: <superuser required> BIOS: American Megatrends v: P01RAG.N43.120612.LEO date: 06/12/2012
Battery:
  ID-1: BAT1 charge: 21.1 Wh (77.0%) condition: 27.4/45.1 Wh (60.7%) volts: 7.7 min: 7.4
    model: SAMSUNG Electronics type: Li-ion serial: N/A status: not charging
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse PID:003f serial: N/A
    charge: 70% (should be ignored) rechargeable: yes status: discharging
  Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard PID:0055 serial: N/A
    charge: 55% (should be ignored) rechargeable: yes status: discharging
  Device-3: hidpp_battery_2 model: Logitech Wireless Keyboard K270 serial: <filter>
    charge: 55% (should be ignored) rechargeable: yes status: discharging
CPU:
  Info: model: AMD A6-4455M APU with Radeon HD Graphics bits: 64 type: MT MCP arch: Piledriver
    level: v2 built: 2012-13 process: GF 32nm family: 0x15 (21) model-id: 0x10 (16) stepping: 1
    microcode: 0x6001119
  Topology: cpus: 1x cores: 2 smt: enabled cache: L1: 96 KiB desc: d-2x16 KiB; i-1x64 KiB
    L2: 2 MiB desc: 1x2 MiB
  Speed (MHz): avg: 1749 high: 1797 min/max: 1300/2100 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 1702 2: 1797 bogomips: 8383
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  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 vulnerable
  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, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not
    affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Trinity [Radeon HD 7500G] vendor: Samsung Co driver: radeon v: kernel
    alternate: amdgpu arch: TeraScale-3 code: Northern Islands process: TSMC 32nm built: 2010-13
    ports: active: HDMI-A-1,LVDS-1 empty: VGA-1 bus-ID: 00:01.0 chip-ID: 1002:990a class-ID: 0300
  Device-2: Z-Star Micro Vega USB 2.0 Camera. type: USB driver: snd-usb-audio,uvcvideo
    bus-ID: 1-5.2:4 chip-ID: 0ac8:c40a class-ID: 0102
  Device-3: Silicon Motion WebCam SC-13HDL11431N type: USB driver: uvcvideo bus-ID: 2-2:3
    chip-ID: 2232:1018 class-ID: 0e02
  Display: x11 server: X.Org v: 1.21.1.7 compositors: 1: xfwm v: 4.18.0 2: Compton v: 1 driver:
    X: loaded: radeon unloaded: fbdev,modesetting,vesa dri: r600 gpu: radeon display-ID: :0.0
    screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99") s-diag: 414mm (16.31")
  Monitor-1: HDMI-A-1 mapped: HDMI-0 pos: primary model: TV Monitor built: 2018 res: 1366x768
    hz: 60 dpi: 60 gamma: 1.2 size: 575x323mm (22.64x12.72") modes: max: 1366x768 min: 720x400
  Monitor-2: LVDS-1 mapped: LVDS model: Seiko Epson 0x3246 built: 2011 res: 1366x768 hz: 60
    dpi: 118 gamma: 1.2 size: 293x165mm (11.54x6.5") diag: 336mm (13.2") ratio: 16:9 modes:
    max: 1366x768 min: 640x480
  API: OpenGL v: 4.5 Mesa 22.3.6 renderer: AMD ARUBA (DRM 2.50.0 / 6.3.0-2mx-ahs-amd64 LLVM
    15.0.6) direct-render: Yes
Audio:
  Device-1: AMD Trinity HDMI Audio vendor: Samsung Co driver: snd_hda_intel bus-ID: 1-5.2:4
    v: kernel chip-ID: 0ac8:c40a bus-ID: 00:01.1 class-ID: 0102 chip-ID: 1002:9902 class-ID: 0403
  Device-2: AMD FCH Azalia vendor: Samsung Co driver: snd_hda_intel v: kernel bus-ID: 00:14.2
    chip-ID: 1022:780d class-ID: 0403
  Device-3: Z-Star Micro Vega USB 2.0 Camera. type: USB driver: snd-usb-audio,uvcvideo
  API: ALSA v: k6.3.0-2mx-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: Samsung Co driver: r8169
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 01:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: Qualcomm Atheros AR9462 Wireless Network Adapter vendor: Samsung Co driver: ath9k
    v: kernel modules: wl pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 168c:0034
    class-ID: 0280
  IF: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: Qualcomm Atheros AR3012 Bluetooth 4.0 type: USB driver: btusb v: 0.8 bus-ID: 5-1:2
    chip-ID: 0cf3:3004 class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 3 state: down bt-service: enabled,running rfk-block:
    hardware: no software: no address: <filter>
  Info: acl-mtu: 1022:8 sco-mtu: 183:5 link-policy: rswitch hold sniff
    link-mode: peripheral accept
Drives:
  Local Storage: total: 140.44 GiB used: 6.73 GiB (4.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: SanDisk model: SDSSDA120G size: 111.79 GiB block-size:
    physical: 512 B logical: 512 B speed: 3.0 Gb/s type: SSD serial: <filter> rev: 70RL scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: USB 3.2Gen1 size: 28.65 GiB
    block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 111.79 GiB size: 111.79 GiB (100.00%) used: 6.73 GiB (6.0%) fs: btrfs
    dev: /dev/sda1 maj-min: 8:1
  ID-2: /home raw-size: 111.79 GiB size: 111.79 GiB (100.00%) used: 6.73 GiB (6.0%) fs: btrfs
    dev: /dev/sda1 maj-min: 8:1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 71.9 C mobo: N/A gpu: radeon temp: 60.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2331 libs: 1216 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/megasync.list
    1: deb [signed-by=/usr/share/keyrings/meganz-archive-keyring.gpg] https://mega.nz/linux/repo/Debian_testing/ ./
  Active apt repos in: /etc/apt/sources.list.d/microsoft-edge.list
    1: deb [arch=amd64] https://packages.microsoft.com/repos/edge/ stable main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirror.rise.ph/mxlinux-pkg/mx/repo/ bookworm main non-free
    2: deb http://mirror.rise.ph/mxlinux-pkg/mx/repo/ bookworm ahs
  Active apt repos in: /etc/apt/sources.list.d/spotify.list
    1: deb http://repository.spotify.com stable non-free
  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: 238 Uptime: 30m wakeups: 7 Memory: 7.23 GiB used: 1.72 GiB (23.8%) 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: BIOS (legacy, CSM, MBR)
I've attached screenshots of a mini walkthrough of how I did my current install from the partition part of the installer all the way to a successful Timeshift snapshot.
P.S. I couldn't attach my minstall.log file for some reason (http error when I attach it to a post) and I can't paste the contents here as it's beyond the characters limit of the forum.
Top
User avatar
doodstecsonhere
Posts: 86
Joined: Sat Jun 17, 2023 10:44 am

Re: MX-23 RC3 (Xfce) Feedback thread

#54 Post by doodstecsonhere »

fehlix wrote: ↑Tue Jul 25, 2023 8:18 am
doodstecsonhere wrote: ↑Mon Jul 24, 2023 10:46 am Here's my QSI:

Code: Select all

System:
  Kernel: 6.3.0-2mx-ahs-amd64 [6.3.11-1~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.3.0-2mx-ahs-amd64 root=UUID=<filter> ro
    rootflags=subvol=@ quiet splash resume=UUID= resume_offset=809951 init=/lib/systemd/systemd
Somthing seems missing with "resume=UUID=" needed for resume from hibernation.
Thanks for the observation, @fehlix ! (y) However I don't really use hibernation and so I decided to not enable it or figure it out for now hehe. See my newer replies: I went back to brfs again from ext4. But I didn't create a subvolume for swap, unlike you here. Should I have? In @dolphin_oracle 's youtube video about btrfs install in MX 21, he didn't do a swap subvolume there in his btrfs partition, though he did have a swap partition in the video. I didn't do a swap partition, should I reinstall again but with a swap subvolume in btrfs partition?
Top
User avatar
doodstecsonhere
Posts: 86
Joined: Sat Jun 17, 2023 10:44 am

Re: MX-23 RC3 (Xfce) Feedback thread

#55 Post by doodstecsonhere »

fehlix wrote: ↑Tue Jul 25, 2023 8:18 am
doodstecsonhere wrote: ↑Mon Jul 24, 2023 10:46 am Tried my first ever manual BTRFS install with RC3 on my device. I followed @dolphin_oracle 's youtube video in that I created a root and home subvolume in the BTRFS partition. In my install, I clicked "new layout", then "reset layout", then checked everything (swap, hibernate, standard snapshot), then I added a "/' and "home" subvolume to the BTRFS partition, which is also my only partition (I didn't create an EFI and swap partition).

Issues:

Timeshift fails to create any BTRFS snapshots.
Works for me, when booted in systemd.
MX-installer:
luks+btrfs+subvol:/@ ( root) , /@home /@swap
minstall-luks-btrfs-efi.jpg
Screensshot shows terminal with "lsblk -f" to list partitons
and timeshift created snapshot:timeshift-luks-btrfs-systemd.jpg
doodstecsonhere wrote: ↑Mon Jul 24, 2023 10:46 am Here's my QSI:

Code: Select all

System:
  Kernel: 6.3.0-2mx-ahs-amd64 [6.3.11-1~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.3.0-2mx-ahs-amd64 root=UUID=<filter> ro
    rootflags=subvol=@ quiet splash resume=UUID= resume_offset=809951 init=/lib/systemd/systemd
Somthing seems missing with "resume=UUID=" needed for resume from hibernation.
@fehlix will you please shortly explain your reasoning behind you vdb1, vdb2, and vdb3 partitions? I'm new to manually partitioning: trying to learn more on it. I usually just to a regular install but I'm at a "enthusiastically confused" stage for now. :)
Top
User avatar
doodstecsonhere
Posts: 86
Joined: Sat Jun 17, 2023 10:44 am

Re: MX-23 RC3 (Xfce) Feedback thread

#56 Post by doodstecsonhere »

dolphin_oracle wrote: ↑Tue Jul 25, 2023 11:57 am I also just use a traditional swap partition.
@dolphin_oracle I have 8GB (7.2GB) ram. Should my swap partition be 7.2GB, too to ensure hibernation can work in all scenarios?
Top
User avatar
fehlix
Developer
Posts: 12608
Joined: Wed Apr 11, 2018 5:09 pm

Re: MX-23 RC3 (Xfce) Feedback thread

#57 Post by fehlix »

doodstecsonhere wrote: ↑Wed Jul 26, 2023 2:10 am However I don't really use hibernation and so I decided to not enable it or figure it out for now hehe. See my newer replies: I went back to brfs again from ext4. But I didn't create a subvolume for swap, unlike you here. Should I have?
I didn't do a swap partition, should I reinstall again but with a swap subvolume in btrfs partition?
Probably a "matter of taste" or experience. The simplest would be to reinstall with adding a /@swap subvolume and keep swap-file selection with the suggested default - as in your case of 3Gb.
Adding manualy a @swap subvolume is also possible. But note: When manually creating a swapfile on a btrfs subvolume the swap file "must" have the attribute "No_CoW" in order to disables builtin BTRFS CoW (copy on write) feature. You can check with "lsattr -l" whether CoW is disabled for the swap-file.
In addtion you would need add manualy entries to /etc/fstab in order to have swap enabled at boot.
doodstecsonhere wrote: ↑Wed Jul 26, 2023 2:00 am P.S. I couldn't attach my minstall.log file for some reason (http error when I attach it to a post) and I can't paste the contents here as it's beyond the characters limit of the forum.
Maybe just create a compressed zip file and attache minstall.log.zip
doodstecsonhere wrote: ↑Wed Jul 26, 2023 2:17 am @fehlix will you please shortly explain your reasoning behind you vdb1, vdb2, and vdb3 partitions? I'm new to manually partitioning: trying to learn more on it. I usually just to a regular install but I'm at a "enthusiastically confused" stage for now. :)
On my KVM/Qemu VM install the partitions are named by the kernel like vdb1, vdb2...

/dev/vdb1 "BIOS_GRUB" : As I do prefere to boot/switch sometimes either within UEFI-boot mode or with classical MBR/BIOS-boot mode, this 1MB sized BIOS_GRUB partition on a GPT-partition table, would keep grub happy, when grub-install'ing
"onto" MBR with grub-install (--target=i386-pc ). The reason: A GPT-partition table do not have unused/free space between the first sector (the real MBR) and the start of the partition, which is needed by MBR-grub-install to place it's own grub core.img onto.

/dev/vdb2 "ESP": This is the ESP (EFI System partition) which grub-install is needing for creating EFI-grub-boot loader, necessary for UEFI-booting

/dev/vdb3 "BOOT": This is the not-encrypted ext4 boot partition, which will hold the boot files for allowing to boot further into the luks-encrypted system at /dev/vdb4
minstall-luks-btrfs-efi.jpg
You do not have the required permissions to view the files attached to this post.
Top
User avatar
doodstecsonhere
Posts: 86
Joined: Sat Jun 17, 2023 10:44 am

Re: MX-23 RC3 (Xfce) Feedback thread

#58 Post by doodstecsonhere »

fehlix wrote: ↑Wed Jul 26, 2023 6:57 am
doodstecsonhere wrote: ↑Wed Jul 26, 2023 2:10 am However I don't really use hibernation and so I decided to not enable it or figure it out for now hehe. See my newer replies: I went back to brfs again from ext4. But I didn't create a subvolume for swap, unlike you here. Should I have?
I didn't do a swap partition, should I reinstall again but with a swap subvolume in btrfs partition?
Probably a "matter of taste" or experience. The simplest would be to reinstall with adding a /@swap subvolume and keep swap-file selection with the suggested default - as in your case of 3Gb.
Adding manualy a @swap subvolume is also possible. But note: When manually creating a swapfile on a btrfs subvolume the swap file "must" have the attribute "No_CoW" in order to disables builtin BTRFS CoW (copy on write) feature. You can check with "lsattr -l" whether CoW is disabled for the swap-file.
In addtion you would need add manualy entries to /etc/fstab in order to have swap enabled at boot.
It seems having a swap partition is better for performance than the swap brfs subvolume as the swap partition is contiguous and not as prone to fragmentation as the swap btrfs subvolume.

I've decided on reinstalling with swap partition size equal to my ram for hibernation. Thanks for the infos and advice, @fehlix ! :puppy:
Top
User avatar
doodstecsonhere
Posts: 86
Joined: Sat Jun 17, 2023 10:44 am

Re: MX-23 RC3 (Xfce) Feedback thread

#59 Post by doodstecsonhere »

fehlix wrote: ↑Wed Jul 26, 2023 6:57 am
doodstecsonhere wrote: ↑Wed Jul 26, 2023 2:00 am P.S. I couldn't attach my minstall.log file for some reason (http error when I attach it to a post) and I can't paste the contents here as it's beyond the characters limit of the forum.
Maybe just create a compressed zip file and attache minstall.log.zip
THANKS for this, @fehlix ! Hehe, I'll do this after reinstall. :turtle:
Top
User avatar
doodstecsonhere
Posts: 86
Joined: Sat Jun 17, 2023 10:44 am

Re: MX-23 RC3 (Xfce) Feedback thread

#60 Post by doodstecsonhere »

fehlix wrote: ↑Wed Jul 26, 2023 6:57 am
doodstecsonhere wrote: ↑Wed Jul 26, 2023 2:17 am @fehlix will you please shortly explain your reasoning behind you vdb1, vdb2, and vdb3 partitions? I'm new to manually partitioning: trying to learn more on it. I usually just to a regular install but I'm at a "enthusiastically confused" stage for now. :)
On my KVM/Qemu VM install the partitions are named by the kernel like vdb1, vdb2...

/dev/vdb1 "BIOS_GRUB" : As I do prefere to boot/switch sometimes either within UEFI-boot mode or with classical MBR/BIOS-boot mode, this 1MB sized BIOS_GRUB partition on a GPT-partition table, would keep grub happy, when grub-install'ing
"onto" MBR with grub-install (--target=i386-pc ). The reason: A GPT-partition table do not have unused/free space between the first sector (the real MBR) and the start of the partition, which is needed by MBR-grub-install to place it's own grub core.img onto.

/dev/vdb2 "ESP": This is the ESP (EFI System partition) which grub-install is needing for creating EFI-grub-boot loader, necessary for UEFI-booting

/dev/vdb3 "BOOT": This is the not-encrypted ext4 boot partition, which will hold the boot files for allowing to boot further into the luks-encrypted system at /dev/vdb4
minstall-luks-btrfs-efi.jpg
Why 1MB for vdb1, why 512MB for vdb2, and why 1GB for vdb3?
Top
Locked

Return to “General”