AmigaOne X1000 - Revision history

Steven Solie at 18:58, 2 October 2015

2015-10-02T18:58:15Z

← Older revision		Revision as of 18:58, 2 October 2015
Line 99:		Line 99:
	** ISO for CDs		** ISO for CDs
	** FFS2, ext2 or FAT for hard disks or CompactFlash		** FFS2, ext2 or FAT for hard disks or CompactFlash
	* CFE can't detect ~~filesystems~~, they must be specified in the boot command		* CFE can't detect file systems, they must be specified in the boot command
	** for a CD: ''-fs=isofs''		** for a CD: ''-fs=isofs''
	** for an AmigaOS FFS partition: ''-fs=amigafs''		** for an AmigaOS FFS partition: ''-fs=amigafs''
Line 106:		Line 106:
	The boot menu is configured through a set of MENU_x_LABEL/MENU_x_COMMAND pairs. If one of the entry doesn't work, you have to check that:		The boot menu is configured through a set of MENU_x_LABEL/MENU_x_COMMAND pairs. If one of the entry doesn't work, you have to check that:
	* the unit exists,		* the unit exists,
	* the ~~filesystem~~ is correct,		* the file system is correct,
	* the amigaboot.of file is present.		* the amigaboot.of file is present.

Line 136:		Line 136:
	Either you modify the menu commands, or you swap the cables on the Sata connectors 0 and 2.		Either you modify the menu commands, or you swap the cables on the Sata connectors 0 and 2.

	==== checking ~~filesystem~~ ====		==== checking file system ====
	Once your units are correctly identified, you should check the ~~filesystem~~ is correct with the ''dir'' command.		Once your units are correctly identified, you should check the file system is correct with the ''dir'' command.
	Note that the error message may be different depending on the type of unit and the ~~filesystem~~. Just keep in mind that if the command status is 0, the ~~filesystem~~ is correct.		Note that the error message may be different depending on the type of unit and the file system. Just keep in mind that if the command status is 0, the file system is correct.
	* trying to read an SFS/02 partition:		* trying to read an SFS/02 partition:
	CFE> dir -fs=amigafs ide0.1,prod:		CFE> dir -fs=amigafs ide0.1,prod:

Steven Solie: /* X1000 boots to black screen with RadeonHD 2.7 driver */

2015-09-18T15:19:04Z

X1000 boots to black screen with RadeonHD 2.7 driver

← Older revision		Revision as of 15:19, 18 September 2015
Line 174:		Line 174:
	== X1000 boots to black screen with RadeonHD 2.7 driver ==		== X1000 boots to black screen with RadeonHD 2.7 driver ==

	Several users have reported the XFX Radeon R9 270X card is not compatible with the RadeonHD 2.7 driver.		Several users have reported the XFX Radeon R9 270X card is not compatible with the RadeonHD 2.7 driver. Another user reported the MSI Radeon R9 270X card is also not compatible. It is probably best to avoid the "270X" cards entirely.

	== X1000 Keyboard does not work while booting==		== X1000 Keyboard does not work while booting==

Steven Solie: /* X1000 won't boot (black screen, no boot at all) with only 3 LEDs lighting on motherboard */

2015-09-18T15:17:24Z

X1000 won't boot (black screen, no boot at all) with only 3 LEDs lighting on motherboard

← Older revision		Revision as of 15:17, 18 September 2015
Line 168:		Line 168:


	==X1000 won't boot (black screen, no boot at all) with only 3 LEDs lighting on motherboard==		== X1000 won't boot (black screen, no boot at all) with only 3 LEDs lighting on motherboard ==

	Check the CMOS battery.		Check the CMOS battery.

			== X1000 boots to black screen with RadeonHD 2.7 driver ==

			Several users have reported the XFX Radeon R9 270X card is not compatible with the RadeonHD 2.7 driver.

	== X1000 Keyboard does not work while booting==		== X1000 Keyboard does not work while booting==

Ölrick Lefebvre: Added link to the firmware update page

2015-04-08T11:49:48Z

Added link to the firmware update page

← Older revision		Revision as of 11:49, 8 April 2015
Line 226:		Line 226:
	Kickstart will load from the highest priority bootable partition on THE FIRST DRIVE ONLY.		Kickstart will load from the highest priority bootable partition on THE FIRST DRIVE ONLY.
	If your highest priority bootable drive is on a second SATA disk, then that will boot over the kickstart found on Disk1.		If your highest priority bootable drive is on a second SATA disk, then that will boot over the kickstart found on Disk1.

			= Updating Nemo's Firmware =

			Warning, this procedure is not harmless and should only be done when you know exactly what you are doing.<br>
			[[Updating Nemo firmware]]


	= AmigaOS 4.1 Final Edition FAQ =		= AmigaOS 4.1 Final Edition FAQ =

Steven Solie at 04:29, 11 November 2014

2014-11-11T04:29:15Z

