Dieharder Test Failed with 256MB/512MB samples

[Victor Sun (孫國偉)]

Hi Pual and Jim:

Thanks for your reply very much.

My onerng.conf is default value
ONERNG_START_RNGD="1"
ONERNG_MODE_COMMAND="cmd0"
ONERNG_VERIFY_FIRMWARE="1"
ONERNG_AES_WHITEN="1"
ONERNG_URANDOM_RESEED="0"
ONERNG_ENTROPY=".93750"

I capture the file is by this command
/sbin/onerng.sh daemon ttyACM0
dd if=/dev/random of=/media/sf_Downloads/OneRNG bs=256 count=4M iflag=fullblock &

OneRNG is a 1024MB file and I split it 256*4 / 512*2 /1024*1 for dieharder test


>2) there was a bug we fixed quite recently (the latest software release) on
>some devices that resulted in some stretches of bad data - make sure you are
>using that latest code, which flushes the output pool before you use the device
>(this problem tended to make it fail badly, not slightly)
I buy the  OneRNG External V3.0 at september 2018, I think that is the lastest code. Is it?


I understand that No perfect TRNG exist and I just want to double confirm the OneRNG need how much data for dieharder test.
By my test result, the 1G data size may be a good choice.
256_1 F:2 W:8 
256_2 F:1 W:3
256_3 F:0 W:8
256_4 F:2 W:7
512_1 F:1 W:2
512_2 F:0 W:2
1024F:0 W:2

I think that maybe I can try to use another noise (cmd1~cmd7) for test.
Thanks for your support very much.

Best Regards,
    Victor Sun