mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Oleksij Rempel <linux@rempel-privat.de>
To: Holger Schurig <holgerschurig@gmail.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: problems with ext4
Date: Wed, 15 Feb 2017 14:39:02 +0100	[thread overview]
Message-ID: <e0397e97-ddd8-1acc-d139-bf5397c3046a@rempel-privat.de> (raw)
In-Reply-To: <CAOpc7mFtB7-Qf4pNSCZsYofdAyj=TPRG17J0=rdi3YEBm+qyRg@mail.gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 752 bytes --]

Am 15.02.2017 um 13:31 schrieb Holger Schurig:
> For what it's worth, my kernel is also in an ext4 partition (on an
> SDCARD or eMMC).
> 
> I format them with "mkfs.ext4 -q -F -D -j /dev/XXXX"
> 
> Inside the partition, I use /boot/vmlinuz as a symlink to the real file
> which is in the same directory.
> ​
> 
> I'm however on an older version of barebox, 2016.07.0

I reformatted boot partition back to ext4. Now the problem is reproducible.
Partition image can be found here
https://github.com/olerem/beagleboneblack/blob/master/boot.tar.bz2

Decompressed it should be:
md5sum 2f3474d39f1d7893e310b55ea57d87bd

the /boot/dtb symlink can't be resolved by barebox. And /boot/dtbs
folder is broken.


-- 
Regards,
Oleksij


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2017-02-15 13:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14 14:22 Oleksij Rempel
2017-02-14 14:46 ` Oleksij Rempel
2017-02-15  7:03 ` Sascha Hauer
2017-02-15  7:22   ` Oleksij Rempel
     [not found]     ` <CAOpc7mFtB7-Qf4pNSCZsYofdAyj=TPRG17J0=rdi3YEBm+qyRg@mail.gmail.com>
2017-02-15 13:39       ` Oleksij Rempel [this message]
2017-02-15 13:46         ` Oleksij Rempel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e0397e97-ddd8-1acc-d139-bf5397c3046a@rempel-privat.de \
    --to=linux@rempel-privat.de \
    --cc=barebox@lists.infradead.org \
    --cc=holgerschurig@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox