|
[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
[NMLUG] DRI/OpenGL
On Fri, Jan 30, 2004 at 05:11:09PM -0700, Gary Sandine
carved this out of pure phosphors:
> On Fri, 2004-01-30 at 16:41, Anthony Martinez wrote:
> > Attached to this
> > message.
>
> That looks perfect to me.
>
> I would try:
>
> 0. Upgrade all X packages to XFree86 4.3.0-0pre1v5. These are
> in experimental, and AFAIK are the only official X 4.3 packages
> for Debian at this time.
>
> If not 0., then:
>
> 1. Try depth 16 color instead of depth 24 (if you're using 24).
>
> 3. Try AGPMode 1 or maybe 0 to see if it has any effect.
>
> 2. Make radeon.o a module instead of compiled in, and replace it
> (it's at /lib/modules/`uname -r`/kernel/drivers/char/drm/radeon.o)
> with the one from drm-trunk-module-src.
I've done stops 1, 2, and 3, and none of them work.. However.... I tried Knoppix
3.3 with the Radeon server, and it works perfectly fine. I get 500 FPS with
glxgears, and no lockup.
I'm about to give up trying to do this, because my IBM Service partition, and my
WindowMaker state file, and my dpkg Available file, along with a few .viminfos
scattered around the system, got corrupted.
Speaking of the dpkg available file, is that necessary? Do i need to rebuild it?
I copied the -old copy on top of the corrupted one.
>
> Do you have something like
>
> Section "DRI"
> Group 0
> Mode 0666
> EndSection
>
> in your XF86Config file? I think glxinfo would fail if this wasn't
> there anyway....
>
> Have you ever been able to run glxgears (with direct rendering enabled)
> in this laptop? I had a bad video card (once, out of many many) that
> would lock up a machine when glxgears was executed.
>
>
> _______________________________________________
> NMLUG mailing list
> NMLUG@nmlug.org
> http://www.nmlug.org/mailman/listinfo/nmlug
--
printk(KERN_WARNING "Warning: defective CD-ROM (volume sequence
number). Enabling \"cruft\" mount option.\n");
2.2.16 /usr/src/linux/fs/isofs/inode.c
|
|
