Sign in with
Sign up | Sign in
Your question

P4i865PE SP2 and Prescott issue - still not in knowledgebase

Last response: in Motherboards
Share
Anonymous
a b V Motherboard
September 6, 2004 3:48:49 PM

Archived from groups: alt.comp.periphs.mainboard.soyo (More info?)

Soyousa has still not posted on their website or knowledgebase
anything about the incompatability with their P4i865PE SP2 and
Prescott issue. This is a disgrace.

Time is money, and so it appears, they'd rather have customers
opening trouble tickets, or calling about a known issue.

I've owned other motherboards in the past, Abit, Asus, Intel,
and now Soyo. This is the last time I'll think of saving money
with a cheap product. You get what you pay for. They don't even
have the tech support phone number on line. First you call their
head office, and the greeting immediately states that if you
want tech support, to call a different number. HOW STUPID. They
should add it to their website, and stop an already frustrated
customer with more BS.

Just had to get that off my chest.

Flavio.
Anonymous
a b V Motherboard
September 6, 2004 4:32:58 PM

Archived from groups: alt.comp.periphs.mainboard.soyo (More info?)

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. It's a problem with the
865, 875 chipsets and since these chips were made by Intel and not
Soyo or Abit or whoever, you can't really lay blame on them. 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.

My biggest complaint at the moment with Soyo is the lack of Intel 915
and 925 based motherboards.

> Soyousa has still not posted on their website or knowledgebase
> anything about the incompatability with their P4i865PE SP2 and
> Prescott issue. This is a disgrace.
>
> Time is money, and so it appears, they'd rather have customers
> opening trouble tickets, or calling about a known issue.
>
> I've owned other motherboards in the past, Abit, Asus, Intel,
> and now Soyo. This is the last time I'll think of saving money
> with a cheap product. You get what you pay for. They don't even
> have the tech support phone number on line. First you call their
> head office, and the greeting immediately states that if you
> want tech support, to call a different number. HOW STUPID. They
> should add it to their website, and stop an already frustrated
> customer with more BS.
>
> Just had to get that off my chest.
>
> Flavio.
Anonymous
a b V Motherboard
September 7, 2004 1:29:57 AM

Archived from groups: alt.comp.periphs.mainboard.soyo (More info?)

"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?
Anonymous
a b V Motherboard
September 7, 2004 1:08:15 PM

Archived from groups: alt.comp.periphs.mainboard.soyo (More info?)

On Mon, 06 Sep 2004 11:48:49 GMT, Flavio
<flavioantonucci@yahooremovethis.ca> wrote:

>Soyousa has still not posted on their website or knowledgebase
>anything about the incompatability with their P4i865PE SP2 and
>Prescott issue. This is a disgrace.
>
>Time is money, and so it appears, they'd rather have customers
>opening trouble tickets, or calling about a known issue.
>
>I've owned other motherboards in the past, Abit, Asus, Intel,
>and now Soyo. This is the last time I'll think of saving money
>with a cheap product. You get what you pay for. They don't even
>have the tech support phone number on line. First you call their
>head office, and the greeting immediately states that if you
>want tech support, to call a different number. HOW STUPID. They
>should add it to their website, and stop an already frustrated
>customer with more BS.
>

Here is a interesting thread about SP2 problem on i865 and i875
chipsets:

http://forums.whirlpool.net.au/forum-replies.cfm?t=2271...

summa summarum: get newest bios

and here:

http://www.thespoke.net/MyBlog/Tudy/MyBlog.aspx

and here:

http://www.howtofixcomputers.com/bb/sutra260408.html

So there _are_ severe problems for some.

best regards

John
Anonymous
a b V Motherboard
September 7, 2004 2:31:10 PM

Archived from groups: alt.comp.periphs.mainboard.soyo (More info?)

Jim,
without trying to lay blame on anyone, as long as SOYO knows
that there is an issue with one of their products, they should
post it for customers to all know that:

1. They are aware and working on an update
2. The estimated time for the update is within 1 day/week/month.
3. In the meantime, customers should not attempt to install SP2.
4. They will keep the knowledgebase updated with any newer
information as it becomes available.