← Older revision		Revision as of 04:29, 11 November 2014
Line 226:		Line 226:
	Kickstart will load from the highest priority bootable partition on THE FIRST DRIVE ONLY.		Kickstart will load from the highest priority bootable partition on THE FIRST DRIVE ONLY.
	If your highest priority bootable drive is on a second SATA disk, then that will boot over the kickstart found on Disk1.		If your highest priority bootable drive is on a second SATA disk, then that will boot over the kickstart found on Disk1.

			= AmigaOS 4.1 Final Edition FAQ =

			Insert documentation here...

Steven Solie at 03:21, 11 October 2014

2014-10-11T03:21:06Z

← Older revision		Revision as of 03:21, 11 October 2014
Line 42:		Line 42:

	Please remember to refer to CFE's documentation located in SYS:Documentation/X1000_CFE.pdf for information on boot configuration.		Please remember to refer to CFE's documentation located in SYS:Documentation/X1000_CFE.pdf for information on boot configuration.

			== Where does Kickstart load from? ==

			As soon as the "amigaboot.of" loader begins, it scans all the available AmigaOS partitions it can find. Specifically, the SATA CD-ROM and SATA drive connected to Port1, SATA2 and IDE devices are scanned for partitions which are set as AmigaOS bootable, using the FFS2 or SFS file systems and containing an AmigaOS system. Kickstart from the partition with the highest priority is then loaded. After Kickstart is loaded, ALL drives will be scanned again and Workbench from the highest priority bootable drive will load. If your highest priority bootable drive is not connected to Port1, SATA2 then a kickstart from another drive will be loaded.

			So, if you add another drive with bootable partitions, you may need to swap SATA cables to get the kickstart to load from the right place.

	== X1000 Won't Reboot Reliably ==		== X1000 Won't Reboot Reliably ==

Lyle Hazelwood: /* Troubleshooting Tips */

2014-09-04T02:33:43Z

Troubleshooting Tips

← Older revision		Revision as of 02:33, 4 September 2014
Line 215:		Line 215:

	Check all PCI(e) cards are securely in their slots.		Check all PCI(e) cards are securely in their slots.

			==Problems updating your Kickstart==

			Kickstart will load from the highest priority bootable partition on THE FIRST DRIVE ONLY.
			If your highest priority bootable drive is on a second SATA disk, then that will boot over the kickstart found on Disk1.

Steven Solie: /* Frequently Asked Questions */

2014-07-25T20:49:10Z

Frequently Asked Questions

← Older revision		Revision as of 20:49, 25 July 2014
Line 36:		Line 36:

	[http://www.amigakit.com AmigaKit] is the worldwide distributor of the AmigaOne X1000 System.		[http://www.amigakit.com AmigaKit] is the worldwide distributor of the AmigaOne X1000 System.

	= Frequently Asked Questions =

	== When will Mixer be upgraded to support the X1000? ==

	The X1000's HDAudio chip does not support monitoring. As such, the Mixer will never work on the X1000 since the hardware does not exist.

	A software only solution may be possible to allow for monitoring but that will use up system resources and may or may not work with Mixer.

	= Troubleshooting Tips =		= Troubleshooting Tips =

Nick Clover at 15:42, 18 May 2014

2014-05-18T15:42:31Z

← Older revision		Revision as of 15:42, 18 May 2014
Line 67:		Line 67:

	I had this problem for a few months and finally tracked it down to loose SATA power connectors.		I had this problem for a few months and finally tracked it down to loose SATA power connectors.

	I had a PSU Modding kit and made a new power lead, MOLEX to 4 SATA, all on the same lead, spaced to fit 4 drives perfectly with no bent wires.		I had a PSU Modding kit and made a new power lead, MOLEX to 4 SATA, all on the same lead, spaced to fit 4 drives perfectly with no bent wires.

	The new connectors are a much tighter fit and since I changed the lead I've not had a single random lockup and reliable booting.		The new connectors are a much tighter fit and since I changed the lead I've not had a single random lockup and reliable booting.

	If you get the insufficient memory error in CFE this is a sign the DVD cable is loose.		If you get the insufficient memory error in CFE this is a sign the DVD cable is loose.

Nick Clover: added X1000 locks up randomly and doesn't boot reliably section

2014-05-18T15:40:36Z

added X1000 locks up randomly and doesn't boot reliably section

← Older revision		Revision as of 15:40, 18 May 2014
Line 63:		Line 63:

	If the X1000 boots up to Workbench, press and hold the power button for 3-5 seconds & it should shut off.		If the X1000 boots up to Workbench, press and hold the power button for 3-5 seconds & it should shut off.

			==X1000 locks up randomly and doesn't boot reliably==

			I had this problem for a few months and finally tracked it down to loose SATA power connectors.
			I had a PSU Modding kit and made a new power lead, MOLEX to 4 SATA, all on the same lead, spaced to fit 4 drives perfectly with no bent wires.
			The new connectors are a much tighter fit and since I changed the lead I've not had a single random lockup and reliable booting.
			If you get the insufficient memory error in CFE this is a sign the DVD cable is loose.

	==X1000 CPU temperatures are rising==		==X1000 CPU temperatures are rising==