From: "Michel Dänzer" <michel@daenzer.net>
To: Christoph Brill <egore911@egore911.de>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: Using a HD 4670 still possible?
Date: Wed, 17 Sep 2014 16:30:55 +0900 [thread overview]
Message-ID: <541938AF.7050009@daenzer.net> (raw)
In-Reply-To: <CAEG350TBOaWHja9pjuwGkWkxuV3i2GJw9pLuCxeH9-j8mD3zHg@mail.gmail.com>
On 14.09.2014 03:13, Christoph Brill wrote:
> Am 08.09.2014 03:41 schrieb "Michel Dänzer" <michel@daenzer.net
> <mailto: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 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?
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
next prev parent reply other threads:[~2014-09-17 7:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-06 16:01 Using a HD 4670 still possible? Christoph Brill
2014-09-08 1:41 ` Michel Dänzer
2014-09-13 18:13 ` Christoph Brill
2014-09-17 7:30 ` Michel Dänzer [this message]
2014-09-17 12:55 ` Alex Deucher
2014-09-17 20:27 ` Christoph Brill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=541938AF.7050009@daenzer.net \
--to=michel@daenzer.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=egore911@egore911.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox