Error everytime I install a kernel

[Cavsfan]

Ok, I rebooted and the virtualbox packages are gone.
When you select a package in MX Package Manager it does not pull in the dependencies, so which of these do I need to install or are there more?

Screenshot-10-02-19.jpg

[Stevo]

I would first install the standard legacy 390.116 driver on the standard 4.19 kernel. Then when you go to MX package installer and see what's in the test repo, the 390.129 versions of what you have installed will be marked as upgrades.

Make sure to uncheck the box that hides the lib** packages. After the installed 390 legacy-driver packages have been upgraded to 390.129, try a reboot to the standard kernel to make sure that version is working for you, then you can install a 5.2 kernel and the build should be successful.

[Paul..]

@Cavsfan, Stevo is the undisputed expert...so his approach is the safest.

Alternative
I have been using the 390.116 driver on the standard 4.19 kernel but was looking for better performance...so ended up installing the newer 435.21 driver on an older nvidia board using the following steps:

1. Ctl-Alt F1 to go to console mode...
2. logged in as root
3. Entered "ddm-mx -i nvidia" at command prompt...then accepted the option to look for newer driver on "Test"
4. ddm-mx found the newer driver 435.21 and installed correctly...
5. I then installed the antix 5.1.2 64-bit from the MX Package Installer and it works fine. (YMMV, of course.)

My nvidia board for comparison (on a Ryzen 5 1400 system):

Code: Select all

inxi -G
Graphics:  Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] driver: nvidia v: 435.21 
           Display: x11 server: X.Org 1.19.2 driver: nvidia resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 750 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 435.21 

HTH

[Cavsfan]

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]

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]

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.

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.

[JayM]

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]

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.

[Cavsfan]

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.

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.

Those 3 errors that popped up for about 1 second when I booted using the bad USB installer stick were apparently caused by Windows Rufus.
I have never seen it do that before and the fact that it continued on to the installation screen after the error was what was weird.

I went by the directions at the bottom of the MX Linux download page to create the USB and it worked well.

Then I installed MX Linux 18.3 for probably the 20th time. I did install the 390.129 nvidia driver in the MX Test repo and rebooted.
All was well. I think I got a bunch of updates.
Then today I installed the antix 5.2 kernel and it got the same errors as before; the one that cause me to open this thread.

So, once again I had to re-install and I'm going with stock packages. If it comes through in regular updates, I'll install it.

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.

So, I'll use the default kernel until another one is released.

[richb]

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.