Sonnet 7200 PCI programming

[grelbfarlk]

Is the LM1084 getting really hot too?

Also what's your OS install situation are you using straight 3.9 or 3.1.4 or a prepackaged build?

[jbenam]

Originally Posted by grelbfarlk

Is the LM1084 getting really hot too?

Also what's your OS install situation are you using straight 3.9 or 3.1.4 or a prepackaged build?

Nope, actually the AIC1084 doesn't get too hot either. Stuff probably melted while I was testing amperes with my Multimeter (it goes easily up to 6A, which should be plenty enough).

3.9 along with BB1, BB2 and BB3+4 plus some bits and bobs like KingCON. It's a pretty vanilla install other than that.

I do know that BB3+4 aren't exactly advised, but I have also tried doing a clean install of 3.9 using WinUAE and all sort of stuff went wrong whenever I switched on real hardware. IIRC the install I have now was done entirely on hardware and it has always been pretty stable.

Should I try with 3.1.4? I am assembling my 040-to-060 and I will probably need to burn a custom kickstart anyway, so I might as well upgrade to 3.1.4... unless it is advised that I stay on 3.9 for the meantime, at least while we are still testing stuff.

[Hedeon]

Made another slight correction to the K1/M1 code in regards to the Mediator and with pcidma memory enabled. Should not affect the ramlib crashing. But can you check if this still works for you, grelbfarlk?

[grelbfarlk]

Originally Posted by jbenam

Nope, actually the AIC1084 doesn't get too hot either. Stuff probably melted while I was testing amperes with my Multimeter (it goes easily up to 6A, which should be plenty enough).

3.9 along with BB1, BB2 and BB3+4 plus some bits and bobs like KingCON. It's a pretty vanilla install other than that.

I do know that BB3+4 aren't exactly advised, but I have also tried doing a clean install of 3.9 using WinUAE and all sort of stuff went wrong whenever I switched on real hardware. IIRC the install I have now was done entirely on hardware and it has always been pretty stable.

Should I try with 3.1.4? I am assembling my 040-to-060 and I will probably need to burn a custom kickstart anyway, so I might as well upgrade to 3.1.4... unless it is advised that I stay on 3.9 for the meantime, at least while we are still testing stuff.

I don't use 3.1.4, but others have successfully.
I use ClassicWB 3.9.


What do the first few lines of your startup-sequence look like, what are your loadmodule/loadresident lines?

[trixster]

3.1.4 tested with both mediator and Prometheus setups, works fine

[grelbfarlk]

Originally Posted by Hedeon

Made another slight correction to the K1/M1 code in regards to the Mediator and with pcidma memory enabled. Should not affect the ramlib crashing. But can you check if this still works for you, grelbfarlk?

Yes, working fine, Warp3d, Voxelspace, Adoom, etc.

I did have a problem with Quake2 with this version, loading the demo the application bombed out out with:
Error: Hunk_alloc failed: Could not allocate 446240 Bytes!
I tried reducing the stack to 4000000 from 5000000 to no effect, maybe just one of the previous applications did not release some memory properly, which might have been GLQuake, Voxelspace or Adoom.
Rebooted and tried launching from a fresh boot and it threw a Sonnet Exception.
Rebooted again and it's running now, so call that an anomaly. Running Quake2, prboom, voxelspace and GLquake fine.
I can see the K1 is not well seated in the slot, so ignore everything after I said it's working fine.

[TheMrKocour]

Hi, its safe to have Sonnet G3 in closed A4k? With some fans?

[amigoun]

Could voodoo banshee be supported beside voodoo 3? Mediator driver supports it and the card produces less heat in comparition to v3, which is what I like about it
Edit: Well, it makes a lot of heat as well, active cooling recommended.

[Hedeon]

Originally Posted by amigoun

Could voodoo banshee be supported beside voodoo 3? Mediator driver supports it and the card produces less heat in comparition to v3, which is what I like about it

Give me a pciinfo and I see what I can do. There are no Warp3D drivers for Banshee, however.

[Timtheloon]

Originally Posted by Hedeon

Give me a pciinfo and I see what I can do. There are no Warp3D drivers for Banshee, however.

Warp 3D works with my banshee on the 68k demos, is it just PPC support?

[grelbfarlk]

Originally Posted by TheMrKocour

Hi, its safe to have Sonnet G3 in closed A4k? With some fans?

Assuming your power supply fan is working properly it should work fine. However I added some speed holes to the Sonnet just in case and hung a case fan from the A4000 crossbar. Others didn't do any of that and it seemed to work. See previous post, which may have been in Trixster's A4000 picture thread.

In the same system without really changing anything, I went to a Rapture to a Ragnarok, with no real difference.

[Hedeon]

Originally Posted by Timtheloon

Warp 3D works with my banshee on the 68k demos, is it just PPC support?

Google didn't know about it.

Could you make a picture of gears running and also which libraries are loaded when you start gears?

[amigoun]

Here the pcinfo details:

Pci Device 2:
VendorID: $121a
VendorName: 3Dfx Interactive, Inc.
DeviceID: $3
DeviceName: Voodoo Banshee
ClassCode: $30000
RevisionID: $3
InterruptPin: 4
SubsystemVendorID: $1102
SubsystemID: $1017
MemSpace0: $60000000 - $61ffffff
MemSpace1: $62000000 - $63ffffff
IOSpace2: $40c06000 - $40c060ff
RomSpace: $64000000 - $6400ffff

