search

quarkscript / linux-armv7-xe303c12-only

Linux kernel for old google-snow chromebook
GNU General Public License v2.0
18 stars 2 forks source link

XE303C12 #14

Open betolley opened 2 years ago

betolley commented 2 years ago

My xe303c12 can boot any of your images. I noticed that the partitions both are chrome partitions. I have also tried multiple other builds from other projects. I can't boot any of them. Are there different XE303C12's? SNOW CLEAR A-I 3922 is the model. Other images (that don't work) have a chrome partition then ext4. The ones that don't boot just beep when I press CTRL-U.

quarkscript commented 2 years ago

Hi. Well, in my case I was getting the same results when the kernel image was larger than 8MB or when using faulty "uboot-tools" or "vboot-utils" to sign the kernel. For the kernel size, someone used a script similar to mine to reduce size when kernel contained unnecessary firmware. May be it helps. https://archlinuxarm.org/forum/viewtopic.php?f=60&t=15834 and https://archlinuxarm.org/forum/viewtopic.php?f=47&t=15169&p=67825#p67825 The type of file system should not affect the ability to boot, at least for kernel boot. I was used btrfs only to put the system image on a 2/4GB sd card. In case the error occurs due to the disk format, then you can use the empty disk image maker script to create your own disk image with rootfs of your choice: btrfs, ext4 ,f2fs (of course, the kernel should support it).

In case other project are for "nv-uboot" firmware it will not boot on Chromebook with regular firmware. Solution may be a flashing nv-uboot or signing kernel and make ChromeOs-type disk.