APM X-C1 (Mustang) - Revision history

Leo: Text replacement - "Category:Hardware" to "{{Navbox Hardware}}Category:Hardware"

2020-06-15T00:45:00Z

Text replacement - "Category:Hardware" to "{{Navbox Hardware}}Category:Hardware"

← Older revision		Revision as of 00:45, 15 June 2020
Line 698:		Line 698:

	{{Navbox Linux}}[[Category:Linux]]		{{Navbox Linux}}[[Category:Linux]]
	[[Category:Hardware]]		{{Navbox Hardware}}[[Category:Hardware]]

2019-09-01T06:17:26Z

Text replacement - "Category:Linux{{Navbox Linux}}" to "{{Navbox Linux}}Category:Linux"

2019-09-01T05:10:48Z

Text replacement - "{{Navbox Linux}}{{Navbox Linux}}" to "{{Navbox Linux}}"

← Older revision		Revision as of 05:10, 1 September 2019
Line 697:		Line 697:


	[[Category:Linux]]~~{{Navbox Linux}}~~{{Navbox Linux}}		[[Category:Linux]]{{Navbox Linux}}
	[[Category:Hardware]]		[[Category:Hardware]]

2019-09-01T05:09:22Z

Text replacement - "Category:Linux" to "Category:Linux{{Navbox Linux}}"

← Older revision		Revision as of 05:09, 1 September 2019
Line 697:		Line 697:


	[[Category:Linux]]{{Navbox Linux}}		[[Category:Linux]]{{Navbox Linux}}{{Navbox Linux}}
	[[Category:Hardware]]		[[Category:Hardware]]

2019-09-01T03:53:20Z

Text replacement - "Category:Linux " to "Category:Linux{{Navbox Linux}} "

2019-09-01T03:12:30Z

2017-07-17T22:49:05Z

2017-07-17T22:28:57Z

Installing Fedora: Hiding old content. Fedora installation is very simple now

← Older revision		Revision as of 22:28, 17 July 2017
Line 224:		Line 224:

	== Installing Fedora ==		== Installing Fedora ==
			Installing Fedora on the board is made very easy since Fedora 24. Simply download the boot.iso Fedora AARCH64 image and {{code\|dd}} it to a USB drive. You can then start the Fedora installer via the UEFI shell.

			For a netinstall or an automated install, edit the boot option in grub and pass in a {{code\|ks=}} value to the kernel.

			<!-- Old outdated content
	The steps outlined below should let you successfully install Fedora 21 and higher.		The steps outlined below should let you successfully install Fedora 21 and higher.

Line 280:		Line 285:

	=== Chain-Loading UEFI ===		=== Chain-Loading UEFI ===
	{{Warning\|There are issues ~~with~~ doing this!\|This method of chainloading UEFI from u-boot will cause the kernel to fail at starting up any additional CPUs probably because the device tree binary blob isn't provided.		{{Warning\|There are serious issues doing this!\|This method of chainloading UEFI from u-boot will cause the kernel to fail at starting up any additional CPUs probably because the device tree binary blob isn't provided.

	You should really just flash the box with APM's UEFI tianocore bios instead described in the next section.}}		You should really just flash the box with APM's UEFI tianocore bios instead described in the next section.}}
Line 327:		Line 332:
	cold reset ...▒		cold reset ...▒
	}}		}}

			-->


	=== Flashing Tianocore UEFI Bios ===		=== Flashing Tianocore UEFI Bios ===

2017-07-17T22:22:27Z

Troubleshooting

← Older revision		Revision as of 22:22, 17 July 2017
Line 508:		Line 508:
	== Troubleshooting ==		== Troubleshooting ==

	=== ~~Bad Flash~~ ===		=== Board Crashes on Startup ===
	When starting the ~~box~~ up, you get:		When starting the board up, you get:
	{{highlight\|lang=text\|code=X-Gene Mustang Board		{{highlight\|lang=text\|code=X-Gene Mustang Board
	Boot firmware (version 1.15.23 built at 13:21:52 on Nov 24 2015)		Boot firmware (version 1.15.23 built at 13:21:52 on Nov 24 2015)
Line 538:		Line 538:
	}}		}}

	~~Possibly~~ a ~~bad flash?~~		This is most likely a mismatch BIOS and Firmware. Try updating to the most recent Tianocore and Slimpro firmware. My temporary workaround to this issue was chainload an older BIOS version via the SD card.

	=== Grub Fails to Start Anaconda Installer ===		=== Grub Fails to Start Anaconda Installer ===

2017-07-17T22:20:08Z

← Older revision		Revision as of 22:20, 17 July 2017
Line 653:		Line 653:

	The kernel output is probably going to the wrong place. Set the {{code\|1=console=ttyS0,115200}} as part of the kernel arguments.		The kernel output is probably going to the wrong place. Set the {{code\|1=console=ttyS0,115200}} as part of the kernel arguments.

			=== Kickstart Storage Issue ===

			Anaconda bails during an automated install process with the error {{code\|failed to find a suitable stage1 device}} as seen during the install process:
			{{highlight\|lang=terminal\|code=
			Generating updated storage configuration
			storage configuration failed: failed to find a suitable stage1 device
			================================================================================

			================================================================================
			Installation

			1) [x] Language settings 2) [x] Time settings
			(English (United States)) (America/Edmonton timezone)
			3) [x] Installation source 4) [x] Software selection
			(http://linbuild.cs.ucalgary.ca (Custom software selected)
			/fedora/26/aarch64/os) 6) [x] Network configuration
			5) [!] Installation Destination (Wired (eth0) connected)
			(Error checking storage
			configuration)

			}}

			Since this system is using a UEFI BIOS, it needs to find a {{code\|/boot/efi}} partition containing the bootloader. The kickstart file did not contain a {{code\|/boot/efi}} partition (it only had a {{code\|/boot}}).

			Adding the partition made the automated install work again.


	[[Category:Linux]]		[[Category:Linux]]