From: Steven Hanley <sjh@wibble.net>
To: Ethan Benson <erbenson@alaska.net>,
Linux PPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Paul's 2.2.15 does not boot a 7200
Date: Sun, 21 May 2000 00:37:07 +1000 [thread overview]
Message-ID: <3926A313.3AB13BBA@wibble.net> (raw)
In-Reply-To: 20000520002947.A6452@plato.local.lan
Ethan
I think it may actually be booting, if it is hooked up to a netwrok try
pinging it or sshing into it, I also had this problem with the 2.2.14
pre series from linuxcare on my 7200/200 with a normal atyfb, the
problem was the thing's video was blank after the bootx sequence
finished loding it and the kernal ran. 2.2.10 was fine so I wanted to
know what the problem with the graphics was/is, it seems some change in
2.2.* recently made it detect the graphics capabilities incorectly and
not use the right mode.
so the fix is to put something like video=atyfb:vmode:5 on the kernel
command line and it will boot with text displauyed, I still am somewhat
annmoyed as 2.2.10 the thing auto detected and displayed 100x40 or osme
similarly sized mode, and now it only does 80x50, which I find way too
large (even on the 14" monitor I have with this machine (heck I happily
run 160x60 console on 15" monitors on my x86 boxen)
Anyway try forcing a specific video mode ont he kernel command line and
you may get a display. I was able to work with the machine with no
display quite happily using only ssh and such and was thus able to try
different kernels.
See You
Steve
--
sjh@wibble.net http://wibble.net/~sjh/
Look Up In The Sky
Is it a bird? No
Is it a plane? No
Is it a small blue banana?
YES
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-05-20 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-20 8:29 Paul's 2.2.15 does not boot a 7200 Ethan Benson
2000-05-20 14:37 ` Steven Hanley [this message]
2000-05-20 14:45 ` Ethan Benson
2000-05-20 16:04 ` Andreas Tobler
2000-05-20 22:38 ` Matt McLean
2000-05-21 2:17 ` Ethan Benson
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=3926A313.3AB13BBA@wibble.net \
--to=sjh@wibble.net \
--cc=erbenson@alaska.net \
--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).