flash-1.txt 3.1KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273
  1. Date: Tue, 18 May 1999 15:45:55 +0200 (MEST)
  2. From: Erik Starback <erik@math.uu.se>
  3. To: netboot@baghira.han.de
  4. Subject: Netboot with Intel EEPRO100+ Management
  5. Message-ID: <Pine.LNX.3.96.990518154313.3875A-100000@anarchy.math.uu.se>
  6. MIME-Version: 1.0
  7. Content-Type: TEXT/PLAIN; charset=iso-8859-1
  8. Content-Transfer-Encoding: 8BIT
  9. Sender: owner-netboot@baghira.han.de
  10. Precedence: bulk
  11. Reply-To: netboot@baghira.han.de
  12. X-Moderator: netboot-owner@baghira.han.de
  13. X-UIDL: 6ca8453c19c46d622813e9be8ada9517
  14. Status: O
  15. X-Status:
  16. Hello!
  17. When Intel eepro100+ NIC disappeared from the market, I didn't know
  18. what to do. I didn't find any information if anyone has used the
  19. new eepro100+ Management Adapter to netboot linux.
  20. I thought that the card should netboot with the same configuration as
  21. the old card when I read Donald Beckers comment:
  22. > The driver should "just work" with the '559. It's not supposed to be
  23. > substantially different than the '558. (I don't have a datasheet
  24. > or sample card to confirm this statement.)
  25. The problem was now only to put the netboot-program to the built in
  26. flash memory on the NIC. With the old card I used a flash memory (Intel
  27. N28F020 [N28010 didn't work])) and the program FUTIL.EXE from Intel to
  28. flash it. FUTIL did't recognize the memory on the management card
  29. and did not work therefore.
  30. I found the intel program FBOOT.EXE that was made to upgrade the built
  31. in Intel BOOT agent. I did: Boot dos from floppy, Run FBOOT (choose
  32. adapter), choose (u)pdate, choose Create restore image, rename the
  33. backup file (in my case 2743BE52.FLS [the eight last hex digits from
  34. the MAC address]), rename your netboot code (in my case netboot 0.8.1)
  35. to the backup files original name (in my case 2743BE52.FLS), run
  36. FBOOT, choose (r)estore.
  37. Voila!
  38. A shorter way (if you don't need the backup of the old Intel BOOT
  39. agent code) is of course: rename netboot file to [the eight last hex
  40. digits from the MAC address].FLS, run FBOOT, choose restore.
  41. Caution: I think it is possible to make a NIC unusable if you have
  42. made the netboot (or etherboot) file with "wrong" parameters. A couple
  43. of month ago I did a etherboot boot file and put it on an old
  44. EEPRO100+ card. It worked fine, but it was impossible to boot local
  45. with it. So I could not boot dos and with FUTIL or FBOOT erase the
  46. flash memory! To erase the chip I had to take out the memory chip,
  47. boot dos and then put in the memory chip. This isn't possible when the
  48. memory chip is build in.
  49. Links:
  50. <http://support.intel.com/support/landesk/configmgr/LSA1_193.HTM>
  51. FUTIL.EXE is a part of LSA1_193.ZIP
  52. <http://support.intel.com/support/etherexpress/pro100/100pboot.htm>
  53. FBOOT.EXE is a part of 100pboot.exe
  54. /Erik S
  55. -------------------------------------------------------------------------
  56. Erik Starbäck, System administrator E-mail address: erik@math.uu.se
  57. Uppsala University Telephone (o): +46 18 4713277
  58. Department of Mathematics Cellular phone: +46 70 4250260
  59. P. O. Box 480 Fax (o): +46 18 4713201
  60. SE-751 06 UPPSALA
  61. Sweden