[onerng talk] Firmware corrupted

[tmp543901 at buckeye-express.com]

> On 2020-06-05 7:29 am, Paul Campbell wrote:
> 
> I think that this is likely a known issue with the python script that checks 
> the signature on the firmware ... the recent switch to python3 as a default is 
> a problem ....

I haven't experienced a validation issue for 2+ years on my main systems
(my Debian9 & Devuan are unaffected) but had issues with CentOS6 years
ago and also when I tried debugging an issue on Mint19.1 for another
user last year.  I know it's not the reason for all failures, but I did
experience incomplete firmware extraction serveral times from dd
terminating prematurely.  Never could figure out exactly why but
someting was glitchy.  At the time I played around and modified the
onerng python script to do the fw extraction using pyserial instead of
using dd in bash and it worked great.  It can be done without pyserial,
and I'm normally very anti-dependency, but pyserial does all the heavy
lifting and really made fw extraction a breeze and reliable (at least
froim my limited testing).  IMHO, I think it would be better to do both
the fw extraction and validation in the python script.  Not sure if I
still have the code but honestly I don't think it was more than a few
extra lines.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ourshack.com/pipermail/discuss/attachments/20200605/623d55f7/attachment.html>