Yes those timings plus the 1T 2T command back for san diegos and the vcore voltages back like 1.36b. Oh and a 3.5 HT multi :p and the 183 and 150 dividers showing up in bios would be good to. Get to work MSI :slapass:
Printable View
Yes those timings plus the 1T 2T command back for san diegos and the vcore voltages back like 1.36b. Oh and a 3.5 HT multi :p and the 183 and 150 dividers showing up in bios would be good to. Get to work MSI :slapass:
Yeh those too! :D Although i think it is possible to activate the half HT multipliers on the current bioses. :)
a little fix up on the sensors will be good too..
I'd rather see the extra things added first though, since (hopefully!) issues such as sensor readout are being continually tuned and refined by the MSI bios team. ;)
I would now like to show you MSI's official response to my request. I think they must have an auto-response for whenever they see the words Venice and bios appear on the same page:
"The full testing will be done for the Venice and San Diego Core processor by end of this month which then if the board pass all tests, we will release a bios update."
This is a truly amazing response, since i never even mentioned the venice / san diego issues in my e-mail! The only time i put Venice down was when i listed what CPU i had!!! Not that i expected much, but it would have been nice to actually address my request about the bios! On the plus side, the problems with venice and san diego are being looked in to... :rolleyes: :(
Looks like if we want these extra implementations, it's gonna have to come from a 3rd party modder.
What are the issues whit the venice/sandiago cores ?
Main issue is that some chips, especially the san diego cores, will only run at a command rate of 2T, and not 1T, in the bios.
Yes they have a 2.5 HT multi but not a 3.5. 3.5 being the useful one :p:Quote:
Originally Posted by CD 1986
Anyone know what model bios savior i need for the neo2 they have 3 plcc models
FWIW the latest 1.8 bios has substantially helped my OC and fixed my temperature readings. I'm getting 31C load temps with a slight overvoltage and 30% overclock now. Feels about right when I touch the IHS. I also am hitting speeds I couldn't hit before.
Still not astounding, but 2.4GHz isnt bad for a measly 3000+.
ok so i've created this excel spreadsheet that helps you calculate every possible FSB and Clock Multiplier Combo for a desired CPU Clock OC speed and i'd like you guys to take a look at it and tell me what u think
feel free to virus check it first if u paranoid :stick:
i'm trying to add a few more things to the sheet (like Vcore etc) but i'd need someone who's really really really good at maths to help me there...
edit:
sorry i was busy posting when the site went down last night
Link?
yeah.. where is the link ???
I'm back guys, I've finally picked up a San Diego 3700+ and I've been messing around, so far I've gotten 2.53 which is fine for now since i'm still testing and tweaking, I should try the new MSI bios and see how it runs, also what idle temps whould I be expecting for at least stock speeds?
@BobTheDinosaur
I really like the idea of the drop-down columns! Maybe you could switch the "CPU clock" column to C, so that it is 1st in the list by default. Just makes more sense to me that way. Also, you could try adding a "max multiplier" filter so that only results within a chip's spec come up. :)
@ Uniacid
The latest 1.8 bios is an improvement on previos bioses, so i'd definitely give it a go. Assuming you are using the stock HSF and have good case cooling, idle temps of around 30-35C at stock speeds would be normal IMO. Have you come across the command rate (1T/2T) problem with your san diego and the Neo2?
ok i moved the cpu clock to column C so it shows up first
i can't put in a filter range for the clock ratio tho cos those values aren't calculated by excel, i had to actually fill in all those values in CPU clock and Ratio manually (a lot of pasting)
so if u want to filter the ratios so that only the ones u can use show then just click on the drop down menu by ratios and click on custom, then choose greater than x and less than x and it'll filter for you...
lemme know if u need help using the menus
Which problem is that? also no I am using a water cooling system, mostly DD parts if you read my sigQuote:
Originally Posted by CD 1986
With some san diegos, the 1T option in the bios is unavailable, but can be changed using A64tweaker.
Finally got my mobo sorted and put in the new Venice. Unfortunately i can't boot at all in dual channel (slots 1&2 or 3&4), but can boot ok in single channel, so hopefully a bios update will fix that. So far at 2.7G after 30 mins playing time, so i'm hoping for 2.8G on air eventually. :)
CD 1986
how do u get ur cpu running so cool at such high clocks with stock cooling??!!
my 3500+ is running at 2641MHz at about 45C idle and today i hit 74C at max load! and i've got a zalman cnps7000 Cu with loads of case fans
bobthedino: wat BIOS r u using ? room temp ?
mine is running idle 33C ... load 45C ... ofcoz im WCing
but 30 C betweem idle and load is too much imo...
in that case yes as I don't see it in bios, is it better to have it set to 2T? I forgot what it was forQuote:
Originally Posted by CD 1986
1T is much faster but make sure to test stability with Memtest thorougly...
i'm running bios 1.8 officialQuote:
Originally Posted by harpyboy
room temp is about 21-24C depending on how the aircon is feeling, with some cool air coming in thru the window (it's winter here now) my load temp drops to 70C
i should mention this isn't just the cpu under load, it's my ram (which can hit 40C) and heat monster HDD and OCd gfx card all makin the ambient inside the case higher
@Bob
What core is that 3500? And what voltage are you putting through it?
And as for MY setup, i had a slight setback yesterday when it switched off without warning and wouldn't start back up. I switched PSU in case that was the problem, started the system back up...and got a nice puff of smoke and lick of flame that i swear came up from the socket right through the heatsink! System's now dead. I'm just hoping the chip hasn't been damaged! There were no marks on it, the heatsink or the socket, but knowing my luck at the moment it'll have damaged something! :eek: :(
I feel your pain. Hope its ok mate :stick:Quote:
Originally Posted by CD 1986