Latest posts of: hammuh

Code:

    0 01:00.0:Evga GTX 1660__6G 90.16.25.00.3D
    Hash 60.513321M Power 69W/70W Card 54°C Card °C Mem °C Fan 60%
    Core 1725 Mem 4600 VDD MVDD MVDDCI
    1 02:00.0:Evga GTX 1660 Ti__6G 90.16.20.00.A0
    Hash 29.526087M Power 70W/70W Card 51°C Card °C Mem °C Fan 60%
    Core 1275 Mem 6550 VDD MVDD MVDDCI
    2 03:00.0:Evga GTX 1660__6G 90.16.34.00.1C
    Hash 20.752554M Power 69W/70W Card 56°C Card °C Mem °C Fan 60%
    Core 1710 Mem 4600 VDD MVDD MVDDCI
    3 04:00.0:Evga GTX 1660__6G 90.16.25.00.3D
    Hash 25.124094M Power 69W/70W Card 53°C Card °C Mem °C Fan 60%
    Core 1725 Mem 4600 VDD MVDD MVDDCI
    4 05:00.0:Msi RTX 3070__8G 94.04.3A.40.63
    Hash 25.316938M Power 109W/110W Card 43°C Card °C Mem °C Fan 60%
    Core 720 Mem 7900 VDD MVDD MVDDCI

HTTP shows incorrect hashrate on T-Rex.
GTX 1660 @ 60 MH/s.
RTX 3070 @ 25 MH/s.

Default SSH login/password?

Placed an order for the full kit. Looking forward to this!

Too easy? Not many people outside of enthusiast forums like this can even manage to build a gaming computer.

Quote from: philipma1957 on June 11, 2019, 03:54:12 AM

Added k21000

13th for this drawing I will do it weds night.

It will be second of seven drawings.

If you I need 2 things an address to send it to and of course proof you purchased one R606

The price is a free compac stick sidehacks first project.

I would like to participate in this drawing. I bought R606 from MinersSupply @ Amazon. Thank you!

https://www.ui.com/unifi-switching/unifi-switch-16-xg/

Scroll down for example of how to support 500+ clients.
In this example, an aggregation switch and 12 x 48-port managed switches.

Quote from: todxx on April 18, 2019, 10:10:21 PM

Team Red Miner v0.4.4 released

https://github.com/todxx/teamredminer/releases

Changes in v0.4.4

Added * mode specifically for modded timings on Vega GPUs. Use with e.g. --cn_config=15*15. This mode is now the default for Vegas.
Introduced slow start/ramp-up. Threads increase their workload slowly at start or restart after e.g. a network outage.
Added interleave adjustment logic. Readjusts the two threads per gpu over time to make sure they don't gravitate and get stuck.
Added support for forcing colors (--force_color) for windows redirected consoles (git bash, cygwin, node.js).
Added hotkey menu system (show stats, enable/disable gpu).

The new * mode opens up tweaking Vega timings for 2MB CN algos like CN-R!
We've seen a few extremely tuned V64 LCs able to hit over 2400h/s on CN-R with 1400/1100 clocks!
For those of you playing with timings, please share your results! We love seeing how far you guys can push these cards

Quick test...

Vega 64 timing via pbfarmer and others:
--RAS 28 --RCDRD 12 --RCDWR 5 --RC 44 --RP 12 --RRDS 3 --RRDL 3 --RFC 248 --REF 15600

Settings:
1401 mhz core
1107 mhz memory
870 mv voltage

TRM v0.4.4 results:
cnr (monero): ~2.400 kh/s
cnv8_rwz (graft): ~3.150 kh/s
cnv8_half (masari): ~4.600 kh/s
cnv8_dbl (x-cash): ~1.200 kh/s

Quote from: kerney666 on April 18, 2019, 04:42:02 PM

Hi!

For everyone testing modded mem timings for CN using TeamRedMiner:

