Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
romburning [2009/08/10 21:50] rwcr |
romburning [2010/08/28 14:30] (current) alecjw |
||
|---|---|---|---|
| Line 58: | Line 58: | ||
| * [[:romburning:intel|Most Intel adapters]] | * [[:romburning:intel|Most Intel adapters]] | ||
| * [[:romburning:tg3|Broadcom 57xx based adapters (tg3)]] | * [[:romburning:tg3|Broadcom 57xx based adapters (tg3)]] | ||
| + | * [[:romburning:3com|3COM 3C905 adapters]] | ||
| * [[:romburning:qemu|QEMU option ROM]] | * [[:romburning:qemu|QEMU option ROM]] | ||
| * [[:romburning:vbox|VirtualBox LAN boot ROM]] | * [[:romburning:vbox|VirtualBox LAN boot ROM]] | ||
| + | * [[:appnotes:gpxeonvmware|VMware e1000 ROM]] | ||
| It probably goes without saying, but you should not boot DOS over SAN from the NIC you're flashing in order to flash it! MEMDISK is safe, though. | It probably goes without saying, but you should not boot DOS over SAN from the NIC you're flashing in order to flash it! MEMDISK is safe, though. | ||
| Line 68: | Line 70: | ||
| Most likely you will be able to enter BIOS Setup before the point at which your boot fails. Search for any option to disable Option ROM scan, either globally or for the PCI slot containing your network card. Try putting gPXE very late in the boot process. If you own a ROM burner and your NIC has a socketed ROM, you can use the ROM burner to erase the ROM; the BIOS won't try booting any option ROM that's missing the 55 AA signature. | Most likely you will be able to enter BIOS Setup before the point at which your boot fails. Search for any option to disable Option ROM scan, either globally or for the PCI slot containing your network card. Try putting gPXE very late in the boot process. If you own a ROM burner and your NIC has a socketed ROM, you can use the ROM burner to erase the ROM; the BIOS won't try booting any option ROM that's missing the 55 AA signature. | ||
| - | If that doesn't work, you'll need to acquire either another gPXE-flashable NIC. Take the bad NIC out of your computer, and flash gPXE onto the new NIC. Put both NICs in your computer, such that the new NIC has a lower PCI bus:dev:fn number than the bad NIC; usually this means the new NIC should be closer to the CPU. Now boot. The BIOS will scan for option ROMs in PCI bus order, so gPXE on the new NIC gets called to initialize itself before the old NIC has a chance to screw things up. When you get prompted with | + | If that doesn't work, you'll need to acquire another gPXE-flashable NIC. Take the bad NIC out of your computer, and flash gPXE onto the new NIC. Put both NICs in your computer, such that the new NIC has a lower PCI bus:dev:fn number than the bad NIC; usually this means the new NIC should be closer to the CPU. Now boot. The BIOS will scan for option ROMs in PCI bus order, so gPXE on the new NIC gets called to initialize itself before the old NIC has a chance to screw things up. When you get prompted with |
| Press Ctrl-B to configure gPXE... | Press Ctrl-B to configure gPXE... | ||
| do so. You now have a regular gPXE prompt, capable of loading e.g. a DOS floppy using MEMDISK that contains a flash tool to fix your broken NIC. | do so. You now have a regular gPXE prompt, capable of loading e.g. a DOS floppy using MEMDISK that contains a flash tool to fix your broken NIC. | ||
