Overview Features Instructions Performance Forum Downloads Products Reseller Contact

Welcome to the Apollo Forum

This forum is for people interested in the APOLLO CPU.
Please read the forum usage manual.
VISIT APOLLO IRC CHANNEL



All TopicsNewsPerformanceGamesDemosApolloVampireCoffinReleasesLogin
Questions and Answers for Coffin AMIGA OS

68040/68060 CPU Library

Mark Breckell

Posts 2
18 Sep 2019 13:41


Could do with a bit of help just installed Amiga os 3.1.4 installed restarted the computer,now it's saying A68040 or 68060 CPU was found in the system, but a corresponding CPU library is missing.where do i get this from that works with the vampire V500+.
 
Thanks in advance  :)


Gunnar von Boehn
(Apollo Team Member)
Posts 4094
18 Sep 2019 13:50


Those libraries are not needed on VAMPIRE


Sean Sk

Posts 277
18 Sep 2019 13:53


Hi Mark,
 
If you don't want the message to popup, just go to your startup sequence and comment out the line near the start that says "C:CPU CHECKINSTALL"


Mark Breckell

Posts 2
18 Sep 2019 15:55


Hi Sean did what you said working fine now.

Thank you for your help  :)


John Fante

Posts 22
19 Sep 2019 19:39


sean sk wrote:

Hi Mark,
 
  If you don't want the message to popup, just go to your startup sequence and comment out the line near the start that says "C:CPU CHECKINSTALL"

I would not advise disabling CPU CHECKINSTALL.

It can mess up other elements in the system. Cpu caches and fpu are missing etc.

Take the 68040old.library from this archive EXTERNAL LINK and rename it to 68040.library and put in in libs. That will take car of the error.


Ronnie Beck

Posts 87
19 Sep 2019 23:38


John Fante wrote:

  I would not advise disabling CPU CHECKINSTALL.
 
  It can mess up other elements in the system. Cpu caches and fpu are missing etc.
 

 
  According to the documentation "CPU CHECKINSTALL" just "Tests for the presence of a CPU library on affected CPU models."
 
  EXTERNAL LINK 
  This is just a check.  Since the library it checks for isn't necessary, it is an unneeded check.
 
 
 
John Fante wrote:

  Take the 68040old.library from this archive EXTERNAL LINK and rename it to 68040.library and put in in libs. That will take car of the error.
 

 
  Why?  These libraries seem to be for Phase5 accelerators and  BigGun has already said this is unnecessary.  If this is truly necessary, please explain IN DETAIL why it is so.  Otherwise this advice should be ignored.


John Fante

Posts 22
20 Sep 2019 05:42


Ronnie Beck wrote:

John Fante wrote:

    I would not advise disabling CPU CHECKINSTALL.
   
    It can mess up other elements in the system. Cpu caches and fpu are missing etc.
 

 
  According to the documentation "CPU CHECKINSTALL" just "Tests for the presence of a CPU library on affected CPU models."
 
  EXTERNAL LINK   
  This is just a check.  Since the library it checks for isn't necessary, it is an unneeded check.
 
 
 
John Fante wrote:

    Take the 68040old.library from this archive EXTERNAL LINK and rename it to 68040.library and put in in libs. That will take car of the error.
 

 
  Why?  These libraries seem to be for Phase5 accelerators and  BigGun has already said this is unnecessary.  If this is truly necessary, please explain IN DETAIL why it is so.  Otherwise this advice should be ignored.

BigGUn is completely right. In reality the 68040 library are not needed/used with the Vampire.

However, the OS (at least OS3.1.4) checks for them and if you want to get past the error message then the easiest and safest solutions (at least in my - and many others - opinion) is to put an old 68040.library in the libs folder.

The old 68040 library is not from Phase 5. It is the old commodore library supplied with OS3.1. You can also just take it from there if you want.

Compared to removing CPU CHECKINSTALL adding the old library is the lesser of two evils since removing CPU CHECKINSTALL can POTENTIALLY mess up other parts of the OS. Adding the library does not.

But it is a free world (at least in Amigaland) so if you do not have any problems with removing CPU CHECKINSTALL then by all means continue with that. And have a nice day :-)


Marcus Gerards

Posts 57
20 Sep 2019 09:19


You must NOT use any 68040.library with the Vampire. As Gunnar wrote, it is not needed and will cause problems like performance losses.

Remove the CPU-line from startup-sequence and you’ll be fine.

This obstacle will be remedied by OS3.2.


John Fante

Posts 22
20 Sep 2019 09:57


Marcus Gerards wrote:

You must NOT use any 68040.library with the Vampire. As Gunnar wrote, it is not needed and will cause problems like performance losses.
 
  Remove the CPU-line from startup-sequence and you’ll be fine.
 
  This obstacle will be remedied by OS3.2.

Ok. I think a verdict from BigGun is needed here :-)

What is the correct/Best Way to get past the 68040 error in 3.1.4?

Remove CPU CHECKINSTALL or adding the old 68040 library to libs?

Thank you in advance.



Gunnar von Boehn
(Apollo Team Member)
Posts 4094
20 Sep 2019 10:34


