Re: [Etherboot-developers] More analysis to the old problem with etherboot+GRUB (diskless/disk)

[Christoph Plattner]

So Mr. OKUJI,

        here a question to you in that stuff. Lets see the 
structure of the parts of GRUB:

        stage1
        stage2   or   diskless
        start    or   nbloader
        
My two scenarios:

        booting   stage1 > start > diskless     --> works
        booting   nbloader > diskless           --> fails !

Is there something done or initialized in `stage1' or `start.S'
which is missed anywhere in `stage2' or `diskless'. I have not
found anything.

My first idea was the STACK, but it is defined in `asm.S'. The 
only thing `start.S' passes to `asm.S' is the boot driver, which
is ignored in `asm.S' in diskless binary.
        
Cheers

        Christoph P.



Christoph Plattner wrote:
> 
> Further experiment: It has nothing to do with the DISKLESS GRUB
> version. I booted the "diskless GRUB" from floppy, prepared in
> the following way:
> 
>         in stage2/ :
>         cat start diskless > stage2-diskless
> 
>         then stage1 and stage2 on a floppy with `dd'
> 
> ... and booted. This GRUB works correct, does a bootp, loads the
> menu definedwith `T150="...."' and boots CORECCTLY !!! (no crash !)
> 
> So really diskless booed GRUB has a problem (independent of GRUB
> itself) !
> 
> Etherboot problem ?
> Is GRUB not completely loaded in RAM ?
> 
> Cheers
>         Christoph
> 
> Christoph Plattner wrote:
> >
> > Hello GRUB and Etherboot people,
> >
> >         finally I had some time to further analysing the
> > problem, I describer a week ago.
> >
> > The problem was: I can boot our (company's) OS (multiboot,
> > loaded at 1MB) with a GRUB booted by floppy, kernel and
> > modules loaded via tftp (plus bootp before...)
> >
> > The OS crashes, if I do the same on a diskless booted GRUB.
> >
> > Discussions with KEN YAP leads me to the fact, that the
> > problem is the ethernet board used twice and is perhaps
> > not resetted in the correct way. So I did an experiement
> > unsing to different types of ethernet boards. A working
> > combination was a NE2000/PCI for etherboot and the i82559
> > or 559er base board for the GRUB to download.
> >
> > The result: THE SAME. The kernel crashes.
> > (By the way, I also tried to embedd the eepro100.c file
> > of 4.7.18 into GRUB to have the newest driver... there !).
> >
> > So the problem seems not to be direct a problem concerning
> > ethernet chip handling. So I have again to analyse the
> > differences in those two GRUB versions. Which point can
> > influence the loading of this kernel. I really have no
> > idea, yet. There are only some lines of C code different.
> >
> > And I often use diskless GRUB + Etherboot for Linux, and
> > I never had problems... on really many different machines
> > and embedded industrial PCs.
> >
> > With friendly regards
> >
> >         Christoph P.
> >
> > -----------------------------------------------------------------
> > private:        address@hidden
> > company:        address@hidden
> >
> > _______________________________________________
> > Etherboot-developers mailing list
> > address@hidden
> > http://lists.sourceforge.net/lists/listinfo/etherboot-developers
> 
> -----------------------------------------------------------------
> private:        address@hidden
> company:        address@hidden
> 
> _______________________________________________
> Bug-grub mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-grub


-----------------------------------------------------------------
private:        address@hidden
company:        address@hidden