MX-23 beta 2 feedback thread

[asqwerth]

so if I understand correctly you specified both a swap partition an a swapfile during installation, but only the swapfile was created/used?

yes, the swap partition was like the EFI were shown in the partition window so I don't touch them. The efi were used, the swap not.

Even if swap partition is shown in the installer "spreadsheet", I believe you still have to select it to "use as swap" and then in the "format" column, choose "preserve" (ie, not to format) it. Otherwise it won't be recorded as a partition you chose to use, and thus won't show up in fstab.

[dolphin_oracle]

Hello @dolphin_oracle,
Installer failed Phase 3 - Grub installation failed.
Installing on BTRFS with encryption, alongside Windows (EFI partition preserved, formerly there was MX23 alpha, on EXT4 w/o encr.).
Created BRTFS subvolumes @, @home in installer.
minstall.log attached.

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=/antiX/vmlinuz quiet splasht nosplash
  Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23_KDE_beta2_x64 Libretto
    June 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop System: Hewlett-Packard product: HP Compaq Pro 6300 SFF v: N/A
    serial: <superuser required> Chassis: type: 4 serial: <superuser required>
  Mobo: Hewlett-Packard model: 339A serial: <superuser required> UEFI: Hewlett-Packard
    v: K01 v03.08 date: 04/10/2019
CPU:
  Info: model: Intel Core i3-3220 bits: 64 type: MT MCP arch: Ivy Bridge gen: core 3 level: v2
    built: 2012-15 process: Intel 22nm family: 6 model-id: 0x3A (58) stepping: 9 microcode: 0x21
  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
  Speed (MHz): avg: 1845 high: 1885 min/max: 1600/3300 scaling: driver: intel_cpufreq
    governor: ondemand cores: 1: 1868 2: 1885 3: 1863 4: 1767 bogomips: 26338
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics vendor: Hewlett-Packard
    driver: i915 v: kernel arch: Gen-7 process: Intel 22nm built: 2012-13 ports: active: VGA-1
    empty: DP-1,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:0152 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: VGA-1 model: Dell E2420H serial: <filter> built: 2020 res: 1920x1080 hz: 60 dpi: 93
    gamma: 1.2 size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes: max: 1920x1080
    min: 720x400
  API: OpenGL v: 4.2 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 2500 (IVB GT1)
    direct-render: Yes
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Hewlett-Packard 7
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20 class-ID: 0403
  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: Intel 82579LM Gigabit Network vendor: Hewlett-Packard driver: e1000e v: kernel
    port: f080 bus-ID: 00:19.0 chip-ID: 8086:1502 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: ASUSTek UT220 Pro wireless/WT300 type: USB driver: hid-generic,usbhid bus-ID: 1-1.4:4
    chip-ID: 0b05:185f class-ID: 0301
