From: Michael Lundkvist <ml@epact.se>
To: Matt Porter <mmporter@home.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Problems with linuxppc_2_2 on an MVME-2400
Date: 20 Aug 2000 15:49:20 +0200 [thread overview]
Message-ID: <qpaee8rqjj.fsf@erbium.epact.se> (raw)
In-Reply-To: Matt Porter's message of "Sun, 20 Aug 2000 06:15:53 -0700"
Matt Porter <mmporter@home.com> writes:
>
> The source used for that build can be retrieved from the Debian powerpc
> patch package at
> ftp://ftp.debian.org/pub/debian/dists/stable/main/binary-powerpc/devel/kernel-patch-2.2.15-powerpc_20000422-2.2.16pre4-1.deb
>
Ahhh. Dselect only showed me the 2.2.15 part.
> Note that it comes from a 22/04/2000 FSMLabs 2.2 tree. Use BK to "checkout
> for edit" files no later than 22/04/2000 in your rsynced version and you
> might find that things work. Source control _is_ useful. :)
>
Hmmm. I tried bk a bit but couldn't get it to give me a version from a
specific date.
> Oh, and one more possibility is that the unified IDE patch helped matters
> since I believe Dan J. ended up applying that to the Debian image builds.
> The exact patch used was ftp://ftp.debian.org/pub/debian/dists/stable/main/binary-powerpc/devel/kernel-patch-2.2.15-ide_20000405-1.deb
>
I tried these two patches. Using the
kernel-patch-2.2.15-powerpc_20000422-2.2.16pre4-1.deb gives me the
same result as before. Panic with moderate disk activity.
Using the kernel-patch-2.2.15-ide_20000405-1.deb I can't even boot.
I tried applying them both to a 2.2.15 kernel but that gives me too
many conflicts that I'm not smart enough to resolve.
/Micke
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-20 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-20 11:02 Problems with linuxppc_2_2 on an MVME-2400 Michael Lundkvist
2000-08-20 13:15 ` Matt Porter
2000-08-20 13:49 ` Michael Lundkvist [this message]
2000-08-20 16:08 ` Michael Lundkvist
2000-08-20 17:01 ` Daniel Jacobowitz
2000-08-20 18:55 ` Michael Lundkvist
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=qpaee8rqjj.fsf@erbium.epact.se \
--to=ml@epact.se \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mmporter@home.com \
/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).