[prev in list] [next in list] [prev in thread] [next in thread] 

List:       grub-help
Subject:    Re (2): Grub on a Micron Trek 2.
From:       peter () easthope ! ca
Date:       2014-06-25 17:28:42
Message-ID: E1Wzqzy-0004YX-9M () dalton ! invalid
[Download RAW message or body]

From:	Jordan Uggla <jordan.uggla@gmail.com>
Date:	Sat, 14 Jun 2014 00:01:20 -0700
> ... don't have a grub.cfg in (hd0,msdos1)/boot/grub/grub.cfg ...

It is there.  http://carnot.yi.org/GrubInstallationStory

> ... or that grub.cfg doesn't have any menu entries. 

There is an entry for Native Oberon.
  http://carnot.yi.org/GrubInstallationStory
  
> Please post your complete grub.cfg ...

In GrubInstallationStory it follows "cat /mnt/boot/grub/grub.cfg".

> ... output of "grub-probe --target=device /boot/grub/grub.cfg" ...

At the end of the GrubInstallationStory.

> ... "grub-mkrelpath /boot/grub/grub.cfg".

Ditto.  

Just prior to the Grub command prompt is this screen.
  http://carnot.yi.org/GrubScreen.png

ae5f..6e91 is the /root part in the host used to install 
Grub; but Grub should be reading the hdd in the extant host.

Commands "chainloader (hd0,5)+1", "boot" at the grub 
prompt start the OS.  If Grub can be coerced to read the 
hdd where it is, rather than hunt for the hdd were it was, 
then the menu is likely work.

Incidentally, 
https://www.gnu.org/software/grub/manual/html_node/Invoking-grub_002dmkconfig.html#Invoking-grub_002dmkconfig
 explains where output is delivered.  Equally important is the input  
used to create the output.  It should be documented.

Thanks for the replies,     ... Peter E.




-- 
123456789 123456789 123456789 123456789 123456789 123456789 123456789 12
Tel +1 360 639 0202  http://carnot.yi.org/  Bcc: peter at easthope. ca


_______________________________________________
Help-grub mailing list
Help-grub@gnu.org
https://lists.gnu.org/mailman/listinfo/help-grub


[prev in list] [next in list] [prev in thread] [next in thread]