402blownstroker
[H]ard|DCer of the Month - Nov. 2012
- Joined
- Jan 5, 2006
- Messages
- 3,242
Correct. The Supermicro G34 4P boards allow 1, 2, 3, or 4 CPU configurations. Previous generation opteron boards support 1, 2, or 4 CPU configurations.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Correct. The Supermicro G34 4P boards allow 1, 2, 3, or 4 CPU configurations. Previous generation opteron boards support 1, 2, or 4 CPU configurations.
It will run and you will be able to do regular SMP. You'll need a 2nd cpu to do bigadv. And running 1 DIMM will slow things down a bunch.I can run one CPU at a time, correct? So I can get the motherboard, 1GB module of DDR3 1333 CL7 (or should each CPU have 2x1GB DDR3 1333 CL7?), 850W PSU (true 850W PSU from like Antec, Corsair, Seasonic) and I'll be good to go with one CPU and add RAM/CPU as I go?
It will run and you will be able to do regular SMP. You'll need a 2nd cpu to do bigadv. And running 1 DIMM will slow things down a bunch.
Depending on the cpus you get and how much you OC an 850 watt PSU may be borderline. I have a Corsair AX1200 and running my 4 cpus and 16 DIMMS at 3.0GHz it's using over 900 watts.
Which CPUs are you using?
I'm betting on 6180's, or something spicy
Depending on the cpus you get and how much you OC an 850 watt PSU may be borderline. I have a Corsair AX1200 and running my 4 cpus and 16 DIMMS at 3.0GHz it's using over 900 watts.
Which CPUs are you using?
I have two rigs and they both act the same way. Both using 6166HE CPUs.
Works fine here.
What makes you think it loses the OC? Can you show expected and not expected output
of 'dmesg | grep -o Detected.*' ?
Do you lose any other BIOS settings as well? Or just the OC?
modprobe nvram ; hexdump -vC /dev/nvram
Hey,Core32.
I can think of two tests you can run.
First test:
1. Boot the machine and make sure that OC is enabled and FAH isn't running
2. Immediately after bootup run and capture results of:
3. Wait whatever amount of time you need to wait to make the issue manifestCode:modprobe nvram ; hexdump -vC /dev/nvram
  but do not power-cycle the box.
