Mac Linux Testing - Revision history

AshleySueMas at 04:42, 24 February 2014

2014-02-24T04:42:04Z

AshleySueMas: /* Wireless Testing */

2013-11-06T00:24:20Z

Wireless Testing

Liliana at 18:14, 17 July 2013

2013-07-17T18:14:21Z

Liliana: /* Wireless Testing */

2013-03-01T21:43:43Z

Wireless Testing

Liliana at 21:42, 1 March 2013

2013-03-01T21:42:38Z

Scellef: And again, because I hate my life

2013-01-04T20:35:47Z

And again, because I hate my life

Scellef: Edited relative links

2013-01-04T20:30:44Z

Edited relative links

Scellef: Added Recovery Mode instructions

2013-01-04T20:25:43Z

Added Recovery Mode instructions

Scellef: /* PowerPC */ Typo

2012-12-28T21:44:52Z

PowerPC: Typo

Scellef: Added processor and battery testing

2012-12-28T21:42:58Z

Added processor and battery testing

@@ Line 69: / Line 69: @@
 Be sure to make the script executable!
   chmod +x $script_name
 [[Category:Macintosh Archive]]

← Older revision		Revision as of 00:24, 6 November 2013
Line 72:		Line 72:

	[[Category:Mac Development]]		[[Category:Mac Development]]
−	[[Category:Macintosh]]	+	[[Category:Macintosh Archive]]

← Older revision		Revision as of 18:14, 17 July 2013
Line 72:		Line 72:

	[[Category:Mac Development]]		[[Category:Mac Development]]
		+	[[Category:Macintosh]]

@@ Line 67: / Line 67: @@
 Otherwise, run our handy wireless setup script: [[Media:Mac-bcm-enable-wifi.sh| Broadcom-setup]]
-Be sure to
+Be sure to make the script executable!
-  chmod +x
+  chmod +x $script_name
 [[Category:Mac Development]]

@@ Line 61: / Line 61: @@
 ==Battery Testing==
 Both Intel and PowerPC Macs can utilize the <code>stress-test</code> loop for battery testing.  See [[Laptop_Testing#Battery_Test|Laptop Testing]] for more details.
 [[Category:Mac Development]]

@@ Line 39: / Line 39: @@
 Alternatively, we can have the Mac PXE boot to our internal network and load Memtest86+ from there.  As Intel Mac firmware utilize a different boot protocol, in order to perform a PXE boot we'll use a utility known as [http://ipxe.org iPXE].  Similarly to Memtest86+, the most straightforward method is to burn an [http://boot.ipxe.org ISO] to disc and boot the Mac from CD.
-Unfortunately, not all Intel Macs will be able to successfully boot from CD, and even then some models (or firmware revisions) will load iPXE but stall during the network bootstrap.  When this is the case, memory testing will have to be conducted inside of an OS: [http://pyropus.ca/software/memtester/ memtester] in Linux, or [http://www.kelleycomputing.net/Rember/ Rember] in OSX.  See the [[#Memory Testing#PowerPC|PowerPC]] section for more information.
+Unfortunately, not all Intel Macs will be able to successfully boot from CD, and even then some models (or firmware revisions) will load iPXE but stall during the network bootstrap.  When this is the case, memory testing will have to be conducted inside of an OS: [http://pyropus.ca/software/memtester/ memtester] in Linux, or [http://www.kelleycomputing.net/Rember/ Rember] in OSX.  See the [[#PowerPC_2|PowerPC]] section for more information.
 As of December 2012, testing is being conducted to see whether iPXE can be chainloaded from a standard Apple network boot.
@@ Line 52: / Line 52: @@
 ''An important thing to note'':  Memory testing utilities are only able to test unused system memory.  When testing memory inside of an OS, a significant portion is used by the operating system, thereby preventing a fully comprehensive test.  This reason in particular is why bootable memory diagnostic utilities are preferable.
-To remedy this issue, we boot into ''Recovery Mode'' ; a limited console environment that utilizes much less of the system memory (typically by a factor of about 10).  See the [[#Recovery Mode#PowerPC|Recovery Mode]] section for instructions.
+To remedy this issue, we boot into ''Recovery Mode'' ; a limited console environment that utilizes much less of the system memory (typically by a factor of about 10).  See the [[#PowerPC|Recovery Mode]] section for instructions.
 * <code>memtester</code>'s syntax looks like this:
    memtester [size of memory to test] [number of passes]

@@ Line 5: / Line 5: @@
 *Battery test procedure
 *When OSX is needed to update firmware, see also [[OSX Bless Testing]]
 ==Processor Testing==
@@ Line 28: / Line 52: @@
 ''An important thing to note'':  Memory testing utilities are only able to test unused system memory.  When testing memory inside of an OS, a significant portion is used by the operating system, thereby preventing a fully comprehensive test.  This reason in particular is why bootable memory diagnostic utilities are preferable.
-To remedy this issue, we boot into ''single-user mode'' mode; a limited console environment that utilizes much less of the system memory (typically by a factor of about 10).  Follow these steps:
+To remedy this issue, we boot into ''Recovery Mode'' ; a limited console environment that utilizes much less of the system memory (typically by a factor of about 10).  See [[#Recovery Mode/PowerPC]] for instructions.
 * <code>memtester</code>'s syntax looks like this:
    memtester [size of memory to test] [number of passes]

@@ Line 38: / Line 38: @@
 * <code>memtester</code>'s syntax looks like this:
    memtester [size of memory to test] [number of passes]
-* Unfortunately, memtester doesn't automatically work up to the available of RAM, so you'll have to manually specify how much you want tested.  In order to see how much free memory is available, run <code>free -m</code> and use the number shown the '''free''' column and the '''Mem:''' row, and specify '''2''' passes.  For example:
+* Unfortunately, memtester doesn't automatically work up to the available of RAM, so you'll have to manually specify how much you want tested.  In order to see how much free memory is available, run <code>free -m</code> and use the number shown under the '''free''' column and the '''Mem:''' row, and specify '''2''' passes.  For example:
    <code>memtester 1005 2</code>
 * memtester will immediately lock all of the memory specified.  If an error is returned, try running it with less memory.