Thanks! I’ll have a play
Basic Guide on Setting up a Prometheus (Firebird) Daughterboard on A3000 and A4000 now here on Amibay
- Thread starter Boing-ball
- Start date
- Replies 110
- Views 9713
No worries.
I’ve just updated the 1st post about Zorro 3 cards not needing the Prometheus drivers.
Last edited:
Mmmm, doesn’t seem to be doing anythingNo worries.
I’ve just updated the 1st post about Zorro 3 cards not needing the Prometheus drivers.
Attachments
Mmmm, doesn’t seem to be doing anything
Okay just noticed something in the picture of the Buddha, Jumper J1 is off? Check the instructions in the manual, but will mean the DOM you have connected won’t work without it.
Online instructions here:
Buddha - IndividualComputers
For the Buddha plus one, here are the online instructions. Pay particular attention to the DOM power jumper:
Last edited:
The DOM is in ide 2 and the jumper is connected. There’s nothing in ide 1Okay just noticed something in the picture of the Buddha, Jumper J1 is off? Check the instructions in the manual, but will mean the DOM you have connected won’t work without it.
Online instructions here:
Buddha - IndividualComputers
wiki.icomp.de
For the Buddha plus one, here are the online instructions. Pay particular attention to the DOM power jumper:
If you are still having issues with the Buddha, maybe worth a try over on the Icomp forums. I only own a couple of the 20th Anniversary editions. The instructions for those clearly state about a couple of jumpers needed to be covering the correct pins for power etc.. to allow the DOM to work correctly. Ten remove said jumpers when attaching CD ROM drives etc so not to burn them out with extra DOM power etc..
I’ve posted a question. I’ll keep you informed
Did anyone had success running A4000D+Firebird+Radeon9200+RTL8139?
I was able to make Radeon work correctly but when I try to init RTL8139 network card with RoadShow TCP/IP stack and one of latest openpci.library, I get instant freeze.
On openpci.library 9.2 system freezes when I try to start RTL8139 driver.
On openpci.library 17.2 it states that card_init: No enough space to allocate 44Kbytes of DMA memory (despite of a fact that DMAsize=2048k is set in Monitors/radeon toolset).
Is it going to work only with voodoo card as DMA memory?
I was able to make Radeon work correctly but when I try to init RTL8139 network card with RoadShow TCP/IP stack and one of latest openpci.library, I get instant freeze.
On openpci.library 9.2 system freezes when I try to start RTL8139 driver.
On openpci.library 17.2 it states that card_init: No enough space to allocate 44Kbytes of DMA memory (despite of a fact that DMAsize=2048k is set in Monitors/radeon toolset).
Is it going to work only with voodoo card as DMA memory?
Last edited:
Hi,
Just noticed this.
Okay the DMA size. Will update in the 1st thread. You can dependent on RTG card RAM increase this. Try DMAsize=4096k
The other issue maybe down to the Network Card. Have had certain makes of card with the RTL8139 on Mediators that may work then freeze up.
Have you just tried the OpenPCI Ver 2.1 Beta 4 that comes bundled with the RTL network driver?
OpenPCI MultiOS/MultiHardware PCI/AGP Drivers
Hi,
Just noticed this.
Okay the DMA size. Will update in the 1st thread. You can dependent on RTG card RAM increase this. Try DMAsize=4096k
The other issue maybe down to the Network Card. Have had certain makes of card with the RTL8139 on Mediators that may work then freeze up.
Have you just tried the OpenPCI Ver 2.1 Beta 4 that comes bundled with the RTL network driver?
OpenPCI MultiOS/MultiHardware PCI/AGP Drivers
bvernoux.free.fr
Yes, I tried original OpenPCI v2.1 but I will do some more tests on Monday when I get back to my workshop.
I didn't try to increase DMAsize, I only tried to decrease it but I had a feeling that this variable was simply ignored by radeon driver (then I checked the binary file of the driver and there is a DMASIZE string so looks like this should be supported).
I tried two different RTL8139 cards (one RTL8139D and one RTL8139DL if I remember correctly).
I asked on Polish Amiga forum and it seems that the same software and settings work correct with Voodoo cards. So I'm interested to know if there is anyone who uses A4000D+Firebird+Radeon9200+RTL8139 configuration successfully.
sbrentson
Member
I’ve the exact same experience.I’ve posted a question. I’ll keep you informed
I’ve acquired the full set of Firebird projects. Before getting started on the AA3000+ build, i set forth on a quick 3000 DB 1.1 build while I wait for a couple of parts sourced from our friends from south east Asia.
I’ve more than one ReAmiga 3000 and I’ve been able to boot from internal SCSI on both an NTSC and PAL assembly. The Firebird 3000 is recognized as a z3 expansion, but as soon as I attempt to add the Buddha Plus One, no boot at all and no expansion boards show up in early boot menu.
I unfortunately sold my last working original 3000 mb, so I have no way to rule out the ReAmiga as the culprit.
For what it’s worth, the same happens if I try the only other Zorro card I have -zz9000. I can boot from internal SCSI, but no zorro expansions at all, although the native RGB pass through to HDMI still functions.
I’ve still got a Firebird 4000 and the AA3000+ to assemble. I’ll at least have more information if I can get the cards to work with either of those two daughter boards.
Thank you for your reply. We have exactly the same issues. It does see the Buddha in the boot menu but that’s it, no auto boot or any leds light up. 
and rgb2hdmi works fine 
I have no idea what’s the cause
and rgb2hdmi works fine I have no idea what’s the cause
sbrentson
Member
I’ve assembled the Firebird 4000 rev1.1 and I can report at least the z2 Buddha Plus One expansion works with the 4000D. I’m actually still waiting on some PCI toys to arrive next week, so I don’t have any of those slots populated, but I can’t imagine there will be any issues.
I can’t rule out that I’ve botched something on my Firebird 3000 rev1.1 build, but it’s not terribly complicated. I’m inclined to think the 3000 is just quirky.
Imma focus on the aa3000+ build for now, but maybe I’ll circle back on this afterwards…
I can’t rule out that I’ve botched something on my Firebird 3000 rev1.1 build, but it’s not terribly complicated. I’m inclined to think the 3000 is just quirky.
Imma focus on the aa3000+ build for now, but maybe I’ll circle back on this afterwards…
I made a significant disasembly of radeon.card driver (thanks God for IRA disasembler) and it definitely ignores dmasize part with simple branch instruction skipping this part of code. And it looks like it was made by someone for a reason. There is a code for reading dmasize tooltype and converting it to integer value. But i still didnt find the part of code which activates dma memory writes.
sbrentson
Member
So still "troubleshooting" my A3000D Firebird rev 1v1. Or more directly, I was troubleshooting a recently assembled ReAmiga 3000 that has been giving me inconsistent internal SCSI bootup. But just because it was nearby, I decided to pop the Firebird DB in it. And not related to anything, I noticed that the 74646 transceiver U704 was getting out-of-this-world toasty. These tend to run hot, and I typically cram a small Noctua fan in that area to keep them cool. But this one measured 86C before I powered down. I did swap that chip and also confirmed that that particular IC normally hits around 50C with a stock DB (nothing in Zorro slots).
The question is, is this typical with the Firebird rev 1.1, or is this a possible clue for me to sort out why my DB doesn't see the Buddha Plus One I've tried?
The question is, is this typical with the Firebird rev 1.1, or is this a possible clue for me to sort out why my DB doesn't see the Buddha Plus One I've tried?
sbrentson
Member
Different issue. I've finally received a Voodoo3 PCI card to get things started.
Presently I have both the Firebird 3000 and 4000 v 1.1 assembled. Disregarding the issue I've had with the BuddhaPlusOne IDE z2 card on the 3000, I experience the exact same blocking issue with both the 3000 and 4000 DB with either a 3640 (rev?) or TF4060. Trying a variety of permutations of Picasso96, and libraries/drivers that either were provided with the materials from Hess or following a few guides peppered here and EAB or reputable YouTube personalities. The result is always a ramlib exception any time the prometheus.library is accessed - typically when the prometheus monitor device has been set up. On startup, this is when LoadMonDrvs is invoked.
I've only the single Voodoo 3 3000 PCI card. Is this in indication that this card is bad?
Presently I have both the Firebird 3000 and 4000 v 1.1 assembled. Disregarding the issue I've had with the BuddhaPlusOne IDE z2 card on the 3000, I experience the exact same blocking issue with both the 3000 and 4000 DB with either a 3640 (rev?) or TF4060. Trying a variety of permutations of Picasso96, and libraries/drivers that either were provided with the materials from Hess or following a few guides peppered here and EAB or reputable YouTube personalities. The result is always a ramlib exception any time the prometheus.library is accessed - typically when the prometheus monitor device has been set up. On startup, this is when LoadMonDrvs is invoked.
I've only the single Voodoo 3 3000 PCI card. Is this in indication that this card is bad?
sbrentson
Member
And I discovered by problem: I was lazy/careless soldering my SMD 33.33 mhz crystals. Instead of breaking out the hot air station, I just tried tacking these on with my iron. They looked good, but not good enough to get a PCI bus clock. Oops.
m68klinuxenjoyer
New member
Thank you this guide. It helped me a lot setting up a A4000 + mediator + voodoo 3 + sonnet PPC setup I ended up with recently. I never had PCI back in the day so I had no idea what was needed to get it working.
For anyone else that is googling about the rtl8039 driver not being able to allocate 44kbytes of dma memory and trying "DMASize=xxx" and getting frustrated:
For openpci68k + the recent voodoo driver (https://aminet.net/package/driver/video/Voodoo) or maybe any of the gfx drivers by the same guy + p96. In the documentation for openpci68k in the FAQ there is a note about this and it says to add "GRANTDIRECTACCESS=Yes" to tooltypes of the monitor. Adding that will allow it to work (For miamidx at least you can go online once but if you offline and try to online again it doesn't work, but the first time you go online networking is usable). Took me ages to find that note
You don't need the DMASize thing.
For reference the complete setup process for me has been:
- Install Amiga OS 3.1.4 (I wanted 3.1 with the large disk annoyances fixes)
- Install mmulib (https://aminet.net/package/util/libs/MMULib)
- Install openpci68k (https://aminet.net/package/driver/other/openpci68k)
- Buy p96 from icomp, install it
- Install the voodoo driver (https://aminet.net/package/driver/video/Voodoo)
- Make the changes to the generic monitor to make it use the voodoo driver
- Add the GRANTDIRECTACCESS thing
- Install MUI3.9
- Install MiamiDX
- Grab the rtl8039 driver(http://bvernoux.free.fr/DevPCI.php)
- Configure it in line with readme
- Configure the interface in miamidx
For anyone else that is googling about the rtl8039 driver not being able to allocate 44kbytes of dma memory and trying "DMASize=xxx" and getting frustrated:
For openpci68k + the recent voodoo driver (https://aminet.net/package/driver/video/Voodoo) or maybe any of the gfx drivers by the same guy + p96. In the documentation for openpci68k in the FAQ there is a note about this and it says to add "GRANTDIRECTACCESS=Yes" to tooltypes of the monitor. Adding that will allow it to work (For miamidx at least you can go online once but if you offline and try to online again it doesn't work, but the first time you go online networking is usable). Took me ages to find that note
You don't need the DMASize thing.
For reference the complete setup process for me has been:
- Install Amiga OS 3.1.4 (I wanted 3.1 with the large disk annoyances fixes)
- Install mmulib (https://aminet.net/package/util/libs/MMULib)
- Install openpci68k (https://aminet.net/package/driver/other/openpci68k)
- Buy p96 from icomp, install it
- Install the voodoo driver (https://aminet.net/package/driver/video/Voodoo)
- Make the changes to the generic monitor to make it use the voodoo driver
- Add the GRANTDIRECTACCESS thing
- Install MUI3.9
- Install MiamiDX
- Grab the rtl8039 driver(http://bvernoux.free.fr/DevPCI.php)
- Configure it in line with readme
- Configure the interface in miamidx
Updated the guide in regards to issues I have found with OpenPCI version 40.50 from Thors latest release with PowerPC PCI Apocalypse card. Have found that version 2.1 of OpenPCI still is the way forward if using PowerPC PCI Apocalypse card.
Were you able to solve this? I'm getting the same issue, even though I have a Voodoo2 installed and working with Voodoo.card driver