TRM v0.4.4 is released on GitHub (https://github.com/todxx/teamredminer/releases).

The release contains a new *-mode specifically targeted towards Vega GPUs with modded mem timings and running normal CN variants (not Turtle). It’s the new default mode for Vegas.

The release also contains a new tuning guide with recipes for Vegas. Using it we can produce seriously sexy hashrates on all Vegas without increasing core clock above 1407 MHz (CN/r: 2440 h/s V64, 2250 h/s V56@64, 2130 h/s 56 Hynix).

The release will be in alpha state for a few hours before we post in our Bitcointalk topic, if anyone has the chance to take it for a spin, please do so and let us know your CN/r results.

Cheers, K

Quote from: misterkit on April 18, 2019, 09:07:13 PM

anyone have vega 56 with samsung memory timings yet? If I use Hynix for it kills the rig. I did not flash it to a 64....

--rp 12 --rc 37 --rrds 3 --rrdl 3 --rcdrd 12 --rcdwr 5 --ras 25

This is what I use. Works on 3 out of 4 of mine.

Quote from: Anwil on April 15, 2019, 12:09:36 PM

Rx Vega 56 hynix memory
1250/875mv 916/925mv
tartl cn 20.12 - 20.20 kh/s L24+24
CN/r 2160 1450/900
60 min no errors.
WinAMDTweak.exe --rcdrd 19 --rcdwr 4 --rc 35 --rp 13 --rrds 4 --rrdl 5 --rfc 148 --REF 15600
Cool!!!

Looks good so far. About 1 kh/s boost to turtle. Didn't work with all my hynix tho. Need to figure out what to change to get to work with weaker card.

Edit: after longer time most gpu crash or have hashrate drop

Quote from: Zorg33 on April 14, 2019, 10:10:42 AM

This is my lighter timing, hopefully stable:
--CL 19 --RAS 30 --RCDRD 12 --RCDWR 6 --RC 44 --RP 13 --RRDS 5 --RRDL 5 --RTP 4 --FAW 18 --CWL 6 --WTRS 4 --WTRL 9 --WR 15 --WRRD 1 --RDWR 18 --REF 17000 --RFC 248

please test it.

Working good so far. Using this on a dozen Vega 64s on turtle.

Thank you. This is very useful.

I checked default timing values and indeed it seems that RC = RAS + RP.
For example for Vega 64 defaults... RC(47) = RAS(33) + RP(14)... true

However I am not seeing the same for the other formula RAS = RCD + WR
For example for Vega 64 defaults... RAS(33) = RCDRD(16) + RCDWR(10)... nope.

Anyone have more information on this?

Quote from: Zorg33 on April 13, 2019, 04:26:15 PM

Quote from: dragonmike on April 13, 2019, 12:40:01 PM

Have you managed to find a good value for RAS to go with the low RCD?

OK... I'm revealing my secrets.

Here are the formulas straight from wikipedia, not hard to find.

If you check ras, rcd, wr, rp, rc you can clearly see the formulas were used.
These values are not hocus pocus. They are calculated according to specific rules.

So if you change ras, you should change rc too and vica-versa

I changed a few things in the timings from todxx/kerney to (hopefully) improve compatibility with more air cooled Vega 64s w/ Samsung:

--rp 12 --rc 45 --rrds 3 --rrdl 3 --rcdrd 12 --rcdwr 5

This should also work for bios flashed 56 -> 64 w/ Samsung. However, I noticed hashrate drop overnight. If anyone has ideas lmk.

For Vega 56s w/ Samsung and original bios:

--rp 12 --rc 37 --rrds 3 --rrdl 3 --rcdrd 12 --rcdwr 5 --ras 25

Also based off of recommended settings from todxx/kerney, changed "rc" to work with Vega 56 w/ Samsung and original bios. Does not work with Hynix.

Edit: added --ras 25 so that RC = RAS + RP

Quote from: todxx on April 11, 2019, 07:45:17 PM

Eliovp, great work on this tool. Here are some of my results:

OS: linux/Ubuntu 18.04
miner: teamredminer 0.4.3
card: Vega 64 air cooled (MSI air boost OC w/ samsung mem)
core clock: ~1150Mhz
mem clock: 1100Mhz
timings modified: --rp 10 --rc 44 --rfc 300 --rrd 3 --rcdrd 12 --rcdwr 5
hashrate w/ stock timings: ~19.5kh/s
hashrate w/ new timings: 21.36kh/s

Unfortunately I don't have power readings from this rig, so I'm not sure how much the power usage increased with the new timings.
I think the card can be pushed more, but I don't have the time to keep tuning at the moment.

I tried todxx timings in Windows teamredminer, turtle algo and working well so far on 6 out of 7 reference Vega 64s. One vega reports dead with the timing, and I believe it is the "rc" value causing it. Will look into these further. Thanks for the start!

I am impressed by how the dev team handled the ASIC/FPGA threat to the previous algo CNV8. The change to CN-waltz helped bring CPU/GPU miners back to the network. Having a unique algo also helps mitigate any potential problems from the hashrate rental services.

setting the environment variable worked for me too

I think the dead gpu problem is from the dot net core install which was required for the GGM grin miner.
https://github.com/mozkomor/GrinGoldMiner
https://dotnet.microsoft.com/download
I have a Vega rig that I previously used to mine Grin and it has problems with some miners like Team Red (but not lyra) and wildrig.

Thank you for adding AMD support.
I am trying to get a Vega 64 + Ubuntu 18 + ROCm to mine Grin29. Not working for me. Here is a log:

anwar@anwar-desktop:~/bminer-v15.1.0-2d30b6f$ uname -r
4.15.0-45-generic

anwar@anwar-desktop:~/bminer-v15.1.0-2d30b6f$ lspci | grep VGA
43:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] (rev c1)

