Steven Beeckman wrote:
> Now I'm using 2.4.24 (in the twenties) but I'm planning on upgrading to
> some 2.6 kernel (the newest one probably). Slackware 10.0 ships with
> X.org [...]
I believe with XOrg and a 2.6 kernel you already have anything you need
to get happy :-)
Cheers,
Martin.
Citeren Martin Spott <[EMAIL PROTECTED]>:
> Steven Beeckman wrote:
>
> > Martin, if you want you may explain to me how to get the ATI Radeon
> 9200
> > to work on a brand new Slackware 10.0 ;-)
>
> Which kernel release do you have with Slackware 10.0 ?
Now I'm using 2.4.24 (in the twenties) bu
Steven Beeckman wrote:
> Martin, if you want you may explain to me how to get the ATI Radeon 9200
> to work on a brand new Slackware 10.0 ;-)
Which kernel release do you have with Slackware 10.0 ?
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
---
Steven Beeckman wrote:
> PS: Alex: what's fglrx? The drivers from ATI? I've tried the rpm I
> think, but it didn't work out either :-s (probably because of what you
> said: two ways to solve the same problem ...)
'fglrx' is the closed source driver from ATI. You probably need to
tweak the build
Steven Beeckman wrote:
> Martin, if you want you may explain to me how to get the ATI Radeon 9200
> to work on a brand new Slackware 10.0 ;-). The docs of DRI speak about
> getting the CVS of X.Org, configuring the kernel [...]
I don't know which release of X11 is being shipped with Slackware 1
Actually, since the radeon driver is working better than fglrx at the moment,
I would like to see if I can speed the framerate up first.
I will include the logs tomorrow.
Thanks in advance,
Ampere
On November 8, 2004 09:27 pm, Ampere K. Hardraade wrote:
> I would certainly like to hear your adv
It turned out that the half of dozen kernel panic I have and my sloppy repair
works was also a contributor to the problem. To make a long story short, I
wipped the drive clean and start fresh.
I would certainly like to hear your advice on the fglrx route. =)
Ampere
On November 8, 2004 11:12 a
Alex Perry wrote:
From: Martin Spott <[EMAIL PROTECTED]>
"Ampere K. Hardraade" wrote:
Sigh... and I thought ATI is supposed to be Linux-friendly?!
Things have changed a bit these days, but the r200 chip is still one of
the best supported GPU's in the OpenSource world. The problem on
From: Martin Spott <[EMAIL PROTECTED]>
> "Ampere K. Hardraade" wrote:
> > Sigh... and I thought ATI is supposed to be Linux-friendly?!
> Things have changed a bit these days, but the r200 chip is still one of
> the best supported GPU's in the OpenSource world. The problem on _your_
> computer is no
Use Internal or not, it doesn't make any difference to me -- no direct
rendering. =(
Ampere
On November 7, 2004 11:27 pm, Alex Perry wrote:
> It found the card, initialized the driver, everything is fine.
> However, you told it to use the built in AGP driver, rather than
> the kernel one, and it
By mask, do you mean this line in XF86Config-4?
Option "AGPMode" "#"
If so, it is no use. X just skips it. =(
I will try again.
Ampere
On November 7, 2004 09:15 pm, Alex Perry wrote:
> If my memory serves me correctly, this is referring to the mask by which
> you specify which AGP modes the ha
The bits I thought were relevant:
> (II) PCI: 01:02:0: chip 1002,5964 card 148c,2074 rev 01 class 03,00,00 hdr 00
> (--) PCI: (0:2:0) Intel Corp. 82845G/GL [Brookdale-G] Chipset Integrated
> Graphics Device rev 1, Mem @ 0x2000/27
> (--) PCI:*(1:2:0) ATI Technologies Inc unknown chipset (0x596
> Also, in the XFree86.0.log, this keeps coming up:
> (EE) fglrx(0): [agp] could not determine AGP since mode=0x
> I did some googlings but I couldn't find anything related to this problem
If my memory serves me correctly, this is referring to the mask by which
you specify which AGP modes
13 matches
Mail list logo
