MX Linux Forum

Posted: **Fri Jun 16, 2023 3:36 pm**

peter_li wrote: Fri Jun 16, 2023 3:24 pm
fehlix wrote: Fri Jun 16, 2023 12:40 pm
peter_li wrote: Fri Jun 16, 2023 12:29 pm @fehlix I think I wrote a answer before with the content that the os-prober on MX-23 does not detect my other Linux Distribution installations correctly. If they sit on BTRFS they will not detected. But I dont find my last post. So for showing you the difference I state the output from os-prober on Manjaro:
That's correct, grub through it's use of os-prober won't be able to detect another install on btrfs,
esp, where /root sits on a /@ subvolume. I haven't tried an btrfs install where root is not on a subvolume
MX defaults to install root on /@, mainly b/c that's a timeshift requirement.
Excuse me please when I ask again. So you mean the output of os-prober on MX Linux is the expected behavior and that what Manjaro and maybe others additionally do is extraordinary? So the solution for a multibooting environment, mainly for testing, is to stick at ext4 it seems?

As far as debian provided grub / os-prober goes, yes. Note: With Debian 12 bookworm, os-prober is kind of completely disabled. In MX-23 we re-enabeled os-prober to further support multi-boot with GRUB. But no attempt was made to enance grub/os-prober to detect os installs with btrfs and root-subvolumes.
User can still manually add other OS grub menu entries, e.g within /boot/grub/custom.cfg
+++EDIT+++
On UEFI systems, you can use rEFInd efi-bootmanager, to multi-boot through rEFInd provided EFI-bootoption menu,
which should also allow boot into any btrfs install.

Posted: **Fri Jun 16, 2023 4:26 pm**

fehlix wrote: Fri Jun 16, 2023 3:36 pm
peter_li wrote: Fri Jun 16, 2023 3:24 pm
fehlix wrote: Fri Jun 16, 2023 12:40 pm
That's correct, grub through it's use of os-prober won't be able to detect another install on btrfs,
esp, where /root sits on a /@ subvolume. I haven't tried an btrfs install where root is not on a subvolume
MX defaults to install root on /@, mainly b/c that's a timeshift requirement.
Excuse me please when I ask again. So you mean the output of os-prober on MX Linux is the expected behavior and that what Manjaro and maybe others additionally do is extraordinary? So the solution for a multibooting environment, mainly for testing, is to stick at ext4 it seems?
As far as debian provided grub / os-prober goes, yes. Note: With Debian 12 bookworm, os-prober is kind of completely disabled. In MX-23 we re-enabeled os-prober to further support multi-boot with GRUB. But no attempt was made to enance grub/os-prober to detect os installs with btrfs and root-subvolumes.
User can still manually add other OS grub menu entries, e.g within /boot/grub/custom.cfg

That would be the next question:
Shouldn't it be expected that Debian Bookworm with GRUB_DISABLE_OS_PROBER=false and MX Linux provide the same result?
Result on Debian:

Code: Select all

menuentry 'openSUSE Leap 15.5 (on /dev/sdb8)' --class opensuse --class gnu-linux --class gnu --class os $m>
        insmod part_gpt
        insmod btrfs
        set root='hd1,gpt8'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt8 --hint-efi=hd1,gpt8 --hint-baremeta>
        else
          search --no-floppy --fs-uuid --set=root 36f9708b-432f-4f9f-9dcd-6bb415e37706
        fi
        linux /boot/vmlinuz-5.14.21-150500.53-default root=UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 ${ext>
        initrd /boot/initrd-5.14.21-150500.53-default
}

/etc/fstab on openSUSE:

Code: Select all

$ sudo cat /mnt/sdb8/etc/fstab
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706  /                       btrfs  defaults                      0  0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706  /var                    btrfs  subvol=/@/var                 0  0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706  /usr/local              btrfs  subvol=/@/usr/local           0  0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706  /tmp                    btrfs  subvol=/@/tmp                 0  0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706  /srv                    btrfs  subvol=/@/srv                 0  0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706  /root                   btrfs  subvol=/@/root                0  0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706  /opt                    btrfs  subvol=/@/opt                 0  0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706  /home                   btrfs  subvol=/@/home                0  0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706  /boot/grub2/x86_64-efi  btrfs  subvol=/@/boot/grub2/x86_64-efi  0  0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706  /boot/grub2/i386-pc     btrfs  subvol=/@/boot/grub2/i386-pc  0  0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706  /.snapshots             btrfs  subvol=/@/.snapshots          0  0
UUID=9fc81fd9-6af1-4a50-9f3a-0d557a9cd476  swap                    swap   defaults                      0  0
UUID=7366-5199                             /boot/efi               vfat   utf8                          0  2

