Danie in Oregon (dro@teleport.com)
Thu, 17 Jun 1999 11:09:38 -0700
grant@torque.net wrote:
> > I have finally gotten the 2.2.9 source tree up...and compiled...with the
> > ppSCSI-9.90.patch.
>
> Good.
>
> > epst.1: Pseudo-interrupt timeout, bs=0 cb=6 db=1024 bu=1
>
> This is the second report of this problem that I've seen.
>
> Please try editing ppscsi.c as follows. Locate the following section
> in the function ppsc_engine() :
>
> phase = pha->proto->get_bus_status(pha);
> if (pha->abort_flag)
> PPSC_FAIL(DID_ABORT,"Command aborted");
> if (pha->protocol_error)
> PPSC_FAIL(DID_ERROR,"Adapter protocol failure");
>
> if (!(phase & PPSC_REQ)) {
> if (pha->timedout)
> PPSC_FAIL(DID_TIME_OUT,"Pseudo-interrupt timeout");
> ppsc_set_intr(pha,ppsc_engine,ppsc_ready,0);
> return;
> }
>
> if (!(phase & PPSC_BSY))
> PPSC_FAIL(DID_ERROR,"Unexpected bus free");
>
> and replace it with
>
> phase = pha->proto->get_bus_status(pha);
>
> if (pha->abort_flag)
> PPSC_FAIL(DID_ABORT,"Command aborted");
>
> if (pha->protocol_error)
> PPSC_FAIL(DID_ERROR,"Adapter protocol failure");
>
> if (!(phase & PPSC_BSY)) {
> if (pha->last_phase == PPSC_PH_STAT) {
> if (V_DEBUG) printk("%s: No msg phase ?\n", pha->device);
> pha->return_code |= (pha->status_byte & STATUS_MASK);
> ppsc_cleanup(pha);
> return;
> }
> PPSC_FAIL(DID_ERROR,"Unexpected bus free");
> }
>
> if (!(phase & PPSC_REQ)) {
> if (pha->timedout)
> PPSC_FAIL(DID_TIME_OUT,"Pseudo-interrupt timeout");
> ppsc_set_intr(pha,ppsc_engine,ppsc_ready,0);
> return;
> }
>
> It seems that some SCSI-2 disk drives omit the "message phase" in the
> SCSI protocol, and ppscsi is getting confused.
>
> --------------------------------------------------------------------------
> Grant R. Guenther grant@torque.net
> --------------------------------------------------------------------------
===========================================================
That nipped it in the bud....:)......
Works like a charmmmmmmmm.........AND...
I was even abel to mount it as vfat.......even better....
I was beginining to wonder if my problems stemmed from the fact that I was also
compiling
in sg.o and dtc.o for support with my Envisions scanner(UMAX UDS-IS-11
card)...which
is ACTUALLY a DTC-3181 scsi controller(or can be).....from Domex-DTCTECK.
So that's the next project.....tackling UMAX and SANE....sigh.
Thank you SO much for the help......I've really missed having my SYJET...in
linux...
==========================================
As an aside....would someone please take the time to let me know off list what
EXACTLY
is the correct procedure...for compiling on a VIRGIN source tree??..on another
Linux
news group...I have asked and got THREE different answers...as things
stand...evertime
I have been compiling and have been having to COMPLETELY remove the 2.2.9 source
tree
remove the old 2.2.9 modules....then reinstalling the source tree...then
applying the patch.
then complete recompile of kernel and modules...etc...lots of work to use for
debugging...eh.
The first said...
do make mrproper, then make menuconfig, then make dep, then make
bzimage, then make modules
then make modules_install.
The second said
DONT do make mrproper......just make menuconfig, then make dep,
then make CLEAN,
then make bzImage, make modules, make modules_install.
The third said
It doesn't matter if you do a make mrproper or make clean on a
virgin source tree...
He said to make menuconfig, make dep,make bzImage............then he
said to reboot with the NEW
kernel............THEN to make modules then make
modules_install....he also said no need to make clean.
I have three different books...on linux.........
Mark Sobell A Practical Guide to Linux
Mat Welsh and Lar Kaufman Running Linux
and
Mat Welsh linux Installation and Getting Started....
They also were different...
The docs from Redhat 5.2 are different from RH6.0...on the kernel
build...RH6.0...says nothing about
make clean.
Just need to know these things folks...
Daniel in Oregon
-- To unsubscribe, send mail to: linux-parport-request@torque.net --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2.0b3 on Thu 17 Jun 1999 - 14:19:42 EDT