Wonderwall

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - V2-V3

Pages: [1] 2 3 ... 12
1
If you are experiencing a slow down of your hash rate as in your GPU mines at the proper Mhash/s and than it drops to khash/s after 10 minutes or so including anything that sounds like extremely slow hash rates in GUIMINER with CGMINER Miner you may need to set your flags for the GPU to the following Flags: -v -w 128 -f 60

2
Pool Support / Re: [Current Event] Bitclocker Service Outages
« on: April 15, 2013, 01:26:20 pm »
I'd be happy to throw my 500+ Mhash/s into the mix if it'll help the pool get back on its feet.

Thank you for making this suggestion. We need all the help we can get!

More hashing power will help restore balance to the pool but it would have to be from the kindness of your heart and considered a donation to the other miners. I will work with BB to explore the option of opening a Donation pool ie "donations.bitclockers.com:8332" this pool will give all earnings to the miners who are currently waiting for a payout.

3
Pool Support / Re: Bitclockers DDOS poll
« on: March 26, 2013, 08:30:41 pm »
Please visit the current events thread for more information and updates.

http://bitclockers.com/forums/index.php?topic=1803.0

4
Pool Support / Re: Bitcoins not appearing
« on: March 26, 2013, 08:30:18 pm »
Please visit the current events thread for more information and updates.

http://bitclockers.com/forums/index.php?topic=1803.0

5
Pool Support / Re: payout
« on: March 26, 2013, 08:29:52 pm »
Please visit the current events thread for more information and updates.

http://bitclockers.com/forums/index.php?topic=1803.0

6
Pool Support / Re: [Current Event] Bitclocker Service Outages
« on: March 26, 2013, 08:19:45 pm »
The pool paid out more bitcoins than it mined due to the pay per share method of mining, this happened until the 8% BTC fee reserve ran out. Once payout problems (shortages) happened some people took it upon themselves to DDOS the pool, at that point 95% of the miners left the pool. I have left my ~50GH/s solo mining and depositing blocks into the pool wallet for miners to withdraw. Currently there are less than ~120 outstanding bitcoins and it is assumed that my solo mining at average difficulty may be able to cover the difference in about 35 days.

7
Pool Support / Re: [Current Event] Bitclocker Service Outages
« on: February 25, 2013, 12:02:02 pm »
My apologies for any inconvenience this has caused, The site is continuing to have problems due to relentless attacks, We are using coudflare for DDOS protection but the most recent attacks have come from within the cloudflare network. This caused a great deal of problems for our systems. We hope to have pool 2 service restored shortly.

8
Pool Support / Re: Negitive bitcoin balance
« on: February 19, 2013, 08:04:40 pm »
Please follow this thread http://bitclockers.com/forums/index.php?topic=1803.0 for updates on Payout, Mining and website related issues.

9
Pool Support / Re: Error: Payout failed. Please try again later.
« on: February 19, 2013, 08:04:18 pm »
Please follow this thread http://bitclockers.com/forums/index.php?topic=1803.0 for updates on Payout, Mining and website related issues.

10
Pool Support / Re: BTC withdraw error on website
« on: February 19, 2013, 08:03:59 pm »
Please follow this thread http://bitclockers.com/forums/index.php?topic=1803.0 for updates on Payout, Mining and website related issues.

11
Pool Support / Re: Cannot withdraw BC
« on: February 19, 2013, 08:02:03 pm »
Please follow this thread http://bitclockers.com/forums/index.php?topic=1803.0 for updates on Payout, Mining and website related issues.

12
Pool Support / Re: Scam warning
« on: February 19, 2013, 08:01:51 pm »
Please follow this thread http://bitclockers.com/forums/index.php?topic=1803.0 for updates on Payout, Mining and website related issues.

13
Pool Support / [Current Event] Bitclocker Service Outages
« on: February 19, 2013, 07:58:02 pm »
Effective immediately, Bitclockers has closed registration of new miners.

http://btcserv.net/ and https://www.bitlc.net/ have also fallen due to PPS...