4. Run commands from step #2 again and capture results as well
5. Post both outputs
6. Power-cycle (by means of 'poweroff' command or 'shutdown -P now')
7. Wait few moments and power the machine back on again
8. See if OC persisted.
Second test:
1. Boot the machine and make sure that OC is enabled and FAH isn't running
2. Run: 'sync' and, once it returns, immediately pull the plug (physically)
3. Wait few moments and power the machine back on again
4. See if OC persisted.
gcc -o refclock refclock.c
# ./refclock
Refclock: 225.013 MHz
#
Now there is
-H8QG6~/fah$ dmesg | grep -o Detected.*
Detected 2340.016 MHz processor.
-H8QG6:~/fah$ sudo ../refclock
Refclock: 259.985 MHz
-H8QG6:~/fah$ sudo modprobe nvram
-H8QG6:~/fah$ sudo hexdump -vC /dev/nvram
00000000 00 00 00 30 f0 30 0e 80 02 ff ff 2f 00 ff 3f 10 |...0.0...../..?.|
00000010 00 00 3f 00 00 00 00 00 00 00 00 30 47 47 47 47 |..?........0GGGG|
00000020 06 e6 ff ff 20 bf bf 7e 0d 00 00 00 00 00 00 00 |.... ..~........|
00000030 1e 69 00 00 00 00 00 00 00 00 00 00 00 00 30 03 |.i............0.|
00000040 00 01 00 40 ee f9 00 00 00 00 00 00 00 00 00 00 |...@............|
00000050 00 80 ae 80 00 00 1f 1f ff 00 02 00 00 00 03 21 |...............!|
00000060 54 00 00 03 76 98 00 00 ba 10 32 54 76 98 d9 18 |T...v.....2Tv...|
00000070 ba 00 |..|
00000072
-H8QG6:~/fah$ dmesg | grep -o Detected.*
Detected 1799.904 MHz processor.
-H8QG6:~/fah$ sudo ../refclock
Refclock: 200.000 MHz
-H8QG6:~/fah$ sudo modprobe nvram
-H8QG6:~/fah$ sudo hexdump -vC /dev/nvram
00000000 00 00 00 30 f0 30 0e 80 02 ff ff 2f 00 ff 3f 10 |...0.0...../..?.|
00000010 00 00 3f 00 00 00 00 00 00 00 00 30 47 47 47 47 |..?........0GGGG|
00000020 06 e6 ff ff 20 bf bf 7e 0d 00 00 00 00 00 00 00 |.... ..~........|
00000030 1e 69 00 00 00 00 00 00 00 00 00 00 00 00 30 03 |.i............0.|
00000040 00 01 00 40 ee f9 00 00 00 00 00 00 00 00 00 00 |...@............|
00000050 00 80 ae 80 00 00 1f 1f ff 00 02 00 00 00 03 21 |...............!|
00000060 54 00 00 03 76 98 00 00 ba 10 32 54 76 98 d9 18 |T...v.....2Tv...|
00000070 ba 00 |..|
00000072
I'm setting up a new 4p system and am planning on trying this out.
I'm new to folding though, and was wondering how to save and run a benchmark WU (6903). I didn't realize that was possible, and on my last set up ended up not completing 2 WU's (also didn't know the client wouldn't re-sync with previous WU if re-installed). I of course don't want to tune on a live WU.
Thanks in advance (for this and all the other info I've gathered from this site).
Someone is writing to the NVRAM area used by OCNG, seems. Odd, because per the
BIOS it should be unused (and it isn't used in all other configurations we've seen
to date).
Can you do one more test? Run your usual smocng.sh with your frequency. And then
capture hexdump immediately after running smocng? No need to power-cycle.
BTW, using CODE tag instead of QUOTE tag makes the forum use monospace font
-- much easier to read
-H8QG6:~/fah$ sudo ../smocng.sh 261 16
Success!
To ensure proper application, POWER-OFF the machine, then power it back on again.
-H8QG6:~/fah$ sudo modprobe nvram
-H8QG6:~/fah$ sudo hexdump -vC /dev/nvram
00000000 00 00 00 30 f0 30 0e 80 02 ff ff 2f 00 3d 10 05 |...0.0...../.=..|
00000010 00 00 f6 00 00 00 00 00 00 00 00 30 47 47 47 47 |...........0GGGG|
00000020 06 a1 ff ff 20 bf bf 7e 0d 00 00 00 00 00 00 00 |.... ..~........|
00000030 1d d9 00 00 00 00 00 00 00 00 00 00 00 00 30 03 |..............0.|
00000040 00 01 00 40 ee f9 00 00 00 00 00 00 00 00 00 00 |...@............|
00000050 00 80 ae 80 00 00 1f 1f ff 00 02 00 00 00 03 21 |...............!|
00000060 54 00 00 03 76 98 00 00 ba 10 32 54 76 98 d9 18 |T...v.....2Tv...|
00000070 ba 00 |..|
00000072
I'm setting up a new 4p system and am planning on trying this out.
I'm new to folding though, and was wondering how to save and run a benchmark WU (6903). I didn't realize that was possible, and on my last set up ended up not completing 2 WU's (also didn't know the client wouldn't re-sync with previous WU if re-installed). I of course don't want to tune on a live WU.
Thanks in advance (for this and all the other info I've gathered from this site).
cd ~
cp -a fah fah-test
cd fah-test
./fah6 -configonly
# Go through configuration and enable proxy on some obscure port, like 1234,
# - when client asks whether to use proxy, answer Yes
# - when client asks about Proxy name, answer 127.0.0.1
# - when client asks about Proxy port, answer 1234
# - when client asks to change advanced settings, answer Yes
# - when client asks about system clock having errors, answer Yes (will prevent
# client from deleting the unit when its deadline passes).
# - when client asks about machine ID, set it to a number you don't normally
# use (e.g. 10)
# Once client configuration is done, continue with the following steps
cd work
mv wudata_*.dat ..
rm *
mv ../wudata_*.dat .
cd ~
tar -czf fah-test.tar.gz fah-test
Core32, you did load Optimal Defaults in the BIOS, right? Did you change any other options?
I'm thinking some customization could be responsible for this....
The only other parameter I changed was the fan profile to Balanced from Full.
BIOS settings to check
- PowerNow set to Disabled (see above for the check)
- NUMA/SRAT set to Enabled
- Node Interleaving set to Disabled
- Bank/channel interleaving set to Auto or Enabled
Anyway, here's one more test:
- make sure memtest86 is installed
- run smocng.sh with your usual parameters
- power the machine off
- wait a while, then power it back on; however, do not let it boot; interrupt it in GRUB's (bootloader) menu and start memtest86 instead
- record CPU frequency value from memtest86 (base: 1800)
- power the machine off
- wait a while, then power it back on and start memtest again
- record CPU frequency value again and compare with the previous one
The idea of this test is isolating the issue to either Linux or BIOS.