Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: commodorejohn on November 01, 2010, 04:36:04 AM
-
So here's a problem. I have an Amiga 2500 (Kickstart 3.1) with (currently) two boards in it: an A2630 accelerator (http://amiga.resource.cx/exp/a2630) with 2MB of 32-bit RAM onboard, and a GVP Impact HC+8 Series II (http://amiga.resource.cx/exp/impact2000hc8) SCSI controller. Until today, the GVP card had 2MB of RAM installed, and all was well with the world. However, I ordered some more SIMMs, planning to max out my Amiga's fast RAM by bringing the GVP card up to 6MB, and that's where things got a little odd. When I installed the SIMMs and set the jumpers for 6MB, the Amiga powered on, went through its basic POST sequence, and...displayed the Kickstart "insert disk" screen.
I set the jumpers back to 2MB and it worked fine, then I tried the 4MB setting and had no trouble; Workbench displayed a total of about 6MB fast RAM. It's only when I set the jumpers to 6MB that it malfunctions and fails to detect the hard disk. However, when I boot into Workbench from a floppy, it does display a total of 8MB fast RAM. What's going on here? Is there some kind of extra "hidden" memory on one of these boards that's throwing the auto-configure for a loop? Or is there memory that the SCSI controller uses to talk to the hard disk, but can't get to because all the fast RAM space is taken?
-
Not only RAM, but *everything* on the Zorro2 bus needs to fit into the 8 MB address space. I am sure the GVP needs a few byes for SCSI I/O, so if you fill up the entire space with RAM, the SCSI does not fit in.
-
Not only RAM, but *everything* on the Zorro2 bus needs to fit into the 8 MB address space. I am sure the GVP needs a few byes for SCSI I/O, so if you fill up the entire space with RAM, the SCSI does not fit in.
Not entirely true - there are two distinct AutoConfig spaces: $200000-$9FFFFF for large allocations (8 MB total) and $E90000-$EFFFFF (7x 64 KB) for small allocations (i.e. I/O). Any additional board failing to allocate memory space will just stay unconfigured/shut up.
So, in theory this should work. A possible problem might be that the two chunks get linked together and something rises from that. Have you tried adjusting the mask value of your partitions so the buffers don't end up in 32 bit RAM? Another approach may be to limit the GVP to 4 MB and AddMem the last 2 MB manually after booting (depending on the board's hardware this may not work).
-
Hmm, interesting. There doesn't look to be any jumpers for the mask value on the amiga.resource.cx page or the manual therein; is there some other way I'd have to do this? Or with the AddMem route, how do I go about finding out what parameters to use with this card?
-
The mask values need to be changed in HDToolBox. You need to use e.g. ShowConfig to find out which RAM maps where.
If for instance the GVP maps from 0x200000-0x7FFFFF you'd use a mask value of 0x7FFFFC to force the buffers to 16 bit RAM.
If the 2630 maps from 0x200000-0x3FFFFF it's a bit more difficult as the masking scheme isn't really designed for this... 0xDFFFFC could do the trick.
-
Okay, when the GVP card is set for 8MB, ShowConfig shows the A2630 mapped at 0x200000 to 0x3FFFFF and the GVP has two fast RAM slots (0x400000-0x5FFFFF and 0x600000-0x9FFFFF) and one I/O slot (0xE90000-E9FFFF.) However, HDToolbox complains about "driver not installed," yet when I reboot in 2MB mode, it simply doesn't display any drives in the list, despite the hard drive being recognized and bootable. Puzzlement!
-
What rev is your motherboard? The A2630 can be configured for 2 or 4 meg of RAM. So I would check the jumper setting to make sure it's not trying to grab 4 meg of Zorro2 space. Also, the mask value is only used for DMA and the GVP scsi driver should fall back to PIO for non-DMAable memory. But all Zorro2 memory is DMAable so I don't see how this could be the problem in any case.
-
Those two cards never played well together in my experience. I gave up and set the GVP card for 0MB and used a Supra card for RAM, I believe.
-
The A2630 can be configured for 2 or 4 meg of RAM. So I would check the jumper setting to make sure it's not trying to grab 4 meg of Zorro2 space.
I seem to remember having a similar problem many years ago. I would definetly check the jumpers to make sure the two boards are not competing for the same address space. I'd take a look at how the jumpers in my A2000 are configured, but sadly I'm half a world away from my Amiga at the moment. Good luck!
-
Hmm, that's a thought. I'll take a look when I open it up next.
-
Well, I popped the case today for another card, and the 2630 is configured for 2MB, so I'm kind of stumped. Unless the GVP card somehow attempts to grab 8MB of space when it's configured for anything more than 4MB, I have no idea what the deal would be.
-
Not entirely true - there are two distinct AutoConfig spaces: $200000-$9FFFFF for large allocations (8 MB total) and $E90000-$EFFFFF (7x 64 KB) for small allocations (i.e. I/O). Any additional board failing to allocate memory space will just stay unconfigured/shut up.
So, in theory this should work. A possible problem might be that the two chunks get linked together and something rises from that. Have you tried adjusting the mask value of your partitions so the buffers don't end up in 32 bit RAM? Another approach may be to limit the GVP to 4 MB and AddMem the last 2 MB manually after booting (depending on the board's hardware this may not work).
How would one create a ram board that stops the AddMem command from working?
-
I had the same issue. Ended up setting the GVP card for 0MB and just using it as a SCSI adapter and threw an 8MB SupraRAM or Microbotics 8-Up! (I forget which) in.
-
Yeah, I'm figuring that might be easiest. I've got a DKB 2632 now, so it won't matter terribly once I get that working, but once a problem gets on my brain it's difficult to get it to go away :/
-
Okay, coming back to this again, I did some experimenting while I had my 2000 open and found the following. When the jumpers on the GVP card are set for 6MB, it occupies a block from 0x200000-5FFFFF (4MB) and a block from 0x600000-7FFFFF (2MB.) However, when it's set for 4MB, it occupies one block from 0x600000-9FFFFF. The 2630, when the GVP card is set for 0MB or 4MB, occupies a block from 0x200000-3FFFFF.
I'm kind of wondering if the GVP card is having some kind of conflict with the 2630 over that area at 0x200000 that both of them seem to want. (Wish I knew more about how Zorro II memory partitioning worked!) I have a copy of AddMem, but I'm not sure if that would be useful in this situation - is it possible to use it so that I can have the GVP card configured for 4MB and manually add the remaining 2MB into 0x800000-9FFFFF?