Search content
Sort by
Showing 9 of 9 results by Desolutionary
Desolutionary - give more information about that version. You can PM me. I am using beta 2
Yeah no sorry. I respect the work Blissz has done and was using v1.12 on 3x D3 for a fair while but the re-connection after dev fee was a killer for me (I missed probably 20~ hours of mining over a week before I switched);so I'm not going to distribute a customer version of his firmware. Someone previously in the thread was saying they were going to release one so I was purely saying someone has already done it.
Hate to break it to a few people but there is already a no dev fee version of 1.12v floating around out there, and after testing it I can confirm it fixes the issues where the miner switches to dev fee then fails to connect properly back to the user pool.
https://image.ibb.co/fhstP6/Nofee.jpg
https://image.ibb.co/fhstP6/Nofee.jpg
Hey guys , I update my miners to v1.12 all looks good , but after 2 days I lost one of my miners on network, when I went on site i found that Red LED = OFF and Green LED = OFF .
Try to reboot/ shut down , perform hard button reset. Nothing still no luck.
Any idea what I can do? is there any fix ? or I need to send to Bitmain (late Nov batch)
Some of my other miners don't show all chains, and some are 54 ASIC only.
Funny enough that after changing from Prohashing to Nicehash 4 out of 10 cards come right ...
Any help will be welcome :-)
Will the new Beta FW help?
Try to reboot/ shut down , perform hard button reset. Nothing still no luck.
Any idea what I can do? is there any fix ? or I need to send to Bitmain (late Nov batch)
Some of my other miners don't show all chains, and some are 54 ASIC only.
Funny enough that after changing from Prohashing to Nicehash 4 out of 10 cards come right ...
Any help will be welcome :-)
Will the new Beta FW help?
You need to do a recovery with a micro SD card. Look at the first post down the very bottom. I had the same problem with both lights off and not showing on network.
Re: ⛰️⛰️⛰️[ANN] SAROS - X11 - AIRDROP - MASTERNODE - BOUNTY - SIGCOMP⛰️⛰️⛰️
pool bounty 1500 SAROS
ready
New Sarospay pool (x11)
https://lpool.name/pool/SAROS
-o stratum+tcp://x11.lpool.name:11977 -u -p c=SAROS
Bounty/Donate: SRPPipdgjA3vFSr2PKRV46TapSYauAP1dV (SAROS)
Node list: https://lpool.name/explorer/peers?id=1977
Explorer: https://lpool.name/explorer/SAROS
Pool is mixing up Saros and Swipp addresses (I had correct symbol in password string)
Would it be possible to point only one hash board at the dev pool instead of redirecting the whole miner? Every time dev fee drops connection to my pool then reconnects the hash rate doesn't register properly 
I suggest you start with one rig. Build it, tweak it, learn how it works, find the pain points, and then decide if you want to spend the rest.
This.
I started mining 4~ months ago and nearly went 20k deep on my first purchases but common sense prevailed. Decided to build one rig and learn the whole process end to end.
Rig cost $2300AUD with 6x RX570 4GB Gigabyte Gaming cards (28.8mh/s ETH or 818h/s XMR) but its paid for itself. Sitting at about $4500USD worth of coins at the moment. I'm planning to use that to build another 2 rigs as soon as I can nail down some cheap graphics cards.
Start small and get the hang of it. I refuse to pay full retail for gear and only buy stuff when on sale
I tried the latest proper release (not the beta) and after about an hour one of my cards would fail dramatically on normal settings. Flashed back to latest firmware from BM and problem has disappeared at what one would assume are the same settings.
Does the Blissz release include fixes from the latest BM D3 firmware?
Loved the options this gave me to optimise each board but I'd be restarting the unit every hour~ to enjoy the privilege. Definitely staying tuned for updates though!
Does the Blissz release include fixes from the latest BM D3 firmware?
Loved the options this gave me to optimise each board but I'd be restarting the unit every hour~ to enjoy the privilege. Definitely staying tuned for updates though!
I will post an update of the Beta firmware soon. It will help you if you have boards that go into xxxx very often. (it's based on the newest source / rewritten all code)
Sounds good I'll have a look.
If you have any more details / photos of a tear down on the D3 it would be great to see. Only had a D3 for 1.5 weeks~ but keen to see what I can do to improve it.
I tried the latest proper release (not the beta) and after about an hour one of my cards would fail dramatically on normal settings. Flashed back to latest firmware from BM and problem has disappeared at what one would assume are the same settings.
Does the Blissz release include fixes from the latest BM D3 firmware?
Loved the options this gave me to optimise each board but I'd be restarting the unit every hour~ to enjoy the privilege. Definitely staying tuned for updates though!
Does the Blissz release include fixes from the latest BM D3 firmware?
Loved the options this gave me to optimise each board but I'd be restarting the unit every hour~ to enjoy the privilege. Definitely staying tuned for updates though!
810H/s~ on Gigabyte RX570 4GB O/C with basic straps and default settings in v11.0
Up from 770H/s~ I was getting on v10.2 (same blockchain drivers used on both versions)
I'll see how it goes for a few hours then try tweak the -h setting (-h 896 at the moment).
Up from 770H/s~ I was getting on v10.2 (same blockchain drivers used on both versions)
I'll see how it goes for a few hours then try tweak the -h setting (-h 896 at the moment).