From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 32821] New: [mach64] DRI doesn't work on SGRAM with 4096Kb
Date: Tue, 4 Jan 2011 04:16:43 -0800 (PST) [thread overview]
Message-ID: <bug-32821-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=32821
Summary: [mach64] DRI doesn't work on SGRAM with 4096Kb
Product: DRI
Version: XOrg CVS
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/other
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: nss.zpeedzter@gmail.com
Created an attachment (id=41615)
--> (https://bugs.freedesktop.org/attachment.cgi?id=41615)
with default packages and default conf
I have an integrated ATI Rage Pro 2x on a Dell OptiPlex GX1.
I'm running ARCHLINUX
here's a part of the xorg log with default packages and default configuration
[ 23.698] (--) Depth 24 pixmap format is 32 bpp
[ 23.757] (WW) MACH64(0): DRI static buffer allocation failed -- need at
least 10000 kB video memory
....
....
[ 23.791] (II) MACH64(0): Direct rendering disabled
and the second situation:
I install mach64drm from AUR and added an xorg.conf and switched to 16bpp
here's a part of xorg log:
[ 25.394] (II) MACH64(0): I2C bus "Mach64" initialized.
[ 25.455] (WW) MACH64(0): DRI static buffer allocation failed -- need at
least 7593 kB video memory
....
....
[ 25.489] (II) MACH64(0): Direct rendering disabled
--
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-01-04 12:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 12:16 bugzilla-daemon [this message]
2011-01-04 12:17 ` [Bug 32821] [mach64] DRI doesn't work on SGRAM with 4096Kb bugzilla-daemon
2011-01-04 17:07 ` bugzilla-daemon
2011-01-04 17:08 ` bugzilla-daemon
2011-01-04 17:14 ` bugzilla-daemon
2019-10-14 13:20 ` 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-32821-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).