MX-17 Beta 1 Feedback Thread

[berlin59]

With boot-repair-disk I first tried to remove all Kernels and reinstall the latest Kernel for the Peppermint-8 OS on sda6.
It never finished, so I closed the program and used the OS-remover for Peppermint-8 on sda4.
That installed the grub new into the esp I hope.

After restart, the gap of 45 seconds was gone.
The Toshiba screen appeared and after 2 seconds, within a split-second the grub-menu appeared.
It says GNU GRUB Version 2.02 beta2-36ubuntu3.9
The menu was a big surprise because there are old and rotten entries from Solus-3. The entry for Peppermint is missing

What else is there ?
- Windows UEFI bootmgfw.efi
- Windows Boot UEFI loader
- EFI/goofiboot/goofibootx64.efi
- EFI/ubuntu/fbx64.efi
- EFI/ubuntu/fwupx64.efi
- EFI/ubuntu/mmx64.efi
- EFI/ubuntu/MokManager.efi
- Windows Boot Manager (on /dev/sda1)
- MX-16.1 Metamorphosis (16.1) (on /dev/sda8)
Advanced options for ...
and MX 17 Horizon ... with advanced options

I thought I had cleaned the goofiboot entry long time ago, it is from Solus-3, but now it shows up again ?

And all the ubuntu-entries ?

Do you have an idea how to clean this mess up ?

[richb]

I cannot vouch for this but it sounds like this is what happened to you.

Now you should also delete the ubuntu subdirectory in the EFI partition to prevent the UEFI firmware from restoring the entry into the BootOrder.

Procedure is in the second post.

https://askubuntu.com/questions/63610/h ... -menu-uefi

[berlin59]

Thank you very much to all who helped me.

I don't know how and why I got to the solution, but it is there.
richb, your comment came too late, sorry.

I googled and found somebody who said I should edit the files in /etc/grubd .
I found the file "25_custom" there where I deleted the entries which did not work in the grub-menu. entries like goofibootx64.efi
or fbx64.efi etc.

Then after sudo update-grub and restart, they were gone in the grub-menu.

If you ask me why they weren't there not before I asked for help ( they were not present in the MX-16 nor in the MX-17 grub-menu ), I think I know the answer.
These old entries were on the partition where LinuxMint 18.2 is installed, they sat there in that grubd-folder inside the 25_custom file all the time. But this OS was not the default OS from which the grub-menu was displayed, therefore it only showed up after I experimented with boot-repair-disk, not knowing exactly what it did.

Obviously not the way others than me should experiment on their machines.

But the laptop is not my production machine, for that I have the PC which has the old fashioned MBR and not Uefi.
No distro ever caused problems on that PC, they all manage the grub perfectly.

Thanks again for your kind help.
I appreciate it very much.

For me this problem is solved now.

[ferlop]

I have installed MX-16.1 (September) and runs pretty well. Indeed, it is a very good distro. Two days ago I tried live MX-17 B1 (and before a4 and a5) and noticed that ram consumption is much higher than MX-16.1 live. Why is that? It can be explained? Thanks.

Not sure how much it consumes on your system ,on mine very little, 4 core AMD, but you can try turning off the conky and see what results. MX Conky and click stop.

Hello.

My computer is a very old one: desktop Dell Optiplex 5200 with a 3,4 GHZ Dual Core Processor, 4 GB Ram.

The MX16.1 live session and the HDD installation: flows between 230-240 MB of ram after starting.

The MX-17 testing (alphas and beta 1): more than 600 MB of ram. Even when conky is disabled it never reaches that low value of ram consumption as the 16.1 does.

MX-17 is not so fast and smooth oppening applications as MX-16.1.

I've got a laptop Lenovo T61 (very old one as well): I am going to do the same job to verify the performance.

Thanks for your answer

[richb]

I have installed MX-16.1 (September) and runs pretty well. Indeed, it is a very good distro. Two days ago I tried live MX-17 B1 (and before a4 and a5) and noticed that ram consumption is much higher than MX-16.1 live. Why is that? It can be explained? Thanks.

