On Sat, May 05, 2001 at 11:36:23PM -0700, Joseph Carter wrote:
> If I had to guess, ACPI. Turn it off. Since you have had luck with the
> Radeon, which motherboard are you using?
o VIA VT82C686b & VT8363/VT8365 ...
Even if I turned off acpi I still got random lock ups. :(
Joseph Carter wrote:
>
> The Radeon 64 works fine in windoze in my brother's box (VIA chipset,
> Intel chip, Celeron 600ish I think) and I'm going to try it in a BX-based
> Linux box to confirm that the Radeon 64 driver works. I suspect it will,
> but in that case the problem is most likely agpg
On Sat, May 05, 2001 at 08:21:11PM -0400, Zilvinas Valinskas wrote:
> > The Radeon 64 works fine in windoze in my brother's box (VIA chipset,
> > Intel chip, Celeron 600ish I think) and I'm going to try it in a BX-based
> > Linux box to confirm that the Radeon 64 driver works. I suspect it will,
On Sat, May 05, 2001 at 05:04:28PM -0700, Joseph Carter wrote:
> The Radeon 64 works fine in windoze in my brother's box (VIA chipset,
> Intel chip, Celeron 600ish I think) and I'm going to try it in a BX-based
> Linux box to confirm that the Radeon 64 driver works. I suspect it will,
> but in th
On Sat, May 05, 2001 at 01:38:03PM -0400, Zilvinas Valinskas wrote:
> > Am I to understand it that the patch you mention simply sets this value
> > regardless of whether or not it's an option in the BIOS?
>
> No only if you the "lucky" owner of KT7A/KT7A-RAID MB
> (or other similar MB with VT86C
On Sat, May 05, 2001 at 01:38:03PM -0400, Zilvinas Valinskas wrote:
> On Fri, May 04, 2001 at 10:36:17PM -0700, Joseph Carter wrote:
> > Am I to understand it that the patch you mention simply sets this value
> > regardless of whether or not it's an option in the BIOS?
>
> No only if you the "luc
On Fri, May 04, 2001 at 10:36:17PM -0700, Joseph Carter wrote:
> Am I to understand it that the patch you mention simply sets this value
> regardless of whether or not it's an option in the BIOS?
No only if you the "lucky" owner of KT7A/KT7A-RAID MB
(or other similar MB with VT86C688b chipset an
On Fri, May 04, 2001 at 09:22:59PM -0400, Zilvinas Valinskas wrote:
> When it comes 'bus lock up' and VIA chipset ... checkout
> http://www.viahardware.com/ there you should find latest
> via 'PCI latency patch' that also fixes ... (or supposed to fix)
> such random locks up ...
>
> btw. That pat
When it comes 'bus lock up' and VIA chipset ... checkout
http://www.viahardware.com/ there you should find latest
via 'PCI latency patch' that also fixes ... (or supposed to fix)
such random locks up ...
btw. That patch is in the latest greatest kernels. including
2.4.3-acX (X > 12) and later.
Jon Pennington wrote:
>
> On Thu, May 03, 2001 at 08:15:19PM -0500, Andy Isaacson wrote:
>
> > On Thu, May 03, 2001 at 04:26:00PM -0600, Brian Paul wrote:
>
> > > Would it be better if the DRI User Guide were divided into a number of
> > > separate HTML pages, instead of one long document? I c
On Thu, May 03, 2001 at 08:15:19PM -0500, Andy Isaacson wrote:
> On Thu, May 03, 2001 at 04:26:00PM -0600, Brian Paul wrote:
> > Would it be better if the DRI User Guide were divided into a number of
> > separate HTML pages, instead of one long document? I could do that
> > with the sgml2html c
On Fri, 4 May 2001, Joseph Carter wrote:
> On Fri, May 04, 2001 at 01:12:47PM +0100, Iain Thomas wrote:
> > > As I said, it seems specific to the Radeon 64, the 32s have been reported
> > > to work fine.
> > We all know that the various Radeons have differend core clock-speeds,
> > right?
> We do
On Fri, May 04, 2001 at 01:12:47PM +0100, Iain Thomas wrote:
> > As I said, it seems specific to the Radeon 64, the 32s have been reported
> > to work fine.
>
> We all know that the various Radeons have differend core clock-speeds,
> right?
We do now. =)
> The retail 64M is 183Mhz, the plain
On Thu, 3 May 2001, Joseph Carter wrote:
> On Thu, May 03, 2001 at 09:47:23PM -0700, Jeffrey W. Baker wrote:
> > > There also appears to be a conflict with the Radeon 64 and the KT133A (or
> > > at least the Abit KT7A..)
> > I've got a KT133A and a Radeon All-in-Wonder, with no problems at all.
>
On Fri, May 04, 2001 at 01:32:52AM -0400, Rich 'Forge' Mingin wrote:
> Actually, the issue described here is an ATI/all-non-Intel chipsets one.
> ATI's drivers ship by default with a tweaked AGPgart (they call it the
> 'atigart'). This, of course, causes massive problems when it
> overrides/confli
is
issue is applicable to Linux.
Rich 'Forge' Mingin
Open Source Advocate
Quake 3 Junkie
Forge on www.tech-report.com
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Joseph
Carter
Sent: Friday, 04 May, 2001 01:14
To: Gareth Hughes
Cc: [EMAIL
On Thu, May 03, 2001 at 09:47:23PM -0700, Jeffrey W. Baker wrote:
> > There also appears to be a conflict with the Radeon 64 and the KT133A (or
> > at least the Abit KT7A..) Nobody so far has been able to confirm it that
> > I've seen, but the problem is documented with workaround for Win00. Giv
On Fri, May 04, 2001 at 02:47:27PM +1000, Gareth Hughes wrote:
> > There also appears to be a conflict with the Radeon 64 and the KT133A (or
> > at least the Abit KT7A..) Nobody so far has been able to confirm it that
> > I've seen, but the problem is documented with workaround for Win00. Given
Joseph Carter wrote:
>
> There also appears to be a conflict with the Radeon 64 and the KT133A (or
> at least the Abit KT7A..) Nobody so far has been able to confirm it that
> I've seen, but the problem is documented with workaround for Win00. Given
> that I have the same setup, same symptoms,
On Thu, 3 May 2001, Joseph Carter wrote:
> There also appears to be a conflict with the Radeon 64 and the KT133A (or
> at least the Abit KT7A..) Nobody so far has been able to confirm it that
> I've seen, but the problem is documented with workaround for Win00. Given
> that I have the same setu
On Thu, May 03, 2001 at 04:34:11PM -0700, Jeffrey W. Baker wrote:
> > > Could someone add to the "Known Problems" for the Radeon that it
> > > doesn't work with certain AMD chipsets? This is a pretty serious bug
> > > that apparently has been known about for quite some time. I certainly
> > > wou
Brian Paul wrote:
>
> >
> > Hmm. Is EMBM supported/required by OpenGL, or is that strictly a DirectX thing?
>
> It could be supported by an OpenGL extension, but I don't think Matrox
> ever spec'd one out. I don't know enough of the details to say how
> hard it would be to implement.
I think
On Thu, May 03, 2001 at 04:26:00PM -0600, Brian Paul wrote:
> Would it be better if the DRI User Guide were divided into a number of
> separate HTML pages, instead of one long document? I could do that
> with the sgml2html converter. I'm hesitant to create new documents
> because that's more wor
On Thu, May 03, 2001 at 04:26:00PM -0600, Brian Paul wrote:
>
> We've got the docs but we have to spend our time working on projects
> which bring in income. We're hopeful that Radeon TCL will get done
> through a future contract. (Yes, I'm being vague).
What is the way / procedure to get hold
Jeffrey W. Baker wrote:
>
> On Thu, 3 May 2001, Brian Paul wrote:
>
>> Mark Allan wrote:
>>
>>> Brian Paul wrote:
>>>
> On Radeon we aren't doing TCL, cube textures, 3D textures and only
> support 2 of the 3 texture units. There's probably a few other things
> but that's off the
On Thu, 3 May 2001, Brian Paul wrote:
> Mark Allan wrote:
> >
> > Brian Paul wrote:
> > > > On Radeon we aren't doing TCL, cube textures, 3D textures and only
> > > > support 2 of the 3 texture units. There's probably a few other things
> > > > but that's off the top of my head.
> > >
> > > I'
Mark Allan wrote:
>
> Brian Paul wrote:
> > > On Radeon we aren't doing TCL, cube textures, 3D textures and only
> > > support 2 of the 3 texture units. There's probably a few other things
> > > but that's off the top of my head.
> >
> > I've just updated the DRI User Guide with more info about
Jon Pennington wrote:
>
> On Thu, May 03, 2001 at 08:33:23AM -0600, Brian Paul wrote:
>
> > Kreuzritter2000 wrote:
> > >
> > > This Feature list would also tell interested people what is done,
> > > and what has still to be done.
> > >
> > > What do you think about such a page?
> >
> > The DRI U
On Thu, May 03, 2001 at 08:33:23AM -0600, Brian Paul wrote:
> Kreuzritter2000 wrote:
> >
> > This Feature list would also tell interested people what is done,
> > and what has still to be done.
> >
> > What do you think about such a page?
>
> The DRI User guide has some of this information for
> Kreuzritter2000 wrote:
>>
>> Hello
>>
>> It would be great if there is a feature list on the dri website.
>>
>> That tells the progress of the driver, in other words what features
>> of the Chip ist are allready supported and what features are not support.
>> In the moment the Driver status page
Brian Paul wrote:
> > On Radeon we aren't doing TCL, cube textures, 3D textures and only
> > support 2 of the 3 texture units. There's probably a few other things
> > but that's off the top of my head.
>
> I've just updated the DRI User Guide with more info about hardware
> features implemented/
Brian Paul wrote:
>
> Kreuzritter2000 wrote:
> >
> > Hello
> >
> > It would be great if there is a feature list on the dri website.
> >
> > That tells the progress of the driver, in other words what features
> > of the Chip ist are allready supported and what features are not support.
> > In the
Kreuzritter2000 wrote:
>
> Hello
>
> It would be great if there is a feature list on the dri website.
>
> That tells the progress of the driver, in other words what features
> of the Chip ist are allready supported and what features are not support.
> In the moment the Driver status page only t
Hello
It would be great if there is a feature list on the dri website.
That tells the progress of the driver, in other words what features
of the Chip ist are allready supported and what features are not support.
In the moment the Driver status page only tells you if the chip works
or doesn't w
34 matches
Mail list logo