MX Linux Forum

timkb4cq wrote: Mon Sep 30, 2019 6:48 pm The 390.116 nvidia driver won't build on the 5.2 kernel. That's why it fails.
The 390.129 nvidia driver in the MX Test repo has been patched for the newer kernels.

Stevo wrote: Mon Sep 30, 2019 8:50 pm You also have build failures for the stock 5.2.24 version of virtualbox and the stock version of broadcom-sta-dkms.

The 5.2.32 version of VBox in the experimental repo will build on the 5.2 kernel, and the 6.0.12 version in the test repo has been tested on up to and including the 5.3 kernel, as has the broadcom-sta-dkms package there.
This is nothing that we're not already aware of on MX, but we don't add the antiX kernels to our repo. We note this gotcha in the announcements when we jump to a new major version of the Liquorix kernels, which we do package.

Stevo wrote: Wed Oct 02, 2019 4:17 pm We've already diagnosed the issue and given the answer--you must upgrade your Nvidia driver to the legacy 390xx version from the test repo, 390.129, before you try and install a 5.2 kernel. It's no mystery why you can't boot if you don't do that.

Cavsfan wrote: Thu Oct 03, 2019 6:34 pm Guess I should have did what Stevo said first. Because I tried installing the 435.21 driver and have not been able to boot into MX Linux 18 since.

I have used the same USB stick to re-install and gotten this error and have downloaded 3-4 other ISOs and none of them will boot. I download the ISOs on Windows 10 and use Rufus to make a bootable USB. I've done this about a hundred times.
But, every time I try to boot with any of them I get this error that flashes just before the install screen pops up (which will not install). It took me a while to catch what it was saying but, I got it with my phone camera:

Code: Select all

               Failed to open \EFI\BOOT\mmx64.efi - Not Found
               Failed to load image \EFI\BOOT\mmx64.efi: Not Found
               Failed to start MokManager: Not Found

JayM wrote: Thu Oct 03, 2019 10:07 pm

Cavsfan wrote: Thu Oct 03, 2019 6:34 pm Guess I should have did what Stevo said first. Because I tried installing the 435.21 driver and have not been able to boot into MX Linux 18 since.

I have used the same USB stick to re-install and gotten this error and have downloaded 3-4 other ISOs and none of them will boot. I download the ISOs on Windows 10 and use Rufus to make a bootable USB. I've done this about a hundred times.
But, every time I try to boot with any of them I get this error that flashes just before the install screen pops up (which will not install). It took me a while to catch what it was saying but, I got it with my phone camera:

Code: Select all

               Failed to open \EFI\BOOT\mmx64.efi - Not Found
               Failed to load image \EFI\BOOT\mmx64.efi: Not Found
               Failed to start MokManager: Not Found

OK, my coffee's finally kicked in this morning, but this still doesn't make any sense to me. How are you able to run the installer if you can't even boot from the USB stick now?

https://mxlinux.org/wiki/system/create- ... s-desktop/ may help with USB creation and booting issues. There's a video about how to make an MX USB when Rufus doesn't work right or something like that.

Cavsfan wrote: Fri Oct 04, 2019 6:49 pm Did you miss "I got it with my phone camera"? That is how I caught the error message. I would see those three errors and then the installation screen would pop-up like normal but, it would not go any farther.

Just to make sure I installed Xubuntu 19.10 beta from a 64GB USB stick and then I did what you mentioned and downloaded the ISO while in Arch Linux. I was then able to re-install MX_Linux 18.3.
I just installed the 390.129 driver from the test repo and am about to reboot. Sure hope like hell it goes past the flashing underscore.

Cavsfan wrote: Thu Oct 03, 2019 6:34 pm But, every time I try to boot with any of them I get this error that flashes just before the install screen pops up (which will not install). It took me a while to catch what it was saying but, I got it with my phone camera:

Code: Select all

               Failed to open \EFI\BOOT\mmx64.efi - Not Found
               Failed to load image \EFI\BOOT\mmx64.efi: Not Found
               Failed to start MokManager: Not Found

JayM wrote: Fri Oct 04, 2019 11:03 pm

Cavsfan wrote: Fri Oct 04, 2019 6:49 pm Did you miss "I got it with my phone camera"? That is how I caught the error message. I would see those three errors and then the installation screen would pop-up like normal but, it would not go any farther.

Just to make sure I installed Xubuntu 19.10 beta from a 64GB USB stick and then I did what you mentioned and downloaded the ISO while in Arch Linux. I was then able to re-install MX_Linux 18.3.
I just installed the 390.129 driver from the test repo and am about to reboot. Sure hope like hell it goes past the flashing underscore.

The only installations screens found in the live USB version of MX are the MX Installer to install MX Linux, MX Updater to install upgrades, Synaptic and MX Package Installer to install new packages. So again, I don't know what you're talking about, unless you possibly mean the live USB's boot menu?

If you're having problems getting a live USB to boot in UEFI mode I suggest that you follow the instructions in the wiki page I linked to in my last post, read the appropriate section of the manual (there's a link at the top of the forum), search the forum to find the help and advise that's already been given to others because maybe that will also be your solution, and if not, start a new topic about getting a live USB to boot on your specific computer.

