Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
romburning [2007/11/19 14:40] mcb30 |
romburning [2010/08/28 14:30] (current) alecjw |
||
|---|---|---|---|
| Line 44: | Line 44: | ||
| cd gpxe/src | cd gpxe/src | ||
| - | make bin/pci_1186_4300.rom | + | make bin/11864300.rom |
| {{ :bootrom.jpeg?120x96|An expansion ROM}} | {{ :bootrom.jpeg?120x96|An expansion ROM}} | ||
| - | where //1186// and //4300// are the PCI vendor and device IDs for your network card. Make a note of the ROM image file (//bin/pci_1186_4300.rom// in the above example). | + | where //1186// and //4300// are the PCI vendor and device IDs for your network card. Make a note of the ROM image file (//bin/11864300.rom// in the above example). |
| + | |||
| + | Check the size of the ROM image file. If your BIOS does not support PCI 3.0, it must fit alongside any other option ROMs in your system (video cards often take up 50kb or so, and bootable RAID and SCSI controllers take up space as well) in the 128kb option ROM space. If you overflow this space, the result will depend on your BIOS; maybe gPXE won't be loaded at all, maybe you'll get an error message with an option to continue, maybe your boot will freeze entirely. To recover the NIC in the latter situation, see the "Recovering from a bad flash" section below. | ||
| ===== Burning the image into ROM ===== | ===== Burning the image into ROM ===== | ||
| Line 54: | Line 56: | ||
| To burn the image file into ROM, you will need to use a utility specific to your network card. Instructions are available for: | To burn the image file into ROM, you will need to use a utility specific to your network card. Instructions are available for: | ||
| - | * [[:romburning:e1000|Intel gigabit adapters (e1000)]] | + | * [[:romburning:intel|Most Intel adapters]] |
| + | * [[:romburning:tg3|Broadcom 57xx based adapters (tg3)]] | ||
| + | * [[:romburning:3com|3COM 3C905 adapters]] | ||
| + | * [[:romburning:qemu|QEMU option 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. | ||
| + | |||
| + | ===== Recovering from a bad flash ===== | ||
| + | If you accidentally burn a corrupted ROM image file, or with some buggy BIOSes even a perfectly fine one that's large enough to overflow option ROM space, you will likely run into a dilemma: you can't boot your system with the NIC installed, but you need to run a program with the NIC installed in order to reflash it. The solution to this is //not// an attempt at PCI hot-plugging (it has been tried and did not work); instead, try these suggestions. | ||
| + | |||
| + | 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 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... | ||
| + | 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. | ||
