Takes too long for any browser to load at the first time
I have Gentoo(4.14.83) with dwm as my DE.
I've tried about 6 browsers and every one of them, as I start it right after the boot up, may load only after 30 seconds and up to 100 seconds.
I use Google Chrome. So if I start it from the terminal, it outputs
getrandom indicates that the entropy pool has not been initialized
linux chrome browser
asked Jan 8 at 14:23
DaniDani
364
add a comment |
I have Gentoo(4.14.83) with dwm as my DE.
I've tried about 6 browsers and every one of them, as I start it right after the boot up, may load only after 30 seconds and up to 100 seconds.
I use Google Chrome. So if I start it from the terminal, it outputs
getrandom indicates that the entropy pool has not been initialized
linux chrome browser
asked Jan 8 at 14:23
DaniDani
364
add a comment |
I have Gentoo(4.14.83) with dwm as my DE.
I've tried about 6 browsers and every one of them, as I start it right after the boot up, may load only after 30 seconds and up to 100 seconds.
I use Google Chrome. So if I start it from the terminal, it outputs
getrandom indicates that the entropy pool has not been initialized
linux chrome browser
asked Jan 8 at 14:23
DaniDani
364
I have Gentoo(4.14.83) with dwm as my DE.
I've tried about 6 browsers and every one of them, as I start it right after the boot up, may load only after 30 seconds and up to 100 seconds.
I use Google Chrome. So if I start it from the terminal, it outputs
getrandom indicates that the entropy pool has not been initialized
linux chrome browser
linux chrome browser
asked Jan 8 at 14:23
DaniDani
364
asked Jan 8 at 14:23
DaniDani
364
asked Jan 8 at 14:23
DaniDani
364
asked Jan 8 at 14:23
DaniDani
364
asked Jan 8 at 14:23
DaniDani
364
364
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Browsers mainly use /dev/random(random), as /dev/urandom(pseudorandom) isn't considered to be trusted(but as man page random(4) points out, it shouldn't be so).
As it turns out, my laptop has neither TPM nor DRNG to efficiently generate random numbers, causing anyone who needs random numbers right after the boot to wait until enough entropy has been gathered. Thus, it has to generate random numbers from things like keyboard, mouse, fan, etc. Meaning you can speed up this process of entropy(random numbers) generation by moving your mouse or typing on the keyboard. It's possible to check available entropy with cat /proc/sys/kernel/random/entropy_avail.
If Chrome just used urandom instead of random there would be no such problem. But it can be easily fixed by feeding random from urandom:
1) Install rng-tools
2) Run sudo rngd -o /dev/random -r /dev/urandom before you start your browser, say, in ~/.xinitrc
answered Jan 8 at 14:46
DaniDani
364
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493242%2ftakes-too-long-for-any-browser-to-load-at-the-first-time%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Browsers mainly use /dev/random(random), as /dev/urandom(pseudorandom) isn't considered to be trusted(but as man page random(4) points out, it shouldn't be so).
As it turns out, my laptop has neither TPM nor DRNG to efficiently generate random numbers, causing anyone who needs random numbers right after the boot to wait until enough entropy has been gathered. Thus, it has to generate random numbers from things like keyboard, mouse, fan, etc. Meaning you can speed up this process of entropy(random numbers) generation by moving your mouse or typing on the keyboard. It's possible to check available entropy with cat /proc/sys/kernel/random/entropy_avail.
If Chrome just used urandom instead of random there would be no such problem. But it can be easily fixed by feeding random from urandom:
1) Install rng-tools
2) Run sudo rngd -o /dev/random -r /dev/urandom before you start your browser, say, in ~/.xinitrc
answered Jan 8 at 14:46
DaniDani
364
add a comment |
Browsers mainly use /dev/random(random), as /dev/urandom(pseudorandom) isn't considered to be trusted(but as man page random(4) points out, it shouldn't be so).
As it turns out, my laptop has neither TPM nor DRNG to efficiently generate random numbers, causing anyone who needs random numbers right after the boot to wait until enough entropy has been gathered. Thus, it has to generate random numbers from things like keyboard, mouse, fan, etc. Meaning you can speed up this process of entropy(random numbers) generation by moving your mouse or typing on the keyboard. It's possible to check available entropy with cat /proc/sys/kernel/random/entropy_avail.
If Chrome just used urandom instead of random there would be no such problem. But it can be easily fixed by feeding random from urandom:
1) Install rng-tools
2) Run sudo rngd -o /dev/random -r /dev/urandom before you start your browser, say, in ~/.xinitrc
answered Jan 8 at 14:46
DaniDani
364
add a comment |
Browsers mainly use /dev/random(random), as /dev/urandom(pseudorandom) isn't considered to be trusted(but as man page random(4) points out, it shouldn't be so).
As it turns out, my laptop has neither TPM nor DRNG to efficiently generate random numbers, causing anyone who needs random numbers right after the boot to wait until enough entropy has been gathered. Thus, it has to generate random numbers from things like keyboard, mouse, fan, etc. Meaning you can speed up this process of entropy(random numbers) generation by moving your mouse or typing on the keyboard. It's possible to check available entropy with cat /proc/sys/kernel/random/entropy_avail.
If Chrome just used urandom instead of random there would be no such problem. But it can be easily fixed by feeding random from urandom:
1) Install rng-tools
2) Run sudo rngd -o /dev/random -r /dev/urandom before you start your browser, say, in ~/.xinitrc
answered Jan 8 at 14:46
DaniDani
364
Browsers mainly use /dev/random(random), as /dev/urandom(pseudorandom) isn't considered to be trusted(but as man page random(4) points out, it shouldn't be so).
As it turns out, my laptop has neither TPM nor DRNG to efficiently generate random numbers, causing anyone who needs random numbers right after the boot to wait until enough entropy has been gathered. Thus, it has to generate random numbers from things like keyboard, mouse, fan, etc. Meaning you can speed up this process of entropy(random numbers) generation by moving your mouse or typing on the keyboard. It's possible to check available entropy with cat /proc/sys/kernel/random/entropy_avail.
If Chrome just used urandom instead of random there would be no such problem. But it can be easily fixed by feeding random from urandom:
1) Install rng-tools
2) Run sudo rngd -o /dev/random -r /dev/urandom before you start your browser, say, in ~/.xinitrc
answered Jan 8 at 14:46
DaniDani
364
answered Jan 8 at 14:46
DaniDani
364
answered Jan 8 at 14:46
DaniDani
364
answered Jan 8 at 14:46
DaniDani
364
364
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493242%2ftakes-too-long-for-any-browser-to-load-at-the-first-time%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
