Re: More analysis to the old problem with etherboot+GRUB (diskless/disk)

[Christoph Plattner]

Further tested leads to following result in the problem described in the 
following lines.

If you all remember, I had the problem (and I already have it) that a
multiboot kernel loaded at 0x00100000 and above crashes, if I boot GRUB
itself via etherboot but booting GRUB from floppy, the kernel works
well.

New experiments leads to following details:
(1)     GRUB is NOT the problem
(2)     Etherboot OR Netboot (Kuhlman) together with our kernel consequneces
        in a crash.

Following experiment shows this:
If I run etherboot (from ROM or floppy) and I select to load from local
(L)
disk, the GRUB is loaded locally from floppy and the kernel crashes.
If I removed the boot rom (or boot floppy for etherboot) and boot GRUB
again
from the local floppy, the kernel boots.
If I use netboot-0.9 by Kuhlman, I see the same effect like in
etherboot.

Again. The problem is NOT the ethernet driver in etherboot/netboot. Our
kernel
does not access network at this time and not the here used NICs. 
Furhter the experiements are done with two different cards. I se
etherboot via
NE2000/ISA and GRUB via eepro100 (I also have the same effect using only
one NIC).

The problem is a consequence of any setup of memory/BIOS stuff or
whatever. 
There must be a initialization in the package (I don't mean init of NICs
here), 
which is incomaptibe with this kernel (delivered from a known company
...) ...

Please etherboot developers and Netboot developers, help me here in
finding a
point of CPU/memory/Chipset/Bios initialization (I also will read
sources),
which can produce the problem.

And again. The problem also exists (!) if I use the option `L' for
loading local
from disk, so I do not use functionality of etherboot, only the fact,
that it is
started, the kernel crashes !!!

With friendly regards

        Christoph Plattner



Christoph Plattner wrote:
> 
> Yes, a Linux kernel works, or seems to work. We don't know, if
> there is a wrong byte in the code.....
> 
> GRUB loads out multiboot kernel at 1MB and beyond.
> 
>         Christoph P.
> 
> -----------------------------------------------------------------
> private:        address@hidden
> company:        address@hidden
> 
> Thierry Laronde wrote:
> >
> > On Thu, Feb 22, 2001 at 09:45:55AM +0100, 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...)
> >
> > IIRC, you said that the problem doesn't appear with non multiboot kernels ?
> > When you say "loaded at 1MB" you mean loaded in protected mode beyond 1MB ?
> >
> > Cheers,
> > --
> > Thierry LARONDE, Centre de Ressources Informatiques, Archamps - France
> > http://www.cri74.org
> > PingOO, serveur de com sur distribution GNU/Linux: http://www.pingoo.org
> >
> > _______________________________________________
> > Bug-grub mailing list
> > address@hidden
> > http://mail.gnu.org/mailman/listinfo/bug-grub
> 
> --
>   +--------V--------+   address@hidden
>   |  A L C A T E L  |   -----------------------------
>   +-----------------+   Phone: +43 1 27722 3706
>          T A S          Fax:   +43 1 27722 3955
> 
> _______________________________________________
> Bug-grub mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-grub

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