[/share/HDA_DATA/Qdownload/bfgminer] # dmesg | tail
[356363.150000] usb 1-1.3.1: new high speed USB device using orion-ehci and address 22
[356363.280000] hub 1-1.3.1:1.0: USB hub found
[356363.280000] hub 1-1.3.1:1.0: 4 ports detected
[356363.420000] usb 1-1.3.2: new full speed USB device using orion-ehci and address 23
[356363.630000] usb 1-1.3.3: new full speed USB device using orion-ehci and address 24
[356363.840000] usb 1-1.3.4: new full speed USB device using orion-ehci and address 25
[356364.050000] usb 1-1.3.1.1: new full speed USB device using orion-ehci and address 26
[356364.290000] usb 1-1.3.1.2: new full speed USB device using orion-ehci and address 27
[356364.500000] usb 1-1.3.1.3: new full speed USB device using orion-ehci and address 28
[356364.730000] usb 1-1.3.1.4: new full speed USB device using orion-ehci and address 29
[/share/HDA_DATA/Qdownload/bfgminer] #
This suggests you don't have the cp210x driver (part of Linux). It should say: [3551139.516400] usb 1-5.1.1: new full-speed USB device number 45 using ehci_hcd
[3551139.609866] usb 1-5.1.1: New USB device found, idVendor=10c4, idProduct=ea60
[3551139.609874] usb 1-5.1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[3551139.609881] usb 1-5.1.1: Product: Block Erupter Sapphire (Silver)
[3551139.609886] usb 1-5.1.1: Manufacturer: Bitfountain
[3551139.609891] usb 1-5.1.1: SerialNumber: ljr0002
[3551139.610704] cp210x 1-5.1.1:1.0: cp210x converter detected |
|
|
|
Remove the --temp-cutoff commandline or "temp-cutoff" from your config file.
thx I have erased the line with --temp-cutoff from config now what is a good target temp for BFL LS? is 65 - 67 ok? TIA BFL devices don't currently support temp-target and ignore it. You can set a temp-cutoff (85 seems like a good value), but note BFGMiner has to shut it off entirely when it goes above it. Do I use the conf file OR the .bat file or do I need both?
Generally one or the other. |
|
|
|
now on BFL LS: Too many values passed to set temp cutoff and a few minutes unable to start new.. Remove the --temp-cutoff commandline or "temp-cutoff" from your config file. |
|
|
|
bfgminer 3.1.4 changed the default storage location for the bfgminer.conf file. Err, no it didn't... O.o;; my mac stores it in ~/.bfgminer/bfgminer.conf used to be stored in ~/bfgminer.conf O.o {facepalm} Must be a homebrew thing... It's always been ~/.bfgminer/bfgminer.conf officially. So, I've amended the bfgminer.conf file removing the pools I don't want and saved it using all files and the .conf extension and yet the pool still appears when I restart bfg.
do I just have to amend each time i have to restart bfg?
It sounds like you're somehow starting bfg with these pools on the commandline. The config file won't remove pools you put on the commandline. |
|
|
|
bfgminer 3.1.4 changed the default storage location for the bfgminer.conf file. Err, no it didn't... O.o;; |
|
|
|
As for addresses, I'm not sure what might be more accurate... Safety deposit box numbers, "SDB" numbers? As with actual postal or bank storage boxes we don't really have their precise coordinates, just a number telling us which one it is. This reenforces the incorrect understanding. There is no grouping by address at all. |
|
|
|
A question, though. What's that DEAD MMQ? I only have 2 Block Erupters running on this system. Using -S erupter:all ? Side note: any idea what other serial device is in your PC? Ah, no. Just -S opencl:noauto -S all Using erupter:all fixed this (in addition to showing BES instead of ICA, and Identify appearing in the Manage list). Other devices are: mouse, keyboard, webcam, iPhone, internal cardreader, internal docking hub. hmm, I wonder if iPhone appears as a MMQ somehow... |
|
|
|
A question, though. What's that DEAD MMQ? I only have 2 Block Erupters running on this system. Using -S erupter:all ? Side note: any idea what other serial device is in your PC? |
|
|
|
Did that change recently? I recall you mentioning in an earlier version that the Zadig drivers would "break" BFGMiner. The Zadig drivers are non-standard. Since Windows doesn't allow two drivers to be installed, Zadig removes the standard ones, thus breaking BFGMiner (and anything else that works with it normally). |
|
|
|
I run a linux Ubuntu Quantal 64-bit system. I compiled BFGMiner from the git archive. When I try to get the miner to detect my Block Erupter USB, it doesn't report that anything is available. I tried "-S all" and it refuses to detect anything except my CPU. First, be sure you have rebooted or replugged the device after running cgminer, if you have run it (it corrupts the driver). If that's not the problem, try the command in README: sudo modprobe cp210x vendor=0x10c4 product=0xea60 Finally, if it still doesn't show up, please post the output from: lsusb -vv
ls /dev/ttyUSB*
lsmod
dmesg |
|
|
|
However, at this point I'm thinking of augmenting it so that it snatches weak funds immediately so I can return funds to peeps who are able to prove ownership of the victim address by signing a message with a bunch of keys with a 1-degree relationship to that address. I'd suggest just requiring the signature of the key itself, plus verifying a name/address. Then share the name/address with others signing for it and let the legit party sue the fraudulent claimee(s) in court.  |
|
|
|
Addresses don't have balances.
From a layman's point of view, that makes no sense. Regardless of how Bitcoin technically works (from the point of view of a developer), most users know of "addresses" and an amount of Bitcoins "located" at that address. That would be a "balance", a.k.a. an amount. This misunderstanding is where education is needed. |
|
|
|
I don't understand. If I print out a paper wallet, why can't I send to that address more than once? Proper paper wallets have unlimited addresses. For example, Armory supports paper wallets. One huge problem stands still, though.
Official client does not agree.
It likes reusing burnt addresses. 1) There is no official client. 2) Bitcoin-Qt never reuses addresses itself. And this is a REAL ISSUE.
We cannot go live before this is fixed.
What's your position about that? All of the Bitcoin-Qt dev team seem to be in agreement that the "Receive coins" tab could use a makeover to discourage address reuse better. |
|
|
|
|
Addresses don't have balances. They are single-use destinations to send coins to, which point at a wallet. While it's technically possible to send to the same address more than once, doing so violates the design of Bitcoin and is problematic from at least a privacy and security standpoint - even if you don't care whether you're anonymous or not. It also provide zero performance/storage benefits: Bitcoin won't notice both transactions were sent to the same address (the system itself has no concept of addresses!). Hopefully the new payment protocol in 0.9 and HD wallets will help eliminate the usability benefits of address reuse.
|
|
|
|
Looks nice, but for $10 more I'd rather use the device atmel studio expects This is the free software thread. Atmel Studio is off-topic. |
|
|
|
Luke, seriously you wish to become a politician? Not really, but someone has to do it, and generally anyone who wants to isn't a good choice.What? Don't you want to? Last time I checked you weren't forced into the role. If I don't, someone else will. Now if someone like gmaxwell were willing, I'd decline my nomination and vote for him instead.  |
|
|
|
Luke, seriously you wish to become a politician? Not really, but someone has to do it, and generally anyone who wants to isn't a good choice. I'd understand you buying your way to the top but political ambitions rarely end up as intended. Huh? |
|
|
|
BFGMiner with BFL LS for [F]an control [D]isable [I]dentify [F]an control
Or press Enter when done
ERR:UNKNOWN COMMAND
It's disabled on current firmwares  |
|
|
|
|
FPGAs aren't mere software.
While scrypt in general might need some RAM added, Litecoin's scrypt can probably be done.
|
|
|
|
|
Show Posts
