MX-21 beta 1 feedback thread

[j.kemp]

I will post my Sysinfo when I get that system back up. Here is a shot of rsync just working away to copy 1.56GB, over twenty rows of dots

https://imgur.com/Bf6pfzN.jpg

[richb]

@j.kemp
Forum Administrator:

Please abide by Forum Rules on image sizes. I have removed the image tags on the link. Users can view it by clicking on the link.

Images added to post via hot links from other websites will be limited to a 640 x 620 pixel size as they appear in the Forum post. Large images take up large areas of the post and thread space, are distracting and impede the flow of the thread. You can post the link to the full image without the [img] tags. Animated images, such as gifs, shall be no larger than 120 x 120 pixels.

[j.kemp]

Thank you.

[j.kemp]

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 lang=en_US kbd=us 
           tz=America/Phoenix persist_root toram gfxsave 
           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: Desktop System: Hewlett-Packard product: HP Z840 Workstation v: N/A 
           serial: <filter> Chassis: type: 6 serial: <filter> 
           Mobo: Hewlett-Packard model: 2129 v: 1.01 serial: <filter> UEFI: Hewlett-Packard 
           v: M60 v02.57 date: 05/21/2021 
CPU:       Topology: 2x 6-Core model: Intel Xeon E5-2620 v3 bits: 64 type: MT MCP SMP 
           arch: Haswell family: 6 model-id: 3F (63) stepping: 2 microcode: 44 
           L2 cache: 30.0 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 114945 
           Speed: 1197 MHz min/max: 1200/3200 MHz Core speeds (MHz): 1: 1197 2: 1198 3: 1197 
           4: 1198 5: 1198 6: 1285 7: 1198 8: 1199 9: 1200 10: 1247 11: 1198 12: 1199 13: 1197 
           14: 1200 15: 1198 16: 1199 17: 1199 18: 1197 19: 1197 20: 1229 21: 1197 22: 1198 
           23: 1197 24: 1198 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: conditional, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GF100GL [Quadro 4000] driver: nouveau v: kernel bus ID: 04:00.0 
           chip ID: 10de:06dd 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: NVC0 v: 4.3 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: Intel C610/X99 series HD Audio vendor: Hewlett-Packard 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:8d20 
           Device-2: NVIDIA GF100 High Definition Audio driver: snd_hda_intel v: kernel 
           bus ID: 04:00.1 chip ID: 10de:0be5 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Intel Ethernet I218-LM vendor: Hewlett-Packard driver: e1000e v: kernel 
           port: 5020 bus ID: 00:19.0 chip ID: 8086:15a0 
           IF: eth1 state: down mac: <filter> 
           Device-2: Intel I210 Gigabit Network vendor: Hewlett-Packard driver: igb v: kernel 
           port: 2000 bus ID: 05:00.0 chip ID: 8086:1533 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 7.76 TiB used: 444.5 MiB (0.0%) 
           ID-1: /dev/sda type: USB vendor: Kingston model: DataTraveler 3.0 size: 28.90 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> rev: PMAP scheme: MBR 
           ID-2: /dev/sde vendor: Western Digital model: WD5000AAKX-60U6AA0 size: 465.76 GiB 
           block size: physical: 512 B logical: 512 B rotation: 7200 rpm serial: <filter> 
           rev: 1H18 scheme: MBR 
           ID-3: /dev/sdf vendor: Seagate model: ST8000VN0022-2EL112 size: 7.28 TiB block size: 
           physical: 4096 B logical: 512 B rotation: 7200 rpm serial: <filter> rev: SC61 
           scheme: GPT 
Partition: ID-1: / raw size: N/A size: 10.93 GiB used: 444.5 MiB (4.0%) fs: overlay 
           source: ERR-102 
Sensors:   System Temperatures: cpu: 44.0 C mobo: N/A gpu: nouveau temp: 70 C 
           Fan Speeds (RPM): N/A gpu: nouveau fan: 2640 
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://la.mxrepo.com/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 383 Uptime: 18m Memory: 15.56 GiB used: 851.3 MiB (5.3%) 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 

