BigRAM2630: Boot hangs after AmigaOS 3.2.1 module update

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.


Also users that are not logged in can not create new threads. This is a, unfortunately needed, counter measure against spam. Please create an account and log in to start new threads.

Don't Panic. Please wash hands.
  • I was wrong, the "bigram" file had no executable flag.

    Anyway, even flashed with the commands you mentioned (bigram addmem maprom) the performance of the A2091 is disastrous 110 Bytes/Sec.

    If I remove the Bigram2630 the read performance returns to 2Mb/Sec.


    I also tried to put the old kickstart 3.1 and the old operating system 3.1. Same thing !


    My configuration is:


    A2630 + BigRam 2630, A2091 scsi controller. Ace2b 2MB Chip Indivision.


    What can I do ?


    kevbrice  Jens

  • That’s a rather different problem than the subject of this thread, no? 🙂 Might be best to start a new one.


    That said, I don’t repro with my A2091, but I’ve got a GuruROM in mine.

  • The GuruROM will use non-DMA transfer, which is a lot faster than using DMA through chipmem - that's what the original 2091 ROM defaults to, if no memory in Z2 area is available.


    The order or options should not play a role at all. Maybe something else changed with the feature changes?

  • Actually, GuruROM v6 will use the following priority for DMA transfer buffers (with CPU copy-up) when one is needed for transferring data to/from targets >16MB Zorro II address spaces:

    - Allocate a 16K buffer in FastRAM pool which has the 24-bit DMA attribute.

    - Allocate a 16K buffer in ChipRAM pool which always has the 24-bit DMA attribute (but subject to Agnus taking bus priority, so slower).

    - PIO - This option will never apply to any A2000-based use case. Mentioned for completeness only.


    This prioritization will get tripped up by the C0.0000 remap tricks (as noted in the thread), as native C0.0000 memory range is normally tagged with the 24-bit DMA attribute. The driver also assumes all target addresses <16MB are natively 24-bit DMA-accessible in an A2000.

    Former GVP Tech Support 1989-93, GuruROM Maker/Supporter (as personal time allows)

  • The last reply was more than 365 days ago, this thread is most likely obsolete. It is recommended to create a new thread instead.