linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Joseph Garcia <jpgarcia@execpc.com>
To: "Keith W. Shaw" <keithws@fork.yi.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Open firmware booting & atyfb
Date: Fri, 14 Jan 2000 01:26:18 -0600	[thread overview]
Message-ID: <387ECF9A.AAFC6DBD@execpc.com> (raw)
In-Reply-To: Pine.NEB.4.21.0001130230090.569-100000@dizzy


"Keith W. Shaw" wrote:
> i've also tried passing various kernel arguements.  my normal
> (bootx) arguement is "video=atyfb:vmode:14,cmode:32"  it appears that it's
> trying to change, but just can't (by the way try vmode:13 for something
> interesting :)

I understand the want to stay with fbdev for glx.  One of these days, I too may
try OF booting.  Anyway, about the white "LCD fire" as some of my friends have
termed it, I recall that occuring often before the MCLK code was added to atyfb
control.  Solution: add a mclk param to your atyfb params.  If that is the
cause, it might clear up.  My wallstreet/300 has a mclk of 100, though some
people have set theirs to 83. (mine does work at 83)  so the new video line
would be "video=atyfb:vmode:14,cmode:32,mclk:100" or 83.

If you'd like to share your expiriences with GLX and OF-booting with me, I would
be grateful.  (I am still using utah-glx with Rage hardware disabled)

Thank you for your time.

-- 
Joseph P. Garcia      jpgarcia@execpc.com      jpgarcia@lidar.ssec.wisc.edu
CS Undergraduate                      Student Employee - Systems Programmer
University of Wisconsin - Madison                            UW Lidar Group

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2000-01-14  7:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-13 10:55 Open firmware booting & atyfb Keith W. Shaw
2000-01-14  7:26 ` Joseph Garcia [this message]

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=387ECF9A.AAFC6DBD@execpc.com \
    --to=jpgarcia@execpc.com \
    --cc=keithws@fork.yi.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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).