From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36817] New: RV670 - Kernel fails to enable acceleration when RAM greater than 32-bit limit
Date: Tue, 3 May 2011 16:57:01 -0700 (PDT) [thread overview]
Message-ID: <bug-36817-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=36817
Summary: RV670 - Kernel fails to enable acceleration when RAM
greater than 32-bit limit
Product: DRI
Version: unspecified
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: reg@achart.me.uk
I sure hope I'm in the right place...
Using a Radeon HD3870 that works fine under Windows (64-bit). After a supposed
initial success using a pre-release version of KMS drivers (which may be a red
herring), I have been unable to get 3D acceleration on any Ubuntu release from
Lucid, unless I use a non-PAE kernel (I have 4GB RAM).
My Ubuntu bug ticket (including logs) is here:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/574884
Another bug that looks similar:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/657576
A similar looking bug with a similar workaround (which I'll shortly try on
mine) on SUSE: http://web.archiveorange.com/archive/v/wmeLDauZzOL6SFQx1uKY
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-05-03 23:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 23:57 bugzilla-daemon [this message]
2011-08-17 18:24 ` [Bug 36817] RV670 - Kernel fails to enable acceleration when RAM greater than 32-bit limit bugzilla-daemon
2016-02-26 6:10 ` bugzilla-daemon
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=bug-36817-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.