Le 11/12/2015 10:10, Matwey V. Kornilov a écrit :
2015-12-11 12:04 GMT+03:00 Guillaume Gardet <guillaume.gardet@free.fr>:
Hi,
Le 11/12/2015 09:55, Matwey V. Kornilov a écrit :
Hello,
I am using openSUSE-Tumbleweed-ARM-JeOS-beaglebone.armv7l-1.12.1-Build350.1.raw from openSUSE:Factory:ARM and see the following:
U-Boot SPL 2016.01-rc1 (Dec 01 2015 - 16:30:32) bad magic bad magic spl_register_fat_device: fat register err - -1 spl_register_fat_device: fat register err - -1 spl_load_image_fat: error reading image u-boot.img, err - -1 spl: ext4fs_open failed spl: ext4fs_open failed spl_load_image_ext: error reading image uImage, err - -1
U-Boot 2016.01-rc1 (Dec 01 2015 - 16:30:32 +0000)
Watchdog enabled I2C: ready DRAM: 512 MiB NAND: 0 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 *** Error - No Valid Environment Area found *** Warning - bad CRC, using default environment
Net: <ethaddr> not set. Validating first E-fuse MAC cpsw, usb_ether =>
Something is probably wrong.
What happen if you type 'boot' command? It boots! Magic! Thank you, but why it doesn't happen automatically?
p.s. I am not sure that it is related to u-boot, but is there any reason why rc-s of u-boot appear in Factory? Would it be better to test them on kittens instead of users?
Most of the time, I test u-boot on boards available to me when I update it. But, I do not have all boards supported by openSUSE, so it may break some boards, but the sooner it is detected, the better it is! ;)
It makes sense. Still would be great to have another JeOS which is guaranteed working out of the box.
Guillaume
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org