| 1 |
On Thursday, 29 November 2018 18:36:11 GMT wabe wrote: |
| 2 |
> Daniel Frey <djqfrey@×××××.com> wrote: |
| 3 |
> > On 11/28/18 12:40 PM, Andrew Udvare wrote: |
| 4 |
> > > > >> On Nov 28, 2018, at 15:09, Daniel Frey <djqfrey@×××××.com> |
| 5 |
> > >> |
| 6 |
> > > > >> wrote: |
| 7 |
> > >> I've attached the two log files. |
| 8 |
> > >> |
| 9 |
> > > > I would like to see your syslog in both cases; dmesg output. |
| 10 |
> > > |
| 11 |
> > > I left the laptop sitting without logging in and when I came back |
| 12 |
> > > ten minutes later I saw that Xorg started. |
| 13 |
> > |
| 14 |
> > I found this in the log: |
| 15 |
> > |
| 16 |
> > [ 298.914537] random: crng init done |
| 17 |
> > [ 298.914542] random: 5 urandom warning(s) missed due to |
| 18 |
> > ratelimiting |
| 19 |
> > |
| 20 |
> > So about five minutes after boot the random number finished |
| 21 |
> > initializing and the Xorg started right after. |
| 22 |
> |
| 23 |
> You could install sys-apps/haveged. |
| 24 |
> |
| 25 |
> I really don't know if this will solve your actual problem, but maybe |
| 26 |
> it helps to speed up the random generation. |
| 27 |
|
| 28 |
If you'd read the part you snipped, you'd have seen that Dan had indeed tried |
| 29 |
haveged and it worked. |
| 30 |
|
| 31 |
Thank you, Dan. I hadn't heard of it, but your report immediately suggested I |
| 32 |
try it to reduce the wait while chronyd started, on two machines here. Worked |
| 33 |
like a charm: no waiting for enough entropy to be collected. |
| 34 |
|
| 35 |
-- |
| 36 |
Regards, |
| 37 |
Peter. |
Archives