Bitcoin Forum
May 28, 2024, 11:31:03 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Bitcoin / Hardware / Re: GekkoScience Terminus R808 Miner Official Support Thread on: April 23, 2018, 07:15:11 PM
The first step to addressing a warranty concern is, talk to the person you bought it from.

thx sidehack.  all over it.

BTW, here they are in action:

2  Bitcoin / Hardware / Re: GekkoScience Terminus R808 Miner Official Support Thread on: April 21, 2018, 05:14:02 AM
"GSE 2: Terminus BM1384 Bitcoin Miner (10030213)
 [2018-04-20 23:21:48.650] GSE 2: found 0 chip(s)
 [2018-04-20 23:21:48.651] Hotplug: GekkoScience added GSE 2
 [2018-04-20 23:21:48.651] GSE 2 failure, disabling!
 [2018-04-20 23:21:48.651] GSE 2: setting frequency to 100.00MHz"

Worked great for two days - almost a straight 48 hours @225MHz in a cooled environment w/ a window fan.  Shut down (unplugged 12v brick) when I was rebooting main system (OS X) and when powered unit back up I noticed that the fans were not turning and got the above message from cgminer. (4.10.0)

Awesome product sidehack / vh and thanks for all the work!  I suspect the unit is dead however.  Purchased from source (sales@gekkoscience.com) so am I able to send for repair or replacement and if so what is the procedure?  If I missed a post regarding this issue plz just throw a link at me.

Thanks in advance!


BTW - Here's what's going on with the mine:

10x 2Pac's on 2x Anker hubs @150MHz (5x ea.)
2x Terminus 808's @ 225MHz
AVG:  190 - 445Gh/s

AWESOME!!
3  Bitcoin / Hardware / Re: GekkoScience 2Pac BM1384 Stickminer Official Support Thread on: December 09, 2017, 03:40:47 AM
Have you tried compiling without Icarus support? You don't need it for either Gekkoscience stick, VH's driver is better. Might be causing conflicts in the detection process.

sidehack...  man, thanks for the speedy response!!!  I'll give it a try and report back, hopefully successfully.

Also, very sincerely thanks for all the effort and wishing you great success with your ongoing & upcoming projects.  I'll stay tuned in fo' sho'.

-
m
4  Bitcoin / Hardware / Re: GekkoScience 2Pac BM1384 Stickminer Official Support Thread on: December 09, 2017, 03:19:22 AM
Greetings.

Has anyone successfully compiled the vthong/cgminer for these really cool looking sticks (thanks in advance vh/sidehack!!!) on OS X (Sierra 10.12.6) lately and its working for you?

Here's my situation:

- 1 2pac on on ANKER 5v hub.
- Total String voltage set @ ~1.47v. -  double...  triple...  every try (you know what they say about insanity, right?)...  voltage checked.
- compiled vthong/cgminer from git using all instructions provided throughout this thread, the various README texts & the ckolivas/cgminer thread using autotools build process as well as trying the ./configure, make, make install method.  (--enable-gekko --enable-icarus) Even tried Homebrew but no new taps for the 2pac code.
- removed all other usb devices (usb hub, keyboard & mouse excepted)
- ran the "sudo usermod -G plugdev -a `whoami`
sudo cp 01-cgminer.rules /etc/udev/rules.d/
sudo reboot" commands.  I'm thinking that is for the Linux build process, but wtf at this point.  No go.
- every time cgminer is launched (in Terminal) this is the output:

 [2017-12-08 20:57:05.386] Started cgminer 4.10.0
 [2017-12-08 20:57:05.387] Loaded configuration file /Users/**user**/.cgminer/cgminer.conf
 [2017-12-08 20:57:05.387] Fatal JSON error in configuration file.
 [2017-12-08 20:57:05.387] Configuration file could not be used.
 [2017-12-08 20:57:05.775] GekkoScience detect (253:7) failed to initialise (incorrect device?), resetting
 [2017-12-08 20:57:05.775] failed usb_init
 [2017-12-08 20:57:06.221] No devices detected!
 [2017-12-08 20:57:06.221] Waiting for USB hotplug devices or press q to quit
 etc.

I've tried the older solutions suggested in both threads - Fabulous Panda, Asteroid (I think its called), etc.

Maybe I'm in the wrong thread for this issue and apologize in advance if so...  but I'm just at wit's end.

I have very basic coding skills (in fact, the last thing I wrote WAS actually in BASIC!?!) so please be gentle and would you very very intelligent folks maybe offer some suggestions, pointers, links, anything that might help get me on the right track.

Thanks in advance for your help.



5  Other / Beginners & Help / Re: ATI 5770 GUIMiner / poclbm will not connect on: January 07, 2014, 08:11:44 PM
Problem solved!