[amigoun]

And the other Banshee card I have these sub* IDs:

SubsystemVendorID: $1092
SubsystemID: $4002

[Hedeon]

Originally Posted by amigoun

And the other Banshee card I have these sub* IDs:

SubsystemVendorID: $1092
SubsystemID: $4002

Try this.

[amigoun]

From a superquick test it works fine, thanks!

[Timtheloon]

Good morning All

@Hedeon

Here you go, below is pictures of my Banshee doing the Warp3D demos on my A1200 with the 68k

I’m using the same drivers as I use with my A4000 with the exception of the Warp3D 1200 files, I never checked if they could do Warp3D, I just assumed it did because it uses the same driver but when having a look on google everywhere states it doesn’t work with the Banshee, unless I’ve installed it wrong and managed to fluke it to work more than likely it can’t do more complex

I’ll see if quake works

[Timtheloon]

So when blitzquake 68K loads it states it is using the Voodoo 3 (Avenger) driver and when starting the game screen is messed up

After you said about it not being supported I had a google too, and one of the comments said about Warp3D being designed to work with the Voodoo 3 avenger chip and not the banshee chip, so looks like Warp3D isn’t compatible with the Voodoo Banshee

It’s a shame really looks like it could work with some tweaking by a very clever person

Here are some screenshots, and sorry if I got peoples hopes up.

[jbenam]

@Hedeon @grelbfarlk

I have made a clean install of OS3.9 BB2.

It is LITERALLY the cleanest install you can do - I have installed the bare minimum: Mediator CD + MMUP 2.6 + Picasso96 2.1b + MMUlib. No Warp3D for now.

I have also tested without Picasso96 (since apparently in the readme it says the K1 doesn't need a VGA adapter to initialise) and without MMUlib.

Usual ramlib errors. I have also tried with dtack as written in the Unreliable Mediator wiki - nothing changed.

I have then proceeded to install Picasso96 (which works as expected) and MMUlib - this time without anything except the bare minimum (no MuFastROM, etc.).

It seems though that the clean install gave me the superpower of being able to withstand the ramlib errors without the entire system dying on itself which means I can now safely save logs. I can also run stuff and it kinda works, except if I try to run any PPC exe, in which case I get ramlib errors but the system keeps going.

Issue is that now MuForce doesn't log any hits (??) and the entire system freezes if I also run MuGuardianAngel before MuForce.

Anyway, logs attached for MuScan + Sashimi output.

V›43mi›40mNCEd Version 3.91 © 2000-2001 Amiga Inc.
performed 1990-2001 by Thomas Richter.
New Shell process 3
3.System3.9:> ›71msashimi
›51mSashimi installed ([Ctrl]+C or "Break 3" to remove)
Sashimi removed.
3.System3.9:> ›71mMuTools
›51m3.System3.9:MuTools> ›71mmuscan
›51mMuScan 46.1 (02.07.2016) © THOR

68040 MMU detected.
MMU page size is 0x1000 bytes.

Memory map:
0x00000000 - 0x001FFFFF CacheInhibit Imprecise NonSerial 
0x00200000 - 0x00BBFFFF Blank 
0x00BC0000 - 0x00BFFFFF CacheInhibit I/O space 
0x00C00000 - 0x00D7FFFF Blank 
0x00D80000 - 0x00DFFFFF CacheInhibit I/O space 
0x00E00000 - 0x00EFFFFF Blank 
0x00F00000 - 0x00F7FFFF CacheInhibit 
0x00F80000 - 0x00FFFFFF ROM 
0x01000000 - 0x06FFFFFF Blank 
0x07000000 - 0x07FFFFFF CopyBack 
0x08000000 - 0x3FFFFFFF Blank 
0x40000000 - 0x40FFFFFF CacheInhibit I/O space 
0x41000000 - 0x5FFFFFFF Blank 
0x60000000 - 0x7FFFFFFF CacheInhibit I/O space 
0x80000000 - 0xFFFFFFFF Blank 
3.System3.9:MuTools> ›71msashimi
›51mSashimi installed ([Ctrl]+C or "Break 3" to remove)
Started Library Init routine
Version: $VER: powerpc.library 17.14 beta (23.03.21)

Detected supported Elbox Mediator PCI bridge
Opening of support libraries completed
3DFX card detected, Gfx address at 64000000, config address at 62000000
Size of Gfx card in PCI memory is 03FFFFF0
Calculated from FE000008
Detected Killer M1/K1 PPC PCI card
Setting up 64MB of PPC memory at 68000000
Setting up PPC card config base at 60000000
Setting up VGA PCI window at C4000000 located from 64000000 with size 8
00FE000
Setting up VGA config block for 3DFX Voodoo located at 62000000
Waiting on PPC card to respond
Accessible PPC memory set up with header at 68410000
Inserted PPC memory into Exec memory list
Library base set up at 6BFF6CB0
Copied PPC kernel code into place
Gort 68K interrupt now running at 077A0A04
MasterControl now running at 07826758
Completed adding various patches to Exec library
Zen support interrupt now running at 68410024

[Hedeon]

Not that it really matters, but you are already a few versions behind. But in principle I won't do anything with reports from older versions. That being said, I don't think I can help you any further at this point. Maybe clone your WB and send it to somebody to test.

Did you test from a normal Shell/CON/KingCON instead of ViNCED?