Search content
Sort by
Showing 20 of 136 results by Brassguy
Quick Question.
Any one else having their S3 report only one working blade.
I've tried
-different power supply
-multiple reboots
-different pci-e plugs
-Currently power all 4 pci-e plugs with a 1600 watt supply
I've filed a ticket with Bitmain but nothing yet.
Anyone have any suggestions short of opening the box and checking connections.
Any one else having their S3 report only one working blade.
I've tried
-different power supply
-multiple reboots
-different pci-e plugs
-Currently power all 4 pci-e plugs with a 1600 watt supply
I've filed a ticket with Bitmain but nothing yet.
Anyone have any suggestions short of opening the box and checking connections.
Bitmain will tell you to open up the case and reseat the plugs from control board to hashing board. 99% of the time that will fix your problem.
well, I still havent got my units up and running whatsoever. Neither of them even connect to my router anymore. I`ve tried accessing them ,and all my webpage says is that its not available. I have a feeling the image of openwrt is currupted. I cant even ssh into them (although maybe i`m using the wrong settings). I assume its 192.168.1.99 root root and port 24?
First you need to find the ip they are on. Look at connected devices in router or jus nmap themThe router does not show them at all in attached devices.
Unplug them both and plug 1 in... Then log in and change the wan ip to something other than .99
Then plug in the 2nd one and leave it or change it as well. If you plug in 2 without changing the ip addresses you'll have an ip conflict and both will be inaccessible.
I got today my S3. One is working fine but the other one was not hashing at all because it had frequency set to 350 MHz.
I tried to reset settings but same so I manually edit the "asic-freq" file and set it to 218MHz. After that it start hashing around 440GH/S but it show a strange status page with double number of ASICs but half are "x".
Using ssh I notice that cgminer binary is different on the 2 systems. I tried copy the binary from the "good" one to the "bad" one but it does not hash at all.
The "bad" one also show fan speed of 0 for chain #2 but visually both fans are spinning at high speed.
I hope this is just an old firmware of something like that. I guess it will be fixed when Bitmain will release a firmware update for S3 and after that I'll get consistent Miner Status results on both units.
Power usage at the wall for the "good" is 337W and for the "bad" one is 323W.
I tried to reset settings but same so I manually edit the "asic-freq" file and set it to 218MHz. After that it start hashing around 440GH/S but it show a strange status page with double number of ASICs but half are "x".
Using ssh I notice that cgminer binary is different on the 2 systems. I tried copy the binary from the "good" one to the "bad" one but it does not hash at all.
The "bad" one also show fan speed of 0 for chain #2 but visually both fans are spinning at high speed.
I hope this is just an old firmware of something like that. I guess it will be fixed when Bitmain will release a firmware update for S3 and after that I'll get consistent Miner Status results on both units.
Power usage at the wall for the "good" is 337W and for the "bad" one is 323W.
That screenshot is promising for the possible upgrade path for people with s1/s2's... Either you have control board from an s1 running your s3 (possibly a test that was shipped by accident, and clocked at 350mhz) or a s3 control board with s1 firmware... Very interesting!
Steel is unfair... Our bronze weapons can't stand up to their weapons...
Gunpowder is unfair... It costs a lot to train my knights and any peasant can shoot them with 10 minutes of training...
The loom is unfair... It can make fabric faster than me.... And I don't have enough money to buy one
The oil industry is unfair... I'd have to go out in the hot sun and dig a well...
I'll just stop now...and say...
Life isn't fair... There is always someone better, faster, stronger, smarter, more capitalized, etc, etc than you... Work hard and be creative... And don't be afraid to fail, it's the only time you actually learn anything.
Or you can just tell your friends to grow up
Gunpowder is unfair... It costs a lot to train my knights and any peasant can shoot them with 10 minutes of training...
The loom is unfair... It can make fabric faster than me.... And I don't have enough money to buy one
The oil industry is unfair... I'd have to go out in the hot sun and dig a well...
I'll just stop now...and say...
Life isn't fair... There is always someone better, faster, stronger, smarter, more capitalized, etc, etc than you... Work hard and be creative... And don't be afraid to fail, it's the only time you actually learn anything.
Or you can just tell your friends to grow up
One more question i forgot:
Is the burned upper Mosfet the reason why i have a short circuit when i plug the PCB to 12 V? There are sometihing like 50 Ohm between the measure points , so its completly far away from infinite and definitly damaged, but is this the reason why the power source goes instantly down? Or maybe there are more burned parts ?
Is the burned upper Mosfet the reason why i have a short circuit when i plug the PCB to 12 V? There are sometihing like 50 Ohm between the measure points , so its completly far away from infinite and definitly damaged, but is this the reason why the power source goes instantly down? Or maybe there are more burned parts ?
Probably. Power supply is detecting a dead short and shutting down.
No change trying different psus... Bfgminer works the best for me but I can't get it to report speed via the API... Which is a necessity for me.
So jmordica cgminer it is... Until I can get dbartl cgminer...
So jmordica cgminer it is... Until I can get dbartl cgminer...
I had the exact same problem with cpuminer. I tried disabling fifo and using inactive restart setting to no avail... I'm currently using jmordica cgminer. It runs fine for 24-48 hours before crashing or a blade goes inactive. I restart every day or so. dbartl has a cgminer for pods/blades based on 4.3.5... but the compile instructions for windows seem out of date... packages for mingw, that you are instructed to download, don't exist. Maybe someone would be willing to compile it and post it here.
Like this
Sure do! sorry for the bad pic, I put it into service immediately
Hot melt glue, 10K pots, works great!
If you have the skills it's the best way to go.
Congrat's. Got pic's?
Congrat's. Got pic's?
Sure do! sorry for the bad pic, I put it into service immediately
Hot melt glue, 10K pots, works great!
Add this to your .bat file...
-S noauto -S gsd:all --set-device gridseed0:clock=838 --set-device gridseed1:clock=838
If you don't specify the frequency with BFG miner it will default to 600... which will give you about 4mh.
-S noauto -S gsd:all --set-device gridseed0:clock=838 --set-device gridseed1:clock=838
If you don't specify the frequency with BFG miner it will default to 600... which will give you about 4mh.
thanks philipma1957..
anyone take it to .75v?
anyone take it to .75v?
I'm going to try to test the lower bounds in a couple days.
Here's all of the frequency settings I nave been able to find. The list isn't complete and is lacking some timeout numbers. I think I have the info for 200mhz and 193mhz. I just have to dig around.
Code:
#option 'freq_value' '4f81' #205GHs (16x)
#option 'chip_freq' '400'
#option 'timeout' '35'
#option 'freq_value' '5f05' #202GHs (15.75x)
#option 'chip_freq' '393.75'
#option 'timeout' '36'
#option 'freq_value' '5e85' #198GHs (15.5x)
#option 'chip_freq' '387.5'
#option 'timeout' '37'
option 'freq_value' '5e05' #195GHs (15.25x)
option 'chip_freq' '381.25'
option 'timeout' '37'
#option 'freq_value' '4e81' #192GHs (15x)
#option 'chip_freq' '375'
#option 'timeout' '38'
#option 'freq_value' '6c09'
#option 'chip_freq' '370.83'
#option 'timeout' '??'
#option 'freq_value' '5d05' #188GHs (14.75x)
#option 'chip_freq' '368.75'
#option 'timeout' '38'
#option 'freq_value' '6b89' #188GHs (14.75x)
#option 'chip_freq' '366.67'
#option 'timeout' '38'??
#option 'freq_value' '5c85' #185GHs (14.5x)
#option 'chip_freq' '362.5'
#option 'timeout' '39'
#option 'freq_value' '5c05' #182GHs (14.25x)
#option 'chip_freq' '356.25'
#option 'timeout' '39'
#option 'freq_value' '4d81' #180GHs (14x) (default)
#option 'chip_freq' '350'
#option 'timeout' '40'
#option 'freq_value' '4c81' #168GHs
#option 'chip_freq' '325'
#option 'timeout' '45'??
#option 'freq_value' '0a81' #275
#option 'chip_freq' '275'
#option 'timeout' '51' or 45??
#option 'freq_value' '0a01' #267M
#option 'chip_freq' '267'
#option 'timeout' '53'
#option 'freq_value' '5102'
#option 'chip_freq' '218.75'
#option 'timeout' '58'??
#option 'freq_value' '5082'
#option 'chip_freq' '212.5'
#option 'timeout' '65'??
#option 'freq_value' '5002'
#option 'chip_freq' '206.25'
#option 'timeout' '68'??
#option 'freq_value' '0781'
#option 'chip_freq' '200'
#option 'timeout' '70'
#option 'freq_value' '4f02'
#option 'chip_freq' '193'
#option 'timeout' '70'
Re: And we have another Bitfinex Hookey THIEVING Short Squeeze!
I've been following Mat's post for a while now... and yes Mat can be a bit over the top and excitable, but I really appreciate his diligence in watching bitfinex. It's not only possible but entirely likely that bitfinex is doing what Mat believes they are doing. There is no reason for bitfinex not to do what they are doing... no one, until Mat, is looking over their shoulder. More importantly, there is almost zero downside risk for bitfinex to engage in these practices.
Re: [ANN] LeaseRig.net Rent & Hire Scrypt(Jane/Nfactor)/SHA3/SHA256/X11 HashPower!
It seems coinking consistently shows dead for any/all of my customers and for me on my pools page. My miners, using LRP, will just spew difficulty 1 shares which are all rejected of course. Ideas?
If you post here, and I talk to the coinguys, and our devs and their devs work together, we can figure this out within a month.
If you hop on the chat page, our devs, the coinking devs and other providers are usually online and we can figure it out in a few minutes.
What algorithm is the miner?
SHA256. 2 antminers using LRP
I believe it was the coinking multiport 9999?
Does anyone have a good working bfgminer.conf or CGminer.conf they wish to share for stock G-blades that'll work under Windows?
Thanks.
Thanks.
I am using just plain ".bat" file ...like this...?
cgminer.exe --scrypt -o stratum+tcp://usa.wemineltc.com:3336 -u YOURUSER -p YOURPASS --gridseed-options=baud=230400 --gridseed-options per_chip_stats=1, freq=838,chips=40 --hotplug 5
Hope it helps...
ZiG
Thanks but it didn't work. What's the equivalent of that in BFGminer's .bat file?
I tried something similar, (displayed later in this response), but it fails with "Unexpected extra command line argument".
This is my failing batch file with BFGminer in a Windows CMD prompt with the following in a .bat file:
bfgminer.exe -S noauto -S gridseed:all --gridseed-options=baud=115200,freq=838,chips=40,modules=1 -hotplug=5 --scrypt -o stratum+tcp://gridseed.wemineltc.com:3333 -u testworker.1 -p 123 --failover-only -o stratum+tcp://stratum.scryptguild.com:3333 -u testworker.1 -p 123.
BFGminer doesn't like the "--gridseed-options=baud=115200,freq=838,chips=40,modules=1 -hotplug=5" portion. It fails & terminates with with "Unexpected extra command line argument".
But this works in a .bat file:
bfgminer.exe -S noauto -S gridseed:all --scrypt -o stratum+tcp://gridseed.wemineltc.com:3333 -u testworker.1 -p 123 --failover-only -o stratum+tcp://stratum.scryptguild.com:3333 -u testworker.1 -p 123. But this won't hash above 8MH/s.
My problem is that they don't go above 3.5MH/s with this string even though they are supposed to hit a minimum of 5.2MH/s. Not seeing this. Getting a top hashing of 6-7MH/s with both G-blades.
Under my Raspberry Pi Model-B I get 11-12Mh/s, minimal HW errors but the hashing on there last about 30 minutes before it all comes to a crawling 720KH/s. Needless to say which is why I'm trying this under windows 7 SP1 now. I tried getting them to work with Multiminer v3.2.2 but the best I got was also between 5-6MH/s.
So now I'm trying to get this to work from the Window CMD prompt.
Once I can past the basic stuff working stable, then I want to get to mod the crap out of these G-blades.
So that's why I was asking if I could get someone to display either their BFGminer.conf file, preferably under v4.2.0 or their CGminer.
Here's my .bat file
If you don't specify frequencies bfg miner will default to 600... hence you're only getting ~2MH per blade.
Code:
bfgminer --scrypt -o pool URL -u Username -p password --api-listen -S noauto -S gsd:all --set-device gridseed0:clock=825 --set-device gridseed1:clock=825 --set-device gridseed2:clock=825 --set-device gridseed3:clock=825
my problem with bfg miner is I can't figure out how to specify frequency by serial number string like cpuminer Cpuminer fails for me after about an hour, even with fifo disabled in windows for those ports.
So I'm currently using jmordica's cgminer. Anytime I have to restart or change settings, I have to run Zadig to get the blades to be detected again. Sometimes have to reset blades over and over and run zadig 5 times to get all my blades running.
Re: [ANN] LeaseRig.net Rent & Hire Scrypt(Jane/Nfactor)/SHA3/SHA256/X11 HashPower!
It seems coinking consistently shows dead for any/all of my customers and for me on my pools page. My miners, using LRP, will just spew difficulty 1 shares which are all rejected of course. Ideas?
Looks like the contract was auto cancelled... It looks like coinking shows as a dead pool, the miner was just spewing rejected difficulty 1 shares...
Hopefully whatever LRP update is being released will fix this weirdness... until then I'm disabling my miners.
Hopefully whatever LRP update is being released will fix this weirdness... until then I'm disabling my miners.
My completely uneducated guess is to reformat and reinstall the hashra controla software... Just based on you changing a setting (causing a write to disk most likely) and a failure immediately after. Sounds like a failed/corrupted write to me.