- #Grub4dos boot iso download install#
- #Grub4dos boot iso download iso#
- #Grub4dos boot iso download windows#
#Grub4dos boot iso download iso#
Right? So you know you can do that with the ISO file and GRUB for DOS to start it going. You successfully completed the installation, and at the end of it Anaconda said to reboot. I thought maybe your optical drive is busted, or maybe you tried a disk and it failed to boot (not unheard of lately).
#Grub4dos boot iso download install#
And there also are legitimate reasons to install from the ISO file and not burn it to a disk (also an easier way). I thought you had one of those reasons (you never said why, and people usually don't like having their motives questioned). There are some legitimate reasons to use another boot loader to boot Fedora and not to allow Anaconda (the Fedora installer) to disturb the existing boot loader arrangement. Then you don't need to be doing what we've been talking about so far. I don't perfer Grub4Dos or whatever, I just want the shortest way. Some things to try at the GRUB for DOS command line (grub>). It's also available by pressing the 'c' key at the menu. The GRUB shell is called "command line" in your GRUB for DOS menu. That is the stuff you need to fix your GRUB for DOS menu.lst file. You can use those commands to find the Fedora boot partition with absolute certainty, see the actual names of vmlinuz and initramfs, and even to cat the contents of the grub.cfg file. P.S.: GRUB for DOS's GRUB shell prompt (grub>) can be used to find files, list the contents of directories, cat the contents of text files, etc. Another thing that matters, and which nothing posted so far can confirm, is that "/boot" should be added to the paths of the kernel and initrd menu commands if you chose not to create a separate boot partition for Fedora. You somehow will have to get a look at those in the actual /boot/grub/grub.cfg file to get something that will work. And finally, the name of the initial ram filesystem file is incomplete. Next, that device name in the root= parameter is missing a letter. First, that can't possibly be the complete name of the vmlinuz file. That has several typos, so it never had a chance of working.
#Grub4dos boot iso download windows#
Here, just for more examples, is my simple GRUB4DOS menu.lst that I use on this machine to boot Arch Linux, two Linux From Scratch systems, and Windows XP. And you can change those nerve-jangling colors. If you choose this method, it will have to be repeated when the kernel updates (that doesn't bother me).Īfter that's working, and if you desire it, you also can get rid of the other stuff in the GRUB4DOS menu. When (if) it boots, then you simply can copy and paste the more verbose stuff from /boot/grub/grub.cfg into the kernel command of the GRUB for DOS menu.lst file (you know, all that cryptic kernel parameter stuff). It may not be pretty, but I've booted Fedora with just those two things in the kernel line before. For the kernel menu command, you probably can get it to boot with just the vmlinuz filename and the device name of the root partition for the root= parameter (you know, /dev/sda1 or whatever it's probably an LVM PV). Again use the old legacy numbering for GRUB for DOS.
You again change x & y to the drive & partition of the Fedora boot partition. When the dialog box prompting for the installation image appears, enter the device name of the partition with the ISO file. P.P.S.: Try putting the ISO file, vmlinuz, and initrd.img in the root directory of any compatible partition (vfat, ext2/3/4) that will not be formatted by the installation, and then launch vmlinuz and initrd.img from GRUB for DOS in the usual and simple way.
So maybe /images/install.img actually went away with the last Fedora version. P.P.S.: The Fedora 15 Installation Guide still mentions /images/install.img, but the file was not present in the /images folder of that DVD either. GRUB for DOS has been my main and only boot loader for a long time now. It's only role would be to load and execute vmlinuz and initrd.img which it is perfectly capable of doing. P.S.: GRUB for DOS surely is not part of the problem even though it is in the thread title. Maybe somebody will have more to say if you describe more precisely where the ISO file is located, where vmlinuz and initrd.img are located, what filesystem types are being used, what you tried step-by-step, and when in the steps you are seeing that error message. After all, it wasn't that long ago (Fedora 9) that /images/install.img wasn't involved (didn't exist, really) in the Hard Drive alternative installation method. It still was in the Fedora 15 guide, but gone now for Fedora 16. Preparing for a Hard Drive Installation". But the Installation Guide for Fedora 16 has conspicuously omitted the part about /images/install.img from "5.2. I haven't installed Fedora from the ISO file in a while, so I have no first-hand experience with Fedora 16.
0 kommentar(er)
