grub boot manager

Booting, installing, newbie
Message
Author
User avatar
babbs
Posts: 397
Joined: Tue 10 May 2005, 06:35
Location: Tijuana, BCN, Mexico

#21 Post by babbs »

I did do a type 2 install.

Should I specify that the kernel is on /dev/hda1 (hd0,0) or should I put a copy of the kernel in the /dev/hdc1/boot partition with the Fedora kernels? The /boot partition is 100M so I'm not running short on space in there.

Thanks!
babbs

Bruce B

Where is the kernel?

#22 Post by Bruce B »

babbs wrote:I did do a type 2 install.

Should I specify that the kernel is on /dev/hda1 (hd0,0) or should I put a copy of the kernel in the /dev/hdc1/boot partition with the Fedora kernels? The /boot partition is 100M so I'm not running short on space in there.

Thanks!
babbs
IF I understand and I think I do - I'd leave the Puppy kernel where Puppy installed it and tell menu.lst where it is.

I think this is right for you:


title Puppy Linux (on /dev/hda1)
root (hd0,0)
kernel /boot/vmlinuz root=/dev/hda1 ro vga=normal

User avatar
Ian
Official Dog Handler
Posts: 1234
Joined: Wed 04 May 2005, 12:00
Location: Queensland

#23 Post by Ian »

Do you have a /boot directory in your Puppy installation.

Have a look at the Wiki under, PageIndex, GrubPuppyBoot.

Bruce B

Do I have a /boot directory?

#24 Post by Bruce B »

Ian wrote:Do you have a /boot directory in your Puppy installation.

Have a look at the Wiki under, PageIndex, GrubPuppyBoot.
I couldn't tell if you asked this questio of me. Maybe not.

YES I have a /boot directory IF I have a type 2 install

NO I don't have a /boot directory IF I have a type 1 install

User avatar
danleff
Posts: 294
Joined: Sun 08 May 2005, 13:11
Location: Albany, NY
Contact:

#25 Post by danleff »

title Puppy Linux v1.0.2
rootnoverify (hd0,0)
kernel /vmlinuz root=/dev/ram0 PFILE=pup001-none-262144 PHOME=hda1
initrd /image.gz
Should be;

title Puppy Linux v1.0.2
rootnoverify (hd0,0)
kernel /vmlinuz root=/dev/hda1


The error is most likely image.gz, which is not in the boot directory and not really needed.
I love it when a plan comes together

--Hannibal Smith

User avatar
babbs
Posts: 397
Joined: Tue 10 May 2005, 06:35
Location: Tijuana, BCN, Mexico

#26 Post by babbs »

Hi guys,

Between my two hard drives, I have 7 partitions:

/dev/hda - Formerly used for Windows, but now contains 4 partitions, each just under 5GB in size. The first partition is where I did the type 2, Puppy install. It is recognized as ext2 with the other three unformatted (no file system installed).

/dev/hdc - Added to the system when I still had Windows working. When I installed Fedora Core 3 on it, the drive was formatted with three ext3 partitions ("/boot" is 100MB, "/" is 18GB and "/swap" is 1GB).

My grub is located in /hdc1/boot/grub.

I looked at the wiki page, but I'm thinking that I need to stir the mix and try a few things. I'll be back shortly.

babbs

User avatar
babbs
Posts: 397
Joined: Tue 10 May 2005, 06:35
Location: Tijuana, BCN, Mexico

#27 Post by babbs »

Tonight, I tried everything I could think of, but it would seem that I am too close to the forrest to see the trees right now. I'm going to rest my eyes and resume this battle tomorrow or the next day...

Here is one version that did NOT work:

Code: Select all

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd1,0)
#          kernel /vmlinuz-version ro root=/dev/hdc2
#          initrd /initrd-version.img
#boot=/dev/hda
default=1
fallback=0
timeout=5
#splashimage=(hd1,0)/grub/splash.xpm.gz
hiddenmenu
password --md5 {Removed}
title Fedora Core (2.6.11-1.14_FC3)
	root (hd1,0)
	kernel /vmlinuz-2.6.11-1.14_FC3 ro root=LABEL=/ rhgb quiet
	initrd /initrd-2.6.11-1.14_FC3.img
title Puppy Linux v1.0.2
	rootnoverify (hd0,0)
	kernel /vmlinuz root=/dev/hda1


Thanks,
babbs

Guest

#28 Post by Guest »

babbs wrote: title Puppy Linux v1.0.2
rootnoverify (hd0,0)
kernel /vmlinuz root=/dev/hda1[/code]
I think I see the problem. The kernel line should read:

kernel /boot/vmlinuz /root/=dev/hda1

Bruce B

#29 Post by Bruce B »

The post above was by me - I guess I wasn't logged in.

Guest

#30 Post by Guest »

