Subject: [Bug #598] Message "GRUB Floppy Error" when using boot floppy - msg#00114

List: boot-loaders.grub.bugs

Date: Prev Next Index Thread: Prev Next Index

=================== BUG #598: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=598&group_id=68

Changes by: Chris Dryburgh <cdryburghca@xxxxxxxxxxxx>
Date: 2002-Jun-20 17:55 (GMT)

------------------ Additional Follow-up Comments ----------------------------
Bernhard, here are the drives that I have on my machine.
Floppy Drive, LG CD-ROM CRD-8522B, and MAXTOR 6l040J2(Hard Drive)
Changing the boot order did not make any difference. I am beginning to suspect
that I will have to wait for okuji to fix the "482 geometry doesn't work with
floppies" bug.

Thanks,
Chris

=================== BUG #598: FULL BUG SNAPSHOT ===================

Submitted by: CDryburgh Project: grub
Submitted on: 2002-Jun-13 17:08
Category: Booting Severity: Major
Priority: None Bug Group: Software Error
Resolution: None Assigned to: None
Status: Open Release: 0.92
Reproducibility: Every Time Planned Release:

Summary: Message "GRUB Floppy Error" when using boot floppy

Original Submission: Have put the GRUB floppy image on to a floppy and recieve
the message "GRUB Floppy Error". The command line never comes up.

Bad Floppy: No. Get to command line using same floppy on two other computers.

Bad Floppy Drive: No. Plugged floppy drive into another computer and got to
command line.

Incompatiable with BIOS: Only possibility that I can think of.

Message when turnig on computer.

"NVIDIA TNT2 Model 64 VGA BIOS
Version 3.05.00.10
Copyright (c) 1996-2000 NVidia Corp.
32.0 MB RAM"

The BIOS setup screen says "Award BIOS Setup Utility" at the top.

I intend to load the Hurd on to this computer but I understand that the Grub is
required to boot the OS. I have very little understanding of bootloaders so my
assistance with the fix may be limited.

Regards,
Chris

Follow-up Comments
*******************

-------------------------------------------------------
Date: 2002-Jun-20 17:55 By: CDryburgh
Bernhard, here are the drives that I have on my machine.
Floppy Drive, LG CD-ROM CRD-8522B, and MAXTOR 6l040J2(Hard Drive)
Changing the boot order did not make any difference. I am beginning to suspect
that I will have to wait for okuji to fix the "482 geometry doesn't work with
floppies" bug.

Thanks,
Chris

-------------------------------------------------------
Date: 2002-Jun-20 08:20 By: treutwein
Hi Chris,

do you have a ZIP or LS120/LS240 drive connected to you machine ? If so try
either to disconnect and/or changing the BIOS boot order of floppy drives.

I had a similar problem with Phoenix BIOS and a ZIP drive.
It was resolved by changing the boot order of the floppies.

regards
Bernhard

-------------------------------------------------------
Date: 2002-Jun-16 15:54 By: CDryburgh
Thankyou for responding. I have two questions.

1. What is geometry?
I have tried playing with BIOS settings but have not found the correct setting
yet. This looks like something for the FAQ.

2. How can I find the geometry setting on the floppy besides the trial and
error method?

Chris

-------------------------------------------------------
Date: 2002-Jun-16 02:22 By: okuji
I think it is likely that the geometry configured in your
BIOS setting isn't identical with that of your floppy.

Okuji

No files currently attached

For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=598&group_id=68

Was this page helpful?

Thread at a glance:

Previous Message by Date: click to view message preview

What does GRUB GRUB mean on bootup?

I created a floppy with grub and the necessary support files. It boots a PC just fine. When I try it on a PC104 CPU, I see GRUB GRUB and nothing more.

Next Message by Date: click to view message preview

Re: Details on blocklist in stage2/stage1_5

On Thu, Jun 20, 2002 at 07:48:02PM +0200, Thierry Laronde wrote: > > OK, since I wrote a new version of the stage1 and I think Okuji is about > to add it to the official source, here are some hints. > > Things that may likely not change in a near future if the new stage1 is > used (since size optimizations imply to use this very place): > > Identification of the GRUB and boot abi version (MBR/first sector): > > system_id: /* offset 03h */ > .ascii "GRUB " /* exactly 5 bytes */ > .byte COMPAT_VERSION /* + 1 byte */ > .byte STAGE1_VERSION /* + 1 byte */ > .byte 0 /* +1 byte = 8 bytes */ > > The COMPAT_VERSION identifies GRUB boot abi. > STAGE1_VERSION can be ignored for that purpose: it is *only* the > revision version of stage1. > > In stage1 too is the crucial info about the first sector (of stage2 or > stage1_5 that is in fact start.S) to load. It is, in the new version, at > offset: > ---- in stage1/stage1.h > /* The offset of STAGE2_SECTOR. */ > #define STAGE1_STAGE2_SECTOR_OFFSET 0x32 > > ---- in stage1/stage1.S > stage2_sector: > .long 1 > > These are unlikely to change too. For stage2/start.S which is the first > sector of stage2/1_5 the structure MAY change but not in the very next > days... > > What I have in mind for the remaining parts (to have an easy way to > identify what infos need to be changed) --- and that we haven't > discussed so far --- is to create fake (I mean possibly unused) C > headers files exposing the boot info structures, so that one can have a > simple way to update tools having to manipulate this. This MAY be used > too, internally by the GRUB, for booting OSes. So there will be a > running time info (multiboot) and a compile time infos: the headers. The > idea is to change for us the `boot' command so that filling up the > correct structures for OSes will allow us to update more easily (having > too perhaps a way to feed GRUB with this at running time via the > `script' abilities (menu)). One follow up. Reading stage1 (MBR/fist sector) leads one to the first sector of the next stage (stage2 or stag1_5). One possibility could be to put in start.S (the first sector of the next stage) a binary description of the block list structure, since there is more room here. This would complement the headers (always good to have it written somewhere). It is --- for me --- unlikeky that the beginning of the blocklist infos (end of the sector, growing backward) will change. But the structure of the infos here may change (I have in mind some simplifications) in the future. Cheers, -- Thierry Laronde (Alceste) <tlaronde@xxxxxxxxxxx> Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C

Previous Message by Thread: click to view message preview

[Bug #598] Message "GRUB Floppy Error" when using boot floppy

=================== BUG #598: LATEST MODIFICATIONS ================== http://savannah.gnu.org/bugs/?func=detailbug&bug_id=598&group_id=68 Changes by: Bernhard Treutwein <BdT@xxxxxxxxxxxxxxxxxxx> Date: 2002-Jun-20 08:20 (GMT) ------------------ Additional Follow-up Comments ---------------------------- Hi Chris, do you have a ZIP or LS120/LS240 drive connected to you machine ? If so try either to disconnect and/or changing the BIOS boot order of floppy drives. I had a similar problem with Phoenix BIOS and a ZIP drive. It was resolved by changing the boot order of the floppies. regards Bernhard =================== BUG #598: FULL BUG SNAPSHOT =================== Submitted by: CDryburgh Project: grub Submitted on: 2002-Jun-13 17:08 Category: Booting Severity: Major Priority: None Bug Group: Software Error Resolution: None Assigned to: None Status: Open Release: 0.92 Reproducibility: Every Time Planned Release: Summary: Message "GRUB Floppy Error" when using boot floppy Original Submission: Have put the GRUB floppy image on to a floppy and recieve the message "GRUB Floppy Error". The command line never comes up. Bad Floppy: No. Get to command line using same floppy on two other computers. Bad Floppy Drive: No. Plugged floppy drive into another computer and got to command line. Incompatiable with BIOS: Only possibility that I can think of. Message when turnig on computer. "NVIDIA TNT2 Model 64 VGA BIOS Version 3.05.00.10 Copyright (c) 1996-2000 NVidia Corp. 32.0 MB RAM" The BIOS setup screen says "Award BIOS Setup Utility" at the top. I intend to load the Hurd on to this computer but I understand that the Grub is required to boot the OS. I have very little understanding of bootloaders so my assistance with the fix may be limited. Regards, Chris Follow-up Comments ******************* ------------------------------------------------------- Date: 2002-Jun-20 08:20 By: treutwein Hi Chris, do you have a ZIP or LS120/LS240 drive connected to you machine ? If so try either to disconnect and/or changing the BIOS boot order of floppy drives. I had a similar problem with Phoenix BIOS and a ZIP drive. It was resolved by changing the boot order of the floppies. regards Bernhard ------------------------------------------------------- Date: 2002-Jun-16 15:54 By: CDryburgh Thankyou for responding. I have two questions. 1. What is geometry? I have tried playing with BIOS settings but have not found the correct setting yet. This looks like something for the FAQ. 2. How can I find the geometry setting on the floppy besides the trial and error method? Chris ------------------------------------------------------- Date: 2002-Jun-16 02:22 By: okuji I think it is likely that the geometry configured in your BIOS setting isn't identical with that of your floppy. Okuji No files currently attached For detailed info, follow this link: http://savannah.gnu.org/bugs/?func=detailbug&bug_id=598&group_id=68

Next Message by Thread: click to view message preview

RedHat 7.3 + Netboot kernel load failure...

Greets folks... I've just started experimenting with the "nbgrub" portions of GRUB 0.92 and I've hit a bit of a wall. The TFTP exchanges take place, but the system hangs up after displaying "Uncompressing Linux... Ok, booting the kernel." If you're interested in lending a hand, here's the background in brief... GRUB 0.92 is compiled with the following operands: ./configure --enable-diskless --enable-eepro100 The kernel is compiled with the following options: IP: Kernel Level Autoconfiguration IP: Kernel Level Autoconfiguration > IP: BOOTP Support IP: Kernel Level Autoconfiguration > IP: DHCP Support Root NFS Appropriate Network Drivers TFTP is active and properly configured. DHCP (BOOTP) is active and properly configured. >From dhcp.conf: option option-150 "(nd)/client-grub.conf"; filename "nbgrub-0.92-eepro100";

Loading Comments...