From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199619] screen stays dark for long on bootup since kernel 4.17.0-rc2+
Date: Wed, 12 Sep 2018 08:00:44 +0000 [thread overview]
Message-ID: <bug-199619-2300-5rlTzr9zmy@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199619-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=199619
--- Comment #13 from Elmar Stellnberger (estellnb@elstel.org) ---
Unfortunately when I install rng-tools I get the following error message with
4.19.0-rc2+: Hardware RNG device inode not found. If I install rng-tools5 I get
no error message but booting does not speed up with rng-tools5 (same long
waiting). Concerning my wireless network card I have an iwlwifi card (Intel
Corporation Ultimate N WiFi Link 5300). However there seems to be no kernel
option in order to gather entropy with this card.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-09-12 8:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 7:34 [Bug 199619] New: screen stays dark for long on bootup since kernel 4.17.0-rc2+ bugzilla-daemon
2018-05-07 10:23 ` [Bug 199619] " bugzilla-daemon
2018-05-07 11:03 ` bugzilla-daemon
2018-05-12 8:00 ` bugzilla-daemon
2018-05-20 23:43 ` bugzilla-daemon
2018-06-08 17:01 ` bugzilla-daemon
2018-06-08 17:32 ` bugzilla-daemon
2018-06-11 16:34 ` bugzilla-daemon
2018-06-11 16:35 ` bugzilla-daemon
2018-06-19 19:51 ` bugzilla-daemon
2018-06-20 8:44 ` bugzilla-daemon
2018-09-11 6:52 ` bugzilla-daemon
2018-09-11 11:00 ` bugzilla-daemon
2018-09-12 8:00 ` bugzilla-daemon [this message]
2018-11-28 13:18 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-199619-2300-5rlTzr9zmy@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.