Perhaps when my power is restored (March 7th maybe) all of this will be worked out and I can try again. My report May not be needed by then.
|
Quote:
|
Quote:
|
however, fpu implementation in 2.7 core is needed to run Quake and some Demoscene productions that require fpu :) also if this one is not very precise or accurate.
|
Quote:
this all makes sense (no judging here) - so the vampire fpu needs some tweaking. Quote:
just remember the most recent cpu flaws (Meltdown/Spectre) - that should be of more concern. |
ALB42 and Chain-Q did help to track down errors in the fpu:
Code:
flype sagt: |
Quote:
Code:
Henryk Richter - 05 Mar 2018 07:30 |
I am surprised the SPI core doesn't use a clock enable and a fixed rate tick to make it insensitive to clock speed changes.
|
I have no idea :)
#1) I found something useful for V600 V2 owners, those boards need a fix for Gold 2.7 Code:
What capasitors do I need to upgrade? What are their numbers on board? Code:
C3 and C6.. NOTE that it's only needed for the V600 V2. |
Gold 2.7 release for the Vampire accelerators
After updating mine it bricked it with a red screen, but then I use the USB blaster and I got it to boot up! No caps mod needed.
Did they do a up to date registered compile for the 2.7 version? I registered my board last week right before they released the 600 version... |
no update for 2.7 yet. nothing i'm aware of. you have that black/white screen now?
IIRC, the problem with V600 V2 may occure under certain circumstances, disk access or something. screen flicker?! maybe depends on the resolution used. I cannot remember exactly. so you may do some more tests. |
Problem With SFS Partitions With Gold2.7:
Code:
The bug causes Workbench to display a second ghosted icon for the SFS partition http://www.doobreynet.co.uk/files/amiga/SFS_Fix.lha |
OK, so power has returned and there is so much new information out there with so many issues worked around and lot's of people sharing their experience. As promised I published my story of issues in the Apollo forums so rather than repost here, I'll just share the link. I feel lost in a sea of information right now so hopefully I can get the info I need in one place, here:
http://forum.apollo-accelerators.com...php?f=7&t=1872 |
thanks for the link. i'll follow what will be written over there :)
#1) yesterday Gunnar gave a link to a Gold 2.7 "SAFE" x10 core V600, which is worth a look too. #2) above I wrote about a sdnet update. #3) plipbox problem fix for Gold 2.7: Code:
It needs to be placed at ENVARC:SANA2/plipbox.config. Code:
Changelog: |
It may be worth to point out that the project has reached a level of complexity where it is very hard to test and debug everything. The past few days have shown a few bugs that were not found before in a year of development and testing but could be fixed in a relatively short time. This has been very positive for the project.
|
So it would be better to release publicly more often :) pointing out its a beta release.... Testing "in-house" is good but i can imagine, very slow. The users could decide for them self if they want to run the beta release or keep the production one....
|
Quote:
Absolutely agree - It's why I'm trying to provide as much detail as possible. I figure the more data the team can collect, the better... |
Gunnar just anncounces 2.7.1:
Quote:
Quote:
|
Quote:
http://forum.apollo-accelerators.com...2&p=2819#p2819 |
Quote:
#1) as a sidenote: if you get a new version of Apollo/CoffinOS, at least archive the standard folder on your boot partition, such as C: L: S: DEVS: LIBS: ... so you saved the config files, which you may use on the new Coffin version :) |
All times are GMT +2. The time now is 23:20. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.