Re: [opensuse-arm] JeOS-beaglebone doesn't boot (uboot 2016.01-rc1)

2015-12-12 Thread Matwey V. Kornilov 
2015-12-11 16:43 GMT+03:00 Guillaume Gardet :
>
>
> Le 11/12/2015 10:46, Matwey V. Kornilov a écrit :
>>
>> 2015-12-11 12:42 GMT+03:00 Guillaume Gardet :
>>>
>>>
>>> Le 11/12/2015 10:10, Matwey V. Kornilov a écrit :

 2015-12-11 12:04 GMT+03:00 Guillaume Gardet :
>
> 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 +)
>>
>>   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: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?
>>>
>>>
>>> Maybe you hit a key on your keyboard stopping autoboot?
>>>
>>> Is the autoboot count down shown?
>>
>> No, I've tried several times. It is just waiting for a command in prompt.
>
>
> Could you try 2016.01-rc2 available at:
> home:Guillaume_G:branches:Base:System
>
> If you still have this problem, please report it upstream.

I've found the problem and sent the patch to upstream.
https://patchwork.ozlabs.org/patch/555979/
Moreover, I've found another problem with 2016.01-rc2:
http://lists.denx.de/pipermail/u-boot/2015-December/237604.html
u-boot is full of bugs! :)

>
>>
>> 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.
>>>
>>>
>>> Standard release (13.2 or 13.1). ;)
>>>
>> Which is not there anymore, leap doesn't support armv7 and tumbleweed
>> is supplied with rc of u-boot :)
>
>
> Yes, Leap without 32 bits support (both ARM and x86) is very annoying... :(

We should do something with it.

>
>
> Guillaume
>



-- 
With best regards,
Matwey V. Kornilov
http://blog.matwey.name
xmpp://0x2...@jabber.ru
--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] JeOS-beaglebone doesn't boot (uboot 2016.01-rc1)

2015-12-11 Thread Matwey V. Kornilov 
2015-12-11 12:42 GMT+03:00 Guillaume Gardet :
>
>
> Le 11/12/2015 10:10, Matwey V. Kornilov a écrit :
>>
>> 2015-12-11 12:04 GMT+03:00 Guillaume Gardet :
>>>
>>> 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 +)

  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: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?
>
>
> Maybe you hit a key on your keyboard stopping autoboot?
>
> Is the autoboot count down shown?

No, I've tried several times. It is just waiting for a command in prompt.

>
>>
 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.
>
>
> Standard release (13.2 or 13.1). ;)
>

Which is not there anymore, leap doesn't support armv7 and tumbleweed
is supplied with rc of u-boot :)

>
> Guillaume
>



-- 
With best regards,
Matwey V. Kornilov
http://blog.matwey.name
xmpp://0x2...@jabber.ru
--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Re: [opensuse-arm] JeOS-beaglebone doesn't boot (uboot 2016.01-rc1)

2015-12-11 Thread Guillaume Gardet 



Le 11/12/2015 10:46, Matwey V. Kornilov a écrit :

2015-12-11 12:42 GMT+03:00 Guillaume Gardet :


Le 11/12/2015 10:10, Matwey V. Kornilov a écrit :

2015-12-11 12:04 GMT+03:00 Guillaume Gardet :

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 +)

  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: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?


Maybe you hit a key on your keyboard stopping autoboot?

Is the autoboot count down shown?

No, I've tried several times. It is just waiting for a command in prompt.


Could you try 2016.01-rc2 available at: home:Guillaume_G:branches:Base:System

If you still have this problem, please report it upstream.




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.


Standard release (13.2 or 13.1). ;)


Which is not there anymore, leap doesn't support armv7 and tumbleweed
is supplied with rc of u-boot :)


Yes, Leap without 32 bits support (both ARM and x86) is very annoying... :(


Guillaume

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