Kano: API issue...
Setting intensity to 'D' doesn't seem to work. Can set other values fine 0, 1, 2 etc., but when D is sent it reverts to 0.
|
|
|
found a bug, if you add a miner that doesnt have --api-network and --api-listen (DOH!) its added "invisibly" - mine showed 4 hosts, and displayed 3. it slowed it down on refresh by LOTS. cant delete it in anubus as its not visible. I deleted it out of mysql though so its all good now.
I've fixed that. Just about done with my mods. Thing is, OCminer seems to have disappeared, so I'm not sure what to do with what I've done :/
|
|
|
Where are my $3 bitcoins I was promised???
|
|
|
10K @ 3.9 that's a hell of a wall.
|
|
|
No, keep selling guys, I want some cheap coins
|
|
|
Very clever The more people put $/B in, the more there is in reserve for the leverages folk to play with and less startfishes.
|
|
|
Not sure if you have a feature request list, but I'd put this:
-- Graphs -- ways to explore historical information? (like, how long has that card been throttling?) -- configurable notifications, and way to test them?
You'll have to find another app to do that. Anubis is a PHP script, it just runs once when the page loads. It can't do any monitoring / data logging etc. It just shows snap-shots of the current situation.
|
|
|
Got it working now It ain't pretty, but it does what it should. Still would like for a single clk setting to force that one clk, then sending a range value ('500-800' etc.) to re-enable the gpu-auto. Same for fan speed.
|
|
|
For the API: Make GPU Clock & Fan Speed accept a range - range = auto, as per... - single value = set just to that value Add target temp Job's a good'un Also add uptime.
|
|
|
I was wondering if the API would accept a GPU clock range.
|
|
|
Workin' on a lil' something... Doesn't change values right now, but won't take me too long (I think). P.S. I hate java script. Someone else can make it more pretty.
|
|
|
***Bug***
in function request, the sub-request socket port is hard-coded to 4028, rather than the value in the data base
$socket2 = getsock($host, 4028);
should be
$socket2 = getsock($host, $hostport);
|
|
|
I'm getting an unholy amount of discarded work and a fare amount of rejects... where should I start looking to fix/improve this?
|
|
|
Re: Cross Compiling... 1. Added #define _GNU_SOURCE to bitforce.c (was having problems with pthread_rwlock_t) - Not fixed 2. Had to comment out the functional affine_to_cpu, leaving just the empty stub in main.c because my libraries evidently don't support processor affinity (Ancient compiler again, I guess). Perhaps a test for cpu_set_t could be done or something. - Fixed
|
|
|
After much headbutting the screen, walls and various other hard objects, I finally got cgminer to cross compile and run under a mipsel processor (for my Asus RT-N16). My main problems was getting the cross-compiler to work; documentation on dd-wrt application development is very VERY sparse. in the end I discovered that optware ( http://www.nslu2-linux.org/wiki/Optware/Platforms) source package includes a self-compiling compiler (though it's ancient). ANYWAY. With the options: --disable-opencl --disable-adl --enable-bitforce, I had to edit a couple of things in the code: 1. Added #define _GNU_SOURCE to bitforce.c (was having problems with pthread_rwlock_t) 2. Had to comment out the functional affine_to_cpu, leaving just the empty stub in main.c because my libraries evidently don't support processor affinity (Ancient compiler again, I guess). Perhaps a test for cpu_set_t could be done or something. So, now cgminer returns with: 'All devices disabled, cannot mine!' Obviously I have no BFL units attached, but should it not scan serial ports or something? Is that the expected result? Also, I've found cgminer configure expects curses.h to be directly in /include/. The default location however, seems to /include/ncurses/.
|
|
|
Still waiting for the value to drop way more. Wanna buy me a whole load of them
|
|
|
Well, got cgminer to compile for the mips (broadcom) processor my ASUS RT-N16 has. Absolutely no idea if it does ANYTHING, but it compiled! All in need to do now is: Actually install DD-WRT on my router. Acquire a BFL unit. See if it does anything
|
|
|
Your DD-WRT'd USB router
|
|
|
Try not to be too jelly of my gargantuan 150MH/s...
|
|
|
|