Really not meaning to offend anyone, this has been a very interesting and entertaining thread, even inspiring all around in a way that leads to substantially more decentralization. However, as an energy industry professional I must say that a kw/h and a kWh is substantially exactly the same thing. Not sure what you guys are onto here... a kW is a unit of energy, it is a 1,000 Watts. Watts are convertible to Joules or Therms or any other unit of energy. And a kW/h is the number of kiloWatts consumed in an hour, as is a kWh, the number of kiloWatts consumed in an hour. a kW is a measurement of power, and a kWh is a volumetric measurement of energy. you can use 100kW in one hour is 100kWh or you can use 50kW for 30 minutes and 150kW for 30 minutes and it will also be 100kWh.
I don't think anyone here would get offended. I'm even grateful for your post as it helped to prove my point. I'm also grateful for the correction below that is the other half of the proof of my point. You can convert Joule to Wh, it is indeed a measurement of amount of energy. Watt's cannot be converted to Joules directly as much as velocity cannot directly be converted to distance without the input of other parameters to build an equation. And a kW/h is the number of kiloWatts consumed in an hour, as is a kWh A kWh is not the number of kiloWatts consumed in an hour, same difference as you can't say that 'distance is the is the number of meters travelled in an hour'. In the analogy with distance, velocity & time; kW/h would be acceleration (how much the energy flow changes per unit of time), kW would be velocity (amount of energy flow), kWh would be distance (how much energy has flown) You can not 'use' xx kW in one hour, you can use xx kWh in one hour though. kW/h is simply the wrong unit to use. But as an energy industry professional you of course know better  This is not really on-topic though but it is simply confusing to people who have little knowledge about this. It might be that most understand that it's an error but using the wrong units on purpose because everyone understands is not productive. I will not go deeper into this as we might as well be discussing whether the earth is flat or not. lol yea multiplication and division are the same thing...come on guys |
|
|
|
Also had the problem with the win update. Was not able to find the miners after the update, the usb ports gave errors. Furthermore, was unable to reinstall the silicon labs driver package for usb as per openingtopic instructions. After a rollback everything immediately worked again so i'm guessing there's a kink in the new windows update  Yea last windows update screwed up drivers pretty bad. Lots of other devices not working either. I’m sure silicon labs will issue driver update to fix soon. BTW if anyone from here is at consensus in NYC I’m there so come say hi! |
|
|
|
Happy to announce finally got our site up, and opening direct sales with almost very payment option possible. Currently serving North America, and rest of world not covered by my direct distributors. Check it out at shop.futurebit.io and use promo code SHOPLAUNCHSALE for this weekend only. Production for the Moonlander 2 has also officially ended, so this is last chance to pick one up. |
|
|
|
Can I order a miner in Russia? Will I have problems at customs? I would like to know the price for Russia
You can try bitshopper or eyeboot...they will probably have the cheapest shipping to Russia. |
|
|
|
You should see 5.4.2-38 at the top if your running the latest version.
It crashed again with segmentation fault although it was not running that specific version. It was running 5.2.0-243. How would i go about rebuilding for latest version? That is the latest version...my fork is just stuck on 5.2 because thats when I forked it...should probably update that. How many units are you running, and what kind of system. |
|
|
|
|
FYI I had done some research on these a while back...keep in mind these are DEVELOPMENT boards...they have alot of crap on them that is not needed for a straight mining board. I did preliminary work on stripping all this stuff and beefing up the power/cooling for higher clocks. Don't know why you would build/buy these in their current state for mining.
|
|
|
|
I have try on A3 but use a different PIC and I get:
root@antMiner_A3:/config# ./set_voltage 1 90
version = 0xff
Wrong PIC version
Is it possible update the code in order to support A3 PIC ?
thx
Ill check the A3 and see if I can get it to work, S9 uses completely proprietary stuff on hardware and software level now so without reverse engineering it wont be possible. Im pretty sure the S9 already does auto voltage tuning anyway. |
|
|
|
@jstefanop 2 of my lander's fans are turning very slowly and the miners slowed down in speed.
Where can I get stock of those little fans?
You should be able to find them online, they are just 25mm fans. If your in NA, I will be launching my site soon that will have replacement fans. Otherwise talk to your local distributor they should have some extra. |
|
|
|
Diff on LTC now 9758801.1623634
Is not worth the invest right now, stop buying L3+ guys, now you get less than 2 usd daily in proffit, and it will be lower, it was 20 usd only 5 months ago, in 3 months you will pay
more for electricity than you mine.
Stop buying L3+ , lets give Bitman a lesson, they need to stop building this like toasters.
They are not, they are probably deploying their 16nm scrypt chips to their data centers now, any L3+ for sale are probably their old units they are swapping out. We will probably be seeing their 1GH 500 watt miner for 2k USD by june for sale, after they have ROIed their own stuff of course. |
|
|
|
Thx jstefanop.
Testing my ten L3+ with lowest voltage (0xfe). Currently running 400 frequency.
Can this set frequency for each board individually?
for example :
board 1,2,3 running very smooth on 450 frequency & voltage 0xc0 with less HW
board 4 cant go over 400 no mater how high is voltage (0x30) , too much HW (error every sec)
No since tuning voltage and frequency for each board is redundant and way more complicated than it needs to be. You just choose a frequency you want to run, and then tune the voltage on each board. Sounds to me like you have a faulty board....there are some boards that will just produce more errors regardless of what voltage/frequency you set (i.e. some chips just have logic defects that will produce errors even if the frequency/voltage is low/high enough). |
|
|
|
After about 1 hour of run time at 555Mhs @ freq 425 I have 2-3 errors on boards 1 & 2, board 3 has zero and
board 4 has 12 HW errors so 1 every 5 minutes.
I will try to decrease the voltage on the 1-3 boards, was set to CO but will try DO and if it has to many can
back off to C8 (think half way between the two settings). So hex values A0, B0, C0 etc and half way finer
settings between those are A8, B8, C8 etc, we have 254 steps for voltage 127 plus and 127 neg of midpoint?
Thats correct, 0x08 gives a resolution of +/- 16 steps that should be sufficient for most tuning. If you really want to go up one step at a time for people that don't know hex...if your starting at 0x90 you would go 0x91, 92....99, 9A, 9B....9F, A0, A1 etc... but that is quite over kill since a single step changes the 12v input voltage by about 10mv, which translates to less than 1mv at the chip level (chip core voltage is input voltage/12). |
|
|
|
Just thought I'd let people know, I ran the tool on my L3++ and the default voltage appears to be 0x60 instead of 0x80 like on the L3+.
so the L3 ++ uses less power at the same hash rate as the L3+ ? . i might buy one more in about two weeks i have a 200 $ coupon some one gave me . sense I looked at the L3 ++ it says you can only use a 220 coupon or lower and mine expires on June 1 st. My understanding is that 0x60 is actually a higher voltage than 0x80. It comes with the frequency set at 450 and hashes around 580-585. I undervolted all but 1 board that I get hardware errors on to 0x90. L3++ is just an L3+ that uses more power and is less efficient. The 0x60 voltage setting for L3++ is a higher voltage, needed because of the higher stock frequency they ship with. Like most people with this tool have found out though most of these boards can handle higher clocks AND be undervolted. Obviously bitmain is just playing it super safe since I'm sure they get lots of newbs freaking out when they see 1 HW error  |
|
|
|
thanks, will wait for your results. @jstefanop
i wouldn't mind to pay for working version that can easily be updated using GUI.. is that possible since most of us here are probably using hosting facility. Has anyone tried down volting L3++ via lowering standard frequencies? any results?
I haven't, but I will be. My goal for this weekend is to tent my setup. In the coming days I'll try the down volting. Need to make sure they're setup and stable in their new home first. I was able to set the voltage on the L3++ to 0x90 on all but 1 of the boards. On one I left it at the default for the L3++ of 0x60 which is interestingly higher than the L3+ which is 0x80. That makes sense, since the L3++ is just an L3+ that is overclocked and they needed to raise the voltage. Thats also why its less efficient. |
|
|
|
git clone https://github.com/jstefanop/bfgminer.git ./futurebit cd futurebit git checkout futurebit2_driver ./autogen.sh ./configure --disable-other-drivers --enable-scrypt --enable-futurebit make should do it if you have all the right dependencies installed(check the readme for those). |
|
|
|
Thanks to the very few of you that have donated. Id spend some time to write a GUI version, except I would need to create a custom firmware version from scratch, since there is no way to edit the web GUI without updating the whole bitmain firmware. Figured this way would be easier and not require you to update the firmware at all. I know the command line seems scary to some but this is super easy to do, and there is very little risk of screwing up your antminer, even if you accidentally delete the whole root directory :p Bitmain's firmware is pretty good in that regard since they unpack the whole kernel and stock filesystem on each reboot. |
|
|
|
Hi. I have downloaded the software specific to the miner and it run fine on a Debian machine. Then i moved the miner to another machine that has Gentoo and bfgminer ran fine for like a day or two and then does segmentation fault. It has happened very consistently so i ran it through dbg to get log. I don't know if there is another place where i can put this or if there is other way to get more debugging info. Starting program: /home/user/bfgminer_5.4.2-futurebit2_linux_x86_64/bfgminer --scrypt -o stratum+tcp://hub.miningpoolhub.com:20523/\#skipcbcheck -u userName.minerName -p p -d 128 -S ALL --set MLD:clock=796
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7ffff4ae2700 (LWP 2349)]
[New Thread 0x7ffff42e1700 (LWP 2350)]
[New Thread 0x7ffff3ae0700 (LWP 2351)]
[Thread 0x7ffff42e1700 (LWP 2350) exited]
[New Thread 0x7ffff32df700 (LWP 2352)]
[Thread 0x7ffff3ae0700 (LWP 2351) exited]
[New Thread 0x7ffff2ade700 (LWP 2353)]
[Thread 0x7ffff32df700 (LWP 2352) exited]
[New Thread 0x7ffff22dd700 (LWP 2354)]
[Thread 0x7ffff2ade700 (LWP 2353) exited]
[New Thread 0x7ffff1adc700 (LWP 2355)]
[Thread 0x7ffff22dd700 (LWP 2354) exited]
[New Thread 0x7ffff12db700 (LWP 2356)]
[Thread 0x7ffff1adc700 (LWP 2355) exited]
[New Thread 0x7ffff0ada700 (LWP 2357)]
[Thread 0x7ffff12db700 (LWP 2356) exited]
[Thread 0x7ffff0ada700 (LWP 2357) exited]
[New Thread 0x7ffff0ada700 (LWP 2360)]
[New Thread 0x7ffff12db700 (LWP 2361)]
[Thread 0x7ffff12db700 (LWP 2361) exited]
[New Thread 0x7ffff12db700 (LWP 2362)]
[Thread 0x7ffff0ada700 (LWP 2360) exited]
[New Thread 0x7ffff1adc700 (LWP 2364)]
[New Thread 0x7ffff22dd700 (LWP 2365)]
[New Thread 0x7ffff3cb8700 (LWP 2366)]
[New Thread 0x7ffff34b7700 (LWP 2367)]
[New Thread 0x7ffff2cb6700 (LWP 2368)]
[New Thread 0x7fffe3fff700 (LWP 2369)]
[Thread 0x7ffff2cb6700 (LWP 2368) exited]
[New Thread 0x7ffff2cb6700 (LWP 2370)]
[New Thread 0x7fffe37fe700 (LWP 9331)]
[Thread 0x7fffe37fe700 (LWP 9331) exited]
Thread 13 "stratum0" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff12db700 (LWP 2362)]
0x00007ffff757ddc0 in ?? () from /usr/lib64/libcurl-gnutls.so.4
#0 0x00007ffff757ddc0 in ?? () from /usr/lib64/libcurl-gnutls.so.4
#1 0x00007ffff757319c in curl_easy_recv () from /usr/lib64/libcurl-gnutls.so.4
#2 0x0000000000437acb in clear_sock (pool=pool@entry=0x6971e0) at util.c:1837
#3 0x000000000043c7c0 in recv_line (pool=pool@entry=0x6971e0) at util.c:1937
#4 0x000000000042ce13 in stratum_thread (userdata=0x6971e0) at miner.c:9657
#5 0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#6 0x00007ffff64ccc7f in clone () from /lib64/libc.so.6
Thread 20 (Thread 0x7ffff2cb6700 (LWP 2370)):
#0 0x00007ffff711facd in read () from /lib64/libpthread.so.0
#1 0x00007ffff6eecaaf in _nc_wgetch () from /usr/lib64/libncurses.so.5
#2 0x00007ffff6eed426 in wgetch () from /usr/lib64/libncurses.so.5
#3 0x00000000004117f3 in __real_getch () at ./miner.h:206
#4 my_cancellable_getch () at miner.c:3787
#5 0x00000000004328f5 in input_thread (userdata=<optimized out>) at miner.c:8895
#6 0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#7 0x00007ffff64ccc7f in clone () from /lib64/libc.so.6
Thread 19 (Thread 0x7fffe3fff700 (LWP 2369)):
#0 0x00007ffff64cd2a3 in epoll_wait () from /lib64/libc.so.6
#1 0x00000000004172f9 in hotplug_thread (p=<optimized out>) at miner.c:13087
#2 0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#3 0x00007ffff64ccc7f in clone () from /lib64/libc.so.6
Thread 17 (Thread 0x7ffff34b7700 (LWP 2367)):
#0 0x00007ffff6497c6d in nanosleep () from /lib64/libc.so.6
#1 0x00007ffff6497baa in sleep () from /lib64/libc.so.6
#2 0x0000000000422bb2 in watchdog_thread (userdata=<optimized out>) at miner.c:11609
#3 0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#4 0x00007ffff64ccc7f in clone () from /lib64/libc.so.6
Thread 16 (Thread 0x7ffff3cb8700 (LWP 2366)):
#0 0x00007ffff712019d in nanosleep () from /lib64/libpthread.so.0
#1 0x0000000000435f75 in _cgsleep_us_r_nanosleep (tv_start=<optimized out>, us=<optimized out>) at util.c:1474
#2 0x0000000000439cf3 in cgsleep_ms_r (ms=30000, tv_start=0x7ffff3cb6ea0) at util.c:1457
#3 cgsleep_ms (ms=ms@entry=30000) at util.c:1483
#4 0x000000000042b8c5 in watchpool_thread (userdata=<optimized out>) at miner.c:11461
#5 0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#6 0x00007ffff64ccc7f in clone () from /lib64/libc.so.6
Thread 15 (Thread 0x7ffff22dd700 (LWP 2365)):
#0 0x00007ffff64c3f63 in select () from /lib64/libc.so.6
#1 0x000000000042780a in submit_work_thread (userdata=<optimized out>) at miner.c:6976
#2 0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#3 0x00007ffff64ccc7f in clone () from /lib64/libc.so.6
Thread 14 (Thread 0x7ffff1adc700 (LWP 2364)):
#0 0x00007ffff711facd in read () from /lib64/libpthread.so.0
#1 0x0000000000451d8c in read (__nbytes=8, __buf=0x7ffff1ad9dd0, __fd=13) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2 _serial_read (fd=fd@entry=13, buf=buf@entry=0x7ffff1ad9dd0 "<\020\377\032\t'V\024`\f", bufsiz=bufsiz@entry=8,
eol=eol@entry=0x0) at lowl-vcom.c:1239
#3 0x0000000000455042 in futurebit_scanhash (thr=0x6bbc10, work=0x6bb330, max_nonce=<optimized out>) at driver-futurebit.c:650
#4 0x0000000000433d3f in minerloop_scanhash (mythr=0x6bbc10) at deviceapi.c:274
#5 0x0000000000434eb2 in miner_thread (userdata=0x6bbc10) at deviceapi.c:772
#6 0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#7 0x00007ffff64ccc7f in clone () from /lib64/libc.so.6
Thread 13 (Thread 0x7ffff12db700 (LWP 2362)):
#0 0x00007ffff757ddc0 in ?? () from /usr/lib64/libcurl-gnutls.so.4
#1 0x00007ffff757319c in curl_easy_recv () from /usr/lib64/libcurl-gnutls.so.4
#2 0x0000000000437acb in clear_sock (pool=pool@entry=0x6971e0) at util.c:1837
#3 0x000000000043c7c0 in recv_line (pool=pool@entry=0x6971e0) at util.c:1937
#4 0x000000000042ce13 in stratum_thread (userdata=0x6971e0) at miner.c:9657
#5 0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#6 0x00007ffff64ccc7f in clone () from /lib64/libc.so.6
Thread 2 (Thread 0x7ffff4ae2700 (LWP 2349)):
#0 0x00007ffff64c18fd in poll () from /lib64/libc.so.6
#1 0x00007ffff7fb5fc1 in ?? () from /lib64/libusb-1.0.so.0
#2 0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#3 0x00007ffff64ccc7f in clone () from /lib64/libc.so.6
Thread 1 (Thread 0x7ffff7f9ab40 (LWP 2345)):
#0 0x00007ffff711b7f6 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1 0x0000000000408a4e in main (argc=1, argv=<optimized out>) at miner.c:13859
Could be an issue with gentoo specific libraries that bfgminer relies on. Since this is a linux machine its easy to build the binaries...I would just do a custom compile on your system and see if that resolves the issue. |
|
|
|
OhGodAGod is sadly already taken. But I'm just a girl, nothing more.
Love your work ... when a pill for another Nvidia card (especially for GTX 1070) will be release ? Doubt that one will ever be released. The GTX 1070 doesn't have G5X memory and thus the injection doesn't work. Neither will it on any other non G5X card. The mining cards P104/102 already have this mod (FAW/RRD) so this tool only applies to the non mining G5X cards, which are 3 types..? What it does is, it accesses the memory block and injects those 2 changes. I've done this mod on the P104 when we first recieved the prototype months ago. It jumped from stock 28Mh to 36Mh with just those 2 changes. It's a nice little trick yes  You are just the guy who decided “not” to release it to anyone and force those to buy the absolute pieces of garbage that are the mining cards. Without letting people know (as I tried) that these mods can be given to any GDDR5X card. IE all of these cards are failed GTX 1080 and Failed GTX 1080TI that nvidia scrapped and that some company decided to buy those scraps and sell them to miners with 3 month warranty. Yeah what a dickhead , then he comes here to spout usless knowlege gtfo Eliovp you turned to the dark side use to be a nice guy , and fuck u and you doubts who knows what this awesome team will come up with. Are you also absolutely kidding me? Useless info? I'm just stating facts here, giving away free info, isn't that what everyone wants? But yeah, you're only a nice guy when you often share stuff for free. Otherwise you're a part of the "dark side". It also of course doesn't help when some specific people spread fud about you, team up in little teams to spread more fud. Mostly is because they feel threatened though.. What they also fail to mention is how they even got the core/base info to even do their "little trick".. No, they didn't figure that out themselves.. It's funny how people see you as "awesome", "best there is", etc.. when you give out free stuff, my freakin signature is free stuff, and don't get me started about all the other things i've shared everywhere. The thing is, i've learned from my mistakes, people are almost all the same, will be your best friend as long as you give out free things. The attention you get, yeah, it's all nice, but doesn't pay my bills. The funny thing is, i was seriously considering sharing vega stuff, but this made me realize that i don't need all the attention, let others have that Thx for the wake-up call Marvell! PS: "Dickhead" Seriously Marvell? I haven't been active on forums for a long time, so i have no freaking idea what i could have said to upset you. I'm pretty sure some specific people spread some bullshit about me and you as well as a lot of others just accepted that bullshit because yeah, they give out free shit :p Karma will eventually win.. or my chatlogs Ye Eliovp you writing that you a nice guy but when i send you a pm messege with a help question you ingnored me at all, if you could even write smth like "sorry dude i cant help you" ok i will understand it , but as was mantion erlier by marvel you a scam dickhead, writing such big words like i did it erlier etc, with no prove like this good guys do from OhGod company, you a peace of scam. I asked you, i was ready to donate as much as you want for your work (in normal mesures) but no you didnt. If you prove your words i will take my words back, but for now i write my opinion about you. Thants exactly what im saying , he comes on here and brags about the fact he came up with this first and then on top of that denigrates the work these guys have done by saying , nah they cant do this they wont etc, just becuase u chose to give a finger to the community doesn’t mean everyone is like you. keep your secret mods Evilop .. if they even exist I don’t even mine eth nor have I tried this tool but I appreciate good work when I see it Stuff like this make me sad. People have forgotten what crypto is about, and its all greed and money now. At least my efforts and others with AMD is paying off, and is why they are releasing low level management tools that do all the mods a few select people having been using since Vega came out. |
|
|
|
D3 is not supported.  Yea ill add D3 support when I have time |
|
|
|
Got down to 625 watts set on freq 312
At 312 freq you can prob set the lowest voltage on all 4 chains (0xfe). |
|
|
|
I just installed the Windows 10 update 1803 and after install the Moonlander2 drivers did not work. In device manager it listed the Moonlanders but had a triangle. BFGMiner when run says "No devices found". I tried reinstalling them, removing them and reinstalling but to no avail. The driver Preinstaller program fails with an error. When I try to manually install the drivers, the error says INF file invalid. I downloaded the v6.7.5 version from the driver page and they worked! In device manager under COM ports it no longer lists them as Moonlander2 and instead lists them as Silicon Labs CP210x USB to UART Bridge (COMx). BFGimner now sees them Just a tip should you run into this. Bob Sounds like some driver signing issue with the new windows release. Im sure silicon labs will sort it out. |
|
|
|
|
Show Posts
