grub install error in core

[Member robertklsz]

Tried to install core and received the following error:

grub-install: error: /usr/lib/grub/i386-efi/modinfo.sh doesn’t exist. Please specify –targer or –directory.

also when selecting reboot or quit from antix-cli menu it asked:

Are you SURE you want to telinit (y/N)

If you need any other info I’ll try to provide it.

[Moderator christophe]

Helpful

Up

0

::

robertklsz wrote:

also when selecting reboot or quit from antix-cli menu it asked:

Are you SURE you want to telinit (y/N)

According to this site:
http://linux-commands-examples.com/telinit

telinit may be used to change the system runlevel. The RUNLEVEL argument should be one of the multi-user runlevels 2-5, 0 to halt the system, 6 to reboot the system or 1 to bring the system down into single-user mode. Normally you would use the shutdown (8) tool to halt or reboot the system, or to bring it down to single-user mode.

So it appears telinit is one way of rebooting/shutting down. 🙂

confirmed antiX frugaler, since 2019

[Member robertklsz]

Helpful

Up

0

::

Did not know that. I’s good to learn new things. Thank you Christophe

[Moderator christophe]

Helpful

Up

0

::

And for your first issue:

Tried to install core and received the following error:

grub-install: error: /usr/lib/grub/i386-efi/modinfo.sh doesn’t exist. Please specify –targer or –directory.

I tried installing core via cli-installer. When we get to the grub part, it goes something like this:

Where should grub be installed?
ESP selection will fail if not booted in legacy mode.
1) MBR (Legacy – Master Boot Record)
2) Root Partition
3) ESP (EFI install)

So that tells me, that the cli-installer needs to be run in legacy mode on an EFI computer or the installation will fail.
So I believe that’s where your problem lies. Previous to antiX-21, the cli-installer did not install to EFI at all. Now it does, but just in legacy mode. (For now, anyway.)

confirmed antiX frugaler, since 2019

[Moderator Brian Masinick]

Helpful

Up

0

::

@christophe: regarding the previous post, I think you are right on the mark. There are quite a few distributions these days that will work with EFI and UEFI, and also the GPT (partition handling) that goes with the overall EFI architecture, which is a long overdue replacement for the ancient BIOS architecture.

However, there are relatively few distributions, mostly the large ones that also have a commercial and server oriented backing, that implement not only UEFI, but Secure UEFI. OpenSUSE and Red Hat Enterprise Linux, and the free Red Hat Fedora software DO handle Secure UEFI. I can’t recall for certain if PCLinuxOS handles it or not; there are a few others, but I haven’t been making a list of them. The first time I set up UEFI, I’m pretty sure I was using either Fedora or OpenSUSE to manage my boot loader until other distributions got at least the “shim” capability necessary to work with UEFI. That doesn’t mean that they can handle Secure Boot with UEFI, a matter that came up for me once again just the other day when I was managing a few of my distributions on one of my newer laptops.

No such problem on this old, reliable Lenovo X201 laptop! I boot straight into antiX Linux on this one, and at the moment I’m devoting this particular system to antiX 19.5 – works GREAT here!

--
Brian Masinick

[Member robertklsz]

Helpful

Up

0

::

Thanks Brian and Christophe.

I tried to install to the root partition and when grub came up it displayed a GRUB in the top left with a flashing cursor but would not except any keyboard input. I think the keyboard was active because the caps light worked. I guess this was expected based on Christophe’s response above. Wanted to see what would happen anyway.

I then tried to install into the MBR and the grub loader loaded and I was able to boot into AntiX.

This is an older core2 duo black mac book. At one point I had MX and then an older version of AntiX on this laptop and do not remember have any issues with the install. Were these installing into the MBR? Trying to understand as I have three older Mac’s I’m trying to revive. Also, to just understand this process better. I do understand Mac’s are a different breed with there own issues. A lot of distro’s will not even boot on my Mac’s but yours does.

Thanks again.

[Moderator Brian Masinick]

Helpful

Up

0

::

One thing I have noticed over the past 3-4 years is that while more recent generation devices are supported by the changes in hardware firmware and system software, some of the older, classic designs are getting left behind.

As an example, I can install antiX or MX Linux on any of my older generation systems, but on my newer systems I have to use the AHS “Advanced Hardware Support” edition to get MX Linux installed; the base release usually will not work, and I’ve not been able to get antiX (not even live or snapshot editions) to work on my newer systems.

Fortunately I have one 5-6 year old system, a few really old 10-15 year old relics in the corner; I can get antiX on all of them, so I either put antiX on them or dual boot them with the regular edition of MX; all of them can run either distribution.

My newer system can run EndeavourOS, siduction or Debian, MX Linux 21 AHS or PCLinuxOS. Alternatively I can also run openSUSE or Fedora too. My newer hardware has a smaller capacity SSD instead of an 8 TB HDD, so I run, at most, four distributions on the newer hardware.

--
Brian Masinick

[Author]

Posts