[j.kemp]

I have a question about migrating to the new release, which is based on Debian (bullseye). Will that cause a rebuilding from scratch?

If so, how do you all do that?

My system currently runs totally in RAM, about 27.8 GB on my old machine.

Can I use Synaptic to create a script of installed packages, or a pkglist to reinstall all packages on the new system?

I realize I would need to add external repositories with keys.

Can I then copy my home folder over to the new system?

Would that be functional doing it that way?

Is there anything in my home folder that would be in conflict with the release version of the OS?

If these questions are not to be in this thread, please pardon me. I did not see a way to delete it and start a new post. Maybe we can move it? Any time spent doing that would be greatly appreciated.

[dolphin_oracle]

I have a question about migrating to the new release, which is based on Debian (bullseye). Will that cause a rebuilding from scratch?

If so, how do you all do that?

My system currently runs totally in RAM, about 27.8 GB on my old machine.

Can I use Synaptic to create a script of installed packages, or a pkglist to reinstall all packages on the new system?

I realize I would need to add external repositories with keys.

Can I then copy my home folder over to the new system?

Would that be functional doing it that way?

Is there anything in my home folder that would be in conflict with the release version of the OS?

If these questions are not to be in this thread, please pardon me. I did not see a way to delete it and start a new post. Maybe we can move it? Any time spent doing that would be greatly appreciated.

upgrading an installed system is possible, and we will probably have some sort of procedure for that. live-usb users will be better off getting a mx21 iso and starting from that once its released. nothing in your home folder should conflict on Xfce. there are a couple of items that may be a little weird on KDE but are easy to change, but they might not show up in an update anyway.

[j.kemp]

rsync is not functioning properly. My persistent partition is 25GB. When I shut it down, the persist-save shows I only have 16 MiB used. It proceeds on to transfer 1.46 GiB. I have been watching it fill over 20 rows of dots. The previous time, I aborted. The system would boot, but not load the desktop. I rebuilt the USB and all seem well again. Went to shut down and save again, the same thing. This will need to be fixed. Can someone else confirm this is happening on their end?

Update: It will not finish. After 30 minutes, it is still painting dots on the screen.

[dolphin_oracle]

rsync is not functioning properly. My persistent partition is 25GB. When I shut it down, the persist-save shows I only have 16 MiB used. It proceeds on to transfer 1.46 GiB. I have been watching it fill over 20 rows of dots. The previous time, I aborted. The system would boot, but not load the desktop. I rebuilt the USB and all seem well again. Went to shut down and save again, the same thing. This will need to be fixed. Can someone else confirm this is happening on their end?

Update: It will not finish. After 30 minutes, it is still painting dots on the screen.

I have not encountered this.

what kind of stick do you have?

[Magister]

Works fine on my Dell Latitude E5470.

However I discovered a problem by after.
My SSD (UEFI) is half windows and half mxlinux. I installed MX21 and everything was fine, GRUB and all, dual boot.
I then re-installed Windows by booting on a USB, manual install so I delete the windows partitions (EFI, the 16MB one, OS), it recreates all of them, install win10, all ok.
Of course GRUB is overwritten, so I reboot on the MX Linux USB, choose "Boot Repair" to re-install GRUB on ESP, and it fails with a simple "cannot mount /boot/efi".
Checking the /var/log/mxbootrepair.log (not sure of the name) I see it is trying to mount the sda1 partition using the UUID it founds in my /etc/fstab (my sda5 root partition) but as I deleted and windows install re-created the partition, the UUID had changed. I checked the new UUID with gparted, mounted my sda5 in /mnt, modified the fstab, unmounted, then relaunched the "MX Boot Repair" and it worked.

All of this to say that the "MX Boot Repair" may

1 - Use better error message, more descriptive
2 - find the UUID using blkid instead of mounting the old root and checking its fstab

Hope it helps!

[Adrian]

1 - Use better error message, more descriptive
2 - find the UUID using blkid instead of mounting the old root and checking its fstab

1. - I wish I could provide more info but all the info the program gets is that the mount command failed...
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?