Drives:
  Local Storage: total: 585.05 GiB used: 13.3 GiB (2.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: DT01ACA050 size: 465.76 GiB block-size:
    physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: A750
    scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Intel model: SSDSC2CW120A3 size: 111.79 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 400i scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 type: USB model: General size: 7.5 GiB block-size: physical: 512 B
    logical: 512 B type: N/A serial: <filter> rev: 5.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  Message: No partition data found.
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 28.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2425 libs: 1333 tools: apt,apt-get,aptitude,nala 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://mxrepo.com/mx/repo/ bookworm main non-free
    2: deb http://mxrepo.com/mx/repo/ bookworm ahs
Info:
  Processes: 224 Uptime: 34m wakeups: 6 Memory: 7.63 GiB used: 2.99 GiB (39.1%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12 Client: shell wrapper
  v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

did you assign a /boot partition? the installer shouldn't have let you proceed without one if encryption was enabled. I didn't see a /boot in your log.

[andy]

Hello @dolphin_oracle,
Installer failed Phase 3 - Grub installation failed.
Installing on BTRFS with encryption, alongside Windows (EFI partition preserved, formerly there was MX23 alpha, on EXT4 w/o encr.).
Created BRTFS subvolumes @, @home in installer.
minstall.log attached.

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=/antiX/vmlinuz quiet splasht nosplash
  Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23_KDE_beta2_x64 Libretto
    June 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop System: Hewlett-Packard product: HP Compaq Pro 6300 SFF v: N/A
    serial: <superuser required> Chassis: type: 4 serial: <superuser required>
  Mobo: Hewlett-Packard model: 339A serial: <superuser required> UEFI: Hewlett-Packard
    v: K01 v03.08 date: 04/10/2019
CPU:
  Info: model: Intel Core i3-3220 bits: 64 type: MT MCP arch: Ivy Bridge gen: core 3 level: v2
    built: 2012-15 process: Intel 22nm family: 6 model-id: 0x3A (58) stepping: 9 microcode: 0x21
  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
  Speed (MHz): avg: 1845 high: 1885 min/max: 1600/3300 scaling: driver: intel_cpufreq
    governor: ondemand cores: 1: 1868 2: 1885 3: 1863 4: 1767 bogomips: 26338
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics vendor: Hewlett-Packard
    driver: i915 v: kernel arch: Gen-7 process: Intel 22nm built: 2012-13 ports: active: VGA-1
    empty: DP-1,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:0152 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: VGA-1 model: Dell E2420H serial: <filter> built: 2020 res: 1920x1080 hz: 60 dpi: 93
    gamma: 1.2 size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes: max: 1920x1080
    min: 720x400
  API: OpenGL v: 4.2 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 2500 (IVB GT1)
    direct-render: Yes
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Hewlett-Packard 7
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20 class-ID: 0403
  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: Intel 82579LM Gigabit Network vendor: Hewlett-Packard driver: e1000e v: kernel
    port: f080 bus-ID: 00:19.0 chip-ID: 8086:1502 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: ASUSTek UT220 Pro wireless/WT300 type: USB driver: hid-generic,usbhid bus-ID: 1-1.4:4
    chip-ID: 0b05:185f class-ID: 0301
Drives:
  Local Storage: total: 585.05 GiB used: 13.3 GiB (2.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: DT01ACA050 size: 465.76 GiB block-size:
    physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: A750
    scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Intel model: SSDSC2CW120A3 size: 111.79 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 400i scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 type: USB model: General size: 7.5 GiB block-size: physical: 512 B
    logical: 512 B type: N/A serial: <filter> rev: 5.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  Message: No partition data found.
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 28.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2425 libs: 1333 tools: apt,apt-get,aptitude,nala 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://mxrepo.com/mx/repo/ bookworm main non-free
    2: deb http://mxrepo.com/mx/repo/ bookworm ahs
Info:
  Processes: 224 Uptime: 34m wakeups: 6 Memory: 7.63 GiB used: 2.99 GiB (39.1%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12 Client: shell wrapper
  v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

did you assign a /boot partition? the installer shouldn't have let you proceed without one if encryption was enabled. I didn't see a /boot in your log.

In fact, now I am not sure about it. I was trying many things.
I will reinstall once more, albeit on a different machine. Will let you know in a while.

[peter_li]

Does somebody knew why grub.cfg sometimes states root=UUID... and sometimes root=/dev/sdbXX? There are cases where my internal sda is not shown and then sdb becomes to sda and the boot stops in a dash shell.

update-grub generates grub menu entries in two flavours: If it detects a grub-installation on the other OS it uses information found within the grub.cfg file on the other OS. If there is no grub installed on the other OS, it would create generic menu entries with root=/dev/name entries. So you better always install GRUB, to get proper root=UUID=xxxx boot parameter.

@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:

Code: Select all

/dev/sda4@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
/dev/sda7:MX 21.3 Wildflower (21.3):MX:linux
/dev/sdb1:Trisquel GNU/Linux 11.0, Aramo (11.0):Trisquel:linux
/dev/sdb10:Ubuntu 23.04:Ubuntu:linux:btrfs:UUID=58a3a355-2870-487f-a190-0e281d56dc29:subvol=@
/dev/sdb11:Ubuntu 22.04.2 LTS (22.04):Ubuntu1:linux
/dev/sdb12:Void Linux:Void:linux
/dev/sdb13:NuTyX GNU/Linux (rolling):NuTyX:linux
/dev/sdb14:MX 23 Libretto (23):MX1:linux
/dev/sdb2:Ubuntu 23.04 (23.04):Ubuntu2:linux
/dev/sdb3:Debian GNU/Linux 12 (bookworm):Debian:linux
/dev/sdb4:EndeavourOS Linux (rolling):EndeavourOS:linux
/dev/sdb5:Artix Linux (rolling):Artix:linux
/dev/sdb6:Garuda Linux:Garuda:linux:btrfs:UUID=4eec2dc6-51e2-4d0a-9c57-13ffff02ca94:subvol=@
/dev/sdb7:Linux Mint 21.1:Linux:linux:btrfs:UUID=47649cc7-8995-4f70-9b19-19b192fff89c:subvol=@
/dev/sdb8:openSUSE Leap 15.5:openSUSE:linux:btrfs:UUID=36f9708b-432f-4f9f-9dcd-6bb415e37706:subvol=@/.snapshots/1/snapshot

On MX the partitions sdb6 up to sdb10, all on btrfs, were not shown.

[fehlix]

@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.

[fehlix]

Are we going back to apt for updates? When applying updates this morning apt showed and not nala.

We had two nala related reports like "nala hangs" and another one where the "nala hanger",
was actually not nala related but due to a 3min timeout of a not properly provided init-script of ntpsec.
The ntpsec timeout hanger has been fixed. But the other two, could not have been reproduced and so
we decided to go back to apt as default - until we can reproduce and potential help to fix nala, if possible.
User can always enable nala
within ~/.config/MX-Linux/apt-notifier.conf
and change this line

Code: Select all

# Alternative apt/apt-get command line package manager
# use_nala = true

to

Code: Select all

# Alternative apt/apt-get command line package manager
use_nala = true

Can I set the notifier/update window back to 80x24 in size?

It's currently not adjustable, but defaults to terminal with of about 75%-80% of screen size.
I guess with people having now more bigger screen may be adding to a max terminal size.
80x25 can be definitely to small in size as user may have other repos with longer urls,
which would create quite some line-breaks with such a small terminal size.

[andy]

...

did you assign a /boot partition? the installer shouldn't have let you proceed without one if encryption was enabled. I didn't see a /boot in your log.

Indeed, I did not. Why? From former experiences, knowing that installer has a good checking for improper setup (always had halted me, when encryption was enabled and I was trying to have boot on root partition), so I was experimenting, if it finally supports boot on root together with encryption.
So, installer let continue, with wrong (unsupported) setting.
(( Why, in the age of surveillance, when attacks on encryption are much easier, and funded by big entities, we still does not have working LUKS2 (which enables much safer PBKDF)?
What is holding smart programmers from making it working? ))

BUT:
Timeshift does not recognise BTRFS.
(its radio button is disabled)

Code: Select all

$ sudo btrfs subvolume list / 
ID 256 gen 36 top level 5 path @

So, I double checked it (reinstalled once more), same result.

[siamhie]

We had two nala related reports like "nala hangs" and another one where the "nala hanger",
was actually not nala related but due to a 3min timeout of a not properly provided init-script of ntpsec.
The ntpsec timeout hanger has been fixed. But the other two, could not have been reproduced and so
we decided to go back to apt as default - until we can reproduce and potential help to fix nala, if possible.
User can always enable nala
within ~/.config/MX-Linux/apt-notifier.conf
and change this line

Code: Select all

# Alternative apt/apt-get command line package manager
# use_nala = true

to

Code: Select all

# Alternative apt/apt-get command line package manager
use_nala = true

@fehlix I recall beta1 had both "use_nala = true" uncommented. Pretty easy to revert back to nala.

It's currently not adjustable, but defaults to terminal with of about 75%-80% of screen size.
I guess with people having now more bigger screen may be adding to a max terminal size.
80x25 can be definitely to small in size as user may have other repos with longer urls,
which would create quite some line-breaks with such a small terminal size.

That's a shame. It seems to take up a lot of real estate on my 1440 monitor and Jerry mentioned his monitor size of 1366x768 which I can only imagine would take up most of his screen.

[peter_li]

@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?

[TerryL]

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?