From: Sven Luther <sven.luther@wanadoo.fr>
To: Meelis Roos <mroos@linux.ee>
Cc: Sven Luther <sven.luther@wanadoo.fr>,
Tom Rini <trini@kernel.crashing.org>,
linuxppc-dev@ozlabs.org, Sven Hartge <hartge@ds9.gnuu.de>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christian Kujau <evil@g-house.de>
Subject: Re: [PATCH 2.6.10-rc3][PPC32] Fix Motorola PReP (PowerstackII Utah) PCI IRQ map
Date: Thu, 24 Feb 2005 18:01:50 +0100 [thread overview]
Message-ID: <20050224170150.GA7746@pegasos> (raw)
In-Reply-To: <Pine.SOC.4.61.0502241832510.21289@math.ut.ee>
On Thu, Feb 24, 2005 at 06:34:03PM +0200, Meelis Roos wrote:
> >Oh, damn, need to fix my daily builder, should be ok for tomorrow. IN the
> >meanwhile, you can try :
> >
> > http://people.debian.org/~luther/d-i/images/2005-02-23/powerpc/netboot/vmlinuz-prep.initrd
>
> This seems to work fine: onboard scsi is OK, pci nic with de4x5 is OK
> too. Haven't got more PCI cards in there currently.
Ok, can you now install the 2.6.10-3 package from :
http://people.debian.org/~luther/powerpc/2.6.10-3
(you need kernel-image-2.6.10-powerpc and mkvmlinuz), call mkvmlinuz on it (or
add it to kernel-img.conf as postinst_hook=/usr/sbin/mkvmlinuz).
You may probably want also to modify /etc/mkinitrd/mkinitrd:MODULES_DEP to dep
instead of MOST, or you may hit size problems with your initrd, i would be
interested in knowing that.
Then just dd your /boot/vmlinuz-2.6.10-powerpc to your prep partition, or
better yet to a tftp server, and try it out. If the scsi problems are there,
can you fill a bug report against kernel-source-2.6.10 ?
Friendly,
Sven Luther
next prev parent reply other threads:[~2005-02-24 17:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 18:54 [PATCH 2.6.10-rc3][PPC32] Fix Motorola PReP (PowerstackII Utah) PCI IRQ map Tom Rini
2005-02-22 8:36 ` Meelis Roos
2005-02-22 12:01 ` Sebastian Heutling
2005-02-22 12:23 ` Leigh Brown
2005-02-22 16:27 ` Christian Kujau
2005-02-22 18:27 ` Sebastian Heutling
2005-02-24 7:47 ` Sven Luther
2005-02-24 15:47 ` Meelis Roos
2005-02-24 16:06 ` Sven Luther
2005-02-24 16:34 ` Meelis Roos
2005-02-24 17:01 ` Sven Luther [this message]
2005-02-24 20:51 ` Meelis Roos
2005-02-25 0:24 ` Christian Kujau
2005-02-25 6:36 ` Sven Luther
2005-02-25 11:59 ` Christian
2005-02-25 12:15 ` Sven Luther
2005-02-26 3:39 ` Christian
2005-02-26 6:04 ` Sven Luther
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=20050224170150.GA7746@pegasos \
--to=sven.luther@wanadoo.fr \
--cc=evil@g-house.de \
--cc=hartge@ds9.gnuu.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mroos@linux.ee \
--cc=trini@kernel.crashing.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