Hi,
On Mon, 20 Nov 2017, Guillaume Gardet wrote:
Le 18/11/2017 à 21:12, Misha Komarovskiy a écrit :
On Sat, Oct 7, 2017 at 3:06 PM, Daniel Bischof <[email protected]>
wrote:
On Mon, 21 Aug 2017, Misha Komarovskiy wrote:
On Sun, Aug 20, 2017 at 3:09 PM, Daniel Bischof <[email protected]>
wrote:
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 tried
openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2017.10.02-Build1.1
today and still no luck. Did you dig into this already? I'm not
skilled enough to be helpful in this stage, i'm afraid...
Guillaume fixed chromebook snow images you can try current TW build
http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Chromebook/images/openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2017.11.17-Build2.2.raw.xz
It boots fine here, i only expirienced hard freeze on first boot which
chanhes partition setup, here is fault output to serial uart
http://paste.opensuse.org/98361543 If it wont reboot for too long on
first boot you probably also caught this fault just reboot by power
key, second boot is fine.
It seems that Build2.4 has video output broken. I guess this is due to
new 4.14.0 kernel? Unfortunately, I do not have any serial access on my
chromebook. Could you have a look, since it seems you have serial on
your chromebook. Or anyone else?
I tried 2017.11.17-Build2.4 today: It boots (yay!) and resizes the file
system. After "Starting the kernel" the screen goes and stays black. So,
yes, video output broken seems likely. I will try again as soon as a new
build is available.
Thank you very much, both of you.
Best regards,
--Daniel.