Using bfgminer to control 5770 in Terminal.  Works great.  55Mh/s+!  Working on squeezing a little more out of it.
6  Bitcoin / Mining support / Re: GUIMiner-poclbm-os x 10.6.8- just stopped working!! on: January 06, 2014, 06:47:49 PM
Update...  all seem to be working properly again!?!
7  Bitcoin / Mining support / GUIMiner-poclbm-os x 10.6.8- just stopped working!! on: December 30, 2013, 04:44:38 AM
Running GUIMiner/poclbm v2011-11-22 fine (20+Mh/s each on several GPUs) until Monday 12/22 and the application just stopped running on 3 systems simultaneously??!!??

Keep getting this error on all miners/systems:

Unexpected error:
2013-12-29 22:34:11: Listener for "user": Traceback (most recent call last):
2013-12-29 22:34:11: Listener for "user": File "HttpTransport.pyc", line 45, in loop
2013-12-29 22:34:11: Listener for "user": File "Transport.pyc", line 117, in queue_work
2013-12-29 22:34:11: Listener for "user": File "Transport.pyc", line 76, in process
2013-12-29 22:34:11: Listener for "user": File "Transport.pyc", line 71, in set_difficulty
2013-12-29 22:34:11: Listener for "user": error: unpack requires a string argument of length 32
2013-12-29 22:35:47: Listener for "user" shutting down


Any help?  A pointer to a topic I'm missing??

I suspect that maybe since mining difficulty has shifted to 1B+ that maybe there's something to the "...requires a string argument of length 32" error but I just don't have the knowledge to track down an answer.

I've looked for updated miners & gui's, searched The Bitcoin Forum, etc. and no answers.

Thanks in advance for replies.
8  Other / Beginners & Help / ATI 5770 GUIMiner / poclbm will not connect on: December 18, 2013, 05:27:27 AM
Running MacPro G-4.1 on OSX 10.6.8 and GUIMiner/poclbm v2011-11-22 will not start mining with ATI Radeon HD 5770. No flags crashes & -v flag never connects to pool (BTCMP).

Constantly crashes on Line 2:

"Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Crashed Thread:  2
"

