Upgrade to F36, trouble with jitter entropy so rngd init fails

Ask Fedora Ask in English
1

I know I have an old CPU (AMD Phenom 9650 Quad-Core Processor) but things were fine on F34. Just requesting suggestions on how to fix this.
Thanks,
Ralph

10:27 AM rngd.service: Consumed 17.883s CPU time. systemd
10:27 AM rngd.service: Failed with result ‘exit-code’. systemd
10:27 AM rngd.service: Main process exited, code=exited, status=1/FAILURE systemd
10:27 AM Maybe RNG device modules are not loaded rngd
10:27 AM Can’t open any entropy source rngd
10:27 AM [rtlsdr]: Initialization Failed rngd
10:27 AM [jitter]: Initialization Failed rngd
10:27 AM [jitter]: Unable to obtain AES key, disabling JITTER source rngd
10:27 AM [jitter]: Initializing AES buffer rngd
10:27 AM [jitter]: JITTER timeout set to 5 sec rngd

2

Hm. I’m seeing something similar, perhaps-not-coincidentally also on an older AMD CPU. (But mine is MUUUCH older: a ca. 2008 AMD Athlon™ 64 X2 Dual Core Processor 4800+.)

I wonder if the failures are a consequence of this mid-2020 change? Which based on the PR title sounds like it may have fixed a bug that was causing false successful inits. (IOW, things may not have been working under F34 either. A bug may have just been hiding the failures.) I haven’t interpreted that PR enough to be sure I really grok it, though.