In article <a182f0ed.0409061132.b5252b8@posting.google.com>,
j.burghdoff@sbcglobal.net says...
> 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. It's a problem with the
> 865, 875 chipsets and since these chips were made by Intel and not
> Soyo or Abit or whoever, you can't really lay blame on them. 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.
>
> My biggest complaint at the moment with Soyo is the lack of Intel 915
> and 925 based motherboards.
>
> > Soyousa has still not posted on their website or knowledgebase
> > anything about the incompatability with their P4i865PE SP2 and
> > Prescott issue. This is a disgrace.
> >
> > Time is money, and so it appears, they'd rather have customers
> > opening trouble tickets, or calling about a known issue.
> >
> > I've owned other motherboards in the past, Abit, Asus, Intel,
> > and now Soyo. This is the last time I'll think of saving money
> > with a cheap product. You get what you pay for. They don't even
> > have the tech support phone number on line. First you call their
> > head office, and the greeting immediately states that if you
> > want tech support, to call a different number. HOW STUPID. They
> > should add it to their website, and stop an already frustrated
> > customer with more BS.
> >
> > Just had to get that off my chest.
> >
> > Flavio.
>
Anonymous
a b V Motherboard
September 8, 2004 2:09:07 AM

Archived from groups: alt.comp.periphs.mainboard.soyo (More info?)

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. This after
putting in the latest BIOS of 5 that update the cpu 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. 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.

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.

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.
"Ron Reaugh" <rondashreaugh@att.net> wrote in message
news:p 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?
>
>
Anonymous
a b V Motherboard
September 8, 2004 4:32:31 AM

Archived from groups: alt.comp.periphs.mainboard.soyo (More info?)

"JK ( at mail dot dk)" <johnknuhtsen@address.invalid> wrote in message
news:ucnqj01an6mh6umqrfi77fq0uau4kmdj79@4ax.com...
> On Mon, 06 Sep 2004 11:48:49 GMT, Flavio
> <flavioantonucci@yahooremovethis.ca> wrote:
>
> >Soyousa has still not posted on their website or knowledgebase
> >anything about the incompatability with their P4i865PE SP2 and
> >Prescott issue. This is a disgrace.
> >
> >Time is money, and so it appears, they'd rather have customers
> >opening trouble tickets, or calling about a known issue.
> >
> >I've owned other motherboards in the past, Abit, Asus, Intel,
> >and now Soyo. This is the last time I'll think of saving money
> >with a cheap product. You get what you pay for. They don't even
> >have the tech support phone number on line. First you call their
> >head office, and the greeting immediately states that if you
> >want tech support, to call a different number. HOW STUPID. They
> >should add it to their website, and stop an already frustrated
> >customer with more BS.
> >
>
> Here is a interesting thread about SP2 problem on i865 and i875
> chipsets:

It's not really an 865/875 chipset issue but a Prescott, Celeron D & Extreme
Edition issue.
MS article:
http://support.microsoft.com/default.aspx?kbid=885626
Anonymous
a b V Motherboard
September 8, 2004 5:55:32 AM

Archived from groups: alt.comp.periphs.mainboard.soyo (More info?)

"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:p 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?
> >
> >
>
>
Anonymous
a b V Motherboard
September 10, 2004 3:04:41 PM

Archived from groups: alt.comp.periphs.mainboard.soyo (More info?)

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.

Wayne
"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:p 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?
>> >
>> >
>>
>>
>
>
Anonymous
a b V Motherboard
September 10, 2004 11:44:25 PM

Archived from groups: alt.comp.periphs.mainboard.soyo (More info?)

"WayneM" <me@privacy.net> wrote in message
news:D Tf0d.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:p 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?
> >> >
> >> >
> >>
> >>
> >
> >
>
>
Anonymous
a b V Motherboard
September 11, 2004 12:25:50 AM

Archived from groups: alt.comp.periphs.mainboard.soyo (More info?)

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.

Wayne

"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:D Tf0d.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:p 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?
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
>
Anonymous
a b V Motherboard
September 11, 2004 1:55:36 AM

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:D Tf0d.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:p 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?
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>
>
!