On MX not in result of os-prober.
I wonder how it comes to the difference?

+++EDIT+++
On UEFI systems, you can use rEFInd efi-bootmanager, to multi-boot through rEFInd provided EFI-bootoption menu,
which should also allow boot into any btrfs install.

That's fine especially cause one can install Grub2 and rEFInd as I read. But you will have to inform it about OS updates or added/deleted systems?
Would it there not be the better or equal behavior to hammer on the F12(at least on a DELL Latitude E6510) key at boot?
But what to do when there is only one time Ubuntu shown in the UEFI Boot but there are three partitions: Ubuntu-Mate, Xubuntu and Pinguy egg created Ubuntu? This seems a bit complicated.

Posted: **Fri Jun 16, 2023 5:16 pm**

I am running into a Kodi issue. Installed the one from popular in MXPI. Seems a VLC one too, but haven't tried that yet.

Code: Select all

libva info: VA-API version 1.17.0
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)

Googled that, ran into this page: https://bbs.archlinux.org/viewtopic.php?id=282638

Which basically says:
"seems to be caused by the recent update of libva to 2.17.0-1. Downgrading to libva 2.16.0-1 helped here."

Someone else says:
"===> So as a workaround define this environment variable (and everything works with libva 2.17.0-1, vlc included) :

Code: Select all

echo "setenv LIBVA_DRIVER_NAME nvidia" > /etc/profile.d/libva.csh
echo "export LIBVA_DRIVER_NAME=nvidia" > /etc/profile.d/libva.sh

"

Well, since this is a play installation anyway I up and did that environment variable, rebooted, waited for it to blow up, and nada, still the same results when I run vainfo.
Likely the right way there, not here. Ah well, would have been fun if I could have served up the solution as well

But we'll run with the info.

I figured I'd share it with you guys, since this kinda looks like it may pop up for more with nvidia cards and Kodi/VLC

Code: Select all

