Overview Features Instructions Performance Forum Downloads Products OrderV4 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 TopicsNewsPerformanceGamesDemosApolloVampireAROSWorkbenchATARIReleases
Documentation about the Vampire hardware

Need Help to Get Stable Setup (V1200/WB3.1.4)page  1 2 

Andre Geisler

Posts 16
29 Mar 2020 10:01


Hi everybody.

I don't get a stable setup with my A1200, Vampire 1200 and WB 3.1.4.
I tried a lot, different filesystems, different IDE setup, using my existing system, installing from the beginning,
but in the end the system get's unusable after a while.

That's what I have done so far:

IDE setup (internal A1200 IDE):
Controller -> CDRom (Slave) -> CF-Card (Master)

Vampire setup:
1. installed GoldCore 2.12
2. flashed Kickstart 3.1.4

WB setup:
1. Partition drives (see below for more details)
2. Installing WB 3.1.4
3. Installing WB Upgrade 3.1.4.1
4. Installing latest P96 from IComp (using the Cybervision 64/3D driver because UAE driver does not exist anymore)
5. Installing Saga driver 1.71
6. Installing Roadshow (latest) using a the cnet device for PCMCIA Network card
7. Installing AHI 4.18
8. Installing MUI 3.8 and some more tools like IBrowse
9. Start using the system (playing some games like Doom, Quake, Nemac 4, Earth 2140, ...)

Result:
The system is stable for about 2 - 3 hours, then I cannot boot anymore (reset or cold start does not matter).
I am always getting a prompt at startup with something like that:

Software Failure
Assign
Program failed (error #8000000B).
Wait for disk activity to finish)
[Suspend]    [Reboot]

