>So - this is what I see: The client network card does PXE, does tftp and=20 >gets the 3c905c-tpo.lzpxe image, unloads PXE, exec the .lzpxe, discovers=20 >the network card and tries to communicate DHCP-ways. But - the MAC has=20 >changed to some fake one (DHCP server sees the request, but is not to=20 >respond to the client card) Also - from what I see on the client - after=20 >.lzpxe is loaded it discovers the card as having id 0x9400, this differs=20 >from what 3c905c-txm should have (0x9200 according to etherboot's 'NIC')=20
The wrong MAC address is easy to explain. There's a bug in the 3c90x.c driver in which it's getting the MAC address from the wrong location in the EEPROM. Older cards had the same MAC address in both the wrong and the right locations so it still worked. Newer cards don't. The fixed driver is not in any release yet as the fix came in after 5.0.6 was released, but you can get it from the CVS archive at the Etherboot web site. Don't know if the wrong device ID is a related bug. _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.openprojects.net
