You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

The following (for the benefit of those from google in the future) WORKS;

Code:

First, copy the /boot/grub/i386-pc folder contents from the floppy, to /i386 on /dev/sda5
insmod part_msdos
insmod ext2
set prefix=(hd0,msdos5)/i386
NOW, 'insmod linux' or 'insmod configfile' work sucessfully
[edit: 'insmod ata' is not needed, and 'set root=...' is not essential]

I can boot debian as described in post #76.If i do 'configfile /boot/grub/grub.cfg' (@ sda5), then the grub boot menu comes up, with debian and my various voyage kernels. NOT like here with options like 'detect any OS'. Do we need the grub.cfg from the floppy??

EDIT: by not using 'insmod ata' I can now load the floppy's boot.cfg, and get the menu shown.

@ hurry_hui This thread has really been informative and you know grub2 really well, I have learned a few things while following this thread, however how can the op install grub2 to the mbr if they still have this problem:

I came across a problem with grub legacy a few years ago where sometimes it would not boot if the partition it was installed from is not flagged bootable. I have been wondering if when debian installed, if it moved the boot flag from the voyage partition to the debian partition and maybe that is why the reinstall of grub legacy didn't work. just a thought

2. Grub1 does not have its file (or cannot detect its files--stage1, stage2, menu.lst).

3. Bootable flag which may be needed.

Solution to the above problems:

(1 & 2). (Although some attempts have been made within chrooted environment) Reinstall grub2 with --recheck, if failed, try again with --force. To see if it is installed properly recheck with boot_info_script.sh.

Run (instead of 'update-grub')

Code:

grub-mkconfig -o file_name

to check whether it can pick both voyage and debian kernels. If successful, run 'update-grub' or

Code:

grub-mkconfig -o /boot/grub/grub.cfg

If failed, try no.(3).

(Btw, there are some discussions on internet on making custom (smaller?) core.img by grub-mkimage -o name_of_grub_image -0 [some_options].)

(3). Copy files (from voyage cd or another distro) needed by grub1, to its folder /boot/grub/.

if you haven't formatted your hard drive yet, you still might be able to get grub legacy to work. First go to voyage /boot/grub folder and make it sure it has a stage1 and stage2 file, a menu.lst, a devicemap file, and about seven more stage files with different names. If they are missing the files can be copied from the /usr/lib/grub/x386 folder.
With a partition manager, such as gparted, parted, cfdisk or any one that you can use flag the voyage partition bootable. To install grub legacy manually, boot into voyage and issue the following commands