[parisc-linux] FW SCSI on the D350

[parisc-linux] FW SCSI on the D350

[Hamish Moffatt]

Hi,

I'm trying to install the 0.9 release on a D350 server. The kernel
recognises the standard SCSI, using the lasi7xxx driver, and finds
the tape drive and the CD-ROM on that host. However, it doesn't
find the Bluefish fast/wide SCSI host, so it doesn't find the
four internal hard disks, which makes installation a little tough.

The boot-up firmware recognises all of the disks OK, but the Bluefish
is just not included in the device list shown at startup/dmesg.

I'll try the 0.9.2 release tomorrow. Any other things I can do
which might help?


thanks,
Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

Re: [parisc-linux] FW SCSI on the D350

[Albert Strasheim]

[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]

Hello,

When in doubt, boot a brand-new kernel. :-)

I suggest downloading the latest CVS snapshot from
puffin.external.hp.com, then cross-compile it according to the
instructions on http://parisc-linux.org/. Basically just add the
xc-latest.tar.gz (the cross-compiler) binaries to your path, then make
mrproper; make oldconfig (possibly making some changes here...
someone?), make dep, make clean, make palo.

Now, grab the latest Debian root.bin, and do the following:

 palo -f /dev/null -k vmlinux -r root.bin -s lifimage \
        -c "0/linux HOME=/ root=/dev/ram initrd=0/ramdisk"

(and perhaps -b iplbool)

where vmlinux is the new kernel you compiled, root.bin is the latest
Debian HPPA root disk) and lifimage is the lifimage make palo made.

Now merrily netboot this lifimage and try installing from the CD (or
network perhaps).

Assuming it works, you'll need to overwrite the kernel the installer 
drops in /boot with your new vmlinux, or rerun palo without the
root.bin and initrd parts, and with root=/dev/sdaN and netboot that 
kernel.

Did I miss anything?

Regards,

Albert

P.S. Thanks to Richard Hirst who provided me with much of this
information on a prior occasion.

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: [parisc-linux] FW SCSI on the D350

[Grant Grundler]

Hamish Moffatt wrote:
> 
> Hi,
> 
> I'm trying to install the 0.9 release on a D350 server. The kernel
> recognises the standard SCSI, using the lasi7xxx driver, and finds
> the tape drive and the CD-ROM on that host. However, it doesn't
> find the Bluefish fast/wide SCSI host, so it doesn't find the
> four internal hard disks, which makes installation a little tough.

The D-class is very similar to Cxxx - ie it has U2 or Uturn in it.
parisc-linux currently only supports GSC devices below the first IOMMU.
Ryan Bradetich is working on "I/O tree" support to enable support
for multiple IOMMUs - then we should be able to walk additional
GSC busses and find more devices.

> The boot-up firmware recognises all of the disks OK, but the Bluefish
> is just not included in the device list shown at startup/dmesg.

Probably because GSC bus with your Bluefish (FWD SCSI) isn't being walked.
That's something Ryan wants to fix once IOtree support is at least
sort-of working.

> I'll try the 0.9.2 release tomorrow. Any other things I can do
> which might help?

Send Ryan cash. ;^)
(Just kidding...)

grant

Re: [parisc-linux] FW SCSI on the D350

[Ryan Bradetich]

On Thu, Sep 27, 2001 at 11:41:28PM -0600, Grant Grundler wrote:
> Hamish Moffatt wrote:
> > 
> > Hi,
> > 
> > I'm trying to install the 0.9 release on a D350 server. The kernel
> > recognises the standard SCSI, using the lasi7xxx driver, and finds
> > the tape drive and the CD-ROM on that host. However, it doesn't
> > find the Bluefish fast/wide SCSI host, so it doesn't find the
> > four internal hard disks, which makes installation a little tough.

You need a newer kernel, and you should be able to see the SCSI
card.  I'm not sure which -pa?? kernel, so just grab CVS head and
that should be sufficient.

> The D-class is very similar to Cxxx - ie it has U2 or Uturn in it.
> parisc-linux currently only supports GSC devices below the first IOMMU.
> Ryan Bradetich is working on "I/O tree" support to enable support
> for multiple IOMMUs - then we should be able to walk additional
> GSC busses and find more devices.

The code is in to detect the card under the "other" IOMMU, but if any
dma is performed on the "other" GSC bus, it will HPMC the machine.  As
Grant said, I have been working on the I/O tree to fix the problem, and
am getting close to having it working for SYSTEM_MAP firmware.

> > The boot-up firmware recognises all of the disks OK, but the Bluefish
> > is just not included in the device list shown at startup/dmesg.

LaMont Jones saw this same behavior on the J200.  Firmware reports the
Bluefish card for me on the C200.  In one of the Later kernel I committed
the support to walk the GSC busses uner ccio so LaMont could boot the
J200.  This should also work for you.

> Probably because GSC bus with your Bluefish (FWD SCSI) isn't being walked.
> That's something Ryan wants to fix once IOtree support is at least
> sort-of working.
> 
> > I'll try the 0.9.2 release tomorrow. Any other things I can do
> > which might help?

I do not think the 0.9.2 release is new enough, try the CVS head
kernel.

> Send Ryan cash. ;^)
> (Just kidding...)

:)

- Ryan

Re: [parisc-linux] FW SCSI on the D350

[Hamish Moffatt]

On Fri, Sep 28, 2001 at 01:05:18AM -0600, Ryan Bradetich wrote:
> > Hamish Moffatt wrote:
> > > I'm trying to install the 0.9 release on a D350 server. The kernel
> > > recognises the standard SCSI, using the lasi7xxx driver, and finds
> > > the tape drive and the CD-ROM on that host. However, it doesn't
> > > find the Bluefish fast/wide SCSI host, so it doesn't find the
> > > four internal hard disks, which makes installation a little tough.
> 
> You need a newer kernel, and you should be able to see the SCSI
> card.  I'm not sure which -pa?? kernel, so just grab CVS head and
> that should be sufficient.

I got 2.4.9-pa30 from CVS and booted it up, and it found the Bluefish
card and the four SCSI drives. Neat! Thanks!

Unfortunately I stuffed up something else, and it couldn't load the
RAM disk, so I haven't been able to actually install it yet. But
it looks promising.


regards,
Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>