Show Posts
|
Pages: [1] 2 3 »
|
--->> Problem Reporting Template for GGS Version 1.3.x
CPU (Cores): CPU with Internal GPU: Yes / No RAM (GB): MoBo: PSU: xxxx W Swap File (GB:
OS: W10 (x) AMD Driver Version: 18.x.x.x
Algo: Settings: Pool: (inkl. Port)
GPU 0: Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) -> Strap: GPU 1: Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) -> Strap: GPU 2: Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) -> Strap: GPU 3: Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) -> Strap: GPU 4: Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) -> Strap:
Problem:
Screenshots:
|
|
|
Zawawa: Just noted that when you stop the miner and it goes idle - the fans stay at the % they were running - even if the idle temp is in around 40c (normaly they are off there). So pse check if there is something stuck and does not get reset when the miner is stopped. / https://s7.postimg.cc/ze5mdcex7/Idle.png / I could reproduce that behavior a few times: 1. Start miner and let it run a while 2. Stop the miner with "Pause" - Fans "stuck" 3. Close the miner - "Fans stuck" Rig after 10 min or so: / https://s7.postimg.cc/4ze8m4kiz/Idle2.png / Devices 1-3 are still at 23%/43%/27% - the only Device that looks kinda normal is Device 0. Fan Settings for all Devices in GGS: Target 53c, Max: 65, Speed Min: 0, Max: 100 Restarting the miner does not solve the problem. What does stop the fans and gets them back to "normal" is i.e. starting Sapphire Twix. Start it, close it and they are back to normal - till ya start the miner and stop it again. Nothing changed on the rig, W10, Cards 470/480/580 as before and driver is still 18.3.4. - as 18.4.1 is a no-go so far.
|
|
|
[...] 1. Windows 10 and Adrenalin 18.4.1 detected my RX 570's as RX 580's. Apparently downgrading Adrenaline to 18.3.4 fixed this.
2.With Pete_X's suggestions, I was able to get my Samsungs around 1000 h/s and my Hynixes around 900 h/s but when I put them together GGS would throttle and I would run out of memory. Any thoughts on this zawawa or anyone?
1. 18.4.1. is just one thing -> bugged ... better stay away from it 2. That is normally i sign for a: wrong intensity or b: a gpu crashed - or both. You should see on the graph or at the speed if it wortks - or not. Second Thread starts with a dely - so don't get fooled by some cards - it can take up to 2 Min or so till the 2nd thread is running at full speed ... Graphs tell also a lot ... flatline, up'n down etc ... Best to test it out is to enable just one card. Voltages in the safe zone and intensity conservative at a lower start. Card by card and notes taken should lead to success .... Not to forget - the swap file - it can't be big enough. For my rigs i simply use a old HDD (1TB) and W10 got a 156GB swap file on that drive PS: Got my hands on an old 570 Pulse 8GB with Hynix MJR - right now running 2-122-8 1200-950-2100-950 @1025h/s
|
|
|
Wow thanks Pete_X really appreciate this. I got my Samsungs up around 1015 h/s at 110 intensity with your settings. Still working on the Hynix but I'm hopeful I can get them there too now. Please DM me your BTC address! Just pick a card to play with and raise Intensity one by one. Normaly the Samsungs should be around 1000h/s at +-105 (18.4.1 that is). 1050+- should be around 115. All that with 1200Core and 2050Mem. Raise these two only after you found a stable Intensity that the cards like ... You'll note that you are close to the right intensity if you get a flat line with no fluctuations after 1-2min ... Hynix ... we'll get there. Samsung 1st DM send - Thanks !
|
|
|
Here's another rig I have running Cryptonight-Heavy with GGS 1.3.7 alpha. This rig has 10x RX 570 8GB Nitro+ but somehow Windows 10 detects them as RX 580 after upgrading to Adrenaline 18.4.1 and my GGS settings: Those churning ~820 h/s are Samsung DDRs and the rest at ~750 h/s are Hynix I haven't toyed with the Memory Timings, kind of scared to fuck up my cards. Anyone can help me improve my hashrate please? Will be happy to give a tip (0.005 BTC) if someone can help me get them to ~900-1000+ with stability. So let's help and get these cards over 1000h/s on CN-Heavy : Depending on the driver you use: 18.3.4 2-124-8 and 1200-900-2150-900 Hynix (Voltages can be tweaked when max hash is found) 2-124-8 and 1200-900-2050-900 Samsung (Voltages can be tweaked when max hash is found) 18.4.1 2-118-8 and 1200-900-2150-900 Hynix (Voltages can be tweaked when max hash is found) 2-118-8 and 1200-900-2050-900 Samsung (Voltages can be tweaked when max hash is found) Start with Intensity around 110 and raise it step by step (best is only a single card to get the idea what they like). I let each card run 5min as a test - that sould give you an idea how the card likes the settings - as not all cards are eqaul. On 18.3.4 most cards top around 124, 18.4.1 differs a bit - there it is around 118+-. With 1225 on the cores you should reach/top 1100 on Samsung and get close to 1100 on Hynix. I know it's a bit tweaking needed - but the results pay back easy Check the straps you use on both of them, normaly everyone useds on Samsung the "1Click" one -> 1750 and up -> 777000000000000022CC1C00AD615C41C0590E152ECC8608006007000B031420FA8900A00300000 010122F3FBA354019 Hynix 1750 and up -> 999000000000000022339D00CEDD6B4470551414B80D960B0040C400750314204A8900A00200000 018123745B92B3A16 There is still some room for tweaks, as the rams probably can do more then what i wrote - but needs testing ... Hope i could help and you get these GPUs over 1000h/s soon 18.3.4 -> https://imgur.com/a/aKu7ZRjCheers
|
|
|
I would say everyone is entitled to her or his privacy. His advice was sound, too. I have some time to work on Hynix today. No worries.
Indeed, we help and share info - but we can't provide a 24/7 service Kinda as example we can use the "Strap" Discussion - there is at least one strap publicly available (even posted in this thread a few posts back) that allows Hynix MJR to go past 1000h/s kinda easy. The only thing someone has to do is to get the stuff together and add 1 to 1. Result would be stable if the starting point is stable and you go from there. Useless to start with timings if the core is not stable etc .... Overall it takes one thing some do not want to invest easy -> time, kinda lots of it ... @Zawawa: Surely you do not support modded bioses for a reason - as there is no chance to cover all do and don't do's which might take a count in the "does not work" ... As long as someone does know what he's doing the results with GGS are nice and stable - it just needs time ... not a really easy one click and top notch oc/strap whatever results. I had to learn also my ropes, started in the 90's at 17600 Newhope Street in Fountain Valley, Ca
|
|
|
@Zawawa: Take your time, as the toy we have an hand now is fun to play with. A bit tricky at times - but when handeled carefully the results are more than nice ! Congrats ! Testing right now with two nice pieces of sillicon (Quality 81.6% and 77.5%) and so far my own timings seem to work - just needs a tad more to stability as i get from time to time a ADL_Overdrive5_PowerControl_Set() failed for Device #1 (thats a 580 8G) ... but well .. Results so far are ok ... got both past 1050h/s on CN Heavy. https://imgur.com/a/3fdcQHFCan you share your timings and settings for reaching that excellent result for 580 8G hynix memory? Parts of it for sure - but the MJR Timings are not public - sry (there is far to much time and presents for my wife in them ). Zawawa does know what that means 01 - Find the sweetspot of your Sillicone (Corevoltage) 02 - Keep an eye on the temps - GDDR5 does not like heat (!). The sensors ya have on the cards are far away from the rams, take the core temp and add at least 10c on top of that (better 15c). 02 - Find an intensity that works best (takes time ...). For example between 105 and 115 the result varies +-100h/s when stable 03 - Look for s stable hashrate - no zigzags or sinus waves etc ... if that happens ... int is off 04 - Straps -> need a TON of time and varies slightly from card to card 05 - Most important -> Have fun ! https://imgur.com/a/sfysgC5
|
|
|
You should be able to reset the fan speed by either the "Restore Stock Settings" button or the "Reset All" button, then. As for power consumption, I forgot to mention that I will update the optimizer so that it would maximize profitability, taking into the cost of electricity into account.
@Zawawa: Take your time, as the toy we have an hand now is fun to play with. A bit tricky at times - but when handeled carefully the results are more than nice ! Congrats ! Testing right now with two nice pieces of sillicon (Quality 81.6% and 77.5%) and so far my own timings seem to work - just needs a tad more to stability as i get from time to time a ADL_Overdrive5_PowerControl_Set() failed for Device #1 (thats a 580 8G) ... but well .. Results so far are ok ... got both past 1050h/s on CN Heavy. https://imgur.com/a/3fdcQHF
|
|
|
I didn't recommend to update AMD driver to version 18.4.1. After update one of cards on rigs start to drop hashspeed to 0 after several seconds untill restart mining. Problem not only on my rig! Several peoples in neighbor themes wrotes about the same problem with 18.4.1 driver! Forced to rollback to 18.3.4 version.
Thats normally a sign that intensity needs some adjustment ... strange ... as my testrig does not complain after a slight tweak on intensity. We'll see ...
|
|
|
Dunno if this behave like a USB stick or if it requires programming skills to flash the program inside. Basically, yes - plug it in, connect the cables /reset and so on/ and install the software/driver and ya are good to go ... no programming skills needed at all - it's kinda plug'n play.
|
|
|
There ya go - it works with 2T now ... just a note for the next release: Please make the upper part of the GUI (specially the part aboput temps/speed etc.) also scaleable, as it is a bit tiny if you are not on VGA https://imgur.com/a/IqqYOtn... as it's too tiny to show you (as example) these nice jumps on the hashrate (taken with 1.3.4) -> https://imgur.com/a/XxtAnSO... or show you what happends if the con goes down and comes up again /1 T gets "lost" and does not come back again /-> https://imgur.com/a/D20Ktcg
|
|
|
Yay ! So far - so good. Just installed it on my testrig and it acts up a bit. CN Heavy: Miner restarts as soon as a 2nd 8GB card wants to start with two threads. Nothing in the logs - just a miner restart. Will dig a bit deeper l8r on when i have a bit more time. More details when i had time to fidel a bit with the miner Crap. I have the same issue. 2 R9 390x. First one starts up, but when second one starts when goes from 1.2GB memory to 2.4, application crashes Yopp, so far i tested : 480 2T and 480 2T * Crash as soon as the 2nd card goes to the 2nd thread 480 2T and 580 2T * Crash as soon as the 2nd card goes to the 2nd thread 480 2T and 480 1T * Works 480 2T and 580 1T * Works 480 2T and 480 1T and 470 1T * Works and so on ... No error msg, nothing in the logs - just a plain miner restart
|
|
|
Gateless Gate Sharp 1.3.6 alpha https://github.com/zawawawa/GatelessGateSharp/releases/tag/v1.3.6-alpha* Redesigned user interface for remote control with smaller screens. * Significantly improved responsiveness of user interface. * Added functionality to manage WDG273-based USB watchdog. (CH340 driver required.) * Improved default device settings for Ethash and RX 480 with Samsung GDDR5 (30Mh/s). * Added functionality to "capture" memory timings in the real-time. * Improved overclocking handling. * Added functionality to monitor ECC errors for Vega and other compatible devices. * Improved geolocation detection. * Switched the file format of user settings to JSON. Phew! Yay ! So far - so good. Just installed it on my testrig and it acts up a bit. CN Heavy: Miner restarts as soon as a 2nd 8GB card wants to start with two threads. Nothing in the logs - just a miner restart. Will dig a bit deeper l8r on when i have a bit more time. More details when i had time to fidel a bit with the miner
|
|
|
Will memory timing mod work on old drivers like 15.12 or 16.9.2?
Please note that the current focus of the project is on AMD and this program has been tested mostly against AMD Radeon Software Adrenalin Edition 18.1.1. Other drivers may or may not work. Prerequisites The minimum requirements for the miner are as follows:
Graphics card(s) with the AMD GCN architecture and/or the NVIDIA Maxwell and Pascal architectures. 64-bit Windows operating system. AMD Radeon Software Adrenalin Edition 18.1.1 or later for AMD cards.
|
|
|
Hello Zawawa! GG Sharp 1.3.2 prealpha worked fine, but 1.3.5 show exception. Whats wrong? Why not supply a bit more information? Hard for Zawawa to help with not much Info ---> Problem Reporting Template for GGS Version 1.3.x
CPU (Cores): CPU with Internal GPU: Yes / No RAM (GB): MoBo: PSU: xxxx W Swap File (GB:
OS: W10 (x) AMD Driver Version: 18.3.x.x
Algo: Settings: Pool: (inkl. Port)
GPU 0: Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) -> Strap: GPU 1: Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) -> Strap: GPU 2: Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) -> Strap: GPU 3: Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) -> Strap: GPU 4: Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) -> Strap:
Problem:
Screenshots:
|
|
|
"find an error" Could I see a screen shot? Which video cards do you have on the PC? Do you have enough physical memory?
Why not use some template to get some Info together ? -> Problem Reporting Template for GGS Version 1.3.x
CPU (Cores): CPU with Internal GPP: Yes / No RAM (GB): MoBo: PSU: xxxx W Swap File (GB:
OS: W10 (x) AMD Driver Version: 18.3.x.x
Algo: Settings: Pool: (inkl. Port)
GPU 0: Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) -> Strap: GPU 1: Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) -> Strap: GPU 2: Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) -> Strap: GPU 3: Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) -> Strap: GPU 4: Bios Version: Original ( ) - Modded ( ): PBE 1-Click ( ) Other ( ) -> Strap:
Problem:
Screenshots:
|
|
|
Do we need the latest driver or is the blockchain one okay with your soft? Thanks
--> I just need to write the following in the bold print somewhere...
1. GGS does not support Blockchain drivers. 2. GGS does not support modded BIOS'es.
I just don't have time to support discontinued drivers or hardware that is way out of specifications as GGS itself does some pretty wild stuff under the hood. Hope you understand.
- It works with the "old" Blockchain Drivers, but ... better to go with 18.3.4 - It works with modded Bioses, but ... don't complain if not
|
|
|
And don't forget to remove 10-12% CPU usage when GGS OC option activated.
That extra usage is for hardware acceleration. Can't understand. Simle overclock settings (clocks and voltages) needs nearly 1 core of 8 core CPU? Phymem and Hardware acceleration options disabled... F.e. Claymore miner sets clocks, voltages, PL and fans with using CPU only at start of miner. During mining thats no need to use CPU power for that... You are comparing Apples and Oranges ... both miners use a diff approach to reach the goal. Just a hint ... Clay has no GUI at all, GGS has a GUI and a lot of stuff is going on without notice for you ... Just my 5 cents on that ...
|
|
|
|