On Saturday, 5 February 2022 09:36:44 GMT Dale wrote:

> It failed with a missing normal.mod file.  That file is in the old grub
> directory.  Once I renamed the directory back to what grub expected, the
> system loaded grub fine.

Ahh!  The normal.mod command:

http://www.gnu.org/software/grub/manual/grub/html_node/normal.html

You won't get a boot menu without this file, or a lot of GRUB commands.  
However, in a GRUB2 installation this file is found here:

# find /boot/ -name normal.mod
/boot/grub/i386-pc/normal.mod

It should not exist the old legacy filesystem.  :-/

I wonder if you have somehow mixed the legacy and new GRUB2 files?

Anyway, the solution is to go fishing for it from the GRUB rescue prompt, using 
the ls command and then set root and set prefix before you can insmode it.


> There's been other threads about kernel boot
> problems and the one I recently built could be having one of those
> problems.  I haven't looked into that.  I doubt there is any file system
> problem.  The problem was me renaming a directory that grub still needs
> files from.  There is likely a way around this but my post was to warn
> others that renaming that directory could cause problems. 

Right, renaming should be done carefully as you could mix the legacy and GRUB2 
filesystems.


> >> I've reinstalled
> >> using the grub-mkconfig command but have not reinstalled using the
> >> grub-install command.

Right, the 'grub-mkconfig' command only generates a new grub.cfg file and 
overwrites the old one.  It does not *install* GRUB, whereby install involves 
dropping GRUB's bootloader code in the MBR and also copying all GRUB files into 
/boot.

TBH, once GRUB2 is installed properly and it works, it tends to carry on doing 
so.  So the question remains, why did it barf at its normal.mod path ...


[snip ...]
> I don't have the old grub installed, just a directory that was installed
> by the old grub but contains files that the new grub needs.

Hmm ... that should not be the case.  The legacy and GRUB2 filesystems are 
different.

> The file
> and path it needs is this:  /boot/grub/i386-pc/normal.mod  Why that
> isn't installed in the new grub directory and told to look there for it,
> I have no idea at the moment.  I may test it one day but don't feel the
> desire to try it today. 

Life's a mystery!  :-)

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to