Sonnet 7200 PCI programming

[drluking]

Originally Posted by grelbfarlk

I built up a new OS install based on ClassicWB and it was flaky with the K1 in slot 4, again it would run Amigenerator or Gears for over an hour, but GLQuake would crash after 5-15 minutes. I moved the K1 to slot 2 and it's been running GLQuake for the last 7569 seconds or 126 minutes. *EDIT *UPDATE* Now running for 10934 seconds or just over three hours.
Same as before:

Slot 5) 100MB NIC
Slot 4) Empty
Slot 3) Voodoo 3-2000
Slot 2) KillerNIC K1
Slot 1) Empty

tested again with order PCI same as your, so:

Slot 5) 100MB NIC RTL
Slot 4) Empty
Slot 3) Voodoo3
Slot 2) KillerNIC K1
Slot 1) Empty

OK demo "by night" encore
then
OK demo "sulaco" encore
then
FREEZE demo "by night" encore
reboot
three races OK with WipeOut 2097 all fine, then at fourth race CRASH and reboot
then "Voxelspace G" demo OK for minutes and then CRASH reboot
then "Quake GL 7.3" demo OK for minutes and then CRASH reboot
then demo "by night" encore OK for minutes and then CRASH reboot
then again "by night" encore OK
then demo "sulaco" encore OK for minutes and then FREEZE
then "Quake WOS" OK for half hour and then CRASH reboot

An so ???

[trixster]

I think you have a hardware incompatibility between your mediator and your K1, which will not be fixed by software. Maybe tolerances are lower somewhere for K1 than the other ppc cards that have been tested, maybe something else. Sorry I can’t be more helpful.

[drluking]

but I have here K1 and M1, two cards ... same as problems ... and tried three different A4000 mainboard (full recapped), and two different Mediators !

[grelbfarlk]

Testing with your build again without moving hardware around, I added four files all of which are probably not needed: mmu.library, 68060.library, Picasso96Settings, and mmu-configuration. These versions of mmu.library and 68060.library are old, from 2016, but are what I am using elsewhere.
GLQuake runs for an hour but it froze when flipping back to workbench to check exact length of time. Workbench is running at same resolution, this bug was repeatable.
Also changed PVS settings to what I posted a couple pages back.
Noticed window close button and send to back buttons were colored green.
Changed Workbench resolution to 1280x720 and launched GLQuake 6.1 again and it's been running about another hour, can flip back to workbench, no issue.

[drluking]

Originally Posted by grelbfarlk

Testing with your build again without moving hardware around, I added four files all of which are probably not needed: mmu.library, 68060.library, Picasso96Settings, and mmu-configuration. These versions of mmu.library and 68060.library are old, from 2016, but are what I am using elsewhere.

I doubt it may be a problem with the MMULib version, but let's try this too; tell me what exact version of MMULib are you using, so I try it

GLQuake runs for an hour but it froze when flipping back to workbench to check exact length of time. Workbench is running at same resolution, this bug was repeatable.
Also changed PVS settings to what I posted a couple pages back.

I had tried your PVS settings, but OK I try again with them

Noticed window close button and send to back buttons were colored green.
Changed Workbench resolution to 1280x720 and launched GLQuake 6.1 again and it's been running about another hour, can flip back to workbench, no issue.

I don't have GLQuake 6.1 , only 6.0 and 7.3 , where can download it ? so that I try this version of Quake

Have you tried this ? http://aminet.net/package/game/demo/WipeOut_2097_Demo
As I have written in last posts, I played correctly three races, and at the fourth ... crash ...

[drluking]

Originally Posted by drluking

I had tried your PVS settings, but OK I try again with them

tried now, and crash again ! ...

send me please the QuakeGL 6.1

I'm using 16mb onboard (4 x 4Mb in maninboard A4000) and 128Mb on WarpEngine 040, Is It needed I remove 16Mb onboard ?

[grelbfarlk]

After running GLQuake for that hour, I played four races in WipeOut, noticed when exiting back to Workbench the window close and move back icons were green again, anyway, then fired up Cowcat's Quake2, that ran a few timedemos before the level loading ran out the memory.
My versions are posted a couple pages back where you ask what file versions of everything were. I have 128MB on Warpengine 060 and 64MB motherboard mod. But I never really run through the Warpengine memory so the motherboard mod is just there for a bigger number at top of Workbench.
Upgraded GLQuake to 7.3, I'll see if that's any different.

GLQuake 7.3 ran for some 30 minutes, tried to flip back to workbench and the mouse cursor hung again. I would guess this is an application bug of some kind. If I hit esc first to see the pointer in the program then it always works. Or if I set workbench to 1280x720.
GLQuake 7.3 seems to be a good bit faster. With 6.1 I was getting about 30 fps, 7.3 gets about 38 fps, a healthy gain. EnStackPatch=1 will get about 40 fps with either version.
*EDIT 16*
Updated to latest MMULib from Aminet. Running GLQuake 7.3 for 38 minutes now without issues. Tired of listening for Q1 demos, quit that and started Q2, running without issue. Q2 ended out of memory after maybe 5-10 minutes. Started Q1 demos again, I guess I wasn't tired of the demo sounds yet. 50 minutes without issue running at near max load.
Tomorrow I'll add the SB128 back in and test again with that.
*EDIT 27*
Finished an hour of running with Q1 timedemos.

