kenzok77
12-03-2003, 15:24
Eccovi la fonte (The Inquirer).
Come dice l'articolo la MSI, ed io aggiungo, anche la Chaintech
hanno un jumper in piu' che risolve il problema.
Io ho controllato la mia Zenith 7NJS, qualcuno mi conferma anche la
Apogee?
----------------------------------------------------------------------------------
Nforce 2 BIOS problems confirmed and fixed
The perils of ignoring the reference design
By Arron Rouse: martedì 11 marzo 2003, 19.10
A SHORT WHILE AGO WE REPORTED that there could be a serious problem with Nforce 2 chipset motherboards. No sooner had the article gone up than Nvidia got in contact wanting to know all of the details.
Users of a new Shuttle Nforce 2 based machine had reported problems with the BIOS. They had been trying to overclock their machines only to find that, once they went past a certain point, the machine would stop working.
At first it looked like a problem with the Shuttle but then Asus motherboard owners reported the same problem. Then Abit and Epox. Not only would they stop working, it was proving difficult to get them working again.
Nvidia stepped into the breach and admitted that there was a fault with the Shuttle and Abit boards. The fault lay in the manufacturers missing off a jumper that Nvidia had specified on the Nforce 2 reference design.
Hard Tecs 4U, a German site, unwittingly uncovered the missing jumper. They had reviewed six Nforce 2 motherboards from different manufacturers and managed to kill all of them. The only one that was easy to recover was an MSI K7N2-L board which has the jumper. Using the jumper sets the BIOS back to a 100MHz FSB safe mode.
Other people had discovered that you could use a 100MHz FSB processor, for example a Duron, in a motherboard that had stopped working to get it going again.
And there lies the problem. Setting the FSB too high can stop Nforce 2 motherboards from POSTing. Once the motherboard has stopped POSTing, the only way to get it going again is to reset the FSB back down to 100MHz. Only most motherboards don't have the jumper so you can't do that.
Nvidia obviously knew about this problem because they built the reference Nforce 2 motherboard with that jumper. The fact that many manufacturers didn't put the jumper onto their motherboards means that someone deserves a slapped wrist at the very least. Whether that's Nvidia for not emphasising the need for the jumper or the manufacturers for not including it is something we may never know.
However, what we do know is that a fix will soon be at hand for everyone. Nvidia has managed to create a fix for the BIOS on Nforce 2 motherboards that will solve the issue. That fix has already gone to several manufacturers who should be able to supply an updated version of the BIOS for their specific motherboards soon.
Nvidia has said that it managed to get that BIOS fix to Shuttle the next working day after our initial article. Hats off to Nvidia for getting the problem sorted so quickly. µ
-----------------------------------------------------------------------------------
Come dice l'articolo la MSI, ed io aggiungo, anche la Chaintech
hanno un jumper in piu' che risolve il problema.
Io ho controllato la mia Zenith 7NJS, qualcuno mi conferma anche la
Apogee?
----------------------------------------------------------------------------------
Nforce 2 BIOS problems confirmed and fixed
The perils of ignoring the reference design
By Arron Rouse: martedì 11 marzo 2003, 19.10
A SHORT WHILE AGO WE REPORTED that there could be a serious problem with Nforce 2 chipset motherboards. No sooner had the article gone up than Nvidia got in contact wanting to know all of the details.
Users of a new Shuttle Nforce 2 based machine had reported problems with the BIOS. They had been trying to overclock their machines only to find that, once they went past a certain point, the machine would stop working.
At first it looked like a problem with the Shuttle but then Asus motherboard owners reported the same problem. Then Abit and Epox. Not only would they stop working, it was proving difficult to get them working again.
Nvidia stepped into the breach and admitted that there was a fault with the Shuttle and Abit boards. The fault lay in the manufacturers missing off a jumper that Nvidia had specified on the Nforce 2 reference design.
Hard Tecs 4U, a German site, unwittingly uncovered the missing jumper. They had reviewed six Nforce 2 motherboards from different manufacturers and managed to kill all of them. The only one that was easy to recover was an MSI K7N2-L board which has the jumper. Using the jumper sets the BIOS back to a 100MHz FSB safe mode.
Other people had discovered that you could use a 100MHz FSB processor, for example a Duron, in a motherboard that had stopped working to get it going again.
And there lies the problem. Setting the FSB too high can stop Nforce 2 motherboards from POSTing. Once the motherboard has stopped POSTing, the only way to get it going again is to reset the FSB back down to 100MHz. Only most motherboards don't have the jumper so you can't do that.
Nvidia obviously knew about this problem because they built the reference Nforce 2 motherboard with that jumper. The fact that many manufacturers didn't put the jumper onto their motherboards means that someone deserves a slapped wrist at the very least. Whether that's Nvidia for not emphasising the need for the jumper or the manufacturers for not including it is something we may never know.
However, what we do know is that a fix will soon be at hand for everyone. Nvidia has managed to create a fix for the BIOS on Nforce 2 motherboards that will solve the issue. That fix has already gone to several manufacturers who should be able to supply an updated version of the BIOS for their specific motherboards soon.
Nvidia has said that it managed to get that BIOS fix to Shuttle the next working day after our initial article. Hats off to Nvidia for getting the problem sorted so quickly. µ
-----------------------------------------------------------------------------------