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