Archived from groups: alt.comp.periphs.mainboard.soyo (
More info?)
"WayneM" <me@privacy.net> wrote in message
news:i5o0d.21487$2s.5970@twister.nyroc.rr.com...
> Thanx, Ron.
>
> I think SOYO has a BIOS update but I'm reluctant to try a flash since I'm
> rather a novice at this stuff and have never flashed a BIOS. SOYO
indicates
> that you can't go back if the flash is bad and must send the BIOS rom to
> SOYO for fixing.
No, if for some extremely obscure reason the flashing process gets
interrupted(30 seconds long process) then one might end up in a situation
where a new BIOS chip is needed. Often interrupted flashing IS recoverable.
Notice...obscure...might etc...it's quite safe. Worry more about giant
meteroid impact and carefully flash the BIOS in the absence of a storm or
nearby electrician.
> "Ron Reaugh" <rondashreaugh@att.net> wrote in message
> news:tun0d.342523$OB3.4637@bgtnsc05-news.ops.worldnet.att.net...
> >
> > "WayneM" <me@privacy.net> wrote in message
> > news:dTf0d.21415$2s.5792@twister.nyroc.rr.com...
> >> I have a SY-P4I865PE Plus DRAGON 2 v1.0 (Prescott-Ready) mobo that I
plan
> > on
> >> using in the near future. The major differences between these boards
> >> seems
> >> to be no RAID and 4 memory slots on the v 1.0 board.
> >>
> >> Therefore, I was wondering if anyone knows if the problems dealing with
> > the
> >> I865PE chipset apply to this board or just to the SY-P4I865PE Plus
DRAGON
> > 2.
> >> The SOYO website indicates that the DRAGON 2 needs a BIOS update but it
> >> doesn't indicate that the v1.0 needs an update.
> >
> > The issue is an SP2 plus Prescott, Celeron D and Extreme Edition issue.
> > Have one of those processors then flash a very recent BIOS. Assume
claims
> > of "Prescott Ready" are inaccurate unless the BIOS version is Aug.2004
or
> > later.
> >
> >> "Ron Reaugh" <rondashreaugh@att.net> wrote in message
> >> news:nEt%c.325984$OB3.291945@bgtnsc05-news.ops.worldnet.att.net...
> >> >
> >> > "Jim B" <j.burghdoff@sbcglobal.net> wrote in message
> >> > news:7kq%c.13556$FV3.594@newssvr17.news.prodigy.com...
> >> >> Well Ron,
> >> >>
> >> >> I have an Abit IC7 Max 3 that ran fine with a Northwood in the
board.
> > Put
> >> > in
> >> >> a Prescott and it won't take SP-2, why? Improper microcode.
> >> >
> >> > Yep, just a Prescott, Celeron D & Extreme Edition issue.
> >> >
> >> >>This after
> >> >> putting in the latest BIOS of 5 that update the cpu microcode.
> >> >
> >> > Not to a high enough version of microcode.
> >> >
> >> >> I've got a customers MIS 865PE Neo2 Platinum here as well. The owner
> >> > updated
> >> >> from a 2.8 Northwood to a 3.0 Prescott after he already had SP-2 on
> >> >> the
> >> >> system. What do you think happened? It won't load the operating
system
> >> >> anymore. Some how it lists an improper microcode.
> >> >
> >> > Curious. Where and how exactly is it saying "improper microcode"?
> >> >
> >> >> I've flashed it to there
> >> >> lastest BIOS update for the board. Two which updated the cpu
microcode
> >> > after
> >> >> the BIOS update that gives the board Prescott support.
> >> >
> >> > Not the right microcode in their BIOS yet. Run Intel's Frequency ID
> >> > utility
> >> > and the "CPU revision =" must be 7 or 8 or higher.
> >> >
> >> >> I find it funny you don't think its a problem with the Intel 865 and
> > 875
> >> >> chipsets when Intel is aware of the problem.
> >> >
> >> > Yes and it's a CPU microcode issue and not a chipset issue and that
is
> >> > what
> >> > Intel is aware of.
> >> >
> >> > See:
http://support.microsoft.com/default.aspx?kbid=885626
> >> >
> >> >> By the way I'll ad that neither Abit or MIS has anything on there
web
> >> > sites
> >> >> about this problem or when a fix will be out.
> >> >
> >> > Yep, many are well behind the curve on this one.
> >> >
> >> >> "Ron Reaugh" <rondashreaugh@att.net> wrote in message
> >> >> news
😛F4%c.319037$OB3.254338@bgtnsc05-news.ops.worldnet.att.net...
> >> >> >
> >> >> > "Jim B." <j.burghdoff@sbcglobal.net> wrote in message
> >> >> > news:a182f0ed.0409061132.b5252b8@posting.google.com...
> >> >> >> Flavio <flavioantonucci@yahooremovethis.ca> wrote in message
> >> >> >
> > news:<MPG.1ba618ea6266ad5a9896bf@nntp.bloor.is.net.cable.rogers.com>...
> >> >> >>
> >> >> >> This problem isn't just limited to Soyo. I'm having the same
> >> >> >> problem
> >> >> >> with Abit as well. You see the problem isn't really the
motherboard
> >> >> >> manufacturers problem but an Intel problem.
> >> >> >
> >> >> > There is NO evidence of that.
> >> >> >
> >> >> >> It's a problem with the
> >> >> >> 865, 875 chipsets
> >> >> >
> >> >> > NO!
> >> >> >
> >> >> >> and since these chips were made by Intel and not
> >> >> >> Soyo or Abit or whoever, you can't really lay blame on them.
> >> >> >
> >> >> > Nonsense.
> >> >> >
> >> >> >> As soon
> >> >> >> as the motherboard manufacturers are given the information they
> >> >> >> need
> >> >> >> to update there BIOS files to correct the problem you will most
> > likely
> >> >> >> see it addressed.
> >> >> >
> >> >> > Some mobo mfgs already have the correct Prescott microcode. Soyo
> >> >> > not
> >> > yet,
> >> >> > why?
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>
>
Facebook
Twitter
Instagram