Topic: GekkoScience Terminus R808 Miner Official Support Thread - page 13. (Read 16917 times)

Try to add slub_debug=FP to /boot/cmdline.txt and reboot

.

No, I originally tried on an old notepad type laptop running xp, but could only get one miner at a time running. This is two miners on a raspberry pi. I have 2 left and each has run longer than 24 hours solo.

I ditched the USB splitter and haven't had any more of the failure to initialize errors after 12 hours or so,  but I'm still getting the error that disables and resets the device.

My pi is also randomly shutting down every 36 hours or so, I'm on the pi forums trying to figure that one out.

You using latest version of cgminer listed on front page?  Also you using Windows 10?  How many terminus you running.  I ran each of mine at standard settings individually for 24 hours to be sure I achieved the results sidehack had posted.

New update if this tells anyone anything - I am still getting the failures with constant resets. Last night I had these running for 12 hours or so and it had cycled through nearly 180 of these errors:

...
[2018-03-10 07:59:21.318] Accepted 02102f35 Diff 124/48 GSE 179
 [2018-03-10 07:59:24.474] Accepted 04410e18 Diff 60/48 GSE 179
 [2018-03-10 07:59:25.540] Accepted 7f923adf Diff 514/48 GSE 179
 [2018-03-10 07:59:26.017] GSE 179 failure, disabling!
 [2018-03-10 07:59:26.017] GSE 179: setting frequency to 100.00MHz
 [2018-03-10 07:59:29.626] GSE 180: Terminus BM1384 Bitcoin Miner (10030015)
 [2018-03-10 07:59:29.836] Hotplug: GekkoScience added GSE 180
 [2018-03-10 07:59:29.942] GSE 180: found 8 chip(s)
 [2018-03-10 07:59:30.058] GSE 180: setting frequency to 100.00MHz
 [2018-03-10 07:59:30.072] GSE 180: open cores @ 100.00MHz
 [2018-03-10 07:59:31.751] GSE 180: start work @ 100.00MHz
 [2018-03-10 07:59:46.753] GSE 180: setting frequency to 125.00MHz
 [2018-03-10 07:59:48.045] Accepted 01074342 Diff 249/48 GSE 180

Then a new one popped up:

[2018-03-10 08:02:58.292] Accepted 89f1fd11 Diff 475/48 GSE 180
 [2018-03-10 08:02:59.924] GSE 180 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2018-03-10 08:03:32.547] GSE 180 attempted reset got err:(-5) LIBUSB_ERROR_NOT_FOUND
 [2018-03-10 08:03:32.548] GSE 180: usb failure (-5)
 [2018-03-10 08:03:32.549] GSE 180 failure, disabling!
 [2018-03-10 08:03:32.549] GSE 180: setting frequency to 100.00MHz
 [2018-03-10 08:03:35.057] GekkoScience detect (1:7) failed to initialise (incorrect device?), resetting
 [2018-03-10 08:03:35.057] failed usb_init
 [2018-03-10 08:03:40.493] GekkoScience detect (1:7) failed to initialise (incorrect device?), resetting
 [2018-03-10 08:03:40.494] failed usb_init
 [2018-03-10 08:03:45.877] GekkoScience detect (1:7) failed to initialise (incorrect device?), resetting
 [2018-03-10 08:03:45.878] failed usb_init
 [2018-03-10 08:03:51.267] GekkoScience detect (1:7) failed to initialise (incorrect device?), resetting
 [2018-03-10 08:03:51.267] failed usb_init
 [2018-03-10 08:03:56.601] GekkoScience detect (1:5) failed to initialise (incorrect device?), resetting
 [2018-03-10 08:03:56.601] failed usb_init
 [2018-03-10 08:03:56.652] GekkoScience detect (1:7) failed to initialise

