From: Olaf Hering <olh@suse.de>
To: Michel Lanners <mlan@cpu.lu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: TiBook powers off on boot
Date: Thu, 9 Aug 2001 10:42:50 +0200 [thread overview]
Message-ID: <20010809104250.B25806@suse.de> (raw)
In-Reply-To: <200108090601.IAA00745@piglet.grunz.lu>; from mlan@cpu.lu on Thu, Aug 09, 2001 at 08:01:43AM +0200
On Thu, Aug 09, Michel Lanners wrote:
> With BenH's latest tree (rsync from two or three days ago), my TiBook
> powers off on boot. The last thing I see on display is the firewire
> thing intializing; after that it just goes 'poof' and it's off.
>
> Also, when this happens, it seems the hardware clock is reset. Next
> boot, it's at 1904...
>
> >From both descriptions I'd say soething scribbles over the PMU memory
> area. Anybody know more?
Firewire is broken since 2.4.7-pre8, so turn it off until it is fixed ;)
If you need a working firewire tree:
/mirror/SuSE/ftp.suse.com/pub/suse/ppc/kernel/BETA/sleep/
Gruss Olaf
--
$ man clone
BUGS
Main feature not yet implemented...
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-08-09 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 6:01 TiBook powers off on boot Michel Lanners
2001-08-09 8:42 ` Olaf Hering [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=20010809104250.B25806@suse.de \
--to=olh@suse.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mlan@cpu.lu \
/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).