Hi Alex, hi Michael,
I filed bug https://bugs.freedesktop.org/show_bug.cgi?id=84017 with all requested infos attached. If you need anything else or if I should test patches just let me know.
Best wishes,
Christoph
2014-09-17 14:55 GMT+02:00 Alex Deucher <alexdeucher@xxxxxxxxx>:
Also mention what chipset your system uses and whether the card is AGP or not.On Wed, Sep 17, 2014 at 3:30 AM, Michel Dänzer <michel@xxxxxxxxxxx> wrote:
> On 14.09.2014 03:13, Christoph Brill wrote:
>>
>> Am 08.09.2014 03:41 schrieb "Michel Dänzer" <michel@xxxxxxxxxxx
>> <mailto:michel@xxxxxxxxxxx>>:
>>
>> > On 07.09.2014 01:01, Christoph Brill wrote:
>> >>
>> >>
>> >> I'm currently trying to get a HD 4670 aka RV730 XT to work against
>> X.org
>> >> 1.16, xf86-video-ati 7.4.0 on a Linux 3.16.1.
>> >>
>> >> Can anyone tell me: Should this card be able to handle an average
>> Gnome
>> >> desktop?
>> >
>> >
>> > Of course.
>> >
>> >
>> >
>> >> The problem was: 3D rendering did not work at all.
>> >>
>> >> Starting gdm lead to hanging Xorg. Calling glxgears on a twm session
>> >> just rendered a black window, which stayed even if the process was
>> >> killed by CTRL+C. I managed to get glxgears do do its job by setting
>> >> "vblank_mode=0".
>> >>
>> >> I guessed my card does not like to play along with vsync at all. So I
>> >> went ahead to disable vsyncing (tearing is still better than no
>> display
>> >> at all). Setting it globally in /etc/drirc seems to get glxgears
>> running.
>> >>
>> >> Testing Xonotic on twm showed, that the card was now able to handle
>> 3D.
>> >> But: gdm still was extremely sluggish and eventually froze. Starting
>> >> gnome-shell directly from startx gets me to the desktop, but any
>> action
>> >> freezes the process.
>> >>
>> >> Is there still hope for this card or should I get rid of it?
>> >
>> >
>> > It sounds like there's a problem with interrupt processing on your
>> system. Please provide the dmesg output. You might try
>> disabling/enabling MSI to see if that works around the problem.
>>
>> Thank you so much for this hint! Booting using radeon.msi=0 finally
>> brings the system into a usable state. The dmesg of a default boot (i.e.
>> radeon.msi=-1) is available at http://pastebin.com/gS1xHYPc
>
>
> Can you file a bug report at
> https://bugs.freedesktop.org/enter_bug.cgi?product=DRI component
> "DRM/Radeon" and attach the dmesg output there?
>
Alex
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
