# Core 169 - Entropy query

**URL:** <https://community.ipfire.org/t/core-169-entropy-query/8157>\
**Category:** Update Trouble\
**Created:** [28 June 2022 22:23 UTC](https://community.ipfire.org/t/core-169-entropy-query/8157 "2022-06-28T22:23:57Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![ag](https://community.ipfire.org/user_avatar/community.ipfire.org/ag/32/12124_2.png) [@ag](https://community.ipfire.org/u/ag)\
**Post date:** [28 June 2022 22:23 UTC](https://community.ipfire.org/t/core-169-entropy-query/8157/1 "2022-06-28T22:23:57Z")

</div>

I’ve upgraded to Core 169 today without any issues so far. I have noticed that the amount of Entropy has decreased quite a lot since the upgrade.

Is this expected or a bug?

 ![Screenshot from 2022-06-28 23-20-51](https://community.ipfire.org/uploads/default/original/2X/7/7a187643240c4487371caf683f14d84ad831fa7c.png)

---

<div class="post-metadata">

**Author:** ![wiztech](https://community.ipfire.org/user_avatar/community.ipfire.org/wiztech/32/15242_2.png) [@wiztech](https://community.ipfire.org/u/wiztech)\
**Post date:** [28 June 2022 22:52 UTC](https://community.ipfire.org/t/core-169-entropy-query/8157/2 "2022-06-28T22:52:30Z")

</div>

I had the same behavior (upgraded from Core168).  
 ![entropy169](https://community.ipfire.org/uploads/default/original/2X/6/65612ff6e02c6b5f0f992a9538c8a7b0dda4467b.png)

---

<div class="post-metadata">

**Author:** ![chrisk1](https://community.ipfire.org/user_avatar/community.ipfire.org/chrisk1/32/4235_2.png) [@chrisk1](https://community.ipfire.org/u/chrisk1)\
**Post date:** [29 June 2022 07:57 UTC](https://community.ipfire.org/t/core-169-entropy-query/8157/3 "2022-06-29T07:57:12Z")

</div>

The same here, too:

 ![grafik](https://community.ipfire.org/uploads/default/original/2X/8/8dcdf0ece5d80fef77705c1f62b01f7dab7c3d4f.png)

---

<div class="post-metadata">

**Author:** ![steph78630](https://community.ipfire.org/user_avatar/community.ipfire.org/steph78630/32/8251_2.png) [@steph78630](https://community.ipfire.org/u/steph78630)\
**Post date:** [29 June 2022 12:17 UTC](https://community.ipfire.org/t/core-169-entropy-query/8157/4 "2022-06-29T12:17:38Z")

</div>

Hi, same here ☹

---

<div class="post-metadata">

**Author:** ![bonnietwin](https://community.ipfire.org/user_avatar/community.ipfire.org/bonnietwin/32/12350_2.png) [@bonnietwin](https://community.ipfire.org/u/bonnietwin)\
**Post date:** [29 June 2022 12:26 UTC](https://community.ipfire.org/t/core-169-entropy-query/8157/5 "2022-06-29T12:26:52Z")

</div>

I think it might be worth someone raising a bug on it.

[https://wiki.ipfire.org/devel/bugzilla](https://wiki.ipfire.org/devel/bugzilla)

[https://bugzilla.ipfire.org/](https://bugzilla.ipfire.org/)

The IPFire people email address and password also act as your credentials to login to bugzilla.

Put CU169 Testing in the title so it is easily spotted.

---

<div class="post-metadata">

**Author:** ![chrisk1](https://community.ipfire.org/user_avatar/community.ipfire.org/chrisk1/32/4235_2.png) [@chrisk1](https://community.ipfire.org/u/chrisk1)\
**Post date:** [29 June 2022 13:32 UTC](https://community.ipfire.org/t/core-169-entropy-query/8157/6 "2022-06-29T13:32:52Z")

</div>

[https://bugzilla.ipfire.org/show\_bug.cgi?id=12893](https://bugzilla.ipfire.org/show_bug.cgi?id=12893)

I’v updated the bug report with some analysis I did and links I found in the web about this topic.

---

<div class="post-metadata">

**Author:** ![pmueller](https://community.ipfire.org/user_avatar/community.ipfire.org/pmueller/32/9019_2.png) [@pmueller](https://community.ipfire.org/u/pmueller)\
**Post date:** [29 June 2022 19:31 UTC](https://community.ipfire.org/t/core-169-entropy-query/8157/7 "2022-06-29T19:31:04Z")

</div>

Hi,

thank you all for reporting this change.

As [already stated in bug #12893](https://bugzilla.ipfire.org/show_bug.cgi?id=12893#c4) - thanks, @chrisk1 -, this change has been intentionally conducted by the kernel developers. It is nothing to worry about (quite the opposite, actually), and at IPFire, there is nothing we can do.

Since the entropy graph does not display any valuable information with this new kernel (it always shows 256 bytes of entropy are available), I will remove it entirely, to avoid additional confusion.

Thanks, and best regards,  
Peter Müller

---

<div class="post-metadata">

**Author:** ![ts1612](https://community.ipfire.org/user_avatar/community.ipfire.org/ts1612/32/8370_2.png) [@ts1612](https://community.ipfire.org/u/ts1612)\
**Post date:** [17 August 2022 15:57 UTC](https://community.ipfire.org/t/core-169-entropy-query/8157/8 "2022-08-17T15:57:34Z")

</div>

> [@pmueller](#):
>
> Since the entropy graph does not display any valuable information with this new kernel (it always shows 256 bytes of entropy are available), I will remove it entirely, to avoid additional confusion.

The only valuable information on that page was if the rngd deamon was running or not. Could/Should this be added to status-\>services?

---

<div class="post-metadata">

**Author:** ![redneckmother](https://community.ipfire.org/user_avatar/community.ipfire.org/redneckmother/32/12675_2.png) [@redneckmother](https://community.ipfire.org/u/redneckmother)\
**Post date:** [17 August 2022 19:29 UTC](https://community.ipfire.org/t/core-169-entropy-query/8157/9 "2022-08-17T19:29:13Z")

</div>

See [11546 – display RNGD status in WebUI process list, too](https://bugzilla.ipfire.org/show_bug.cgi?id=11546)
