https://wiki.fogproject.org/wiki/index.php?action=history&feed=atom&title=SiS-900_based_NIC 2026-06-15T15:25:12Z Revision history for this page on the wiki MediaWiki 1.30.0 https://wiki.fogproject.org/wiki/index.php?title=SiS-900_based_NIC&diff=1201&oldid=prev 2009-01-01T21:17:37Z

<p>New page: A bad designed PXE stack in the SiS 900-based NIC causes FOG to hang on the pxelinux-phase (before the menu appears). In order to get things working without replacing the NIC [http://www.e...</p> <p><b>New page</b></p><div>A bad designed PXE stack in the SiS 900-based NIC causes FOG to hang on the pxelinux-phase (before the menu appears). In order to get things working without replacing the NIC [http://www.etherboot.org Etherboot] comes in handy. Etherboot is an open-source PXE stack, supporting quite a range of NIC's. In order to load Etherboot you have basically three options:<br /> <br /> * Boot from a floppy, to load the PXE stack (not ideal).<br /> * Chainloading Etherboot<br /> * Flashing Etherboot into the system BIOS<br /> <br /> The first option basically explains itself, you'll find pre-compiled images at the [http://www.rom-o-matic.net Rom-o-Matic] website. Write them to floppy using rawwrite or rawwritewin.<br /> <br /> The second option basically loads Etherboot using the NIC's built-in PXE stack (Loading PXE using PXE). When Etherboot is loaded, it will attempt a PXE boot again and will load FOG. To avoid an endless loop, some tricking with the DHCP configuration is need. You'll find an [http://etherboot.org/wiki/pxechaining Howto] on the Etherboot website.<br /> <br /> The third option is a bit tricky, it involves tampering with the system bios which could lead to a bricked mainboard! The PXE code needed to boot from LAN is stored as part of the system bios (in case of onboard NIC's). On some mainboards, you'll be able to replace the existing (buggy) PXE code with Etherboot. Try it at your own risk, you'll find an howto [http://etherboot.org/wiki/biosext here].</div>

Tux-