Re: [opensuse-arm] Re: Re : [opensuse-arm] Latest Chromebook images

Le 06/02/2014 08:49, Josua Mayer a écrit :

Hi,

I was trying something different to get the chromebook working: I found in the Images.wiwi.in, that a lot of packages are marked as PKG_BOOT_TAG and that way included in the initrd, suchas vboot, gptfdisk,mrvl-firmware, which shouldnt be needed for booting imo. I reduced those to just PKG_BOOT_TAG(u-boot-chromebook), PKG_BOOT_TAG(dtb-exynos5), which resulted in a smaller initrd that loaded without warnings. But then I get just a black screen after the kernel is (hopefully) started.

This may be caused by a bad DTB file. kernel-chromebook provide "/boot/exynos5250-snow.dtb" and we actually use "/boot/dtb/exynos5250-snow.dtb" from dtb-exynos5 package. Try to replace the DTB file in /boot/dtb/ with the one from kernel-chromebook package. Guillaume

In my opinion, this initrd is far too huge anyway, and I wonder why that is.

Josua Mayer

Am 05.02.2014 20:46, schrieb guillaume.gardet@free.fr:

...

Hi,

----- Daniel Bischof a écrit :

...

Hi,

are the latest Chromebook images supposed to work? I tried the most recent Factory-ARM-XFCE-chromebook.armv7l-1.12.1-Build169.2 (of today) and got No. The problem is "ext2fs doesn't support tripple indirect blocks" which prevent to load all the initrd.

I am working on upstream u-boot which could fix that. But it is not yet ready. :(

Guillaume

...

----- ** File not found uEnv.txt Loading file "boot.scr" from mmc device 1:2 (lxboot) 2138 bytes read Running bootscript ... ## Executing script at 40007000 mmc_init err 0, time 101923 mmc0(part 0) is current deuice Loading file "boot/linux.vmx" from mmc deuice 0:2 (KERN-A) Failed to mount ext2 filesystem ... ** Bad ext2 partition or disk — mmc 0:2 ** mmc1 is current device Loading file "boot/linux.vmx" from mmc device 1:2 (lxboot) 3568304 bytes read Loading file "boot/initrd.uboot" from mmc device 1:2 (lxboot) ** ext2fs doesn't support tripple indirect blocks. ** ** Unable to read "boot/initrd.uboot" from mmc 1:2 ** Loading file "dtb/exynos5250—snow.dtb" from mmc device 1:2 (lxboot) 34150 bytes read ## Booting kernel from Legacy Image at 40007000 ... Image Name: Linux—3.4.0—2—chromebook Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3568240 Bytes = 3.4 MiB Load address: 40008000 Entry Point: 40008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 4f000000 ... Image Name: Initrd Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 156490936 Bytes = 149.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... Bad Data CRC Ramdisk image is corrupt or invalid mmc0(part 0) is current device ** Block device usb 0 not supported mmc1 is current device ** Block device usb 1 not supported (Re)start USB... USB: Register 1313 NbrPorts 3 [USB] usb_lowlevel_init:852 0 [USB] usb_lowlevel_init:852 1 USB EHCI 1.00 1 USB Device(s) found scanning bus for storage devices ... 0 Storage Device(s) found Tring USB on device ** Block device usb 0 not supported ** Block device usb 0 not supported SMDK5250 # -----

on initial boot. Same result with most recent 13.1 images.

Best regards,

--D.B. -- Daniel Bischof

-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org