PM sent

I thought about that, about an hour after I sent the post.  Well we will see if they do anything on a Weekend or if I get something on their Monday.

Just fired off an e-mail to them about 10 minutes ago.  Lets start the clock.

First thing I would just try a reboot on your router.  If you do DHCP for your miners, try moving them to static IPs in your subnet.  Make sure those static IPs are not in the "Dynamic Space" that your router assigns as some other device on your network may be taking the address.  IP networking works mostly by a who responds first method, so if you have two devices that somehow get the same IP (should not happen with DHCP, but depending on the software in the router it can), the faster guy wins and a PC, Tablet, Phone etc... which are designed to be more real time will almost always win.

If your router supports it (and you can find it), look at the connected devices page. See what MAC address it says for the IP you have assigned to the miner.  Compare that with the info from the minor info screen.

It is rare, but some older home router firmware (or broken firmware) will not have a good NAT (Network Address Translation) table that will make is so something that connects gets dropped.  This most often only happens with things like VoIP and Gaming but can happen with other protocols.  If you can, I would find a "High Quality" not "High Priced" router, and better yet try a custom firmware load like DD-WRT or OpenWRT if you have the willingness to go that far.

I run an older Netgear WNDR3700 v3 with DD-WRT with over 25+ devices doing both outbound and inbound connections.

Hi All,

First Thank You Canary for doing the group buy!

Has anyone noticed that running these on the USB Controller is highly unstable?  

I have two of my three units so far and both are highly unstable.  I can not get them to keep up at anywhere near 1.4Ths.  I can get them to run, but they drift all over the place from 600Ghs to an occasional burst at 1.5Ths.  

I have tried running them on the RPi and the CubieTruck.  I have used the stock 4.7.0 CGminer, Fixed Debian Build of 4.7.0-1 CGminer, and the BlockErupter 4.6.1 build of CGminer from GitHub.  None have fixed or even made improvements.  I have tried both the standard (no --bet-clk option) and --bet-clk=23 timing.  

One thing I have noticed is that there is a lot of extended output in the BlockErupter Controller, that shows the chip status.  Can we get that status from CGminer somehow?

On the official CGminer 4.7.0 on both the RPi and on CubieTruck I got those errors on both options. As I said in an earlier post, pulling the USB controller and putting it back may have cleared it up.

This is for those of you who have the USB controller.

I found something that may or may not be of use and needs some testing by others.

If in CGminer you are getting

-- Sync Error
-- Unexpected ??

Try this:

1. Shutdown CGminer (Yes I know it has hot-plug)
2. Unplug and re-plug the USB Controller (power-cycling a powered hub may work)
3. Restart CGminer.

Please report back.

After I had power cycled the Prisma itself 3 times and this problem did not go away I was frustrated and tried this thinking what could happen and it fixed the problem.  I am thinking their may be some sort of initiation issue in ASICMiner's code they gave the CGminer folks.  Causing a already initiated USB-to-Serial device to not correctly re-initialize.

I have had each of two of them up with CGminer 4.7.0 on Both Rasbien Jessie and Debian Jessie on the CubieTruck. 

Important note on CGminer for Debian Jessie, the one that fell into the repository is broken.  We did not catch a build system bug fast enough.

The Prisma is a bit of a bear to get running.  It seems to generate a *LOT* of crap when it starts up and sometimes will cause CGminer to segmentation fault.  This is not the fault of the CGminer folks as they were just given the driver by ASICMiner and included it.  After a couple of tries of starting CGminer it will hash stably.

Another minor item to note: The chip on the USB device seems to get power from Prisma so if you power off the Prisma it will disconnect from the computer or at least one of mine did.

Can we get someone with direct contact to ASICMiner in the forums working on providing more info on switchs and what the errors in CGminer mean?  I know they have said China is blocking BitcoinTalk, but any *Good* hacker can get around a firewall or find a friend to be a communication person for them.

The following is a questing from the Debian pkg-bitcoin-dev group and I am interested too:


Debian Jessie and Unstable (SID) libusb
libusb-1.0-0 (2:1.0.19-1)