John Fante wrote:

What is the correct/Best Way to get past the 68040 error in 3.1.4?

To be honest this is a bug in the 3.1.4 Workbench CPU command.
The OS 3.1.4 guys are aware of this.
AFAIK they have fixed this for the next release.

How about to contact them, and ask them to send you the fix now?




Gunnar von Boehn
(Apollo Team Member)
Posts 4094
20 Sep 2019 11:43


Regarding 68040 and 68060 and 68080.

When the 68040 was designed by Motorola
Motorola decided to include the FPU inside the Chip
but to leave away some rare used FPU instruction which before took many cycles and where basically running a ROM program in 68881 FPU.
Motorolas decision was NOT to put such ROM program in the 68040 but
to have people run a software program.
Those instructions are FSIN, FCOS, FTAN ..

The 68040 Library was developed by MOTOROLA it does provide the Software functions to execute these operations.

With the 68060 such leaving out of instructions got worse.
The 68060 does not support also several Integer Instructions, for example MUL64, and DIV64
The 68060 Library was again developed by Motorola and provides software functions for the missing FPU and missing INTEGER instructions.

Now the 68080 CPU is "complete".
The 68080 does include ROM-code to execute FSIN/FCOS like 68881 FPU did - so it does NOT needs a library.
And the 68080 misses no Integer instructions (not like the incomplete 68060) so again it does not need such library.

This is the simple reason you NOT need any of those libs on Vampire.


John Fante

Posts 22
20 Sep 2019 12:48


Gunnar von Boehn wrote:

John Fante wrote:

  What is the correct/Best Way to get past the 68040 error in 3.1.4?
 

 
  To be honest this is a bug in the 3.1.4 Workbench CPU command.
  The OS 3.1.4 guys are aware of this.
  AFAIK they have fixed this for the next release.
 
  How about to contact them, and ask them to send you the fix now?
 
 

Thank you for the clarification. I will reach out to the OS-developers and see what they say.

And thank you for a great product :-)



Henryk Richter
(Apollo Team Member)
Posts 105
20 Sep 2019 13:08


Given the public statements by the lead (and most vocal) developer,there is no need (and not much point) to contact the OS developers for this matter.

Please be advised that the upcoming Gold2.12 release for the Vampire cards will contain a valid Vampire specific 68040.library. That library will include some fixes and precautions known to potentially affect older Kickstart versions when run on faster CPUs. It avoids some other patches that are not needed on 68080, though.

Also in testing is a 68080/Vampire aware re-implementation of 680x0.library which fixes some issues encountered with the BestWB installations.

Consequences of these two libraries:
- BestWB works without manual post-processing (i.e. no removal of mmu.library and 680x0.library necessary)
- c:cpu checkinstall won't complain anymore on 3.1.4


John Fante

Posts 22
20 Sep 2019 13:38


Henryk Richter wrote:

Given the public statements by the lead (and most vocal) developer,there is no need (and not much point) to contact the OS developers for this matter.
 
  Please be advised that the upcoming Gold2.12 release for the Vampire cards will contain a valid Vampire specific 68040.library. That library will include some fixes and precautions known to potentially affect older Kickstart versions when run on faster CPUs. It avoids some other patches that are not needed on 68080, though.
 
  Also in testing is a 68080/Vampire aware re-implementation of 680x0.library which fixes some issues encountered with the BestWB installations.
 
  Consequences of these two libraries:
  - BestWB works without manual post-processing (i.e. no removal of mmu.library and 680x0.library necessary)
  - c:cpu checkinstall won't complain anymore on 3.1.4

Thank you for the answer. Great news :-)

As far as I can see the new library is not implemented in the RC2 of the 2.12 core. At least I get the same missing library error with RC2 as I got with 2.11 if I remove the 68040.library and have CPU CHECKINSTALL in the startup sequence.

I have just made a forum post about the issue on the OS3 development forum on Amiga.org to determin what the best fix is until we get the new core. Lets see what that brings.


John Fante

Posts 22
21 Sep 2019 14:38


@ALL

I stand corrected. :-)

Commenting out CPU CHECKINSTALL is the best way to go.

I posted the issue/discussion on Amiga.org (https://forum.amiga.org/index.php?topic=74304.0) and Thomas Richter (OS3.1.4 developer) answered this:

"The answer is quite simple: 3.1.4 was never considered to support anything beyond what 3.1 supported. So there is no fault in here. "CPU Checkinstall" is by default in the startup-sequence since I've seen plenty people that came here or to other fora that observed "slow execution" and "sporadic software alerts" due to forgetting to install the support libraries. It really does not do anything else."

Since it only checks if the librarys are there and nothing else and as BigGun have posted Vampire does not need any librarys I think we can conclude that commenting out CPU CHECKINSTALL is the best way to go on a 3.1.4 Vampire install.

At least that is the way I will go from here :-)




Vojin Vidanovic

Posts 1334
21 Sep 2019 14:44


Next GOLD2 core will solve the issue by integrating lib in Vamp. Other then dumb OS 3.1.4 check, its really not benefitial nor needed to 080.

posts 16