System:
  Kernel: 6.1.0-9-amd64 [6.1.27-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-9-amd64 root=UUID=<filter> ro quiet
  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_beta2_x64 Libretto June 15  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop Mobo: ASUSTeK model: TUF B450-PLUS GAMING v: Rev X.0x serial: <superuser required>
    UEFI: American Megatrends v: 1607 date: 06/17/2019
Battery:
  Device-1: hidpp_battery_0 model: Logitech MX Ergo Multi-Device Trackball serial: <filter>
    charge: 100% (should be ignored) rechargeable: yes status: discharging
CPU:
  Info: model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+ gen: 2 level: v3 note: check
    built: 2018-21 process: GF 12nm family: 0x17 (23) model-id: 8 stepping: 2 microcode: 0x800820D
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 768 KiB
    desc: d-8x32 KiB; i-8x64 KiB L2: 4 MiB desc: 8x512 KiB L3: 16 MiB desc: 2x8 MiB
  Speed (MHz): avg: 1502 high: 1550 min/max: 1550/3200 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 1545 2: 1533 3: 1533 4: 1534 5: 1550 6: 1451
    7: 1550 8: 1535 9: 1530 10: 1544 11: 1512 12: 1442 13: 1472 14: 1425 15: 1448 16: 1433
    bogomips: 102193
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb
    vendor: Hauppauge works driver: cx23885 v: 0.0.4 pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    bus-ID: 07:00.0 chip-ID: 14f1:8880 class-ID: 0400
  Device-2: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: ASUSTeK driver: nvidia v: 525.105.17
    non-free: 530.xx+ status: current (as of 2023-03) arch: Pascal code: GP10x process: TSMC 16nm
    built: 2016-21 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 08:00.0 chip-ID: 10de:1c82
    class-ID: 0300
  Device-3: Logitech QuickCam E 3500 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-7:3
    chip-ID: 046d:09a4 class-ID: 0102 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: nvidia
    gpu: cx23885,nvidia display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x286mm (40.00x11.26")
    s-diag: 1055mm (41.55")
  Monitor-1: DVI-D-0 pos: right res: 1920x1080 hz: 60 dpi: 102 size: 477x268mm (18.78x10.55")
    diag: 547mm (21.54") modes: N/A
  Monitor-2: HDMI-0 pos: primary,left res: 1920x1080 hz: 60 dpi: 92
    size: 531x299mm (20.91x11.77") diag: 609mm (23.99") modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 525.105.17 renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
    direct-render: Yes
Audio:
  Device-1: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb
    vendor: Hauppauge works driver: cx23885 bus-ID: 1-7:3 v: 0.0.4 pcie: chip-ID: 046d:09a4 gen: 1
    class-ID: 0102 serial: <filter> speed: 2.5 GT/s lanes: 1 bus-ID: 07:00.0 chip-ID: 14f1:8880
    class-ID: 0400
  Device-2: NVIDIA GP107GL High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
    pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 08:00.1 chip-ID: 10de:0fb9 class-ID: 0403
  Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 bus-ID: 0a:00.3 chip-ID: 1022:1457 class-ID: 0403
  Device-4: Logitech QuickCam E 3500 type: USB driver: snd-usb-audio,uvcvideo
  API: ALSA v: k6.1.0-9-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: ASUSTeK PRIME B450M-A
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 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: Ralink MT7601U Wireless Adapter type: USB driver: mt7601u bus-ID: 1-1:2
    chip-ID: 148f:7601 class-ID: 0000 serial: <filter>
  IF: wlan0 state: down mac: <filter>
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb v: 0.8
    bus-ID: 1-8: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: 931.54 GiB used: 158.25 GiB (17.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q
    temp: 34.0 C scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 3B6Q
    temp: 35.0 C scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q
    temp: 34.0 C scheme: GPT
  ID-4: /dev/sdd maj-min: 8:48 vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 3B6Q
    temp: 34.0 C scheme: GPT
Partition:
  ID-1: / raw-size: 58.59 GiB size: 57.37 GiB (97.92%) used: 7.92 GiB (13.8%) fs: ext4
    dev: /dev/sdb1 maj-min: 8:17
  ID-2: /boot/efi raw-size: 500 MiB size: 499 MiB (99.80%) used: 26.5 MiB (5.3%) fs: vfat
    dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 166.48 GiB size: 162.81 GiB (97.79%) used: 274.7 MiB (0.2%) fs: ext4
    dev: /dev/sdb3 maj-min: 8:19
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 7.81 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdb2
    maj-min: 8:18
Sensors:
  System Temperatures: cpu: 42.6 C mobo: 34.0 C gpu: nvidia temp: 42 C
  Fan Speeds (RPM): cpu: 760 fan-2: 795 fan-3: 0 fan-4: 695 fan-6: 0 gpu: nvidia fan: 26%
  Power: 12v: N/A 5v: N/A 3.3v: 3.36 vbat: 3.29
Repos:
  Packages: pm: dpkg pkgs: 2206 libs: 1149 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
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://nl.mxrepo.com/mx/repo/ bookworm main non-free
Info:
  Processes: 347 Uptime: 8m wakeups: 3 Memory: 31.28 GiB used: 2.27 GiB (7.3%) 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

Posted: **Fri Jun 16, 2023 5:29 pm**

Hi there,
Can I ask a simple question here?
How can I upgrade beta1 from beta2 iso without losing my home and setings?

I didnt want to reinstall from scratch and have to handle configs again.
Thanks

Posted: **Fri Jun 16, 2023 5:54 pm**

peter_li wrote: Fri Jun 16, 2023 4:26 pm Shouldn't it be expected that Debian Bookworm with GRUB_DISABLE_OS_PROBER=false and MX Linux provide the same result?
Result on Debian:

Code: Select all

menuentry 'openSUSE Leap 15.5 (on /dev/sdb8)' --class opensuse --class gnu-linux --class gnu --class os $m>
        insmod part_gpt
        insmod btrfs
        set root='hd1,gpt8'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt8 --hint-efi=hd1,gpt8 --hint-baremeta>
        else
          search --no-floppy --fs-uuid --set=root 36f9708b-432f-4f9f-9dcd-6bb415e37706
        fi
        linux /boot/vmlinuz-5.14.21-150500.53-default root=UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706 ${ext>
        initrd /boot/initrd-5.14.21-150500.53-default
}

/etc/fstab on openSUSE:

Code: Select all

$ sudo cat /mnt/sdb8/etc/fstab
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706  /                       btrfs  defaults                      0  0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706  /var                    btrfs  subvol=/@/var                 0  0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706  /usr/local              btrfs  subvol=/@/usr/local           0  0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706  /tmp                    btrfs  subvol=/@/tmp                 0  0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706  /srv                    btrfs  subvol=/@/srv                 0  0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706  /root                   btrfs  subvol=/@/root                0  0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706  /opt                    btrfs  subvol=/@/opt                 0  0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706  /home                   btrfs  subvol=/@/home                0  0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706  /boot/grub2/x86_64-efi  btrfs  subvol=/@/boot/grub2/x86_64-efi  0  0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706  /boot/grub2/i386-pc     btrfs  subvol=/@/boot/grub2/i386-pc  0  0
UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706  /.snapshots             btrfs  subvol=/@/.snapshots          0  0
UUID=9fc81fd9-6af1-4a50-9f3a-0d557a9cd476  swap                    swap   defaults                      0  0
UUID=7366-5199                             /boot/efi               vfat   utf8                          0  2

On MX not in result of os-prober.
I wonder how it comes to the difference?

That's correct, it should have also listed btrfs install with "/" on top-volume.

peter_li wrote: Fri Jun 16, 2023 4:26 pm
+++EDIT+++
On UEFI systems, you can use rEFInd efi-bootmanager, to multi-boot through rEFInd provided EFI-bootoption menu,
which should also allow boot into any btrfs install.
That's fine especially cause one can install Grub2 and rEFInd as I read. But you will have to inform it about OS updates or added/deleted systems?
Would it there not be the better or equal behavior to hammer on the F12(at least on a DELL Latitude E6510) key at boot?

I idea for inventing rEFInd was something like an easier efi-bootmanager. It can be set as default efi-loader and would list all found efi-loader, not only those which are listed with NVRAM(and may be invalid already).

peter_li wrote: Fri Jun 16, 2023 4:26 pm But what to do when there is only one time Ubuntu shown in the UEFI Boot but there are three partitions: Ubuntu-Mate, Xubuntu and Pinguy egg created Ubuntu? This seems a bit complicated.

That's Ubuntu and secure-boot related issue, as all those ubuntu-flavors use just one efi-loader entry.
That's actually similar what Debian is now doing, so if you have to install two debian installations, you would only find one EFI-loader. One way to solve it, use for every such install a separate ESP.

Posted: **Fri Jun 16, 2023 6:14 pm**

gRegNfo wrote: Fri Jun 16, 2023 5:29 pm Hi there,
Can I ask a simple question here?
How can I upgrade beta1 from beta2 iso without losing my home and setings?

I didnt want to reinstall from scratch and have to handle configs again.
Thanks

just run your regular updates. I'm not changing the labels for updated systems from beta1 and beta2, but you are getting updates.

once we go final all beta and rc releases will see their version strings bumped.

Posted: **Fri Jun 16, 2023 6:42 pm**

MX Linux 23 Beta 2 won't install.
Writes "Critical error. AntiX/linuxfs file could not be found"

Posted: **Fri Jun 16, 2023 6:57 pm**

megaherz33 wrote: Fri Jun 16, 2023 6:42 pm MX Linux 23 Beta 2 won't install.
Writes "Critical error. AntiX/linuxfs file could not be found"

Install on what kind of a machine (Quick System Info)
Did you check the integrity of the download?
Did you run the USB check? Try reformating it

Posted: **Fri Jun 16, 2023 7:26 pm**

TerryL wrote: Fri Jun 16, 2023 3:34 pm OK, my initial effort was to run the beta-2 as a live USB - no problems noticed

Second was to go to an installed beta-1 and updat / upgrade - no problem, everything looked to be upgraded nicely

What I didn't try was to install from the beta-2 USB - that failed. I was going to overwrite an MX-21.3 partition on one of the spare laptops BUT at the step ti select the partition (the SSD has 2 partitions, MX-21.3 and Debian 11 + a swap) things looked odd, almost I would guess like the Antix system? The MX-23 beta-1 didn't look like that and an install on another old laptop worked fine as expected.

Has anyone else had this problem?

Forgot to add - MX-23 beta-2 XFCE on a Lenovo X240

Posted: **Fri Jun 16, 2023 7:29 pm**

megaherz33 wrote: Fri Jun 16, 2023 6:42 pm MX Linux 23 Beta 2 won't install.
Writes "Critical error. AntiX/linuxfs file could not be found"

Some more details would be good.
Have you made /selected "Check Integrity of the Live media"?
Also, we use the term "install" for installing MX Linux from a live Booted media
after boot.
The message "AntiX/linuxfs file could not be found" indicates
that the LiveBoot was not performed.
So suggest give more details, how you created the LiveBoot Media from the downloaded ISO.

MX Linux Forum

MX-23 beta 2 feedback thread

Re: MX-23 beta 2 feedback thread

Re: MX-23 beta 2 feedback thread

Re: MX-23 beta 2 feedback thread

Re: MX-23 beta 2 feedback thread

Re: MX-23 beta 2 feedback thread

Re: MX-23 beta 2 feedback thread

Re: MX-23 beta 2 feedback thread

Re: MX-23 beta 2 feedback thread

Re: MX-23 beta 2 feedback thread

Re: MX-23 beta 2 feedback thread