public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Kujau <evil@g-house.de>
To: sheutlin@gmx.de
Cc: linuxppc-dev@ozlabs.org,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Sven Hartge <hartge@ds9.argh.org>
Subject: Re: [FYI] linux 2.6 still not working with PReP (ppc32)
Date: Sun, 05 Dec 2004 18:41:55 +0100	[thread overview]
Message-ID: <41B34863.3090007@g-house.de> (raw)
In-Reply-To: <1102207299.6778.16.camel@weizen.left.earth>

[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sebastian Heutling schrieb:
> You got the powerstack booting from scsi (reading and interpreting the

yes, but now the disk is gone and i have to use nfsroot.

> bug report). I had problems booting 2.6 kernels as well (never tested
> any 2.5 kernels). It turned out that the pci slot numbering has changed
> sometime and this wasn't reflected in arch/ppc/platforms/prep_pci.c.
> After having set up the slot0...slot8 using the values of
> slot10...slot18 (except for slot1 which got value 4 so IDE is usable out
> of the box), the machine booted a 2.6 kernel (2.6.8).

boy! this *is* an early christmas present, for sure! how did you come to
this conclusion? something *must* have changed in the pci setup after
2.5.30, because the problem did not go away when i used a different NIC
driver. but i could not fiddle out the changeset to blame here, because i
failed to compile many kernels > 2.5.30.

changing one line in arch/ppc/platforms/prep_pci.c made my PReP booting a
recent 2.6-BK, patch attached.

it's booting now, "init=/bin/bash" is working, but i still can't ping to
the outside world, which is still a bit strange, but i hope i can work it out.

tausend dank (really),
Christian.
- --
BOFH excuse #304:

routing problems on the neural net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBs0hj+A7rjkF8z0wRAo3RAKDF+QYA6cosLH+kWtiAmiWtRzlQkQCeKcpx
FXOiNRfl9/vOynE8d4hDJJg=
=sKOm
-----END PGP SIGNATURE-----

[-- Attachment #2: prep_pci_2.6.10-rc2.patch --]
[-- Type: text/x-patch, Size: 499 bytes --]

--- linux-2.5-PPC-BK/arch/ppc/platforms/prep_pci.c	2004-12-05 18:20:04.000000000 +0100
+++ linux-2.5-PPC-BK/arch/ppc/platforms/prep_pci.c.edited	2004-12-05 18:21:33.000000000 +0100
@@ -61,7 +61,7 @@
         0,   /* Slot 11 - unused */
         5,   /* Slot 12 - SCSI - NCR825A */
         0,   /* Slot 13 - unused */
-        3,   /* Slot 14 - enet */
+        1,   /* Slot 14 - enet */
         0,   /* Slot 15 - unused */
         2,   /* Slot 16 - unused */
         3,   /* Slot 17 - unused */

  parent reply	other threads:[~2004-12-05 17:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-04 22:45 [FYI] linux 2.6 still not working with PReP (ppc32) Christian Kujau
     [not found] ` <1102207299.6778.16.camel@weizen.left.earth>
2004-12-05 17:41   ` Christian Kujau [this message]
2004-12-06  1:46     ` Sebastian Heutling
2004-12-05 19:57   ` [PATCH] linux 2.6 not^Wnow " Christian Kujau
2004-12-06 18:49     ` Tom Rini

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=41B34863.3090007@g-house.de \
    --to=evil@g-house.de \
    --cc=hartge@ds9.argh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sheutlin@gmx.de \
    /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