And so on for hours on end. I found it when I woke up today and restarted everything, but one of my miners is getting that failure error every few minutes or so. It successfully starts again at 100mHz and eventually goes up (I have them set to max 150 right now to make sure overwork isn't the cause of this) until it resets again. Cycling through this process means my overall hash rate is about 10-15 less than it should be when averaged out... plus the unsettling feeling that one of these is on the verge of breaking...

Hi folks.

I'm going to try and get four of these running on a pi. Not too optimistic as even the man, the myth, the legend himself said he had issues with it... But hey why not?

I'll going to try a USB splitter to get four connected. Anytime have advice on a model I should try?

If it's a fool's errand or ends up costing more than a new pi, I'll just go with that. But I'd appreciate any advice you can throw my way.

Anyone been a to run these off a pi zero?

That's not very many errors. If you think of it as a percentage of accepted shares (all of which are in the neighborhood of 5.3 million) and also as accumulation over 3 full days, it's almost trivial.

Been running at 200Mhz for 3 days.  Average has been steady right around the reported rate for 200Mhz.  My question is the HW errors normal?  Core voltage is set at the 'factory setting'  Would adjusting that decrease or increase errors?

So it turns out that I shouldn't have spoken so soon. I only managed to get it working for a short time. Now cgminer is failing to detect any of the chips on the Terminus. My log file reads as follows:

[2018-03-07 14:20:34.593] Started cgminer 4.10.0
 [2018-03-07 14:20:34.858] GSE 0: Terminus BM1384 Bitcoin Miner (10030000)
 [2018-03-07 14:20:35.064] GSE 0: found 0 chip(s)
 [2018-03-07 14:20:35.064] Probing for an alive pool
 [2018-03-07 14:20:35.064] GSE 0 failure, disabling!
 [2018-03-07 14:20:35.065] GSE 0: setting frequency to 100.00MHz
 [2018-03-07 14:20:35.299] Pool 0 difficulty changed to 4000
 [2018-03-07 14:20:35.323] Pool 0 message: Authorised, welcome to solo.ckpool.org
 [2018-03-07 14:20:36.066] Network diff set to 3.29T
 [2018-03-07 14:20:41.322] GSE 1: Terminus BM1384 Bitcoin Miner (10030000)
 [2018-03-07 14:20:41.527] GSE 1: found 0 chip(s)
 [2018-03-07 14:20:41.527] Hotplug: GekkoScience added GSE 1
 [2018-03-07 14:20:41.527] GSE 1 failure, disabling!
 [2018-03-07 14:20:41.530] GSE 1: setting frequency to 100.00MHz
And so on and so on...

I'm using the most recently posted build of cgminer, and I have tried reinstalling and troubleshooting the Zadig drivers. Any suggestions?

Ok, then I presume it's SHA-256 only? I don't want to assume, that's all as sometimes miner hardware can do multi algo,

Thanks for replying..

Is it a good enough hint that this is posted in the Bitcoin section?

Apologies in advance for asking this as I have difficulty finding the answer..

What algo can it handle? Scrypt or SHA-256? The expected 66 GH/s is for what algo?

Many thanks in advance

I just got my first Pi. Haven't been able to pull it off with these ... yet.

I have three open USB ports on the Pi - USB wireless keyboard/mouse, so I'll shoot for that, someday.

Yup! That was it!

I got both units running at a breakneck 84 ghash on a single Raspberry pi.

Thank you so much for your help everyone in getting a dunce up and running.

When my 2 new units arrive, I could always just set up a second pi to get them running.

I eagerly await your next project!

A couple of final questions:

1) Sidehack himself said he couldn't get more than two running to a pi. Given that there's only 4 usb drives and you need a keyboard and mouse I'm not even sure how you could pull that off without a USB splitter. If anyone figures out how to run 4 off a single pi, let me know.

2) Maintenance on these guys: is there any need to unplug them occasionally? Or does running 24/7 until they break not matter?

The error, and to a certain extent its solution, is here:


I bet if you look into cgminer's included README file for that error you'll find some advice.

Or you could check the FAQ section, which includes this little tidbit:

See? I'm enough of a computer illiterate I didn't even know that.

