VOGONS


First post, by Rav

User metadata
Rank Newbie
Rank
Newbie

Hi there!

I would like to max out the memory on my cyrix 5x86 system to put a big disk cache (like installing 72MB and setting the XHDD so I have only 32MB usable)
But the L2 is set to WB and anything over 32MB is not cached.

I did read somewhere here that setting the jumper to the same setting as a DX4 should do the trick.
So I did, but it's still WB.

According to these jumper configuration : https://stason.org/TULARC/pc/motherboards/A/A … 6-G-A1GX-2.html, the DX4 have the same jumper setting than the normal 486.
So what give? Why WB is still enabled.

Can it be set to WT after boot using register hacks?

If none is possible, is it possible to set XHDD to use anything after the first 32MB?

Last edited by Rav on 2023-09-18, 22:35. Edited 1 time in total.

Reply 1 of 6, by jakethompson1

User metadata
Rank Oldbie
Rank
Oldbie

I think you are mixing up write-back internal cache (L1) and write-back external cache (L2)
The internal cache can cache the whole 4GB range.
It is the external cache that is set up such that 32MB can be cached by a 256KB cache and 7-bit tag. Write-back versus write-through cache is controlled by a chipset register and therefore by a (possibly hidden or missing) BIOS setting.

Reply 2 of 6, by Rav

User metadata
Rank Newbie
Rank
Newbie

Okay, that make sense, so the CPU WB support is not related to the L2.

CTCM still say that the L1 is Write-back too with the 486/486DX4 settings.
But for some unknown reason, now it does not crash anymore when I set the L2 to 0WS/0WS instead of 1WS/0WS. Ali1429G magic 😁

Reply 3 of 6, by tauro

User metadata
Rank Member
Rank
Member
Rav wrote on 2023-09-18, 22:44:

Okay, that make sense, so the CPU WB support is not related to the L2.

CTCM still say that the L1 is Write-back too with the 486/486DX4 settings.
But for some unknown reason, now it does not crash anymore when I set the L2 to 0WS/0WS instead of 1WS/0WS. Ali1429G magic 😁

On a 486:
The CPU has cache memory called L1 (level 1). It can be 8KB or 16KB depending on your CPU. Earlier ones have 8KB, later ones 16KB.
The motherboard may or may not have cache memory, called L2.

According to the link you posted, your motherboard does not have L2 cache. So you don't have to worry about that.

A board with L2 cache usually looks like this:

m912.cache.jpg
Filename
m912.cache.jpg
File size
1009.26 KiB
Views
96 views
File license
CC-BY-4.0

Those are DIP-28 SRAM modules.

According to the size of your L2 cache you can cache your motherboard's RAM. That means it would work a little bit faster.

And you don't really have to worry about L2 cache for a 486. Upgrading the CPU is far more important if you want a faster 486, the BUS speed and waitstates are also very important.

Disk drive caching is a different subject.

Reply 4 of 6, by Rav

User metadata
Rank Newbie
Rank
Newbie
tauro wrote on 2023-09-18, 23:22:

On a 486:
The CPU has cache memory called L1 (level 1). It can be 8KB or 16KB depending on your CPU. Earlier ones have 8KB, later ones 16KB.
The motherboard may or may not have cache memory, called L2.

Cyrix 5x86 have 16K.

tauro wrote on 2023-09-18, 23:22:

According to the link you posted, your motherboard does not have L2 cache. So you don't have to worry about that.

Sorry for that, there is more than one model of A1GX-2, see : https://theretroweb.com/motherboards/s/acer-a1gx-2-w-cache
For the rest of the jumpers, it's the same

I have 256K

tauro wrote on 2023-09-18, 23:22:

And you don't really have to worry about L2 cache for a 486. Upgrading the CPU is far more important if you want a faster 486, the BUS speed and waitstates are also very important.

All benchs went off the chart since I have upgraded the ram and set the L2 to 0WS/0WS. Ram upgrade alone change nothing in the benchs except for 7-zip (7za b)
For now, only 48MB of ram (16MB not cached), instead of 32MB (fully cached)

As for the CPU, it's a Cyrix 5x86 @ 120Mhz, with the experimental stuff on (the safe one, no BTB).
The not the fastest 486 but it's not far.

