BIOS updates for Intel E0 stepping

[not_my_ip]

Thanks Rolo, email sent.

I hope that this bios will bring option for VT

[V3sta]

hmm having the same porb with the FP-In9 Sli and the q9550 e0... wont work even with the v18 bios under dos flashed...

Any suggestios for another board to get without spending more than 60 bucks?! I dont aim for sli or crossfire, but would like to oc the cpu a bit.

[Terry Lei]

Does anyone m629b_18.bin bios? It is for IP35Pro, abit website shows only v17.

Hoping for virtualization option in BIOS, 17 does not give one

Here's IP35 Pro BIOS ( m629b_18 )
http://cid-cf1877b188d90629.office.l...0&sa=210869165

[Tublor]

Here's IP35 Pro BIOS ( m629b_18 )
//cid-cf1877b188d90629.office.live.com/browse.aspx/abit%20BIOS%20updates%20for%20Intel%20E0%20stepping?nl=1&uc=2&wa=wsignin1.0&sa=210869165

Hi, I have a Q9550 E0 I am trying to get working properly on a Abit IP35 Pro XE and have tried the above BIOS (for the XE) but still show's temp as 103C. This BIOS is in fact the same one as the official Abit v11 BIOS from abit.com.tw site. Was there another version from the now discontinued abitshop.eu site and if so can anyone point me to a working link please? Thanks.

[Rolo01]

Hi, I have a Q9550 E0 I am trying to get working properly on a Abit IP35 Pro XE and have tried the above BIOS (for the XE) but still show's temp as 103C. This BIOS is in fact the same one as the official Abit v11 BIOS from abit.com.tw site. Was there another version from the now discontinued abitshop.eu site and if so can anyone point me to a working link please? Thanks.

http://forums.hexus.net/abit-care-he...ml#post2047305

[Tublor]

forums.hexus.net/abit-care-hexus/149415-bios-updates-intel-e0-stepping-10.html#post204730

Thanks but that is the same link as above, ie: the official release from the abit.com.tw website and does not support my Q9550 E0. I have checked it with FC (file compare). I think it must have been uploaded by accident.

There was supposed to be a version tweaked by abit.NL tech support that was hosted on the abitshop.eu website originally posted in this thread that was different to that one (though named the same). Cannot find it anywhere since abitshop.eu went down. If someone could email/pm me a copy or point me to a link that would make me bonkers happy! thanks.

Or is there some way I can turn the fans down with the cpu reporting the incorrect temp to uGuru? Disable uGuru via jumper or something? Core temps are reporting correctly, but uGuru still sees CPU 103C. It works but it's very noisey!

[Rolo01]

Thanks but that is the same link as above, ie: the official release from the abit.com.tw website and does not support my Q9550 E0. I have checked it with FC (file compare). I think it must have been uploaded by accident.

There was supposed to be a version tweaked by abit.NL tech support that was hosted on the abitshop.eu website originally posted in this thread that was different to that one (though named the same). Cannot find it anywhere since abitshop.eu went down. If someone could email/pm me a copy or point me to a link that would make me bonkers happy! thanks.

Or is there some way I can turn the fans down with the cpu reporting the incorrect temp to uGuru? Disable uGuru via jumper or something? Core temps are reporting correctly, but uGuru still sees CPU 103C. It works but it's very noisey!

Try this one :
http://tinyurl.com/6d34bym
Its a copy of the initial file from abitshop.eu

[Tublor]

Try this one tinyurl.com/6d34bym
Its a copy of the initial file from abitshop.eu

That's it, beautiful to see it working! Thanks a ton!

Someone needs to save that somewhere, I'll be keeping a copy.

[Terry Lei]

Try this one :
http://tinyurl.com/6d34bym
Its a copy of the initial file from abitshop.eu

Thanks a lot ^o^

[zooburner]

Links for IP36 pro XE not working

[Rolo01]

Links for IP36 pro XE not working

If you need the bios drop me a line.

[fiveolddogs]

Here's an Abit IP35 and IP35-E BIOS fix. It's based on the last beta BIOS (for the Intel E0 stepping). The fixed issue: VT-x is disabled after resuming from S3 sleep, if there ever was a system reboot/reset, before entering standby. I have tested it on my IP35-E board, but I can't be held responsible for any kind of damages that may occur.

I have the IP35 Pro (P35-ICH9R) mainboard (Q6600 cpu), and I'm having trouble getting VirtualBox to run. It claims I have vt-x disabled, but I have it enabled. This is not after S3 sleep, but all the time, even right after enabling vt-x and booting into Windows 7 64-bit.

Anyone have any suggestions here? Is there any reason to think the S3 vt-x fix above would help me here?

I am hesitant to roll my own bios with this fix. Has anyone applied this fix to the most recent beta with E0 stepping for the IP35 Pro mainboard? If so, could you share the bin file?

Thanks.

[mhanor]

You should not apply the fix if you don't use S3 sleep at all. Shut down the machine (no S3/hibernate), remove the power from the PSU, then power it up again. You can also try to clear the CMOS, or updating the BIOS to a newer official version (without any modding).
I haven't seen any feedback on the fix. As far as I know, I'm the only one running it, on my IP35-E.
Btw, I don't know how IP35 Pro works, but if it doesn't shut itself down and restart itself after enabling VT-x in BIOS, you should power down manually and restart it.

[sqdqin]

yes, i also want to see the result.
pls show us more information.

[mhanor]

sqdqin, to whom are you referring to? what result are you interested in?

[fiveolddogs]

You should not apply the fix if you don't use S3 sleep at all. Shut down the machine (no S3/hibernate), remove the power from the PSU, then power it up again. You can also try to clear the CMOS, or updating the BIOS to a newer official version (without any modding).
I haven't seen any feedback on the fix. As far as I know, I'm the only one running it, on my IP35-E.
Btw, I don't know how IP35 Pro works, but if it doesn't shut itself down and restart itself after enabling VT-x in BIOS, you should power down manually and restart it.

Just wanted to say thanks for this. The unplug trick worked. Too bad there's no way to fix this bug with a BIOS update at this point.