Reply 20 of 78, by Grem Five
- Rank
- Member
rootinit wrote on 2022-06-24, 17:11:PC Hoarder Patrol wrote on 2022-06-24, 14:40:Whilst faulty is possible (cpu or slotket), don't rule out compatibility as well. […]
rootinit wrote on 2022-06-24, 07:45:Further development. I tossed the same Slotket/CPU combo in my Dell XPS T550, and it was dead as a doornail as well. I know that these are both OEM machines, but I am beginning to think that either the Slotket is bad or the CPU is. Unfortunately, I don't have another Socket 370 CPU to test out. I guess I have to actually order one just to try it?
Whilst faulty is possible (cpu or slotket), don't rule out compatibility as well.
Although I don't have the IBM board for comparison, I do have a Dell XPS Txxx board with the latest A11 BIOS and, like you, a combination of the same Abit Slotket !!! / SL5QV cpu gives me nothing beyond the orange LED on the board, whereas the same cpu but on an MSI MS-6905 Master sloket starts first time.
A quick test on some other BX boards from QDI & Supermicro gave the same results - MSI works but Abit doesn't. I even changed the cpu to a 850/256/100 SL49G but still no go on any BX board with the Abit until I tried the P2B-DS (single cpu only) which worked without issue. Then moving up to a later chipset - the i810E on my Jetway 913AF slot 1 / skt 370 combo board - every cpu worked on the Abit without issue.
Most of the above were tested at both auto & hard FSB / voltage settings without effect, and can't be solely BIOS related either, given the Dell results. Strange indeed!
That is great! You are doing testing where I am unable to. That is really helpful information. Thank you so much. So, perhaps the Abit is not so good with BX boards, and I should work on getting one of those MSIs. Sure the Dell and the IBM are not the same, but they are both 440BX boards, and that is a theme with the Abit.
I don't have an IBM board but if you want I could take pics of the slotkets that work on my Dell board. (doesn't sound like it would be much help for what you started the thread on)