home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!sdd.hp.com!cs.utexas.edu!rutgers!cbmvax!daveh
- From: daveh@cbmvax.commodore.com (Dave Haynie)
- Newsgroups: comp.sys.amiga.hardware
- Subject: Re: Hurricane '030 incompatible with 2.1 setpatch?
- Keywords: 2.1 problem
- Message-ID: <37896@cbmvax.commodore.com>
- Date: 15 Dec 92 10:09:43 GMT
- References: <1992Dec9.160352.4621@sparky.imd.sterling.com>
- Reply-To: daveh@cbmvax.commodore.com (Dave Haynie)
- Organization: Commodore, West Chester, PA
- Lines: 21
-
- In article <1992Dec9.160352.4621@sparky.imd.sterling.com> chris@.IMD.Sterling.COM (Chris Olson) writes:
- >Last night I was helping my brother upgrade from 1.3 to 2.1. He 'had' a
- >Hurricane 030 board in the CPU slot of his 2000. Funny thing was, the 2.1
- >was crashing (8000 0004 ???? ????) everytime during the 2.1 boot sequence.
- >I think we isolated it to the SetPatch command. I'm not sure. The thing would
- >boot up using a 1.3 startup disk. It boots fine minus the accelerator.
-
- The problem is the Hurricane accelerator. Unlike most '030 systems, the
- Hurricane doesn't manage caching in hardware. Because of this, it can only
- cache its own memory, and it needs an MMU table to tell it what's cachable.
- When you boot up, the system comes up with I-Cache on only (no problem, the
- missing cache management logic affects only data caching), but as soon as
- SetPatch is run, the data cache is turned on, and the Hurricane dies. You
- need to specify NOCACHE on the SetPatch line in your Startup-Sequence. You may
- be able to enable it later, I think "SetCPU FASTROM CACHE" would do the job.
-
- --
- Dave Haynie / Commodore Technology, High-End Amiga Systems Design (cool stuff)
- "The Crew That Never Rests" {uunet|pyramid|rutgers}!cbmvax!daveh BIX: hazy
- SCIENCE: "I'll believe it when I see it"
- RELIGION: "I'll see it when I believe it"
-