Maurice van Kruchten

@libjared from stable to beta to dev there will be no powerwash only when going back dev to beta to stable there is a powerwash needed.

@libjared Something is indeed wrong, I need to investigate further, but I had to put the backup kernel that the script creates back from a linux distro to make my...

Ok, I think I narrowed it down. When running the script it adds 2 flags `lsm.module_locking=0 disablevmx=off` on reboot it goes fine for me, however when I close the lid...

@libjared Yeah, looked at the latest kernel commits, but couldn't find anything that popped out at first sight. Maybe @drinkcat has an idea why enabling vmx is causing a reboot/crash...

I found this [crbug](https://bugs.chromium.org/p/chromium/issues/detail?id=789027&q=disablevmx&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified) It seems the same issue, since I noticed that they [backported kaiser also to 3.18](https://chromium.googlesource.com/chromiumos/third_party/kernel/+log/chromeos-3.18)

@libjared Well you can, but you will need to boot a linux distro on your chromebook and dd the backup kernel back manually. I see if I have some time...

I tried it with ``` chronos@localhost / $ uname -a Linux localhost 3.18.0-17049-gd99a5b37a7d2 #1 SMP PREEMPT Thu Mar 22 14:17:10 PDT 2018 x86_64 Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz GenuineIntel...

@peterboord As soon as we solve #45 I will make this work again.

Sorry guys, been too occupied lately. I indeed think new kernel headers are the way to go. However if you follow the guide in the wiki you will build from...

@drinkcat Ah ok, should be good enough. Thanks. @Pdbrantley try building the kernel headers with the above mentioned branch, that should be the right one for your kernel.