I get this also but if I restart CGminer a few times it eventually starts hashing fine.  Seems that there is something odd with the driver or the chips put out some odd crap at first after power up.

However I have a question about the -bet-clk=23 thing  According to CGminer docs this value is x10 so to get 240 you would want 24, which is the default value of the setting.  Am I understanding this wrong?  Do we need to run the Prisma at 230 not 240?  At --bet-clk=23 my unit will not do stable over 800Ghs

CrazyGuy was talking about making a Minera image for the RPi but I do not know where he is on it.

I working on a port to a Debate package, but I don't know how much else is going on.

I will be putting out a packaged version of cgminer 4.7.0 for Rasbian as soon as we can get the bugs in the build system ironed out.  I do not know if I will be able to back port to wheezy or if they will only be early builds for Jessie.  I have a working package for Jessie now on Rasbian but want the official numbering fixes done before I let it into the wild.

Hi All,

My first 2 of 3 Prismas showed up at my office on Thursday.  I had one of my drivers bring one home to me to play with this weekend and here are my initial reactions to the device.

1. Device itself.
a. BIG
b. Pretty, (Geeky way, Sci-Fi fan and all)
c. Functionality:
One of the handles is a little bent in but that only made it a bit difficult to connect a PSU connecter.  The Dip switches being where they are will make setting the next one in the chain up interesting.  Speaking of that where is the chart on the switches?

2. Software Setup / USB device
I am using the USB dongle, as the current software for the Controller Box does not work with most pools

a. CGminer
After figuring out that the Debian build of CGminer was broken (long story).  I was able to get the unit to work somewhat.  I was getting a lot of "Unexpected Response 00 from BET 0" and "Sync Error"  I am not sure what is causing this as the solution was several power cycling of the miner and unplugging the USB device from the computer.

b. BFGminer
I built a custom 4.10.0 build of BFGminer but was not able to get it to detect the Prisma at all.  I tried several things without results.  Will have to look into this more.

3. Powering
a. Don't even bench test with less then a 1300W PSU.  I had a 1000W PSU I thought I could use on the bench for short power up tests and minor 10 minutes bursts of mining.  No it did not work.  Thank god for protection circuits or that sucker would have been a goner.

b. Using Dual PSUs, there may be a sequencing thing that is needed to be done with the boards.  I have not proven this yet.  I am still testing to see if this is what causes the errors mentioned above.

Please note that the build of CGminer 4.7.0 currently in Debian unstable probably will not work. It was compiled with some of the drivers enabled that should only be enabled on dedicated hardware.   

I am working with the Debian pkg-bitcoin-dev team to get this fixed.

This is for those lucky few of you who have their units and USB controllers. I do not have my unit yet so can not test this.

CGminer 4.7.0 has now been added to Debian Sid (unstable). If you find any bugs please use reportbug on your Debian system, so we can get them tracked.

A little addition to my previous note on CGminer 4.7.0 getting into Debian Sid. It got built for all architectures.

If you are running Jessie you can manually pull the package down from your favorite mirror and install it with the "dpkg -i " command.

[Pkg-bitcoin-devel] cgminer_4.7.0-1_i386.changes ACCEPTED into unstable

Debian FTP Masters ftpmaster at ftp-master.debian.org
Sun Oct 26 15:50:06 UTC 2014
Previous message: [Pkg-bitcoin-devel] Processing of cgminer_4.7.0-1_i386.changes
Next message: [Pkg-bitcoin-devel] Bug#757381: marked as done (cgminer:   autobotched manpage)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Accepted:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sun, 26 Oct 2014 10:04:39 -0400
Source: cgminer
Binary: cgminer
Architecture: source i386
Version: 4.7.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Bitcoin Packaging Team <pkg-bitcoin-devel at lists.alioth.debian.org>
Changed-By: Scott Howard <showard at debian.org>
Description:
 cgminer    - multi-threaded multi-pool Bitcoin miner
