Topic: S9 cards only run on older FW? BrainsOS fails on them?? (Read 503 times)

... ... ... except a few times where you have called me things like a racist and such ...

Years of abusing people? I have been here since 2011 and don't really post publicly for obvious reasons being an OG bitcoiner. I never insult I just state the facts and inform people about what I know and don't make statements about things I don't know. Spreading misinformation is not what I am about and you should try to have that mentality too. Seriously I think you need this mentality. Spreading misinformation can have negative consequences for both personal and business life. Misinformation is false or inaccurate information that is spread intentionally or unintentionally, and it can have serious consequences. In personal life, spreading misinformation can damage relationships and reputations. When people share misinformation with others, they may be seen as untrustworthy or unreliable, which can harm their personal relationships. Additionally, spreading misinformation can also cause confusion and misunderstandings, which can lead to conflicts and problems in personal life and I think this might be why you are always upset with me. In business life, spreading misinformation can also have negative consequences. Misinformation can damage a company's reputation and credibility, which can lead to lost customers and revenue. Additionally, spreading misinformation can also lead to legal problems if the misinformation is seen as deceptive or fraudulent. You do realize you work for a registered company and your actions are there actions.

Also yes you learned about the efuse from me that was when you first started to understand that it's not actually a fuse it's a key being signed for the SoC. I did not create this but I taught you about it young grasshopper. But that is not the point you could have learned it from Jesus it's just smoke up my ass anyways ahahaha.

It has nothing to do with running my firmware. Stop going off topic anyways you are the king of it. But to recap

Miner had S19 and wanted to run it off s17 control board. Solution is to flash s17 to stock s19 and now he can run it. The miner was now able to run his s19 and his problem was resolved. Also he was not able to run braiins or vnish so your welcome I helped support a potential client of yours. you are welcome.

Because according to you now i need "education". But what you have years doing is insulting and abusing others in this forum and you have stated countless times its the only reason you come here for.

Like i told you before, its not about being able to run your fw, no one cares about that. Yes, that efuse is for signed boot, no i didn't learn it from you, its all in your dreams, you think you made everything when you did nothing.

Yay you learned the term eFuse from me congrats. Also no that's not blocked. Firmware runs just fine off a locked control board. Our S19 firmware from early last year ran off locked control boards. Your firmware has the same bootloader method we used so what does that have to do with anything. Also that is not bricking a control board you idiot. Clearly you don't know what bricking a control board is vs signing an RSA key.....

Also no. That is not even remotely close. Antbuild didn't have an RSA key or eFuse to burn they hacked the shit out of the linux os to prevent  I rather not go into too much detail as this is how we got really popular in the early days by offering an anti-virus and a cleaning solution if a farm was infected with these types of malware but yeah they are really nasty and no very different than an eFuse as those control boards do not have the same SoC.

If you weren't so hostile and offensive I wouldn't mind educating you on these things. I think you forgot we started this industry and know a lot more than you probably think.

Yes, that is exactly how you call the people that follow your advice "dumb". And you are the one pretending to be a "professional" now, but you are always the same...

Of course you want them to be chained to you, it triggers the eFuse, its all about blocking the install of Braiins OS+. Basically a human (social engineered) variant of those old Russian/Chinese malware that did it to S9s with default passwords.

I come back here strictly to bother you.

No one bricked c52 board also you can't brick it with our firmware silly goose. Stop spreading lies. Only thing you can do is turn a 17 series xlinx into a 19 series. That is not bricking it that is locking the boot loader dumb dumb. You would know this if you actually played with these things except echo chambered your feelings.

Also you can't brick a control board by flashing the wrong bitmain firmware. You just need to flash the correct one. Your just making stuff up because it won't boot it if it's the wrong firmware. Go ahead try to flash bb firmware on a xilinx board watch as nothing happens.

Can you please dig up this post because it's kind of funny to see you talking about things without context.

Also why do you label it c52 etc. Xilinx, BB, Amlogic are the only 3 boards. There are variants of each but they are pretty much the exact same thing and work identical except for lower level driver controls on i/o.

You just said modding cgminer but not understanding the hardware. Explain to me how you make a driver.... you understand the hardware to do so.

Yes everyone does copy us. We have been around the longest and changelogs do not lie

Have nice day mr copy cay echo chamber meanie pants!

No your work is useless tuning in 3 days for a beagle bone and getting 30w/t at 110t lol. Sometimes copying people isn't the best route you should first understand the hardware and understand the science behind what we develop before copying it.

