MX-19 Beta 1 Feedback
Re: MX-19 Beta 1 Feedback
Here's the new packages, ignore the dbgym packages as usual.
https://drive.google.com/open?id=1y3jrh ... Cv-gKvn_ek
Wait, they are uninstallable, since we don't have xiccd (yet). Let me backport that.
OK, here's xiccd. Install that deb for your architecture first. https://drive.google.com/open?id=1q7V_H ... KNiu4UoxGi
https://drive.google.com/open?id=1y3jrh ... Cv-gKvn_ek
Wait, they are uninstallable, since we don't have xiccd (yet). Let me backport that.
OK, here's xiccd. Install that deb for your architecture first. https://drive.google.com/open?id=1q7V_H ... KNiu4UoxGi
- entropyfoe
- Posts: 615
- Joined: Thu Apr 19, 2007 11:42 am
Re: MX-19 Beta 1 Feedback
OK, I am impressed.
Downloaded 64 nit, the md5 is good. A couple minutes to get it on an old USB 2 stick. It booted with the option toram. Everything worked after the sound card was selected. So, I installed to my 4th test partition, I think a window popped up during the install like it was automounting the drives. I closed it and proceeded.
Installed as normal. I rebooted, went into MX 18.3, and did the update-grub thing. Booted into the MX-19 beta1.
Selected the sound card. Sound works. Wired eth0 works. Enabled the data drive with disk manager, set wallpaper. synaptic installed 129 packages including dependencies.
Installed the nvidia driver with the MX tool. Got the 418.74. Rebooted normally, driver is in use. The machine boots to about 520MB of RAM.
Suspend and wake works, 3 second sound resumes, 7 sec to the full system is back.
Earlier comments were about open root thunar here. That function seems to work here on folders.
Also, catfish works finding files fast.
Hmm, samba seems not to be working. This is one of the MX magical OTB things that usually just works, to my amazement, my windows machine just shows up, and files area accessible with authentication.But in this beta, the windows machine is not showing up. samba is installed, and the configuration does not show a way to find the network shares on the Win 7 machine.
I just did 4 synaptic updates, and got this error message at completion
So far very fast and stable, needs more testing and messing about. The samba- would like to get it working, I use that often.
Downloaded 64 nit, the md5 is good. A couple minutes to get it on an old USB 2 stick. It booted with the option toram. Everything worked after the sound card was selected. So, I installed to my 4th test partition, I think a window popped up during the install like it was automounting the drives. I closed it and proceeded.
Installed as normal. I rebooted, went into MX 18.3, and did the update-grub thing. Booted into the MX-19 beta1.
Selected the sound card. Sound works. Wired eth0 works. Enabled the data drive with disk manager, set wallpaper. synaptic installed 129 packages including dependencies.
Installed the nvidia driver with the MX tool. Got the 418.74. Rebooted normally, driver is in use. The machine boots to about 520MB of RAM.
Suspend and wake works, 3 second sound resumes, 7 sec to the full system is back.
Earlier comments were about open root thunar here. That function seems to work here on folders.
Also, catfish works finding files fast.
Hmm, samba seems not to be working. This is one of the MX magical OTB things that usually just works, to my amazement, my windows machine just shows up, and files area accessible with authentication.But in this beta, the windows machine is not showing up. samba is installed, and the configuration does not show a way to find the network shares on the Win 7 machine.
I just did 4 synaptic updates, and got this error message at completion
Code: Select all
E: nvidia-persistenced: installed nvidia-persistenced package post-installation script subprocess returned error exit status 1
So far very fast and stable, needs more testing and messing about. The samba- would like to get it working, I use that often.
MX 23.5 on Asus PRIME X470-PRO
AMD Ryzen 3600X (12 threads @ 3.8 GHz)
32 Gig DDR4 3600 (Crucial CL 16)
Nvidia GeForce GT 710
Samsung 970 NVMe nvme0n1 P1-3=MX-23.5, P4=testing
Samsung 980 NVMe =1TB Data, plus 2TB WD =backups
on-board ethernet & sound
AMD Ryzen 3600X (12 threads @ 3.8 GHz)
32 Gig DDR4 3600 (Crucial CL 16)
Nvidia GeForce GT 710
Samsung 970 NVMe nvme0n1 P1-3=MX-23.5, P4=testing
Samsung 980 NVMe =1TB Data, plus 2TB WD =backups
on-board ethernet & sound
Re: MX-19 Beta 1 Feedback
1. Frugal_static installation worked with no problems.
2. The desktop's display was garbled after booting then auto-logging in as demo the very first time but it cleared up in a few seconds except that the panel looks partially white like this:

Changing themes in Settings/Appearance, enabling a compositor in MX Tweak, or doing anything in Panel Preferences didn't fix it, but logging out and back in did:

After a restart I had the garbling for just a fraction of a second, then it went to a dark screen with the (normal looking) panel, then the desktop wallpaper and conky loaded and everything looks fine. I rebooted again a few minutes later and there was no garbling at all.
3. Development/Icon Browser is slow to load icons. It takes over 10 seconds. My past experience with a frugal_static installation of MX 18.3 was that everything ran as fast as on an installed system so I don't know what's happening here. Maybe it has something to do with my system and the recent CPU upgrade? I did underclock the new CPU from 2.8GHz to 2.6GHz and also lowered the CPU voltage by two "notches" so it would run cooler. I haven't had any stability issues so far in my installed MX 18.3 though. Or maybe that app is just slow?
4. I can't duplicate any of the issues that others are reporting. All of the MX Tools I've tested launch OK, and I can open a root Thunar wherever I like. Firefix, GIMP, the updater works, and many other apps that I've tested all open.
5. I saved my testing notes and QSI info in Documents and my two screencaps in Pictures within Demo's home directory thinking they'd be available in my frugal partition later when I booted back into 18.3 but they were nowhere to be found. They weren't in Live-usb-storage/demo/ on the USB either. I had to boot back into 19b1 and copy/paste them into /media/jay/antiX-Frugal/Live-usb-storage/demo/ to make them available in 18. I wonder where Demo's home directory is? Within the squashfs? Again this seems different from my previous experience of an MX-18 frugal installation.
2. The desktop's display was garbled after booting then auto-logging in as demo the very first time but it cleared up in a few seconds except that the panel looks partially white like this:

Changing themes in Settings/Appearance, enabling a compositor in MX Tweak, or doing anything in Panel Preferences didn't fix it, but logging out and back in did:

After a restart I had the garbling for just a fraction of a second, then it went to a dark screen with the (normal looking) panel, then the desktop wallpaper and conky loaded and everything looks fine. I rebooted again a few minutes later and there was no garbling at all.
3. Development/Icon Browser is slow to load icons. It takes over 10 seconds. My past experience with a frugal_static installation of MX 18.3 was that everything ran as fast as on an installed system so I don't know what's happening here. Maybe it has something to do with my system and the recent CPU upgrade? I did underclock the new CPU from 2.8GHz to 2.6GHz and also lowered the CPU voltage by two "notches" so it would run cooler. I haven't had any stability issues so far in my installed MX 18.3 though. Or maybe that app is just slow?
4. I can't duplicate any of the issues that others are reporting. All of the MX Tools I've tested launch OK, and I can open a root Thunar wherever I like. Firefix, GIMP, the updater works, and many other apps that I've tested all open.
5. I saved my testing notes and QSI info in Documents and my two screencaps in Pictures within Demo's home directory thinking they'd be available in my frugal partition later when I booted back into 18.3 but they were nowhere to be found. They weren't in Live-usb-storage/demo/ on the USB either. I had to boot back into 19b1 and copy/paste them into /media/jay/antiX-Frugal/Live-usb-storage/demo/ to make them available in 18. I wonder where Demo's home directory is? Within the squashfs? Again this seems different from my previous experience of an MX-18 frugal installation.
Code: Select all
System: Host: mx1 Kernel: 4.19.0-5-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19beta-1_x64 patito feo August 25 2019 base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop Mobo: ASRock model: A780GM-LE serial: <filter>
BIOS: American Megatrends v: P1.50 date: 05/25/2010
CPU: Topology: Quad Core model: AMD Phenom II X4 925 bits: 64 type: MCP arch: K10
family: 10 (16) model-id: 4 stepping: 2 microcode: 10000DB L2 cache: 2048 KiB
flags: lm nx pae sse sse2 sse3 sse4a svm bogomips: 20755
Speed: 800 MHz min/max: 800/2600 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 1600
Vulnerabilities: Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass status: Not affected
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, STIBP: disabled, RSB filling
Graphics: Device-1: AMD RS780 [Radeon HD 3200] vendor: ASRock driver: radeon v: kernel
bus ID: 01:05.0 chip ID: 1002:9610
Display: x11 server: X.Org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa
resolution: 1280x1024~60Hz
OpenGL: renderer: AMD RS780 (DRM 2.50.0 / 4.19.0-5-amd64 LLVM 7.0.1)
v: 3.3 Mesa 18.3.6 compat-v: 3.0 direct render: Yes
Audio: Device-1: AMD SBx00 Azalia vendor: ASRock driver: snd_hda_intel v: kernel
bus ID: 00:14.2 chip ID: 1002:4383
Sound Server: ALSA v: k4.19.0-5-amd64
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock
driver: r8169 v: kernel port: e800 bus ID: 02:00.0 chip ID: 10ec:8168
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 1.03 TiB used: 3.45 GiB (0.3%)
ID-1: /dev/sda vendor: Gigabyte model: GP-GSTFS31120GNTD size: 111.79 GiB block size:
physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 61.3 scheme: MBR
ID-2: /dev/sdb vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB block size:
physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter>
rev: CC43
ID-3: /dev/sdc type: USB vendor: Toshiba model: TransMemory size: 14.45 GiB
block size: physical: 512 B logical: 512 B serial: <filter> rev: 1.00 scheme: MBR
Partition: ID-1: / raw size: N/A size: 7.81 GiB used: 41.4 MiB (0.5%) fs: overlay
source: ERR-102
Sensors: Message: No sensors data was found. Is sensors configured?
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/buster buster main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian buster main contrib non-free
2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 202 Uptime: 3m Memory: 7.55 GiB used: 510.0 MiB (6.6%) Init: SysVinit
v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3
running in: quick-system-in inxi: 3.0.33
Last edited by JayM on Tue Aug 27, 2019 1:45 am, edited 2 times in total.
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.
Re: MX-19 Beta 1 Feedback (frugal-persist woes?)
You're absolutely right: i had copied /antiX-Frugal-4.19.0-5-amd64/boot/grub/grub.cfg instead of /antiX-Frugal-4.19.0-5-amd64/grub.entryfehlix wrote: Mon Aug 26, 2019 8:00 pm The frugal-directory is correctly named: "/antiX-Frugal-4.19.0-5-amd64".
The created grub.entry shall work if you copy it into an existing grub-install under /boot/grub/custom.cfg,
Working well now, persistence and all.
Re: MX-19 Beta 1 Feedback
Just found out about MX recently and wanted to try out XFCE 4.14, so I'm writing this from the MX-19 Beta! So far things are running very well. Nice work dev team! Also, it is great to see another non-systemd distro, although I am not completely opposed to systemd, I am glad there are options out there.
I did notice a small quirk when booting into the system using full disk encryption. If you have a very long passphrase, it goes outside the display box. Other distros handle this better and hide any input that goes outside the box. Here's a photo for reference:

I did notice a small quirk when booting into the system using full disk encryption. If you have a very long passphrase, it goes outside the display box. Other distros handle this better and hide any input that goes outside the box. Here's a photo for reference:

Re: MX-19 Beta 1 Feedback
MX-18 does that too. I just ignore it. But if it's something that can be changed or tweaked to make MX look nicer this is a good time to suggest it. 

Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.
Re: MX-19 Beta 1 Feedback
I've seen this too, not sure how easy it would be to fix that. Another option is to open MX Boot Options, select the Tribar theme and you'll be sorted.
Re: MX-19 Beta 1 Feedback
If it works in other boot themes maybe the default one can be modified to hide overflow characters? I wouldn't have the slightest idea how to go about doing that though.
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.
Re: MX-19 Beta 1 Feedback
Root Terminal disappeared?
Re: MX-19 Beta 1 Feedback
I've never encountered this problem at all, and I've tried all the early alphas.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400