linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andreas <toa@pop.agri.ch>
To: Dev-LinuxPPC <linuxppc-dev@lists.linuxppc.org>
Subject: atyfb and Powerbook G3 250 (wallstreet)
Date: Mon, 17 May 1999 20:48:00 +0200	[thread overview]
Message-ID: <37406460.9B171AC8@pop.agri.ch> (raw)


Hello,

last week I got my Wallstreet G3 250 back from repair. They changed
CPU-Board, Chache, Flex Cable and the Display. Don't know why. On the
MacOS all works ok so far.
Then I tried LinuxPPC kernel 2.2.6 with no video driver off -> should
use atyfb.
I worked for half an hour on the text mode trying to build one of the
latest kernel. After this half hour the screen went into unreadable
chars. As usual I thought nothing bad and did a reboot. Same situation
even worse. Changed back to kernel 2.2.4, same behaviour. Then I checked
the option no video driver. Huh, the book came in readable chars up. At
least the console modus works. I then shutdown because I'm very unsure now.

I was working with PB and Linux for quite a long time with different
kernels. Since BootX gives the option to enter kernel options I did. I
set video=atyfb vmode:14,cmode:32 and mclk=63.

Now I don't know if I hurt the book with this Linux or do I have a ***
book which  is very affective on things like that.

Does anybody had symptoms like that? Do I have set something wrong?

Any hints are appreciated,

thanks
Andreas

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

                 reply	other threads:[~1999-05-17 18:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=37406460.9B171AC8@pop.agri.ch \
    --to=toa@pop.agri.ch \
    --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).