ps. you do realize your firmware violates a few things correct? No one talks about it because we don't care to bring it up and hurt your business.

You still infringe on cgminer, so there is nothing to say to the likes of you, except: cease and desist. For someone who "doesn't post here" you keep coming. Yes you have made people brick their C52 with that "advise" of yours. What you actually want is to trap people into your mod. No one cares if your illegal mod works with C52, you told them "they are the same", and someone believed in you and tried factory fw and bricked it thanks to you.

You do not understand the hardware because you never code for it. You are modding cgminer and add crap around it which in turn was modded by the manufacturer from who knows what code base (old ck or current kano?). That is why you are so ignorant. You pretend you are not vnish, but you talk like you are behind it. Who has been telling lies here? It is only you.

The sad thing is you keep saying everyone copies from you. That would be a super deadly trap, your work is useless AND illegal. America is the land of lawyers so someday someone will sue, especially if a public traded company makes the mistake of touching your "product".

You realize I have better things to do than be a fake user I don't even post on here anymore. You need to lay off the pipe. What's next I am frodo too ahahahah

It's not garbage they landed on the moon with less processing power than the BeagleBone. It's called efficient code kiddo. "true autotuning" You just make up words now. Also what cpu on these boards have so many cores it's arm architecture so you develop for the hardware at hand and walla no issues at all. You can't make cpu/ram hungry programs for a devboard that was made over 10 years ago. Also that statement is great because I have people leaving because your tuning takes days and breaks hardware and our tuning takes a fraction of the time but then again that's what happens when you try to copy paste someone else IP and then implement it wrong yet again.

C52 and C55 work fine what are you talking about. We support every control board. When do I ever tell people to install factory firmware on their miner we boot from the SD card and don't write to it to preserve warranty so that right there is how I know your lying. Just because you can't figure it out doesn't make it my problem. Also I think you forget we target different markets you target home miners while our average client is an industrial miner. Hence the reason we do a lot of the things we do. Also "I don't send people" all my coworkers are in Ukraine the majority don't speak English also I got banned from your group by one of your old mods because I muted them in my group for bothering customers.

I like how you skipped all the text I wrote you can't respond to  now sit boy

I knew it was you, you are always making fake users everywhere.

BeagleBone Black is garbage, period. Underpowered low ram single core cpu.  We do true autotuning and its multithreaded, you don't because you can't since its not your software. It is a sad thing you keep the lies up, this confuses the people that leave vnish for Braiins OS thinking your lies were true and are utterly wrong and we have to tell them again and again that, no, what vnish does has nothing to do with what we do.

Exactly like when you spread the lie about C52 being "the same" as C55 and have people bricking their control boards with x19 factory firmware. So my only word of advise is never trust anything coming from vnish/marc or whatever fake user of the day they decide to make (its simple: we don't send "people" to troll to their groups while they can't never stop from doing that).

The day you write your own mining software and remove cgminer, we can say something remotely resembling a "competition" can start. In the meantime, you have nothing. That is what i meant. Now get to work and remove cgminer if you don't want to be seen as a 3 person basement operation trolling/loling your poor misguided users forever.

I want you to think for a minute when the Vnish team grew or do you still think it's just the 3 of us in our basements like it was 5 years ago lol.

Also your comment about leeching work is quiet funny... I guess we must inspire you a lot to copy paste our features  I am sorry I know that upsets you but you are more fun than Kano.

But yes he is correct we created the feature back in the day that has limits of how high the temperature will get before the firmware will start to back itself down. Some others have copied it but it's okay I highly recommend you use it if you plan to play with firmware to protect your investment!

ps. Please stop spreading lies about beagle bone boards being under powered for tuning and not having enough ram.. I heard that one today in a chat that was forwarded to me and I laughed so hard. Explain how we tuned on an L3+ in a few hours from software we made 4 years ago on a miner that was far more difficult to tune.

You mean Bitmain makes it pretty clear, since you did nothing. In fact you are a mere vnish whitelabel and vnish didn't code the mining software so all you are doing is leeching the work of others by infringing cgminer's license.

Since we don't use cgminer, there is absolute zero correlation to any of the mods. bosminer may be inspired by cgminer, but that's about it. bosminer is conservative, if there are issues it stops using the hashboard instead of risking damage (unlike what others do). So yeah, its pretty easy to have a mild fault make bosminer not use a hashboard while bmminer (or a mod of it) continues to use it no matter what...

