Awesome! Now if we can just find some cheap PRPMC2800s, since we have the manuals for Marvel Discovery I & II now.

Would like to get some help in getting an M1 going in an a4000.

Computer: A4000
Ram: 2mb chip, no mb ram, bfg9060 50 mhz
Mediator 4000 di 3v mk iv
Workbench: 3.2.2.1
Videocard: voodoo 3
Picasso: latest version
Latest drivers from elbox installed.

I followed the first time install manual and get stuck after install sonnet.
So videocard works. Pciinfo sees a second card. The lights on the card also blink.
It then says warm reboot and type some stuff and then initppc.
After initppc it just hangs..
Adding Run >NIL: <NIL: C:InitPPC to startup sequence will result in the message above a window: powerpc exception.

So bit stuck in what now to do…
Probably did something wrong or so..

Here's where I suggest trying different slots. Usually I will put the Voodoo in slot 2, closer to the Mediator bridge and put the PPC card above it in slot 3.
Install the KillerNIC in the top slot for termination or if you have a network card put that in the last or top slot, whether that's a 10MB or 100MB NIC or a Sound card.

Thanks for the tips. Indeed does something different however does not work yet.
So my first post was with the voodoo in 4 (top) and m1 in 2.
When I put voodoo in 2 and m1 in 3 the system crashes/freezes after initppc.
Putting voodoo in 2 and m1 in 4 will result in PowerPC cpu not responding.
Sorry have no other pci cards.
Pictures of the crash and error message.

Do you have DMA memory enabled? I read that the PPC core may need some DMA memory to start up(?). Actual PPC folks, please correct me if I'm wrong.

Yes indeed,
ENVARC:mediator/VoodooMem=13
But I believe Hedeon has a specific error message for that condition.
"Unable to allocate DMA buffers" or something to that effect.

Do you have the swap config jumper off on the Mediator?
I don't know if the bfg9060 sets up memory any differently that you would need to use that, it should be off.

*EDIT*
The other thing to try when you have the Voodoo in slot 2 and the M1 in slot 4 (or 3 test that too), and you get the PowerPC cpu not responding message, start the system, don't initialize the PPC in startup-sequence. Let the system boot and sit on the workbench or run 68k programs for 10 minutes and then try to initialize the PPC.
The preferred method for initialization for me is to put ppc.library and powerpc.library in for example, libs/powarr/ directory and as part of my IconX it goes:
The benefit of this is that if there's some library or datatype that has powerpc.library code in say startup sequence or something in your WBStartup directory, it will try to launch the library that way, which... works but is slightly flaky.

Last time I was talking about this:
https://eab.abime.net/showthread.php?p=1604699

Are you using mmu libs and if so, what is the configuration?

All jumpers are set on the Mediator board.
MMU-libs are installed via the WB 3.2 installer. (As 68060.library is needed)
MMU-configuration file in Prefs in ENV-Archive has been renamed for tests above.

That doesn't answer the question. What is the mmu configuration? Without a configuration file it still sets up the mmu. Can you put the output of MuScan here?

Ok hereby. I’m not very knowledgeable on this stuff. But you probably already thought stupid newby.

Swap config jumper to open has no effect.

System freezes and resets when trying the initialisation via a file in wb with ppc libs installed somewhere else.
Also tried various combinations with also ppc in 3 and a random Soundcard in 4.
Including waiting for a longer time. Most occurring error is: PowerPC is not responding.
Voodoo fixed in 2.

Or maybe the card is not OK. As pciinfo does not give vendorname and devicename.
Vendorname should be Freescale…. But it says unknown. If I compare it with working YouTube videos.

Muscan output:

Muscan output seems fine. vendorname/devicename depends on whether you have the vendors.txt file in the right location. Seeing that the voodoo is recognized by name I guess FreeScale is missing in that vendors.txt file.

Those screenshots, are those voodoo screens or native screens? In other words, is the voodoo running?

Maybe cleaning of the PCI connector helps.

I noticed over on aworld, a guy is trying to build Gorky 17 for WarpOS.
https://amigaworld.net/modules/newbb...45248&forum=15

Sounds like he's using GCC 2.95.2 and a vintage version of libsdl.a, or is someone providing the old versions we used?

Used the first time install guide based on a clean wb install.
Everything works until the guide says “Initppc”.
So voodoo works great in every slot.

Cleaning. Yes maybe (not very likely) will try it later today. I however cleaned the connector before installing even added a tiny bit deoxit.

Maybe should try a second card also for troubleshooting but this one was the only hit on eBay of all the supported card/names found on the GitHub (just copy pasted the names in EBay). Are there other cards which can be bought for non crazy prices which would fit in an A4000 D? Any tips?

I see that the 400 450 MHz G4 cards on ebay quadrupled in price and that he now has Amiga in the description.... Otherwise I would have said get one of those for $100. Plus a carrier from A1k for another 100.

A G4 card…For 100 I can always try it for troubleshooting.
What is a carrier?

Ok I saw you mean it is now 400 :(

Made an offer on this one:

EMERSON MOTOROLA PRPMC8005E-1259 PRPMC8005E 450 MHZ 7410 Processor PMC MODULE

So now I need a carrier I assume to convert it to PCI…

If you’re using that with a mediator you can buy one of Torsti’s pmc carrier boards on amibay but you’ll have to remove the vrm on the mediator as it will not supply enough power to power the ppc board.

If you don’t want to do that you’ll have to find a more expensive pmc carrier with vrm such as a ramix 239/f.

Send a PM to Torsti @ A1k forum. So hopefully he can help..

I guess Lukzer no longer sells them

Does anyone know how to increase the 450MHz on the PrPMC8005E G4 450MHz modules?