It appears MT.RED is experiencing similar problems as BitClockers, Read more here: https://bitcointalk.org/index.php?topic=15929.msg1793833#msg1793833

Im working with backburn to do everything to keep the pool running. If anyone has any ideas or can offer their services it would be greatly appreciated.

The pool paid out more bitcoins than it mined due to the pay per share method of mining, this happened until the 8% BTC fee reserve ran out. Once payout problems (shortages) happened some people took it upon themselves to DDOS the pool halting mining operations, taking down the website and forums, and clogging up the payout system., and causing about 95% of the miners to leave the pool. I have left my ~50GH/s solo mining and depositing blocks of 25BTC into the pool wallet for miners to withdraw. At this point withdraws are dependent on available BTC in the pool wallet. When a block reward is confirmed and available for withdraw the funds may only be available for a short time before they are withdrawn by other miners in the pool. because the payouts are dependent on when the pool mines its next block it is hard to say when the next payout will be available. The pool is about 1/2 way to another 25 BTC payout in terms of shares per average difficulty currently 3,287,583 of 7,670,000 for the next block of 25 BTC. At the current pool hash rate and difficulty there is an average of 10 days per block if luck is on our side.



news updates to the following issues will be made in this thread.

Current Tasks
  • Payout System Lock
      Admins will process payouts manually


    Completed
    • Website Access Restored
    • Mining Operations Disabled
    • API now Working
    • Forums Restored
    • Enhanced DDOS Protections through Cloud Flare and Prolexic

    14
    As of this week I have noticed a significant decrease in the time it takes to get funds from MtGox into my Dwolla account.

    Previously MtGox transfers to Dwolla averaged 3 days to complete. And Dwolla to Checking transfers averaged 11 days. The total estimated time for BTC to cash in hand was about 2 weeks.

    MtGox to Dwolla transfers now average 1 hour to complete.
    Dwolla to Checking transfers are averaging 5 calendar days. At current I am seeing BTC to cash in hand averaging 6 days.

    As a dedicated miner the reduced delay is a big advantage for my operations and provides much needed fiscal flexibility.

    What is your experience with transfers?

    15
    Pool Support / Re: Registration Fail
    « on: August 13, 2012, 05:47:53 pm »
    I recommend clearing your cookies and restarting your browser or PC, let us know if you continue to have this issue.

    socket errors may also be related to improper use or  abuse of CAPTCHA

    16
    General Discussion / Re: MH/s from GUIMiner or MH/s from Dashboard?
    « on: August 13, 2012, 05:43:50 pm »
    it is normal for your hash rate to vary up and down due to the sample rate of the pool, an average of your  hash rate over a longer period of time is best for a more accurate measurement.

    Your mining client will show you the instantaneous hash rate. Some clients will have the option to see the hash rate over time.

    17
    General Discussion / BAMT + AMD Radeon HD 7970
    « on: August 07, 2012, 05:00:48 pm »
    Anyone have luck with 7970's on BAMT 0.5c?


    Quote
    Open Root Terminal

    Code: [Select]
    sudo passwd root
    [enter your new pass]
    [enter your new pass again]
    su

    now do some fixer!

    Code: [Select]
    /opt/bamt/fixer

    hit enter a few times until you get your prompt back.

    Code: [Select]
    cd /opt/
    mkdir ADL
    cd ADL
    wget http://download2-developer.amd.com/amd/GPU/zip/ADL_SDK_3.0.zip
    unzip ADL_SDK_3.0.zip
    cd /opt/miners/
    wget http://ck.kolivas.org/apps/cgminer/cgminer-2.5.0.tar.bz2
    tar xsfv cgminer-2.5.0.tar.bz2
    mv cgminer cgminer.org
    mv cgminer-2.5.0 cgminer
    cp /opt/ADL/include/*.h /opt/miners/cgminer/ADL_SDK/
    cd cgminer
    CFLAGS="-O2 -Wall -march=native -I/opt/AMD-APP-SDK-v2.4-lnx32/include/" LDFLAGS="-L/opt/AMD-APP-SDK-v2.4-lnx32/lib/x86/" ./configure --enable-bitforce
    make install
    /usr/share/ati/fglrx-uninstall.sh --force
    sync
    coldreboot

    I don't know if the --enable-bitforce flag is required, seems sort of ridiculous but it works regardless so I would leave it.

    the URL to cgminer's files will likely change when a new version comes out.  you can just change the number in the URL and it will get that version.  at least 2.5.0 is the latest today.

    now we need our new driver, i haven't tried 12.6 yet, it might be faster.

    Code: [Select]
    cd /home/user/Desktop/
    wget http://www2.ati.com/drivers/linux/amd-driver-installer-12-4-x86.x86_64.run
    chmod 755 amd-driver-installer-12-4-x86.x86_64.run
    chmod +x amd-driver-installer-12-4-x86.x86_64.run
    ./amd-driver-installer-12-4-x86.x86_64.run
    sync
    coldreboot

    Code: [Select]
    nano /etc/bamt/bamt.conf

    set each card to be enabled in the bamt.conf (diabled: 0) so that mgpumon doesn't think the cards are disabled.  don't change clocks or anything though, the cgminer conf does that.

    also make sure each card has cgminer: 1 on it, like this:

    Code: [Select]
    gpu1:
    disabled: 0
    cgminer: 1

    and somewhere in the settings part you need a 'cgminer: 1', anywhere above the # GPU Configuration should work.  I doubt you would need the cgminer opts because bamt isn't loading cgminer, but for the sake of flying cows let's put something there.

    like this:

    Code: [Select]
    ...
    cgminer: 1
    cgminer_opts: --api-listen --auto-gpu --auto-fan -c /etc/bamt/cgminer.conf

    # GPU Configurtation

    and that having been said, I just found a typo in bamt.. configurtation?

    ok so ctrl+o to save, ctrl+x to exit nano.

    Code: [Select]
    apt-get remove network-manager*
    this is to remove the network-manager apps that cause the system to lose it's IP after a few hours, it's optional, but i recommend it.  scroll up a couple posts in this thread for instructions on the layout of this file you should edit:

    Code: [Select]
    nano /etc/network/interfaces

    and then restart the network.

    Code: [Select]
    /etc/init.d/networking restart

    now let's start cgminer to create a config file.  alternatively, instead of starting cgminer right now you could just create a cgminer.conf and paste in working settings.  if you do it that way, enter the aticonfig and the export lines before you start cgminer.

    Code: [Select]
    aticonfig --adapter=all --initial  -f
    export DISPLAY=:0
    export GPU_USE_SYNC_OBJECTS=1
    cd /opt/miners/cgminer
    ./cgminer

    cgminer will ask you for your URL, username, pass, etc for the first pool, set that up, then hit S for settings, then W to write config file, save it as /etc/bamt/cgminer.conf then hit Q to quit, then edit your conf from nano using:

    Code: [Select]
    nano /etc/bamt/cgminer.conf

    and you should have a configuration that's somewhat ready.  you could alternatively use cgminer itself to set all the settings you want, then save, it really doesn't make a difference at this point.

    now that nano is open, let's mod the config some.  since I already have this set up, here's a working config:

    Code: [Select]
    {
    "pools" : [
            {
                    "url" : "http://whateverpool.com:8332",
                    "user" : "yourusername",
                    "pass" : "yourpassword"
            }
    ]
    ,
    "intensity" : "14,14,14",
    "vectors" : "2,2,2",
    "worksize" : "64,64,64",
    "kernel" : "diablo,diablo,diablo",
    "gpu-engine" : "800-1155,800-1135,750-1000",
    "gpu-fan" : "70-85,70-85,70-95",
    "gpu-memclock" : "0,0,0",
    "gpu-memdiff" : "-150,-150,-150",
    "gpu-powertune" : "0,0,0",
    "gpu-vddc" : "0.000,0.000,0.000",
    "temp-cutoff" : "92,92,92",
    "temp-overheat" : "87,87,87",
    "temp-target" : "82,82,82",
    "api-port" : "4028",
    "expiry" : "120",
    "gpu-dyninterval" : "7",
    "gpu-platform" : "0",
    "gpu-threads" : "1",
    "log" : "5",
    "queue" : "1",
    "retry-pause" : "5",
    "scan-time" : "60",
    "temp-hysteresis" : "3",
    "shares" : "0",
    "kernel-path" : "/usr/local/bin"
    }

    that's for 3 cards, 2 of them are 7970 and the 3rd is a 7950.  seems to be working alright.

    ctrl+o to save, ctrl+x to exit nano.

    now technically speaking, you're done. 

    go start mining!

    Code: [Select]
    cd /opt/miners/cgminer
    ./cgminer --api-listen --auto-gpu --auto-fan -c /etc/bamt/cgminer.conf

    Now it's running, but if your session dies (if you close the terminal window) cgminer will stop.  So we need to put it in a screen so it can mine forevers!

    Code: [Select]
    screen
    ./cgminer --api-listen --auto-gpu --auto-fan -c /etc/bamt/cgminer.conf
    ctrl+a d

    Now cgminer is running in the screen.  Note that 'ctrl+a' are pressed together but release 'ctrl' when hitting 'd'.  To see your screens, enter:

    Code: [Select]
    screen -ls

    And to reattach a screen, now that you know the screen's number, you can reattach that screen with:

    Code: [Select]
    screen -r ####

    If you get an 'all devices disabled, cannot mine' error, try doing a sync and coldreboot, might take a couple tries.
    Credit: maplesyrupghost http://www.bitcointrading.com/forum/index.php?topic=416.msg1710#msg1710

    18
    Pool Support / Re: Support FAQ - Frequently Asked Questions
    « on: July 23, 2012, 01:17:27 pm »
    Hello,

    Thank you for bringing this to our attention.  the 50% stale ratio you observed was the result of The pool server incorrectly reporting stales on block # 728
     
    The stales reported are purely cosmetic as the server was reporting 1 stale for every share submitted, thus it did not effect payouts.

    This issue has now been resolved with today's code update.

    Thank you for your patience.

    19
    Pool Support / Re: 50% bad shares...
    « on: July 23, 2012, 01:17:14 pm »
    Hello,

    Thank you for bringing this to our attention.  the 50% stale ratio you observed was the result of The pool server incorrectly reporting stales on block # 728
     
    The stales reported are purely cosmetic and did not affect payouts. The server was counting valid shares as both valid and stale at the same time.

    This issue has now been resolved with today's code update. Stale counts should now be properly reported in your dashboards.

    Thank you for your patience.

    20
    General Discussion / Re: Why do you mine here?
    « on: May 30, 2012, 06:09:15 pm »
    100%digital,

    I have not seen you on IRC

    Please feel free to contact me if you wish to have a discussion.

    21
    General Discussion / Bitclockers Status Update
    « on: May 30, 2012, 06:08:00 pm »
    All anti hopper counter measures have now been disabled.
    With the successful implementation of a Pay Per Share rewards system they will no longer be needed.

    22
    General Discussion / Re: Pay Per Share Enabled
    « on: May 23, 2012, 05:18:03 pm »
    Optional proportional rewards system is in the works, more information will be released as development progresses.

    23
    Pool Support / Pay Per Share Enabled
    « on: May 19, 2012, 12:11:32 am »
    As of block #650 8% Pay per share is currently enabled.

    Miners will receive rewards for every share submitted to the pool.

    24
    General Discussion / Pay Per Share Enabled
    « on: May 19, 2012, 12:11:09 am »
    As of block #650 8% Pay per share is currently enabled.

    Miners will receive rewards for every share submitted to the pool.

    25
    General Discussion / Re: Wallet just got emptied
    « on: May 14, 2012, 02:13:17 pm »
    I am contacting backburn to see if he can get more detailed information on this.  to be safe. I recommend changing all your passwords for bitclockers and any related email addresses or other log on information.

    Pages: [1] 2 3 ... 12