On 24 October 2016 at 18:43, <p.wa...@gmx.at> wrote: >> I started working on this today, I reproduce see the issue during a >> lot of tests until it magically disappeared. Then LEDE started booting >> on my unit with kernel 4.4. > > Oh - that rings a bell. > May I point you to a discussion we had earlier this year? > http://lists.infradead.org/pipermail/lede-dev/2016-May/000980.html > > I had this issue on all my WRT54GLs: > trunk images stopped booting at "Starting program at 0x80001000". > However, if I compiled the images myself (with the exact same configuration > as the buildbot), the images would boot fine. > I later checked again: buildbot's images did not boot. > (It was kernel 4.1 back then, but it's the exact same behaviour as you > describe > in the commit message) > Additionally builtbot's images worked out-of-the-box on an ASUS WL500gP V2.
It seems I'm experiencing the same crazy problem. Local builds work for me (as explained in commit message), but image from buildbot (https://downloads.lede-project.org/snapshots/targets/brcm47xx/legacy/) doesn't boot. This is some totally crazy thing :| -- Rafał _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
