Feedback thread for MX-Base ISO's

[m_pav]

ANY REASON WHY IT IS BLOCKED/BLACKLISTED BY DEFAULT

Please do not shout.

I have never seen that before though my systems do not use the WL driver. Booting up base64 in VBox, the only blacklisted drivers are particular Broadcom drivers.

Here's something you might not know, but that might assist in the future. If you have enough RAM, when running live, go ahead and check for updates, then install everything and answer Y if presented (you will be asked because a VirtualBox update has been rolled out).

The updates will not be wasted because whatever system changes you make will be integrated when the installer is run, and for the Base ISO's, there is a switch to a more efficient driver stack which came out just after I finished building the ISO's. Where low level driver changes are concerned, a reboot is always the best policy, which is effected post install.
Desktop changes are not automatically integrated, there's a checkbox for that in the installer if you want to use it.

In my experience, desktop aberrations such as the display not "painting" the latest change are 75% related to drivers and on your particular laptop, you might be better off switching to the 4.09 LTS kernel, it will be better matched to your processors capabilities.

[mrhalloween]

I can't download MX-19.2_base_x32.iso or MX-19.2_base_x64.iso. I am redirect back to https://sourceforge.net/projects/mx-linux/files/ in both Brave browser and Firefox.

[Jerry3904]

Then click on the Community Respond folder to open it.

[BitterTruth]

Please do not shout.

Apologies. I was trying to make it stand out, shouldv'e used bold instead.

I have never seen that before though my systems do not use the WL driver. Booting up base64 in VBox, the only blacklisted drivers are particular Broadcom drivers.

Here's something you might not know, but that might assist in the future. If you have enough RAM, when running live, go ahead and check for updates, then install everything and answer Y if presented (you will be asked because a VirtualBox update has been rolled out).

The updates will not be wasted because whatever system changes you make will be integrated when the installer is run, and for the Base ISO's, there is a switch to a more efficient driver stack which came out just after I finished building the ISO's. Where low level driver changes are concerned, a reboot is always the best policy, which is effected post install.
Desktop changes are not automatically integrated, there's a checkbox for that in the installer if you want to use it.

In my experience, desktop aberrations such as the display not "painting" the latest change are 75% related to drivers and on your particular laptop, you might be better off switching to the 4.09 LTS kernel, it will be better matched to your processors capabilities.

There's been all sorts of things going on. I've been playing with it all day and like I said it was my dad's daily driver laptop (for all that he only watches his youtube playlist on it), so when I got excited and installed the MX19.2_base iso on it and wiped the Lubuntu off it, he wasn't too pleased when it didn't work.

I have the broadcom bcm4322 wifi in it. Funny thing is during the live session, loading the 'wl' driver worked (that's why i got excited and installed it). My home networks and my phone hotspot were detected. After the install and subsequent restart, however, neither was working so I unloaded the 'wl' driver and loaded the b43. Bam! phone hotspot working but home wifi still not working. I blacklisted the other drivers and did all the updates followed by a reboot. Still no home wifi. Tried some of the suggestions in the other MXlinux threads and Ubuntu ones, watched Dolphins video on it, no joy.

The issue with the panel never came back. I must have reinstalled the iso about 7/8 times now, if not more. I've selected 'save desktop changes' during installation so I don't know why it removes the 'wl' driver after reboot. I found something here which might be of interest to you:

viewtopic.php?f=92&t=36348&start=30 (post #34) something about broadcom-sta-dkms package not being on the iso image.

You may be right about the kernels, although Lubuntu 20.04.1 is using the 5.4 kernel which works. For what it's worth, i ran it on VBox before putting on the compaq and it ran really well on my ThinkpadT410.
Also, the splash screen during the live session startup doesn't come up after installing. It would be nice to have that same 'quiet splasht splash' parameter permanent.

Anyway, i hope that's enough feedback for you.

[Jerry3904]

After it's installed, can you use MX Network Assistant to correct the driver?

[JayM]

The x64 iso is downloading today. After installing in VirtualBox I had some screen flicker when changing the focus between two open window. I ran MX Tweak, Compositor tab, changed VBlank from "auto" to "xpresent" to stop the flicker. Other than that, no problems. It's basically bog-standard MX Linux only with things like LibreOffice, GIMP, VLC, Clementine not preinstalled. It seems faster to boot too, though I don't know why that would be so. It seems to be very stable. I haven't seen any glitches or gotchas so far.

Now I want to try the 32-bit Fluxbox-only version to see how that was done as MX Fluxbox depends a lot on Xfce for stuff such as Featherpad and Thunar. I'm curious if m_pav substituted a non-DE-specific text editor and file manager or what.

[JayM]

Ah, I see how it was done. MX Fluxbox is just the default X session instead of Xfce. I can still log out and select Xfce from the "peanut icon" in LightDM Greeter and get the standard MX desktop.

Speaking of desktops, this version of the base respin doesn't like VMSVGA video default in VirtualBox. After installing the guest editions, rebooting the guest, then auto-resizing the guest display nothing ever happens, and if I restart after the attempt to resize the guest display I get a (small) black screen with a mouse cursor instead of the desktop. I had to change the VM's display settings to VBoxSVGA to get it to work. Hope this will help others.

[BitterTruth]

@jaym yes I've been setting it to vboxsvga for the past few times as well and I've probably setup 10 or 15 different linux VM with different distros in the last few days. So it's not just this iso or mx19.2. We did get a vbox update a couple of days ago but even my previous version was the same. Vbox has moaned and given me the 'invalid settings detected' every time but it works well if I leave the 3d acceleration unchecked. My resolution is pretty good, stays after reboot and i can resize properly too.

EDIT: The boot time seemed slightly faster to me as well which led me to wonder if some modules, drivers were not being loaded but I'm not knowledgeable enough to be able to tell :)
m_pav has made a lot of suble tweaks (and obviously put a lot of work in) like in the installer when you type the password the 'bullet point' characters are larger and the red and green colours for password check are more vivid for me.

It would be nice to get a list of what has been removed/tweaked when he has time.

[nbarrera]

Hi guys, I tried to install mx linux 19 on a 4gb ssd old drive.
I found the installer asks at least 6gb free for the root partition.

I thought this mx base would be lighter and maybe fit into such a small size requirement but no.. I found the exact same limit of 6gb.

I 've researched before asking and found this recommendation:
viewtopic.php?t=42981#p422325

which I tired to follow but still got the same 6gb restriction.

maybe 4gb is too few even for this "base" version of mx, is this be true?

thanks!

[dolphin_oracle]

4gb is probably too small, but you can override the size check in /usr/share/gazelle-installer-data/installer.conf if you are feeling lucky.