From fnaumann@mail.cs.uni-magdeburg.de Wed Jun 30 19:16:55 2004 Message-ID: <021a01c45ec4$7e6e8630$0a01a8c0@tonic> From: "Brian J. Roland" To: "MiNT" References: Subject: Re: [MiNT] Misc. CT2b Problems Date: Wed, 30 Jun 2004 12:05:40 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) at fishpool.fi Delivered-To: mint@fishpool.com Delivered-To: mint@lists.fishpool.fi X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: bjr@localink4.com Precedence: bulk List-help: List-unsubscribe: List-ID: X-List-ID: X-Milter: ClamAV 0.70/0.70kjel X-Milter: milter-regex 1.5jel X-Milter: ClamAV 0.70/0.70kjel > > The machine gets warm..... > > Then that exact same MiNT setup boots and runs fine. > > But then as the machine gets 'warmer', it's anybody's guess what'll happen if a > > reboot is needed. > > > > Strange strange strange that it'll boot on a warm machine but pitch fits and > > lock up when freshly turned on. > > If the problems are dependant on the temperature of your hardware, you > have a hardware problem. Is it possible to switch the CT2 to run the bus > at 16MHz instead of 25? If so, try that. It sounds like you have a bus/timing > problem, I did a lot of tuning and hacking to my own Falcon/Afterburner > a few years ago and experienced a *lot* of strange, subtle problems until > I got everything right. I don't doubt something is wrong hardware wise.... I'm pretty clueless about how to track it down. What I find interesting, and strange, is that MiNT is the environment it chokes in, and primarily at boot-up. MagiC, Geneva, or built in TOS don't appear to suffer....and they do things a heck of alot faster too, in ways that one would think tax the bus even more than MiNT's methods. I.E. ethernet over ROM or SCSI, or moving a pile of files around on disk. Maybe MiNT is relying on some timers that are bad, or have bad connections? If I can get my hands on a spare, I'll seed the thing to CenTek for a good tuneup...I suspect a problem maybe in the Falcon itself rather than the CT2b...I.E. the audio inputs have never worked, and can only get one channel input over the FDI. The error messages I get most are: Bus Error $02 Address Error $03 Line F emulation $?? (forget the number now) Illegal CoProcessor instruction Brian