Re: [Bug-grub] Grub network booting

[Christoph Plattner]

Hello,

First of all, the 8256EM, is this the number of the chip on it. If this
is the chip nunber, then it is definitlo NO eepro100 NIC. Chips relating
to the eepro100 standard are: 82557, 82558, 82559 and 82559ER.

Further the GRUB driver for the eepro100 is not on the current state of
eepro100 development. Some newer cards with modified EEPROM access are
not working in GRUB. Further the newer 82559ER is not recognized. (I had
written a patch, but this one never came into main stream).

If I had more spare time, I want to update the whole NIC driver stuff
(one day).

So try to find out, what NIC you really have (for example boot Linux
locally or from CD and check `/proc/pci'. The eepro100 cards have the
"vendor ID" 0x8086 and the "chip ID" 0x1229 (82559ER = 0x1209).

Then, if it is a eepro100, I can give you the patch.

With friendly regards
Christoph P.


Jason Thomas wrote:
> 
> not sure how to do what your doing, but you might like to try the latest
> version 0.90
> 
> On Thu, Dec 06, 2001 at 05:43:12PM -0500, John Whitfield wrote:
> > I am using Grub 0.5.96.1 which I downloaded and compiled this
> > afternoon.  I specified --enable-diskless and --enable-eepro100 in my
> > compile.  The diskless computer is a Slim PC MS-6215 with an onboard
> > 8256EM nic.  When I attempt to boot the system I get
> > Probing...[eEPRO100]BOOTP/DHCP fails.  Do I need another driver or is
> > there any suggestion what I have that is wrong.
> >
> > I am also using DHCP rather than BOOTP.  There is an example in the
> > manual of how to pass the menu using T150 to BOOTP.  How is this
> > information passed using DHCP.  I must be overlooking something.

-- 
  +--------V--------+   address@hidden
  |  A L C A T E L  |   -----------------------------
  +-----------------+   Phone: +43 1 27722 3706 
         T A S          Fax:   +43 1 27722 3955