2015-01-24, 05:40
(2015-01-23, 09:00)Matt Devo Wrote:(2015-01-23, 03:47)VanillaXtract Wrote: I got a new Chromebook. I ran through your script, same issue. No HDMI out. Restored the original firmware. Ran your script but did ^c when it started checking for a new bios. Now I have HDMI out. My question is that is the original bios fine to stick with? Where does your script get the files from? Should I keep trying new ones and working backwords until I find one that works?
ok, then stick with that - I make no promises that any of this will work with the Haswell ChromeBooks, especially not the firmware (which I guarantee 100% will brick them). If the stock legacy BIOS on your ChromeBook is functional (unlike with the Asus/HP ChromeBoxes) then there's no reason to update it.
the firmware files use by my script (both the full coreboot firmware and SeaBIOS payload for the stock firmware) are built by me, and optimized/tested only on the Haswell ChromeBoxes; the Haswell ChromeBooks are different because they have an onboard display and sensors for lid open/shut etc. I have built custom firmware for ChromeBook users who have requested it, though I don't make those available publicly, only upon request, since I can't test them beforehand.
FYI, I added a proper legacy BIOS (SeaBIOS) for Haswell ChromeBook users, who can now safely use the dual boot features of the script. It's completely transparent, and I'd appreciate it if you could give it a test for me. Just run the script and choose the legacy BIOS update option (#4)
