Archive:Chromebox - Revision history

Bam80: Note bootloop when powering via USB-C PD

2022-03-08T22:48:41Z

Note bootloop when powering via USB-C PD

← Older revision		Revision as of 22:48, 8 March 2022
Line 227:		Line 227:

	'''Important:''' The write-protect screw should be left out permanently.		'''Important:''' The write-protect screw should be left out permanently.
			<br />
			Note without the screw there was [https://github.com/MrChromebox/scripts/issues/185#issuecomment-1059306791 a case registered] with bootloop when powering from USB-C Power Delivery. Your mileage may vary.
	<br />		<br />
	<br />		<br />

Matt Devo: /* Broadwell */

2021-09-26T18:42:44Z

Broadwell

← Older revision		Revision as of 18:42, 26 September 2021
Line 106:		Line 106:
	\|-		\|-
	\| CPU/GPU		\| CPU/GPU
	\| style="text-align: center;" \| Celeron 3205U (HD Graphics / GT1)<br /> Core i3-5005U (HD Graphics 5500 / GT2)		\| style="text-align: center;" \| Celeron 3205U (HD Graphics / GT1)<br /> Core i3-5005U, Core i7-5500U (HD Graphics 5500 / GT2)
	\| style="text-align: center;" \| Celeron 3205U (HD Graphics / GT1)<br /> Core i3-5005U, Core i7-5500U (HD Graphics 5500 / GT2)		\| style="text-align: center;" \| Celeron 3205U (HD Graphics / GT1)<br /> Core i3-5005U, Core i7-5500U (HD Graphics 5500 / GT2)
	\| style="text-align: center;" \| Celeron 3205U (HD Graphics / GT1)<br /> Core i3-5005U (HD Graphics 5500 / GT2)		\| style="text-align: center;" \| Celeron 3205U (HD Graphics / GT1)<br /> Core i3-5005U (HD Graphics 5500 / GT2)
Line 143:		Line 143:

	All Broadwell model Chromeboxes are fully supported by the ChromeBox Kodi E-Z Setup Script.		All Broadwell model Chromeboxes are fully supported by the ChromeBox Kodi E-Z Setup Script.


	==== Kabylake ====		==== Kabylake ====

Karellen: Text replacement - "{{Updated|16}}" to ""

2020-11-14T07:27:33Z

Text replacement - "{{Updated|16}}" to ""

← Older revision		Revision as of 07:27, 14 November 2020
Line 595:		Line 595:
	* [https://www.google.com/work/chrome/ Google's "Chrome for Work" web page]		* [https://www.google.com/work/chrome/ Google's "Chrome for Work" web page]

	~~{{Updated\|16}}~~

	[[Category:Hardware-Archived]]		[[Category:Hardware-Archived]]

Karellen: Karellen moved page Chromebox to Archive:Chromebox without leaving a redirect: Outdated Hardware

2020-08-04T05:28:33Z

Karellen moved page Chromebox to Archive:Chromebox without leaving a redirect: Outdated Hardware

← Older revision	Revision as of 05:28, 4 August 2020
(No difference)

Karellen at 05:28, 4 August 2020

2020-08-04T05:28:12Z

← Older revision		Revision as of 05:28, 4 August 2020
Line 1:		Line 1:
	~~{{mininav\|[[Devices]]\|[[x86 hardware]]}}~~
	{{device notice}}		{{device notice}}

Line 373:		Line 372:
	If you have an LibreELEC dual boot setup and are switching to an LibreELEC standalone setup, then you can backup your settings etc using the built-in tools, copy to another PC/USB, and then restore after performing the standalone setup.		If you have an LibreELEC dual boot setup and are switching to an LibreELEC standalone setup, then you can backup your settings etc using the built-in tools, copy to another PC/USB, and then restore after performing the standalone setup.

	If you have a standalone setup and wish to switch to a dual boot setup, you need to first ~~[[Chromebox#Resetting_to_Stock\|~~restore the stock firmware]], then ~~[[Chromebox#Perform_a_Factory_Reset\|~~perform a factory reset]], after which you can continue with the dual boot setup.		If you have a standalone setup and wish to switch to a dual boot setup, you need to first restore the stock firmware, then perform a factory reset, after which you can continue with the dual boot setup.
	<br />		<br />
	<br />		<br />
Line 416:		Line 415:
	:* Measy RC11 Android Monitor Wireless Keyboard Air Mouse Remote Controller With Gyroscope (cannot wake up Chromebox but works otherwise nicely, with keys as well as with mouse pointer at both OpenELEC and ChromeOS)		:* Measy RC11 Android Monitor Wireless Keyboard Air Mouse Remote Controller With Gyroscope (cannot wake up Chromebox but works otherwise nicely, with keys as well as with mouse pointer at both OpenELEC and ChromeOS)
	:* Amazon FireTV / Fire Stick remotes (Bluetooth)		:* Amazon FireTV / Fire Stick remotes (Bluetooth)
	:NOTE: If you need to re-map remote buttons, you can use the ~~[[Add-on:Keymap Editor\|~~Keymap Editor Add-on]] to do so.		:NOTE: If you need to re-map remote buttons, you can use the Keymap Editor Add-on to do so.

	:'''Currently non-working''':		:'''Currently non-working''':
Line 443:		Line 442:
	:* Help! I'm stuck on the black SeaBIOS boot screen, with the "booting from hard disk" text displayed (and possibly a bunch of nonsensical text afterwards).		:* Help! I'm stuck on the black SeaBIOS boot screen, with the "booting from hard disk" text displayed (and possibly a bunch of nonsensical text afterwards).
	:*:This happens because SeaBIOS is trying to boot from the internal hard drive, but no bootable OS (or only ChromeOS) is installed.		:*:This happens because SeaBIOS is trying to boot from the internal hard drive, but no bootable OS (or only ChromeOS) is installed.
	::* If you have a dual boot setup, 99% of the time this is due to not having performed a factory reset prior to running the EZ Setup Script, ~~[[Chromebox#Perform_a_Factory_Reset\|~~as listed in the Device Prep section above]]. Simply perform the factory reset, then redo the dual boot setup using the script as before.		::* If you have a dual boot setup, 99% of the time this is due to not having performed a factory reset prior to running the EZ Setup Script, as listed in the Device Prep section above. Simply perform the factory reset, then redo the dual boot setup using the script as before.
	::* If you have a standalone setup, and are trying to boot from USB:		::* If you have a standalone setup, and are trying to boot from USB:
	::*: If you see the 'Press ESC for boot menu' text but pressing it doesn't work, then the issue is your keyboard, so try using a different one.		::*: If you see the 'Press ESC for boot menu' text but pressing it doesn't work, then the issue is your keyboard, so try using a different one.
Line 570:		Line 569:
	== Resetting to Stock ==		== Resetting to Stock ==

	If you have a dual boot setup, simply ~~[[Chromebox#Perform_a_Factory_Reset\|~~perform a factory reset]], then hit [space] on the developer mode boot screen to revert to verified boot mode. Done. (Note: be sure to use the Kodi EZ Setup Script to reset the boot options to default before doing this, or you may not be able to exit developer mode)		If you have a dual boot setup, simply perform a factory reset, then hit [space] on the developer mode boot screen to revert to verified boot mode. Done. (Note: be sure to use the Kodi EZ Setup Script to reset the boot options to default before doing this, or you may not be able to exit developer mode)
	<br />		<br />
	<br />		<br />
Line 587:		Line 586:
	*: If not, select your ChromeBox model so the appropriate firmware can be downloaded		*: If not, select your ChromeBox model so the appropriate firmware can be downloaded
	<br />		<br />
	After restoring the stock firmware, reboot, and proceed to ~~[[Chromebox#~~Perform_a_Factory_Reset~~\|Perform_a_Factory_Reset]]~~ above to restore/reload ChromeOS.		After restoring the stock firmware, reboot, and proceed to Perform_a_Factory_Reset above to restore/reload ChromeOS.
	<br />		<br />
	<br />		<br />
Line 598:		Line 597:
	{{Updated\|16}}		{{Updated\|16}}

	[[Category:Hardware]]		[[Category:Hardware-Archived]]

Karellen at 21:44, 19 July 2020

2020-07-19T21:44:29Z

← Older revision		Revision as of 21:44, 19 July 2020
Line 599:		Line 599:

	[[Category:Hardware]]		[[Category:Hardware]]
	~~[[Category:x86]]~~
	~~[[Category:Hardware]]~~
	~~[[Category:Linux]]~~

Karellen at 07:11, 10 July 2020

2020-07-10T07:11:40Z

← Older revision		Revision as of 07:11, 10 July 2020
Line 599:		Line 599:

	[[Category:Hardware]]		[[Category:Hardware]]
	~~[[Category:HTPC]]~~
	[[Category:x86]]		[[Category:x86]]
	[[Category:Hardware]]		[[Category:Hardware]]
	[[Category:Linux]]		[[Category:Linux]]

Karellen at 02:06, 8 July 2020

2020-07-08T02:06:48Z

← Older revision		Revision as of 02:06, 8 July 2020
Line 587:		Line 587:
	*: If not, select your ChromeBox model so the appropriate firmware can be downloaded		*: If not, select your ChromeBox model so the appropriate firmware can be downloaded
	<br />		<br />
	After restoring the stock firmware, reboot, and proceed to [[~~ASUS_Chromebox~~#Perform_a_Factory_Reset\|Perform_a_Factory_Reset]] above to restore/reload ChromeOS.		After restoring the stock firmware, reboot, and proceed to [[Chromebox#Perform_a_Factory_Reset\|Perform_a_Factory_Reset]] above to restore/reload ChromeOS.
	<br />		<br />
	<br />		<br />

Matt Devo: /* Generations and Models */

2019-05-11T19:15:18Z

Generations and Models

← Older revision		Revision as of 19:15, 11 May 2019
Line 144:		Line 144:

	All Broadwell model Chromeboxes are fully supported by the ChromeBox Kodi E-Z Setup Script.		All Broadwell model Chromeboxes are fully supported by the ChromeBox Kodi E-Z Setup Script.


			==== Kabylake ====

			Kabylake Chromeboxes were released in the Spring of 2018, and feature a few notable improvements over the previous Haswell/Broadwell models (which are effectively identical). The Kabylake SoC provides a nice speed bump, but more importantly the GPU features full 10-bit HEVC/VP9 decoding, as well as 4Kp60 output (via USB-C DisplayPort alt-mode).

			Unfortunately, the GPU in the Kabylake SoC still doesn't natively support HDMI 2.0 output. This means that 4Kp60 output still requires the use of a DisplayPort to HDMI 2.0 adapter (via the USB-C port), and thus a LSPCON (level shifter/protocol converter). The use of a LSPCON means that HD audio bitstreaming almost certainly won't work (due to driver limitations), so one must choose between using the HDMI 1.4 output with HD audio, or the USB-C output with 4K output.

			Also, although the Kabylake SoC is HDR capable, Intel has not implemented HDR capability under Linux. Because of this and the above factors, it's hard to recommend a Kabylake Chromebox at this time, unless you simply want a faster, HEVC/VP9 capable device and the aforementioned limitations do not bother you. Even still, there likely better options available at a lower price point.

			{\| class="prettytable"
			\|-
			\| width="100" \| Make / Model
			\| width="250" align="center" \| [https://www.asus.com/us/Chrome-Devices/ASUS-Chromebox-3/ Asus Chromebox 3 / CN65]
			\| width="250" align="center" \| [https://www.acer.com/ac/en/US/content/professional-series/acerchromeboxcxi3 Acer Chromebox CXI3]
			\| width="250" align="center" \| [https://www8.hp.com/us/en/desktops/product-details/10273058 HP Chromebox G2]
			\| width="250" align="center" \| [https://ctl.net/products/ctl-chromebox CTL Chromebox CBx1]
			\|-
			\| SoC/GPU
			\| colspan="4" style="text-align: center;" \| Kabylake-U / HD610 (Celeron, i3/i5-7xxx)<br />Kabylake-R / UHD620 (i5/i7-8xxx)
			\|-
			\| CPU
			\| width="250" align="center" \| Celeron 3865U, Core i3-7100U, Core i5-8250U, Core i7-8550U
			\| width="250" align="center" \| Celeron 3865U, Core i3-7130U, Core i5-8250U, Core i7-8550U
			\| width="250" align="center" \| Celeron 3865U, Core i5-7300U, Core i7-8560U
			\| width="250" align="center" \| Celeron 3865U, Core i7-8550U
			\|-
			\| RAM
			\| colspan="4" style="text-align: center;" \| Dual-channel DDR4 2133, 2x SODIMMs, 32GB max.
			\|-
			\| Display Outputs
			\| colspan="4" style="text-align: center;" \| 1x [http://en.wikipedia.org/wiki/HDMI#Version_1.4 HDMI 1.4a] <br />1x [https://www.displayport.org/displayport-over-usb-c/ USB-C]
			\|-
			\| width="100" \| Internal storage
			\| colspan="4" style="text-align: center;" \| m.2 SATA SSD, 42mm (2242); 80mm drives can be used as well <br /> Core-i models support NVMe drives (PCIe x4)
			\|-
			\| Ethernet
			\| colspan="4" style="text-align: center;" \| 1x Realtek RT8169, RJ45, 10/100/1000 Mbps
			\|-
			\| WiFi / BT
			\| colspan="4" style="text-align: center;" \| Intel 7265 802.11 ac + BT 4.0
			\|-
			\| Audio
			\| colspan="4" style="text-align: center;" \| 7.1 digital audio (bitstream or PCM) via [http://en.wikipedia.org/wiki/HDMI#Version_1.4 HDMI] and [http://en.wikipedia.org/wiki/DisplayPort DisplayPort]<br />Front-panel 3.5mm headset jack (not functional under Linux currently due to driver issues)
			\|-
			\| USB Ports
			\| colspan="4" style="text-align: center;" \| USB 3.0: 3x rear, 2x front<br />USB 3.1 Gen 1 Type-C: 1x rear
			\|-
			\| Card Reader
			\| colspan="4" style="text-align: center;" \| Front internal micro-SD card slot
			\|-
			\| Model Notes
			\| colspan="4" style="text-align: center;" \|
			\|}

			All Kabylake model Chromeboxes are fully supported by the ChromeBox Kodi E-Z Setup Script. Currently, Legacy Boot Mode is broken in Google's stock firmware, so dual booting is not functional at this time.

	== Device Preparation ==		== Device Preparation ==

Matt Devo: /* Troubleshooting, Known Issues, Fixes/Workarounds */

2019-05-11T18:15:20Z

Troubleshooting, Known Issues, Fixes/Workarounds

← Older revision		Revision as of 18:15, 11 May 2019
Line 462:		Line 462:
	:* the snd_soc_skl audio driver is breaking things, so we need to blacklist it. Open up the 'configfiles' network share on your Chromebox, then the modprobe.d folder. If it doesn't already exist, create a new text file blacklist.conf and add the line 'blacklist snd_soc_skl' to it. Save and reboot the Chromebox.		:* the snd_soc_skl audio driver is breaking things, so we need to blacklist it. Open up the 'configfiles' network share on your Chromebox, then the modprobe.d folder. If it doesn't already exist, create a new text file blacklist.conf and add the line 'blacklist snd_soc_skl' to it. Save and reboot the Chromebox.

	Slow Ethernet performance with LibreELEC 9.x (or kernel 4.19+):		Slow Ethernet performance with LibreELEC 9.0/9.01 (or kernel 4.19+):
	:* A regression was introduced in kernel 4.19 which severely cripples the Ethernet throughput on Haswell/Broadwell/Kabylake Chromeboxes (this only affects the built-in Ethernet, and not wifi nor USB to Ethernet adapters). This issue can be mitigated by the addition of the kernel command-line parameter 'pcie_aspm.policy=performance'.		: Note: this issue is fixed in LibreELEC 9.0.2/kernel 4.19.36
			:* A regression was introduced in kernel 4.19 which severely cripples the Realtek rt8169 Ethernet throughput on Haswell/Broadwell/Kabylake Chromeboxes (this only affects the built-in rt8169 Ethernet, and not wifi nor USB to Ethernet adapters). This issue can be mitigated by the addition of the kernel command-line parameter 'pcie_aspm.policy=performance'.
	:: On LibreELEC setups:		:: On LibreELEC setups:
	:::<nowiki>ssh root@<ip address></nowiki><br />		:::<nowiki>ssh root@<ip address></nowiki><br />