[linux-armv7] kernel 5.10.16 to 5.11.0 cant boot chromebook

[m040601]

---------------------------------------------------------------------------------------
- [linux-armv7] kernel upgrade 5.10.16-1 to 5.11.0-1 cant boot chromebook
- solution: package downgrade from 5.11 to 5.10.6
- suspected cause: changes in kernel "config"
---------------------------------------------------------------------------------------

After these 2 packages update

linux-armv7
linux-armv7-chromebook

my Samsung Chromebook,
https://archlinuxarm.org/platforms/armv ... chromebook,
cant't boot any more.

I strongly suspect these big set of changes,
https://github.com/archlinuxarm/PKGBUIL ... mv7/config
made to the kernel config file "config". But I am not an expert here.


This has happened already before in the last years with similar botched kernel updates. Usually it's a blank screen. The issue gets solved in the next package releases.

But this time, it's not even that. It doesnt even tries to boot.
It seems it cant find the kernel, and the message

$this->bbcode_second_pass_quote('', '&')quot;Chrome OS is damaged or missing"

[macbaze]

To save some others time i'll post a bit more detailed info on how to downgrade XE303 to 5.10.16 kernel if you don't have bootable ChromeOS (broken Arch Linux is in emmc)
Creation of recovery USB was exactly the same as described in wiki, but i did it on x86_64 Arch linux and of course there was no cgpt. Got it with vboot-utils from AUR.
My chromebook for some reason was unable to boot from USB (two beeps after pressing Ctrl+U).
I see no other way to restore flags than using Chrome recovery removable. Prepared USB drive as described here https://dev.chromium.org/chromium-os/de ... n-dev-mode

[m040601]

Just saw that there were some new updates to these not working packages,

https://archlinuxarm.org/packages/armv7 ... -armv7/log
https://github.com/archlinuxarm/PKGBUIL ... inux-armv7

The updates were from version linux-armv7 5.11.0-1, to, version linux-armv7 5.11.0-2.
It seems it was only this little change in file "config"

$this->bbcode_second_pass_code('', '
-CONFIG_VIRTIO_PCI=m
+CONFIG_VIRTIO_PCI=y')

I already tested them. On the rescue USB stick of course, not on the main chromebook.

No change in the situation.
The same boot problem continues.



PS: The above commit seems to be totally unrelated to this problem, but still interesting.

I am not very knowlegdeable about "who" and "how" these kernel packages updates work.

Could someone who knows, describe these proceses better, to us end users ?

This might be one of those, "this is obvious". Well it might be "obvious" to you if you are a maintainer, developer working daily on this stuff.I cant seem to form a picture of how the "system" works just by reading what is available on the main site, archlinuxarm.org

I am really curious about how all these important big kernel changes, in the end affect my laptop and my raspberry pi running arch arm. Where do those updates come from ? "Upstream" linux? The Raspberry Foundation linux kernel fork ? Individual Arch arm developer changes ? Who is a "commiter" and who is an "author" ? Why do these changes break the system sometimes ? Arent they automatically tested ?

In this case, let me have a go trying to understand it with this example.

Alexandru Stan seems to be a google employee, https://hypertriangle.com/~alex/resume/
With a personal fork of the PKGBUILDS, https://github.com/amstan/PKGBUILDs .
His changes , https://github.com/amstan/PKGBUILDs/commits/master , seem to be regularly merged into the official PKGBUILDS

He had this interesting pull request, https://github.com/archlinuxarm/PKGBUILDs/pull/1856

$this->bbcode_second_pass_quote('', '.')..I was finally able to get my qemu going for linux-armv7

To confirm and expand what macbaze has said on these two separate issues:

1. $this->bbcode_second_pass_quote('', '.')..Creation of recovery USB ...