One tip I can give you is to format the USB stick again in Windows, as Fat32, then try burning the iso with Rufus again, making sure you choose the appropriate options to make it UEFI-bootable. Sometimes things get messed up when you reburn isos to already-used USB sticks and you need to wipe them clean by reformatting them and start over fresh.

Edit: first, do what fehlix suggested below. He knows more about fixing booting issues (and about many other Linux things) than I do.

fehlix wrote: Fri Oct 04, 2019 11:54 pm

Cavsfan wrote: Thu Oct 03, 2019 6:34 pm But, every time I try to boot with any of them I get this error that flashes just before the install screen pops up (which will not install). It took me a while to catch what it was saying but, I got it with my phone camera:

Code: Select all

               Failed to open \EFI\BOOT\mmx64.efi - Not Found
               Failed to load image \EFI\BOOT\mmx64.efi: Not Found
               Failed to start MokManager: Not Found

You might probaly "fix" the issue in a way as mentioned here: https://forum.mxlinux.org/viewtopic.php ... 02#p520002
by copying grubx64.efi to mmx64.efi within the /EFI/BOOT folder on the USB-stick.

But, I think it is too much to ask for a user to mix test repo packages with stable packages. I know a little but, just consider me a regular user. I do not feel comfortable installing any kernel this way.

richb wrote: Sat Oct 05, 2019 4:26 pm

But, I think it is too much to ask for a user to mix test repo packages with stable packages. I know a little but, just consider me a regular user. I do not feel comfortable installing any kernel this way.

To be clear no one forces a user to install from the test repo. It is a test repo. The packagers want feedback if a user chooses to install. That is why it is test. Only if feedback is positive will the package be moved to main.

Stevo wrote: Sat Oct 05, 2019 6:03 pm I haven't tested the antiX 5.2 kernel, but wonder if you are seeing the driver rebuild when you install it. It's pretty apparent when you scroll back up the terminal output after its done.

I also wonder if you're getting the same failures if you install the 5.2 Liquorix kernel--I have more experience with that one.

Stevo wrote: Wed Oct 16, 2019 8:55 pm Dolphin_oracle just fixed the Nvidia Installer on at least MX 19 to install the 435.21 driver from the test repo correctly when that's the choice, and it now works correctly in my tests. The new version should be pushed as an update to MX 19 and 18 quite soon, so wait a bit. Before the fix, you get the stock Debian version no matter what your choice.

As a workaround before the fix, I was able to update the 418.74 stock Buster driver to the 435.21 version after the stock version was incorrectly installed from the test repo tab of MX PI, as explained above, but you had to check to make sure your hardware would work with the 435 version.

$ inxi -SMCG
System:    Host: mxlinux19 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 Desktop: Xfce 4.14.1 
           Distro: MX-19beta-3_x64 patito feo September 22  2019 
Machine:   Type: Desktop System: ASUS product: All Series v: N/A serial: <root required> 
           Mobo: ASUSTeK model: Z87-K v: Rev X.0x serial: <root required> 
           UEFI: American Megatrends v: 1103 date: 01/02/2014 
CPU:       Topology: Quad Core model: Intel Core i7-4770K bits: 64 type: MT MCP 
           L2 cache: 8192 KiB 
           Speed: 2976 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 3664 2: 3478 3: 3531 
           4: 3491 5: 3587 6: 3676 7: 3656 8: 3453 
Graphics:  Device-1: NVIDIA GM200 [GeForce GTX 980 Ti] driver: nvidia v: 418.74 
           Display: x11 server: X.Org 1.20.4 driver: nvidia resolution: 3840x2160~60Hz 
           OpenGL: renderer: GeForce GTX 980 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 418.74 

Stevo wrote: Mon Nov 04, 2019 3:50 pm If you do want to track new kernel releases, you can add the Liquorix kernel repo, or I rebuild them for our test repos about once a week or so.

But then you have to make sure your third party drivers will build against a new kernel release, or at least be prepared to revert to a known working kernel via the "advanced options" submenu in GRUB.

$ inxi -S -G
System:    Host: mxlinux19 Kernel: 5.2.15-antix.1-amd64-smp x86_64 bits: 64 Desktop: Xfce 4.14.1 
           Distro: MX-19_x64 patito feo October 21  2019 
Graphics:  Device-1: NVIDIA GM200 [GeForce GTX 980 Ti] driver: nvidia v: 435.21 
           Display: x11 server: X.Org 1.20.4 driver: nvidia resolution: 3840x2160~60Hz 
           OpenGL: renderer: GeForce GTX 980 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 435.21 

$ ls -lA /boot | grep " -"
lrwxrwxrwx 1 root root       35 Nov 23 20:55 initrd-antix.img -> initrd.img-5.2.15-antix.1-amd64-smp
lrwxrwxrwx 1 root root       25 Nov 23 19:07 initrd.img -> initrd.img-4.19.0-6-amd64
lrwxrwxrwx 1 root root       22 Nov 23 19:07 vmlinuz -> vmlinuz-4.19.0-6-amd64
lrwxrwxrwx 1 root root       32 Nov 23 20:56 vmlinuz-antix -> vmlinuz-5.2.15-antix.1-amd64-smp