linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Daniel Egger <degger@fhm.edu>
Cc: Dustin Lang <dalang@cs.ubc.ca>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Re:No backlight control on PowerBook G4
Date: Sun, 09 Nov 2003 13:59:53 +1100	[thread overview]
Message-ID: <1068346792.673.25.camel@gaston> (raw)
In-Reply-To: <1068198639.796.109.camel@sonja>

On Fri, 2003-11-07 at 20:50, Daniel Egger wrote:
> Am Don, den 06.11.2003 schrieb Benjamin Herrenschmidt um 01:28:
> 
> > No, I told you to use _my_ 2.6 tree which contains a new radeonfb
> > that have not yet been merged upstream.
> 
> Still cannot try this because your kernel wouldn't even survive yaboot.

Can you give details ? It should work just fine, except if I broke
something in the past few days when getting G5 support in, but I didn't
have any other report of this, so...

> With your tree I now have the problem that it doesn't even boot anymore.
> The CHRP kernel which worked before stopped after "CHRP kernel
> loader...", the elf-pmac one still crashes with:
> Elf32 kernel loaded...
> chrpboot starting: loaded at 0x01000000
> heap at 0x00003000
> gunzipping (0x00010000 <- 0x01006cf8:0x01155486)...
> Decrementer exception at %SRR0: 01005804   %SRR1: 00003030
>  ok
> 0 >

Well, you are not supposed to use the zImage.chrp on a PowerMac,
and definitely not from yaboot.

It may have altered some open firmware settings in a bad way.
I suggest you reset your nvram first (hopefully, booting with
cmd-opt-P-R will do the trick).

Last I tried, then just netbooting vmlinux.elf-pmac worked fine
on all the "newworld" models I have here). For yaboot, you need
to load a plain vmlinux binary.

Ben.


  reply	other threads:[~2003-11-09  3:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-02 19:23 No backlight control on PowerBook G4 Dustin Lang
2003-11-03  0:45 ` Benjamin Herrenschmidt
2003-11-03  8:51   ` Dustin Lang
2003-11-03  9:04     ` Benjamin Herrenschmidt
2003-11-03 16:57   ` Daniel Egger
2003-11-03 21:54     ` Benjamin Herrenschmidt
2003-11-04 10:43       ` Daniel Egger
2003-11-04 20:05       ` Daniel Egger
2003-11-06  0:28         ` Benjamin Herrenschmidt
2003-11-06  8:01           ` Daniel Egger
2003-11-06  8:16             ` Dustin Lang
2003-11-06  8:26             ` Benjamin Herrenschmidt
2003-11-06  9:36               ` Daniel Egger
2003-11-07  9:50           ` Daniel Egger
2003-11-09  2:59             ` Benjamin Herrenschmidt [this message]
2003-11-09  9:55               ` Daniel Egger
2003-11-09 11:03                 ` Benjamin Herrenschmidt

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=1068346792.673.25.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=dalang@cs.ubc.ca \
    --cc=degger@fhm.edu \
    --cc=linux-kernel@vger.kernel.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).