anwar@anwar-desktop:~/bminer-v15.1.0-2d30b6f$ rocm-smi

======================== ROCm System Management Interface ========================
================================================================================================
GPU Temp AvgPwr SCLK MCLK PCLK Fan Perf PwrCap SCLK OD MCLK OD GPU%
0 69.0c 110.0W 1401Mhz 945Mhz 8.0GT/s, x16 37.65% manual 260.0W 0% 0% 0%
================================================================================================
======================== End of ROCm SMI Log ========================

anwar@anwar-desktop:~/bminer-v15.1.0-2d30b6f$ ./bminer -devices amd:0 -uri cuckaroo29://hammuh:rig10@us-east.stratum.grin-pool.org:3416
[FATA] [2019-03-01T13:54:29-05:00] No supported devices are available for the AMDCL platform
[WARN] [2019-03-01T13:54:29-05:00] Miner died! It will be restarted soon...

Any ideas?

Quote from: Lonnegan64 on February 15, 2019, 08:16:57 PM

Is it a quite weak machine? I had that problem a while ago with Monero and some older machines. The pool rised the difficulty higher and higher till the machine had no chance to return a hash in the given time. As a solution, I added the smallest allowed difficulty after the wallet address in the config file. With your pool it should be ".100000"

I'm using fixed difficulty, but I think the main problem is the linux JCE just goes to command line after IP ban instead of reconnecting. It should keep trying to reconnect to the pool.

I sometimes get booted from pool with latest linux version of JCE cpu miner. Am mining Turtlecoin to Steadyhash pool.

miner: jce_cn_cpu_miner.linux.033q.zip
os: ubuntu 16.04 & 18.04
log:
07:58:04 | Rejected by the pool in 54 ms.
07:58:04 | Connection failed: The pool kicked you out as Unauthenticated, its Difficulty 600023 is probably too high for your computing power. If the pool allows fixed Difficulty, fix it to a lower value.
07:58:04 | Connection interrupted, waiting 5s then retry, attempt #1
07:58:04 | Connection failed: Socket receive error: socket explicitly closed by the pool
07:58:04 | Connection interrupted, waiting 5s then retry, attempt #2
07:58:09 | Connecting to mining pool trtl.steadyhash.org:3853 ...
07:58:10 | Connecting to mining pool trtl.steadyhash.org:3853 ...
07:58:10 | Connected to pool. Now logging in...

Had 3 different ubuntu machines mining to same pool. When I woke up I saw it was at the ubuntu command line on all 3 machines instead of actually logging in.

Note that I got some windows machines on xmrig that don't seem to experience this issue.
Unsure if pool or jce is the cause.