Not sure how much it consumes on your system ,on mine very little, 4 core AMD, but you can try turning off the conky and see what results. MX Conky and click stop.

Hello.

My computer is a very old one: desktop Dell Optiplex 5200 with a 3,4 GHZ Dual Core Processor, 4 GB Ram.

The MX16.1 live session and the HDD installation: flows between 230-240 MB of ram after starting.

The MX-17 testing (alphas and beta 1): more than 600 MB of ram. Even when conky is disabled it never reaches that low value of ram consumption as the 16.1 does.

MX-17 is not so fast and smooth oppening applications as MX-16.1.

I've got a laptop Lenovo T61 (very old one as well): I am going to do the same job to verify the performance.

Thanks for your answer

The devs have been looking at this. More to follow.

[chrispop99]

There has been some discussion here and elsewhere about the default image viewer. This is important to me as it's something I use a lot. I don't like gThumb at all, for numerous reasons, and I don't like Mirage (MX-16 default) because it has no print facility. The best I had come up with was the Gnome Image Viewer (EOG), but that has no resizing option.

I've spent some time this weekend testing a number of image viewers, and unless I've missed something obvious, I've found one that I think does pretty much everything.

It's 'Nomacs', and it's in the Testing repo.

It has printing capability, does cropping, resizing, and a reasonably comprehensive amount of image manipulation. It will also open PSD files (native Photoshop), something few other viewers do. It has been stable during my limited testing. In spite of how comprehensive it is, speed is very good. It is much faster at opening an image on an ancient Pentium M laptop than gThumb.

It would be great if others could test this, and offer their opinions.

Chris

[richb]

Could not find Nomacs in the test repo, but found it in the default repo.

Just too a quick look. I particularly like the scroll wheel zoom feature. It looks like more of an image manipulation program rather than an image viewer. I do not find that a negative.

[stsoh]

does anyone notice this or not;
open any apps and close it, does not stay at it's last closed location.
turn off conky, apps will then opens at it's last closed location.

[berlin59]

I cannot vouch for this but it sounds like this is what happened to you.

Now you should also delete the ubuntu subdirectory in the EFI partition to prevent the UEFI firmware from restoring the entry into the BootOrder.

Procedure is in the second post.

https://askubuntu.com/questions/63610/h ... -menu-uefi

richb,
sorry for giving another feedback after telling everybody that the old uefi-entries are gone.
They are not gone, it only seemed to be so.

After using boot-repair-disk (of course from an usb-live-stick) to remove an OS from my Toshiba uefi-laptop, the new grub-menu showed all the old entries again.

So I followed exactly the procedure you suggested.
I definitely was able to delete the old entries in the efi-partition.

Later on I used boot-repair-disk again and after that the new grub-menu has them all back.
I wonder where these old entries are stored.
Somewhere the update-grub after a new grub-install into the esp must grab them.

Edit: I think I got it now.
Not with a live-usb linux, but from within LinuxMint. Although efi-partition is mounted, with sudo I was able to make a directory and mount sda1 there, sda1 = my esp.
Then I removed everything which looked nasty to me. In strange folders I found the solus3-files again and other files which I removed.
After the final sudo update-grub and restart, the grub-menu now is clean. All the old entries are gone.
Mission accomplished.

[Jerry3904]

This post in the Italian forum raises a question (G trans):

For pure curiosity I tested live version 17 beta. I would like to point out this anomaly: in the launch of the MX-16 live, the presence of wifi networks was immediately reported, so that time before, I could install the distro with the wifi connection only. It should be kept in mind that I have the b43 card, which has always caused problems with various distro. When launching the live MX-17 beta, however, wifi is not detected, although b43-fwcutter has already been installed. I should have connected to the ethernet network for installation. Of course I let it go because I did not care to waste time. I bring anomaly to developers' attention for any controls.

I will test on my only laptop later todeay that has b43 (and b44).

EDIT: works fine on my Dell 700m