Results 1 to 8 of 8
I'm very new to Linux, been playing around with several different distros with varying success.
I got an Eee PC for my son, really like the Puppeee distro for that, ...
- 04-15-2009 #1Just Joined!
- Join Date
- Apr 2009
- Posts
- 6
Another Grub Config Problem
I'm very new to Linux, been playing around with several different distros with varying success.
I got an Eee PC for my son, really like the Puppeee distro for that, very lightweight and quick on a machine with limited storage and resources. But I can't get it installed into a bootable form.
In the Puppy installer, the Grub Configure utility runs after the install to make it bootable. When you get through with the grub config, you get a message telling you that you need to edit /boot/grub/menu.lst to change location of vmlinuz, ( the kernel I assume), but it doesn't tell you what to change the location to. As a linux noob, I'm lost, and have been beating my head against this for the past 4 days. I'm fairly sure it has something to do with how Linux and grub differ in the way they number drives, but can't figure it out.
I've attached a couple of screenshots, both of the message prompt and the default menu.lst, I hope some one out there can help me. I really like Puppeee and would like to use it, but there are other distros that are much easier to install than this.
By the way, the OS is installed on partition sda1
- 04-15-2009 #2Just Joined!
- Join Date
- Apr 2009
- Posts
- 6
Oooops, here's the other screenshot.
- 04-15-2009 #3
Hi and Welcome !
ScreenShot is too small. I would suggest you to post contents of menu.lst file here. Post the output of these commands too :
Code:su - fdisk -l ls /boot
It is amazing what you can accomplish if you do not care who gets the credit.
New Users: Read This First
- 04-15-2009 #4Just Joined!
- Join Date
- Apr 2009
- Posts
- 6
Results of commands is:
su - Takes me to root, I think, no directory indicator in this terminal.
fdisk -1 Returns as invalid option, then gives a list of command options
ls /boot (Actually had to use ls /mnt/sda1/boot) returns two items, the grub folder and vmlinuz, which I think is the kernel.
menu.lst should be attached
- 04-15-2009 #5
Its small L in fdisk -l. Contents of menu.lst file are correct. We have to check the output of fdisk -l command now.
It is amazing what you can accomplish if you do not care who gets the credit.
New Users: Read This First
- 04-15-2009 #6Just Joined!
- Join Date
- Apr 2009
- Posts
- 6
Oops, sorry, still learning the commands. Doc file with fdisk -l output attached.
And thanks for the help.
- 04-16-2009 #7
Execute this
Create new menu.lst file and add these cotents :Code:su - cd /boot/grub mv menu.lst menu.lst.bak
Save file and reboot machine. In case it doesn't work, post the output of ls /boot command.Code:timeout=10 title Linux root (hd0,0) kernel /boot/vmlinuz root=/dev/sda1 ro vga=normal
It is amazing what you can accomplish if you do not care who gets the credit.
New Users: Read This First
- 04-16-2009 #8Just Joined!
- Join Date
- Apr 2009
- Posts
- 6
cd /boot/grub returns "No such file or directory"
Same thing for ls /boot
I noticed when I ran Grub config, it's asks for the partition to install on. Default value is /dev/sda1. But if I mount the drive and browse the files, /dev/sda1 is not a partition, it's a drive. The actual partition path for sda1 is /mnt/sda1, and that's where the boot folder is. If you specify /mnt/sda1 grub config returns an error that /mnt/sda1 is not linux.
I ran the above commands adding /mnt/sd1 to them ( ie cd/mnt/sda1/boot/grub), the output is attached.
Also, you referenced creating a new directory. To be certain, I need to be in the directory I want to crate the directory in, and use <mkdir menu.lst>?
Sorry this is taking so long, apparently we're on an ~ 12 hour time difference!


Reply With Quote