Support/BayTrail - Revision history

Matt Devo at 05:17, 2 March 2017

2017-03-02T05:17:56Z

Matt Devo at 07:19, 10 March 2016

2016-03-10T07:19:26Z

Reynhout at 17:46, 6 March 2016

2016-03-06T17:46:03Z

Reynhout at 17:37, 9 February 2016

2016-02-09T17:37:44Z

Reynhout: /* GalliumOS Known Issues */

2016-02-01T20:31:12Z

‎GalliumOS Known Issues

Reynhout at 02:24, 23 December 2015

2015-12-23T02:24:33Z

Reynhout: Created page with "== WIP! == === GalliumOS Support on Intel Bay Trail Models === Bay Trail models are less well-tested than Haswell and Broadwell, but everything should largely work, with a f..."

2015-12-16T20:36:37Z

Created page with "== WIP! == === GalliumOS Support on Intel Bay Trail Models === Bay Trail models are less well-tested than Haswell and Broadwell, but everything should largely work, with a f..."

New page

== WIP! ==

=== GalliumOS Support on Intel Bay Trail Models ===

Bay Trail models are less well-tested than Haswell and Broadwell, but everything should largely work, with a few known exceptions:

# '''Audio'''
#* GalliumOS BETA1 has known problems with audio on Bay Trail. This will be fixed in BETA2

==== Device-specific Details ====

(none)

← Older revision		Revision as of 05:17, 2 March 2017
Line 1:		Line 1:
	Intel processors using the BayTrail architecture are very popular in 2014/2015-era ChromeOS devices.		Intel processors using the BayTrail architecture are very popular in 2014/2015-era ChromeOS devices.

−	Factory firmware support for booting legacy OSes via SeaBIOS is nonexistent, but custom firmware is available for ~~most (~~all?) BayTrail models -- see [[Firmware]].	+	Factory firmware support for booting legacy OSes via SeaBIOS is nonexistent, but custom firmware is available for all BayTrail models -- see [[Firmware]].

← Older revision		Revision as of 07:19, 10 March 2016
Line 1:		Line 1:
−	Intel processors ~~with Bay Trail cores~~ are very popular in ~~newer~~ ChromeOS devices.	+	Intel processors using the BayTrail architecture are very popular in 2014/2015-era ChromeOS devices.

−	Factory firmware support for ~~coreboot and~~ SeaBIOS is nonexistent, but custom firmware is available for most or all ~~Bay Trail models from John Lewis: https://johnlewis.ie/custom-chromebook-firmware/rom-download/.~~	+	Factory firmware support for booting legacy OSes via SeaBIOS is nonexistent, but custom firmware is available for most (all?) BayTrail models -- see [[Firmware]].
−
−	~~There is only one firmware update option available:~~
−
−	~~# '''BOOT_STUB'''~~
−	~~#* Bypasses the white "OS verification is OFF" screen~~
−	~~#* Removes the ability to run ChromeOS natively, creating a small risk of bricking your device~~
−	~~#* Leaves the “REFRESH + POWER” functionality of the stock ROM intact~~
−	~~#** If you engage this key sequence, device will reboot and try to run ChromeOS Recovery (which will fail)~~
−	~~#** This process will repeat on every boot until you disassemble the device and briefly disconnect the battery~~
−
−	~~== Model-Specific Notes ==~~
−
−	~~=== Dell Chromebook 11 (3120), 2015 (CANDY~~) ~~===~~
−	* '''RW_LEGACY''' flash is possible (uniquely among Bay Trail models?)
−	** https://bugs.chromium.org/p/chromium/issues/detail?id=544236#c5
−	** firmware mirrored at https://galliumos.org/tmp/seabios-candy.cbfs
−	** untested, unverified, but presumed reliable
−	~~<pre style="margin:0 0 0 4em">~~
−	~~Comment 5 by vapier@chromium.org, Nov 13, 2015~~
−
−	~~please give this file a try. to use it:~~
−	~~- open crosh: ctrl+alt+t~~
−	~~- get a shell: shell~~
−	~~- switch to root: sudo su -~~
−	~~- get a writable dir: cd /tmp~~
−	~~- read the bios: flashrom -r bios.bin~~
−	~~- download seabios: wget~~ -~~O seabios.cbfs <url from this post>~~
−	- ~~merge the two: dd if=seabios.cbfs of=bios.bin seek=2 bs=2M conv=notrunc~~
−	~~- write to legacy: flashrom -w bios.bin -i RW_LEGACY~~
−
−	~~then reboot and~~ see ~~if CTRL+L works now. seems to for me on candy~~.
−	~~</pre>~~

← Older revision		Revision as of 17:46, 6 March 2016
Line 11:		Line 11:
	#** If you engage this key sequence, device will reboot and try to run ChromeOS Recovery (which will fail)		#** If you engage this key sequence, device will reboot and try to run ChromeOS Recovery (which will fail)
	#** This process will repeat on every boot until you disassemble the device and briefly disconnect the battery		#** This process will repeat on every boot until you disassemble the device and briefly disconnect the battery
		+
		+	== Model-Specific Notes ==
		+
		+	=== Dell Chromebook 11 (3120), 2015 (CANDY) ===
		+	* '''RW_LEGACY''' flash is possible (uniquely among Bay Trail models?)
		+	** https://bugs.chromium.org/p/chromium/issues/detail?id=544236#c5
		+	** firmware mirrored at https://galliumos.org/tmp/seabios-candy.cbfs
		+	** untested, unverified, but presumed reliable
		+	<pre style="margin:0 0 0 4em">
		+	Comment 5 by vapier@chromium.org, Nov 13, 2015
		+
		+	please give this file a try. to use it:
		+	- open crosh: ctrl+alt+t
		+	- get a shell: shell
		+	- switch to root: sudo su -
		+	- get a writable dir: cd /tmp
		+	- read the bios: flashrom -r bios.bin
		+	- download seabios: wget -O seabios.cbfs <url from this post>
		+	- merge the two: dd if=seabios.cbfs of=bios.bin seek=2 bs=2M conv=notrunc
		+	- write to legacy: flashrom -w bios.bin -i RW_LEGACY
		+
		+	then reboot and see if CTRL+L works now. seems to for me on candy.
		+	</pre>

← Older revision		Revision as of 17:37, 9 February 2016
Line 11:		Line 11:
	#** If you engage this key sequence, device will reboot and try to run ChromeOS Recovery (which will fail)		#** If you engage this key sequence, device will reboot and try to run ChromeOS Recovery (which will fail)
	#** This process will repeat on every boot until you disassemble the device and briefly disconnect the battery		#** This process will repeat on every boot until you disassemble the device and briefly disconnect the battery
−
−	~~=== GalliumOS Known Issues ===~~
−
−	GalliumOS BETA1 has known issues with internal audio, but this is fixed in nightly builds. You can update a BETA1 install via the usual <code>apt-get update ; apt-get dist-upgrade</code> method to pull in all bugfixes.

← Older revision		Revision as of 20:31, 1 February 2016
Line 14:		Line 14:
	=== GalliumOS Known Issues ===		=== GalliumOS Known Issues ===

−	GalliumOS BETA1 has known issues with internal audio, but this is fixed in nightly builds. You can update a BETA1 install via the usual <code>apt-get update ; apt-get upgrade</code> method to pull in all bugfixes.	+	GalliumOS BETA1 has known issues with internal audio, but this is fixed in nightly builds. You can update a BETA1 install via the usual <code>apt-get update ; apt-get dist-upgrade</code> method to pull in all bugfixes.

@@ Line 1: / Line 1: @@
-== WIP! ==
+Intel processors with Bay Trail cores are very popular in newer ChromeOS devices.
-=== GalliumOS Support on Intel Bay Trail Models ===
+Factory firmware support for coreboot and SeaBIOS is nonexistent, but custom firmware is available for most or all Bay Trail models from John Lewis: https://johnlewis.ie/custom-chromebook-firmware/rom-download/.
-Bay Trail models are less well-tested than Haswell and Broadwell, but everything should largely work, with a few known exceptions:
+There is only one firmware update option available:
-# '''Audio'''
+# '''BOOT_STUB'''
-#* GalliumOS BETA1 has known problems with audio on Bay Trail. This will be fixed in BETA2
+#* Bypasses the white "OS verification is OFF" screen
-==== Device-specific Details ====
+=== GalliumOS Known Issues ===
-(none)
+GalliumOS BETA1 has known issues with internal audio, but this is fixed in nightly builds. You can update a BETA1 install via the usual <code>apt-get update ; apt-get upgrade</code> method to pull in all bugfixes.