[Bug 92858] AMD Radeon GPU Acceleration Disabled Under Kernels 4.2.x and later versions - bugzilla-daemon

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: Sun, 08 Nov 2015 19:55:59 +0000	[thread overview]
Message-ID: <bug-92858-502-sbVpR25esv@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92858-502@http.bugs.freedesktop.org/>

[-- Attachment #1.1: Type: text/plain, Size: 1961 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=92858

--- Comment #4 from Christian König <deathsimple@vodafone.de> ---
Well you are already doing quite fine and as far as I understand you are
capable to build your own kernel from source and that's everything you need.

I will try to explain the rest step by step in detail and what the commands do.

First of all the long strings of text like
"c11d716218910c3aa2bac1bb641e6086ad649555" are hash code, which identify a
patch or change in the history of the kernel development.

Each change the developers did between 4.1 and 4.2 has such a hash code which
is basically just a fingerprint of the whole source code at that moment.

When you initially clone a source repository using "git clone" it indeed checks
out the latest version by default.

Now you already did "git bisect start v4.2 v4.1" in the newly created source
directory which tells git that version 4.2 is bad and version 4.1 is good.

This command than takes a look at all the changes between version 4.1 and 4.2
and then jumps into the middle of this list. In your case that is commit
"[c11d716218910c3aa2bac1bb641e6086ad649555] Merge tag 'armsoc-cleanup' of...".

This commit is now checked out and you can build, install and test the kernel.

Then you go into the directory again and do "git bisect good" if the newly
build kernel works and if it doesn't work you do "git bisect bad".

Git will then look at the list of changes again and jumps either toward the
direction of version 4.1 or 4.2 (depends on if you said good or bad) and then
checks out the next change to test.

This repeats roughly 13 times until git found the change which caused your
problems.

All you need to do is making sure you always boot the latest installed kernel.
By default grub for example will boot the kernel with the highest version
number.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2886 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