linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Heutling <sheutlin@gmx.de>
To: Marc Dietrich <marvin24@gmx.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [FYI] linux 2.6 still not working with PReP (ppc32)
Date: Tue, 04 Jan 2005 15:42:54 +0100	[thread overview]
Message-ID: <1104849774.6164.19.camel@weizen.left.earth> (raw)
In-Reply-To: <200501041504.57588.marvin24@gmx.de>

On Tue, 2005-01-04 at 15:04 +0100, Marc Dietrich wrote:
> Hallo Sebastian,
> 
> Am Dienstag, 4. Januar 2005 12:31 schrieben Sie:
> > Hello Marc,
> >
> > Marc Dietrich wrote:
> > >Hi Christian,
> >
> > Erm ... I'm Sebastian ;-)
> 
> ah! - sorry Sebastian, to many confusion in the last time...

Hehe :)


> 
> > I am using a 2.6.8 (I was too lazy to patch & compile a 2.6.9 and wanted
> > to test 2.6.10 when it's (the sources) in debian/unstable).
> >
> > >Can you put a working zImage.prep somewhere on the web (<1.44 MB, so I can
> > >write it to a floppy disk)?
> >
> > I will do that and tell you later where you can download it.
> 
> This may no longer be necessary, but see below.
> 
> Acording to your log, your scsi drive also fails later, but boots from ide 
> (how did you managed to install the ide disks?).

Yep, it fails later but it doesn't boot from IDE. The SCSI disk is
recognized correctly and the system is on the SCSI drive. The IDE disks
only contain data. It fails later that is right but it still works after
failure.
Making IDE work was easy. A friend soldered the connectors and then I
passed "ide0=ide0=0x1f0,0x3f6,14" as kernel parameter to make channel 0
work. Later on after, discovering what was wrong with 2.6 kernels, I
enabled the correct interrupt in the appropriate table in prep_pci.c.

> 
> I posted a message to linux-scsi describing this problem. I guess the sym2 
> driver never worked on the PReP machines. I tried it also with 2.4 kernels. 
> 
> So to summerize it: No one has a working Powerstack with 2.6 kernel and 
> booting from SCSI. I hope there will be some input from the scsi list.

As said above, it does really work although I have to admit there is a
problem with PCI or IRQ handling in general. You can also see in my log
that one of the ethernet devices has problems every now and then. All in
all it is sort of functional.
You can also try to remove every additional PCI device except the gfx
card and see what happens. I had to remove an additional SCSI host
controller in order to avoid problems with other PCI devices (mostly it
was one of the ethernet devices which lost an interrupt).
But I share your thoughts that there is something wrong with the sym2
driver.


> 
> > >How does your boot.log looks like?
> >
> > Attached it.
> > Note that I use a Matrox MilleniumII gfx card and XFree4 runs fine
> > (without any crash) since I got a 2.6 kernel running (although I am not
> > using XFree because I use the Powerstack as a router/server which has no
> > Monitor).
> 
> Yeah - I search so many times for a Millenium card on eBay. Now I got one for 
> EUR 1.00 but  it is in Germany, while I'm in France now for holidays :-(
> I also have a P9100 here, but it is not supported (yet?) under linux...

:(


Sebastian

  reply	other threads:[~2005-01-04 14:43 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 [this message]
     [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
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=1104849774.6164.19.camel@weizen.left.earth \
    --to=sheutlin@gmx.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=marvin24@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).