[deling]

Originally Posted by grelbfarlk

After running GLQuake for that hour, I played four races in WipeOut, noticed when exiting back to Workbench the window close and move back icons were green again, anyway, then fired up Cowcat's Quake2, that ran a few timedemos before the level loading ran out the memory.
My versions are posted a couple pages back where you ask what file versions of everything were. I have 128MB on Warpengine 060 and 64MB motherboard mod. But I never really run through the Warpengine memory so the motherboard mod is just there for a bigger number at top of Workbench.
Upgraded GLQuake to 7.3, I'll see if that's any different.

GLQuake 7.3 ran for some 30 minutes, tried to flip back to workbench and the mouse cursor hung again. I would guess this is an application bug of some kind. If I hit esc first to see the pointer in the program then it always works. Or if I set workbench to 1280x720.
GLQuake 7.3 seems to be a good bit faster. With 6.1 I was getting about 30 fps, 7.3 gets about 38 fps, a healthy gain. EnStackPatch=1 will get about 40 fps with either version.
*EDIT 16*
Updated to latest MMULib from Aminet. Running GLQuake 7.3 for 38 minutes now without issues. Tired of listening for Q1 demos, quit that and started Q2, running without issue. Q2 ended out of memory after maybe 5-10 minutes. Started Q1 demos again, I guess I wasn't tired of the demo sounds yet. 50 minutes without issue running at near max load.
Tomorrow I'll add the SB128 back in and test again with that.
*EDIT 27*
Finished an hour of running with Q1 timedemos.

Very strange I have few Amiga 4000 and I had similar problem
With stabillity k1 like drunkling maybe You have another Amigas :-)
Word word word , show US photos and movies

[Hedeon]

Green buttons on screen switching is I think caused by going from a BE to an LE screen or vice versa. It is a bug/feature in voodoo.card.

[drluking]

yes, and also for Voodoo3 switching from LE to BE (go in screenmode and do test from LE to BE, then you’ll see green in the window)
It’s not important

An other bug is if you have VoodooMemOS=Yes in that case you’ll have a freeze if you test a video mode in BE if you are in OS with LE (try yourself)

[trixster]

My offer to test your k1/m1 in a mediator system which is known to work stably with 3 different ppc cards and 2 different graphics cards stands.

[drluking]

Originally Posted by trixster

My offer to test your k1/m1 in a mediator system which is known to work stably with 3 different ppc cards and 2 different graphics cards stands.

thanks, but I have 3 A4000, 2 Mediator, 060, 040, cyberstorm ppc, 2 Voodoo3 PCI, 2 ATI 9200 PCI , and Amiga1/Pegasos ... I use amiga from I was child ... never had so many problem with amiga hardware, I want to solve myself, I'm skilled about amiga system

But if you want to help me, I send you my SYS: OS to test

[Hedeon]

Originally Posted by drluking

An other bug is if you have VoodooMemOS=Yes in that case you’ll have a freeze if you test a video mode in BE if you are in OS with LE (try yourself)

That is because of the memory list corruption. The list node of the VoodooMem is actually in voodoo memory and hardware byte-swapping it makes it corrupt. This is pci.library issue.

[Hedeon]

So what happened with installing COP? It has a good manual IMO.

[k0x]

Originally Posted by drluking

thanks, but I have 3 A4000, 2 Mediator, 060, 040, cyberstorm ppc, 2 Voodoo3 PCI, 2 ATI 9200 PCI , and Amiga1/Pegasos ... I use amiga from I was child ... never had so many problem with amiga hardware, I want to solve myself, I'm skilled about amiga system

But if you want to help me, I send you my SYS: OS to test

OK, send me your SYS and scenarios you want to test

[drluking]

Originally Posted by Hedeon

That is because of the memory list corruption. The list node of the VoodooMem is actually in voodoo memory and hardware byte-swapping it makes it corrupt. This is pci.library issue.

ok, thanks for the explanation

[drluking]

Originally Posted by Hedeon

So what happened with installing COP? It has a good manual IMO.

not yet, I was hoping that you could identify the problem, but if you fail we will see that you do too

[drluking]

Originally Posted by k0x

OK, send me your SYS and scenarios you want to test

sure, I send you now it (done, you have it)
thanks

[trixster]

Originally Posted by drluking

not yet, I wa s hoping that you could identify the problem, but if you fail we will see that you do too

But k1 works for him! And other people! You are the one who has the problems, so surely you must test with stuff like COPs to prove the problem why must he search for the problems you are experiencing?

[Hedeon]

COP is a debugger. I cannot guess what is happening on your system. It will help.