ATI Rage XL on x86_64

ATI Rage XL on x86_64

[Andrew Walrond]

I have lots of server boards with Rage XL onboard, and have just spent a few 
hours trying to get a working framebuffer using the atyfb driver (built-in)

However I have failed miserably so far. Before I start wading through the 
code, perhaps someone  can confirm that I am using the right kernel 
parameters?

This
 video=atyfb:vmode:14,cmode:8
gives
 atyfb: using auxiliary register aperture
 atyfb: 3D RAGE XL (Mach64 GR, PCI-33MHz) [0x4752 rev 0x27]
 atyfb: 8M SDRAM (2:1) (32-bit) 29.498928 MHz XTAL, 230MHz PLL, 83 MHz MCLK  
63MHz XCLK
 atyfb: MACH64 chips are designed for max 1600x1200
 select anoter resolution
 atyfb: MACH64 chips are designed for max 1600x1200
 select anoter resolution
 atyfb: vclk out of range
 atyfb: vclk out of range
 atyfb: fb0: ATY Mach64 frame buffer device on PCI

and this
 video=atyfb:vmode:14,cmode:8
gives
 atyfb: using auxiliary register aperture
 atyfb: 3D RAGE XL (Mach64 GR, PCI-33MHz) [0x4752 rev 0x27]
 atyfb: 8M SDRAM (2:1) (32-bit) 29.498928 MHz XTAL, 230MHz PLL, 83 MHz MCLK  
63MHz XCLK
 atyfb: MACH64 chips are designed for max 1600x1200
 select anoter resolution
 atyfb: MACH64 chips are designed for max 1600x1200
 select anoter resolution
 atyfb: fb0: ATY Mach64 frame buffer device on PCI


(The speliing mistake is real BTW)

Any clues?

Andrew Walrond



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

Re: ATI Rage XL on x86_64

[Andrew Walrond]

On Wednesday 26 January 2005 09:10, Andrew Walrond wrote:

Sorry the second parameter line should have been
 video=atyfb:mode:1024x768

A 1280x1024 TFT screen is attached BTW


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

Re: ATI Rage XL on x86_64

[Ville Syrjälä]

On Wed, Jan 26, 2005 at 09:39:48AM +0000, Andrew Walrond wrote:
> On Wednesday 26 January 2005 09:10, Andrew Walrond wrote:
> 
> Sorry the second parameter line should have been
>  video=atyfb:mode:1024x768

atyfb:1024x768 is the correct format.

You can also add depth and/or refresh rate eg. atyfb:1024x768-8@60

> A 1280x1024 TFT screen is attached BTW

Digital or analog? The driver doesn't touch any of the TDMS registers so I 
don't know if digital flat panels will work.

-- 
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

Re: ATI Rage XL on x86_64

[Andrew Walrond]

Hi Ville

On Wednesday 26 January 2005 10:54, Ville Syrjälä wrote:
> On Wed, Jan 26, 2005 at 09:39:48AM +0000, Andrew Walrond wrote:
> > On Wednesday 26 January 2005 09:10, Andrew Walrond wrote:
> >
> > Sorry the second parameter line should have been
> >  video=atyfb:mode:1024x768
>
> atyfb:1024x768 is the correct format.
>

I had tried that first, since it is the default. Googling and the framebuffer 
howto suggested the other formats

When I try video=atyfb:1024x768-8@60, I get even less output:

 atyfb: using auxiliary register aperture
 atyfb: 3D RAGE XL (Mach64 GR, PCI-33MHz) [0x4752 rev 0x27]
 atyfb: 8M SDRAM (2:1) (32-bit) 29.498928 MHz XTAL, 230MHz PLL, 83 MHz MCLK  
63MHz XCLK
 atyfb: fb0: ATY Mach64 frame buffer device on PCI

In all cases, the screen blanks for a moment during boot, then reppears in 
original 80x25 format.


These messages:

 atyfb: MACH64 chips are designed for max 1600x1200
 select anoter resolution
 atyfb: MACH64 chips are designed for max 1600x1200
 select anoter resolution
 atyfb: vclk out of range
 atyfb: vclk out of range

suggest to me that something is going quite wrong, probably 64bit related, 
although that suprises me because I think the ppc folks use this driver quite 
a bit. But perhaps only ppc32.

I'll have a dig in the code and see whats going on.

>
> > A 1280x1024 TFT screen is attached BTW
>
> Digital or analog? The driver doesn't touch any of the TDMS registers so I
> don't know if digital flat panels will work.

Analog, so this shouldn't be an issue. I am running linux-2.6.10.

Andrew Walrond


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

Re: ATI Rage XL on x86_64

[Andrew Walrond]

[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]

On Wednesday 26 January 2005 12:09, Andrew Walrond wrote:
>
> When I try video=atyfb:1024x768-8@60, I get even less output:
>
>  atyfb: using auxiliary register aperture
>  atyfb: 3D RAGE XL (Mach64 GR, PCI-33MHz) [0x4752 rev 0x27]
>  atyfb: 8M SDRAM (2:1) (32-bit) 29.498928 MHz XTAL, 230MHz PLL, 83 MHz MCLK
> 63MHz XCLK
>  atyfb: fb0: ATY Mach64 frame buffer device on PCI
>
> In all cases, the screen blanks for a moment during boot, then reppears in
> original 80x25 format.

FYI I have resolved this issue.

I had CONFIG_FRAMEBUFFER_CONSOLE=m

in the kernel config. I think the frambuffer code was working fine (explaining 
the screen blanking during boot), but then the console subsystem 
reconfiguring the display back to text mode.

Changing to CONFIG_FRAMEBUFFER_CONSOLE=y fixed this.

This is obviously a 'gotcha' to remember for the future, but perhaps also a 
candidate for further thought, since all subsequent use of the fb device (for 
graphics) produced a corrupt display.

Andrew Walrond

[-- Attachment #2: Type: text/html, Size: 1343 bytes --]