|
What a genuine piece of shit he is. Sorry to hear that, man.
|
|
|
|
I use a daskeyboard. Gotta love that clickity-clack.  ^^ Perfect for mastering typing.  I have the regular, non masochist type. |
|
|
|
|
I keep seeing people state that heating with miners is bad for your health, but with no proof presented. Proof or BS.
|
|
|
|
It's a shame there were so many S4's out with problems.
Mine came in, I manually set difficulty, increased the frequency and consistently hash at 2.3TH no problem and no complaints.
Same here with my B2. My B1's PSU died, but it was replaced quickly. All in all I'm a fan of the S4s. CK's updated cgminer helped a lot too. |
|
|
|
Mine for good? With computers? Why not just do good? For others?
Better yet, do both. |
|
|
|
Bitmain has released a second firmware update for the S4: Antminer S4 - Firmware Flashed fine for me. Note it resets settings again. Seems to be a small hash rate boost. Can you find out if they included ck's cgminer fixes? I think I'll hold off flashing for now. Can anyone post a screen shot of the modified status page? |
|
|
|
|
Either scrypt or SHA256. PM me what you have. Local meetup preferred in Montreal area.
|
|
|
|
|
Got my replacement today, no duties to pay.
|
|
|
|
No bang on that unit yet. ck's custom cgminer version disables the 5 second and BS reports. |
|
|
|
Ok, so I tried both Debian and Mint. Still having the same issue. The problem lies with p2pool or my installation of it using the script I linked earlier. Does anyone have any ideas?
Ok, just spent the day installing ubuntu server over and over to see what happens with this and that. I tried a few options for correcting the problem: 1) Edit connections >>> delete whatever connection is listed, create / add new connection ... I tried that, but it had no effect at all, rebooted, still no effect. 2) In terminal >>> sudo service network-manager stop && sudo rm /var/lib/NetworkManager/NetworkManager.state && sudo service network-manager start >>> reboot ... no effect 3) Uninstall libglib2.0-0 >>> reinstall libglib2.0-0 >>> it broke my server >>> reinstalled 4) Uninstalling and then re-installing the network-manager - no effect. I then recalled that during the setup and install of ubuntu server, it asks which ethernet port (I have two onboard gblans) is primary, I chose eth0, but, it appears I was plugged into eth1 with the ethernet cable >>> I changed the cable to the other port et voila!! - all better instantly, connection manager recognized that I was plugged in and showed all appropriate info in the Connection Information window. So, no guarantee, but perhaps you have a similar situation with which port you're connecting the ethernet cable to when there's only one cable connected - worth checking out. Cheers. Wow, thanks for taking the time to try all that! The motherboard I'm using right now only has one NIC, so it's definitely the right port.  I have no problem establishing a connection to my LAN, the issue is keeping it working properly. It just sort of half dies on me, no matter what. Weird thing is when it happens, I can no longer ping my router (192.168.1.1) or the WWW (google.com for example) but I can still ping other rigs on my LAN and they can also ping the troubled Ubuntu rig (192.168.1.200). I set everything up on a VM using virtualbox, and for some reason it works flawlessly. I can't wrap my head around this. |
|
|
|
|
Ok, so I tried both Debian and Mint. Still having the same issue. The problem lies with p2pool or my installation of it using the script I linked earlier. Does anyone have any ideas?
|
|
|
|
Ubuntu sucks big hairy goat balls. Go for Debian - it's the OS Ubuntu used to be before they broke it.
At this point I'd be willing to try that. Would this install script be compatible with Debian? http://bitcoin.kyros.info/ |
|
|
|
I'm having a really strange problem with p2pool and I can't figure it out. Something related to it is killing my ethernet connection, seemingly when I refresh the statistics page randomly. I asked for help on ubuntu forums, since I think it was a ubuntu problem but now I strongly suspect the issue lies with p2pool. Here is what I posted on ubuntu forums with all the details: http://ubuntuforums.org/showthread.php?t=2249933Can a linux/p2pool guru give me a hand? I'm pulling my hair out over here and I've tried everything I can think of / find on google. I'm a linux noob. I was having the exact same thing happen to me a few months ago, on two different machines, about 2 weeks apart. The first time it happened was when I started running with two nics to two different neworks, everytime I restarted the computer both connections start, and they seem to fight over who's in control, (even though they're going out to different networks - probably my lack of knowledge and not setting things up correctly), but, if I turned off one and then restarted the other it would be fine and the connection would no longer drop out. For this machine I never solved it, but the band-aid solution of not using the 2nd connection was adequate. The second instance was a stand-alone nic in a basic 14.04 desktop environment, the connection kept dropping out, I did some updates and restarted the machine and it stopped happening. I don't know what the actual cure was, but double checking that you have all updates and restarting may provide relief. Unfortunately, this doesn't give you any hard data. But, you're not alone, I did a quick google and a lot of people have had similar happenings, one was solved by uninstalling amule, one was solved by removing the nic and installing a new compatible one. Cheers. Glad you got it worked out in the end. I can't believe that in 2014 an operating system still can't set up a NIC properly. So far I've tried a board with dual NICs, both realtek. Both had the same issue. Now I'm using a different motherboard with a single Intel NIC (82579V) and it's still happening. I've installed all available updates, updated the kernel to the latest available, and installed the latest Intel drivers from sourceforge. Rebooted countless times. I don;t know what to try next.. Whenever it messes up it can be fixed by simply clicking the network icon at the top right of the screen and clicking on "Wired connection 1". |
|
|
|
I'm having a really strange problem with p2pool and I can't figure it out. Something related to it is killing my ethernet connection, seemingly when I refresh the statistics page randomly. I asked for help on ubuntu forums, since I think it was a ubuntu problem but now I strongly suspect the issue lies with p2pool. Here is what I posted on ubuntu forums with all the details: http://ubuntuforums.org/showthread.php?t=2249933Can a linux/p2pool guru give me a hand? I'm pulling my hair out over here and I've tried everything I can think of / find on google. I'm a linux noob. |
|
|
|
What are ideal share difficulty and pseudo difficulty settings for an S4?
I don't own an S4, nor am I likely to, but I would hazard a guess at the standard 2048 that they work with? Maybe someone who's running one here can chime in? Peace Yeah, I figured 2048 would be ideal for the pseudo difficulty but I'm not sure what to set the other difficulty at? Sorry if this doesn't make sense, I just set up a p2pool node on Linux for the first time and I don't have much experience with p2pool in general. It seems to be working very well without specifying either, though. 2 units are showing a combined 4.2TH/s and about 3% DOA. I'm just wondering if I can tweak anything else to make things as efficient as possible. |
|
|
|
|
What are ideal share difficulty and pseudo difficulty settings for an S4?
|
|
|
|
Latest firmware, but using CK's most recent cgminer build.  |
|
|
|
Hi, yesterday I received an email about sending 3 new PSUs and information that other 7 will be shipped ASAP. I was really happy because I have had 3 miners without PSUs, but not for a long time. Nowadays I have 10 pcs S4 B1 and 10 pcs S4 B2 and a lot of S3+ miners. Today morning when I arrived to work I smelled burnt stink. Employees were scared, called me and ran around. WTF I said for myself. I hoped that the reason for all arround was not caused by miners but I was not right. I looked at the miners and two of them were down. Immediately I switched off all breakers dedicated for miners. And yes, one miner had PSU burned down. It was very easy to find which miner was bad  It was the fourth failed PSU. I checked all breakers and only one was switched off automatically. When the smell disappeared from the building (after 2 hours) I started with switching on the breakers one by one. After that I switched on PSUs on S4s. But another one from B1 and also one from B2 could not start. Also fans were stopped. I tried to reconnect the power but nothing helped. I have not understood what happened. All miners were running more than one week continuously. The PSUs do have really some problems. I hoped that PSUs in B2 were good, but....or today is only bad day for mining Today status is 5 failed PSUs from 10 pcs from B1 and one failed PSU from 10 pcs from B2. Can you confirm that the B2 miner that failed had a sticker on it? Early B2 units were shipped out with defective PSU also. You can see it by removing the top, no need to remove the PSU. (on my B2 anyways, maybe the sticker is elsewhere on others) Yes there is a sticker. On the other hand I have to say this B2 has a bit different inside in comparison with B1. How does it look different?? My B1 and B2 are identical inside. Your dead S2 PSU could just be bad luck, everything has a failure rate. If there are more reports of dead B2 PSUs I'll pick up 2 DPS2000 PSUs to power them and have peace of mine. |
|
|
|
|
Good stuff! Let us know how everything goes.
|
|
|
|
Hi, yesterday I received an email about sending 3 new PSUs and information that other 7 will be shipped ASAP. I was really happy because I have had 3 miners without PSUs, but not for a long time. Nowadays I have 10 pcs S4 B1 and 10 pcs S4 B2 and a lot of S3+ miners. Today morning when I arrived to work I smelled burnt stink. Employees were scared, called me and ran around. WTF I said for myself. I hoped that the reason for all arround was not caused by miners but I was not right. I looked at the miners and two of them were down. Immediately I switched off all breakers dedicated for miners. And yes, one miner had PSU burned down. It was very easy to find which miner was bad It was the fourth failed PSU. I checked all breakers and only one was switched off automatically. When the smell disappeared from the building (after 2 hours) I started with switching on the breakers one by one. After that I switched on PSUs on S4s. But another one from B1 and also one from B2 could not start. Also fans were stopped. I tried to reconnect the power but nothing helped. I have not understood what happened. All miners were running more than one week continuously. The PSUs do have really some problems. I hoped that PSUs in B2 were good, but....or today is only bad day for mining Today status is 5 failed PSUs from 10 pcs from B1 and one failed PSU from 10 pcs from B2. Can you confirm that the B2 miner that failed had a sticker on it? Early B2 units were shipped out with defective PSU also. You can see it by removing the top, no need to remove the PSU. (on my B2 anyways, maybe the sticker is elsewhere on others) |
|
|
|
|
Show Posts
