I first want to congratulate MrChromebox on his awesome scripts, and continuing awesomeness.
except for the audio almost everything worked out of the box on this machine (‘roric/rull’) with Arch linux.
Bluetooth audio works, and that is almost as good (or better).
fn-f# keys were silly, and cannot be used to switch to a virtual terminal (this seems to be fixable)
I personally could not get suspend to ram to work.
I have seen no reports on this relatively new intel chromebook setup.
Is anyone able to suspend or suspend to disk to work?
my lazy setup for testing which does not suspend:
using developer mode with mrchromebox script, did not touch solidstate drive, did not remove WP, archinstall for installation, and primary partition is on usb3 thumbdrive with LUKS. zram stuff from archinstall is running.
suspend error seems to be a ‘suspend timeout’
I assume that because this device is is use by others in the forum, that my problem may be associated with the nonstandard install I did (USB key/ WP enabled/ LUKS encryption/ archinstall/zram?)
PS other OS tried: manjaro –> had a weird x11/wayland(?) black screen, but it did boot, and seemed to load up until desktop (did not freeze), fn-f# keys did not work to switch to virtual terminal for debugging
I did not remove the WP screw,
1.5 I used the script to allow seabios edk2 to boot
1.7 and installed arch from one booted usb to another using the archinstall package
When it boots, it boots into developer mode, then ctrl +L to seabios, then to whatever the Arch bootloader is, then to arch.
Does anyone know if installing the full rom might make the sleep behavior fixable or fix it?
**
that is my real question**, because I know a couple of you guys have this installed, and probably know if suspend works on your machines.
okay so you are saying that the RW_LEGACY Still relies on chrome firmware or some other google firmware which:
may have a bug which:
may be causing the suspend issue?
So that I may get different results with unbroken firmware using the “full rom”
Question: ?Am I using possibly broken firmware with RW_LEGACY? which isn’t compatible with the modern linux kernel?
RW_LEGACY is just a bootloader. you’re still running the stock Google firmware. built for running ChromeOS.
Basically, if it works cool, if not there’s nothing that can be done from the firmware side of things. Maybe you can work around the issue in the OS. But it’s not something most of the developers here spend any time on.
Right, awesome, sweet! That means I will wait and see if someone has it working using the full_rom and if some troll answers yes, then I will believe them… hehe maybe I should just @cydoxcydox because he sounds like he has the fullrom install.
Cydox, or anyone else: do you know suspend work on the full_rom ed2k firmware in (any) linux?
by the way thank both of you for all the work you’ve done, the firmware fix for the touchpad and everything else!
Thanks for helping me figure this out!
Wait, I am assuming that this means I will not be running google firmware if I use the ‘fullrom’ option and get rid of chrome?
edk2 to boot