From: Ryan Bradetich <rbradetich@uswest.net>
To: Phil Anderson <andersop@neverland.ncssm.edu>
Cc: palinux <parisc-linux@lists.parisc-linux.org>
Subject: Re: 735 and SCSI (was: Re: [parisc-linux] Firmware upgraded, STI console problem)
Date: 16 Dec 2001 22:43:13 -0700 [thread overview]
Message-ID: <1008567794.533.9.camel@beavis> (raw)
In-Reply-To: <Pine.LNX.4.33.0112141351590.31282-100000@bob.ncssm.edu>
On Fri, 2001-12-14 at 11:58, Phil Anderson wrote:
> On 13 Dec 2001, Ryan Bradetich wrote:
>
> > On Wed, 2001-12-12 at 22:20, Matthew Wilcox wrote:
> > > On Wed, Dec 12, 2001 at 07:41:57PM -0900, Tom wrote:
> > > > By all means, feel free to post corrections, either here or direct to
> > > > me, and I'll update it. Also, if someone can think of something else
> > > > useful for it, just ask... (Perhaps the minimum kernel revision needed?)
> > >
> > > E, F, G, H, I class aren't supported straight off the CD; they require
> > > additional changes, AIUI. Not to mention no support for their SCSI
> > > adapters. K mostly works... similar problems to E. D & R should work
> > > fine (problem with D class with remote management console). 735's FWDiff
> > > scsi doesn't work.
> >
> > 755 has the same FWDiff as the 735 (outfield) so it doesn't work either.
>
>
> So that would explain why none my 735's can detect hard drives.
>
> I can boot off a CD on the regular scsi, and even though the boot_admin
> will detect my disks debian won't.
>
> so has _anyone_ gotten a 735 working or anything? I have 7 of them that
> are taking up space in my dorm room, and two 755's under the desk that
> server the same purpose...
Yes, I tested an early 0.9.3-rc image on the 755 using a single ended
disk on the 755. The Hardball ERS is published at:
http://parisc-linux.org/documentation/index.html
if you are interested in taking a stab at getting the FW scsi working :)
- Ryan
> -phil
>
>
>
>
>
>
> >
> > - Ryan
> >
> > > --
> > > Revolutions do not require corporate support.
> > >
> > > _______________________________________________
> > > parisc-linux mailing list
> > > parisc-linux@lists.parisc-linux.org
> > > http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
> > >
> >
> >
> >
> > _______________________________________________
> > parisc-linux mailing list
> > parisc-linux@lists.parisc-linux.org
> > http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
> >
>
> --
> ===============================================================================
>
> Phil Anderson
> UNIX Systems Administrator
> andersop@neverland.ncssm.edu
> The_13th_Ewok@hotmail.com
>
> "Go CRAZY? Don't mind if I do! Woowoowoowoo!" -Homer Simpson
>
>
prev parent reply other threads:[~2001-12-17 5:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 19:34 [parisc-linux] Firmware upgraded, STI console problem James P. Kinney III
2001-12-12 19:57 ` Matthew Wilcox
2001-12-12 20:39 ` Grant Grundler
2001-12-12 20:50 ` Tom
2001-12-12 21:02 ` Matthew Wilcox
[not found] ` <1008218517.2031.1.camel@crudball>
2001-12-13 5:20 ` Matthew Wilcox
2001-12-13 14:21 ` Ryan Bradetich
2001-12-14 18:58 ` 735 and SCSI (was: Re: [parisc-linux] Firmware upgraded, STI console problem) Phil Anderson
2001-12-14 22:55 ` Richard Hirst
2001-12-17 5:43 ` Ryan Bradetich [this message]
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=1008567794.533.9.camel@beavis \
--to=rbradetich@uswest.net \
--cc=andersop@neverland.ncssm.edu \
--cc=parisc-linux@lists.parisc-linux.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