Inferno Katana Beta bios G16 and G14-gti plus new tweaker firmware

[Lord Trident]

Ok latest bios for Inferno Katana
lots of fixes and even the P55 iphone fix as well

sorry i do have the list but to busy to list up what fixed

have fun


Inferno Katana G16
http://www.ex3clan.com/foxconn/Infer..._-979F1G16.zip

Inferno Katano GTI G14
http://www.ex3clan.com/foxconn/Infer...I-97AF1G14.zip


For the overclock chip
Tweaker FIrmware
http://www.ex3clan.com/foxconn/Infer...12110-beta.zip

[saaya]

does setfsb or the foxconn ocing tool work on it now?
or still only bios ocing? :/

[Lord Trident]

no idea
noone every reported it did not work, think you was the only one to say it does not work so you should have contacted the person that make setfsb with the information lol

[Chebu]

@saaya: The Foxconn AegisPanelEx (for oc in windows) works fine since the first day.

@Lord Trident: I tried the new beta bios on my inferno katana:

bugs since BIOS P04:
1) switching between "dynamic mode" and "fixed mode" without cmos-reset before switching results in overvolting the vcore
- for e.g.: selected in BIOS: 1.25v -> hardware monitor and measure point for vcore: 1.55v !!!
2) current core speed in post-screen shows only cpu standard clock while overclocking

wishes:
1) lower pll-voltage than 1.70v
2) lower vdimm than 1.40v
3) lower vref than 0.69v

[Lord Trident]

thanks for the information
will pass on thanks

[saaya]

no idea
noone every reported it did not work, think you was the only one to say it does not work so you should have contacted the person that make setfsb with the information lol

http://www.benchtec.co.uk/index.php/...na-gti-review/

Due to a couple of reasons, one being simply time, and secondly the lack of a Windows tool to adjust the bclk, I wasn’t able to get the maximum performance possible out of this board. I’d be willing to put money on being able to get to 220bclk with setfsb or an equivalent, as the system could fully boot and run SuperPi 32M at 215.

and there is nothing hiyo can do with setfsb since the pll is controlled by the i-tweaker chip afaik...

@saaya: The Foxconn AegisPanelEx (for oc in windows) works fine since the first day.

your the first person who said that... i thought there was no tool for inferno katana at all? which version of aegis panel EX do you use? and bclock adjustments work???
so far i havent seen a single person manage to get a higher bclock than what they can boot at, cause there is no way to adjust the clocks within windows...

[Chebu]

http://www.quantum-force.net/pub/Dow...202.1.2.68.zip

[saaya]

http://www.quantum-force.net/pub/Dow...202.1.2.68.zip

and that supports bclock adjustments?

[Chebu]

and that supports bclock adjustments?

yes. fan speed, voltages and bclk are adjustable. note: vcore is only adjustable if "fixed mode" in bios is activated.

[saaya]

yes. fan speed, voltages and bclk are adjustable. note: vcore is only adjustable if "fixed mode" in bios is activated.

sorry if i ask again, but have you actually tried it? can you post a screenshot of lets say 220bclock or higher? shouldnt be a problem as 215bclock is benchstable, and ive seen boards reach 240bclock within windows without too much hassle..

[Lord Trident]

the reason people have problem is they using the gti version which is a lot poor at overclocking
you need to add heatsink to the voltage reg, the full version board is a lot better but not many out there (think none in the EU)

i will see if i can get information to the guy who make setfsb so keeping you happy saaya lol

[Chebu]

well, at least one full version katana has reached europe...

[Lord Trident]

lol think i got the other 2
and one of them is my work machine now

[saaya]

the reason people have problem is they using the gti version which is a lot poor at overclocking
you need to add heatsink to the voltage reg, the full version board is a lot better but not many out there (think none in the EU)

i will see if i can get information to the guy who make setfsb so keeping you happy saaya lol

that would only affect stability under cpu load... it should affect bclock overclocking at all :P

