VOGONS


Am5x86 Write Back mode on Asus VL/I-486SV2GX4

Topic actions

First post, by stinkydiver

User metadata
Rank Newbie
Rank
Newbie

Hello fellow vogons

Has anyone successfully enabled write back L1 cache with an Am5x86 on a Asus VL/I-486SV2GX4 rev 2.0 without running into issues with the floppy drive? I am running the latest beta bios.

As mentioned here on Jan's page http://www.steunebrink.info/amd5x86.htm, I am unable to boot from a DOS startup disk, and when copying files off a floppy I am getting read issues when in WB mode.

I have my jumpers set below:
JP16 1-2, 5-6
JP17 1-2, 5-6
JP18 1-2
JP19 1-2, 3-4, 5-6
JP20 1-2
JP21 3-4
JP22 1-2, 4-5

External Clock is set to 33mhz:
Jp23 2-3
Jp24 2-3
Jp25 2-3

Voltage is 3.45v as set by JP32:
JP32 1-2

Hardware trap is:
Jp5 1-2
Jp6 2-3

I did experiment by setting the hardware trap to JP5 and JP6 both 1-2. The system posted fine but then I got an error when it came to booting off the hard drive.

I also attempted to set a wait state with JP28 and 29, but saw no difference

Setting my cache to WT mode (JP21 2-3) the floppy drive works as normal, but as expected my speedsys score drops from around 50 to 42.

My bios chipset settings were set as follows:

At bus clock: 1/4 CLKIN
Dram speed: faster
dram write ws: 1ws
dram write cas: 2t
dram wrie burst: enabled
slow refresh: disabled
hidden refresh: disabled

L1 cache scheme: auto
L2 cache scheme: auto
cache burst read: 2t
cache write cycle: 2t
video shadow: non cacheable
mem hole at 16mb: disabled
fast reset emulation: enabled
fast reset latency: 2 us
latch local bus: t3
local bus relay: synchronise

Take that there and put it in here

Reply 1 of 21, by Stesch

User metadata
Rank Newbie
Rank
Newbie
stinkydiver wrote on 2025-07-06, 23:32:
Hello fellow vogons […]
Show full quote

Hello fellow vogons

Has anyone successfully enabled write back L1 cache with an Am5x86 on a Asus VL/I-486SV2GX4 rev 2.0 without running into issues with the floppy drive? I am running the latest beta bios.

As mentioned here on Jan's page http://www.steunebrink.info/amd5x86.htm, I am unable to boot from a DOS startup disk, and when copying files off a floppy I am getting read issues when in WB mode.

I have my jumpers set below:
JP16 1-2, 5-6
JP17 1-2, 5-6
JP18 1-2
JP19 1-2, 3-4, 5-6
JP20 1-2
JP21 3-4
JP22 1-2, 4-5

External Clock is set to 33mhz:
Jp23 2-3
Jp24 2-3
Jp25 2-3

Voltage is 3.45v as set by JP32:
JP32 1-2

Hardware trap is:
Jp5 1-2
Jp6 2-3

I did experiment by setting the hardware trap to JP5 and JP6 both 1-2. The system posted fine but then I got an error when it came to booting off the hard drive.

I also attempted to set a wait state with JP28 and 29, but saw no difference

Setting my cache to WT mode (JP21 2-3) the floppy drive works as normal, but as expected my speedsys score drops from around 50 to 42.

My bios chipset settings were set as follows:

At bus clock: 1/4 CLKIN
Dram speed: faster
dram write ws: 1ws
dram write cas: 2t
dram wrie burst: enabled
slow refresh: disabled
hidden refresh: disabled

L1 cache scheme: auto
L2 cache scheme: auto
cache burst read: 2t
cache write cycle: 2t
video shadow: non cacheable
mem hole at 16mb: disabled
fast reset emulation: enabled
fast reset latency: 2 us
latch local bus: t3
local bus relay: synchronise

Hi, I think some of the CPU jumper settings are not correct. Try to jumper JP16 - JP22 like this but with JP20 set to 1-2 like you already did for x4 multiplier.

Screenshot-2025-06-20-143631.png

crayon eater (but only the tasty ones)

Reply 2 of 21, by Stesch

User metadata
Rank Newbie
Rank
Newbie
stinkydiver wrote on 2025-07-06, 23:32:
Hello fellow vogons […]
Show full quote

Hello fellow vogons

Has anyone successfully enabled write back L1 cache with an Am5x86 on a Asus VL/I-486SV2GX4 rev 2.0 without running into issues with the floppy drive? I am running the latest beta bios.

As mentioned here on Jan's page http://www.steunebrink.info/amd5x86.htm, I am unable to boot from a DOS startup disk, and when copying files off a floppy I am getting read issues when in WB mode.

I have my jumpers set below:
JP16 1-2, 5-6
JP17 1-2, 5-6
JP18 1-2
JP19 1-2, 3-4, 5-6
JP20 1-2
JP21 3-4
JP22 1-2, 4-5

External Clock is set to 33mhz:
Jp23 2-3
Jp24 2-3
Jp25 2-3

Voltage is 3.45v as set by JP32:
JP32 1-2

Hardware trap is:
Jp5 1-2
Jp6 2-3

I did experiment by setting the hardware trap to JP5 and JP6 both 1-2. The system posted fine but then I got an error when it came to booting off the hard drive.

I also attempted to set a wait state with JP28 and 29, but saw no difference

Setting my cache to WT mode (JP21 2-3) the floppy drive works as normal, but as expected my speedsys score drops from around 50 to 42.

My bios chipset settings were set as follows:

At bus clock: 1/4 CLKIN
Dram speed: faster
dram write ws: 1ws
dram write cas: 2t
dram wrie burst: enabled
slow refresh: disabled
hidden refresh: disabled

L1 cache scheme: auto
L2 cache scheme: auto
cache burst read: 2t
cache write cycle: 2t
video shadow: non cacheable
mem hole at 16mb: disabled
fast reset emulation: enabled
fast reset latency: 2 us
latch local bus: t3
local bus relay: synchronise

also, does your BIOS offer a manual write back option for L1 cache instead of 'auto'? Mine does, but im not using the beta BIOS but a modified version of it with the L2 cache dirty tag fix. I don't trust the 'auto' option 😀

crayon eater (but only the tasty ones)

Reply 3 of 21, by Jackhead

User metadata
Rank Oldbie
Rank
Oldbie

I run the same setup with L2 fixed bios. I had also problems on some point with the floppy's. solution for me was switching to a vlb controller that offers WB support. Adaptec AHA-2842A works great with WB and FSB OC. Look for the model with the WB Jumper.
For the jumpers on your Asus use this: https://theretroweb.com/motherboard/manual/cp … 56022401852.pdf
It is basically jumped like a dx4100WB.

Dos 6.22: Asus VL/I-486SV2GX4 Rev 2.0 1Mb L2 - A5x86 X5 P75 - 64MB - AHA-2842A VLB - ET4000W32P VLB - CT2230 - GUS ACE - MPU-401AT with YucatanFX
Win98SE: Asus P5K-WS - E8600 @ 4,5GHz - Strange God Voodoo 5 6000 PCI-X - 2GB DDR2 1066 - Audigy 2 ZS

Reply 4 of 21, by mockingbird

User metadata
Rank Oldbie
Rank
Oldbie

I could never get this combination stable and abandoned it years ago.

mslrlv.png
(Decommissioned:)
7ivtic.png

Reply 5 of 21, by stinkydiver

User metadata
Rank Newbie
Rank
Newbie

I may have to admit defeat also!

Setting Jp16 from 5-6 to 4-5 as advised by @Stesch resulted in a Error 40 floppy drive failure at boot.

I have an ADD2 VLB i/O card with a DW729 chip and a Goldstar Prime 2C 9510 chip. No idea if this supports WB or not - unable to find any manual online.

Last edited by stinkydiver on 2025-07-09, 03:58. Edited 1 time in total.

Take that there and put it in here

Reply 6 of 21, by mockingbird

User metadata
Rank Oldbie
Rank
Oldbie
stinkydiver wrote on 2025-07-08, 03:11:

I may have to admit defeat also!

Just to clarify - I was testing with a Cyrix 5x86 -- not sure with an AM5x86.

I got everything working, but it just wasn't stable when using SETMUL to switch multipliers, it would go haywire when switching back and forth. And it would also hang in Doom even on the slowest memory settings in the BIOS.

I gave up and just threw a 486 DX/33 in there... I still have to put it through its paces (Doom is a good way to test), but it's been sitting collecting dust for a few months while I've been involved with other projects.

I have a feeling UMC VLB might be a better platform for higher end 486 systems.

