Forum Home
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Popular

    Can we get a re-definitive, foolproof guide up somewhere again?

    Mining
    3
    6
    1553
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • H
      HopeStillFlies Regular Member last edited by

      I’ve been following Cryptobadgers’ and it worked well in the past but uses an old version of cgminer and when I tried using a new one I ended up destroying a small continent and killing a billion people while trying to compile (zomg cflags=O2 not cflags=02).

      So here’s my dilemma. Following the cryptobadger guide:

      http://www.cryptobadger.com/2013/04/build-a-litecoin-mining-rig-linux/

      I ditched the CGMiner section and went to do sgminer because, you know, scrypt support:

      http://blog.shindasingh.com/2014/01/sgminer-4-0/

      Replace instances of 4.0.0 with 4.1.0.

      SGminer is on there! It is!

      It’s just not doing a damn thing and I have to manually launch. I tried altering the scripts listed in the main guide but it’s. just. not. working.

      I appreciate the help, thanks.

      EDIT: Went back and re-did

      export DISPLAY=:0
      export GPU_USE_SYNC_OBJECTS=1
      

      in sgminer directory. Maybe?

      just rename all instances of sgminer as cgminer

      …didn’t work.

      Went ahead and reinstalled 2.11.4 and rewrote the scripts. brb.

      EDIT2:

      haha, completely busted, no display on screens. OMG.

      I’m about ready to beg one of you running the same thing I am (could’ve swore there were a couple? Gigabyte board, sapphire 7950s) to zip up your disk image and shoot it over here.

      1 Reply Last reply Reply Quote 0
      • W
        wec Regular Member last edited by

        I have been running CGMiner 3.7.2 since 18 January 2014. CGMiner 3.7.2 was the last version with scrypt support. Try the below and follow the remaining cryptobadger instructions.

        wget http://ck.kolivas.org/apps/cgminer/3.7/cgminer-3.7.2.tar.bz2

        tar jxvf cgminer-3.7.2.tar.bz2

        1 Reply Last reply Reply Quote 0
        • H
          HopeStillFlies Regular Member last edited by

          [background=#ffffff]I have been running CGMiner 3.7.2 since 18 January 2014. CGMiner 3.7.2 was the last version with scrypt support. Try the below and follow the remaining [/background][background=#ffffff]cryptobadger instructions.[/size][/background]

          wget http://ck.kolivas.org/apps/cgminer/3.7/cgminer-3.7.2.tar.bz2
          tar jxvf cgminer-3.7.2.tar.bz2

          I’m telling you, the instructions are built around pre-compiling and since that doesn’t work I tried compiling that version; it doesn’t compile, at least as is. Something happened to it. Might additionally need AMD SDK or something but then we’re deviating too far from the original guide.

          1 Reply Last reply Reply Quote 0
          • U
            uncle_muddy administrators last edited by

            PM sent

            1 Reply Last reply Reply Quote 0
            • H
              HopeStillFlies Regular Member last edited by

              I’ve about had it.

              Ran Xubuntu, completely stock based on the CryptoBadger guide. Booted, got in, configured the old cgminer, because it should’ve worked, come on, it used to with this hardware there’s no reason not to. It loads up CGMiner and this immediately happens:

              Error -5: Enqueueing kernel onto command queue. (clEnqueu eNDRangeKernel)
              

              Shuts off my far side card. Middle card runs 110khs, card closest to the processor does 300k and then BAM. Starts overheating like the card that was once in it’s position.

              Eff that, I say. Plug in BAMT 1.4 because that’s what GUIMiner says to use for 7950s. Okay. Configing right. Change thread concurrency to correct value, up the intensity… mining! Feels slow, though, but what do I know? Sit there for 10 mins and it’s working fine. Take it back to the shop where I have it 24/7 and hook it up to their network and it reports it’s 192.168.1.112 on the network. That’s weird. It’s not showing in the router panel nor on my Angry IP scanner. I try forever to ssh into it, no dice. It’s not there. Everytime I spend 2 minutes rigged up to it with a screen it starts “mining” (BUT NOT REALLY.), spinning up the fans and maxing out the graphs before killing my cursor and keyboard input (crash?). Screw it again, I say, we’ll go back to Xubuntu and I’ll troubleshoot that goddamn enqueueing shit, try the version of CGMiner above. Rig up, get the desktop, says it’s connected at 192.168.1.138, nowhere on the network to get that. Impossible. Not being assigned an IP. Check to make sure it’s not running static. Frozen. Reboot. No display after bios screen. Repeat 5 times, having to wait about 2 minutes inbetween each attempt because I know it gets funky about showing the xubuntu boot screen when it hasn’t had all the power drained from the board.

              I’m tearing it down. I’m going to go pick up a BRAND SPANKING NEW flash drive JUST IN CASE that’s it, I’m going to a friend’s again tonight and I’ll try to piece by piece it back together again, one component at a time to determine but I seriously will have to consider that I’ve had some piece of the hardware go nutball on me.

              EDIT: NOPE. Verified, power cord from power supply into ATX 12V apparently caught fire. No idea what’s not working. Main ATX power cable not coming out of socket. Might’ve melted in there. Trying to remove now. May have to try to return the motherboard AND the Seasonic.

              EDIT2: It is not coming out of there. Anyone have suggestions on how to remove an ATX power connector from a socket it might’ve melted into?

              1 Reply Last reply Reply Quote 0
              • H
                HopeStillFlies Regular Member last edited by

                Why not start again, use xubuntu 13.10 x64, use the CGMiner in my link if you want or don’t just saves faffing about with compiling and the AMD SDK, Try with a single card.

                if you run through these and you get the command line reporting the temp of the card you are good to go.
                use a basic cgminer with just your user and password and the stratum of your pool

                • sudo apt-get install fglrx-updates fglrx-amdcccle-updates fglrx-updates-dev
                  sudo aticonfig --lsa
                  sudo aticonfig --adapter=all --initial
                  sudo reboot
                • After your computer reboots, you can verify that everything worked by typing:sudo aticonfig --adapter=all --odgt
                • If you see all of your GPUs listed, with “hardware monitoring enabled” next to each, you’re good to go.

                I did all that under a fresh 12.10 and it showed me “hardware monitoring enabled” and temperatures for each but it didn’t matter by the time I went back into cgminer because it did exactly what I said.

                It’s definitely the board and the power supply. I’ll be RMAing them tomorrow.

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post