[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#997954: marked as done (linux: Missing HW RNG on Pine64 on bullseye and bookworm)

Your message dated Thu, 20 Feb 2025 14:02:25 +0100 (CET)
with message-id <20250220130225.4726CBE2EE7@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #997954,
regarding linux: Missing HW RNG on Pine64 on bullseye and bookworm
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
997954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997954
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: linux
Severity: normal

Dear Maintainer,

Installing bullseye or bookworm on a Pine64 [0] results in a
system with very low entropy. After some light usage over the
serial console I see:

```
cat /proc/sys/kernel/random/entropy_avail
3
```

This device has a hardware RNG which could be used with rng-tools [1]
to increase entropy but the kernel configuration has it disabled.

Could the `CRYPTO_DEV_SUN8I_CE_PRNG` option be enabled? Then all
users of the A64 SOC could have access to more entropy. A practical
imediate impact is that boot times will decrease for users of
systemd since the systemd-random-seed.service [2] will be able
to gather entropy much faster. Currently on a Pine64
`systemd-analyze blame` shows the random seed service taking 3
seconds on boot.


[0]: https://wiki.debian.org/InstallingDebianOn/PINE64/PINEA64
[1]: https://packages.debian.org/bullseye/rng-tools5
[2]: https://manpages.debian.org/bullseye/systemd/systemd-random-seed.service.8.en.html

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 11.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-9-amd64 (SMP w/1 CPU thread)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: