Basic Guide on Setting up a Prometheus (Firebird) Daughterboard on A3000 and A4000 now here on Amibay

[tramal]

I decided to write this to you because I didn't find any information anywhere that voodoo4 is compatible with Prometheus Firebird. Maybe this information will be useful to someone

 

[Boing-ball]

I decided to write this to you because I didn't find any information anywhere that voodoo4 is compatible with Prometheus Firebird. Maybe this information will be useful to someone

Thanks.

I have now started to make a new build of a Prometheus Firebird setup. I have now installed a Voodoo 4 card with extra power added to the Prometheus. Where I have spotted mistakes or where further clarification is required I have added this to the 1st post.

Remember that this is a ongoing project and drivers etc.. Are always in development and being updated.

 

[oguzog]

Hello everyone,

My friend built Prometheus card

This project

GitHub - shanshe/Prometheus-Resurrector

Contribute to shanshe/Prometheus-Resurrector development by creating an account on GitHub.

github.com

But it is not working.
It is built by instructions given on that github

And tested instructions given here

Basic Guide on Setting up a Prometheus (Firebird) Daughterboard on A3000 and A4000 now here on Amibay

I have copied and pasted the guide here. Please feel free to comment and add anything I have missed or requires amendment. This is something I had to piece together from Information that others have kindly shared: ———- ———— *PLEASE NOTE* The instructions below really are for the PCI side of...

www.amibay.com

We can see prometheus on whichamiga and also voodoo 3 itself but we cannot get graphics from Picasso.
Even tried newest libraries, drivers but same. tried on both 3.2 roms and 3.2 OS and 3.9 roms on 3.9 OS.

Same result

prmscan detects something but Picasso doesn't detect anything.
Tried both voodoo 3 3000 and s3 virge
(both cards tried on a1200 mediator without any poblem)

Also thought maybe something went wrong on build and we built a new one.
Same results.

Maybe system doesn't find RAM for DMA. Added DMASIZE=2048K to the info as seen on screenshots

See screenshots

Any suggestions?

 

[Boing-ball]

Hello everyone,

My friend built Prometheus card

This project

GitHub - shanshe/Prometheus-Resurrector

Contribute to shanshe/Prometheus-Resurrector development by creating an account on GitHub.

github.com

But it is not working.
It is built by instructions given on that github

And tested instructions given here

Basic Guide on Setting up a Prometheus (Firebird) Daughterboard on A3000 and A4000 now here on Amibay

I have copied and pasted the guide here. Please feel free to comment and add anything I have missed or requires amendment. This is something I had to piece together from Information that others have kindly shared: ———- ———— *PLEASE NOTE* The instructions below really are for the PCI side of...

www.amibay.com

We can see prometheus on whichamiga and also voodoo 3 itself but we cannot get graphics from Picasso.
Even tried newest libraries, drivers but same. tried on both 3.2 roms and 3.2 OS and 3.9 roms on 3.9 OS.

Same result

prmscan detects something but Picasso doesn't detect anything.
Tried both voodoo 3 3000 and s3 virge
(both cards tried on a1200 mediator without any poblem)

Also thought maybe something went wrong on build and we built a new one.
Same results.

Maybe system doesn't find RAM for DMA. Added DMASIZE=2048K to the info as seen on screenshots

See screenshots

Any suggestions?

Hi,

- So looking at the screenshots. You have followed the instructions about in Devs:Monitors that the monitor file needs to be “Prometheus”?

- Which version of P96 are you using? Old Aminet version 2 or new Individual Computers version?

-You only have 1 RTG card installed? Something I have found out is that if you have a Zorro RTG and PCI RTG then you get a confliction and the system will not detect either card.

 

[oguzog]

1- yes monitor file is prometheus
2- tried both old and new one
3-never tried 2 RTG same time. One by one.

 

[Boing-ball]

1- yes monitor file is prometheus
2- tried both old and new one
3-never tried 2 RTG same time. One by one.

Okay. I am currently using THors latest openPCI library on my setup:

- *NEW OPENPCI.LIBRARY by THor*: https://eab.abime.net/showthread.php?t=117768 currently at version 12.3

Maybe worth a shot.

 

[oguzog]

No luck same result

 

[Boing-ball]

No luck same result

Silly question perhaps? But you have tried the RTG card installed into different PCI slots?

Another thing to try. Have you downloaded and tried setting up a different monitor file with Thors new Voodoo card driver for openPCI?

Aminet - driver/video/Voodoo.lha

aminet.net

This will only allow for the Voodoo card to work and thus works differently to the Prometheus driver. You will need to use the new Indi P96 software from version 3.3.0 onwards.

 

[oguzog]

It is solved.

The oscillator we have used is old style one. Changed it with SMD type one. Fixed the problem.

 

[Bruce72]

-You only have 1 RTG card installed? Something I have found out is that if you have a Zorro RTG and PCI RTG then you get a confliction and the system will not detect either card.

