DFI NF570 Build Tutorial - Revision history

Uwe: Hm, "used with permission" it seems. Still, pretty tiny and useless IMHO.

2010-09-26T14:45:27Z

Hm, "used with permission" it seems. Still, pretty tiny and useless IMHO.

2008-12-13T13:54:58Z

2008-12-07T17:33:26Z

2008-12-07T17:26:18Z

2008-11-23T13:48:57Z

2008-11-18T17:16:06Z

2008-11-18T12:05:13Z

2008-11-17T19:25:36Z

2008-11-17T10:11:39Z

2008-11-16T14:21:43Z

← Older revision		Revision as of 14:45, 26 September 2010
Line 10:		Line 10:

	The designers have chosen an identical chip set to the Gigabyte M57SLI, so I only had to make trivial code changes for it to work to the standard shown below. All credit to coreboot's M57SLI team.		The designers have chosen an identical chip set to the Gigabyte M57SLI, so I only had to make trivial code changes for it to work to the standard shown below. All credit to coreboot's M57SLI team.
−
−
−	~~This photograph is used with the kind permission of DFI-Europe, so many thanks to them.~~
−
−	~~[[Image:INFINITY.jpg\| The NF570-M2/G mother board]]~~
−

	The BIOS chip is bottom left, below, and slightly left of the battery.		The BIOS chip is bottom left, below, and slightly left of the battery.

← Older revision		Revision as of 13:54, 13 December 2008
Line 421:		Line 421:
	You should build a static kexec and add that to the coreboot build, I am working on it.		You should build a static kexec and add that to the coreboot build, I am working on it.

−	But this boots my system; I have built kexec on this system,and can boot into other systems from there.	+	But this boots my system; I have built kexec on this system,and can boot into other systems from there; though this is not a good idea unless you stop your services, unmount most partitions, and remount the rest read only.
		+
		+	But I still want a menu so I can choose which system I want; so I am thinking of using some sort of screen, to ask which system the booted kernel will kexec into.

@@ Line 401: / Line 401: @@
 === A Linux Payload ===
-This was a lot easier than I thought it would be.  You need to buy some SST49LF160C chips, So 16 M Bit gives you 2M bytes.  There do not seam to be any bigger chips.
+This was a lot easier than I thought it would be.  You need to buy some SST49LF160C chips, So 16 M Bits gives you 2M bytes.  There do not seem to be any bigger chips.
 You need a system with a small kernel.  The first system on this machine is "Linux from Scratch", and with careful pruning I have got the kernel down to  around 1.8M bytes.
@@ Line 419: / Line 419: @@
 You can use this as a payload now, and change the size of BIOS chip in your build parameters from 4 M bit to 16 M bit.  Then put in a new chip and flash it.
-You should build a static kexec and add that to the coreboot build, I am working on it.  But this boots my system; and I kexec into other systems from that.
+You should build a static kexec and add that to the coreboot build, I am working on it.

@@ Line 242: / Line 242: @@
-== The payload filo ==
+== The payload ==
-See the documentation about coreboot, and why it needs a payload.  So far I have only used filo.
+See the documentation about coreboot, and why it needs a payload.
 Copy your /boot/grub directory to /boot/filo.  This stops any interaction between grub and filo.  Your future BIOS will boot according to /boot/filo/menu.lst, and the hard disk will boot according to /boot/grub/menu.lst.
@@ Line 387: / Line 389: @@
 Build your filo.elf and copy it into /boot.  Boot it via the grub command line and make sure it works.
 == Null Modem Cable ==

@@ Line 129: / Line 129: @@
 |RAM_DDR3_status = N/A
 |RAM_dualchannel_status = Untested
-|RAM_ecc_status = Untested
+|RAM_ecc_status = N/A
-|IDE_status = N/A
+|IDE_status = OK
-|IDE_comments =
+|IDE_comments = My standard Seagate as system disk
 |IDE_CF_status =
 |IDE_CF_comments =

@@ Line 12: / Line 12: @@
-DFI-Europe have given me permission to use this picture, so many thanks to them.
+This photograph is used with the kind permission of DFI-Europe, so many thanks to them.
 [[Image:INFINITY.jpg| The NF570-M2/G mother board]]
@@ Line 518: / Line 518: @@
          return sum == old_sum;
 </pre>
 Now build nvramtool from coreboot's source package, and use it to reset the CMOS value to the correct value.
@@ Line 523: / Line 526: @@
+== Timing ==
 {| border="0" style="font-size: smaller"
@@ Line 546: / Line 549: @@
 |}
 {{PD-self}}

← Older revision		Revision as of 19:25, 17 November 2008
Line 14:		Line 14:
	Here is a picture of the motherboard:		Here is a picture of the motherboard:

−	~~[[Image:INFINITY NF570SLI-M2-G.jpg\|DFI Infinity mother board]]~~	+	Withdrawn, back soon
		+

@@ Line 125: / Line 125: @@
 |RAM_SODIMM_status = N/A
 |RAM_DDR_status = N/A
-|RAM_DDR_comments = N/A
+|RAM_DDR_comments =
 |RAM_DDR2_status = OK
 |RAM_DDR2_comments = Using  2 cards of 2GB 667
@@ Line 436: / Line 436: @@
+.
-The next step is to use that file to flash a brand new chip.  To hot swap the BIOS chip I found it best to lay the machine on its back so you can put the chip out vertically.  So gently extract the BIOS chip and put it into an anti-static bag.  Get one of you new chips and locate it very carefully into position, note the bevel on one corner.  Gentle pressure will now push the chip home.  Put the computer back onto its feet, and check that the chip is there.
+The next step is to use that file to flash a brand new chip.  To hot swap the BIOS chip I found it best to lay the machine on its back so you can put the chip out vertically.  So gently extract the BIOS chip and put it into an anti-static bag.  Get one of your new chips and locate it very carefully into position, note the bevel on one corner.  Gentle pressure will now push the chip home.  Put the computer back onto its feet, and check that the chip is there.
 <pre>

@@ Line 492: / Line 492: @@
 == Gremlins, Bugs and Gotchas ==
 The ethernet gets changed from eth0 to eth1 by udev during the kernel start up.
-Splash screens get wrecked, due to lack of video driver at start up.
+=== My splash screen looks horrible ===
 You might see this error in the coreboot log, and want to correct it.