Bug 60390

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT)

Description of problem:
When I try to install RH 7.2 on my running RH 5.2 system I see the installer 
load the ncr53c8xx driver. Switchin with <ctrl><alt><f4> to another console I 
see it enters a loop of time-outs and resetting the SCSi bus. I reported this 
to the support team and after a few e-mail exchanges Franklin Abud suggested to 
post this as a possible bug.
When I went back to the 5.2 installer I get to choose between the ncr53c7xx and 
ncr53c8xx driver. The first works and gets the installation under way, the 
second one doesn't with similar errors in the 4th console.
The RH7.2 installer no longer offers the option of the ncr53c7xx driver. How 
can I perform the installation?
This problem is being discussed in service request 201263 with Franklin Abud 
the responsible tech.
I included the output of dmesg from a succesfull Rh 5.2 boot in that request.
Franklin suggested to download update-disk-20020117. I did, booted with boot: 
update expert noprobe
but was never asked to load that disk by the installer.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.put install floppy in drive
2.reboot computer
3.boot: expert noprobe
4.enter driver disk when asked
5.answer questions about language, keyboard, install media (SCSI cdrom)
	

Actual Results:  Installer tries to load ncr53c8xx with the described results

Expected Results:  I expected that the installer would succesfully load a SCSI 
driver for my ASUS PCI SCSI-200 SCSI controller (as the system already runs 
RedHat Linux and has done so very stable for a couple of years) and would 
perform the installation of RH 7.2

Additional info:

After I chose the SCSI driver I switch with to the 4th console.
The start of the scsi messages goes as follows:
at PCI bus 0, device 12, function 0
<6> ncr53c8xx : 53c810a detected
<6> ncr53c8xx-0 : rev 0x11 on pci bus 0 device 12 function 0 irq 9
<6> ncr53c8xx-0 : ID 7, Fast-10, Parity Checking
<6> scsi0 : ncr53c8xx-3.4.3b-20010512
<4> Vendor SEAGATE Model ST34520 REV 1498
<4> Type : Direct Access		     ANSI SCSI revision 02
<6> ncr53c8xx-0-<1,0> : phase change 6-2 1@05d34dc resid=1
<6> ncr53c8xx-0-<1,0> : phase change 2-3 6@05cd3488 resid=5
<6> ncr53c8xx-0 : SCSI parity error detected SCR1=1 DBC=b0000000 STAT1=b
That's all I could catch off the screen and write down...
After this the process goes into a loop of time-outs, parity errors and 
resetting the SCSI bus.