On Sat, Apr 14, 2001 at 02:29:13PM -0600, Harold Oga wrote:
> On 14 Apr 2001, at 12:54, Simon Kirby wrote:
>
> > I'll try AGPMode "2" to see if it crashes with that as well, but it
> > definitely looks like there are some problems on my ASUS P2B-DS (BX
> > chipset) and 4x AGP. Err, maybe it's n
On 14 Apr 2001, at 12:54, Simon Kirby wrote:
> Well, I think I just figured out what was doing it. Option "AGPMode" "4"
> in my X configuration file. I turned it off, and just played Q3 for
> around two hours in a hot room with no crashes.
>
> I'll try AGPMode "2" to see if it crashes with that
On Fri, Apr 13, 2001 at 08:59:13PM -0700, Joseph Carter wrote:
> On Fri, Apr 13, 2001 at 12:10:11PM -0700, Simon Kirby wrote:
> >
> > Hmm! Where is this option? I can't seem to find it in my BIOS anywhere.
> > Perhaps it's only an option on newer boards.
> >
> > What other things have you tr
On Fri, Apr 13, 2001 at 12:10:11PM -0700, Simon Kirby wrote:
> > Actually, what is REALLY freakin' weird is that it seems to work just
> > about to the point that I start typing something, at which point the next
> > thing I type has to start with SysRq because it's locked tight.. It's
> > truly
On Fri, Apr 13, 2001 at 05:02:42AM -0700, Joseph Carter wrote:
> Actually, what is REALLY freakin' weird is that it seems to work just
> about to the point that I start typing something, at which point the next
> thing I type has to start with SysRq because it's locked tight.. It's
> truly bizar
On Thu, Apr 12, 2001 at 01:16:06AM -0700, Simon Kirby wrote:
> > After a few hours, the machine will lock up if I have the drm module
> > loaded. It runs fine for days on end without it, so it's probably AGP
> > related. Lockups happen a lot faster if I run a GLX app that uses more
> > than a fe
On Sat, Apr 07, 2001 at 08:03:38PM -0700, Joseph Carter wrote:
> After a few hours, the machine will lock up if I have the drm module
> loaded. It runs fine for days on end without it, so it's probably AGP
> related. Lockups happen a lot faster if I run a GLX app that uses more
> than a few tex
On Mon, Apr 09, 2001 at 12:24:52PM +0200, Stefan Lange wrote:
> mtrr: detected mtrr type: Intel
> ...
> ...
> this is probably not related to your problems, but I'm just wondering why your mtrr
>is detected as `type: Intel'
> is that the usual behaviour for AMD Durons?
I believe so. I actually
from your dmesg:
...
...
CPU0
mtrr: v1.40 (20010327) Richard Gooch ([EMAIL PROTECTED])
mtrr: detected mtrr type: Intel
PCI: PCI BIOS revision 2.10 entry at 0xfb430, last bus=1
...
...
this is probably not related to your problems, but I'm just wondering why your mtrr is
detected as `type: Intel'
My Radeon has been sucking it back too. In Quake3 anything to do with 2d
is broken. And when I tried to quit it crashes and I'm forced to
reboot. Also Quake3 can't change video modes.
-Miles
On Sat, 7 Apr 2001, Harold Oga wrote:
> On Sat, Apr 07, 2001 at 09:36:00PM -0700, Joseph Carter wrote
On Sat, Apr 07, 2001 at 09:36:00PM -0700, Joseph Carter wrote:
>I would have to check, but I believe that it's already using 32.
>
>Yes, according to xdpyinfo:
>
>bitmap unit, bit order, padding:32, LSBFirst, 32
Hi,
Ok, I just tried it and it looks like the radeon driver doesn't support
24b
On Sat, Apr 07, 2001 at 10:15:20PM -0600, Harold Oga wrote:
> Hi,
>I have no problems with my Radeon LE on a MSI K7T Pro-2a board, which
> is a KT133, not a KT133a. One thing that you have setup different than I
> do is that you have it setup for 24bpp rather than 32bpp, which is what I
> hav
On Sat, Apr 07, 2001 at 08:31:52PM -0700, Jeffrey W. Baker wrote:
> > I'm still having problems with the Radeon. Since I grabbed the BIOS
> > settings on the last reboot, I'll try to provide as much information as I
> > can in the hopes that the problem may be reproduced, worked around, or
> > fi
On Sat, Apr 07, 2001 at 08:03:38PM -0700, Joseph Carter wrote:
>Section "Screen"
> Identifier "Default Screen"
> Device "ATI Radeon VIVO"
> Monitor "Dell P110"
> DefaultDepth24
># DefaultDepth16
> SubSection "Display"
>
On Sat, 7 Apr 2001, Joseph Carter wrote:
> I'm still having problems with the Radeon. Since I grabbed the BIOS
> settings on the last reboot, I'll try to provide as much information as I
> can in the hopes that the problem may be reproduced, worked around, or
> fixed. I've been using Mercury's
I'm still having problems with the Radeon. Since I grabbed the BIOS
settings on the last reboot, I'll try to provide as much information as I
can in the hopes that the problem may be reproduced, worked around, or
fixed. I've been using Mercury's CVS DRI Debian packages.
After a few hours, the m
16 matches
Mail list logo
