[Dri-devel] Re: [Newbie]Radeon & AMD 751 Chipset Problem

[Iain T. <Iai...@nt...>]

On Fri, 9 Mar 2001, Dan Mullineux wrote:
> > After fighting this thing for some time, I finally got my Radeon AIW to
> > work with Linux.
> > I'll give my specs:
> > Athlon 700
> > AMD 751 Irongate / VIA 686A SuperSouth Chipset
> > Radeon All In Wonder 32MB DDR
> > 256MB Ram
> > Triple Boot Linux Red Hat 7, Win 98, Win NT
> > Kernel 2.4.2
> > XFree 4.0.2 (CVS sources from dri.sourceforge.net)
> > I have looked and found many other people that have this same problem and
> > the commonality seems to be the AMD 751 Irongate Chipset
> Iain Thomas reports that Kenneth Arnold has a VIA KT133 chipset crashing 
> after a few seconds, although others (Iain himself) has that chipset stable!

I'll note Kernel 2.4.x again, vs my working 2.2.18.

Anyhow, BIOS settings to try: I don't know which, if any, of these will
break it if changed, this is just what by CMOS setup says...

Memore Hole                Disabled
PCI Master Pipeline Req    Enabled
P2C/C2P Concurrency        Enabled
Fast R-W Turn Around       Enabled
System BIOS Cacheable      Enabled
Video RAM Cacheable        Disabled
AGP Arperture Size         64M
AGP-4X Mode                Enabled
AGP Driving Control        Auto
AGP Driving Value          68 (this appears greyed out)
Fast Write Supported       Supported
CPU to PCI Write Buffer    Enabled
PCI Dynamic Bursting       Enabled
PCI Master 0 WS Write      Enabled
PCI Delay Transaction      Enabled
PCI#2 Access #1 Retry      Enabled
AGP Master 1 WS Write      Disabled
AGP Master 1 WS Read       Disabled

These can be found in "Advanced Chipset Features", and note that my board
(the KT7) is based on Award BIOS; the Asus/Gigabyte AMI BIOSes do, I
believe, have some similar settings, but I can't name the menus etc.

I'll also just note: i /have/ found a way to crash X; while just about
everything works fine, xdaliclock -transparent -cycle frequently causes
crashes (Sig 11) in X when I move the window with Enlightenment, with no
odd messages in dmesg, or the log file (well, other than Caught Signal
11...). Occurs with the DRM loaded, doesn't occue when window is resized.
Must get that special module-aware GDB at some point...
Odd though, that it just seems to be xdaliclock, netscape/terminals/xmms
are all fine.

-- 
Regards, Iai...@di....
My website: http://www.warwick.ac.uk/~csuli/
XMMS now playing: Sting - Desert Rose