Firebird PCI Daughterboards

  • Thread starter Thread starter hese
  • Start date Start date
  • Replies Replies 71
  • Views Views 15102
Is it possible to use simultaneously all PCI slots and all Zorro III slots?
 
Is it possible to use simultaneously all PCI slots and all Zorro III slots?
Yes, assuming the zorro cards are half length* and / or do not require use of a rear bracket that a pci card needs.

*Some zorro and pci cards can overlap as long as ic’s don’t clash
 
I've been asked to do a revised version of Firebird daughterboard that fits to the A3000 motherboard housed in a Checkmate 1500 case.
Some info about A3000 motherboard in Checkmate 1500 case here.

I'm gauging how much interest there would be for a Firebird A3000 Checkmate edition daughterboard.

Do you have a Checkmate case with A3000 mounting kit?
Would you be interested in a Firebird Checkmate daughterboard for A3000? Or for AA3000+? Or both?

You could either post your interest here or by private message.
Very interested in a AA3000+ firebird for checkmate case!!
 
Hi and one more question. There have been released Voodoo drivers for the G-Rex board and CybergraphX. Are they in any case usable for the firebird pci daughterboard in a A4000 equipped with Cyberstorm MKI?
 
No, the G-Rex drivers only work with the G-Rex daughterboard. Firebird is based on the Prometheus PCI and for it you need drivers that are written for the Prometheus hardware.
But there are Voodoo drivers also for the Prometheus so you can use Voodoo graphics cards with Firebird.
 
Thank you, it's clear now. Do you prefer the P96 version 2.1b, or the new P96 releases, what is better? There is also a Permedia 2 driver in the new V3.3.3. Permedias are easier to find and cheaper.

AAh, I have seen there is also a Permedia 2 driver in 2.1b.
 
Last edited:
P96 3.0 and newer work ok with Prometheus, but if you wish to use warp3d be aware that for some unknown reason p96 3.x cuts the fullscreen framerate by a third.
 
I would go also for the 2.1b Version, because some older software don't like to work with the new p96. Not difficult to try for both releases.
 
Dumb Q
  1. Is there an FAQ somewhere?
  2. Where do people get the Prometheus and/or Firebird related software (drivers and tools)?
  3. Is the Firebird in an AA3000+ 3.3V PCI compatible?
I have a handful of Radeon 256MB PCI cards that I'd like to see if they are enumerated (prmscan?), as well as an incoming PowerPC card
 
Okay, via successful scouring, i found prmscan, openpci.library, and prometheus.library 4.1 and was able to run prmscan against my two Radeon 9250 256MB boards. However, i'm seeing the boards only scan as 128MB - is this expected? Is the RAM potentially partitioned such that 128MB is accessible over PCI, and the other 128MB is "frame-buffer" video memory?

Both boards come up as:
prmscan 1.7 (05.1.2010) ...
prometheus.library version 4.1
PCI cards listing:
---------------------
Board on bus 0, in slot 2, function 0
Vendor: ($1002) unknown ($1002) <-- THIS IS AMD/ATI
Device: ($5960) unknown ($5960) <-- THIS IS RADEON 9200 PRO / 9250
Revision: 1
Device class 03, subclass 00.
BAR0 address range: 60000000 - 67FFFFFF (128 MB)
BAR1 address range: 7FE01000 - 7FE010FF (256 B)
BAR2 address range: 68000000 - 6800FFFF (64 kB)
128 kB of ROM at 68020000 - 6803FFFF.
Board driver: NONE
 
Okay, via successful scouring, i found prmscan, openpci.library, and prometheus.library 4.1 and was able to run prmscan against my two Radeon 9250 256MB boards. However, i'm seeing the boards only scan as 128MB - is this expected? Is the RAM potentially partitioned such that 128MB is accessible over PCI, and the other 128MB is "frame-buffer" video memory?

Both boards come up as:
prmscan 1.7 (05.1.2010) ...
prometheus.library version 4.1
PCI cards listing:
---------------------
Board on bus 0, in slot 2, function 0
Vendor: ($1002) unknown ($1002) <-- THIS IS AMD/ATI
Device: ($5960) unknown ($5960) <-- THIS IS RADEON 9200 PRO / 9250
Revision: 1
Device class 03, subclass 00.
BAR0 address range: 60000000 - 67FFFFFF (128 MB)
BAR1 address range: 7FE01000 - 7FE010FF (256 B)
BAR2 address range: 68000000 - 6800FFFF (64 kB)
128 kB of ROM at 68020000 - 6803FFFF.
Board driver: NONE
Best source also for such questions might be the EAB and the thread over here
 
Okay, via successful scouring, i found prmscan, openpci.library, and prometheus.library 4.1 and was able to run prmscan against my two Radeon 9250 256MB boards. However, i'm seeing the boards only scan as 128MB - is this expected? Is the RAM potentially partitioned such that 128MB is accessible over PCI, and the other 128MB is "frame-buffer" video memory?

Both boards come up as:
prmscan 1.7 (05.1.2010) ...
prometheus.library version 4.1
PCI cards listing:
---------------------
Board on bus 0, in slot 2, function 0
Vendor: ($1002) unknown ($1002) <-- THIS IS AMD/ATI
Device: ($5960) unknown ($5960) <-- THIS IS RADEON 9200 PRO / 9250
Revision: 1
Device class 03, subclass 00.
BAR0 address range: 60000000 - 67FFFFFF (128 MB)
BAR1 address range: 7FE01000 - 7FE010FF (256 B)
BAR2 address range: 68000000 - 6800FFFF (64 kB)
128 kB of ROM at 68020000 - 6803FFFF.
Board driver: NONE
Where did you scour these from?
 
Hi,
I'm traying to run Killer K1 with Sonnet library. I'm using powerpc.library version 17.14 which supports Prometheus.
After call InitPPC I get message "e300 based PPC cards currently not working correctly!". According to documentation this card should work.
Has anybody run this card in Firebird PCI?
 
Hi,
I'm traying to run Killer K1 with Sonnet library. I'm using powerpc.library version 17.14 which supports Prometheus.
After call InitPPC I get message "e300 based PPC cards currently not working correctly!". According to documentation this card should work.
Has anybody run this card in Firebird PCI?
Have a look at post #43 of this sales thread:


I believe the Firebird has to have the correct components in place.

Also have a look at the Thread on Prometheus Firebird setup I put together. Just in case you are missing something which can be found over in Amiga.org here:

 
Have a look at post #43 of this sales thread:


I believe the Firebird has to have the correct components in place.
I checked and there are this components.
Also have a look at the Thread on Prometheus Firebird setup I put together. Just in case you are missing something which can be found over in Amiga.org here:

I configured it with this manual and other boards works correctly.
 
What about the picture in post #43. Does your board have that same component make up?
Yes, it has. But I see that PPC board works but are some lags for example when loading workbench pattern.
I think it's known problem, I found in documentation:
"WARNING: Timings on the Prometheus seem not so tolerant. K1/M1 cards do not work with the Prometheus and Warp3D (bus errors)"
 
Back
Top Bottom