Inability to setup AVL_MXE-23.1-20240120_x64 [Solved]

[Justinian]

This is a three month story which does not raise a particular point in regard to my failure to boot AVL_MXE-23.1-20240120_x64.iso past Grub after having successfully checked it live on two machines where it was then installed. At the end of the tale though I now have AVL_MXE-23.2-20240405_x64.iso installed on Matisse. AVL-MXE-21 was much appreciated the year before.

Code: Select all

System:
  Kernel: 6.6.9-1-liquorix-amd64 [6.6-11~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable rcupdate.rcu_expedited=1 BOOT_IMAGE=/antiX/vmlinuz threadirqs nosplash
CPU:
  Info: model: AMD A8-7680 Radeon R7 10 Compute Cores 4C+6G bits: 64 type: MT MCP arch: Excavator
    level: v3 note: check built: 2015 process: GF 28nm family: 0x15 (21) model-id: 0x60 (96)
    stepping: 1 microcode: 0x600611A
Drives:
  ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: KUIJIA model: Dahua U116 size: 29.3 GiB
    block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 8.07 scheme: MBR
Boot Mode: UEFI


System:
  Kernel: 6.6.12-1-liquorix-amd64 [6.6-16~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable rcupdate.rcu_expedited=1 BOOT_IMAGE=/boot/vmlinuz-6.6.12-1-liquorix-amd64
    root=UUID=<filter> ro threadirqs quiet
  Desktop: Enlightenment v: 0.25.4 vt: 7 dm: LightDM v: 1.26.0 Distro: AVL_MXE-23.2-20240405_x64
    Enlightened April 5 2024 base: Debian GNU/Linux 12 (bookworm)
CPU:
  Info: model: AMD Ryzen 5 3500 bits: 64 type: MCP arch: Zen 2 gen: 3 level: v3 note: check
    built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23) model-id: 0x71 (113) stepping: 0
    microcode: 0x8701021
Graphics:
  Device-1: AMD Polaris 20 XL [Radeon RX 580 2048SP] driver: amdgpu v: kernel arch: GCN-4
    code: Arctic Islands process: GF 14nm built: 2016-20 pcie: gen: 1 speed: 2.5 GT/s lanes: 16
    link-max: gen: 3 speed: 8 GT/s ports: active: HDMI-A-1 empty: DP-1,DVI-D-1 bus-ID: 09:00.0
    chip-ID: 1002:6fdf class-ID: 0300 temp: 35.0 C
Partition:
  ID-1: / raw-size: 34.18 GiB size: 33.34 GiB (97.56%) used: 14.69 GiB (44.1%) fs: ext4
    dev: /dev/sda2 maj-min: 8:2
Info:
  Processes: 329 Uptime: 3m wakeups: 1 Memory: 15.56 GiB used: 823.1 MiB (5.2%) 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)

So that the 23.1 iso wouldn't be wasted I thought maybe I could try frugal for the first time. The simplest instructions I could follow were by EasyOS. I chose antiX-23.1-runit_x64-base to have a small enough running system and created three folders for the frugal files of vmlinuz, initrd and _.sfs. Had to use the Ventoy-unfriendly EasyOS 5.7 live to copy each. Was able to create one folder as well using the advanced option on MX-KDE live Grub. However after rebooting from the live session to no avail and then doing update-grub on AntiX, it would only present itself on Grub when rebooting. So I resorted to Limine with EasyOS live and the Limine boot screen showed AntiX and EasyOS but not AVL, MX-KDE and MX-ahs. Problem gone with the new release. By the way I really liked the appimage choices on EasyOS.

Code: Select all

System:
  Host: antix1 Kernel: 5.10.199-antix.1-amd64-smp arch: x86_64 bits: 64
    Desktop: IceWM v: 3.4.5 Distro: antiX-23.1-runit_x64-base Arditi del Popolo 21 February 2024
CPU:
  Info: triple core model: AMD A6-3500 APU with Radeon HD Graphics bits: 64
    type: MCP cache: L2: 3 MiB
Drives:
  Local Storage: total: 465.76 GiB used: 33.49 GiB (7.2%)
  ID-1: /dev/sda vendor: Samsung model: ST500LM012 HN-M500MBB
    size: 465.76 GiB


-Computer-
Processor	: 12x AMD Ryzen 5 5600G with Radeon Graphics
Memory		: 15750MB (1163MB used)
Machine Type	: Physical machine
Operating System: Easy Kirkstone64


 \avlfrugalfiles\initrd   42.5 MB
 \avlfrugalfiles\linuxfs  5.23 GB 
 \avlfrugalfiles\vmlinuz  8.50 MB

The system drive gets swapped around a bit which goes to show how flexible MX is, the same way it has been to me since before MX-15.

[CharlesV]

So, were you able to install the regular MX 23?

[Justinian]

Yes, since last year. For now I am not experimenting with frugal anymore. MX and AVL installs are all fine. Been happy with the distro since 2014.

[AVLinux]

@Justinian

Did it actually 'not boot' or was it simply the pesky 'backlight set to 0' bug that could cause the lightDM login window to be faded to 0 and therefore not visible?

[Justinian]

Could be lightdm but I don't have 23.1 anymore and 23.2 works as long as it's not on sysvinit. Sorry for the late response as I am rather intermittently online.

[Justinian]

23.2 resides on a 2.5" hdd for duty as external/internal boot drive for any of the above machines that might require AVL. On an old laptop that once handled 21.3 quite well, the touchpad buttons this time responded poorly and somehow the spacebar was needed as a clicker. To be reasonable, the hardware's not meant for it. Hadn't mentioned it before but there were some hiccups right after installation. On first boot, Thunar stopped responding and then disappeared from the taskbar. Trying to get it back from the menu, somehow Thunar got lodged to the dock on the right where it still is now. Next occasion to boot was a failure and I did not return to it for days but when I did, AVL-MXE has never failed on AMD Matisse, Cezzane, Carrizo and Llano.

Code: Select all

Snapshot created on: 20240421_1008
System:
  Kernel: 6.6.12-1-liquorix-amd64 [6.6-16~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable rcupdate.rcu_expedited=1 BOOT_IMAGE=/boot/vmlinuz-6.6.12-1-liquorix-amd64
    root=UUID=<filter> ro threadirqs quiet init=/lib/systemd/systemd
  Desktop: Enlightenment v: 0.25.4 vt: 7 dm: LightDM v: 1.26.0 Distro: AVL_MXE-23.2-20240405_x64
    Enlightened April 5 2024 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Laptop System: FUJITSU product: FMVA533AB v: N/A serial: <superuser required> Chassis:
    type: 10 serial: <superuser required>
  Mobo: FUJITSU model: FJNBB06 serial: <superuser required> BIOS: FUJITSU // Phoenix
    v: Version 1.22 date: 04/03/2019
CPU:
  Info: model: Intel Core i3 M 350 bits: 64 type: MT MCP arch: Westmere gen: core 1 level: v2
    built: 2010-11 process: Intel 32nm family: 6 model-id: 0x25 (37) stepping: 2 microcode: 0x11
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
    desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: Western Digital model: WD5000LPVX-60V0TT0
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: HDD rpm: 5400 serial: <filter>
    rev: 01.0 scheme: MBR
Partition:
  ID-1: / raw-size: 34.18 GiB size: 33.34 GiB (97.56%) used: 16.66 GiB (50.0%) fs: ext4
    dev: /dev/sdb2 maj-min: 8:18
Info:
  Processes: 268 Uptime: 4m wakeups: 1 Memory: 3.63 GiB used: 656.9 MiB (17.7%) 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)