mslrlv.png
(Decommissioned:)
7ivtic.png

Reply 7 of 21, by stinkydiver

User metadata
Rank Newbie
Rank
Newbie

My system seems relatively stable when using either WT or WB mode, aside from booting from disks and at times installing applications from floppy (Windows 3.11 files for example will fail to copy)

Doom and other applications seem to run ok. I have noticed in Windows 3.11 file manager a couple of times a weird glitch where if I delete a file, all the other files in the directory suddenly have the same name. Sometimes if I exit out of Windows 3.11 the dos prompt locks up and I have to hard reset. If I soft reboot the monitor will display things in black and white, and I will have to hard power off and back on again to resolve the problem.

I am considering installing the original DX100 CPU back in. The reason for the upgrade was I was interested in seeing if there was a performance increase in games like X-Wing with the extra boots in clock speed and cache + WB mode.

Take that there and put it in here

Reply 8 of 21, by Stesch

User metadata
Rank Newbie
Rank
Newbie
stinkydiver wrote on 2025-07-08, 04:30:

My system seems relatively stable when using either WT or WB mode, aside from booting from disks and at times installing applications from floppy (Windows 3.11 files for example will fail to copy)

Doom and other applications seem to run ok. I have noticed in Windows 3.11 file manager a couple of times a weird glitch where if I delete a file, all the other files in the directory suddenly have the same name. Sometimes if I exit out of Windows 3.11 the dos prompt locks up and I have to hard reset. If I soft reboot the monitor will display things in black and white, and I will have to hard power off and back on again to resolve the problem.

I am considering installing the original DX100 CPU back in. The reason for the upgrade was I was interested in seeing if there was a performance increase in games like X-Wing with the extra boots in clock speed and cache + WB mode.

I am pretty sure you can get the VLI working correctly with L1 WB cache, I've used a similiar setup but switched to an IBM 5x86c later. CPU Jumper settings shouldn't be too different tho, I will try the AMD X5 when I'm back from work and report back 😀

crayon eater (but only the tasty ones)

Reply 9 of 21, by Jackhead

User metadata
Rank Oldbie
Rank
Oldbie

Another test you can try, connect only a floppy to your controller, no ide device. Can you boot from floppy ? I tested many VLB Controller with the board. For example from QDI, Promise ... Only the adaptec works fine for me in WB.

Dos 6.22: Asus VL/I-486SV2GX4 Rev 2.0 1Mb L2 - A5x86 X5 P75 - 64MB - AHA-2842A VLB - ET4000W32P VLB - CT2230 - GUS ACE - MPU-401AT with YucatanFX
Win98SE: Asus P5K-WS - E8600 @ 4,5GHz - Strange God Voodoo 5 6000 PCI-X - 2GB DDR2 1066 - Audigy 2 ZS

Reply 10 of 21, by stinkydiver

User metadata
Rank Newbie
Rank
Newbie

I've re-set JP16 back to 5-6 (and let me tell you, changing jumpers with the motherboard INSIDE the case is like trying to steal the NOC list, needs a steady hand and calm breath)

With the IDE cable to the i/o card removed and hard drive set to none in the bios the computer still refuses to boot from floppy disk.

If I disable the L1 cache in the bios, floppy boot works. I should say though, the floppy drive itself does not sound happy, it kinda chugs, spurs and spurts a littler louder and longer than usual.. I don't think it likes this CPU

Take that there and put it in here

Reply 11 of 21, by Jackhead

User metadata
Rank Oldbie
Rank
Oldbie

It sounds like same problem I had. I also notice sometimes an ide CD-ROM can't read a disc. As I sad switching to scsi and a controller with WB cache anything works fine.

Dos 6.22: Asus VL/I-486SV2GX4 Rev 2.0 1Mb L2 - A5x86 X5 P75 - 64MB - AHA-2842A VLB - ET4000W32P VLB - CT2230 - GUS ACE - MPU-401AT with YucatanFX
Win98SE: Asus P5K-WS - E8600 @ 4,5GHz - Strange God Voodoo 5 6000 PCI-X - 2GB DDR2 1066 - Audigy 2 ZS

Reply 12 of 21, by mkarcher

User metadata
Rank l33t
Rank
l33t

