Hello Daniel, On Sun, Aug 20, 2017 at 3:09 PM, Daniel Bischof <[email protected]> wrote: > Hi, > > On Mon, 14 Aug 2017, msuchanek wrote: > >> On Sat, 12 Aug 2017 14:16:51 +0200 (CEST) Daniel Bischof >> <[email protected]> wrote: >> >>> I tried >>> openSUSE-Tumbleweed-ARM-XFCE-chromebook.armv7l-2017.07.22-Build1.1 recently, >>> but it just beeps and kicks me back to the boot screen immediately. No >>> messages on screen, partition resizing, etc. >>> >>> Any hints? Some cgpt magic I could try from ChromeOS perhaps? >> >> >> You can try installing upstream u-boot following the chainload steps >> deteailed in several places on the interwebs - eg here >> http://chrodyssey.blogspot.cz/2015/04/the-bootloader-chained.html >> >> The current u-boot supports display on Snow but the EFI GOP emulation >> (which the Tumbleweed image would use if it booted) is broken. >> >> It probably does not boot because the loader is missing or not marked as >> bootable or you did not enable USB boot on the chromebook. >> >> The developer mode on current versions of ChromeOS has more features than >> it used to but is also more flaky - it seems services tend to stop working >> randomly and currently I Cannot boot at all after the devmode installation >> fell apart. > > > thanks to both of you (Michal and Misha) for your answers, nice to hear that > you didn't give up on Snow, even since it is no longer available for > purchase. >
I partly revived my chromebook snow and i was able to test current Tumbleweed image openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2017.08.13-Build1.6.raw.xz I found that factory U-Boot for some reason don't like our chainloading U-BOOT partition with message: GptNextKernelEntry looking at new prio partition 1 GptNextKernelEntry s1 t5 p10 GptNextKernelEntry likes partition 1 Found kernel entry at 2048 size 409604 Not a valid verified boot key block. Verifying key block signature failed. Not a valid verified boot key block. Verifying key block hash failed. Marking kernel as invalid. GptNextKernelEntry looking at new prio partition 1 GptNextKernelEntry s1 t5 p10 GptNextKernelEntry no more kernels i will try to investigate further why this happen. > I played around a little with the broken image, but failed to recompile > u-boot as described in the above link - need to dig into this. > > I switched (temporarily, i hope) to archlinuxARM [1], which works fine (all > HW incl. 2d acceleration), but it is uncomfortable for me, since i've never > used archlinux before. Kali (Debian-based) works, too, but has no 2d > acceleration. Both appear to use the ChromeOS-kernel. > > I don't use ChromeOS, but keep it up-to-date via guest mode - maybe a > not-so-good idea afterwards... > > [1] https://archlinuxarm.org/platforms/armv7/samsung/samsung-chromebook > > > Best regards, > > --D. > --- > Daniel Bischof <[email protected]> > -- > To unsubscribe, e-mail: [email protected] > To contact the owner, e-mail: [email protected] > -- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