I may have made a mistake!

Your still getting the same file not found error? Try;

title Puppy Linux v1.0.2
rootnoverify (hd0,0)
kernel /boot/vmlinuz root=/dev/hda1

I believe that vmlinuz is in the boot directory in the Puppy installation?

In Fedora, I bet vmlinuz is a symbolic links to /boot/vmlinuz

This was mentoned above? Sorry!

Also, is there a space between kernel and /boot/vmlinuz... in the Puppy line? There should be.

If this does not work, make sure that Puppy is really at hda1.

In Fedora, run fdisk -l at a command line as root user. That's the small case letter, not the number one.

Or in Puppy, run, in a command line (rxvt) probepart

You should see the partitioning scheme for both drives.

User avatar
babbs
Posts: 397
Joined: Tue 10 May 2005, 06:35
Location: Tijuana, BCN, Mexico

#31 Post by babbs »

I didn't try /boot/vmlinuz because I thought it would conflict with the /dev/hdc1/boot routing, which is where I believe the stage 2 part of the boot manager resides. I will give it a try when I get home tonight.

Thanks a million!
babbs

Bruce B

#32 Post by Bruce B »

I'm pretty sure it will work because the instructions you were using looked for the kernel on / and the kernel was not there.

I do it all in one line and it works for me. An example of one line booting:

kernel (hd0,0)/boot/vmlinuz root=/dev/hda1

The command makes a lot of sense if you study it. What you are doing is telling GRUB a couple things it needs to know: the location and name of the kernel and the location of / (the root of the directory structure), not to be confused with the user known as 'root' or the /root directory

The mystery to me is why so many Linux distros use LILO

newuser

#33 Post by newuser »

sorry to backtrack, but im still trying to use the grub boot by making the floppy. i went to grub bootloader config, and chose 2nd setting.

I am at the part where it asks 'where do u want the GRUB files to go?' i have tried /dev/hda1..hda0,hda2,fd0 without success. I am still on the FAT16 harddrive, and puppy recognizes the partition as VFAT partition at /dev/hda1 having 90mb free space on hard drive. It should be able to see it and copy the needed files.

I was reading on the forum that puppy requires 2 partitions to create the boot manager..so that it will boot up puppy everytime computer is turned on.. >> ?

I've alo tried manually copying the usr_cram file, and 3 other files onto my harddrive.,but it's not working.

I've also tried 'Install Puppy Harddrive' from the start menu, but it cannot create a floppy that will boot.

newuser

#34 Post by newuser »

sorry i forgot to add that that screen says ' the partition 'dev/hda1' is not Linux.'

fd0 gives me a similar msg.

Bruce B

#35 Post by Bruce B »

I think you will have some difficulties.

90 MB HD free space is not really enough. It take about 60 MB for vmlinuz, usr_cram.fs and image.gz and then...

... you still want a pup file to store your user settings files. The default size for this file is 256 MB. In my experience Puppy when booting from CD-ROM will make the PUP001 smaller if there is not enough free space. But there is another problem ...

... I don't think Puppy will write a the PUP001 file to a FAT16 partition type.

I think I can be more helpful if you tell more about your hard disk size and partitions and RAM

newuser

#36 Post by newuser »

i have manually copied the 4 files onto the harddisk, and have 90mb free space remaining. so about 150mb if i deleted those files.

it is a pentium computer with 128mb SDRAM.

newuser

#37 Post by newuser »

sorry i forget to add.. why doesnt puppy write to FAT16. is it the same problem as NTFS?

i thought puppy could write to vfat, dos, and a few others? isnt FAT16 a subset of vfat or dos?

Bruce B

#38 Post by Bruce B »

Puppy won't use the FAT16 as far as I know, but I forget the reason why.

Yes, I think the FAT16 is VFAT type.

I think there were only three files you needed to copy from CD-ROM and not four. That is beside the point.

I think you need to make a FAT32 partition or convert your existing partition to FAT32. I don't know what DOS and/or Windows you are running or if it supports FAT32.

I don't know how big the disk is or nada.

newuser

#39 Post by newuser »

I had win95 running previously, and still have 95 booting as default.
hope to get puppy as default soon.

User avatar
danleff
Posts: 294
Joined: Sun 08 May 2005, 13:11
Location: Albany, NY
Contact:

#40 Post by danleff »

If I remember correctly, Win 95 only supports fat16 and Win 98 supports fat32. You can convert the existing partition, or make room for a fat32 partition, if you have partitioning software, such as PartitionMagic. I don't know if cfdisk or fdisk will support this in Linux or not. You could also use a Win 98 boot disk with fdisk support to do this, I think.

Or, make a second ext2 partition, which Puppy will look for off the CD.
I love it when a plan comes together

--Hannibal Smith

Post Reply