Le 02/12/2014 13:57, Guillaume Gardet a écrit :
Le 02/12/2014 00:34, Alexander Graf a écrit :
On 02.12.14 00:19, Misha Komarovsky wrote:
Hello,
I found that kernel or dtb file in current Chromebook contrib factory
image, tested on version 245, have boot problems. After kernel start
no signs of activity on stdout or serial console.
If i replace linux.vmx and dtb on lxboot partition and modules on
lxroot with same files from 12.3 dist image for chromebook im able to
boot and pass installation fine.
Also after installation and reboot, sd card not bootable at all, first
partition on sdcard changed type code to 0700 and size to 32mb,
probably cgpt script failed to fix it after installation for some
reason.
Bundled armsoc x11 driver fail to start because it is for abi 13 not abi 18.
I updated armsoc driver just now from 0.0.1 to 1.1.0. It may help. :)
That does indeed sound pretty broken. I think someone needs to sit down
and check which of all those components is already done well enough
upstream to drop our hacks.
For example, I think u-boot has upstream snow support now, so we could
just use that. The kernel should be ok as well.
Current Factory u-boot-snow (2015.01-rc2) does boot but is not really usable.
It seems there is a problem to access SD card. But LCD and keyboard are working
fine. :)
I will have a look at it.
With some patches, I am able to use a USB stick (no external SD) with upstream
u-boot-snow and Factory kernel-lpae does boot !
On kernel start, you must wait a little bit because at the beginning, there is
just a black screen, followed later by a normal screen and a blue YaST
Firstboot screen. :)
But the are some problems:
* upstream u-boot does not handle external SD card for an unknown reason
(internal eMMC is usable). Downstream u-boot has no bootz support.
* keyboard does not work under Linux (you must use an USB keyboard).
* Second boot is deeply broken. U-Boot is not launched at all because "cgpt"
command is applied to /dev/mmcblk0 (internal eMMC) instead of /dev/sda (USB stick) (Kiwi
bug?). Once this one manually fixed, u-boot load the kernel and then hang with a black
screen. Probably due to missing modules in dracut initrd. (I will submit a JeOS update
once tested)
* No wifi (at least on 1st boot)
I will send an update (and SR) once tests are passed.
Guillaume
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
