On Tue, 2014-07-01 at 22:17 +0200, John Crispin wrote: > > On 01/07/2014 22:12, Ben Mulvihill wrote: > > Hello again, > > > > I have just tried sysupgradeNAND on the BTHOMEHUBV2B, and it fails > > with the following error: > > > > > > cat: can't open '/tmp/sysinfo/board_name': No such file or > > directory Unlocking kernel ... > > > > Writing from <stdin> to kernel ... [ ]tar: sysupgrade-/kernel: > > not found in archive > > > > > > Procd relies on /tmp/sysinfo/board_name being present, but I don't > > have a /tmp/sysinfo directory at all. Should I have? If so, should > > I add code to lib/functions/lantiq.sh to generate > > /tmp/sysinfo/board_name using lantiq_board_id() ? And if so, what > > do I hook it to to make sure it gets executed? > > > > Thanks, > > > > Ben > > > > > > ermm yes ... it should work the same as on imx6, ramips, ar71xx ... > > you can either do this tonight or i can do it in the morning. which > ever you prefer :) > Just did a quick test and the mechanism seems simple enough. But I'm afraid my day job and other commitments will keep me busy now until the weekend. I guess it depends whether you feel like taking time from the 101 other things you are working on simultaneously ;-) I'll send the UbinizeImage patch anyway now, with an extra line to generate the SysupgradeNAND tar files.
One unfortunate thing: lantiq has lantiq_board_id and lantiq_board_name, whereas the other architectures all have xxxxx_board_name and xxxxx_model, and for sysupgrade to work /temp/sysinfo/board_name will have to contain the value of lantiq_board_id, not, as would seem logical, lantiq_board_name. Confusing! _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
