On Sun, 2017-08-13 at 11:56 +0200, Robert Schlabbach wrote: > Von: "Ian Campbell" <i...@debian.org> > > There is one other option, which is to ask people to adjust their > u- > > boot boot scripts as Robert has done, however the QNAP systems are > > often run headless and without access to the serial console (it's a > > special cable which only a minority of users will have access to) > so > > that really is a last resort. > > Note that it is possible to modify the u-boot environment without the > serial console, using the "fw_setenv" command in a running debian > system.
Given a correct /etc/fw_env.config, yes. I think the TS-xxx ones are pretty well known although I don't think we ship any anywhere and we certainly don't install one automatically. > So one possibility would indeed be to modify the flash-kernel scripts > to use fw_printenv, "parse" the environment to detect affected systems > and, if needed, use fw_setenv to make the necessary changes. > > That's not really a "pretty" solution, though, and any bugs in that > function could easily brick the device. Then again, there have been > "bricking" changes in the past, so it wouldn't be an entirely new > risk ;-) Do you know if this particular brickage is undone by the recovery procedure (http://www.cyrius.com/debian/kirkwood/qnap/ts-219/recovery/) . I think one of the mtd devices which is backed up is the boot loader config (mtd4) so I think the answer must be yes, but I've not tried it. Ian. > At least making the change _without_ flashing a new kernel should not > be harmful as the moved initramfs location appears to be backwards > compatible (though I've tried only 4.9 in practice). > > Best regards, > -Robert >
