All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henry Worth <haworth@ncal.verio.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Pismo Aty128fb problem in 2.4.3-pre*?
Date: Mon, 05 Mar 2001 15:04:23 -0800	[thread overview]
Message-ID: <3AA41B77.73470672@ncal.verio.com> (raw)


I wasn't able to boot Kaoru-san's 2.4.3-pre1_0a binary
or kernels built from bitkeeper tar's of 2.4.3-pre1 and pre2.
This is on a Pismo and in all cases there's a sequence of
early boot messages ending in "open_pic exit" and then a few
seconds pause before the screen goes haywire (mostly blank,
but with a flashing fragments of a couple of the boot messages
and some other artifacts).

So, it finally dawned on me that I should try video=ofonly
and novideo bootparms instead of the usual aty128fb parms
and they both boot.

Is this a known problem? Or does 2.4.* require different
video bootparms for the Rage 128 than 2.2.*?

Haven't messed with 2.4 since the late 2.3 period, so I
don't have have anything to compare against to look for
changes. What's the last version of 2.4.* that aty128fb
is known to work, particularly for the Pismo, and are
the sources available somewhere to rsync or as a tarball?

Henry

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

             reply	other threads:[~2001-03-05 23:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-05 23:04 Henry Worth [this message]
2001-03-06  0:30 ` Pismo Aty128fb problem in 2.4.3-pre*? Henry Worth
2001-03-06 16:33 ` Henry Worth
2001-03-07 11:56   ` Michel Dänzer
2001-03-09  3:03     ` Henry Worth
2001-03-09 12:34       ` Michel Dänzer

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=3AA41B77.73470672@ncal.verio.com \
    --to=haworth@ncal.verio.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.