G38 Bios for Bloodrage and sas firmware

[Lord Trident]

ok some more bios

http://www.ex3clan.com/foxconn/Foxco...1-8A1F1G38.zip

1. Update CPU micro-code for Server and Desk Top Gulftown CPU, stepping B1 CPUID:206C2h Patch ID 0Ch.
2. Update CPU micro-code for Nehalem-EX CPU stepping D0 CPUID:206E6h Patch ID 05h.
1. Modify "B2B CAS Delay" item value from "Auto,3T to 31T" to "Auto,1T to 31T",
Set to Auto the value equal to 0T.


so that is all of B2b open for you and intel spec was only from 3t
for 0t use auto

sas firmware latest we have got
http://www.ex3clan.com/foxconn/Foxco...mware/6320.zip

this may now fix the problem for one person but


well have fun

[ProStock]

Thx a bunch you Rox!!!

[Mescalamba]

Whoa.. time to check 0T.

[lysyn123]

SAS how to install the firmware?

[Lord Trident]

copy the files to a dos boot device and run X58A01.bat

Like a bios or anyother firmware you have to do in dos

thanks

[lysyn123]

copy the files to a dos boot device and run X58A01.bat

Like a bios or anyother firmware you have to do in dos

thanks

I installed the firmware for the SAS Blodrage and now I have an error.

MARVELL 88SE63xx/64xx Adapter - bios version 3.1.0.2400
ERROR: Bios data error!

I installed the firmware for the SAS Blodrage and now I have an error.
What do I do now?

[Lord Trident]

when you get the error as your screen shoot does not show

[lysyn123]

How do you get this error all the stops.

Please give me the old firmware.

[Lord Trident]

no............





you did not say please

http://www.ex3clan.com/foxconn/Foxco.../old%20sas.zip

[lysyn123]

I said please.


I installed the old firmware. It works fine.

My adapter is probably the 6440.
The new firmware does not include the 6440 file.

Please correct.

[Lord Trident]

can you please recheck the chip on your board
it should say 88SE6320-TFJ2

as that the only chip i know of if it not that then i got problem lol

thanks

[lysyn123]

can you please recheck the chip on your board
it should say 88SE6320-TFJ2

as that the only chip i know of if it not that then i got problem lol

thanks

My czipset:

[Lord Trident]

yep that the 6320 and not 6440

i will check again to see why you had a problem

[lysyn123]

yep that the 6320 and not 6440

i will check again to see why you had a problem

Old firmware work ok!!

Maybe there is a bug in the new firmware? I wonder if someone already installed it? Sorry for my English.

[Slayer68]

How does one disable B2B if you can't find a stable setting? Does Auto=0, 0=off?? From what I can tell prior to this B2B is disabled in the BIOS entirely? I ried CPU-Tweaker to see if I could test some B2B settings in windows before flashing to this BIOS but it does not seem to work with the Bloodrage.

[Mescalamba]

You cant disable that, its like if you want disable CL setting.

B2B at 6+ should be like 100% stable for most systems.. (at least 6 is apparently default on mine as I get exactly same results from P09 and G36 set to B2B 6).

Well, and you have two BIOS chips, soo use second and flash it to P10 or P09 if you need to?

[scoobie dave]

Got this running bios running on my gti ok.

I have my ram running @DDR3 2000

What is everyone finding the most stable setting is for the B2B CAS Delay at the moment? For me at the moment its a toss up between 4 and 6 at the moment. Just trying to find the right one. Have to say it does effect stability if on the wrong settings it seems!

Would be really interested in know what other have set it to.

[Mescalamba]

Sure its meant to affect stability. But also affect performace, as usually when one tinker with BIOS.

[mocker]

G38 works really fine, needing 20mV less VTT for same clock Thanx Lord Trident!!!!

[scoobie dave]

G38 works really fine, needing 20mV less VTT for same clock Thanx Lord Trident!!!!

What B2B setting you using?

[mocker]

still 6, but testing now, btw i can reduce VTT even 30mV

[Slayer68]

I'm using B2B of 3 with no problem, the strange thing is it works on 6 fine but 4 will fail almost instantly (Can't even load Windows)

[therager]

I installed the old firmware. It works fine.

My adapter is probably the 6440.
The new firmware does not include the 6440 file.

Please correct.

I did some tests recently with my new raid setup - 2xWD6000HLHX. With stock Marvell SAS firmware v3.1.0.16 it was complete failure. You cannot save created raid volume in bios interface of SAS controller and if you create it from within Marvell software in Windows - after restarting there is no raid volume at all! In this thread I found your negative results with firmware v3.1.0.24. So I searched and found on the Asus forum one different firmware - v3.1.0.23. After quick boot in MS-DOS and easy flash from command line ("mvf 0827.bin") now I have a fully functional SAS with a couple of WD6000HLHX. During the flashing process it says "6440", but it's not correct - the chip is exactly 6320.

PS. Attached v3.1.0.23 SAS firmware.