Yes the autotuning will try lower values but if you set a crazy high limit, it will try rising values and see if chips remain stable, since they won't it will keep lowering them down until they do. For an immersed S9 that is a tremendous waste of time, but it does work and i have seen it, took like a week to tune and it ended using like 1700W or so (set to 5000W). No, it didn't burn out since the tuner quickly noticed the chips were not responding regardless of the insane setting.

Unlike using manual settings where you can easily cause damage if you don't know what you are doing or blindly trust others "presets". Each hashboard is unique and a "preset" can only give sub-optimal results at best.

Just installed ours asic.to or vnish. We won't throw an error and will make it pretty clear why it's failing. Also our presets or where the tuning starts from are already pre known good configurations so when it starts tuning it's already starting from pretty solid settings.

Ok, then I stand corrected, as I said, I don't have enough experience with BO+, I was expecting it would do the same thing with Vnish in regards to tuning down the hashboard to get them to a stable state, since this isn't the case, i'd think more manual intervention is required by the user, so perhaps always start below stock power, so 1200w for S9 and then clim your way up.

With brains os+ it is different as far as my experience goes. If you set a power target that is to high (which was the default for my version) the boards will be overloaded and instantly fail. Brains will then only throw an error and never start to hash unless you lower the target.
Still the process how to fix it will stay the same.

I am not very familiar with BO+ tuning but I believe it's similar to vnish, on BO+ you set a power limit on your miner which the firmware will try to achieve either by underclocking or overclocking certain boards/chips individually, similar to Vnish if you set a target so high which one of the boards can't stand the firmware would start to ignore your "target" and slowly adjust the setting to the downside until all chips become stable.

So setting a high profile from the get-go is not a good idea, the miner could take forever to actually get to a stable state, the best approach would be setting a profile/power limit similar to the stock, so something like 14TH on Vnish, or 1250w on BO+, then check the chip's status, if they are happy with the setting for 2-3 hours, you can try another push, maybe 1350w or 15th, if the miner takes too long to finish tunning it's probably telling you that your miner's capabilities are way far below what you are asking.

So in the above example if the tuning takes too long, fall back to 1300W or 14.5th, if the miner is happy with 1350w or 15th and your PSU is capable and you want to push it, go 1450w/16th, despite having to monitor the miner for a few hours, this is a lot safer and faster than going to 16th/1450w straight, because if your mine can only do 13th/1200w it will take so many hours for the runner to step down from 16th/1450w and you will think that the firmware isn't working when in fact you are pushing your miner way too hard.

Also, I don't recall if there is a default setting for ASICBOOST on BO+ but on Vnish it comes disabled, so make sure you enable it before tuning.

Yes you can do this or start Auto Tune with a lower value like for example 1000 Watts for an S9 and than go up in 50 Watt steps to find out at what level the hashboards start to fail. In any case you should be careful not to push the miner to far.

Yeah if you auto tune with braiins it will hit boards up with high power then lower some board do not like that.

So do not auto tune

go manual set at freq 400 volts 8 or 8.1 or 8.2 or 8.3

When I flashed Brains Os+ I had the issue that there was a too high power setting in there as standard. With that high power setting my miner would not run, since it was simply a wrong setting.  When I put in the correct power setting everything worked correctly. So try to double check all values.

Did you read the guide carefully it seems you don't know how to read the guide.

The image file that you downloaded must be extracted and the bin that you see extracted including the other files must be moved to the SD card make sure it is well formatted before you copy-paste all extracted files to the SD card.

After that move, the JP4 and insert the SD card then turn on the miner and the led must be flashing until it stops remove the SD card and reconnect the miner to the Power supply.

Now after it is done download the firmware from Bitmain look for the 2016-2019 firmware and flash it through the WebGUI.

Thanks, but how do i use these files, i have had a play and looked for instructions but can not find any?

I can see it had a load of BIN files plus a large 4Gb image file?

I know how to flash via NAND/create image/Jumper 4 switch.

I am trying to downgrade as i have a lot of older FWs, mainly fixed frequency 550, 600, 650Mhz, plus the variable one. I also have an aftermarket FW with autotune function that is mainly used to use.

I can't find any intructions or process on how to downgrade?

I have a few cards here that i presume will work on the older/pre dated FW 2016-2019.

Cheers