On 30 June 2016 at 19:13, Robert Nelson <robertcnel...@gmail.com> wrote:
> On Wed, Jun 29, 2016 at 5:30 AM, Michal Suchanek <hramr...@gmail.com> wrote:
>> On 29 June 2016 at 10:45, Karsten Merker <mer...@debian.org> wrote:
>>> On Wed, Jun 29, 2016 at 09:30:33AM +0200, Michal Suchanek wrote:
>>>> I tried loading system with recent u-boot but it does not work.
>>>> Trying some ext4ls shows there is some problem accessing the filesystem.
>>>> Not sure if this should be attributed to the ext driver or to the mmc
>>>> driver or something else entirely.
>>> I haven't tested that myself, but I have seen reports on other
>>> platforms that the u-boot ext4 driver has problems with ext4
>>> filesystems which use the "flex_bg" filesystem feature, as that
>>> causes certain changes to the on-disk layout compared to ext4
>>> without this feature. From what people have reported, it appears
>>> that "flex_bg" is enabled by default on ext4 filesystems created
>>> with a recent mkfs.ext4 version.
>> Reformatting without flex_bg does not seem to have any effect.
>> However, ls seems to give some random stuff for directories other than
>> / so some similar remapping feature could cause this.
> it's csum/64bit, disable it:
> mkfs.ext4 -O ^metadata_csum,^64bit
This works for me.
If a fix is too difficult to roll out immediately at least an error
message when trying
to mount filesystem with unsupported features would be nice.
Cool cooler btw
U-Boot mailing list