I followed the instructions here and I have been able to get CGMiner to run, but it isn't recognizing my miner. Any advice?

 [2018-03-06 19:09:37.276] Started cgminer 4.10.0
 [2018-03-06 19:09:37.494] USB init, open device failed, err -3, you don't have privilege to access - BSC device 1:8
 [2018-03-06 19:09:37.494] See README file included for help
 [2018-03-06 19:09:37.494] GekkoScience detect (1: failed to initialise (incorrect device?), resetting
 [2018-03-06 19:09:37.494] failed usb_init
 [2018-03-06 19:09:37.494] No devices detected!
 [2018-03-06 19:09:37.494] Waiting for USB hotplug devices or press q to quit
 [2018-03-06 19:09:37.494] Probing for an alive pool
 [2018-03-06 19:09:37.912] Pool 0 difficulty changed to 4000
 [2018-03-06 19:09:38.260] Pool 0 message: Authorised, welcome to ckpool.org 15rN7atb8w7avfQH7PUjh6zEmForXvDr2x!
 [2018-03-06 19:09:38.496] Network diff set to 3.29T
 [2018-03-06 19:09:38.631] Pool 0 difficulty changed to 40
 [2018-03-06 19:09:43.712] USB init, open device failed, err -3, you don't have privilege to access - BSC device 1:8
 [2018-03-06 19:09:43.712] See README file included for help
 [2018-03-06 19:09:43.713] GekkoScience detect (1: failed to initialise (incorrect device?), resetting
 [2018-03-06 19:09:43.713] failed usb_init
 [2018-03-06 19:09:49.045] USB init, open device failed, err -3, you don't have privilege to access - BSC device 1:8
 [2018-03-06 19:09:49.046] See README file included for help
 [2018-03-06 19:09:49.047] GekkoScience detect (1: failed to initialise (incorrect device?), resetting
 [2018-03-06 19:09:49.047] failed usb_init
 [2018-03-06 19:09:54.379] USB init, open device failed, err -3, you don't have privilege to access - BSC device 1:8
 [2018-03-06 19:09:54.381] See README file included for help
 [2018-03-06 19:09:54.381] GekkoScience detect (1: failed to initialise (incorrect device?), resetting
 [2018-03-06 19:09:54.382] failed usb_init

I'm honored!

Also, I solved the issue. Turns out that (maybe just with my particular setup) the Terminus really dislikes USB 3.0 ports. I tried 3.0 ports both on the case and mobo and it always seemed to be capped out at hashing about 10GH regardless of the frequency or V. However, when I plugged it into one of the mobo 2.0 ports it immediately began hashing about 75GH at 175Mhz - right where it should be.

If you followed the instructions, cgminer should be living in the git/vthoang directory within your home directory. When you open up a new terminal, type " cd git/vthoang" and then to start cgminer type the run syntax "./cgminer -o (POOL INFO) -u (USERNAME) -p (PASSWORD)". Worse case if it doesn't want to work properly, recompile everything and try again. All the instructions worked like a charm for me running a few 2pacs for fun on a Pi and I literally knew nothing about Linux at the time so there is no reason it shouldn't work.

I'm sure there is a way to make it all run automatically along the lines of a .bat file but since you should not have to be starting/stopping the program all the time I never bothered to figure it out.

The "make -j 2" line is where it compiles the program. Once that line runs, your terminal should be pointing to the folder where cgminer was compiled.

After that, you run the "./cgminer -o"whateverelse line like under the "How to Run" part of the post. With your pool configs instead of the sample ones.

If you're following the directions and somewhere you think you're required to click on something with a mouse, you're probably doing something wrong.

Also what you're doing is not coding, has very little to do with coding, so coding knowledge is mostly irrelevant. What you want to learn is how to navigate a Unix/Linux terminal. Basically equivalent to DOS shell in Windows, just a whole lot better.

Uhmmm. Maybe? I think I followed the directions up above by copy/pasting each command serially as you say. When I was done there was just a new command prompt, no cgminer. Does that mean I built it? How do I know if I did it correctly?

I had to open the git file it linked to and find the cgminer executable file, which I can bring up but it won't recognize the miners and I have to copy/paste everything into it to get it started (pool address, my Bitcoin address, etc.  The same stuff I use a Windows .bat file to do).

You do know that the build instructions are done entirely by typing everything (or copy-pasting) into a terminal, exactly as it's presented, right? Put in one line, hit "Enter", wait for it to do its thing and get you back to the shell prompt, and then punch in the next line. Should take minutes. Except for the "apt-get install" all the dependencies line, I've pretty much got the whole thing memorized by now.