Jump to content
HWBOT Community Forums

exaberries

Members
  • Posts

    17
  • Joined

  • Last visited

Converted

  • Location
    Vancouver

Converted

  • realname
    Jason

exaberries's Achievements

Apprentice

Apprentice (3/14)

  • Collaborator Rare
  • Reacting Well Rare
  • Dedicated Rare
  • First Post Rare
  • Conversation Starter Rare

Recent Badges

3

Reputation

  1. I've been messing with this controller for a while now and have some basic voltage control for it. Full range voltage control and other details should be done by the end of the summer. The monitoring should be able to be applied to a 8266 as well. Most of this is based on the xml files detailing the i2c/pmbus interface in the evc2 software + disassembling/decompiling the raspberry pi voltage control software for the epower classified. I also verified this working with a arduino through a level shifter on a 680 classified through the evbot header. Since the epower classified has the controller at address 0x40 instead of 0x46 I modded the binary with a hex editor use the different address. Tested working with the asp1212 on a 780 dcu. Just use vset_mod linked. My test program for the raspberry pi is also linked. To compile it make sure you link with the i2c lib. Heres a pastebin of the arduino code i've been messing with: https://pastebin.com/HwaiEBRU Hopefully this should be enough info for anyone experienced with i2c to get basic voltage control. Once I iron out all the details i'll post a more complete overview with tools. vset_mod asp1212-test-rpi.cpp
  2. Here's the results so far with my 2 kits of 4000-16-16 1.4V ripjaws v: first kit maxes out at around 1.9v struggles more with 3900-12-11-11 190 tRFC second kit goes all the way to 2.0v does 3900-12-11-11 180/190 tRFC pretty easy both kits together run 3250 10-10 pretty easily at 1.75-1.8v still working on 3250 10-9 seems to be still quite a bit of lottery for high scaling but good bin for lower voltages. I got each of these kits for 250 CAD on newegg.ca.
  3. Default was 1.35 I think. I was trying to see how quickly the voltage rised when turning the pot to see what the non linear behavior was like.
  4. So I finally got a 560 ti modded for both core and mem, cap mods, delided, and on an aio and before running any benchmarks I raised memory voltage above 1.7 volts (I don't know exactly what it hit) and had immediate shutoff followed by artifacting and inability to get into windows outside of safe mode. The Elpida datasheets suggests that the gddr5 should tolerate 2v. Its possible that I passed this point but i'm thinking that its more likely the memory controller. At least I already had ordered another 560ti (hopefully without elpida this time). I'm hoping that somene with more experience with this can shed some light on safe memory voltages for fermi cards. I'll post a full rundown of the mods soon.
  5. From what I know you are already basically describing the geekbench memory test. I think it would be better to have two seperate benchmarks rather than a legacy mode. Updating is both kinda necessary to deal with changes in architecure but also a massive problem for rules/scoring. My preference would be having algorithms change with major versions and each major version being a seperate benchmark à la geekbench.
  6. If anyones is looking for boardviews for other stuff: asus: http://schematic-x.blogspot.com/2018/04/asus-pack-198-files.html also has asrock including oc formulas: http://schematic-x.blogspot.com/2019/09/asrock-schematic.html gigabyte: http://schematic-x.blogspot.com/2018/04/gigabyte-schematics-pack.html and gpus: http://schematic-x.blogspot.com/2018/04/blog-post.html
  7. I've never personally had problems just changing without resetting with msconfig on windows 7. I think its the removememory/truncate memory that you have to reset before use but i've only ever tried that once on windows 10.
  8. To add to what leeghoofd said with 3d stacking new cpus might start to have enough cache for entire benchmarks to run in. Though autodetecting the amount of cache and changing the benchmark is a good idea you have to be careful, with new releases it might just start scoring better diminishing the effect actual ram oc. I generally think that having a benchmark which significantly changes the workload it runs based on what hardware its running on can lead to wierd results for global ranking not really a problem for hardware ranking. IMO ideally that platform that the benchmark is run on should have little effect on the score but I know that's not really possible due to the effects of architecture like infinity fabric, etc... I don't think a ram focused benchmark that uses a lot of ram (20GB+) / requires a lot of stability would be interesting since it would limit pushing things the edge. Maybe something that uses about 1GB so maxmem is still a thing but cache hopefully matters less.
  9. (wanted maxmem in GB + 0.8) * 1024 is what I put into msconfig for windows 7 usually as a quick and dirty way to get close. I'm sure someone can give a more accurate way to calculate what the exact value you should enter
  10. Core voltage is where I have the most problems just stop setting at some point randomly, oc panel also can't change vcore anymore. I have more problems when a benchmark such as superpi is open. CPU ratio stops working on the oc panel but continues to work in turbov core sometimes. BCLK continues to work in both. Same issues even when oc panel is not plugged in. I also have been running into a wierd bug where trying to assign per core oc when core are disabled in bios instantly locks the system.
  11. Does anyone have the turbo vcore version/MEI driver. I've been using turbo vcore 1.10.07, 1.01.15 and 1.00.3 with MEI 10001204 and it takes about 3-4 tries for voltages / clock speeds to actually set.
×
×
  • Create New...