Indivision ECS v4 RTG, WBPattern problem with 32 colors upwards

Caution: Non registered users only see threads and messages in the currently selected language, which is determined by their browser. Please create an account and log in to see all content by default. This is a limitation of the forum software.


Please understand that you need to create an account to be able to post, guest posting was disabled as an anti spam measure.

    Hello

    I have such a small problem that if I use Indi's graphics modes with the number of colors from 32 upwards, then in WBPattern after selecting an image, no matter whether as desktop background or window background, the Indivision crashes. A gray screen appears, the situation is saved only by resetting the Amiga. In 16 colors I can use WBPattern and images as background.

    Once such a message jumped out at me:



    The situation is also similar when trying to run the Indivision settings program. When using Indi graphics modes (even in 16 colors) - clicking on the IndivisionEcs preference program, the Amiga crashes.


    My hardware is an A600 with A630 50MHz turbo card with coprocessor and 128MB Fast, kicstart and Workbench 3.1.


    Regards

    Mariusz

    Yes, I have the latest version of MMULib,


    setpatch 44.18



    I also noticed that when I have P96 running I can't do kickstart swap after through MuMapRom, it pops up the message "not enough available memory".

    If I remove Devs: Monitors/IndiECS then I do kickstart swap without problem...

    Games such as ADoom, DoomAttack, the Shapeshifter program, imp3, Dopus run flawlessly...

    MuMaprom uses chipmem (the author explained that a week ago on a1k.org). For loading Kickstart from a file, you should use the MapROM capabilities of the accelerator (BTW, I haven't heard of a 68030 accel with 128M for A600, so maybe a link to the maker would give me a hint about what's wrong here).


    However, the Indivision ECS V4 P96 driver *should* allocate fastmem for it's local buffer. The only reason I can think of why it's not doing that is that the memory has out-of-the-ordinary flags, which the driver doesn't like, or the MMU doesn't cover for other reasons. Please run "showconfig debug" in a shell and post a picture of the output.


    Jens

    Quote

    BTW, I haven't heard of a 68030 accel with 128M for A600, so maybe a link to the maker would give me a hint about what's wrong here

    Archi-tech A630


    Quote

    Please run "showconfig debug" in a shell and post a picture of the output

    I'll check it out tonight

    Mariusz

    Edited once, last by Jens: Link to commercial page removed - I don't want to deal with the legal implications. ().

    Thanks - the "prefers 8-meg space" looks suspicious, but I'll ahve to talk to a few software people to find out if that might cause an issue.


    Jens

    That is, having too much memory in Amiga is not healthy ;-).

    Anyway, I am waiting for some information.

    If there is a demand for beta testing of Indivision firmware, P96 software or other, go ahead and write to me :-).

    Mariusz

    So far, this seems to be a dead end, as the buffer size will be the same, no matter the colour depth up to 256 colours - it's chunky anyway, so one byte per pixel will be allocated.


    Now that I'm reading your message a bit closer, I have a feeling that the memory itself is not stable. Please try to switch off burst and see if the situation improves: Type in a shell:


    CPU nocache


    and then try again.


    Jens

    Unfortunately, disabling the cache did not help.

    I'll also add the information that after the Amiga hangs up, after a reset, it throws out my scsi.device uploaded with Loadmodule. Also, after a reset Loadmodule once again needs to upload this driver.

    Mariusz

    If it helps...My Indivision V4 also reports the "prefers 8-Meg space" using showconfig debug, but I do not have the problems being described in this thread.

    #dwight01

    Thanks for the information.


    So as I suspect it is the size of the Fast memory, i.e. 128MB that is the problem :-( .

    I, in terms of memory, checked my card carefully - everything is ok.


    I suspect that my problem, must have something to do with memory addressing by the IndiECS monitor or MMULib, something overlapping or something being done there ;-) .

    In MuScan I found such differences, maybe they will help something:

    ---without IndiECS monitor


    --- with the IndiECS monitor (I've highlighted the differences)

    forum.icomp.de/core/index.php?attachment/5181/


    Maybe it would be possible to somehow secure memory access for Indi ECS/MMULib via MuSetCacheMode ???

    Mariusz

    I screwed up something in the previous post, also photo to:

    --- with the IndiECS monitor (I've highlighted the differences)

    I insert again

    We'll need more information. Please install SegTracker, then run MuForce with option "DISPC STACKCHECK STACKLINES=32". If you don't have a serial nullmodem, you should also install Sashimi to be able to see the messages that normally come through the onboard serial.


    This is the only way we can see the actual code that's crashing.


    Jens

    Also, is there any tool for your accelerator that is running in the background? If so, can you disable that?


    Jens

    No, the A630 card does not have any dedicated tools. Everything is done with MMULib (MuFastRom, MuMapRom) or Workbench (disabling cache).


    Hence the surprise that with the IndiECS monitor running, when WB shows that I have a free 2MB Chip, it does not map my kickstart and pops up a message about low available memory.

    Thanks - while this is one more data point, it's not an explanation.


    Please do run SegTracker and MuForce, so we can see where it actually crashes.


    Jens

    I downloaded segtracker from aminet.

    How to use it? What commands to enter?

    Mariusz


    PS

    For now, I've grown an icon for segtracker and can dump information from the SHOW and DUMP commands.

    Muforce doesn't dump anything for me, what commands are needed?