| View previous topic :: View next topic |
| Author |
Message |
kimux
n00b
Joined: 25 Mar 2013
Posts: 17
|
|
| Back to top |
|
 |
figueroa
Advocate
Joined: 14 Aug 2005
Posts: 2965
Location: Edge of marsh USA
|
 Posted: Mon Feb 19, 2024 5:02 am Post subject: |
 |
|
Suggest an Internet search.
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
| Back to top |
|
|
kimux
n00b
Joined: 25 Mar 2013
Posts: 17
|
| Posted: Mon Feb 19, 2024 5:17 am Post subject: |
|
|
| figueroa wrote: | | Suggest an Internet search. |
I've tried searching, but haven't found a solution
I haven't used gentoo in about a few years.
I just switched to gentoo from arch a few days ago because I want to use openrc again |
|
| Back to top |
|
|
figueroa
Advocate
Joined: 14 Aug 2005
Posts: 2965
Location: Edge of marsh USA
|
| Posted: Mon Feb 19, 2024 6:12 am Post subject: |
|
|
Search on the following:
| Code: | | Unable to determine pool size |
I got many good hits.
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
| Back to top |
|
|
kimux
n00b
Joined: 25 Mar 2013
Posts: 17
|
| Posted: Mon Feb 19, 2024 7:34 am Post subject: |
|
|
| figueroa wrote: | Search on the following:
| Code: | | Unable to determine pool size |
I got many good hits. |
If I could find the solution myself I wouldn't be asking here...
Actually, I have been looking for a solution to this problem since February 10th  |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54330
Location: 56N 3W
|
| Posted: Mon Feb 19, 2024 8:57 am Post subject: |
|
|
kimux,
You need to provide some context, not just the warning message.
Make friends with wgetpaste and use it to share you dmesg output. That's probably where it from.
The output ofmay be useful too.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 21724
|
| Posted: Mon Feb 19, 2024 1:58 pm Post subject: |
|
|
| figueroa wrote: | Search on the following: | Code: | | Unable to determine pool size |
I got many good hits. |
For the benefit of OP, whose preferred search engine apparently is not returning these hits (or who receives these hits, but does not consider them good), could you provide a few examples? This may also benefit future readers, if those good hits fall out of the search first page, but remain applicable to the problem. |
|
| Back to top |
|
|
figueroa
Advocate
Joined: 14 Aug 2005
Posts: 2965
Location: Edge of marsh USA
|
| Posted: Mon Feb 19, 2024 4:44 pm Post subject: |
|
|
Fair enough, Hu. There was little enough to go on, so I was directing the OP back on his own resources, even though I was interested in the outcome.
A DuckDuckGo search for seedrng Unable to determine pool size (added seedrng to avoid swimming pool hits):
The first hit returned from DuckDuckGo is this thread:
Second hit is where OP cross-posted on reddit, the source of the bootup snapshot:
https://www.reddit.com/r/Gentoo/comments/1arx9t2/seedrng_unable_to_determine_pool_size/
There were good ideas in that thread but little to indicate the user taking most of them seriously.
Idea, for kimux: Boot from the gentoo-kernel-bin as a trial to see if you continue to get the same or similar boot-up messages.
For what it's worth, here are my own .config settings containing RANDOM:
| Code: | $ grep RANDOM .config
CONFIG_RANDOMIZE_BASE=y
CONFIG_RANDOMIZE_MEMORY=y
CONFIG_RANDOMIZE_MEMORY_PHYSICAL_PADDING=0x0
CONFIG_ARCH_HAS_ELF_RANDOMIZE=y
CONFIG_HAVE_ARCH_RANDOMIZE_KSTACK_OFFSET=y
CONFIG_RANDOMIZE_KSTACK_OFFSET=y
# CONFIG_RANDOMIZE_KSTACK_OFFSET_DEFAULT is not set
CONFIG_SLAB_FREELIST_RANDOM=y
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_TIMERIOMEM=y
CONFIG_HW_RANDOM_INTEL=y
# CONFIG_HW_RANDOM_AMD is not set
# CONFIG_HW_RANDOM_BA431 is not set
# CONFIG_HW_RANDOM_VIA is not set
# CONFIG_HW_RANDOM_XIPHERA is not set
# CONFIG_RANDOM_TRUST_CPU is not set
# CONFIG_RANDOM_TRUST_BOOTLOADER is not set
# CONFIG_RANDOM32_SELFTEST is not set
# CONFIG_WARN_ALL_UNSEEDED_RANDOM is not set |
I did not find related output in /var/log/dmesg.
I did find some in my boot log. I narrowed them down to a time 12:56:14 and read that from the most current boot log. Here is the relevant snippet.
| Code: | # less boot-20240212.gz | grep 12:56:14
Sun Feb 11 12:56:14 2024: * Saving key mapping ...
Sun Feb 11 12:56:14 2024: [ ok ]
Sun Feb 11 12:56:14 2024: * Saving terminal encoding ...
Sun Feb 11 12:56:14 2024: [ ok ]
Sun Feb 11 12:56:14 2024: * Seeding random number generator ...
Sun Feb 11 12:56:14 2024: * Seeding 256 bits and crediting
Sun Feb 11 12:56:14 2024: * Saving 256 bits of creditable seed for next boot
Sun Feb 11 12:56:14 2024: [ ok ]
Sun Feb 11 12:56:14 2024: * Create Volatile Files and Directories ...
Sun Feb 11 12:56:14 2024: [ ok ]
Sun Feb 11 12:56:14 2024: INIT: Entering runlevel: 3
Sun Feb 11 12:56:14 2024: * WARNING: clock skew detected!
Sun Feb 11 12:56:14 2024: * Starting metalog ...
Sun Feb 11 12:56:14 2024: [ ok ] |
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
| Back to top |
|
|
kimux
n00b
Joined: 25 Mar 2013
Posts: 17
|
| Posted: Tue Feb 20, 2024 12:30 am Post subject: |
|
|
| Hu wrote: | | figueroa wrote: | Search on the following: | Code: | | Unable to determine pool size |
I got many good hits. |
For the benefit of OP, whose preferred search engine apparently is not returning these hits (or who receives these hits, but does not consider them good), could you provide a few examples? This may also benefit future readers, if those good hits fall out of the search first page, but remain applicable to the problem. |
| figueroa wrote: | Fair enough, Hu. There was little enough to go on, so I was directing the OP back on his own resources, even though I was interested in the outcome.
A DuckDuckGo search for seedrng Unable to determine pool size (added seedrng to avoid swimming pool hits):
The first hit returned from DuckDuckGo is this thread:
Second hit is where OP cross-posted on reddit, the source of the bootup snapshot:
https://www.reddit.com/r/Gentoo/comments/1arx9t2/seedrng_unable_to_determine_pool_size/
There were good ideas in that thread but little to indicate the user taking most of them seriously.
Idea, for kimux: Boot from the gentoo-kernel-bin as a trial to see if you continue to get the same or similar boot-up messages.
For what it's worth, here are my own .config settings containing RANDOM:
| Code: | $ grep RANDOM .config
CONFIG_RANDOMIZE_BASE=y
CONFIG_RANDOMIZE_MEMORY=y
CONFIG_RANDOMIZE_MEMORY_PHYSICAL_PADDING=0x0
CONFIG_ARCH_HAS_ELF_RANDOMIZE=y
CONFIG_HAVE_ARCH_RANDOMIZE_KSTACK_OFFSET=y
CONFIG_RANDOMIZE_KSTACK_OFFSET=y
# CONFIG_RANDOMIZE_KSTACK_OFFSET_DEFAULT is not set
CONFIG_SLAB_FREELIST_RANDOM=y
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_TIMERIOMEM=y
CONFIG_HW_RANDOM_INTEL=y
# CONFIG_HW_RANDOM_AMD is not set
# CONFIG_HW_RANDOM_BA431 is not set
# CONFIG_HW_RANDOM_VIA is not set
# CONFIG_HW_RANDOM_XIPHERA is not set
# CONFIG_RANDOM_TRUST_CPU is not set
# CONFIG_RANDOM_TRUST_BOOTLOADER is not set
# CONFIG_RANDOM32_SELFTEST is not set
# CONFIG_WARN_ALL_UNSEEDED_RANDOM is not set |
I did not find related output in /var/log/dmesg.
I did find some in my boot log. I narrowed them down to a time 12:56:14 and read that from the most current boot log. Here is the relevant snippet.
| Code: | # less boot-20240212.gz | grep 12:56:14
Sun Feb 11 12:56:14 2024: * Saving key mapping ...
Sun Feb 11 12:56:14 2024: [ ok ]
Sun Feb 11 12:56:14 2024: * Saving terminal encoding ...
Sun Feb 11 12:56:14 2024: [ ok ]
Sun Feb 11 12:56:14 2024: * Seeding random number generator ...
Sun Feb 11 12:56:14 2024: * Seeding 256 bits and crediting
Sun Feb 11 12:56:14 2024: * Saving 256 bits of creditable seed for next boot
Sun Feb 11 12:56:14 2024: [ ok ]
Sun Feb 11 12:56:14 2024: * Create Volatile Files and Directories ...
Sun Feb 11 12:56:14 2024: [ ok ]
Sun Feb 11 12:56:14 2024: INIT: Entering runlevel: 3
Sun Feb 11 12:56:14 2024: * WARNING: clock skew detected!
Sun Feb 11 12:56:14 2024: * Starting metalog ...
Sun Feb 11 12:56:14 2024: [ ok ] |
|
I made a stupid mistake.
Because CONFIG_SYSFS is not turned on in my kernel configuration file.
Therefore there is no sys directory in /proc.
Everything works fine now. |
|
| Back to top |
|
|
figueroa
Advocate
Joined: 14 Aug 2005
Posts: 2965
Location: Edge of marsh USA
|
| Posted: Tue Feb 20, 2024 2:17 am Post subject: |
|
|
| kimux wrote: |
...
Because CONFIG_SYSFS is not turned on in my kernel configuration file.
Therefore there is no sys directory in /proc.
Everything works fine now. |
Confession is good for the soul (and the operating system). You were deep in the woods. Do you recall what led to that problem? Best of luck going forward.
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
| Back to top |
|
|
kimux
n00b
Joined: 25 Mar 2013
Posts: 17
|
| Posted: Tue Feb 20, 2024 4:24 am Post subject: |
|
|
| figueroa wrote: |
Confession is good for the soul (and the operating system). You were deep in the woods. Do you recall what led to that problem? Best of luck going forward. |
Maybe I accidentally pressed the space key when browsing the kernel configuration file, but I didn’t notice it
I hope I will not make similar stupid mistakes in the future
Anyway, it is a good thing to resolve the problem |
|
| Back to top |
|
|
|
Installing Gentoo
