All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Lundkvist <ml@epact.se>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Going from 2.2.12 to 2.2.17pre10
Date: 06 Jul 2000 19:32:49 +0200	[thread overview]
Message-ID: <qp66qji2pq.fsf@erbium.epact.se> (raw)
In-Reply-To: Gabriel Paubert's message of "Thu, 6 Jul 2000 19:17:46 +0200 (METDST)"


Gabriel Paubert <paubert@iram.es> writes:

> On 6 Jul 2000, Michael Lundkvist wrote:
>
> >
> > Please don't tell me my 2.2.12 partitioned disk is wrong. :)
>
> What's your version of fdisk ?

It seems like Hollis Blanchard was right so I'm doing a reinstall with
2.2.16 instead.

>
> Under 2.2.12 dd if=/dev/hda of=xxx bs=512 count=1 and see what comes out.
> Can PPCBUG actually boot from these disks ?
>

Nope. I think I'll go for Bugboot. Ramix also talked about the
possibility of modifying PPCBug to add support for the Ramix 233.

> >
> > Where do I go for the best LinuxPPC 2.4 kernel for MVME-boards? Is it
> > fsmlabs Bitkeeper repository?
>
> I have 2.4.0-test2 running on an MVME2600, look at:
>
> 	ftp://vlab1.iram.es/pub/linux-2.4
>
> did not try the MVME2400 yet (they are all in use for real tasks, I'm
> waiting for more and have to develop on the 16Mb MVME2600 :-(). But I
> only have SCSI disks or NFSRoot.
>

OK. I'll try that on a MVME2400.

We have ~25 MVME2400 just lying around here since they haven't been
able to get VxWorks working properly on them yet. :)

> I have a 2.2.16 kernel compiled but never booted, I could give you R/O
> access to my BK trees if you want (but the machine on which they are is
> not up 100% of the time).
>
> 	Gabriel.

How much difference is there between that and the main kernel?

The main reason I'm moving from the 2.2.12 is that it wasn't stable
under load on the MVME2400. I figured it was pointless to try to debug
it on an old kernel.

/Micke

--
ml@epact.se

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-07-06 17:32 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-06 13:27 Going from 2.2.12 to 2.2.17pre10 Michael Lundkvist
2000-07-06 13:54 ` Hollis Blanchard
2000-07-06 17:17 ` Gabriel Paubert
2000-07-06 17:32   ` Michael Lundkvist [this message]
2000-07-06 17:55     ` Gabriel Paubert
2000-07-06 22:23       ` Michael Lundkvist
2000-07-07  8:22         ` Gabriel Paubert
2000-07-07  8:55           ` Michael Lundkvist
2000-07-07  9:21             ` Gabriel Paubert
2000-07-07  9:47               ` Michael Lundkvist
2000-07-07 10:19                 ` Gabriel Paubert
2000-07-08  0:08                   ` Problem with de4x5 on an MVME-2400 Michael Lundkvist
2000-07-10 11:58                     ` Gabriel Paubert
2000-07-12 13:01                       ` Michael Lundkvist
2000-07-08 23:29     ` Going from 2.2.12 to 2.2.17pre10 Matt Porter
2000-07-09  6:12       ` Michael Lundkvist
2000-07-10  5:29         ` Matt Porter
2000-07-10 12:25           ` Gabriel Paubert
2000-07-11  5:57             ` Matt Porter
2000-07-11  9:37               ` Adrian Cox
2000-07-11 10:17                 ` Benjamin Herrenschmidt
2000-07-11 12:57                   ` Adrian Cox
2000-07-11 14:10                     ` Claus
2000-07-11 19:15                     ` Geert Uytterhoeven
2000-07-12 13:31                       ` Benjamin Herrenschmidt
2000-07-13 11:17                         ` Geert Uytterhoeven
2000-07-12  9:11                     ` Timothy A. Seufert
2000-07-12 14:16                 ` Matt Porter
2000-07-13 11:43                   ` Gabriel Paubert
2000-07-13 14:12                     ` Matt Porter
2000-07-12 12:52           ` Michael Lundkvist
2000-07-12 14:17             ` Matt Porter
2000-07-10 12:12       ` Gabriel Paubert
2000-07-11  6:12         ` Matt Porter
2000-07-11 10:48           ` Gabriel Paubert

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=qp66qji2pq.fsf@erbium.epact.se \
    --to=ml@epact.se \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.