From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Brill Subject: Re: Using a HD 4670 still possible? Date: Sat, 13 Sep 2014 20:13:06 +0200 Message-ID: References: <540D095F.2000509@daenzer.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1517409760==" Return-path: Received: from wp030.webpack.hosteurope.de (wp030.webpack.hosteurope.de [80.237.132.37]) by gabe.freedesktop.org (Postfix) with ESMTP id F1D356E093 for ; Sat, 13 Sep 2014 11:32:04 -0700 (PDT) Received: by mail-vc0-f173.google.com with SMTP id le20so2011158vcb.18 for ; Sat, 13 Sep 2014 11:13:07 -0700 (PDT) In-Reply-To: <540D095F.2000509@daenzer.net> 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 --===============1517409760== Content-Type: multipart/alternative; boundary=001a11339096810bd50502f65a91 --001a11339096810bd50502f65a91 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am 08.09.2014 03:41 schrieb "Michel D=C3=A4nzer" : > > 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=3D0". >> >> 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=3D0 finally bring= s the system into a usable state. The dmesg of a default boot (i.e. radeon.msi=3D-1) is available at http://pastebin.com/gS1xHYPc > > -- > Earthling Michel D=C3=A4nzer | http://www.amd= .com > Libre software enthusiast | Mesa and X developer --001a11339096810bd50502f65a91 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Am 08.09.2014 03:41 schrieb "Michel D=C3=A4nzer" <michel@daenzer.net>:
>
> On 07.09.2014 01:01, Christoph Brill wrote:
>>
>>
>> I'm currently trying to get a HD 4670 aka RV730 XT to work aga= inst 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 sessi= on
>> 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 setti= ng
>> "vblank_mode=3D0".
>>
>> I guessed my card does not like to play along with vsync at all. S= o I
>> went ahead to disable vsyncing (tearing is still better than no di= splay
>> at all). Setting it globally in /etc/drirc seems to get glxgears r= unning.
>>
>> Testing Xonotic on twm showed, that the card was now able to handl= e 3D.
>> But: gdm still was extremely sluggish and eventually froze. Starti= ng
>> gnome-shell directly from startx gets me to the desktop, but any a= ction
>> 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=3D0 finally br= ings the system into a usable state. The dmesg of a default boot (i.e. rade= on.msi=3D-1) is available at http:= //pastebin.com/gS1xHYPc

>
> --
> Earthling Michel D=C3=A4nzer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 http://www.amd.com
> Libre software enthusiast=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Mesa and X developer

--001a11339096810bd50502f65a91-- --===============1517409760== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1517409760==--