VOGONS


First post, by dave343

User metadata
Rank Member
Rank
Member

I have a P166 MMX build that has been solid, and decided I'd drop in a K6-2 300/66 over the weekend. Since my board is the TX97-E 1.21v I got the jumper settings from here -> http://www.lairdslair.com/TX97E.shtml
The system posted ok and recognized the K6-2 300 properly, but... after it counts the ram and detects the IDE drives, the screen goes black for a second then reboots. It'll just loop like that continuously.
I haven't had time to trouble-shoot yet, I'm thinking maybe the voltage is wrong and too low, but I followed those above settings correctly. Any idea's before I roll up my sleeves tonight? Since the system bus is still 66mhz, I'm thinking it can't be the PCI ATI card, or the nic. I'm using EDO ram although I have no idea what speed since it's unmarked, but it looks a lot newer then old type EDO. I'm leaning towards voltage, but any suggestions or idea's would help, thanks in advance for any replies.

K6-2 300
32mb EDO
ASUS TX97-E
Quantum Fireball 1.2GB
ATI 3D Rage II 2MB
Sound Blaster 16 2940 ISA
AT Case w/200w PSU
Lite-On 48x CD

Last edited by dave343 on 2016-04-25, 16:29. Edited 1 time in total.

Reply 1 of 4, by PhilsComputerLab

User metadata
Rank l33t++
Rank
l33t++

Rather than copying the settings, are the settings silk-screened on the PCB?

I would double and triple check them all based on the actual values, like frequencies, multipliers and voltage. It's also ok to feed the CPU a bit extra voltage in case the right voltage option isn't there.

Clearing CMOS / Loading BIOS defaults might also be a good idea. Oh and is there a BIOS update maybe?

YouTube, Facebook, Website

Reply 2 of 4, by dave343

User metadata
Rank Member
Rank
Member

I'm running the lasted beta BIOS for the board, which was version 0112e-1 with patch J.2 for AMD K6-2+ and K6-III+ support, and for IDE HDDs up to 128GB (32GB bugfix). The settings on board only go up to K6-266, but of course the board will support much higher, K6-2's and 3's up to 550mhz. I know there's a few different revisions of the board's floating around, and they have slightly different settings for the voltage. The fact that it posts and shows K6-2 300 leads me to believe it's at the right speed. Maybe it's set to 2.1V and not the 2.2V it requires... I'll play with it tonight. The link to the settings I provided are for the version of board I have, which is why I tried those settings first.

Last edited by dave343 on 2016-04-25, 18:50. Edited 1 time in total.

Reply 3 of 4, by PhilsComputerLab

User metadata
Rank l33t++
Rank
l33t++

That's good. You can also under-clock it to see if it makes a difference. Something conservative like 66 x 2.5.

And for sure do a clear CMOS.

YouTube, Facebook, Website

Reply 4 of 4, by dave343

User metadata
Rank Member
Rank
Member

Sorry to bump such an old post I made, but I wanted to post a follow up in case anyone else ran into this problem. It's been a long while since I played around with this system, and about 2 weeks I was using a 233mmx cpu in it. I decided to toss in the K6-2 300 chip 2 days ago but had totally forgotten about the reboot issue. Sure enough the system was posting but restarting in a loop. I tried various other K6-2 CPU's, as well as memory switching between SD and EDP ram thinking it was one of those two, but that made no difference.

Finally after googling for a while, I found a post in which someone had the same problem, and followed up that the issue was related to the 18 pin IR adapter that plugs into the board. Now this IR adapter, in my case for the TX97-E has 2 USB ports, a PS2 port and the Infrared plug. At first I thought it was the USB ports maybe pulling too much V, but since I use both the USB ports for a keyboard and mouse on the 233mmx, and the K6-2 actually uses less voltage, I ruled that out.

Solution... cutting the PS2 and IR wires. Wires, or pins, 1-10 (The ones that belong to the IR and PS2) I cut, and the system works flawless now. I'm not sure why that was causing post loops since I had nothing plugged into the PS2 port, nor the IR port, but I'll take the fix.