On Sat, May 19, 2001 at 02:10:43PM +1000, Gareth Hughes wrote:
> I'm currently working on some kernel-related tasks, but I can take a
> look into the problems you (and others) have mentioned regarding the
> Radeon driver early next week. Are you running it from the DRI CVS? If
> you're game, you
"Stephen C. Tweedie" wrote:
>
> Well, in composing the previous email I did several reboots with what
> I thought was the "good" configuration and some of them failed. So
> I've just spent half an hour rebooting into full DRI, and finally got
> the X server to start properly. Now that it has go
> and the chipset is one a lot of people have had problems with: an AMD
> IronGate AMD-751 (though most of the problems I've seen reported on
> the lists have been Radeon+AMD-750, not 751).
I can only comment on this.
AMD-750 (760/760MP with DDR-SDRAM support) is the name for the whole chipset.
Hi,
On Sat, May 19, 2001 at 12:57:38AM +0100, Stephen C. Tweedie wrote:
> In other words, merely loading the DRI module is guaranteed to cause
> lockup on subsequent display initialisation, even if the DRI is not
> successfully initialised. The only reliable way to start X is to
> comment out t
(I'm not subscribed to the list, please CC: me any replies)
I've had screen corruption and lockup problems with my Voodoo3 3500 TV since
when I started using XFree86 4.0. After downloading the whole source code, I
found the "NoAccel" option, which let me at least use the server (with a few
visua
Hi all,
OK, I think I've got about as far as I can get with this card on my
own. Time to dump the current status to the experts and see where we
go from here.
The basic problem is that X locks up at startup with a corrupt display
if the DRI is loaded. I'm currently running a DRI built from CVS
On Fri, May 18, 2001 at 09:19:43AM +0100, Alan Hourihane wrote:
> On Thu, May 17, 2001 at 07:31:40PM -0400, Norbert Veber wrote:
> > Hi,
> >
> > I'm currently using the 20010430 daily build, which detects my card fine. I
> > just tried the 0.7 release, which is not able to detect the card.
> >
Your tuxracer problem can be fixed by editing the options file in the
$HOME/.tuxracer directory. Find the following line and change it to the
following:
use_sphere_display_list false
That should make him black again.
L8r,
Ken
reiner wrote:
> Hello all,
>
> I have tested v0.7 dri + Extra-p
Petr Sebor wrote:
>
> Hello,
>
> I have reported this earlier, but this is a confirmation that
> GL_LINEAR_MIPMAP_NEAREST is still broken in v0.7 with radeon 32 ddr.
> Just to sum it up - first mipmap is rendered correctly with LINEAR filtering while
> subsequent mips are rendered with NEAREST f
After playing q3demo for some time, and then quitting the game, DRI
reproduceably locks up. It freezes on the credits screen. Mouse is not
moveable, vt's are not changeable. SysRq key does work, and a reboot
can be acheived that way.
This is kernel 2.4.4, with kdb installed. If you want any i
Hello all,
I have tested v0.7 dri + Extra-package for radeon on debian/unstable.
My suggestions:fast and reliable (so far)
parsec works great
armagetron works too
thanks for this good work
the only d
I've noticed that after playing the Loki Descent3 demo for a moment or
two, and then exiting the game, the top-left quarter (approximately) of
the screen becomes corrupted. Its nothing terrible, just the whole
quadrant is reduced in resolution to about 4 blocks.
This didn't occur with the DRI in
On Thu, May 17, 2001 at 07:31:40PM -0400, Norbert Veber wrote:
> Hi,
>
> I'm currently using the 20010430 daily build, which detects my card fine. I
> just tried the 0.7 release, which is not able to detect the card.
>
Change the line in your XF86Config file from
Driver "ati"
to
Driver "rade
13 matches
Mail list logo
