From: Andrew Walrond <andrew@walrond.org>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: ATI Rage XL on x86_64
Date: Wed, 26 Jan 2005 09:10:14 +0000 [thread overview]
Message-ID: <200501260910.14102.andrew@walrond.org> (raw)
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
next reply other threads:[~2005-01-26 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 9:10 Andrew Walrond [this message]
2005-01-26 9:39 ` ATI Rage XL on x86_64 Andrew Walrond
2005-01-26 10:54 ` Ville Syrjälä
2005-01-26 12:09 ` Andrew Walrond
2005-01-27 14:54 ` Andrew Walrond
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200501260910.14102.andrew@walrond.org \
--to=andrew@walrond.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).