"Thread 2 Crashed:
0   libSystem.B.dylib                0x00007fff8a5b7290 strncmp + 16
1   ...pple.ATIRadeonX3000GLDriver   0x000000010bce33d8 glrCompLoadBinary + 3560
2   ...pple.ATIRadeonX3000GLDriver   0x000000010bce34db glrCompLoadBinary + 3819
3   ...pple.ATIRadeonX3000GLDriver   0x000000010bce3692 glrCompBuildProgram + 322
4   com.apple.opencl                 0x00007fff81840175 clBuildProgram + 2301
5   _cl.so                           0x0000000103473689 pyopencl::program::build(std::string, pyopenclboost::python::api::object) + 141
6   _cl.so                           0x0000000103470e18 _object* pyopenclboost::python::detail::invoke<int, void (pyopencl::program::*)(std::string, pyopenclboost::python::api::object), pyopenclboost::python::arg_from_python<pyopencl::program&>, pyopenclboost::python::arg_from_python<std::string>, pyopenclboost::python::arg_from_python<pyopenclboost::python::api::object> >(pyopenclboost::python::detail::invoke_tag_<true, true>, int const&, void (pyopencl::program::*&)(std::string, pyopenclboost::python::api::object), pyopenclboost::python::arg_from_python<pyopencl::program&>&, pyopenclboost::python::arg_from_python<std::string>&, pyopenclboost::python::arg_from_python<pyopenclboost::python::api::object>&) + 104
7   _cl.so                           0x000000010347a9a1 pyopenclboost::python::detail::caller_arity<3u>::impl<void (pyopencl::program::*)(std::string, pyopenclboost::python::api::object), pyopenclboost::python::default_call_policies, pyopenclboost::mpl::vector4<void, pyopencl::program&, std::string, pyopenclboost::python::api::object> >::operator()(_object*, _object*) + 135
8   _cl.so                           0x00000001034b0e73 pyopenclboost::python::objects::function::call(_object*, _object*) const + 733
9   _cl.so                           0x00000001034afa20 pyopenclboost::python::objects::py_function_impl_base::~py_function_impl_base() + 358
10  _cl.so                           0x00000001034bf1bc pyopenclboost::python::detail::exception_handler::operator()(pyopenclboost::function0<void> const&) const + 174
11  _cl.so                           0x00000001034a0b42 bool pyopenclboost::_bi::list3<pyopenclboost::arg<1>, pyopenclboost::arg<2>, pyopenclboost::_bi::value<void (*)(pyopencl::error const&)> >::operator()<bool, pyopenclboost::python::detail::translate_exception<pyopencl::error, void (*)(pyopencl::error const&)>, pyopenclboost::_bi::list2<pyopenclboost::python::detail::exception_handler const&, pyopenclboost::function0<void> const&> >(pyopenclboost::_bi::type<bool>, pyopenclboost::python::detail::translate_exception<pyopencl::error, void (*)(pyopencl::error const&)>&, pyopenclboost::_bi::list2<pyopenclboost::python::detail::exception_handler const&, pyopenclboost::function0<void> const&>&, long) + 24
12  _cl.so                           0x00000001034a097b pyopenclboost::detail::function::function_obj_invoker2<pyopenclboost::_bi::bind_t<bool, pyopenclboost::python::detail::translate_exception<pyopencl::error, void (*)(pyopencl::error const&)>, pyopenclboost::_bi::list3<pyopenclboost::arg<1>, pyopenclboost::arg<2>, pyopenclboost::_bi::value<void (*)(pyopencl::error const&)> > >, bool, pyopenclboost::python::detail::exception_handler const&, pyopenclboost::function0<void> const&>::invoke(pyopenclboost::detail::function::function_buffer&, pyopenclboost::python::detail::exception_handler const&, pyopenclboost::function0<void> const&) + 43
13  _cl.so                           0x00000001034bf223 pyopenclboost::python::handle_exception_impl(pyopenclboost::function0<void>) + 99
14  _cl.so                           0x00000001034aff4f pyopenclboost::python::detail::pure_virtual_called() + 191
15  org.python.python                0x0000000102b08ec1 PyObject_Call + 97
16  org.python.python                0x0000000102ba0845 PyEval_EvalFrameEx + 18725
17  org.python.python                0x0000000102ba37d7 PyEval_EvalCodeEx + 2103
18  org.python.python                0x0000000102ba3988 PyEval_EvalCode + 360
19  org.python.python                0x0000000102ba062d PyEval_EvalFrameEx + 18189
20  org.python.python                0x0000000102ba37d7 PyEval_EvalCodeEx + 2103
21  org.python.python                0x0000000102ba3988 PyEval_EvalCode + 360
22  org.python.python                0x0000000102ba062d PyEval_EvalFrameEx + 18189
23  org.python.python                0x0000000102ba37d7 PyEval_EvalCodeEx + 2103
24  org.python.python                0x0000000102ba3988 PyEval_EvalCode + 360
25  org.python.python                0x0000000102ba062d PyEval_EvalFrameEx + 18189
26  org.python.python                0x0000000102ba37d7 PyEval_EvalCodeEx + 2103
27  org.python.python                0x0000000102ba3988 PyEval_EvalCode + 360
28  org.python.python                0x0000000102ba062d PyEval_EvalFrameEx + 18189
29  org.python.python                0x0000000102ba3913 PyEval_EvalCode + 243
30  org.python.python                0x0000000102ba062d PyEval_EvalFrameEx + 18189
31  org.python.python                0x0000000102ba37d7 PyEval_EvalCodeEx + 2103
32  org.python.python                0x0000000102b3144b PyClassMethod_New + 1547
33  org.python.python                0x0000000102b08ec1 PyObject_Call + 97
34  org.python.python                0x0000000102ba0eea PyEval_EvalFrameEx + 20426
35  org.python.python                0x0000000102ba3913 PyEval_EvalCode + 243
36  org.python.python                0x0000000102ba062d PyEval_EvalFrameEx + 18189
37  org.python.python                0x0000000102ba3913 PyEval_EvalCode + 243
38  org.python.python                0x0000000102ba062d PyEval_EvalFrameEx + 18189
39  org.python.python                0x0000000102ba37d7 PyEval_EvalCodeEx + 2103
40  org.python.python                0x0000000102b3144b PyClassMethod_New + 1547
41  org.python.python                0x0000000102b08ec1 PyObject_Call + 97
42  org.python.python                0x0000000102b1ac47 PyInstance_New + 16535
43  org.python.python                0x0000000102b08ec1 PyObject_Call + 97
44  org.python.python                0x0000000102b9b324 PyEval_CallObjectWithKeywords + 180
45  org.python.python                0x0000000102bd8042 initthread + 2754
46  libSystem.B.dylib                0x00007fff8a5edfd6 _pthread_start + 331
47  libSystem.B.dylib                0x00007fff8a5ede89 thread_start + 13"

I suspect since this is an older OSX Machine & maybe mismatched GPU that maybe I'm missing a driver or firmware update for the ATI 5770.  Getting about 50Mh/s with ganged GeForce cards on seperate machines (prob losing $$$) but the ATI 5770 would triple capacity.  Still "dry-panning at Carbon Creek" but its something.  Any help greatly appreciated!

Of particular note in Thread 2 - "1   ...pple.ATIRadeonX3000GLDriver   0x000000010bce33d8 glrCompLoadBinary + 3560"  Maybe wrong driver?

Thanks in advance for any replies!!

Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!