Closes: 757381
Changes:
 cgminer (4.7.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * libusb_init_warning.patch: Log a warning and don't quit if
     libusb_init() fails (Closes: #757381).
Checksums-Sha1:
 4ad3ea80570108377aaea9d0a5996f29ad8127bf 2068 cgminer_4.7.0-1.dsc
 e14f159f617a54d9e1f2fef4a102c5b2c3c3d2d4 2048238 cgminer_4.7.0.orig.tar.gz
 90a00ca63d647de874ea6c899e03e58cdfa88954 10708 cgminer_4.7.0-1.debian.tar.xz
 a196d70fc58ac8b318016388e44412509d94b8e4 577918 cgminer_4.7.0-1_i386.deb
Checksums-Sha256:
 ecaa77f5ebd400210b75cee61f290da08486a0614ee35b0afc981dd64c0cdc7a 2068 cgminer_4.7.0-1.dsc
 fc9430bf18a55787c1cf478620116881ddcb6cdb1b16f167c15675cd5e3216b0 2048238 cgminer_4.7.0.orig.tar.gz
 e3451184e15b690245ac044b77129ce678e043162c8866f799876993822dfaf5 10708 cgminer_4.7.0-1.debian.tar.xz
 c0c799e5a135a303d9dbe8b89408041ae3640ade107fefab328f65b4ff11c8c7 577918 cgminer_4.7.0-1_i386.deb
Files:
 57f3700cf5d6185c5af34d91b3d7c1b6 2068 net optional cgminer_4.7.0-1.dsc
 15c74490a78b52845d8fbd8fef9af330 2048238 net optional cgminer_4.7.0.orig.tar.gz
 1556ed06f4bb3bcd7756b99157990b34 10708 net optional cgminer_4.7.0-1.debian.tar.xz
 42547121c9fc014a7e4d89287f7092e0 577918 net optional cgminer_4.7.0-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUTQaLAAoJEI7QYGkDfiTyknsQAKSxWQaVkY0eexAe9KCAv7X7
NrxKxm4Q6SncMYzrtrhG8RG7eeUjBl2lwGPDVGecQdKlDT3pAI6hlM2eDj2wm/2Z
noljZ4/WCWdMM0Ck0K5Tt9MxQjD+uS3Cfqr0xBMRTgYjx299vN3phKERQqwSrE4F
iX1ZAt9UPuNeyLMAL8c0kNfLuKIvqkYwJTc0aMyGry56eyTa/JvbDIhrByr7KOyM
rxxQGcJPQaNk4R4aKntB9B4DI6eK/mJ+MbGk8VFwnGhKa/2VcHyCGILYQf18LFTe
ywil0rhza0UmEPlweOJE3j/QdvbPMrK2JYZPb0kWDhoILbzy/ZysI8ihlfhKE/tn
bch43h+uJ8o/PddIQfZXNaNgwk2MXcNdKZUgGV2JKnEG1x81Uq8fQ9iUzwXcZaWq
9xgKxLv2xwJ6M9LfwO0UNR/MGTLHrtN+D6Q8wwzTOUHBuXKctUqlB+8Gq8CvbR7/
vm02uSpaiW2ll5S4kEo/eOmyG+YRGa6+3a5yMMzkFRAgKnkZgZh8srgwMCN80wQR
+Lnr1EIPQKmgdODyB2FBWZtv+rQPQq6aaGLPTbOYi8rQjFq3JccB98ku+A5NwU2H
gto1K0TzQMkDZZY8w4/dW5G6/G2CHwMLQFwjgrJg9usNFBhRojhH/5mu/SJ29Zpl
gUrftd8y78qQBvcRqHLM
=0qqQ
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.

Previous message: [Pkg-bitcoin-devel] Processing of cgminer_4.7.0-1_i386.changes
Next message: [Pkg-bitcoin-devel] Bug#757381: marked as done (cgminer:   autobotched manpage)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Pkg-bitcoin-devel mailing list

The easiest way to reset the password is to use the small reset button on the Antminer S1 controller board. This will reset all of the settings and its IP address back to defaults.

For detailed instructions, Doggie has a guide here in the forum on the Antminer S1. I don't have the link handy but a quick search will find it.

You made a small typo there. That should be 192.168.1.99.

I have both bought and sold several units on eBay. Bought them as I was moving up from Stick Miners and sold them as I move to S3s and beyond.