Re: Did test ... Re: grub is stuck with an on-board eepro100

[Yedidyah Bar-David]

On Wed, Feb 06, 2002 at 11:13:23AM +0100, Christoph Plattner wrote:
> Hello,
> 
> so I have test result.

Thanks for your testing, but,

> 
> Before going in details: The PCI bus master enabling and the 
> `eepro100.c' driver is working OK !!
> Mr. Okuji has done complete work (including PCI handling).
> 
> To the test case:
> I reused the embedded machine with the define problem. This 
> version of prototype board has definitly a problem, if the
> etherboot driver do not activate the bus master mode.
> 
> I retried this non-working etherboot version - machine 
> cannot communicate via the LAN, althogh all data and output
> on the console seems to be ok.
> 
> Then I tried to boot a current CVS version of GRUB compiled
> with 
> ../grub/configure --enable-diskless --enable-eepro100
> --enable-preset-menu=../ep.preset 

Tried now exactly this (all the same except not a serial console),
both from a floppy and from PXE, and it hangs after printing
Probing...[Intel EtherExpressPro100]Ethernet addr: xx:xx:xx:xx:xx:xx

This version doesn't even print "." every few seconds.

My hardware: An Intel STL2 board, on-board eepro100 whose chip
is labeled:

GD82559
L132LX21

What should I further try to debug?

Thanks,

        Didi

> 
> and a preset menu:
> 
> # serial console setup
> serial --unit=0 --port=0x3f8 --speed=19200
> terminal --timeout=0 serial
> 
> # setup network
> bootp
> 
> I used a floppy boot notto have influence of etherboot, and
> of course I did the boot after power off/on, not to have
> bus master enabled by other influences a boot before.
> 
> GRUB boots from floppy and loads the menu from net (after
> bootp, etc....) --> PASS !
> 
> So your problem is another EEPRO100 chip or a other problem
> case. The PCI setup and eepro100 driver seems to work on
> the quite new 82559ER chip.
> 
> Bye
> Christoph
> 
> 
> 
> Yedidyah Bar-David wrote:
> > 
> > On Wed, Feb 06, 2002 at 02:50:44AM +0900, Yoshinori K. Okuji wrote:
> > > At Tue, 5 Feb 2002 09:36:39 +0200,
> > > Yedidyah Bar-David wrote:
> > > > Of course it's desirable, but is it possible? I don't really know grub,
> > > > but isn't the fact that it's written in C, in 32bit, means it would be
> > > > difficult to call 16 bit APIs? I downloaded the PXE specs, and looked
> > > > at the pxelinux source (all asm), and don't really know what to do.
> > > > E.g., how do I write an function in asm that is callable from C?
> > >
> > > Please take a look at stage2/asm.S, for example. GRUB can switch
> > > between real mode and protected mode. Also, note that PXE has an
> > > interface for protected mode as well.
> > 
> > I will look at that.
> > 
> > >
> > > > I tried Etherboot-5.0.5, and the sympthoms are mostly the same.
> > > > What else should I try?
> > >
> > > Would you like to report the problem to the Etherboot people? Because
> > > Etherboot is the upstream project of the network drivers, it is
> > > preferable to fix the problem in Etherboot and propagate the change to
> > > GRUB afterwards. Furthermore, they are probably better at debugging
> > > network drivers than us.
> > 
> > I will.
> > 
> > >
> > > Thanks,
> > > Okuji
> > 
> >         Didi
> > 
> > _______________________________________________
> > 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