https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #57 from Mike Lothian ---
I got lots of radeon: The kernel rejected CS, see dmesg for more information.
from the wine process
If this is a separate issue I'll look into it more tomorrow
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #56 from Mike Lothian ---
Created attachment 75082
--> https://bugs.freedesktop.org/attachment.cgi?id=75082=edit
Dmesg output
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part
https://bugs.freedesktop.org/show_bug.cgi?id=56405
Mike Lothian changed:
What|Removed |Added
CC||mike at fireburn.co.uk
--- Comment #55
https://bugs.freedesktop.org/show_bug.cgi?id=56405
Mike Lothian m...@fireburn.co.uk changed:
What|Removed |Added
CC||m...@fireburn.co.uk
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #56 from Mike Lothian m...@fireburn.co.uk ---
Created attachment 75082
-- https://bugs.freedesktop.org/attachment.cgi?id=75082action=edit
Dmesg output
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #57 from Mike Lothian m...@fireburn.co.uk ---
I got lots of radeon: The kernel rejected CS, see dmesg for more information.
from the wine process
If this is a separate issue I'll look into it more tomorrow
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=56405
Michael Dressel changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=56405
Michael Dressel mdrs...@t-online.de changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #53 from runetmember at gmail.com ---
Yesterday I installed 3.8rc1 and also can confirm - fix works for me too.
Thanks!
Michael, if you also doesn't have this problem anymore please close the ticket.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #52 from Johannes Hirte ---
Fix works for me.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #52 from Johannes Hirte johannes.hi...@fem.tu-ilmenau.de ---
Fix works for me.
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #53 from runetmem...@gmail.com ---
Yesterday I installed 3.8rc1 and also can confirm - fix works for me too.
Thanks!
Michael, if you also doesn't have this problem anymore please close the ticket.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=56405
Florian Mickler changed:
What|Removed |Added
CC||florian at mickler.org
--- Comment
https://bugs.freedesktop.org/show_bug.cgi?id=56405
Alex Deucher changed:
What|Removed |Added
CC||adamreichold at myopera.com
--- Comment
https://bugs.freedesktop.org/show_bug.cgi?id=56405
Florian Mickler flor...@mickler.org changed:
What|Removed |Added
CC||flor...@mickler.org
https://bugs.freedesktop.org/show_bug.cgi?id=56405
Alex Deucher ag...@yahoo.com changed:
What|Removed |Added
CC||adamreich...@myopera.com
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #49 from Alex Deucher ---
(In reply to comment #48)
> Does this patch get into kernel 3.8?
Yes. It will be in 3.8 and the stable kernels.
--
You are receiving this mail because:
You are the assignee for the bug.
--
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #48 from klausenbusk at hotmail.com ---
(In reply to comment #41)
> Created attachment 71284 [details] [review]
> Patch gpu pipe
>
> Does this kernel patch fix the issue ?
Does this patch get into kernel 3.8?
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #48 from klausenb...@hotmail.com ---
(In reply to comment #41)
Created attachment 71284 [details] [review]
Patch gpu pipe
Does this kernel patch fix the issue ?
Does this patch get into kernel 3.8?
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #49 from Alex Deucher ag...@yahoo.com ---
(In reply to comment #48)
Does this patch get into kernel 3.8?
Yes. It will be in 3.8 and the stable kernels.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=56405
Alex Deucher changed:
What|Removed |Added
CC||kphillisjr at gmail.com
--- Comment #47
https://bugs.freedesktop.org/show_bug.cgi?id=56405
Alex Deucher changed:
What|Removed |Added
CC||johannes.hirte at fem.tu-ilmen
https://bugs.freedesktop.org/show_bug.cgi?id=56405
Alex Deucher ag...@yahoo.com changed:
What|Removed |Added
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=56405
Alex Deucher ag...@yahoo.com changed:
What|Removed |Added
CC||kphilli...@gmail.com
---
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #45 from Michael Dressel ---
(In reply to comment #41)
> Created attachment 71284 [details] [review]
> Patch gpu pipe
>
> Does this kernel patch fix the issue ?
Yes it does solve the bug! And it seams
to solve bug #56720 too.
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #44 from Alex Deucher ---
(In reply to comment #43)
> (In reply to comment #42)
> > case CHIP_SUMO2:
> > - rdev->config.evergreen.num_ses = 1;
> > + rdev->config.evergreen.num_ses = 2;
> >
> > None of the
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #43 from klausenbusk at hotmail.com ---
(In reply to comment #42)
> case CHIP_SUMO2:
> - rdev->config.evergreen.num_ses = 1;
> + rdev->config.evergreen.num_ses = 2;
>
> None of the APUs have multiple
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #42 from Alex Deucher ---
case CHIP_SUMO2:
-rdev->config.evergreen.num_ses = 1;
+rdev->config.evergreen.num_ses = 2;
None of the APUs have multiple SEs.
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #41 from Jerome Glisse ---
Created attachment 71284
--> https://bugs.freedesktop.org/attachment.cgi?id=71284=edit
Patch gpu pipe
Does this kernel patch fix the issue ?
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #40 from klausenbusk at hotmail.com ---
Any update?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #40 from klausenb...@hotmail.com ---
Any update?
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #41 from Jerome Glisse gli...@freedesktop.org ---
Created attachment 71284
-- https://bugs.freedesktop.org/attachment.cgi?id=71284action=edit
Patch gpu pipe
Does this kernel patch fix the issue ?
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #42 from Alex Deucher ag...@yahoo.com ---
case CHIP_SUMO2:
-rdev-config.evergreen.num_ses = 1;
+rdev-config.evergreen.num_ses = 2;
None of the APUs have multiple SEs.
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #43 from klausenb...@hotmail.com ---
(In reply to comment #42)
case CHIP_SUMO2:
- rdev-config.evergreen.num_ses = 1;
+ rdev-config.evergreen.num_ses = 2;
None of the APUs have multiple SEs.
So it
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #44 from Alex Deucher ag...@yahoo.com ---
(In reply to comment #43)
(In reply to comment #42)
case CHIP_SUMO2:
- rdev-config.evergreen.num_ses = 1;
+ rdev-config.evergreen.num_ses = 2;
None of the
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #45 from Michael Dressel mdrs...@t-online.de ---
(In reply to comment #41)
Created attachment 71284 [details] [review]
Patch gpu pipe
Does this kernel patch fix the issue ?
Yes it does solve the bug! And it seams
to solve bug
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #39 from Alex Deucher ---
(In reply to comment #38)
> The distorted graphics problem disappears when setting the option
> Option "NoAccel" "on".
> (This may be obvious to the experts.)
>
> In this mode a new phenomenon appears:
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #38 from Michael Dressel ---
The distorted graphics problem disappears when setting the option
Option "NoAccel" "on".
(This may be obvious to the experts.)
In this mode a new phenomenon appears: When moving th mouse to the
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #38 from Michael Dressel mdrs...@t-online.de ---
The distorted graphics problem disappears when setting the option
Option NoAccel on.
(This may be obvious to the experts.)
In this mode a new phenomenon appears: When moving th mouse
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #39 from Alex Deucher ag...@yahoo.com ---
(In reply to comment #38)
The distorted graphics problem disappears when setting the option
Option NoAccel on.
(This may be obvious to the experts.)
In this mode a new phenomenon
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #37 from runetmember at gmail.com ---
For me "ColorTiling2D" "false" doesn't help too.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #36 from Michael Dressel ---
(In reply to comment #35)
> To confirm, does:
> Option "ColorTiling2D" "false"
> in the device section of your xorg.conf also fix the issues?
No it does not solve this bug but it solves bug #56986 for
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #35 from Alex Deucher ---
To confirm, does:
Option "ColorTiling2D" "false"
in the device section of your xorg.conf also fix the issues?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #35 from Alex Deucher ag...@yahoo.com ---
To confirm, does:
Option ColorTiling2D false
in the device section of your xorg.conf also fix the issues?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #36 from Michael Dressel mdrs...@t-online.de ---
(In reply to comment #35)
To confirm, does:
Option ColorTiling2D false
in the device section of your xorg.conf also fix the issues?
No it does not solve this bug but it solves bug
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #37 from runetmem...@gmail.com ---
For me ColorTiling2D false doesn't help too.
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #34 from Michael Dressel ---
I finished bisecting (again).
The result looks like this:
git bisect bad
c0c979eebc076b95cc8d18a013ce2968fe6311ad is the first bad commit
commit c0c979eebc076b95cc8d18a013ce2968fe6311ad
Author: Jerome
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #34 from Michael Dressel mdrs...@t-online.de ---
I finished bisecting (again).
The result looks like this:
git bisect bad
c0c979eebc076b95cc8d18a013ce2968fe6311ad is the first bad commit
commit
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #33 from Michael Dressel ---
Created attachment 70454
--> https://bugs.freedesktop.org/attachment.cgi?id=70454=edit
the patch I used lately
This is a patch I need to apply in order to get at least
r600_dri.so compiled.
Could the
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #32 from Michael Dressel ---
Created attachment 70453
--> https://bugs.freedesktop.org/attachment.cgi?id=70453=edit
new bisect log
I started bisecting from the second last bad commit.
I could verify it's bad. The new bisect log
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #32 from Michael Dressel mdrs...@t-online.de ---
Created attachment 70453
-- https://bugs.freedesktop.org/attachment.cgi?id=70453action=edit
new bisect log
I started bisecting from the second last bad commit.
I could verify it's
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #33 from Michael Dressel mdrs...@t-online.de ---
Created attachment 70454
-- https://bugs.freedesktop.org/attachment.cgi?id=70454action=edit
the patch I used lately
This is a patch I need to apply in order to get at least
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #31 from Michel D?nzer ---
(In reply to comment #29)
> libGL error: dlopen /usr/lib/xorg/modules/dri/r600_dri.so failed
> (/usr/lib/libglsl.so: undefined symbol: hash_table_string_hash)
Is /usr/lib/libglsl.so built from your Mesa
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #30 from Michael Dressel ---
I found I made a mistake during bisecting.
In order to get rid of the latest compile problem
I upgraded libgl to the 9.0.1 version.
Now gnome starts and does not show the problem.
I finished bisecting
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #30 from Michael Dressel mdrs...@t-online.de ---
I found I made a mistake during bisecting.
In order to get rid of the latest compile problem
I upgraded libgl to the 9.0.1 version.
Now gnome starts and does not show the problem.
I
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #31 from Michel Dänzer mic...@daenzer.net ---
(In reply to comment #29)
libGL error: dlopen /usr/lib/xorg/modules/dri/r600_dri.so failed
(/usr/lib/libglsl.so: undefined symbol: hash_table_string_hash)
Is /usr/lib/libglsl.so built
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #29 from Michael Dressel ---
(In reply to comment #28)
> (In reply to comment #27)
> > (In reply to comment #26)
> > > (In reply to comment #25)
> > > LIBGL_DEBUG=verbose glxinfo | grep render
> > I don't have glxinfo
>
> Ah I
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #28 from Michael Dressel ---
(In reply to comment #27)
> (In reply to comment #26)
> > (In reply to comment #25)
> > LIBGL_DEBUG=verbose glxinfo | grep render
> I don't have glxinfo
Ah I found it on archlinux AUR in the
package
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #27 from Michael Dressel ---
(In reply to comment #26)
> (In reply to comment #25)
> LIBGL_DEBUG=verbose glxinfo | grep render
I don't have glxinfo
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #26 from Michel D?nzer ---
(In reply to comment #25)
> But now gnome starts in fallback mode with the new r600_dri.so.
Does
LIBGL_DEBUG=verbose glxinfo | grep render
give any hints as to what might be wrong with this r600_dri.so?
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #25 from Michael Dressel ---
I have not tried that before.
Now I cherry picked
0b616b2f5164621e3a63caeb15c6eb1d01bbc55a
4a162f6eba73a8cb2654cd99a2bd12bd468925a6
on top of
302862defa61b2cee1ae24159aca306f090ca854
The r600_dri.so
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #24 from Michel D?nzer ---
(In reply to comment #22)
> bisect log
It does look like you're getting close to isolating a commit. Most likely it's
one of the remaining r600g commits, but there's still too many of them to guess
which
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #23 from Michael Dressel ---
Created attachment 70327
--> https://bugs.freedesktop.org/attachment.cgi?id=70327=edit
patch I used for compilation
This is git diff -p output showing the patches I applied to get some thing
compiled.
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #22 from Michael Dressel ---
Created attachment 70326
--> https://bugs.freedesktop.org/attachment.cgi?id=70326=edit
bisect log
I think all the information can be derived by replaying
bisect log information from the file I
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #21 from Michel D?nzer ---
(In reply to comment #19)
> I have 15 commits left to test.
Which ones?
> Anyway I'm not even convinced my test is a good test. Because since a while I
> only get the r600_dri.so built. And I only
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #21 from Michel Dänzer mic...@daenzer.net ---
(In reply to comment #19)
I have 15 commits left to test.
Which ones?
Anyway I'm not even convinced my test is a good test. Because since a while I
only get the r600_dri.so built.
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #23 from Michael Dressel mdrs...@t-online.de ---
Created attachment 70327
-- https://bugs.freedesktop.org/attachment.cgi?id=70327action=edit
patch I used for compilation
This is git diff -p output showing the patches I applied to
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #24 from Michel Dänzer mic...@daenzer.net ---
(In reply to comment #22)
bisect log
It does look like you're getting close to isolating a commit. Most likely it's
one of the remaining r600g commits, but there's still too many of them
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #25 from Michael Dressel mdrs...@t-online.de ---
I have not tried that before.
Now I cherry picked
0b616b2f5164621e3a63caeb15c6eb1d01bbc55a
4a162f6eba73a8cb2654cd99a2bd12bd468925a6
on top of
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #26 from Michel Dänzer mic...@daenzer.net ---
(In reply to comment #25)
But now gnome starts in fallback mode with the new r600_dri.so.
Does
LIBGL_DEBUG=verbose glxinfo | grep render
give any hints as to what might be wrong with
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #27 from Michael Dressel mdrs...@t-online.de ---
(In reply to comment #26)
(In reply to comment #25)
LIBGL_DEBUG=verbose glxinfo | grep render
I don't have glxinfo
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #28 from Michael Dressel mdrs...@t-online.de ---
(In reply to comment #27)
(In reply to comment #26)
(In reply to comment #25)
LIBGL_DEBUG=verbose glxinfo | grep render
I don't have glxinfo
Ah I found it on archlinux AUR in
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #29 from Michael Dressel mdrs...@t-online.de ---
(In reply to comment #28)
(In reply to comment #27)
(In reply to comment #26)
(In reply to comment #25)
LIBGL_DEBUG=verbose glxinfo | grep render
I don't have glxinfo
Ah
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #20 from Alex Deucher ---
(In reply to comment #19)
> Even if I would succeed in finding the bad commit how would you fix
> it if you can not reproduce the problem?
It will help narrow down what's causing the problem and give us a
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #19 from Michael Dressel ---
I'm stuck with:
g++ -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector
--param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wall -std=c99
-Werror=implicit-function-declaration -Werror=missing-prototypes
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #19 from Michael Dressel mdrs...@t-online.de ---
I'm stuck with:
g++ -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector
--param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wall -std=c99
-Werror=implicit-function-declaration
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #20 from Alex Deucher ag...@yahoo.com ---
(In reply to comment #19)
Even if I would succeed in finding the bad commit how would you fix
it if you can not reproduce the problem?
It will help narrow down what's causing the problem
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #18 from Michel D?nzer ---
(In reply to comment #17)
> Can I just stop gdm set the environment and start gdm with systemctl?
I don't think so. It mainly needs to be in gnome-shell's environment, but I'm
not sure offhand how best to
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #18 from Michel Dänzer mic...@daenzer.net ---
(In reply to comment #17)
Can I just stop gdm set the environment and start gdm with systemctl?
I don't think so. It mainly needs to be in gnome-shell's environment, but I'm
not sure
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #17 from Michael Dressel ---
(In reply to comment #14)
> (In reply to comment #13)
> Maybe it would be easier to just do manual builds instead of using PKGBUILD
> for the bisect? You can point to the directory containing the
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #16 from Michael Dressel ---
I compiled the commit 6671d0dad300e591ac7c0e5110c6778373d0149a
which I picked to start bisecting. (I picked it because the date
is related to the date of the 8.0 branch as mentioned above)
It shows the
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #15 from Michael Dressel ---
I tried to compile c1f4867c89adb1a6b19d66ec8ad146115909f0a7
the commit taged with mesa-8.0.4 and I get the following compilation error:
g++ -c -I. -I../../../src/gallium/include
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #15 from Michael Dressel mdrs...@t-online.de ---
I tried to compile c1f4867c89adb1a6b19d66ec8ad146115909f0a7
the commit taged with mesa-8.0.4 and I get the following compilation error:
g++ -c -I. -I../../../src/gallium/include
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #16 from Michael Dressel mdrs...@t-online.de ---
I compiled the commit 6671d0dad300e591ac7c0e5110c6778373d0149a
which I picked to start bisecting. (I picked it because the date
is related to the date of the 8.0 branch as mentioned
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #17 from Michael Dressel mdrs...@t-online.de ---
(In reply to comment #14)
(In reply to comment #13)
Maybe it would be easier to just do manual builds instead of using PKGBUILD
for the bisect? You can point to the directory
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #14 from Michel D?nzer ---
(In reply to comment #13)
> These are the compile errors I get with the above mentioned commit.
> The compile errors are fixed in the commit also mentioned above.
One strategy for such cases is to look at
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #14 from Michel Dänzer mic...@daenzer.net ---
(In reply to comment #13)
These are the compile errors I get with the above mentioned commit.
The compile errors are fixed in the commit also mentioned above.
One strategy for such
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #13 from Michael Dressel ---
Created attachment 69640
--> https://bugs.freedesktop.org/attachment.cgi?id=69640=edit
compilation errors
These are the compile errors I get with the above mentioned commit.
The compile errors are
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #12 from Michel D?nzer ---
What are the compile errors?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #12 from Michel Dänzer mic...@daenzer.net ---
What are the compile errors?
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #13 from Michael Dressel mdrs...@t-online.de ---
Created attachment 69640
-- https://bugs.freedesktop.org/attachment.cgi?id=69640action=edit
compilation errors
These are the compile errors I get with the above mentioned commit.
The
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #11 from mdrslmr at t-online.de ---
Created attachment 69497
--> https://bugs.freedesktop.org/attachment.cgi?id=69497=edit
script to build libraries and drivers
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #10 from mdrslmr at t-online.de ---
I could still do some bisecting if anyone could help me
building the packages ati-dri and libg. I'm using
a modified PKGBUILD. I guess I don't need everything
build by that script. In order to get
https://bugs.freedesktop.org/show_bug.cgi?id=56405
runetmember at gmail.com changed:
What|Removed |Added
CC||runetmember at gmail.com
---
https://bugs.freedesktop.org/show_bug.cgi?id=56405
runetmem...@gmail.com changed:
What|Removed |Added
CC||runetmem...@gmail.com
---
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #10 from mdrs...@t-online.de ---
I could still do some bisecting if anyone could help me
building the packages ati-dri and libg. I'm using
a modified PKGBUILD. I guess I don't need everything
build by that script. In order to get
https://bugs.freedesktop.org/show_bug.cgi?id=56405
--- Comment #11 from mdrs...@t-online.de ---
Created attachment 69497
-- https://bugs.freedesktop.org/attachment.cgi?id=69497action=edit
script to build libraries and drivers
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=56405
Andreas Boll changed:
What|Removed |Added
Component|Drivers/DRI/Radeon |Drivers/Gallium/r600
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=56405
Andreas Boll andreas.boll@gmail.com changed:
What|Removed |Added
Component|Drivers/DRI/Radeon
https://bugs.freedesktop.org/show_bug.cgi?id=56405
Alex Deucher changed:
What|Removed |Added
CC||klausenbusk at hotmail.com
--- Comment
1 - 100 of 114 matches
Mail list logo
