Yeah I have it set to /1000+1 also. With 12GH/s I don't realize notice the higher share variance. Hopefully that gives some breathing room for smaller miners. I am not sure if that is a stat that can be tracked. % of hash power using higher share diff or maybe more useful is "diff per GH stat". i.e right now network is 749 diff for 348 = 2.15 diff/GH. Lets see if we can get that below 2!
If it can be tracked and charted we can encourage more people to help out.
Im down with this, what would your recomended settings be for 1.7GS/s. Also I wouldnt mind a detailed howto on the setup, I browsed ~5 pages backwards in this thread and cant seem to find one.
|
|
|
Well, after solving the IP addressing issue (assigned a static IP and all is well) ... I have another machine that seems to be having an issue. This machine seems to lock up with I have the --api-listen line in cgminer_opts. If I remove that, the machine is stable.
Anyone got any ideas why that might cause just this one machine to become unstable?
Your mining at gpumax ? I had some similiar like issues and had to abondin it for now myself.
|
|
|
I have not been here long but I have been a computer tech for over 15 years. I am currently mining with about 8gh/s and would like to keep expanding. My concerns with this situation might mean very little to some but i thinks most honest miners would feel the same way. This person is more than likely to have infected more computers then I can imagine. I have cleaned computers infected to the point they are almost useless. Yes I know that these infected probably don't effect the performance like a regular virus.Still the fact that innocent people are being subjected to theft and paying for this asshole to profit is a disgrace to BTC in my opinion. Do we really want BTC associated with this criminal activity?Stealing CPU and GPU cycles and having thousands of innocent people foot the bill is just plan wrong. I don't think BTC would ever be accepted on a larger scale with a big portion on the so called security being done by the world biggest stolen bot net. I do have a problem with this and would like to know how other true miners feel and not speculators.I don't know the laws in any place but USA but this is criminal here in the states.
+1
|
|
|
Unfortunatelly, BAMT not support wireless network I've had no problem in running bamt over a wireless network.
|
|
|
If it's a botnet Im fairly sure I will have confirmation of it within a few days, the "active researcher in a major company dealing in antiviral/security-software" I mentioned contacting a few pages back in this thread is actually prettymuch the "biggest star" in he's line of work: I got Mikko H. Hyppönen, the Chief Research Officer of F-Secure to look in to it. As soon as I have more I will be posting here.
|
|
|
I've been watching this thread for a while and today came up with a way to possibly confirm if this new miner indeed is a botnet, I e-mailed an active researcher in a major company dealing in antiviral/security-software, I have no way of knowing if the mail will ever be even read or responded to. However should I get a reply I will be reporting in.
I got a reply: (translated to english) " We have seen a few bitcoin botnets... I'll check if any match the discription." If it's a botnet then this could potentially mean trouble for it in long run
|
|
|
I've been watching this thread for a while and today came up with a way to possibly confirm if this new miner indeed is a botnet, I e-mailed an active researcher in a major company dealing in antiviral/security-software, I have no way of knowing if the mail will ever be even read or responded to. However should I get a reply I will be reporting in.
|
|
|
I had a monitor hooked up to a rig for some time because I was testing lowest energy consuming BIOS settings (no way to do that remotely I think at least not cheaply). Did get any problems after turning it off but I did once I unplugged it (bamt crashed, but it was more driver-related as far as I remember), I remember another user here having the same problem but the solution is to unplug the monitor after saving the BIOS settings (before booting bamt). But this is really not much of a problem Once you have everything set up, boot the rig without the monitor and see throught web gpumon or ssh if everything's correct. It happens for you with all gpus, regardless of the slot used? No, just Gpu0. Im going to try Lordcrappos advice once Im done swapping out the stock cooling on the next gpu im plugging in as it's a lowly 5770 and I figure having the lowest hashing card as gpu0 makes sense... guess that'll be tuesday because of snail-mail latency
|
|
|
This is propably more of a feature than a bug/problem, but im clueless as to where to start looking for a solution so here goes: (In before rtfm and read the thread, done multiple times) Im running a rig with 3 gpu's in it and to the gpu0 (5830) there is a monitor attached. Whenever I turn the monitor off my hashrate drops about 100Mhs. the motherboard is Asus P5Q-E, bamt is in it's most recent version (up to date 5h ago atleast). Any other info I should supply ?
And I do know I shouldnt even have a monitor attached to the rig, but as it is very much a work in progress I find it easyer this way.
I am unsure what happens when the monitor powers itself doen after X minutes, am currently waiting for this to happen.
Any and all hints would greatly be appreciated.
|
|
|
Jotakuinkin 1,5Ghz ja yksi lankku vielä matkalla, varmaankin semmonen 1,8Ghz kunhan sekin on kiinni. Sitten varmaankin pidän paussia raudan haalimisessa ja keskityn ratkaisemaan kesän mukana tulevat lämpö-ongelmat.
|
|
|
Im running 2 5870's: #1 474Mhs @ core 1030Mhz, 1,110v, mem 296Mhz, aggression 12 #2 456Mhs @ core 990Mhz, 1,10v, mem 294Mhz and aggression 12 With Phoenix, using phatk2 kernel. It took me just about forever to find these stable settings tho.
|
|
|
I'm based in Canada, however I know that the demand for these boards will be international. My goal is to mitigate some of the shipping cost by decreasing the profit margin, like I say my goal is only to make enough to be worthwhile and pass on the rest of the savings. As well, small form factor and an off-board power supply will also help with this, though I know this holds for most FPGA mining technologies.
Shipping is a minor cost, the real problem is the 23% in taxes (thats 23% of the order price including shilling) when ordering electronics from outside the Eu.
|
|
|
Where are you based ?
..this becomes extremeley relevant when getting hardware shipped in to Eu, Finland to be more exact, automaticly adds a price of +23% for the hardwareand shipping/handling.
|
|
|
This issue could be resolved somewhere in this thread but I sure as hell cant find it, I apologize if it's there:
I would like to setup gpumax and my rigs in a fashion where, they work at gpumax whenever public work is available and to work in P2pool when it is not. I know how to set them up in fashion where the rigs would try mining at gpumax at first and if it fails then swap to P2pool for X shares... after which try back at gpumax (rinse and repeat) I think (am not sure) that I however am not able to set up a worker at gpumax without specifying a "failover" pool. Is this possible ? If it isnt could you make it possible? (seems like a very small tweak). Is there something im not taking in to account ?
You can setup your own VPS with a p2pool node, and set that as your "private pool". Wow, thank you.. I guess the first issue in getting this to work is overcoming my dynamic ip address? [Edit] The second issue I see is the additional latecy coming from submitting work to gpumax and then back to my p2pool instance, would this hurt my shares badly in P2pool ?
|
|
|
This issue could be resolved somewhere in this thread but I sure as hell cant find it, I apologize if it's there:
I would like to setup gpumax and my rigs in a fashion where, they work at gpumax whenever public work is available and to work in P2pool when it is not. I know how to set them up in fashion where the rigs would try mining at gpumax at first and if it fails then swap to P2pool for X shares... after which try back at gpumax (rinse and repeat) I think (am not sure) that I however am not able to set up a worker at gpumax without specifying a "failover" pool. Is this possible ? If it isnt could you make it possible? (seems like a very small tweak). Is there something im not taking in to account ?
|
|
|
Card Manufacturer: AMD Card Model Number: HD 5870 Card OEM: ATI MHash per Second: 458MHS Core Clock: 1010MHZ Memory Clock: 294MHZ Average Operating Temperature: 62C Ambient Temperature: 22C Fan Speed: 50% Host OS: Bamt 0.5 Driver Version: 11.6 and SDK 2.4 Mining Program: Phoenix Command Line Flags/GUIminer Settings: BFI_INT VECTORS, FASTLOOP=false AGGRESSION=10 Watts Drawn While Mining: Unknown Other Information: kernel phatk2, core voltage 1.7 Record stable uptime at current settings 8d (and counting).
That can't be your GPU voltage, or it would be a smoky pile of smoke. Plus, see edited original post and above for new GPU MHz to benchmark at, so we can measure who's the best at tweaking their mining software. You are correct, theres a typo in there the correct core voltage is 1.17 I also should propably mention that the stock fans have been replaced with Arctic coolings Accelero Extreme.
|
|
|
|