On Thu, Nov 04 1999, OKUJI Yoshinori wrote:

Hi again,

> From: Goran Koruga <[EMAIL PROTECTED]>
> Subject: Re: Troubles with grub on my SCSI drive
> Date: Wed, 3 Nov 1999 19:58:36 +0100
> 
> > more news. Geometry command reports the following data : 553/255/63
> > for C/H/S,
> > respectively (this is different from what Linux kernel reports).
> 
>   So GRUB must be able to access the entire disk (553 * 255 * 63 *
> 512bytes = about 4.3GB). The fact that the geometry is different from
> the one reported by Linux is no problem.
> 
> > Is there anything else
> > I could do to figure out where it dies ?
> 
>   Check if the variable STAGE2_SECTOR in the stage1 installed on your
> disk is identical with the location of the first sector of the stage2.
> To see STAGE2_SECTOR, you need to use some utility like ``od''. The
> offset is 0x41 and the size is 4bytes (unsigned long). To see the
> location of the first sector, use the command ``testload'' for the
> stage2. It will print out the sector numbers, and the first one is
> what you should see.

Here's the info :

testload command said that first sector of stage2 file is : 6563727

hex data from offset 0x40 of MBR on hard disk (from Norton's Disk Editor) :

0x40: FF 8F 27 64 00 00 80 00 08 FA EA 4F 7C 00 00 31

So I take it that 4 bytes at offset 0x41 give me : 0x0064278F which is
6563727 in decimal. It looks OK. Sector 6563737 definitely looks like
stage2 file (I compared the one on floppy (because I know where it is)
to this one). Any clues ?

> 
> > I remember that GRUB 0.4 had
> > "debug" mode where it printed letters indicating what it had done so far
> > in stage1 - is there something similar in GRUB 0.5.x ?
> 
>   Yes.

Hmm, I didn't notice anything like that in GRUB 0.5 sources - can you please
enlighten me ? I wanted to add more of my own debugging messages but I was
getting internal errors from gas (I simply copied the relevant lines from
other places in stage1.S).

Thanks, Goran

--

Writing about music is like dancing about architecture.
    -- Frank Zappa 

Reply via email to