From: s.telford@ed.ac.uk (Scott Telford) Subject: Re: 387 recognition -- bad coupling ? Date: 8 Jun 1993 12:29:21 GMT
In article <model2.739531712@tardis-b4>, model2@stud.ee.ethz.ch
(course) writes:
> At boot-up a message complains about a IRQ13-error, and the log
> file says there were a bad 386/387-coupling.
> But: The coprozessor obviously works, xlander is 20x as fast as
> without coprozessor.
> (N.B. The coprozessor is correctly installed, the AMI-BIOS reports
> it correctly and it passes the IIT installation software
> check (under MS-DOS).)
This is nothing to worry about: the "bad coupling" error can be
ignored (if youe FPU is OK it is overwritten on the screen, but shows
up in the log) and the other message is just telling you it's found
the FPU.
(This is at least the third posting about this I've seen. Shouldn't
somebody change the kernel to generate less confusing messages?)
-- Scott Telford, Edinburgh Parallel Computing Centre, <s.telford@ed.ac.uk> University of Edinburgh, Mayfield Rd, Edinburgh, EH9 3JZ, UK. (+44 31 650 5978) ======= Rollin' over like a big, big cloud, Walkin' out in the Big Sky! =======