linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ethan Benson <erbenson@alaska.net>
To: Matt McLean <keys@yikes.com>
Cc: Debian-PowerPC <debian-powerpc@lists.debian.org>,
	Linux/PPC-devel <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Paul's 2.2.15 does not boot a 7200
Date: Sat, 20 May 2000 18:17:06 -0800	[thread overview]
Message-ID: <20000520181706.F7243@plato.local.lan> (raw)
In-Reply-To: <Pine.BSF.4.21.0005201535200.59827-100000@nerf.yikes.com>; from keys@yikes.com on Sat, May 20, 2000 at 03:38:37PM -0700

[-- Attachment #1: Type: text/plain, Size: 925 bytes --]

On Sat, May 20, 2000 at 03:38:37PM -0700, Matt McLean wrote:
> Hey,
> 
> That sounds like it's not recognizing your onboard video...

would that cause the kernel to fail to boot entirely?  the machine
never becomes pingable, sshable, nor does it dial ppp at boot like it
usually does.  

> Be sure you have CONFIG_FB, CONFIG_FB_OF, and CONFIG_FB_PLATINUM set to
> yes in your kernel config...

yup, my .config is available on request, i did not want to spam the
list with such a large file.  besides i tried using paul's config
included in his rsync tree as well, it failed too, the exact same way...

> Otherwise, do you have a strange CPU upgrade?  Did earlier versions of
> Paul's kernel work on your machine?

no and yes, the machine is perfectly stock except for having more
ram.  and paul's 2.2.14 works on it (that is what it is running now)

-- 
Ethan Benson
http://www.alaska.net/~erbenson/

[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]

      reply	other threads:[~2000-05-21  2:17 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
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 [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=20000520181706.F7243@plato.local.lan \
    --to=erbenson@alaska.net \
    --cc=debian-powerpc@lists.debian.org \
    --cc=keys@yikes.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 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).