[opensuse-arm] Chromebook factory image problems
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. -- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
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.
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. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
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. 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. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
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: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hello, Just tried to book chromebook images version 253. Usb wont boot sayin no kernel found, maybe so trick is required? VbTryLoadKernel() start, get_info_flags=0x1 USB: Register 1313 NbrPorts 3 USB EHCI 1.00 2 USB Device(s) found USB: Register 1313 NbrPorts 3 USB EHCI 1.00 2 USB Device(s) found scanning bus for storage devices... 1 Storage Device(s) found MMC: no card present mmc_init err -16, time 1986 boot_device_mmc.c: boot_device_mmc_scan: mmc_init fail MMC Device 4 not found VbTryLoadKernel() found 0 disks VbSetRecoveryRequest(90) VbBootDeveloper() - no kernel found on USB utility.c: VbExBeep: About to beep for 250 ms at 200 Hz. VbSetRecoveryRequest(0) leaving VbDisplayScreenFromGBB() with 0 VbBootDeveloper() - trying fixed disk
From SD i can reach u-boot, it said unknow partition for mmc dev 1 and detect capacity is wrong.
snow # mmc dev 1 dwmci_send_cmd: DATA ERROR! dwmci_send_cmd: DATA ERROR! switch to partitions #0, OK mmc1 is current device snow # mmc info Device: EXYNOS DWMMC Manufacturer ID: 3 OEM: 5344 Name: SL08G Tran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: w.4 GiB Bus Width: 4-bit snow # mmc part ## Unknown partition table snow # If i try to use SD card and USB stick at same time, mainline u-boot start only XHCI hub and wont detect any storage devices here: U-Boot 2015.01-rc2 (Dec 01 2014 - 21:54:38) for snow CPU: Exynos5250@1700MHz Board: Google Snow I2C: ready DRAM: 2 GiB trace: copying 000ad9c0 bytes of early data from 50000000 to bedef000 trace: enabled Board PMIC init TPS>5090 PMIC init MMC: EXYNOS DWMMC: 0, GXYNOS DWMMC: 1 SF: Detectmd GD25LQ32 with page size 256 Bytes, erase size 4 KiBl total 4 MiB *** Warning - bad CRC, using default environment Exynos DP init done RKɽ͵ec-keyb _ut: lcd Err: lcd Net: No ethernet found. Hit any key`to stop autoboot: 0 mmc - MMC sub system Usage: mmc info - display info of the current MMC device mmc read addr blk# cnt mmc write addr blk# cnt mmc erase blk# cnt mmc rescan mmc part - lists available partition on current mmc device mmc dev [dev] [part] - show or set current mmc device [partition] mmc list - lists available devices mmc bootbus dev boot_bus_width reset_boot_bus_width boot_mode - Set the BOOT_BUS_WIDTH field of the specified device mmc bootpart-resize <dev> <boot part size MB> <RPMB part size MB> - Change sizes of boot and RPMB partitions of specifiel device mmc partconf dev boot_ack boot_partition partition_access - Change the bits of the PARTITION_CONFIG field of the specified device mmc rst-function dev value - Change the RST_n_FUNCTION field of the specified device WARNING: This is a write-once field and 0 / 1 / 2 are the only valid values. mmc setdsr <value> - set DWR register value snow # usb storage USB is stoppel. Please issue 'usb start' first. snow # usb start (Re)start USB... USB0: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found snow # usb storage No storage devices, perhaps not 'usb start'ed..? snow # On Wed, Dec 3, 2014 at 5:19 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
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
-- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, Le 06/12/2014 22:19, Misha Komarovsky a écrit :
Hello, Just tried to book chromebook images version 253. Usb wont boot sayin no kernel found, maybe so trick is required?
You need an updated u-boot. ;) I am waiting for 2015.01-rc3 (should be out in 2 or 3 days) to push my changes because there are lots of problem with -rc2. If you want to test now, please use this u-boot (based on a modified GIT version): http://guillaume.gardet.free.fr/openSUSE/u-boot.img Then, copy it to your USB stick with this script (update path to u-boot.img and fix your device: /dev/sdX): http://guillaume.gardet.free.fr/openSUSE/dd_snow.sh SD card booting is not working ATM, so please boot from USB (black USB2 slot, not blue USB3 slot). JeOS is working fine. X11 images are broken (strange display once Xorg is booted, only the cursor is ok.) Guillaume
VbTryLoadKernel() start, get_info_flags=0x1 USB: Register 1313 NbrPorts 3 USB EHCI 1.00 2 USB Device(s) found USB: Register 1313 NbrPorts 3 USB EHCI 1.00 2 USB Device(s) found scanning bus for storage devices... 1 Storage Device(s) found MMC: no card present mmc_init err -16, time 1986 boot_device_mmc.c: boot_device_mmc_scan: mmc_init fail MMC Device 4 not found VbTryLoadKernel() found 0 disks VbSetRecoveryRequest(90) VbBootDeveloper() - no kernel found on USB utility.c: VbExBeep: About to beep for 250 ms at 200 Hz. VbSetRecoveryRequest(0) leaving VbDisplayScreenFromGBB() with 0 VbBootDeveloper() - trying fixed disk
From SD i can reach u-boot, it said unknow partition for mmc dev 1 and detect capacity is wrong.
snow # mmc dev 1 dwmci_send_cmd: DATA ERROR! dwmci_send_cmd: DATA ERROR! switch to partitions #0, OK mmc1 is current device snow # mmc info Device: EXYNOS DWMMC Manufacturer ID: 3 OEM: 5344 Name: SL08G Tran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: w.4 GiB Bus Width: 4-bit snow # mmc part ## Unknown partition table snow #
If i try to use SD card and USB stick at same time, mainline u-boot start only XHCI hub and wont detect any storage devices here:
U-Boot 2015.01-rc2 (Dec 01 2014 - 21:54:38) for snow
CPU: Exynos5250@1700MHz Board: Google Snow I2C: ready DRAM: 2 GiB trace: copying 000ad9c0 bytes of early data from 50000000 to bedef000 trace: enabled Board PMIC init TPS>5090 PMIC init MMC: EXYNOS DWMMC: 0, GXYNOS DWMMC: 1 SF: Detectmd GD25LQ32 with page size 256 Bytes, erase size 4 KiBl total 4 MiB *** Warning - bad CRC, using default environment
Exynos DP init done RKɽ͵ec-keyb _ut: lcd Err: lcd Net: No ethernet found. Hit any key`to stop autoboot: 0 mmc - MMC sub system
Usage: mmc info - display info of the current MMC device mmc read addr blk# cnt mmc write addr blk# cnt mmc erase blk# cnt mmc rescan mmc part - lists available partition on current mmc device mmc dev [dev] [part] - show or set current mmc device [partition] mmc list - lists available devices mmc bootbus dev boot_bus_width reset_boot_bus_width boot_mode - Set the BOOT_BUS_WIDTH field of the specified device mmc bootpart-resize <dev> <boot part size MB> <RPMB part size MB> - Change sizes of boot and RPMB partitions of specifiel device mmc partconf dev boot_ack boot_partition partition_access - Change the bits of the PARTITION_CONFIG field of the specified device mmc rst-function dev value - Change the RST_n_FUNCTION field of the specified device WARNING: This is a write-once field and 0 / 1 / 2 are the only valid values. mmc setdsr <value> - set DWR register value
snow # usb storage USB is stoppel. Please issue 'usb start' first. snow # usb start (Re)start USB... USB0: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found snow # usb storage No storage devices, perhaps not 'usb start'ed..? snow #
On Wed, Dec 3, 2014 at 5:19 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
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: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
dd_snow.sh script need also /tmp/newkern is it symlink to u-boot.img or real new kernel? On Sun, Dec 7, 2014 at 4:21 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Hi,
Le 06/12/2014 22:19, Misha Komarovsky a écrit :
Hello, Just tried to book chromebook images version 253. Usb wont boot sayin no kernel found, maybe so trick is required?
You need an updated u-boot. ;) I am waiting for 2015.01-rc3 (should be out in 2 or 3 days) to push my changes because there are lots of problem with -rc2. If you want to test now, please use this u-boot (based on a modified GIT version): http://guillaume.gardet.free.fr/openSUSE/u-boot.img
Then, copy it to your USB stick with this script (update path to u-boot.img and fix your device: /dev/sdX): http://guillaume.gardet.free.fr/openSUSE/dd_snow.sh
SD card booting is not working ATM, so please boot from USB (black USB2 slot, not blue USB3 slot).
JeOS is working fine. X11 images are broken (strange display once Xorg is booted, only the cursor is ok.)
Guillaume
VbTryLoadKernel() start, get_info_flags=0x1 USB: Register 1313 NbrPorts 3 USB EHCI 1.00 2 USB Device(s) found USB: Register 1313 NbrPorts 3 USB EHCI 1.00 2 USB Device(s) found scanning bus for storage devices... 1 Storage Device(s) found MMC: no card present mmc_init err -16, time 1986 boot_device_mmc.c: boot_device_mmc_scan: mmc_init fail MMC Device 4 not found VbTryLoadKernel() found 0 disks VbSetRecoveryRequest(90) VbBootDeveloper() - no kernel found on USB utility.c: VbExBeep: About to beep for 250 ms at 200 Hz. VbSetRecoveryRequest(0) leaving VbDisplayScreenFromGBB() with 0 VbBootDeveloper() - trying fixed disk
From SD i can reach u-boot, it said unknow partition for mmc dev 1 and detect capacity is wrong.
snow # mmc dev 1 dwmci_send_cmd: DATA ERROR! dwmci_send_cmd: DATA ERROR! switch to partitions #0, OK mmc1 is current device snow # mmc info Device: EXYNOS DWMMC Manufacturer ID: 3 OEM: 5344 Name: SL08G Tran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: w.4 GiB Bus Width: 4-bit snow # mmc part ## Unknown partition table snow #
If i try to use SD card and USB stick at same time, mainline u-boot start only XHCI hub and wont detect any storage devices here:
U-Boot 2015.01-rc2 (Dec 01 2014 - 21:54:38) for snow
CPU: Exynos5250@1700MHz Board: Google Snow I2C: ready DRAM: 2 GiB trace: copying 000ad9c0 bytes of early data from 50000000 to bedef000 trace: enabled Board PMIC init TPS>5090 PMIC init MMC: EXYNOS DWMMC: 0, GXYNOS DWMMC: 1 SF: Detectmd GD25LQ32 with page size 256 Bytes, erase size 4 KiBl total 4 MiB *** Warning - bad CRC, using default environment
Exynos DP init done RKɽ͵ec-keyb _ut: lcd Err: lcd Net: No ethernet found. Hit any key`to stop autoboot: 0 mmc - MMC sub system
Usage: mmc info - display info of the current MMC device mmc read addr blk# cnt mmc write addr blk# cnt mmc erase blk# cnt mmc rescan mmc part - lists available partition on current mmc device mmc dev [dev] [part] - show or set current mmc device [partition] mmc list - lists available devices mmc bootbus dev boot_bus_width reset_boot_bus_width boot_mode - Set the BOOT_BUS_WIDTH field of the specified device mmc bootpart-resize <dev> <boot part size MB> <RPMB part size MB> - Change sizes of boot and RPMB partitions of specifiel device mmc partconf dev boot_ack boot_partition partition_access - Change the bits of the PARTITION_CONFIG field of the specified device mmc rst-function dev value - Change the RST_n_FUNCTION field of the specified device WARNING: This is a write-once field and 0 / 1 / 2 are the only valid values. mmc setdsr <value> - set DWR register value
snow # usb storage USB is stoppel. Please issue 'usb start' first. snow # usb start (Re)start USB... USB0: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found snow # usb storage No storage devices, perhaps not 'usb start'ed..? snow #
On Wed, Dec 3, 2014 at 5:19 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
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
-- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
new_kern is built using vbutil_kernel command. So, you need the vboot package to be installed: http://software.opensuse.org/package/vboot?search_term=vboot Guillaume Le 07/12/2014 15:43, Misha Komarovsky a écrit :
dd_snow.sh script need also /tmp/newkern is it symlink to u-boot.img or real new kernel?
On Sun, Dec 7, 2014 at 4:21 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Hi,
Le 06/12/2014 22:19, Misha Komarovsky a écrit :
Hello, Just tried to book chromebook images version 253. Usb wont boot sayin no kernel found, maybe so trick is required?
You need an updated u-boot. ;) I am waiting for 2015.01-rc3 (should be out in 2 or 3 days) to push my changes because there are lots of problem with -rc2. If you want to test now, please use this u-boot (based on a modified GIT version): http://guillaume.gardet.free.fr/openSUSE/u-boot.img
Then, copy it to your USB stick with this script (update path to u-boot.img and fix your device: /dev/sdX): http://guillaume.gardet.free.fr/openSUSE/dd_snow.sh
SD card booting is not working ATM, so please boot from USB (black USB2 slot, not blue USB3 slot).
JeOS is working fine. X11 images are broken (strange display once Xorg is booted, only the cursor is ok.)
Guillaume
VbTryLoadKernel() start, get_info_flags=0x1 USB: Register 1313 NbrPorts 3 USB EHCI 1.00 2 USB Device(s) found USB: Register 1313 NbrPorts 3 USB EHCI 1.00 2 USB Device(s) found scanning bus for storage devices... 1 Storage Device(s) found MMC: no card present mmc_init err -16, time 1986 boot_device_mmc.c: boot_device_mmc_scan: mmc_init fail MMC Device 4 not found VbTryLoadKernel() found 0 disks VbSetRecoveryRequest(90) VbBootDeveloper() - no kernel found on USB utility.c: VbExBeep: About to beep for 250 ms at 200 Hz. VbSetRecoveryRequest(0) leaving VbDisplayScreenFromGBB() with 0 VbBootDeveloper() - trying fixed disk
From SD i can reach u-boot, it said unknow partition for mmc dev 1 and detect capacity is wrong.
snow # mmc dev 1 dwmci_send_cmd: DATA ERROR! dwmci_send_cmd: DATA ERROR! switch to partitions #0, OK mmc1 is current device snow # mmc info Device: EXYNOS DWMMC Manufacturer ID: 3 OEM: 5344 Name: SL08G Tran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: w.4 GiB Bus Width: 4-bit snow # mmc part ## Unknown partition table snow #
If i try to use SD card and USB stick at same time, mainline u-boot start only XHCI hub and wont detect any storage devices here:
U-Boot 2015.01-rc2 (Dec 01 2014 - 21:54:38) for snow
CPU: Exynos5250@1700MHz Board: Google Snow I2C: ready DRAM: 2 GiB trace: copying 000ad9c0 bytes of early data from 50000000 to bedef000 trace: enabled Board PMIC init TPS>5090 PMIC init MMC: EXYNOS DWMMC: 0, GXYNOS DWMMC: 1 SF: Detectmd GD25LQ32 with page size 256 Bytes, erase size 4 KiBl total 4 MiB *** Warning - bad CRC, using default environment
Exynos DP init done RKɽ͵ec-keyb _ut: lcd Err: lcd Net: No ethernet found. Hit any key`to stop autoboot: 0 mmc - MMC sub system
Usage: mmc info - display info of the current MMC device mmc read addr blk# cnt mmc write addr blk# cnt mmc erase blk# cnt mmc rescan mmc part - lists available partition on current mmc device mmc dev [dev] [part] - show or set current mmc device [partition] mmc list - lists available devices mmc bootbus dev boot_bus_width reset_boot_bus_width boot_mode - Set the BOOT_BUS_WIDTH field of the specified device mmc bootpart-resize <dev> <boot part size MB> <RPMB part size MB> - Change sizes of boot and RPMB partitions of specifiel device mmc partconf dev boot_ack boot_partition partition_access - Change the bits of the PARTITION_CONFIG field of the specified device mmc rst-function dev value - Change the RST_n_FUNCTION field of the specified device WARNING: This is a write-once field and 0 / 1 / 2 are the only valid values. mmc setdsr <value> - set DWR register value
snow # usb storage USB is stoppel. Please issue 'usb start' first. snow # usb start (Re)start USB... USB0: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found snow # usb storage No storage devices, perhaps not 'usb start'ed..? snow #
On Wed, Dec 3, 2014 at 5:19 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
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: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Forgot to install vboot dependencies, now it creates /tmp/newkern fine. On Sun, Dec 7, 2014 at 5:55 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
new_kern is built using vbutil_kernel command. So, you need the vboot package to be installed: http://software.opensuse.org/package/vboot?search_term=vboot
Guillaume
Le 07/12/2014 15:43, Misha Komarovsky a écrit :
dd_snow.sh script need also /tmp/newkern is it symlink to u-boot.img or real new kernel?
On Sun, Dec 7, 2014 at 4:21 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Hi,
Le 06/12/2014 22:19, Misha Komarovsky a écrit :
Hello, Just tried to book chromebook images version 253. Usb wont boot sayin no kernel found, maybe so trick is required?
You need an updated u-boot. ;) I am waiting for 2015.01-rc3 (should be out in 2 or 3 days) to push my changes because there are lots of problem with -rc2. If you want to test now, please use this u-boot (based on a modified GIT version): http://guillaume.gardet.free.fr/openSUSE/u-boot.img
Then, copy it to your USB stick with this script (update path to u-boot.img and fix your device: /dev/sdX): http://guillaume.gardet.free.fr/openSUSE/dd_snow.sh
SD card booting is not working ATM, so please boot from USB (black USB2 slot, not blue USB3 slot).
JeOS is working fine. X11 images are broken (strange display once Xorg is booted, only the cursor is ok.)
Guillaume
VbTryLoadKernel() start, get_info_flags=0x1 USB: Register 1313 NbrPorts 3 USB EHCI 1.00 2 USB Device(s) found USB: Register 1313 NbrPorts 3 USB EHCI 1.00 2 USB Device(s) found scanning bus for storage devices... 1 Storage Device(s) found MMC: no card present mmc_init err -16, time 1986 boot_device_mmc.c: boot_device_mmc_scan: mmc_init fail MMC Device 4 not found VbTryLoadKernel() found 0 disks VbSetRecoveryRequest(90) VbBootDeveloper() - no kernel found on USB utility.c: VbExBeep: About to beep for 250 ms at 200 Hz. VbSetRecoveryRequest(0) leaving VbDisplayScreenFromGBB() with 0 VbBootDeveloper() - trying fixed disk
From SD i can reach u-boot, it said unknow partition for mmc dev 1 and detect capacity is wrong.
snow # mmc dev 1 dwmci_send_cmd: DATA ERROR! dwmci_send_cmd: DATA ERROR! switch to partitions #0, OK mmc1 is current device snow # mmc info Device: EXYNOS DWMMC Manufacturer ID: 3 OEM: 5344 Name: SL08G Tran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: w.4 GiB Bus Width: 4-bit snow # mmc part ## Unknown partition table snow #
If i try to use SD card and USB stick at same time, mainline u-boot start only XHCI hub and wont detect any storage devices here:
U-Boot 2015.01-rc2 (Dec 01 2014 - 21:54:38) for snow
CPU: Exynos5250@1700MHz Board: Google Snow I2C: ready DRAM: 2 GiB trace: copying 000ad9c0 bytes of early data from 50000000 to bedef000 trace: enabled Board PMIC init TPS>5090 PMIC init MMC: EXYNOS DWMMC: 0, GXYNOS DWMMC: 1 SF: Detectmd GD25LQ32 with page size 256 Bytes, erase size 4 KiBl total 4 MiB *** Warning - bad CRC, using default environment
Exynos DP init done RKɽ͵ec-keyb _ut: lcd Err: lcd Net: No ethernet found. Hit any key`to stop autoboot: 0 mmc - MMC sub system
Usage: mmc info - display info of the current MMC device mmc read addr blk# cnt mmc write addr blk# cnt mmc erase blk# cnt mmc rescan mmc part - lists available partition on current mmc device mmc dev [dev] [part] - show or set current mmc device [partition] mmc list - lists available devices mmc bootbus dev boot_bus_width reset_boot_bus_width boot_mode - Set the BOOT_BUS_WIDTH field of the specified device mmc bootpart-resize <dev> <boot part size MB> <RPMB part size MB> - Change sizes of boot and RPMB partitions of specifiel device mmc partconf dev boot_ack boot_partition partition_access - Change the bits of the PARTITION_CONFIG field of the specified device mmc rst-function dev value - Change the RST_n_FUNCTION field of the specified device WARNING: This is a write-once field and 0 / 1 / 2 are the only valid values. mmc setdsr <value> - set DWR register value
snow # usb storage USB is stoppel. Please issue 'usb start' first. snow # usb start (Re)start USB... USB0: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found snow # usb storage No storage devices, perhaps not 'usb start'ed..? snow #
On Wed, Dec 3, 2014 at 5:19 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
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
-- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hello Guillaume, I cant understand where u-boot now lives in snow images. I tried dd_snow.sh script, it asks for run cgpt repair first on fresh created usb stick but no luck, u-boot version still same on start. Filled first partition of usb stick with /dev/zero, still same u-boot 2015.01-rc2, mystic. Got crazy idea maybe it is loaded from lxroot/boot/u-boot.img, replaced it with custom binary, no luck still 2015.01-rc2. Tried deleting gpt partitions one by one and only after partition 1 deleted, it stops to work, but whole partition filled with zeros. On Sun, Dec 7, 2014 at 5:55 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
new_kern is built using vbutil_kernel command. So, you need the vboot package to be installed: http://software.opensuse.org/package/vboot?search_term=vboot
Guillaume
Le 07/12/2014 15:43, Misha Komarovsky a écrit :
dd_snow.sh script need also /tmp/newkern is it symlink to u-boot.img or real new kernel?
On Sun, Dec 7, 2014 at 4:21 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Hi,
Le 06/12/2014 22:19, Misha Komarovsky a écrit :
Hello, Just tried to book chromebook images version 253. Usb wont boot sayin no kernel found, maybe so trick is required?
You need an updated u-boot. ;) I am waiting for 2015.01-rc3 (should be out in 2 or 3 days) to push my changes because there are lots of problem with -rc2. If you want to test now, please use this u-boot (based on a modified GIT version): http://guillaume.gardet.free.fr/openSUSE/u-boot.img
Then, copy it to your USB stick with this script (update path to u-boot.img and fix your device: /dev/sdX): http://guillaume.gardet.free.fr/openSUSE/dd_snow.sh
SD card booting is not working ATM, so please boot from USB (black USB2 slot, not blue USB3 slot).
JeOS is working fine. X11 images are broken (strange display once Xorg is booted, only the cursor is ok.)
Guillaume
VbTryLoadKernel() start, get_info_flags=0x1 USB: Register 1313 NbrPorts 3 USB EHCI 1.00 2 USB Device(s) found USB: Register 1313 NbrPorts 3 USB EHCI 1.00 2 USB Device(s) found scanning bus for storage devices... 1 Storage Device(s) found MMC: no card present mmc_init err -16, time 1986 boot_device_mmc.c: boot_device_mmc_scan: mmc_init fail MMC Device 4 not found VbTryLoadKernel() found 0 disks VbSetRecoveryRequest(90) VbBootDeveloper() - no kernel found on USB utility.c: VbExBeep: About to beep for 250 ms at 200 Hz. VbSetRecoveryRequest(0) leaving VbDisplayScreenFromGBB() with 0 VbBootDeveloper() - trying fixed disk
From SD i can reach u-boot, it said unknow partition for mmc dev 1 and detect capacity is wrong.
snow # mmc dev 1 dwmci_send_cmd: DATA ERROR! dwmci_send_cmd: DATA ERROR! switch to partitions #0, OK mmc1 is current device snow # mmc info Device: EXYNOS DWMMC Manufacturer ID: 3 OEM: 5344 Name: SL08G Tran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: w.4 GiB Bus Width: 4-bit snow # mmc part ## Unknown partition table snow #
If i try to use SD card and USB stick at same time, mainline u-boot start only XHCI hub and wont detect any storage devices here:
U-Boot 2015.01-rc2 (Dec 01 2014 - 21:54:38) for snow
CPU: Exynos5250@1700MHz Board: Google Snow I2C: ready DRAM: 2 GiB trace: copying 000ad9c0 bytes of early data from 50000000 to bedef000 trace: enabled Board PMIC init TPS>5090 PMIC init MMC: EXYNOS DWMMC: 0, GXYNOS DWMMC: 1 SF: Detectmd GD25LQ32 with page size 256 Bytes, erase size 4 KiBl total 4 MiB *** Warning - bad CRC, using default environment
Exynos DP init done RKɽ͵ec-keyb _ut: lcd Err: lcd Net: No ethernet found. Hit any key`to stop autoboot: 0 mmc - MMC sub system
Usage: mmc info - display info of the current MMC device mmc read addr blk# cnt mmc write addr blk# cnt mmc erase blk# cnt mmc rescan mmc part - lists available partition on current mmc device mmc dev [dev] [part] - show or set current mmc device [partition] mmc list - lists available devices mmc bootbus dev boot_bus_width reset_boot_bus_width boot_mode - Set the BOOT_BUS_WIDTH field of the specified device mmc bootpart-resize <dev> <boot part size MB> <RPMB part size MB> - Change sizes of boot and RPMB partitions of specifiel device mmc partconf dev boot_ack boot_partition partition_access - Change the bits of the PARTITION_CONFIG field of the specified device mmc rst-function dev value - Change the RST_n_FUNCTION field of the specified device WARNING: This is a write-once field and 0 / 1 / 2 are the only valid values. mmc setdsr <value> - set DWR register value
snow # usb storage USB is stoppel. Please issue 'usb start' first. snow # usb start (Re)start USB... USB0: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found snow # usb storage No storage devices, perhaps not 'usb start'ed..? snow #
On Wed, Dec 3, 2014 at 5:19 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
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
-- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, The image I gave you is a patched -rc2. So, you will get -rc2 as u-boot version. ;) Did you edit dd_snow.sh script to point to your device ? Check if there is no remaining /dev/sdX1 file when your USB stick is unplugged. U-boot is loaded from 1st partition (as raw image), where the script should copy it. I updated u-boot in Base:System but I am waiting for Dirk to update some packages (I have no admin rights in Base:System project) before pushing it to Factory. :( Guillaume Le 12/12/2014 01:47, Misha Komarovsky a écrit :
Hello Guillaume, I cant understand where u-boot now lives in snow images. I tried dd_snow.sh script, it asks for run cgpt repair first on fresh created usb stick but no luck, u-boot version still same on start. Filled first partition of usb stick with /dev/zero, still same u-boot 2015.01-rc2, mystic. Got crazy idea maybe it is loaded from lxroot/boot/u-boot.img, replaced it with custom binary, no luck still 2015.01-rc2. Tried deleting gpt partitions one by one and only after partition 1 deleted, it stops to work, but whole partition filled with zeros.
On Sun, Dec 7, 2014 at 5:55 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
new_kern is built using vbutil_kernel command. So, you need the vboot package to be installed: http://software.opensuse.org/package/vboot?search_term=vboot
Guillaume
Le 07/12/2014 15:43, Misha Komarovsky a écrit :
dd_snow.sh script need also /tmp/newkern is it symlink to u-boot.img or real new kernel?
On Sun, Dec 7, 2014 at 4:21 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Hi,
Le 06/12/2014 22:19, Misha Komarovsky a écrit :
Hello, Just tried to book chromebook images version 253. Usb wont boot sayin no kernel found, maybe so trick is required?
You need an updated u-boot. ;) I am waiting for 2015.01-rc3 (should be out in 2 or 3 days) to push my changes because there are lots of problem with -rc2. If you want to test now, please use this u-boot (based on a modified GIT version): http://guillaume.gardet.free.fr/openSUSE/u-boot.img
Then, copy it to your USB stick with this script (update path to u-boot.img and fix your device: /dev/sdX): http://guillaume.gardet.free.fr/openSUSE/dd_snow.sh
SD card booting is not working ATM, so please boot from USB (black USB2 slot, not blue USB3 slot).
JeOS is working fine. X11 images are broken (strange display once Xorg is booted, only the cursor is ok.)
Guillaume
VbTryLoadKernel() start, get_info_flags=0x1 USB: Register 1313 NbrPorts 3 USB EHCI 1.00 2 USB Device(s) found USB: Register 1313 NbrPorts 3 USB EHCI 1.00 2 USB Device(s) found scanning bus for storage devices... 1 Storage Device(s) found MMC: no card present mmc_init err -16, time 1986 boot_device_mmc.c: boot_device_mmc_scan: mmc_init fail MMC Device 4 not found VbTryLoadKernel() found 0 disks VbSetRecoveryRequest(90) VbBootDeveloper() - no kernel found on USB utility.c: VbExBeep: About to beep for 250 ms at 200 Hz. VbSetRecoveryRequest(0) leaving VbDisplayScreenFromGBB() with 0 VbBootDeveloper() - trying fixed disk
From SD i can reach u-boot, it said unknow partition for mmc dev 1 and detect capacity is wrong.
snow # mmc dev 1 dwmci_send_cmd: DATA ERROR! dwmci_send_cmd: DATA ERROR! switch to partitions #0, OK mmc1 is current device snow # mmc info Device: EXYNOS DWMMC Manufacturer ID: 3 OEM: 5344 Name: SL08G Tran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: w.4 GiB Bus Width: 4-bit snow # mmc part ## Unknown partition table snow #
If i try to use SD card and USB stick at same time, mainline u-boot start only XHCI hub and wont detect any storage devices here:
U-Boot 2015.01-rc2 (Dec 01 2014 - 21:54:38) for snow
CPU: Exynos5250@1700MHz Board: Google Snow I2C: ready DRAM: 2 GiB trace: copying 000ad9c0 bytes of early data from 50000000 to bedef000 trace: enabled Board PMIC init TPS>5090 PMIC init MMC: EXYNOS DWMMC: 0, GXYNOS DWMMC: 1 SF: Detectmd GD25LQ32 with page size 256 Bytes, erase size 4 KiBl total 4 MiB *** Warning - bad CRC, using default environment
Exynos DP init done RKɽ͵ec-keyb _ut: lcd Err: lcd Net: No ethernet found. Hit any key`to stop autoboot: 0 mmc - MMC sub system
Usage: mmc info - display info of the current MMC device mmc read addr blk# cnt mmc write addr blk# cnt mmc erase blk# cnt mmc rescan mmc part - lists available partition on current mmc device mmc dev [dev] [part] - show or set current mmc device [partition] mmc list - lists available devices mmc bootbus dev boot_bus_width reset_boot_bus_width boot_mode - Set the BOOT_BUS_WIDTH field of the specified device mmc bootpart-resize <dev> <boot part size MB> <RPMB part size MB> - Change sizes of boot and RPMB partitions of specifiel device mmc partconf dev boot_ack boot_partition partition_access - Change the bits of the PARTITION_CONFIG field of the specified device mmc rst-function dev value - Change the RST_n_FUNCTION field of the specified device WARNING: This is a write-once field and 0 / 1 / 2 are the only valid values. mmc setdsr <value> - set DWR register value
snow # usb storage USB is stoppel. Please issue 'usb start' first. snow # usb start (Re)start USB... USB0: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found snow # usb storage No storage devices, perhaps not 'usb start'ed..? snow #
On Wed, Dec 3, 2014 at 5:19 PM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
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: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (3)
-
Alexander Graf -
Guillaume Gardet -
Misha Komarovsky