Charles Galpin said ...
>
> I'll do a bit of cut and pasting here from previous emails to get everyone
> up to speed :) Sorry this might get a bit long.
>
> First to answer your questions, Yes the CDROM is on a 50 pin bus, not I have
> not tried to lower it's tranfer rate. I have tried with the drive only (no
> other SCSI devices) by doing an nfs install. no difference.
The two busses are independent of each other, so lowering transfer rates
on the one won't really effect the other.
> I tried attaching an IDE drive so I could get a base install and upgrade it
> to a 2.2 kernel and the latest scsi drivers since I have corresponeded with
> someone who has the 2940U2W working fine, but added this card to an existing
> system running 2.2.6.
>
> Anyway, when I add the drive, enable IDE support in the bios, it does not
> get detected by my MOBO, and then the system won't boot off the scsi drive
> anymore. I tried as master on both primary and secondary channel - no
> difference. I will try again tonight, but removing the adaptec controller,
> and only adding it back when linux is up and running.
The latest aic7xxx driver is 5.1.14/3.2.4. I personally am using
5.1.13/3.2.4 without any problems. I'm using a 2.0.36 kernel.
> I am going to order another drive today and return this one. It cannot hurt
> (except cost me shipping and restocking/handling fees).
>
> I do have another system I could compile a new kernel on, I'ts currently
> running Red Hat 5.2. I don't know if I can get the latest scsi driver
> without going to a newer kernel (currently 2.0.35), and am also scared to
> upgrade the kernel (laptop see). I guess this might be one of the easier
> ways, but don't even know how to make a boot/install floppy with the latest
> kernel.
Well, the old reliable method is:
# make zdisk
This does the logical equivalent of:
# make zImage
# dd bs=8192 if=arch/i386/boot/zImage of=/dev/fd0
> I have tried another cable.
>
> I have isoloated it down to only using the HD on the 68 pin chain, and
> trying an nfs install. I have an active terminator at the end of the chain,
> and the card termination on. There is no change in the behaviour, and again
> all this works under NT.
After re-reading this mail thread, I'd have to say it's not the hardware.
Suggest you upgrade your kernel to 2.0.36 and apply the 5.1.13 aic7xxx patch.
> One thing that might be of relevance is I seem to get different errors
> depending on whether I cold booted or not. I had dropped the tranfer rate
> down to 10mb, and started getting a different error that the timeouts. When
> I raised it back up, I got this same error (not the timeout) , until a cold
> boot which put me back at the timeouts.
>
> And from my original post :
>
> First a summary:
>
> During installation of Redhat 5.2, it hangs on the dialog saying it is
> scanning for SCSI devices. Virtual console 4 shows the adapter has been
> recognized, and the module installed. I get the following error repeatedly:
>
> <4> scsi: aborting command due to timeout: pid0, scsi0, channel0, id0, lun0,
> 0x00 00 00 00 00
>
> Full blown details:
>
> OS: Redhat Linux 5.2
> OS: NT Serve 4.0 - all works fine
> MB/CPU: Epox MVP3G (award bios) / AMD K6 2 450
> Adapter: 2940U2W bios v2.01.0
> Drive: ibm ultrastar 9ES DDRS 39130 (9gb LVD/ultra 2 wide)
> CDROM: toshiba XM6401
> CDRW: yamaha4416S
> SCSI module: 5.1.2/3.2.4 (CD) and 5.1.7/3.2.4 (latest boot floppy)
~~~~~~~~~~~ ~~~~~~~~~~~
Theses are both pretty old versions. I'd really suggest applying the
latest driver (and latest kernel). I'd also suggest selecting the driver
as being built into the kernel (not as a module).
> -----------------------------
> | controller[ID 7] |
> | |
> | ( chain 0 - 68pin) |-- HD [ID 0] -- Active Terminator
> | |
> | ( chain 1 - 50 pin) |
> -----------------------------
> |
> |--- CDRW [ID 3] ---- CDROM [ID 6] (drive terminted w/ jumper)
>
--
Peter A. Castro ([EMAIL PROTECTED]) or ([EMAIL PROTECTED])
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
