Re: grub is stuck with an on-board eepro100

[Christoph Plattner]

Hello.

I had the same problem on a embedded board, where the PCI Bus Master
was not activated by the driver. 
In older etherboot versions (up to 5.0.4) there was a code to activate
the BM mode. Now etherboot does this in gerneral in the PCI stuff. 
We have to check, if this is also done in the GRUB now on a central
place, or if the PCI stuff is not fully updated in GRUB.

But of course, this is only one of many reasons for the problem,
but it looks like this ...

With friendly regards
Christoph P.


Yedidyah Bar-David wrote:
> 
> Hello,
> 
> First, Thank you for your time devoted to grub. I use it as a boot
> menu for a few tens of PCs that boot from the network.
> 
> Now, to my problem:
> On 2 different machines with an on-board eepro100, grub is loaded
> successfully from the tftp server, but freezes shortly after.
> On other machines with an on-board eepro100 it works well, as well
> as on machines with a PCI card eepro100.
> 
> I #defined DEBUG 1 at the beginning of eepro100.c, with grub 0.91,
> and this is what I get:
> =========================================================================
> CLIENT MAC ADDR: xx xx xx xx xx xx  GUID: xxxxxxxx-xxxx-xxxx-xxxxxxxxxxxx
> CLIENT IP: xxx.xxx.xxx.xxx  MASK: 255.255.255.0 DHCP IP: xxx.xxx.xxx.xxx
> GATEWAY IP: xxx.xxx.xxx.xxx
> Found Intel EtherExpressPro100 at 0x1400, ROM address 0x0000
> Probing...[Intel EtherExpressPro100]Ethernet addr: xx:xx:xx:xx:xx:xx
> Setup_eaddr:
> 00031A80  00 00 01 00 A0 56 02 00 00 D0 B7 B8 16 FF 00 00
> 00031A90  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> transmitting type 0800 packet (576 bytes). status = A000, cmd=0100
> txfd:
> 00031A80  00 00 0C 40 80 1A 03 00 90 1A 03 00 00 80 20 02
> 00031A90  EC 7B 06 00 0E 00 00 00 EC 7C 06 00 40 02 00 00
> s1 = 0000, s2 = A000.
> .
> ========================================================================
> The last 4 lines repeat (without DEBUG, I only get the "." repeating).
> 
> This machine does boot well with pxelinux (from syslinux), and Linux
> also works well, including doing dhcp and mounting nfsroot.
> 
> Besides hoping for a solution, I have a question: Is it possible to
> add a pseudo-driver that will use the PXE? How difficult would it be
> for me to do, assuming I don't have much experience with such low-level
> programming.
> 
> Thanks,
> 
>         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