[ltp] FireGL T2 3d under SuSE 9.0

[Niel Lambrechts]

> -----Original Message-----
> From: linux-thinkpad-admin@linux-thinkpad.org 
> [mailto:linux-thinkpad-admin@linux-thinkpad.org] On Behalf Of Hamie
> Sent: 19 June 2004 07:36 PM
> To: linux-thinkpad@linux-thinkpad.org
> Subject: Re: [ltp] FireGL T2 3d under SuSE 9.0
> 
> 
> Niel Lambrechts wrote:
> 
> >Hi,
> >
> >I'm trying (for much too long now) to get the ATI fglrx driver going 
> >under X with 3d acceleration.
> >
> >Cfg: SuSE 9.0, kernel 2.6.7-rc3-mm1, Thinkpad R50P.
> >
> >Here is what I have done using fglrx-4.3.0-3.9.0:
> >
> >fglrx module
> >-------------
> >1. Applied the latest regparm patch for 3.9.0 driver
> >2. Fixed the "structure has no member named count" error 
> which shows up 
> >under this kernel. 3. At this point, fglrx module compiles 
> ok and can 
> >be loaded.
> >
> >Setup
> >-----
> >4. modprobe intel_agp
> >Linux agpgart interface v0.100 (c) Dave Jones
> >agpgart: Detected an Intel 855PM Chipset.
> >5. modprobe fglrx - no problem
> >6. Fix /proc/mtrr:
> >  
> >
> >>cat /var/log/XFree86.0.log|grep ATI|grep PCI
> >>    
> >>
> >(--) PCI:*(1:0:0) ATI Technologies Inc unknown chipset (0x4e54) rev 
> >128, Mem @ 0xe0000000/27, 0xc0100000/16, I/O @ 0x3000/8
> >  
> >
> >>echo "disable=2" >| /proc/mtrr
> >>echo "base=0xe0000000 size=0x8000000 type=write-combining" >|
> >>    
> >>
> >/proc/mtrr
> >
> >So now /proc/mtrr shows:
> >reg00: base=0x00000000 (   0MB), size= 512MB: write-back, count=1
> >reg01: base=0x1ff80000 ( 511MB), size= 512KB: uncachable, count=1
> >reg02: base=0xe0000000 (3584MB), size= 128MB: 
> write-combining, count=5
> >reg03: base=0xd0000000 (3328MB), size= 256MB: 
> write-combining, count=1
> >
> >* If my info is correct, reg02 is now correctly showing 
> 128MB videomem. 
> >7. startx After X is up, I see fglrx is indeed used:
> >lsmod|grep fglrx
> >fglrx                 210884  249
> >
> >but
> >PROBLEMS
> >--------
> >  
> >
> >>glxinfo|grep -i direct
> >>    
> >>
> >direct rendering: No
> >OpenGL renderer string: Mesa GLX Indirect
> >* No DRI???
> >
> >  
> >
> >>fglrxinfo
> >>    
> >>
> >display: :0.0  screen: 0
> >OpenGL vendor string: Mesa project: www.mesa3d.org
> >OpenGL renderer string: Mesa GLX Indirect
> >OpenGL version string: 1.3 Mesa 4.0.4
> >
> >* This is obviously WRONG, it should show ATI.
> >
> >  
> >
> >>fgl_glxgears
> >>    
> >>
> >Error: couldn't get fbconfig
> > 
> >  
> >
> >>dmesg|grep -i mtrr
> >>    
> >>
> >mtrr: no MTRR for e0000000,400000 found
> >mtrr: no MTRR for e0400000,200000 found
> >mtrr: no MTRR for e0600000,100000 found
> >* still pops up even though my mtrr has been fixed up?
> >
> >  
> >
> 
> The fglrx drivers use their own mtrr stuff, so I belive 
> there's no need 
> to play with the kernel mtrr stuff.
> 
> >Any help would be appreciated!!!
> >
> >Niel
> >
> >
> >PS: Some things from my XFree-log:
> >  
> >
> >>cat /var/log/XFree86.0.log|grep WW
> >>    
> >>
> >(WW) Open APM failed (/dev/apm_bios) (No such device)
> >(WW) fglrx(0): board is an unknown third party board, chipset is 
> >supported
> >(WW) fglrx(0): Cannot read colourmap from VGA.  Will restore with 
> >default
> >(WW) Open APM failed (/dev/apm_bios) (No such device)
> >
> >Not sure if this is a problem, I use ACPI and not APM.
> >
> >  
> >
> 
> Well, I use ACPI on an r50p as well. I have the fglrx drivers working 
> under kernel 2.6.6, but gave up because of several problems.
> 
> 1. Can't restore video after suspending to ram.
> 2. When switching from X -> Console -> X, then the colourmap 
> seems to be 
> screwed up.Not completely, just... strange... icons with some funny 
> colours, text on some apps looks multi-coloured. (Not xterms though).
> 
> I moved to Xorg's X server this week. And now I can suspend 
> to ram & not 
> have to reboot all the time. All I need now is suspend to 
> disk & I'll be 
> happy. Even if DRI & 3d acceleration don't work with Xorg's 
> server. It's 
> still quick (I didn't do much 3d work anyway, even though the fglrx 
> drivers were blindingly fast. Over 100fps using fglrx_gears 
> full screen.
> 
> Where did you get the XF86Config-4 from? There's an fglrx 
> config utility 
> with the drivers that will set it all up for you. Or you can download 
> one from <http://www.travellingkiwi.com/> (Follow the link 
> for Linux on 
> an r50p).
> 
> Hamish.
> 

Hi,

Even your XF86Config-4 file does not do the trick for me (yes, I am
pulling some hair out now)

Did you have to relinking of X libraries in any way?
Did you also have to apply the special regparm patch before you could
get the fglrx driver to compile?

Strangely, neither dmesg or Xfree logs show me any errors that could
shed some light on this...
In fact, I see a "DRIScreenInit done" message?

Regards,
Niel