From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 92858] AMD Radeon GPU Acceleration Disabled Under Kernels 4.2.x and later versions Date: Thu, 12 Nov 2015 02:40:56 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1375299554==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id DD0AC6EBA4 for ; Wed, 11 Nov 2015 18:40:56 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1375299554== Content-Type: multipart/alternative; boundary="1447296056.7eBDAfE80.18380"; charset="UTF-8" --1447296056.7eBDAfE80.18380 Date: Thu, 12 Nov 2015 02:40:56 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=92858 --- Comment #5 from Darren --- Thanks you again for the guide--it was simple and human-readable and I understood the directions, I think. 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)". I'd take a screencapture but there's no way to do so until X is up, and this is before X is started. I've used a config file I built myself via make menuconfig, the default ubuntu 4.3 kernel config file, and the distro's current running kernel (4.1.12) config, obtaining by "zcat /proc/config.gz > .config. The same message occurred under all three of the kernels I built. I'll keep on compiling in the meantime until I isolate the problem, but I did have one question: Let's assume the first kernel I compile boots and acceleration works. After I get the kernel to compile and boot, do I need to run "make clean" in the source tree directory after "git bisect good," or is that going to strip away files that git bisect needs in order to keep a record of good and bad commits? -- You are receiving this mail because: You are the assignee for the bug. --1447296056.7eBDAfE80.18380 Date: Thu, 12 Nov 2015 02:40:56 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 5 on bug 92858 from 
Thanks you again for the guide--it was simple and human-readable and I
understood the directions, I think. 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)". I'd take a screencapture but
there's no way to do so until X is up, and this is before X is started. I've
used a config file I built myself via make menuconfig, the default ubuntu 4.3
kernel config file, and the distro's current running kernel (4.1.12) config,
obtaining by "zcat /proc/config.gz > .config. The same message occurred under
all three of the kernels I built.

I'll keep on compiling in the meantime until I isolate the problem, but I did
have one question: Let's assume the first kernel I compile boots and
acceleration works. After I get the kernel to compile and boot, do I need to
run "make clean" in the source tree directory after "git bisect good," or is
that going to strip away files that git bisect needs in order to keep a record
of good and bad commits?

You are receiving this mail because:
  • You are the assignee for the bug.
--1447296056.7eBDAfE80.18380-- --===============1375299554== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============1375299554==--