[onerng talk] Firmware verification failed, on move to other system
James Cameron
quozl at laptop.org
Sun Apr 19 21:46:01 BST 2015
On Fri, Apr 17, 2015 at 10:54:45PM +1200, Paul Campbell wrote:
> On Fri, 17 Apr 2015 20:48:46 James Cameron wrote:
> > Apr 17 20:32:03 sys2 OneRNG: firmware verification failed: Bad image
>
> we think this is a python version thing I'm going to try and get a
> new version of the support code out this weekend - watch this space
Installed 3.2, but problem continues. "Bad image".
4aa006e7c7c44a493cd092773241e15c /sbin/onerng_verify.py
/usr/bin/python version is 2.7.6
After changing the code to report the length values,
{{{
failure("Bad image (expected %d but got %d)" % (length, len(c)))
}}}
There are a varying number of bytes received.
Apr 20 06:34:51 tv OneRNG: firmware verification failed: Bad image (expected 262144 but got 128182)
Apr 20 06:38:45 tv OneRNG: firmware verification failed: Bad image (expected 262144 but got 132613)
Apr 20 06:39:56 tv OneRNG: firmware verification failed: Bad image (expected 262144 but got 130920)
After changing the code to delay 200ms and try a continuation read,
{{{
if len(c) != length:
syslog.syslog(syslog.LOG_ERR, "short read (expected %d but got %d)" % (length, len(c)))
time.sleep(0.2)
c += f.read(length - len(c))
if len(c) != length:
failure("Bad image (expected %d but got %d)" % (length, len(c)))
}}}
There's no sign of those bytes arriving later.
Apr 20 06:43:31 tv OneRNG: short read (expected 262144 but got 117747)
Apr 20 06:43:31 tv OneRNG: firmware verification failed: Bad image (expected 262144 but got 117747)
Apr 20 06:43:39 tv OneRNG: short read (expected 262144 but got 128944)
Apr 20 06:43:39 tv OneRNG: firmware verification failed: Bad image (expected 262144 but got 128944)
Apr 20 06:43:46 tv OneRNG: short read (expected 262144 but got 139810)
Apr 20 06:43:46 tv OneRNG: firmware verification failed: Bad image (expected 262144 but got 139810)
Hope that helps. Let me know if you need any further data.
--
James Cameron
http://quozl.linux.org.au/
More information about the Discuss
mailing list