From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92858] AMD Radeon GPU Acceleration Disabled Under Kernels 4.2.x and later versions
Date: Thu, 12 Nov 2015 04:59:20 +0000 [thread overview]
Message-ID: <bug-92858-502-DOeIA3yDrn@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92858-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1828 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92858
--- Comment #7 from Darren D. <ysxikrhn@vomoto.com> ---
(In reply to Michel Dänzer from comment #6)
> (In reply to Darren from comment #5)
> > Sadly, as of thus far, every kernel I've compiled panics at bootup, with a
> > message like this, or similar: "kernel panic. vfs unable to mount root on
> > unknown block (0,0)".
>
> Sounds like there's a problem with the .config or maybe the root=[...]
> parameter on the kernel command line. For .config, I'd recommend starting
> with the original .config from 4.3-rc7 and then just running "make
> oldconfig".
>
>
And that helped--in a sense. It produced a kernel that would at least boot
partially instead of a kernel panic, but the boot froze on the distro splash
screen. It's progress, though! I edited grub.cfg (I've read not to do this, but
it was a temporary modification to test a theory) to use "nosplash" instead of
"splash" on the kernel command lin grub entry for the kernel I'd compiled, and
once I booted that kernal again, I noticied a 'could not locate modules:
template usr/lib/modules/$KERNELVERSION" type of error. Again, no way to
screenshot it as it was early in the boot process.
I'm guessing now I've discovered the problem: Renaming the
/usr/lib/modules/$KERNELVERSION directory to something different than what the
"make modules_install" command named it when it built the directory--and prior
to running the mkinitcpio command to build the initial ramdisk--is a bad idea.
Live and learn.
I'm back on track now, and with any luck and free time between day job and
sleep, eventually I'll have a bootable kernel compiled soon so I can actually
start bisecting to locate the bad commit.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2885 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-11-12 4:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 22:57 [Bug 92858] AMD Radeon GPU Acceleration Disabled Under Kernels 4.2.x and later versions bugzilla-daemon
2015-11-08 11:47 ` bugzilla-daemon
2015-11-08 11:55 ` bugzilla-daemon
2015-11-08 15:40 ` bugzilla-daemon
2015-11-08 15:56 ` bugzilla-daemon
2015-11-08 19:55 ` bugzilla-daemon
2015-11-12 2:40 ` bugzilla-daemon
2015-11-12 2:52 ` bugzilla-daemon
2015-11-12 4:59 ` bugzilla-daemon [this message]
2015-11-12 12:57 ` bugzilla-daemon
2015-11-15 0:58 ` bugzilla-daemon
2015-11-15 11:00 ` bugzilla-daemon
2015-12-05 17:47 ` bugzilla-daemon
2015-12-05 18:28 ` bugzilla-daemon
2015-12-12 19:57 ` bugzilla-daemon
2015-12-17 7:19 ` bugzilla-daemon
2015-12-17 7:24 ` bugzilla-daemon
2015-12-19 16:33 ` bugzilla-daemon
2015-12-19 17:58 ` bugzilla-daemon
2016-01-10 2:46 ` bugzilla-daemon
2016-01-10 2:47 ` bugzilla-daemon
2016-01-10 2:47 ` bugzilla-daemon
2016-01-13 7:14 ` bugzilla-daemon
2016-01-16 16:12 ` bugzilla-daemon
2016-01-18 6:35 ` 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-92858-502-DOeIA3yDrn@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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