From: Sven Luther <sven.luther@wanadoo.fr>
To: Sebastian Heutling <sheutlin@gmx.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [FYI] linux 2.6 still not working with PReP (ppc32)
Date: Mon, 10 Jan 2005 07:34:59 +0100 [thread overview]
Message-ID: <20050110063459.GA22078@pegasos> (raw)
In-Reply-To: <41E1BBA2.30008@gmx.de>
On Mon, Jan 10, 2005 at 12:17:54AM +0100, Sebastian Heutling wrote:
> Marc Dietrich wrote:
>
> >Hi all,
> >
> >I didn't recognise that the kernel from Sebastian - which was working fine
> >here - was build from the debian sources (no hint in the kernel version).
> >So I build everything again from debian source and fixed the irq's in
> >prep_pci.c.
> >
> >
> Erm ... well ... yes - it's a debian kernel ;).
Notice that 2.6.8-9, currently in unstable, has this patch, as well as the d-i
image which will be built in a few hours. The same goes for 2.6.9-4, which i
am uploading and should be in unstable tomorrow evening. For d-i, we have to
wait for the 2.6.8-9 kernel to enter testing so it is fully operational. In
the meantime, you have to :
1) when you reach partman, you have to switch to console 2, or go back unto
the main menu and chose shell console if on serial console, and run parted by
hand and create the prep-boot partition (set 1 prep on). An 8MB prep partition
would be ideal.
2) you *have* to use /dev/hda3 as /. The debian kernel is configured for that,
and there is not yet a way to modify this.
3) after base-install, you will get the no bootloader message, telling you the
root path, there you have to go into a shell again, chroot to /target, and
wget the unstable 2.6.8-9 kernel (or othrwise apt-get it, but this needs
modifying the /etc/apt/sources.list to include unstable).
4) once the kernel is installed, you exit the chroot, and simply need to dd
the kernel to the prep partition with :
# dd if=/target/boot/vmlinuz-2.6.8-powerpc of=/dev/scsi/host3/bus0/target0/lun0/part1
(or whatever your disk is, in devfs paths).
You have to use the daily-builds d-i images, not RC2 obviously. All these
steps will be made unnecessary once the 2.6.8-9 kernel makes it to testing (in
2-3 days), and i upload both partman-prep (which allow to set the prep
partition in partman), and prep-installer (which takes care of dd-ing the
kernel).
2.6.10 powerpc kernels will follow, but they may be some time in the NEW
queue.
> >I can confirm now, that this debian+irq_fix kernel 2.6.8 runs fine and
> >produces no scsi timeouts!
> >
> >Something happend in kernels >= 2.6.9 which makes the scsi unusable. Also
> >it seems, that even in 2.6.8 kernels and with ide hard disks (Sebastians
> >setup) the scsi controller timeouts, but continues to operate - correct?
> >
> >
>
> Yep correct.
> I also tried the 2.6.10 and found out that it doesn't work here as well.
> First I get a lot of lost interrupts from the IDE driver and after that
> I also get the SCSI timeouts. It must have something to do with the prep
> changes in 2.6.9. One difference in IRQ setup I noticed is in
> prep_pcibios_fixup(). If I remember correctly before 2.6.9 at least on
> this Utah machine the IRQs are assigned from Motherboard_routes[]
> without doing anything else. Now additionally the IRQ is also written
> into the devices pci config space which might not work on the
> PowerstackII Utah.
> It's only a guess and I haven't had the time yet to test it.
Can you try the debian kernels i upload and fill bugreports against them ?
Friendly,
Sven Luther
next prev parent reply other threads:[~2005-01-10 6:25 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-26 13:35 [FYI] linux 2.6 still not working with PReP (ppc32) Marc Dietrich
2004-12-27 2:47 ` Christian
2004-12-27 21:37 ` Marc Dietrich
2005-01-02 0:31 ` Sebastian Heutling
2005-01-03 12:26 ` Marc Dietrich
2005-01-04 0:54 ` evilninja
2005-01-04 11:31 ` Sebastian Heutling
2005-01-04 14:04 ` Marc Dietrich
2005-01-04 14:42 ` Sebastian Heutling
[not found] ` <1104850036.6164.25.camel@weizen.left.earth>
2005-01-05 11:33 ` Marc Dietrich
2005-01-05 15:47 ` Sven Luther
2005-01-05 17:10 ` Christian
2005-01-05 17:39 ` Sven Luther
2005-01-06 16:00 ` Christian
2005-01-06 16:27 ` Sven Luther
2005-01-06 20:27 ` Christian
2005-01-06 21:07 ` Sven Luther
2005-01-06 21:21 ` Christian
2005-01-06 21:49 ` Sven Luther
2004-12-31 9:55 ` Sven Luther
2004-12-31 15:00 ` Sebastian Heutling
2004-12-31 22:28 ` Sven Luther
2005-01-01 23:56 ` Sebastian Heutling
2005-01-02 9:39 ` Sven Luther
2005-01-02 21:33 ` Sebastian Heutling
[not found] ` <200501051733.06350.marvin24@gmx.de>
[not found] ` <20050105165551.GA29287@pegasos>
2005-01-05 20:57 ` Marc Dietrich
2005-01-09 23:17 ` Sebastian Heutling
2005-01-10 6:34 ` Sven Luther [this message]
2005-01-10 15:19 ` Sebastian Heutling
2005-01-10 6:54 ` Sven Luther
-- strict thread matches above, loose matches on Subject: below --
2005-01-04 2:12 Christian
2005-01-04 13:23 ` Marc Dietrich
2005-01-04 15:08 ` Christian
2004-12-04 22:45 Christian Kujau
2004-12-05 0:41 ` Sebastian Heutling
2004-12-05 17:41 ` Christian Kujau
2004-12-06 1:46 ` Sebastian Heutling
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=20050110063459.GA22078@pegasos \
--to=sven.luther@wanadoo.fr \
--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;
as well as URLs for NNTP newsgroup(s).