From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 198345] AMD-RNG can't find a device. Kernel 4.15rc6 with AMD Vega64
Date: Wed, 03 Jan 2018 17:02:17 +0000 [thread overview]
Message-ID: <bug-198345-2300-5VKCLpGKMJ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198345-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=198345
--- Comment #2 from Justin J. (justin2201@gmail.com) ---
xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x90 cap: 0xf, Source Output, Sink Output, Source Offload, Sink
Offload crtcs: 6 outputs: 4 associated providers: 0 name:Radeon RX Vega @
pci:0000:03:00.0
Provider 1: id: 0x46 cap: 0xf, Source Output, Sink Output, Source Offload, Sink
Offload crtcs: 3 outputs: 4 associated providers: 0 name:modesetting
sudo modprobe -v amd-rng
[sudo] Passwort für justin:
insmod /lib/modules/4.15.0-rc6-custom/kernel/drivers/char/hw_random/rng-core.ko
insmod /lib/modules/4.15.0-rc6-custom/kernel/drivers/char/hw_random/amd-rng.ko
modprobe: ERROR: could not insert 'amd_rng': No such device
I loaded it properly... Seems to do the same mistake.
and yes rng-core should be supported. the first time loading works.
--
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-01-03 17:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 16:22 [Bug 198345] New: AMD-RNG can't find a device. Kernel 4.15rc6 with AMD Vega64 bugzilla-daemon
2018-01-03 16:26 ` [Bug 198345] " bugzilla-daemon
2018-01-03 17:02 ` bugzilla-daemon [this message]
2018-01-03 17:13 ` bugzilla-daemon
2018-01-03 17: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-198345-2300-5VKCLpGKMJ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox