From: Stefan Jeglinski <jeglin@4pi.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: whacked out 2.2.18pre17?
Date: Fri, 3 Nov 2000 00:53:40 -0500 [thread overview]
Message-ID: <p04330100b627ff09296b@[192.168.0.1]> (raw)
I have a PowerTowerPro with a 500/1M PowerLogix G3 upgrade, have been
running Paul's 2.2.17 linux-pmac-stable for a while now (originally
rsynced from penguinppc.org), with great success, using BootX 1.1.3.
But for the last 4 nights I've been trying to run 2.2.18pre17 (also
rsynced from penguinppc.org) with no luck. The compile always
succeeds (just a vanilla compile, no changes to the default config),
but I either cannot boot completely, or the boot completes but is
seriously messed up.
The first night, all it would do is freeze at "booting..."
The second night, it booted, but the no video checkbox was somehow
inverted in operation. IOW, with no video turned on (I have a twin
turbo card, OFfb is my only choice in running X), I never get the
OFfb driver, it always insists on loading the imsttfb driver, so X is
impossible.
Last night, the video anomaly was still in effect, but the boot never
completed (kernel panic after an error that I cannot recall to save
me now)
Tonight, again the video anomaly is also still in effect, but the
boot never completes again, however for a different reason (kernel
panic after "machine check in kernel mode" which leads to the message
"unknown values in srr1").
I am aware that this kernel is being worked on daily (that's why I
try to rebuild it each night), but I'm a little surprised that I am
having so much trouble with a pre17 kernel. Anybody know what's up?
Is this thing going through such big changes that I should let it go
for a while instead of trying each night?
Stefan Jeglinski
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-11-03 5:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-03 5:53 Stefan Jeglinski [this message]
2000-11-03 15:56 ` whacked out 2.2.18pre17? Benjamin Herrenschmidt
2000-11-04 6:03 ` Stefan Jeglinski
2000-11-04 12:47 ` Benjamin Herrenschmidt
2000-11-04 15:55 ` Stefan Jeglinski
2000-11-05 9:36 ` Michel Lanners
2000-11-05 22:59 ` Stefan Jeglinski
2000-11-06 7:12 ` Michel Lanners
2000-11-18 3:12 ` whacked out 2.2.18pre21? Stefan Jeglinski
2000-11-18 20:03 ` Stefan Jeglinski
2000-11-18 20:09 ` aic7xxx panic in 2.2.18pre21 Hollis R Blanchard
2000-11-18 21:33 ` Stefan Jeglinski
2000-11-10 6:58 ` whacked out 2.2.18pre17? [partly solved] Stefan Jeglinski
2000-11-03 23:52 ` whacked out 2.2.18pre17? Tony Mantler
2000-11-04 1:15 ` Stefan Jeglinski
2000-11-04 2:01 ` Tony Mantler
2000-11-04 12:35 ` Simon Piette
2000-11-04 15:32 ` Tony Mantler
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='p04330100b627ff09296b@[192.168.0.1]' \
--to=jeglin@4pi.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).