Description of problem:
With kernel 3.8, the kernel can source entropy from the TPM chips on Intel platforms. This entropy can be read by rngd and fed to the kernel's entropy pool. It could also fetch entropy from the RDRAND instruction, if available.
rngd should be started by default to take advantage of such newer hardware features.
We will probably want a udev rule to only start if /dev/hwrng exists. That will still require a bug against systemd to allow autostarting though:
This is also useful for virtual machines, as QEMU now has a hwrng device, virtio-rng. Linux has had support for virtio-rng for quite a while. virtio-rng is hooked up to the hwrng interface in the kernel, and is available via /dev/hwrng.
The TPM input, as well as RDRAND input are from different sources (not /dev/hwrng).
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
Seems to work if you start it manually. I think it should have a rule in /use/lib/systemd/system/rngd.service saying it should start after a certain service has started. I think it tries to start to early in the startup sequence.
It seems to work if you start it up manually by typing sudo systemctl start rngd
Same for fedora 20.
For me it does not start, even manually. I tried stoping and starting rngd, and with restart. It keeps repeating the same messages on system log:
Unable to open file: /dev/tpm0
can't open any entropy source
Maybe RNG device modules are not loaded
I am using Fedora 20, with kernel 3.16.7-200.fc20.x86_64.
rngd has been enabled by default for a while.
@Henderb: if rngd does not detect your hardware, please file a separate bug, describing the rng hardware that you have, and including rngd output.
*** This bug has been marked as a duplicate of bug 857765 ***