[linux-armv7 4.17-4.18] Will not boot on Asus C201

[hyshka]

I am running the linux-veyron kernel on an Asus C201PA laptop. I was using the mainline linux-armv7 previously but it became unstable. I started to test out the mainline kernel again because some further instructions had been added to the Asus Chromebook Flip C100P instructions: https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p

I have followed the instructions several times for a USB drive. I am able to boot a fresh linux-veyron kernel but not a fresh linux-armv7 kernel. I get the same result if I install directly from a tarball (ex. http://os.archlinuxarm.org/os/ArchLinux ... est.tar.gz
) or if I install the linux-veyron tarball (http://os.archlinuxarm.org/os/ArchLinux ... est.tar.gz), boot it, and then install the linux-armv7 kernel (and linux-armv7-chromebook) through pacman.

After installing the linux-armv7 kernel the device will not boot. After hitting the 'boot from external device' key combination with the default ChromeOS bootloader (CTRL-U) the device hangs with a white screen.

I've double checked that the device is in developer mode and has `dev_boot_signed=0`, `dev_boot_legacy=1`, and `dev_boot_usb=1`.

I've also tried booting into ChromeOS, quickly shutting down, and booting into the linux-armv7 kernel as suggested in some other thread but the same issue occurred.

This package seems to be broken on Asus C201PA devices and am wondering if there is a fix out there or a way to debug this further to see what's going on.

[yaroze]

I also have the same problem after updating I can not boot just get a blank screen.

On the Asus Chromebook Flip C100P I have been using the mainline kernel as the Veyron build does not perform as well.

But after updating its dead.

[hyshka]

I'm going to try building an older version based of the alarm PKGBUILDs. I think 4.13 was the last to work for me so I will see if I can get it working again with a fresh install.

[yaroze]

The last one I used that worked was 4.16 back in April.
I am sticking with that for now but I guess going forward there is no way to see why latest version is broken as there is no way to boot it.

Anyone have a better idea on how check why it is broken?

[TheSaint]

What about keeping the two kernel. If the newer still cause problems, then switch back to the working one.

[hyshka]

I finished building the kernel myself. I can confirm that "linux-armv7-4.13.11-1 and linux-armv7-chromebook-4.13.11-1" as well as "4.14.15-1" versions will boot on the c201 and that the "4.17.12-1" version would not.

I will try building 4.15, 4.16, etc. myself and see if there's a specific version that breaks down.

[yaroze]

So 4.14.15-1 is the newest version that works?

Would anyone have a idea how we can get the later versions working ie how do we go about finding out why they dont work.

If they wont boot where what kind of things could cause that?


Thanks!

[TheSaint]

I installed the latest 4.18 for linux-arm7 on Asus TB S, and it seems working fine. But I can't say much about the chromebook.

[summers]

$this->bbcode_second_pass_quote('', 'I') installed the latest 4.18 for linux-arm7 on Asus TB S, and it seems working fine. But I can't say much about the chromebook.

[yaroze]

I guess I will just have to jump over to the ChromeOS 3.14 kernel to stay upto date and accept the performance issues.

Can I do that without re-installing everything the wiki shows how to go from ChromeOS 3.14 kernel to mainline but not the other way.

Thanks