Re: Fw: 3.0.17 woody install boot disks won't net install?

["Donald R. Spoon" <dspoon@satx.rr.com>]

Paul Slootman wrote:
> On Tue 09 Apr 2002, Paul Slootman wrote:
>
> > > There are some earlier messages during the controller init about "CACHE 
> > > TEST FAILED: DMA error (dstat=0xa0). <3>  CACHE Incorrectly Configured." 
> > > followed a couple of line later by "CACHE TEST FAILED: script execution 
> > > failed.  Start 800F9414, pc=800F9414, end 800F9440".  Strange thing is 
> > > that the source code for this particular driver indicates it hasn't been 
> > > changed in several years!  It looks like something might be messed up in 

I am still getting this error (DMA error (dstat=0xa0)... on subsequent 
compiles with the sym53c8xx driver code compiled into the kernel.  Still 
getting a disconnect and subsequent kernel panic.

> OK, I did it :-) (destroying my athlon's uptime while I was at it,
> because I screwed up trying to get the monitor out of the Athlon and
> into my Alpha, pulling out the keyboard because of cable spaghetti, and
> having to reboot it to get my keyboard working again ;-(

Thanks for your sacrifice(s).  I will have to double my reward <g>!


> Anyway, the good news is that I had no problem whatsoever to boot
> 2.4.18.  It recognized my 810 without any problem:
>
> ncr53c8xx: at PCI bus 0, device 9, function 0
> ncr53c8xx: IO region 0x9000[0..127] is in use
>
> I have this in my .config:
>
> CONFIG_SCSI_NCR53C8XX=y
> CONFIG_SCSI_SYM53C8XX=y
> CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=8
> CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32
> CONFIG_SCSI_NCR53C8XX_SYNC=10

Here is the "defaults" I was using:

CONFIG_SCSI_NCR53C8XX=y
CONFIG_SCSI_SYM53C8XX=y
CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=8
CONFIG_SCSI_NCR53C8XX_MAX_TAGS=4
CONFIG_SCSI_NCR53C8XX_SYNC=5

This is one difference.

> Note that I am not booting from that controller, however;
> I have a QLogic ISP1020 with a wide SCSI 9GB IBM on it.
> I use the NCR for cdrom and tape (and sometimes an external disk).
>
> Nothing about cache problems...
> And I have 14MB extra free on my small root filesystem. Probably libs
> and such that had been upgraded x times while still in use and such...
> Sometimes it *is* useful to reboot.

Great!  That tells me there is a good possibility that my problem is 
"operator error" on my end.  Almost a certainty, given my history :)

I am trying to boot off the NCR 53c810a SCSI controller card.  That is 
another difference, but it works fine under the 2.2.20 "generic" kernel 
and the source code seems unchanged between 2.2.20 and 2.4.18... dunno. 
 Something else is going on I suspect.

Could you send me your .config file that worked for you?  Also, which 
version of milo were you using to boot? Which compiler did you use?? 
(2.95.4 or 3.0 or "other")

> I first tried compiling a pre19 patch, but that didn't compile properly.
> I didn't have time to look into it further, so I took vanilla 2.4.18 and
> stripped out a number of things I had selected above the bare
> essentials. Maybe soon I'll try again with a pre patch.

I tried the pre-pach too (2.4.19-pre6) but it bombed out fairly early in 
the compile.  Neither the gcc 2.95.4 nor the 3.0 liked it much.

Thanks again!

Cheers,
-Don Spoon-






--
To UNSUBSCRIBE, email to debian-alpha-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org