Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 86. (Read 5805508 times)

Any luck getting the Hashfast voltage tweak working for the Habanero board? I know you had given some feedback to JakeTri about it and I know you are traveling. Just curious. Thanks!

You are confused and in the wrong place and wrong time. Computers used to mine bitcoin on their own in the distant past, but no more. Computers do not mine bitcoin with cgminer. Cgminer is used to run specialised hardware that you plug into your computer.

The U devices are actually pretty decent and should run fine, your problem is new to me but downgrading to 4.3.5 will get you one that works fine on them.
As for future devices, dunno... the future world of amateur mining doesn't look rosy.

I intend to try this, but on a VPS,
if need great specs?
please give me an explanation, I am still confused to start

Hi
Why I obtain a lot of ZOMBIES each day? with terraminer
Energy?. How can I fix that?. What should I buy to solve that?
Thanks

4.4.1 and so far its only been 1 device so far and it won't mine in this state. It seemed to start happening after I pulled a potentialy bad u2 from my hub ( really low hashing and hot to the touch while good ones stay cool and average 22 shares per second if I look at it right)

I thought it was released to try to tweak the U devices so they wouldn't dissappear.  I'm leaning toward a rock miner next month so I hope that gives you less grief.

Also if the U devices are potential cgminer grief, do you have any advertising page to whats been good to you so we can keep getting support from you. Drillbits been good but I won't see a potential new product from then till the fall my luck.

I don`t use cgwatcher as yet, but i`ll give it a go.  Thanks

LIN is a rockminer R-Box. Don't ask me what LIN stands for, that's what the sample rockminer driver decided to call it and I just left it that way. There was an issue with 4.4.0 which would falsely label U* devices as rockminers (because all these goddamn manufacturers don't use any kind of identifiers and use the woefully outdated 15 year old USB1.1 chip that costs them a few cents instead of something newer). The main reason I released 4.4.1 was to try and not wrongly identify U1/2s as rockminers. What cgminer version is it that you're running?

Anyone know what a lin device is. one of my antminer u2s is being picked up as one. I only know since when I unplug it the lin dissapears. Probably another device I have to chuck.

Thanks and sorry for the multiple posts. I have no idea how far ckOlivias will check back and hopefully this will keep our thoughts clean.

Are you using cgwatcher with this since that opens a temporary config file and unless you also disabled it theres a beta feature to keep pools from being changed so maybe either of those are the issue.

Turn off cgwatcher, run cgminer and add pool and save. Restart cgwatcher.

Kano before you build could you check something for the antminer s1 for me. I was recommended to try multiminer so I didn't have to change my api but the current kano version or whatever's been tweaked elsewhere leaves me with an access denied message in the program. I'm not sure exactly what it uses to communicate with the antminer but I'm hoping its a easy fix to make.

Thanks

I'm still having issues with cg since 4.4.0. 

TRied to add or remove pools goes ok untill you click save .conf.

Cg then crashes (windows tries to solve issue) close it down, and  when restarts, the .conf is empty.

The workaround is to manually edit the .conf, but still a little frustrating.

Thanks

Yes, that is the Makefile I am using (or will be for the S1).

Firstly though I am trying to get this to work using the Avalon instructions as you suggested.  I appear to have everything I need for the build but am just having problems with LIBCURL.

Can I please ask what set up you use to build this on?

Also, can I ask which of the 2 .config files you use?

The Makefile is in the feed.
Did you not look in there when I pointed it out?
https://bitcointalksearch.org/topic/m.7462671

I'll do a new S1 tonight ... and put it up for testing (and run it myself as well of course)

The problem is that I am using an already written Makefile so don't really want to mess around with it.  I have yet to find out how to pass any switches to the build, if it is actually possible, when cross compiling.

you may need to pass the build switch that excludes drivers other than Bitmain. One of them would have the dependency for curl.

Ok, back to trying to build cgminer for the Antminer S1.

Thanks to some pointers from kano and norgan and in between watching way too much football I have made some progress but am still a little stuck.

I figured the best bet would be to try to get the Avalon instructions to work and once successful there adapt it for the S1 but that isn't being too successful!

I am basing this on the instructions here : https://forum.openwrt.org/viewtopic.php?id=45693 changing cp package/cgminer/data/config .config to copy config.avalon.703n to .config (I have tried a couple of the others as well)

The error I am getting is "checking for LIBCURL... no" and the build stops with an error.  Having searched and searched the internet, not helped by the openwrt wiki being down, I have not got around that error.  However, in the cgminer readme it mentions curl is optional so does the Avalon (and susequently the Antminer S1) need curl, and if not how would I disable it.  If it does, how the heck do I get the make to find it?  I believe libcurl needs to be in the openwrt buildroot rather than associated with Ubuntu - but please correct me if this is wrong.  This error probably isn't really anything to do with cgminer but I figured someone on here may know the solution.

Also, when building I get the OpenWrt Configuration screen come up.  Does anything need changing in there?  Again I could find no help searching the internet.

Once I crack this, it should be straight forward to get this to work for the S1 as I already have the Makefile for that although the config files with it are still named after the Avalon but the actual code appears to have been changed for the S1 but there are a couple of choices still.

So, any further pointers would be greatly appreciated.

I'm not sure when I will be online today as our electricity meter is being changed so I can move to a cheaper supplier!

No, while I made an initial driver for cgminer based on the knc driver itself with some minor changes from me and included it in cgminer, the knc driver maintainers have since deviated from the original code I included and made no attempt to push their code back to mainline cgminer, so what is in mainline cgminer is now an ageing version of their earlier driver and not whatever is now part of their firmware.

Are there on the latest version some fixes for the KNCMINER Jupiter or neptune?

Thanks, I'll search along those line.