[SOLVED] Grub4dos booting error Minimal BASH-like line editing pendrivelinux
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
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.
Click Here to receive this Complete Guide absolutely free.
Grub4dos booting error Minimal BASH-like line editing pendrivelinux
This seems to be a pretty common problem but I have been unable to resolve it after reading many forum posts.
I am trying to boot to a USB flash drive that was created using pendrivelinux that contains iso's for Ubuntu, PartedMagic, and a few more. This flash drive boots fine on any other machine that I have tried booting it with in the past two years.
The screen that I am stuck on is the familiar:
GRUM4DOS 0.4.5b 2010-11-24, Mem: 638K/2013M/0M, End: 34D578 [Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ]
So far, I have only encountered this issue on this particular set of hardware. This hardware boots to Windows Vista just fine that is on the internal hard drive.
Hardware is as follows:
AMD Athlon 64 3800+ 2.4Ghz
ASUS M2NBP-VM CSM Motherboard
Is there any reason that this will not boot on this particular set of hardware?
The USB is set up with a syslinux menu that allows the user to select which image they would like to boot to. That part works perfectly fine like usual. The issue comes when trying to boot to any of those images, it comes up with the pre-described text.
If there is any other information that is needed, please let me know.
If you used pendrivelinux to create the flash drive on windows, it would be using syslinux as the bootloader. Where is Grub4Dos and how does it fit into the picture, why would it be needed. I have never used pendrivelinux or the windows software Grub4DOS as I prefer to multiboot flash drives with Grub or Grub2. I guess that would be a problem for you since you seem to only have windows vista??
I guess I am not quite sure as to why the grub4dos screen comes up. Its just like a simplified bash terminal that does not have very many options. I did not use the software Grub4DOS, which is why I'm confused as to why it is coming up. The syslinux menu comes up as expected when I boot to the usb flash drive. I used the pendrivelinux software on windows 7. Windows vista is just the OS that happens to be on the hard drive of the machine I am trying to boot to linux on. My end goal is to just wipe the drive and install either CentOS or Ubuntu on it. Before I do that, I was wanting to boot to parted magic to check the health of the hard drive since I recently just picked up this box for cheap. This flash drive works perfectly fine on all the other systems I have used it on in the past having no issue at all.
More specifically, I used XBOOT from pendrivelinux.
Do you mean that when you boot the flash drive you see the syslinux menu which you see when booting the flash on other computers but on this specific machine it takes you to the specified Grub4Dos you described? If you have a Linux system installed you might try putting the flash in the drive when booted to it and take a look at the files when the flash is mounted to see if there are any Grub4Dos files. That doesn't really seem like a logical possibility though. Maybe Grub4Dos is on the vista machine somewhere.
Do you mean that when you boot the flash drive you see the syslinux menu which you see when booting the flash on other computers but on this specific machine it takes you to the specified Grub4Dos you described?
That is correct.
Originally Posted by yancek
If you have a Linux system installed you might try putting the flash in the drive when booted to it and take a look at the files when the flash is mounted to see if there are any Grub4Dos files. That doesn't really seem like a logical possibility though. Maybe Grub4Dos is on the vista machine somewhere.
On the Root of the flash drive, there is a direcotry called Boot. Inside there, there are two more directories named grub4dos and syslinux. The config files in both (.cfg for syslinux and .lst for grub4dos) appear to have many of the same things in them. On the boot menu for the flash drive, there are two directories besides the default boot to hard drive and Help!. They are Utility and Linux (those are the two categories of iso's that I have on the drive). The syslinux has many .cfg files along with an .mbr file, and .c32 files. These all look correct. The grub4dos folder has only the linux.lst and utility.lst for the two directories on the boot screen.
Since this flash drive works everywhere else besides this one machine, is there any reason that the hardware in the machine would not allow it to be booted into a linux drive? I just find it really weird that the syslinux part comes up perfectly fine then it just will not boot into the other iso files. If there is some insight on any of this, that would be really helpful.
Usually it's the video card that will give you the most trouble (to the point of not booting at all), but that usually leads to a black screen, and that's not what you are reporting. But it is something that can mess you up.
Here's where you can get some help in editing your grub to boot without acpi support:
The problem is that the nVidia GeForce 6 is integrated with the motherboard. I tried both adding acpi=off to the boot parameters within the syslinux boot menu and completely disabled ACPI and APIC Support from the BIOS since both ACPI and APIC are in the same option in my BIOS. I am running the latest non-beta version of the bios on the motherboard. (version 0902)
In the "askubuntu" link, there were some other variations on the no acpi theme. Did you try these?
I've recently purchased a HP Envy 17 j053ea machine to take advantage of the i7 and oodles of memory .. Cutting to the chase I suffered from many issues with this install .. the wireless didn't work, the screen "black screened" during installation and thereafter during booting. The get around for the black screen was the boot option acpi=off ... but this of course meant that the laptop would not suspend when I closed the lid -> clearly suboptimal ... After searching for the past two days I have found many good articles/explanations of acpi and a much better option:
Then I found: No ACPI support for my PC, what can I do? from irrational_john ... way to go .. acpi=ht didn't work but pci=noacpi has done the trick ... many thanks … for your hardware I'd recommend John's approach pf cycling through the options he provided:
I don't know why there would be both Grub4Dos and syslinux on the flash. I suppose it might be something used with pendrivelinux as it like Grub4Dos is windows software. Never having used either I don't have any insight. I usually use either Grub Legacy or Grub2 as described in the link posted by rootboy above.
Do you see the Grub4Dos error after selecting any option from the syslinux menu? Any/all of the different entries give the same result?
Sorry for the late reply, haven't had a whole lot of time to mess with it this week.
yancek, Yes, the error would occur after any selection from the syslinux menu.
However, I am not sure what the actual issue is, I am assuming something with the grub4dos that is on there along with the syslinux. I was unable to ever get that flash drive to boot, but I did download a minimal install of CentOS 7 iso file and used a terminal on my Mac to write the iso to my flash drive using the dd command. This worked to install CentOS on a different machine so I decided to try and boot the machine that has been giving me the problems and it booted perfectly fine to the GUI installer, so I would say it would be an issue with the Grub4Dos and compatibility of some sort with the hardware.