It maybe a quirk of my own AA3000+ but I've got both a CV64/3d & a Radeon9200 pro running together (Workbench on the CV64, and Doom on the Radeon) with no issues.

 

[Boing-ball]

It maybe a quirk of my own AA3000+ but I've got both a CV64/3d & a Radeon9200 pro running together (Workbench on the CV64, and Doom on the Radeon) with no issues.

Maybe a A3000 version of the card is different? I tried on my A4000 version and it was a no go. Could be the way I have my system setup. Good to know. Thanks.

 

[oguzog]

We abled to geti it worked following HW
voodoo 3
s3 virge
Realtek 8139 ethernet.
usb card with NEC chip
All works but sound...

We've tried both sb128 (CT4750) and Fortmedia fm801

I've put those files to the DEVS/AHI
When we open AHI i dont see any of them

any suggestions?

 

[Boing-ball]

We abled to geti it worked following HW
voodoo 3
s3 virge
Realtek 8139 ethernet.
usb card with NEC chip
All works but sound...

We've tried both sb128 (CT4750) and Fortmedia fm801

I've put those files to the DEVS/AHI
When we open AHI i dont see any of them

any suggestions?

Try AHI version 4.18

Aminet - driver/audio/ahiusr_4.18.lha

aminet.net

Then try Version 6

Aminet - driver/audio/m68k-amigaos-ahiusr.lha

aminet.net

 

[oguzog]

Tried both no chance.

Do you know any compatibility list for sound cards?

Neither sb128 (CT4750) nor Fortmedia fm801 works.

Both were working well with mediator.

See attached photos

 

[Boing-ball]

Tried both no chance.

Do you know any compatibility list for sound cards?

Neither sb128 (CT4750) nor Fortmedia fm801 works.

Both were working well with mediator.

See attached photos

List of OpenPCI sound cards here:

OpenPCI MultiOS/MultiHardware PCI/AGP Drivers

bvernoux.free.fr

 

[Sir_Loin]

Do I need to put any jumpers here to get it to the kickstart screen? I’m just getting RGB output but no kickstart screen is appearing.
It’s a re-Amiga 3000 and all diagrom tests are 100% ok. Thanks!

 

[Boing-ball]

Do I need to put any jumpers here to get it to the kickstart screen? I’m just getting RGB output but no kickstart screen is appearing.
It’s a re-Amiga 3000 and all diagrom tests are 100% ok. Thanks!

Sorry. No idea. The jumpers you are referring to on the picture look to be for Clockport addressing. Which is used to set the Clockport memory address for Clockport add ons such as USB adapters etc..

This looks to be a Revision 1.1? Are you sure you have the right Daughterboard here? The A3000 relies on a Daughterboard present to function, whereas the A4000 doesn't need this requirement.

Have you just tried the Firebird Daughterboard without anything plugged into the PCI and Zorro Slots?

What happens with an Original A3000 Daughterboard?

 

[Sir_Loin]

Sorry. No idea. The jumpers you are referring to on the picture look to be for Clockport addressing. Which is used to set the Clockport memory address for Clockport add ons such as USB adapters etc..

This looks to be a Revision 1.1? Are you sure you have the right Daughterboard here? The A3000 relies on a Daughterboard present to function, whereas the A4000 doesn't need this requirement.

Have you just tried the Firebird Daughterboard without anything plugged into the PCI and Zorro Slots?

What happens with an Original A3000 Daughterboard?

it is a revision 1.1 and it is for the 3000. I have now got the kickstart screen as it should be. But now I’ve posted below my current headache. Thanks!

 

[Sir_Loin]

I’ve built a Re-Amiga 3000 that boots to the kickstart screen as it should. I now need to install Workbench. I have the Prometheus 3000 1.1 and Buddha IDE card. How do I get those configured to install workbench. I know there are libraries to install for the Prometheus, but how do I do that without an OS installed?

There is one bug I’m trying sort in the meantime, the floppy, both internal and external, are recognised with the classic click every couple of seconds but they’re not reading discs.

Any help would be greatly appreciated, thanks!

 

[Boing-ball]

I’ve built a Re-Amiga 3000 that boots to the kickstart screen as it should. I now need to install Workbench. I have the Prometheus 3000 1.1 and Buddha IDE card. How do I get those configured to install workbench. I know there are libraries to install for the Prometheus, but how do I do that without an OS installed?

There is one bug I’m trying sort in the meantime, the floppy, both internal and external, are recognised with the classic click every couple of seconds but they’re not reading discs.

Any help would be greatly appreciated, thanks!

Hi,

The driver element for the Prometheus comes in later. Anything you plug into the Zorro slots is treated normally like the standard Daughterboard. So for the Buddha, just plug that in and off it goes.

The drivers really come into it for the PCI side. So for example you need a dedicated RTG card such as the voodoo so that you can setup DMA for any other PCI card you fit, such as USB, Network. All instructions for this can be followed in my first post.