or
Software Failure
HD1
Program failed (error #8000000A).
Wait for disk activity to finish.
[Suspend]    [Reboot]

Instead of Assign sometimes other programs fail at startup (C:Mount, Devs:Monitors/PAL, ...)

It does not matter if I am using it with or without CD-Rom.
I tried different CF-Cards.
I tried different file systems (FFS (International,Directory Cash), SFS2)

The system is absolute stable with an ACA1230/40MHz.

So what I am doing wrong? It's a strange behavior.
 
Which filesystem to you suggest?
What are the right values for mask (0x7ffffffe), MaxTransfer (0x1fe00) and Blocksize (512)?

I really don't have any idea what I can do to get stable system for more then two hours?
The only way currently is to extract my backup system every few hours.

Any ideas?

regards
eliot


Andre Geisler

Posts 16
29 Mar 2020 14:39


I got this error during Payback installation (wanted to start a shell in parallel:

EXTERNAL LINK 
And after reboot:

EXTERNAL LINK 
Only possible fix: reinstall everything (used a backup)

I also tried another PSU, which did change anything.



Andre Geisler

Posts 16
29 Mar 2020 18:29


I just started from the beginning:
 
  0. Created 2 partitions
  EXTERNAL LINK  EXTERNAL LINK  EXTERNAL LINK 
  1. Formatted (FFS, Int Mode, Directory Cache)
  2. Installed AOS 3.1.4, reboot
  3. Installed Update to 3.1.4.1, reboot
  4. Installed P96 (CVision64/3D), deleted it from Monitors,reboot
  5. Installed Saga 1.71, reboot
  6. Start P96 mode, selected display settings to match vampiregfx, reboot
  7. ERROR
  EXTERNAL LINK 
  I really don't know what to do.
  Maybe I am doing something wrong, maybe Vampire does not work with AOS 3.1.4,
  maybe my Vampire is broken, ...
 
 


Peter Heginbotham

Posts 183
29 Mar 2020 21:13


Have you tried to install P96 version 2.0 with uaegfx.card then upgrade

EXTERNAL LINK


Nixus Minimax

Posts 415
30 Mar 2020 13:10


Andre Geisler wrote:

  Result:
  The system is stable for about 2 - 3 hours, then I cannot boot anymore (reset or cold start does not matter).

You are trying many thing at the same time. Granted, I don't see a reason why they shouldn't work. The fact that it works and then breaks down seems to indicate a heat related problem. Something in your setup heats up and starts to behave differently. This could be any component. The 1230 working fine with it is not a sure sign of the Vampire being the root cause. It may well be that only the speed of the Vampire causes the different behaviour to get noticed and then cause a crash. With these old computers the first things to mention are power supply unit, caps on the Amiga PCB, cleanliness of contacts of the expansion port. Of course, there could be something wrong with the Vampire just as well, your specific one or with the v1200s in general. The best way to find out would be to build your system one step after the other. Start off with just a CF connected to IDE. Build a standard 3.1 Workbench and run that, no new kickstart versions, no new P96 versions. Newer isn't always more reliable. If WB3.1/kick3.1 run well, add the next component and test that for extended periods of time. Right now there are too many unknowns in your setup.



Andre Geisler

Posts 16
30 Mar 2020 14:36


Hi,
starting with WB 3.1 is not an option for me.
And I think Vampire was tested with WB 3.1.4, so starting
form there sounds like a good option to me.

Concerning the A1200 hardware: yes the board has new resistors and the PSU is also new (this one https://www.vesalia.de/d_apower[9204].htm).
I tried it with old PSU -> no change.

I also tested it without the cdrom, which also did not make any difference.
I will have a new try with the old P96 release, perhaps this will help.


Gunnar von Boehn
(Apollo Team Member)
Posts 4706
30 Mar 2020 14:45


Nixus advice was very good.
 
Start with something well, known which is known to be "stable" is clever.
 
OS 3.1.4. is brand new, with new bugs.
Same for the newPicasso, some people say there were NEW bugs introduced into it.
 
I think a good idea is to either use a well tested WB setup - like Coffin. Then you know it will work.
You can of course also all install yourself but this is a lot more complicated.


Andre Geisler

Posts 16
30 Mar 2020 16:25


Hi,

boot crash just with plain wb 3.1.4.1:
EXTERNAL LINK 
My last try: use pfs instead of ffs


Gunnar von Boehn
(Apollo Team Member)
Posts 4706
30 Mar 2020 16:41


Andre Geisler wrote:

    boot crash just with plain wb 3.1.4.1:
 

   
Did you try out a working setup like Coffin, to rule out other issues?


Andre Geisler

Posts 16
30 Mar 2020 18:20


Hi no, I did no try Coffin, I rather don't know what this should be?
 
  I just tested it with PFS3aio, sadly, same result.
 
  Flashed the Vampire again (Gold 2.12, Kickstart 3.1.4) -> same error.
 
  Putting in ACA 1230 -> everything is fine.
  AOS 3.1.4 runs great here on several Amigas.
  I bought the Vampire1200 for using it with AOS 3.1.4,
  not any other OS.
 
  Do I need to change anything in the Kickstart module before I falsh it to Vampire?
I will give this a try:
https://wiki.apollo-accelerators.com/doku.php/os:amigaos:v3.1.4


Gunnar von Boehn
(Apollo Team Member)
Posts 4706
30 Mar 2020 19:33


Andre Geisler wrote:

  Putting in ACA 1230 -> everything is fine.
 

 
But unfortunately, this proves absolutely nothing at all.
Maybe you flashed 3.1.4 badly?
Maybe you installed 3.1.4 badly with some incompatible libraries?

 
Andre Geisler wrote:

  Hi no, I did no try Coffin, I rather don't know what this should be?
 

Testing the V1200 with another OS like Coffin would be good option to verify that the V1200 runs well in your A1200.
But you are not willing to do this?
 
 


Manfred Bergmann

Posts 179
30 Mar 2020 20:51


I'm also setting up a fresh AOS 3.1.4 on V1200.
But it's working OK so far.
Have it running for ~4 hours now. It's sitting mostly idle though.

I haven't installed a lot yet, just the OS and a few tools.
Also I have burned the ROMs myself.

Maybe you should also try without maprom of Vampire.

Manfred


Andre Geisler

Posts 16
30 Mar 2020 21:09


>But unfortunately, this proves absolutely nothing at all.

Well that shows that the other hardware is running.

>Maybe you flashed 3.1.4 badly?

Do you mean the Kickstart?
Just calling VampireFlash314 <kickstart image>
Did it several times now.

>Maybe you installed 3.1.4 badly with some incompatible libraries?

I did not install any libraries.
Plain AOS 3.1.4 from Floppy drives.
Afterwards AOS 3.1.4.1 update
Afterwards Picasso 2.0 (as suggested)
Saga 1.7.1
nothing else

Perhaps I should skip the update to 3.1.4.1?
I will have a try.

> testing the V1200 with another OS like Coffin would be good option to verify that > the V1200 runs well in your A1200.

Yes I can do this. But my goal is to use AOS, not Coffin Os.


Andre Geisler

Posts 16
30 Mar 2020 21:13


Manfred Bergmann wrote:

I'm also setting up a fresh AOS 3.1.4 on V1200.
  But it's working OK so far.

Did you try to install the update 3.1.4.1?
Which Picasso do your use?
Did you modify the kick.a1200.46.143 kick rom?



Manfred Bergmann

Posts 179
30 Mar 2020 21:35


Andre Geisler wrote:

Manfred Bergmann wrote:

  I'm also setting up a fresh AOS 3.1.4 on V1200.
  But it's working OK so far.
 

 
  Did you try to install the update 3.1.4.1?
  Which Picasso do your use?
  Did you modify the kick.a1200.46.143 kick rom?
 

No, I didn't install the update yet. Will do shortly. But I doubt that makes a difference (for your case I mean).

I don't use P96 either. Just a stock AGA display.

I've modified the kickstart insofar that I replaced intuition with the v45 version.
But the ROMs. Either they work or not. If they don't work you don't get far.

One question mark for me would be what the Vampire does to the Kickstart and under which conditions modules are changed/replaced.

Manfred


Gunnar von Boehn
(Apollo Team Member)
Posts 4706
31 Mar 2020 08:06


Andre Geisler wrote:

I did not install any libraries.

OS 3.1.4 installs many libraries and some of them you not want on Apollo.

Andre Geisler wrote:

Yes I can do this. But my goal is to use AOS, not Coffin Os.

Coffin is Amiga OS.


Manfred Bergmann

Posts 179
31 Mar 2020 08:43


Gunnar von Boehn wrote:

Andre Geisler wrote:

  I did not install any libraries.
 

  OS 3.1.4 installs many libraries and some of them you not want on Apollo.
 

While Coffin OS is certainly a very convenient alternative to putting the OS together with a lot of effort, I run AOS 3.1.4(.1) as custom composed systems on all my Vampires without any problems. Most of them were originally 3.9 installs with 3.1.4 put on top.

Which libraries are you referring to that one not wants on Apollo?

Manfred


Gunnar von Boehn
(Apollo Team Member)
Posts 4706
31 Mar 2020 08:54


Manfred Bergmann wrote:

While Coffin OS is certainly a very convenient alternative to putting the OS together with a lot of effort, I run AOS 3.1.4(.1) as custom composed systems on all my Vampires without any problems. Most of them were originally 3.9 installs with 3.1.4 put on top.
 
Which libraries are you referring to that one not wants on Apollo?

For example the MMU Lib or 68060 Lib you not want to run on your Apollo 68080 CPU.

Installing a new OS with updates and lots of extra components and drivers on an old A1200 with Powersupply of unknown status - has a number of issues which could cause problems.

Maybe the old PSU?
Maybe the P96 Upgrade not like SAGA driver?
Maybe OS 3.1.4 68060 Library causes problems?

To test this - I would propose a strategy to "exclude" parts.
One sensible approach would be to exclude OS 3.1.4 as Error-source and to run Coffin.
 


Andre Geisler

Posts 16
31 Mar 2020 10:17


Uf,
 
  boot with no startup-sequence, got a crash when calling dir in ram:
  EXTERNAL LINK 
  OS 3.1.4 does not provide any 060er lib or mmu as far as I know?
  The PSU is new, this one:
https://www.vesalia.de/d_apower[9204].htm

  Old p96 already tested, same errors.
 
  Last step for me: try Coffin, ....


Gunnar von Boehn
(Apollo Team Member)
Posts 4706
31 Mar 2020 10:45


Andre,

I would propose you use the normal FPGA Core, with normal Coffin.
To rule out that something during 3.1.4 install went wrong.
Some MMU libs which are not compatible - a lot can be done wrong in detail - hard to diagnose from remote.

Also I would propose to run some Memory test program.
MR2TEST is a very good memory test, please run this.
 
 
  The errors that you have can have many reasons: For example:
  - bad memory chip
  - memory bit flips caused by weak power supply
  - not "green" enough FPGA compile
 
  I would propose the following:
  a) Run memory test
  b) Remove extra "power consumer" like e.g CDROM.
  c) Try another FPGA core

posts 30page  1 2