Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
biosext [2008/03/02 01:12]
mdc
biosext [2008/11/19 01:07]
markwarren Add pointer to RD1 BIOS Savior product.
Line 6: Line 6:
  
 ** Note:  This is completely without warranty. ​ It worked for me.  It may not work for you.  It may wreck your system. ​ If you don't know what you're doing, don't do it.  You have no recourse but to blame yourself and sit in the dark rocking in the fetal position if this fails.** ** Note:  This is completely without warranty. ​ It worked for me.  It may not work for you.  It may wreck your system. ​ If you don't know what you're doing, don't do it.  You have no recourse but to blame yourself and sit in the dark rocking in the fetal position if this fails.**
 +
 +The "​[[http://​www.ioss.com.tw/​web/​English/​RD1BIOSSavior.html|RD1 BIOS Savior]]"​ from [[http://​www.ioss.com.tw/​|IOSS]] is a US$30 device that plugs into the motherboard BIOS ROM socket and allows manual switching between two BIOS chips. ​ This allows you to boot from one BIOS ROM, then switch to a second BIOS ROM chip for trial flashing. If the new BIOS fails, you can switch back to the first, unmodified BIOS ROM, and try again (info from [[http://​en.wikipedia.org/​wiki/​LinuxBIOS|Coreboot]]).
  
 I am currently using a large number of J7F2WE based motherboards for a computing cluster. ​ The machines have no local storage at all, just a 1 GHz Via C7 processor and 1 GB of RAM.  The on-board NIC on the motherboard is based on the VIa Rhine II chipset. ​ My machines also have three more NICs per box, but they don't factor in to getting gPXE loaded. ​ gPXE replaces the Intel PXE code included for the on-board NIC. I am currently using a large number of J7F2WE based motherboards for a computing cluster. ​ The machines have no local storage at all, just a 1 GHz Via C7 processor and 1 GB of RAM.  The on-board NIC on the motherboard is based on the VIa Rhine II chipset. ​ My machines also have three more NICs per box, but they don't factor in to getting gPXE loaded. ​ gPXE replaces the Intel PXE code included for the on-board NIC.
Line 45: Line 47:
 Scan the output for your onbaord NIC, mine showed up as: Scan the output for your onbaord NIC, mine showed up as:
  
-  ​root@bops1-cf:​~# lspci+  # lspci
     ...     ...
   00:12.0 Ethernet controller: VIA Technologies,​ Inc. VT6102 [Rhine-II] (rev 78)   00:12.0 Ethernet controller: VIA Technologies,​ Inc. VT6102 [Rhine-II] (rev 78)
Line 53: Line 55:
 Using the infromation from above, lets interogate the PCI device: Using the infromation from above, lets interogate the PCI device:
  
-  ​root@bops1-cf:​~# lspci -n -s 00:12.0+  # lspci -n -s 00:12.0
     ...     ...
   00:12.0 0200: 1106:3065 (rev 78)   00:12.0 0200: 1106:3065 (rev 78)

Navigation

* [[:start|Home]] * [[:about|About our Project]] * [[:download|Download]] * [[:screenshots|Screenshots]] * Documentation * [[:howtos|HowTo Guides]] * [[:appnotes|Application Notes]] * [[:faq:|FAQs]] * [[:doc|General Doc]] * [[:talks|Videos, Talks, and Papers]] * [[:hardwareissues|Hardware Issues]] * [[:mailinglists|Mailing lists]] * [[http://support.etherboot.org/|Bugtracker]] * [[:contributing|Contributing]] * [[:editing_permission|Wiki Edit Permission]] * [[:wiki:syntax|Wiki Syntax]] * [[:contact|Contact]] * [[:relatedlinks|Related Links]] * [[:commerciallinks|Commercial Links]] * [[:acknowledgements|Acknowledgements]] * [[:logos|Logo Art]]

QR Code
QR Code biosext (generated for current page)