
MX-21 beta 1 feedback thread
- Eadwine Rose
- Administrator
- Posts: 14478
- Joined: Wed Jul 12, 2006 2:10 am
Re: MX-21 beta 1 feedback thread
Just a bump to push this back up after yours truly made a booboo 

MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Re: MX-21 beta 1 feedback thread
1 - I understand :-/Adrian wrote: Thu Aug 19, 2021 4:41 pm1. - I wish I could provide more info but all the info the program gets is that the mount command failed...1 - Use better error message, more descriptive
2 - find the UUID using blkid instead of mounting the old root and checking its fstab
2. - I can use blkid to to get UUIDs but then how do I know which UUID corresponds to the partition that you are looking for?
2 - it was not mounting the efi partition, but I specified /dev/sda1, and blkid will report the UID "XXXX-XXXX" format and the PARTLABEL is "EFI System Partition" so it could be guessed from that maybe? Especially since the UUID from fstab was different than the one in blkid. Maybe just display in a popup that there is a UUID discrepancy and ask if we want to use the other one to mount efi ? This implies modifying the root partition mounted in /tmp to modify the etc/fstab
Dual booting may be important for a lot of people, especially people new to Linux, and after they re-install windows it would be nice that the repair works fine

HP Mini311 - N270@2GHz - 3/120 - Geforce 9400M - MX21.3
Dell Latitude E5470 - i5-6200U - 8/256 - MX23
Bee-link SER5 - Ryzen 5 5600H - 32/1500 - MX23
Dell Latitude E5470 - i5-6200U - 8/256 - MX23
Bee-link SER5 - Ryzen 5 5600H - 32/1500 - MX23
Re: MX-21 beta 1 feedback thread
1. I wonder if the mount exit status would help. Mount command manual (Fedora) states:Adrian wrote: Thu Aug 19, 2021 4:41 pm1. - I wish I could provide more info but all the info the program gets is that the mount command failed...1 - Use better error message, more descriptive
2 - find the UUID using blkid instead of mounting the old root and checking its fstab
2. - I can use blkid to to get UUIDs but then how do I know which UUID corresponds to the partition that you are looking for?
Code: Select all
EXIT STATUS
mount has the following exit status values (the bits can be ORed):
0 success
1 incorrect invocation or permissions
2 system error (out of memory, cannot fork, no more loop devices)
4 internal mount bug
8 user interrupt
16 problems writing or locking /etc/mtab
32 mount failure
64 some mount succeeded
The command mount -a returns 0 (all succeeded), 32 (all failed), or 64 (some failed, some succeeded).
Re: MX-21 beta 1 feedback thread
IIRC, removing EFI System partition and create a new one, might not be really needed for installing an additonal OS. I'm not sure Windows is requiring to create a new ESP when re-installing. Even as ESP is a system partition, removing all files and folder on the ESP would be ok. MX Boot Repair would just work fine and re-populate the existing ESP.Magister wrote: Fri Aug 20, 2021 7:54 am Dual booting may be important for a lot of people, especially people new to Linux, and after they re-install windows it would be nice that the repair works fine![]()
Re: MX-21 beta 1 feedback thread
AK-47, I will probably get only 32. Fehlix makes a good point that you don't need to recreate ESP.
I will try to implement some UUID validation and prompts if they don't match, maybe a project for the weekend...
I will try to implement some UUID validation and prompts if they don't match, maybe a project for the weekend...
Re: MX-21 beta 1 feedback thread
Dear all
Try to install on HP EliteBook 8540w, but at the end, GRUB cannot install. First try with disk encryption, next w/o. Both the same. Before was MX 19.4 AHS installed in UEFI mode, works fine. Thank you all for new MX 21 :-) Booting is very fast..
Try to install on HP EliteBook 8540w, but at the end, GRUB cannot install. First try with disk encryption, next w/o. Both the same. Before was MX 19.4 AHS installed in UEFI mode, works fine. Thank you all for new MX 21 :-) Booting is very fast..
Code: Select all
System: Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash
Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-21_beta1_x64 Wildflower July 27 2021 base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Laptop System: Hewlett-Packard product: HP EliteBook 8540w v: N/A
serial: <filter> Chassis: type: 10 serial: <filter>
Mobo: Hewlett-Packard model: 1521 v: KBC Version 32.36 serial: <filter>
UEFI: Hewlett-Packard v: 68CVD Ver. F.60 date: 11/11/2015
Battery: ID-1: BAT0 charge: 61.6 Wh condition: 64.8/64.8 Wh (100%) volts: 16.8/14.4
model: Hewlett-Packard Primary type: Li-ion serial: <filter> status: Charging
CPU: Topology: Quad Core model: Intel Core i7 Q 720 bits: 64 type: MT MCP arch: Nehalem
family: 6 model-id: 1E (30) stepping: 5 microcode: A L2 cache: 6144 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 25538
Speed: 931 MHz min/max: 933/1600 MHz boost: enabled Core speeds (MHz): 1: 931 2: 931
3: 931 4: 931 5: 931 6: 931 7: 931 8: 931
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds
status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: NVIDIA GT216GLM [Quadro FX 880M] vendor: Hewlett-Packard driver: nouveau
v: kernel bus ID: 01:00.0 chip ID: 10de:0a3c
Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa
resolution: 1600x900~60Hz
OpenGL: renderer: NVA5 v: 3.3 Mesa 20.3.5 direct render: Yes
Audio: Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:3b56
Device-2: NVIDIA GT216 HDMI Audio vendor: Hewlett-Packard driver: snd_hda_intel
v: kernel bus ID: 01:00.1 chip ID: 10de:0be2
Sound Server: ALSA v: k5.10.0-8-amd64
Network: Device-1: Intel 82577LM Gigabit Network vendor: Hewlett-Packard driver: e1000e
v: kernel port: 4020 bus ID: 00:19.0 chip ID: 8086:10ea
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel Centrino Advanced-N 6200 driver: iwlwifi v: kernel port: 3000
bus ID: 03:00.0 chip ID: 8086:4239
IF: wlan0 state: down mac: <filter>
Drives: Local Storage: total: 144.23 GiB used: 5.98 GiB (4.1%)
ID-1: /dev/sda vendor: OCZ model: VERTEX2 size: 107.13 GiB block size:
physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 1.37 scheme: GPT
ID-2: /dev/sdb type: USB vendor: Transcend model: JetFlash Transcend 32GB
size: 29.44 GiB block size: physical: 512 B logical: 512 B serial: <filter> rev: 1.00
scheme: MBR
ID-3: /dev/sdc type: USB vendor: Buffalo model: USB Flash Disk size: 7.66 GiB
block size: physical: 512 B logical: 512 B serial: <filter> rev: 4000 scheme: MBR
Partition: ID-1: / raw size: N/A size: 6.10 GiB used: 333.6 MiB (5.3%) fs: overlay
source: ERR-102
Sensors: System Temperatures: cpu: 56.0 C mobo: N/A gpu: nouveau temp: 59 C
Fan Speeds (RPM): N/A
Repos: 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 bullseye-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bullseye main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ bullseye main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 265 Uptime: 12m Memory: 7.69 GiB used: 1.59 GiB (20.7%) Init: SysVinit
v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in
running in: quick-system-in inxi: 3.0.36
You do not have the required permissions to view the files attached to this post.
Re: MX-21 beta 1 feedback thread
I have a Kingston Data Traveler 64GBI have not encountered this.
what kind of stick do you have?
I think you're right. I tried an old PNY 64GB and it worked.
Re: MX-21 beta 1 feedback thread
The Popular Applications tab, in the MX Package Installer, list a LAMP package under server. When installing, it cannot find php7.3. I search the repository and can only find php7.4 which is good (version wise) but the installation fails due to that.
- dolphin_oracle
- Developer
- Posts: 22103
- Joined: Sun Dec 16, 2007 12:17 pm
Re: MX-21 beta 1 feedback thread
THANKS!j.kemp wrote: Fri Aug 20, 2021 2:01 pm The Popular Applications tab, in the MX Package Installer, list a LAMP package under server. When installing, it cannot find php7.3. I search the repository and can only find php7.4 which is good (version wise) but the installation fails due to that.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Re: MX-21 beta 1 feedback thread
Can anyone else confirm that xscreensaver can not find the rss-glx fancy screensavers, per this bug report? https://bugs.debian.org/cgi-bin/bugrepo ... bug=979490
Since the bug report includes a patch to fix rss-glx, we can rebuild an MX version that works with xscreensaver 5.45
Since the bug report includes a patch to fix rss-glx, we can rebuild an MX version that works with xscreensaver 5.45