tauro wrote on 2023-09-18, 23:22:

Disk drive caching is a different subject.

Indeed, the backup idea (if even possible) was to use the extra ram for disk caching if possible, Keep the cached RAM for the programs and the uncached RAM (anything over 32M) for the disk cache (Still faster than CF in PIO3...)

My actual limit, is the motherboard... You know, very limited ACER BIOS.
And onboard cirrus logic video card, It's "VLB" but well, it bench between ISA and VLB, it's really under-performing, and there is no actual VLB slot.

Would also be cool to know why the PC crash with the L2 to 0ws/0ws instead of 1ws/0ws if I run the jumper configuration in Cyrix 5x86 config, but it work just fine with a nice performance uplift if a set the board jumper to "Intel 486"

Last edited by Rav on 2023-09-19, 00:40. Edited 1 time in total.

Reply 5 of 6, by tauro

User metadata
Rank Member
Rank
Member
Rav wrote on 2023-09-18, 23:52:

The not the fastest 486 but it's not far.

That's one of the fastest Socket 3 CPU (only the 133MHz version is faster), but it's not exactly a 486, it's closer to a Pentium 😉

The fastest proper 486 is the AMD Am5x86, and it can run at 160MHz easily, some at 180MHz and far fewer at 200MHz... Personally I could get a few that work OK at 180MHz 4v (60x3). There's no point really in running a 486 so fast but... it's fun.

Rav wrote on 2023-09-18, 23:52:

Indeed, the backup idea (if even possible) was to use the extra ram for disk caching if possible, Keep the cached RAM for the programs and the uncached RAM (anything over 32M) for the disk cache (Still faster than CF in PIO3...)

I don't know how you could pull that off but maybe you could. I think DOS uses RAM incrementally, but Windows instead uses it the other way, so it always uses the uncached part.

Rav wrote on 2023-09-18, 23:52:

My actual limit, is the motherboard... You know, very limited ACER BIOS.
And onboard cirrus logic video card, It's "VLB" but well, it bench between ISA and VLB, it's really under-performing, and there is no actual VLB slot.

Cirrus cards are quite good. You could also find a VLB riser and use other cards too.

Rav wrote on 2023-09-18, 23:52:

Would also be cool to know why the PC crash with the L2 to 0ws/0ws instead of 1ws/0ws if I run the jumper configuration in Cyrix 5x86 config, but it work just fine with a nice performance uplift if a set the board jumper to "Intel 486"

Maybe it's because the cache chips can't take it. Maybe when you set the jumpers to use an intel 486 you are setting the L1 to WB mode, or you are changing the BUS speed.
To make sure if your L2 is running in WB or WT, run CTCM and see what it reports.

Reply 6 of 6, by Rav

User metadata
Rank Newbie
Rank
Newbie
tauro wrote on 2023-09-19, 00:19:

I don't know how you could pull that off but maybe you could. I think DOS uses RAM incrementally, but Windows instead uses it the other way, so it always uses the uncached part.

Real mode seam to do that, I'm not sure about protected mode. (Try running cachechk in protected mode and see)

tauro wrote on 2023-09-19, 00:19:

Cirrus cards are quite good. You could also find a VLB riser and use other cards too.

Not possible unfortunately (not with that board, there is no extra VLB part on the riser slot

tauro wrote on 2023-09-19, 00:19:

Maybe it's because the cache chips can't take it. Maybe when you set the jumpers to use an intel 486 you are setting the L1 to WB mode, or you are changing the BUS speed.
To make sure if your L2 is running in WB or WT, run CTCM and see what it reports.

* I did not change the L2 since all the test
* CTCM say both L1 and L2 are WB
* I did not touch the bus speed (it's a different jumper that allow to select 25/33/40 and unofficially, 50)
I also did not touch the CPU voltage, with is 3.45V

Also, I did notice that the system "POST" a lot faster (spend a lot less time between memory count and actually start to boot from the hdd). That since I put the jumper in "486" configuration.

You can see that the board have very different jumpers weirdness specifically for the CX586
If you look at JP17 and JP26 (They are jumper array). For all the cpu **except** the cx586, there all on the same like all on 1-2 or all on 2-3. While in CX586 mode it's kinda random. Maybe Acer messed up?