I am acutally quite surprised that the AHA-2842 helps with the floppy issue. It has a standard Intel 82077 floppy controller (which supports 2.88MB floppy drives and floppy streamers at 1MBit/s), but that one is connected to the ISA bus like any other floppy controller is as well, and it uses ISA DMA channel 2 like any other floppy controller. I also don't think the I saw some cache workarounds in the BIOS of the 2842, when looking at EDD support for it (although I don't specifically remember looking at the 2842A, just at the 2842VL, the earlier revision of that card).

On the other hand, I do understand that the bus-mastering VL SCSI controller has WB support (which may be disabled using a jumper). On compatible mainboards with that jumper set, the SCSI part is supposed to work perfectly with L1WB. Removing that jumper will break L1WB operation, but may fix L1WT operation on incompatible mainboards.

Indeed, the key point to get L1WB working is to have

  • The HITM pin from the processor routed to the correct pin of the chipset
  • The chipset in the correct mode to wait for and recognize the HITM signal on every ISA DMA cycle
  • The processor receive a valid INV signal on DMA writes

The first item requires correct processor type jumpering. Jumpering for a Enhanced DX2 WB processor or an Enhanced DX4 WB processor should include the correct routing of the signals. HITM* from the processor socket is supposed to be connected to pin 90 of the SiS 471.

The second item typically requires proper initialization of the chipset by the BIOS, but in the case of the 471, the hardware "traps" (nowadays, we call stuff like this "straps") need to be set appropriately as well. Bit 4 of chipset register 50 needs to be set if a L1WB processor is operating in L1WB mode. As the datasheet says, the BIOS should only set that bit if the traps are set to either Cyrix M6/M7 or P24D/T mode. The AMD 5x86 is compatible with the P24D/T mode, and incompatible with the Cyrix M6/M7 mode, so you require the traps to be set to P24D/T and the cache mode bit needs to be set. JP5 and JP6 need to bne set in a way that pins 190 and 191 are both pulled high (possibly that is what the setting "both to 1-2" does). For setting the cache mode bit, you rely on the BIOS to do the correct thing, and that may be a problem: You recognize WB processors by them having specific "well-known" CPU IDs. The AMD 5x86 in 4x clock mode uses CPU IDs no other processor used before, so if a BIOS is older than the 5x86 (aka X5 or DX5) specification, the ID is not "well-known", and the chipset will not be prepared for L1WB operation. Intel and AMD CPUs can not be software-configured to L1WB or L1WT, but they rely entirely on hardware strapping, so a working L1WB solution for Intel/AMD requires the WB/WT jumper to enable the L1WB enhanced bus protocol, the chipset (s)trapping and the L1WB enable bit of the chipset all to be in sync, or bad things will happen, so with a BIOS that doesnt support the 5x86, you are out of luck, at least in 4x mode. In 3x mode, the CPU ID of an AMD 5x86 looks similar enough to WB-enabled Intel DX4 processors, so a BIOS supporting those Intel processors might support the 5x86 in "DX4 mode" as well.

The this item is usually acomplished by shorting the INV pin with the W/R pin at the 486 socket, which is done using a jumper.

The L1WB mode in the BIOS setup will enable or disable the software-controlled L1WB mode of Cyrix processors, and if the BIOS is behaves remotely sensible, also configure the chipset accordingly if a Cyrix processor is installed, but the effect of that BIOS option for Intel and AMD processors is not well-defined. As the L1WB mode of those processors is hardware defined, it does not really make sense to configure the chipset based on a software option instead of the CPU ID. On the other hand, it makes some sense to let the expert user override the CPU-ID based determination of the WB/WT mode of Intel/AMD processors in case the CPU ID is not clearly recognized. So there are reasons to ignore this option for Intel/AMD and reasons to apply this option for Intel/AMD.

You can verify the connection of HITM* to the chipset and of INV to W/R using a continuity checker. You can also verify whether the traps are both pulled up using electrical measurements (likely JP5/6 have pin 1 to Vcc/GND, pin 3 to GND/Vcc and pin 2 via 2k2 to the corresponfing trap pin). You can only hope the BIOS does the right thing if the hardware settings all line up perfectly.

Reply 13 of 21, by stinkydiver

User metadata
Rank Newbie
Rank
Newbie

Thank you for the detailed response @mkarcher.

I have another VLB i/o card I could try..

It has a Goldstar prime 2c 9434 chip and compass lab CL3202 9432 z06 chip

