MX-19 Beta 1 Feedback

[dolphin_oracle]

Error exiting from Live USB after completed HDD installation...
Exit-error.JPG

anything special you had mounted??

[dolphin_oracle]

Quick first impressions: I like the clear panel default. I like Conky up in the right hand corner, but the default clock in Conky is distracting. Having menubar enabled by default in the terminal might be useful for new users. The default icons seem tiny, smaller than in MX 18 anyway, and they don't appear to expand like they should when I increase the panel bar unless I make it huge. Would be interesting if it seems the same on larger screens, this is on a 12" screen.
So far MX 19 is working great on my X220 Thinkpad. Next will try it on my other Lenovo 11e laptop as well as my HP laptop.

Edit 1: I must be having some of the same intel issues mentioned earlier in this thread. On my HP laptop it will not launch at all when I select the drive MX is installed on in the bios. It skips to the default Debian install on that machine. On my Lenovo 11e it gets past Plymouth screen then crashes.

Edit 2: My Acer C720 laptop boots up fine with MX 19.

Edit 3: I can boot the live version of MX 19 on my HP laptop with the Sandybridge cpu and intel graphics. And I can run a full install of MX 18 on it, but not a full install of MX 19.

My Lenovo 11e with a Bay Trail cpu and intel graphics will not boot a live or installed version of MX 19, but it boots up an installed version of MX 18 without issue. If any other info is needed let me know.

what is the symptom of "not booting?" I ask because many folks mistake not bootin for X not starting or some other issue.

[dolphin_oracle]

Can anyone test if the nvidia-persistenced file installs successfully if you boot with systemd?

I did get the same error message on my Optimus system weeks ago when I tried a backport of the 430 driver from experimental, which didn't work, so reinstalled our MX 18 test repo version of 418.74 from my local repo. But I just removed the package to no ill effect to fix that issue. I couldn't figure out what package was pulling it in either...maybe our installer could remove it as the last step if it's present and then fix the system.

I know it's an ugly workaround, but the alternative is to find out what's pulling it in, rebuild the package to stop that happening, and possibly then breaking the system if you boot it with systemd.

I am in systemd now, or rather

Code: Select all

ps aux | less

has a systemd thing right at the top, so.. I wager that is it, even though the boot whined about not being able to boot due to missing .. something. It was gone before I knew it.

Of course nvidia is already installed here, as is nvidia-persistenced. Reinstalling throws an error..

can you tell me what you want me to do exactly? (back in 18.3 now, but holler if you see me)

re-install nvidia-persistenced while running in systemd mode. you may have to purge it first

Code: Select all

apt purge nvidia-persistenced

[colin_b]

Sorry for butting in, but I've found something which should be mentioned. If I leave it I'm sure I'll forget.

https://www.youtube.com/watch?v=MKVUzScmS00 has a review of MX 19, and at about 6 min it talks about a problem with wireless transfers and how a program installation solves the problem.

If this software is required to get things working is it go to be included in MX 19?

[dolphin_oracle]

Sorry for butting in, but I've found something which should be mentioned. If I leave it I'm sure I'll forget.

https://www.youtube.com/watch?v=MKVUzScmS00 has a review of MX 19, and at about 6 min it talks about a problem with wireless transfers and how a program installation solves the problem.

If this software is required to get things working is it go to be included in MX 19?

already done

[colin_b]

already done

I should have guessed

[caprea]

I just purged, installed and reinstalled nvidia-persistenced while NOT in systemd mode. Seems to work now without errors.

[dolphin_oracle]

I just purged, installed and reinstalled nvidia-persistenced while NOT in systemd mode. Seems to work now without errors.

thanks for the update!

[KBD]

what is the symptom of "not booting?" I ask because many folks mistake not bootin for X not starting or some other issue.

The HP laptop skips past my selection to boot a full install of MX 19 like it isn't even there and boots into my Debian install instead. It boots into the Live version of MX 19, but a full install does nothing. Something happening after the installation.

The Lenovo 11e laptop starts to boot a full install but gets hung up after plymouth screen. Same thing with live MX 19. Looks a graphic issue on the Lenovo 11e which has a Bay Trail cpu, I think that one is a system on a chip deal.

[dolphin_oracle]

for the baytrail, go with "nosplash" boot code to disable plymouth.

for the HP, sounds like secure boot is still enabled.