Re: Etherboot-discuss Digest, Vol 41, Issue 10

Am Sun, 27 Sep 2009 15:37:14 +0200
hat Thomas Miletich <[email protected]> (Thomas Miletich)
folgendes geschrieben:


> The thing is that the old forcedeth cards store their MAC address in
> reverse in the EEPROM, and the new ones store it in the correct order.
> The driver has to know whether to reverse the address or take it as-is
> from the EEPROM. Maybe the Windows driver you use is confused about
> your card's MAC address order.
> Check if there's a updated forcedeth driver for Windows available that
> could fix this problem.
> 
> Please also let us know the MAC address used by Windows and how you
> determined the MAC address is in reverse in Windows. Is it the same
> order as in gPXE when you boot linux or some other Windows?
> 


Hi,
recompiling was not the solution.

I also try to implement a newer driver into the winpe 2.1 image.

I see the reverse order in the dhcp log. Also win pe 3.0 uses the
reverse order, but it configures the network correct, so that i can
ping my iscsi-target.

While booting, the pc gets the preconfigured static IP. Then it boots
winpe with that ip and when the network is configured in winpe,
the MAC is reversed, it gets a new IP and then i was not abel to ping
around from this box.

In linux itself and in windows 2k8, xp all is correct after the OS is
booted.




-- 
Nine (not 9)
Never trust a hippie

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf