Classic Mac OS debugging output - Revision history

Huntertur: /* Bitflags */ Note Mac OS 8.6

2025-09-26T07:14:07Z

Bitflags: Note Mac OS 8.6

← Older revision		Revision as of 07:14, 26 September 2025
Line 70:		Line 70:

	Adding all the bitflags together that enable logging (anything with an asterisk) gives 3013FFF.		Adding all the bitflags together that enable logging (anything with an asterisk) gives 3013FFF.

			0x2000, and all options from 0x8000 onwards, do not exist in Mac OS 8.6. 0x1000 is labeled "Enable debugging output AFTER Open Firmware is gone." but it does not seem to do anything there.

	== NanoKernel Log sample ==		== NanoKernel Log sample ==

Huntertur: /* Notes */ Be more specific

2025-09-26T06:29:36Z

Notes: Be more specific

← Older revision		Revision as of 06:29, 26 September 2025
Line 176:		Line 176:
	* The NanoKernel Log suggests that it initializes itself once without on-disk virtual memory support then immediately re-initializes itself with it enabled.		* The NanoKernel Log suggests that it initializes itself once without on-disk virtual memory support then immediately re-initializes itself with it enabled.
	* It calls <code>CreateArea</code> for the 4096-byte page containing <code>deadbeef</code>, possibly so it is always a valid address? It shows up in [[PowerMacInfo]] for some preemptive tasks.		* It calls <code>CreateArea</code> for the 4096-byte page containing <code>deadbeef</code>, possibly so it is always a valid address? It shows up in [[PowerMacInfo]] for some preemptive tasks.
	* From the NanoKernel Log, VMMaxVirtualPages (0x0005fffe) * 4096 = 1,610,604,544 (1,536 MiB). Could this be the source of the max memory limit in the classic Mac OS?		* From the NanoKernel Log, VMMaxVirtualPages (0x0005fffe) * 4096 = 1,610,604,544 (1,536 MiB - 8 KiB). Could this be the source of the max memory limit in the classic Mac OS?

	[[Category:Guides]]		[[Category:Guides]]

Huntertur: /* Bitflags */ Reformat as table

2025-09-26T06:27:14Z

Bitflags: Reformat as table

@@ Line 19: / Line 19: @@
 == Bitflags ==
-From the beginning of the debugging output:
+From the beginning of the debugging output, but formatted as a proper table:
-AAPL,debug bit settings (-OR- bits together):
+|+ AAPL,debug bit settings (-OR- bits together):
-* = Print general informative messages.
+| style="text-align: right;" |        1 || * || = Print general informative messages.
-* = Dump Mac OS tables (except config/universal info).
+| style="text-align: right;" |        2 || * || = Print formatted Mac OS tables (except config/universal info).
-* = Print "special" node info.
+| style="text-align: right;" |       20 || * || = Print property info while copying the device tree.
 </pre>

Huntertur: Add note on VMMaxVirtualPages

2025-09-26T06:20:59Z

Add note on VMMaxVirtualPages

← Older revision		Revision as of 06:20, 26 September 2025
Line 151:		Line 151:
	== Notes ==		== Notes ==
	* This does not work on a tray-loading iMac G3 because <code>/packages/telnet</code> does not exist.		* This does not work on a tray-loading iMac G3 because <code>/packages/telnet</code> does not exist.
	* The NanoKernel Log suggests that it initializes itself once without virtual memory then immediately re-initializes itself with ~~virtual~~ ~~memory~~.		* The NanoKernel Log suggests that it initializes itself once without on-disk virtual memory support then immediately re-initializes itself with it enabled.
	* It calls <code>CreateArea</code> for the 4096-byte page containing <code>deadbeef</code>, possibly so it is always a valid address? It shows up in [[PowerMacInfo]] for some preemptive tasks.		* It calls <code>CreateArea</code> for the 4096-byte page containing <code>deadbeef</code>, possibly so it is always a valid address? It shows up in [[PowerMacInfo]] for some preemptive tasks.
			* From the NanoKernel Log, VMMaxVirtualPages (0x0005fffe) * 4096 = 1,610,604,544 (1,536 MiB). Could this be the source of the max memory limit in the classic Mac OS?

	[[Category:Guides]]		[[Category:Guides]]

Huntertur: Add NanoKernel Log

2025-09-26T06:12:04Z

Add NanoKernel Log

@@ Line 47: / Line 47: @@
 Adding all the bitflags together that enable logging (anything with an asterisk) gives 3013FFF.
 == Notes ==
 * This does not work on a tray-loading iMac G3 because <code>/packages/telnet</code> does not exist.
 [[Category:Guides]]

Huntertur: Move log phases out of Notes section

2025-09-26T05:40:35Z

Move log phases out of Notes section

← Older revision		Revision as of 05:40, 26 September 2025
Line 13:		Line 13:
	# Run <code>dev / 3013FFF encode-int " AAPL,debug" property</code>, substituting the hexadecimal number as necessary.		# Run <code>dev / 3013FFF encode-int " AAPL,debug" property</code>, substituting the hexadecimal number as necessary.
	# Run <code>mac-boot</code>.		# Run <code>mac-boot</code>.

		⚫	Telnet output will end before the Happy Mac even appears. When this happens, the following is printed to the screen: <code>Off to MacOS. The next (and last) call into OpenFirmware is quiesce().</code>

		⚫	After telnet output ends, a separate NanoKernel Log will appear on screen, get covered by the Welcome to Mac OS dialog, then appear a second time before disappearing entirely with the "Starting up..." text.

	== Bitflags ==		== Bitflags ==
Line 46:		Line 50:
	== Notes ==		== Notes ==
	* This does not work on a tray-loading iMac G3 because <code>/packages/telnet</code> does not exist.		* This does not work on a tray-loading iMac G3 because <code>/packages/telnet</code> does not exist.
	* Telnet output starts about two seconds after the screen turns gray. Output then ends, before the Happy Mac even appears.
⚫	** When this happens, the following is printed to the screen: <code>Off to MacOS. The next (and last) call into OpenFirmware is quiesce().</code>
⚫	* After telnet output ends, a separate NanoKernel Log will appear on screen, get covered by the Welcome to Mac OS dialog, then appear a second time before disappearing entirely with the "Starting up..." text.

	[[Category:Guides]]		[[Category:Guides]]

Huntertur: Rewrite instructions

2025-09-26T05:35:48Z

Rewrite instructions

← Older revision		Revision as of 05:35, 26 September 2025
Line 1:		Line 1:
	You can make the Classic Mac OS dump a bunch of debugging output ~~to Open Firmware~~ during ~~boot and sometimes the screen after~~ boot.		You can make the Classic Mac OS dump a bunch of debugging output during boot.

			== Instructions ==
	To do this, open Open Firmware during boot with Command-Option-O-F and enter <code>dev / 3013FFF encode-int " AAPL,debug" property</code>. Then, boot with <code>mac-boot</code>.

			# Boot into Open Firmware (Command-Option-O-F).
	If you want a log of this output, you should hook your machine up to the local network, then run this, replacing the IP address with whatever is available for the machine to use:
			# Since log output is massive, consider logging over the network instead of to the screen:

	dev /packages/telnet		## Run <code>dev /packages/telnet</code>.
	" enet:telnet,192.168.18.10" io		## Run <code>" enet:telnet,192.168.18.10" io</code>, substituting the IP address as necessary.
			##* On-screen text input and output will end.

			## On another computer, telnet into that IP address.
	Then connect to your machine via Telnet before booting.
			##* The screen will blank itself until booting begins.
			# Use the [[#Bitflags]] table to choose a debugging configuration.
			# Run <code>dev / 3013FFF encode-int " AAPL,debug" property</code>, substituting the hexadecimal number as necessary.
			# Run <code>mac-boot</code>.

	== Bitflags ==		== Bitflags ==
Line 42:		Line 46:
	== Notes ==		== Notes ==
	* This does not work on a tray-loading iMac G3 because <code>/packages/telnet</code> does not exist.		* This does not work on a tray-loading iMac G3 because <code>/packages/telnet</code> does not exist.
	* The screen will become blank after connecting from the client machine. The screen will come back to life once booting begins.
	* Telnet output starts about two seconds after the screen turns gray. Output then ends, before the Happy Mac even appears.		* Telnet output starts about two seconds after the screen turns gray. Output then ends, before the Happy Mac even appears.
	** When this happens, the following is printed to the screen: <code>Off to MacOS. The next (and last) call into OpenFirmware is quiesce().</code>		** When this happens, the following is printed to the screen: <code>Off to MacOS. The next (and last) call into OpenFirmware is quiesce().</code>

Huntertur: /* Notes */ Note the "Off to MacOS." message

2025-09-26T05:27:45Z

Notes: Note the "Off to MacOS." message

← Older revision		Revision as of 05:27, 26 September 2025
Line 44:		Line 44:
	* The screen will become blank after connecting from the client machine. The screen will come back to life once booting begins.		* The screen will become blank after connecting from the client machine. The screen will come back to life once booting begins.
	* Telnet output starts about two seconds after the screen turns gray. Output then ends, before the Happy Mac even appears.		* Telnet output starts about two seconds after the screen turns gray. Output then ends, before the Happy Mac even appears.
			** When this happens, the following is printed to the screen: <code>Off to MacOS. The next (and last) call into OpenFirmware is quiesce().</code>
	* After telnet output ends, a separate NanoKernel Log will appear on screen, get covered by the Welcome to Mac OS dialog, then appear a second time before disappearing entirely with the "Starting up..." text.		* After telnet output ends, a separate NanoKernel Log will appear on screen, get covered by the Welcome to Mac OS dialog, then appear a second time before disappearing entirely with the "Starting up..." text.

Huntertur: /* Notes */ Note NanoKernel Log

2025-09-26T04:57:05Z

Notes: Note NanoKernel Log

← Older revision		Revision as of 04:57, 26 September 2025
Line 43:		Line 43:
	* This does not work on a tray-loading iMac G3 because <code>/packages/telnet</code> does not exist.		* This does not work on a tray-loading iMac G3 because <code>/packages/telnet</code> does not exist.
	* The screen will become blank after connecting from the client machine. The screen will come back to life once booting begins.		* The screen will become blank after connecting from the client machine. The screen will come back to life once booting begins.
			* Telnet output starts about two seconds after the screen turns gray. Output then ends, before the Happy Mac even appears.
	*
			* After telnet output ends, a separate NanoKernel Log will appear on screen, get covered by the Welcome to Mac OS dialog, then appear a second time before disappearing entirely with the "Starting up..." text.

	[[Category:Guides]]		[[Category:Guides]]

Huntertur: /* Bitflags */ Explain 3103FFF

2025-09-26T04:51:55Z

Bitflags: Explain 3103FFF

← Older revision		Revision as of 04:51, 26 September 2025
Line 37:		Line 37:
	40000000 = Halt after end of FCode (useful if outputting to screen).		40000000 = Halt after end of FCode (useful if outputting to screen).
	</pre>		</pre>

			Adding all the bitflags together that enable logging (anything with an asterisk) gives 3013FFF.

	== Notes ==		== Notes ==