It looks like something messed up with the install because it can't find either the kernel or the initial ramdisk, one of those two.
paste the contents of /boot/grub/menu.lst and the files in /boot/
Did you say the windows one wasn't booting either? Do you have it exactly as I pasted?
Oh, and for the future, NEVER do what you just did again. It will more than likely NEVER work, you can't just switch like that, as the config will be different per distro
Did you say the windows one wasn't booting either? Do you have it exactly as I pasted?
Oh, and for the future, NEVER do what you just did again. It will more than likely NEVER work, you can't just switch like that, as the config will be different per distro
Here's what my menu.lst looks like if it's any help:
Code:
Code:
## ## End Default Options ##
title Ubuntu, kernel 2.6.15-27-386
root (hd0,2)
kernel /boot/vmlinuz-2.6.15-27-386 root=/dev/hda3 ro quiet splash
initrd /boot/initrd.img-2.6.15-27-386
savedefault
boot
title Ubuntu, kernel 2.6.15-27-386 (recovery mode)
root (hd0,2)
kernel /boot/vmlinuz-2.6.15-27-386 root=/dev/hda3 ro single
initrd /boot/initrd.img-2.6.15-27-386
boot
title Ubuntu, memtest86+
root (hd0,2)
kernel /boot/memtest86+.bin
boot
# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/hda1
title Windows NT/2000/XP (loader)
root (hd0,0)
savedefault
makeactive
chainloader +1
It won't help much chip, as they can be radically different. For example, here's mine, notice the 'missing' initrd lines? (and, of course, the change in the kernel names)
Code:
Code:
default 2
timeout 10
splashimage=(hd0,1)/boot/grub/splash.xpm.gz
title=AMD64 Gentoo Linux 2.6.17-r7
root(hd0,1)
kernel /boot/kernel-2.6.17-gentoo-r7 root=/dev/sda2
title=AMD64 Gentoo Linux 2.6.15-r5
root(hd0,1)
kernel /boot/kernel-2.6.15-gentoo-r5 root=/dev/sda2
title=Windows XP Pro
rootnoverify (hd0,0)
makeactive
chainloader +1
Here is /boot -> http://www.geocities.com/soad1101/boot.zip
This is menu.lst. I took out most of the comments. The full version is in the zip.
Code:
This is menu.lst. I took out most of the comments. The full version is in the zip.
Code:
# This sets the default entry to boot.
# Remember that GRUB counts from 0, so 1 is the second entry.
default 0
# This sets the length of time in seconds that grub will wait for the user to select an OS
# before it boots the default on. I reccommend at least 15 seconds.
timeout 15
# Enter the entry for DSL here. Something like this.
title DSL
kernel /boot/linux24 root=/dev/hda2 quiet vga=normal noacpi noapm nodma noscsi frugal
initrd /boot/minirt24.gz
title DSL fb800x600
kernel /boot/linux24 root=/dev/hda2 quiet vga=788 noacpi noapm nodma noscsi frugal
initrd /boot/minirt24.gz
title DSL fb1024x768
kernel /boot/linux24 root=/dev/hda2 quiet vga=791 noacpi noapm nodma noscsi frugal
initrd /boot/minirt24.gz
title DSL fb1280x1024
kernel /boot/linux24 root=/dev/hda2 quiet vga=794 noacpi noapm nodma noscsi frugal
initrd /boot/minirt24.gz
title=Windows on Second Drive
rootnoverify (hd1, 0)
makeactive
chainloader +1
Try this grub entry
Code:
Post the contents of /etc/lilo.conf also, please. Oh, and its a little late now, but you just needed to add this to lilo.conf get lilo to boot windows, oops (you *can* switch back by just running /sbin/lilo )
Code:
Code:
title DSL (test)
root(hd0,1)
kernel /boot/linux24 root=/dev/hda2Post the contents of /etc/lilo.conf also, please. Oh, and its a little late now, but you just needed to add this to lilo.conf get lilo to boot windows, oops (you *can* switch back by just running /sbin/lilo )
Code:
other=/dev/hdb1
label=windows
This is lilo.conf
Code:
Code:
vga=791
# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# --------------- `install-mbr(8)', `/usr/share/doc/lilo/',
# and `/usr/share/doc/mbr/'.
# +---------------------------------------------------------------+
# | !! Reminder !! |
# | |
# | Don't forget to run `lilo' after you make changes to this |
# | conffile, `/boot/bootmess.txt', or install a new kernel. The |
# | computer will most likely fail to boot if a kernel-image |
# | post-install script or you don't remember to run `lilo'. |
# | |
# +---------------------------------------------------------------+
# Support LBA for large hard disks.
#
lba32
# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
#disk=/dev/hde
# bios=0x81
#disk=/dev/sda
# bios=0x80
# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda
# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hda1
# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller. Using `compact' is especially recommended when
# booting from a floppy disk. It is disabled here by default
# because it doesn't always work.
#
# compact
# Installs the specified file as the new boot sector
# You have the choice between: bmp, compat, menu and text
# Look in /boot/ and in lilo.conf(5) manpage for details
#
install=/boot/boot-menu.b
# Specifies the location of the map file
#
map=/boot/map
# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration. If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well. Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000
# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=20
# You can put a customized boot message up if you like. If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress. `single-key' goes with the `alias' lines in the
# `image' configurations below. eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
# prompt
# single-key
# delay=100
# timeout=100
# Kernel command line options that apply to all installed images go
# here. See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""
append="hda=scsi hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi apm=power-off nomce noapic"
# Boot up Linux by default.
#
default=Linux
image=/boot/linux24
label=Linux
read-only
# restricted
# alias=1
image=/vmlinuz.old
label=LinuxOLD
read-only
optional
# restricted
# alias=2
# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
# label=HURD
# restricted
# alias=3
For whatever reason, it didn't even show up on grub's list when I booted.
EDIT: How do I switch it from a live cd? Do I do /sbin or /mnt/hda1/sbin?
EDIT: How do I switch it from a live cd? Do I do /sbin or /mnt/hda1/sbin?
Try this. When at the grub boot menu, hit the letter 'e' (i think thats it - look at the bottom, whatever one is for 'edit'), then edit out the initrd line and hit 'b' to boot it
Otherwise you have to run lilo from a chroot. From the livecd "chroot /mnt/hda1", "env-update", "source /etc/profile" - then just run "/sbin/lilo" (theoretically, i'm not 100% certain about that, sorry)
Otherwise you have to run lilo from a chroot. From the livecd "chroot /mnt/hda1", "env-update", "source /etc/profile" - then just run "/sbin/lilo" (theoretically, i'm not 100% certain about that, sorry)
Kllrnohj wrote:
Try this. When at the grub boot menu, hit the letter 'e' (i think thats it - look at the bottom, whatever one is for 'edit'), then edit out the initrd line and hit 'b' to boot it
It just said unknown commmand when I tried that.
Kllrnohj wrote:
Otherwise you have to run lilo from a chroot. From the livecd "chroot /mnt/hda1", "env-update", "source /etc/profile" - then just run "/sbin/lilo" (theoretically, i'm not 100% certain about that, sorry)
When I try "chroot /mnt/hda1" it says, "chroot: cannont change root directory to /mnt/hda1: Operation not permitted
er, my bad, try "chroot /mnt/hda1 /bin/bash" - make sure /mnt/hda1 is mounted, of course
as for the grub, look at the bottom, it should say "press xyz to edit" or something along those lines - it might be c - like I said, just read the instructions on the bottom
as for the grub, look at the bottom, it should say "press xyz to edit" or something along those lines - it might be c - like I said, just read the instructions on the bottom
Kllrnohj wrote:
er, my bad, try "chroot /mnt/hda1 /bin/bash" - make sure /mnt/hda1 is mounted, of course
I got the same error message.
Kllrnohj wrote:
as for the grub, look at the bottom, it should say "press xyz to edit" or something along those lines - it might be c - like I said, just read the instructions on the bottom
No, it was 'e'. I edited out the initrd line, like you said, but got that error when I tried to boot it.
oh, i forgot to mention this, but to do a chroot you must be root - i just assumed the live cd booted as root, if not, switch to root first, sorry
As for the grub, try having it match the one that I posted if its not showing up when you added it to menu.lst
As for the grub, try having it match the one that I posted if its not showing up when you added it to menu.lst
Kllrnohj wrote:
Otherwise you have to run lilo from a chroot. From the livecd "chroot /mnt/hda1", "env-update", "source /etc/profile" - then just run "/sbin/lilo"
I got env-update as "command not found"
then skip that and go straight to the /sbin/lilo part - although i'm not 100% positive that will work, I'm trying to adopt it from the way its done in Gentoo 
If all else fails it looks like a reinstall might be your best option...
EDIT: This looks promising: http://www.damnsmalllinux.org/wiki/index.php/Installing_Grub
If all else fails it looks like a reinstall might be your best option...
EDIT: This looks promising: http://www.damnsmalllinux.org/wiki/index.php/Installing_Grub
Kllrnohj wrote:
then skip that and go straight to the /sbin/lilo part - although i'm not 100% positive that will work, I'm trying to adopt it from the way its done in Gentoo
It says "Fatal: open /dev/hda: Permission denied"
EDIT: I tried the example from the DSL Wiki
title DSL
root (hd0,0)
kernel /boot/linux24 root=/dev/hda1
makeactive
boot
It says:
root (hd0,0)
Filesystem type is ext2fs, partion type 0x83
makeactive
boot
Error 8: Kernal must be loaded before booting
EDIT2: I changed the windows one from root (hd0,1) to root(hd1,0). It said "Error 11: Unrecognized device string"
Uh... foamy? Thats not what I told you to put for the windows one
Code:
Did you forget that already?
(note that I had (hd1,0), not (hd0,1) - also note that its rootnoverify not just root)
As for the linux one, try removing the "makeactive" line and/or the "boot" line
EDIT: Oh, and you WERE root when you were trying to run lilo, right?
Code:
title=Windows On Second Drive
rootnoverify (hd1,0)
makeactive
chainloader +1Did you forget that already?
(note that I had (hd1,0), not (hd0,1) - also note that its rootnoverify not just root)
As for the linux one, try removing the "makeactive" line and/or the "boot" line
EDIT: Oh, and you WERE root when you were trying to run lilo, right?
Kllrnohj wrote:
Uh... foamy? Thats not what I told you to put for the windows one
Code:
Did you forget that already? (note that I had (hd1,0), not (hd0,1) - also note that its rootnoverify not just root)
As for the linux one, try removing the "makeactive" line and/or the "boot" line
EDIT: Oh, and you WERE root when you were trying to run lilo, right?
Code:
title=Windows On Second Drive
rootnoverify (hd1,0)
makeactive
chainloader +1Did you forget that already?
(note that I had (hd1,0), not (hd0,1) - also note that its rootnoverify not just root)
As for the linux one, try removing the "makeactive" line and/or the "boot" line
EDIT: Oh, and you WERE root when you were trying to run lilo, right?
I tested what you said to do for windows, first. It didn't work, either. What I posted there is from the link you posted. That didn't work either.
EDIT: Grub's default options won't boot because I don't have /boot/minirt24.gz What is that, and where can I get it? I checked /boot on the live cd, but I didn't see it there.
EDIT2: I got mad and just reinstalled DSL.
EDIT3: After a fresh install, I tried setting up grub for windows again. I editted it to
Code:
rootnoverify (hd1,0)
makeactive
chainloader +1Instead of giving me an error, it said, "Booting command-list" then
Code:
rootnoverify (hd1,0)
makeactive
chainloader +1Register to Join the Conversation
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Advertisement