Re: Booting loops (Downloading SCSI SCRIPTS)
Karl Hammar <karl@kalle.csb.ki.se> writes:
> *** linux-scsi:
>
> Regarding master parity error. It seems that the moderboard was erring.
>
> I put the same Tekram DC390U in another machine and there it worked with
> pci parity checking on (see dmesg last in mail).
>
>
> *** debian-boot and Adam Di Carlo:
>
> Don't file a bug against the kernel.
> It fix is almost already there
> I suggest the following patch (and similar for other languages):
>
> $ diff -u f6.txt.~1~ f6.txt
> --- f6.txt.~1~ Thu Nov 23 07:37:20 2000
> +++ f6.txt Thu Nov 23 07:43:29 2000
> @@ -11,7 +11,7 @@
> BusLogic SCSI Hosts 0fbuslogic=0biobase07
> Certain DELL machines 0faic7xxx=no_probe07
> Future Domain TMC-8xx/950 0ftmc8xx=0bmem_base0f,0birq07
> -NCR-810 SCSI controller 0fsym53c8xx=safe:y07
> +NCR-based SCSI controllers 0fsym53c8xx=safe:y07
> Pro Audio Spectrum 0fpas16=0biobase0f,0birq07
> PS/2 ESDI (MCA) 0fed=0bcyl0f,0bhead0f,0bsec07
> Seagate ST-0x 0fst0x=0bmem_base0f,0birq07
Ok, applied.
So we don't need to document "sym53c8xx=mpar:n" ?
> And possible mention in the release-notes that we switched from the
> ncr to the sym-driver which checks for parity errors on the pci bus.
> Which results in driver loops during boot for some bad controller-
> motherboard combinations. Fix as above.
I'll send this to the release notes maintainer for his consideration.
--
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>
Reply to: