From: "Jim Somerville" <somer@nortelnetworks.com>
To: Gabriel Paubert <paubert@iram.es>
Cc: linuxppc-dev@lists.linuxppc.org, valette@crf.canon.fr,
"Corey Minyard" <minyard@nortelnetworks.com>
Subject: Re: MCP750 and CPX2000 System Scsi Woes
Date: Fri, 15 Jan 1999 17:40:47 -0500 (EST) [thread overview]
Message-ID: <199901152240.QAA07784@lists.linuxppc.org> (raw)
In message "Re: MCP750 and CPX2000 System Scsi Woes",
"Gabriel Paubert" <paubert@iram.es> writes:
>Not very surprising, which is the actual interrupt used for SCSI
>(it should be in the doc and in the residual data).
>
>Tell me if the zImage-2.2.0-pre5 on ftp://vcorr1.iram.es/pub/ works
>better. Early boot messages will be different and it will try to use
>the OpenPIC (that's the image running on my MVME2600 right now).
>I'm completely reorganizing my source code and patches, hopefully
>I'll be able to make it available during the week-end.
Gabriel, it worked! SCSI devices were found successfully. It died at the
end trying to mount the non-existent root partition. If you have a
ramdisk image that contains an installer, it would be appreciated. :-)
I'll look for your source on Monday.
Thanks again,
-Jim
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next reply other threads:[~1999-01-15 22:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-15 22:40 Jim Somerville [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-01-14 22:59 MCP750 and CPX2000 System Scsi Woes Jim Somerville
1999-01-15 2:42 ` Gabriel Paubert
1999-01-15 8:35 ` VALETTE Eric
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=199901152240.QAA07784@lists.linuxppc.org \
--to=somer@nortelnetworks.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=minyard@nortelnetworks.com \
--cc=paubert@iram.es \
--cc=valette@crf.canon.fr \
/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).