Looking to commission a new Chromium build (COMMUNITY BOUNTY)

[brent.thierens]

There is a lot to be adapted to this, but I currently do not have the time to do it. This only has like 5 changes or so. However, it might be interesting to check how we can get the kernel to install itself to the boot partition, as required by uboot.

---

And indeed the toolchain is quite old, but I tried upgrading it manually, and that only resulted in more problems.
I think it would be very interesting to see how we can take a normal Gentoo build environment and transform it into a ChromiumOS one. Then, we could have the latest versions of all the packages and I think it would make things easier. However, I tried that several times already, no luck there either: a lot of dependency conflicts...

[brent.thierens]

Anyone knows what this means?
https://pastebin.com/csWqPaHp
Seems like there is something seriously wrong

---

Seems to be a uboot problem. Does anyone know where to find the mainline uboot image to flash?

[brent.thierens]

Okay, so if someone has the time to investigate this further:
1. Build the image from the overlay above, or download it from here (link)
2. Flash uboot to the image (link)
3. Mount the 12th partition and paste all the contents of this link on that partition (link)
4. Boot the SD card and connect the serial debugging cable, you will see that the image stops around 

Code:

[    5.668890] chromeos-boot-alert: self_repair
chromeos-boot-alert: self_repair

If have also attached the log (link).
I will try to make a new overlay so all this stuff isn't necessary, but the real problem is that CrOS does not want to boot because of the self repair he triggers (but no idea why)

[clover]

@brent.thierens
Warning: /lib/modules/5.9.0-rc4-00034-g7fe10096c150/modules.devname not found - ignoring

did you forget to install kernel modules?


self_repair: Message when starting to rebuild stateful partition.

this is printed before starting to rebuild a corrupted stateful partition.

I see (step 3) that you are mounting a partition and altering it before trying to boot the image.

If I understand correctly, you can't touch *any* partitions after the image is created, or checksums will fail / chromium os will see the partitions as corrupted.

We might be able to get around this by setting DISABLE_STATEFUL_SECURITY_HARDENING as true in the startup script per https://chromium.googlesource.com/chromi...tartup#137

[brent.thierens]

Thanks, I will check later to see if I can change something to this behaviour. However, this has also been the case long ago, when I had a working build script so I did not have to mess around with the partitions myself. Furthermore, I only edited ROOT-A, not STATE
PS Image now available

[clover]

@brent.thierens
I do not see a boot.scr in your overlay or in boot.zip... uboot needs this script in /boot to run correctly, doesn't it?

[clover]

@brent.thierens

We might be able to get around this by setting DISABLE_STATEFUL_SECURITY_HARDENING as true in the startup script per https://chromium.googlesource.com/chromi...tartup#137

nevermind, this did nothing

[brent.thierens]

@brent.thierens
I do not see a boot.scr in your overlay or in boot.zip... uboot needs this script in /boot to run correctly, doesn't it?

will check! However, I think boot.scr is a replacement for the extlinux.conf file, not sure

[clover]

I have gotten further with this. no graphical output yet but i am able to log in to a tty shell from the serial console.

[clover]

https://www.ironrobin.net/clover/droppy/...2020-09-20
Just reporting some progress on this. Link to latest build with working kernel + graphical output. Still missing libraries, cant login via gui yet.

not sure where they best place to get libraries is. missing libraries need to be in /usr/lib64 i think.

tty login is
user=chronos
password=test0000