go ahead and try, i talked to him way before inferno katana was launched and the engineers told me there was no way to get to the pll besides going through the micro controller, and they wouldnt open that up to third party tools... then again, they told me many things were impossible and i know its not true... and some you managed to make them get done

but dont waste your time on this...
1. i only heard from 4 people using that board, one guy from foxconn china, rich who reviewed it, you, and chebu... so chebu is the only non foxconn employee who played with it that i know of the katana is off the radar for 99% of enthusiasts, the people who buy it arent into serious ocing so they probably dont care...
2. IF aegis panel really allows bclock adjustments as chebu claims (but didnt show in screenshots :P) then there is no problem... as long as there is a tool, any tool, thats alright...

[Chebu]

2. IF aegis panel really allows bclock adjustments as chebu claims (but didnt show in screenshots :P) then there is no problem... as long as there is a tool, any tool, thats alright...

190 MHz booted BCLK:


200 MHz BCLK adjusted with AegisPanel (CoreTemp shows already booted BCLK!):

[saaya]

190 MHz booted BCLK:


200 MHz BCLK adjusted with AegisPanel (CoreTemp shows already booted BCLK!):

cool!
whats the max bclock you got out of it?

[Chebu]

I need a better cpu to test it. my max is at 205 mhz with 1.4v vtt. -.-

[r1ch]

Hey guys, just to clear this up - at the time I reviewed the board I was told there wasn't a version of Aegis Panel that supported bclk adjustment. I haven't revisited the review since then as I wasn't aware there was a version of Aegis that worked.

And Carl - my results weren't too bad so the GTI board is ok! Granted the extra phases on the non-GTI board can't hurt, but nothing wrong with the GTI

[Chebu]

@Lord Trident: I tried the new beta bios on my inferno katana:

bugs since BIOS P04:
1) switching between "dynamic mode" and "fixed mode" without cmos-reset before switching results in overvolting the vcore
- for e.g.: selected in BIOS: 1.25v -> hardware monitor and measure point for vcore: 1.55v !!!
2) current core speed in post-screen shows only cpu standard clock while overclocking

wishes:
1) lower pll-voltage than 1.70v
2) lower vdimm than 1.40v
3) lower vref than 0.69v

@Lord Trident: can you give me any information or feedback about the bugs?

...and one more wish : can you integrate the option to set the first turbo-multi manually? e.g. multi 22 of a core i7-860...

[Lord Trident]

all i can say is the bug and wish list is passeed to bios person
so it will come but i need more fixes for the destroyer, and i think bloodrage has some more fixes as well

so it will come, just takes time

[Chebu]

all right, thanks!

[saaya]

Hey guys, just to clear this up - at the time I reviewed the board I was told there wasn't a version of Aegis Panel that supported bclk adjustment. I haven't revisited the review since then as I wasn't aware there was a version of Aegis that worked.

And Carl - my results weren't too bad so the GTI board is ok! Granted the extra phases on the non-GTI board can't hurt, but nothing wrong with the GTI

i dont think anybody knew it... none of the reviews mentions the aegis panel tool and iirc thg and anandtech also mentioned that setfsb didnt work and there was no tool to adjust fsb either... thats why i was so surprised to find out it actually works, and for a couple of weeks even apparently...

[Chebu]

@saaya: The Foxconn AegisPanelEx (for oc in windows) works fine since the first day.

@Lord Trident: I tried the new beta bios on my inferno katana:

bugs since BIOS P04:
1) switching between "dynamic mode" and "fixed mode" without cmos-reset before switching results in overvolting the vcore
- for e.g.: selected in BIOS: 1.25v -> hardware monitor and measure point for vcore: 1.55v !!!
2) current core speed in post-screen shows only cpu standard clock while overclocking

wishes:
1) lower pll-voltage than 1.70v
2) lower vdimm than 1.40v
3) lower vref than 0.69v

Are there any news from the programmers front?