I played around with the hardware trap settings again and can confirm no other configuration other than jp5 1-2 and jp6 2-3 work. Anything else and the computer fails to recognise floppy / ide drives.

It is likely l will just have to live with the CPU in WT mode, or set it to WB and disable the L1 cache when required for floppy disk use.

Take that there and put it in here

Reply 14 of 21, by majestyk

User metadata
Rank Oldbie
Rank
Oldbie

Here are my settings for Am5x86 @ 160 MHz with L1WB and L2WB, no issues booting from floppy or harddrive:

The attachment gx4_wb.JPG is no longer available

Reply 15 of 21, by stinkydiver

User metadata
Rank Newbie
Rank
Newbie

What are your hardware trap settings? Also what revision motherboard? I have a rev 2.0

Also you appear to have your voltage set to 3.6v

Take that there and put it in here

Reply 16 of 21, by majestyk

User metadata
Rank Oldbie
Rank
Oldbie

Mine is 2.0 also, JP5 and JP6 are both set to "1-2".

(Voltage setting to 3.45 or 3.6 doesn´t make a difference here.)

Reply 17 of 21, by stinkydiver

User metadata
Rank Newbie
Rank
Newbie
majestyk wrote on 2025-07-09, 05:52:

Here are my settings for Am5x86 @ 160 MHz with L1WB and L2WB, no issues booting from floppy or harddrive:

The attachment gx4_wb.JPG is no longer available

Good sir, thank you for your insight.

I have set JP 16 to 1-2 , 4-5
Hardware trap to 1-2, 1-2

System boots off floppy OK and hard drive OK, and write back mode is enabled! Huzzah

Last edited by stinkydiver on 2025-07-13, 22:33. Edited 2 times in total.

Take that there and put it in here

Reply 18 of 21, by stinkydiver

User metadata
Rank Newbie
Rank
Newbie

BIOS L1/L2 CACHE SET TO WRITE BACK MODE:
CacheChk
L1 (16KB) - 135.5 MB/s 7.7ns
L2 (256KB) - 44.2 MB/s 23.7ns
Main Memory Speed - 14.1 MB/s 74.6ns
Effective RAM Access Time (read) - 298ns
Effective RAM Access Time (write) - 97ns

BIOS CACHE SET TO AUTO MODE
CacheChk
L1 (16KB) - 135.5 MB/s 7.7ns
L2 (256KB) - 44.2 MB/s 23.7ns
Main Memory Speed - 31.1 MB/s 33.7ns
Effective RAM Access Time (read) - 134ns
Effective RAM Access Time (write) - 97ns

Speedsys CPU score 50.26
SpeedSys Cache/Memory Benchmark
L1 - Read 124 MB/s, Write 39.59 MB/s, Move 155.42 MB/s, Average 106.35 MB/s
L2 - Read 40.66 MB/s, write 39/47 MB/s, Move 20.22 MB/s, Average 33.41 MB/s
Memory - Read 28.47 MB/s, Write 39.57 MB/s, Move 13.92 MB/s, Average 27.32 MB/s

From what I understand, the BIOS needs to be set to AUTO mode for WB to function, manually setting it to WB results in poor performance as you can see in those first results

Last edited by stinkydiver on 2025-07-14, 00:07. Edited 1 time in total.

Take that there and put it in here

Reply 19 of 21, by jakethompson1

User metadata
Rank Oldbie
Rank
Oldbie
stinkydiver wrote on 2025-07-13, 22:26:
BIOS L1/L2 CACHE SET TO WRITE BACK MODE: CacheChk L1 (16KB) - 135.5 MB/s 7.7ns L2 (256KB) - 44.2 MB/s 23.7ns Main Memory Speed […]
Show full quote

BIOS L1/L2 CACHE SET TO WRITE BACK MODE:
CacheChk
L1 (16KB) - 135.5 MB/s 7.7ns
L2 (256KB) - 44.2 MB/s 23.7ns
Main Memory Speed - 14.1 MB/s 74.6ns
Effective RAM Access Time (read) - 298ns
Effective RAM Access Time (write) - 97ns

Might you be in 8+0 tag ("always dirty") mode here? The L1 and L2 are good but memory is bad here. Compare to two optimized DX2-66es over here: Re: UM481/UM491 "Always Dirty" modification HOWTO
The Award BIOS provides no user-visible option for this; you have to use Modbin to flip the appropriate chipset register bit and reflash. Or, you could have a small .COM file to do it on each boot.