Pages:
Author

Topic: Bytom Mining - ASIC algorithm now cracked by GPU miners? Big profits? - page 20. (Read 17651 times)

legendary
Activity: 2296
Merit: 1031
I had this working on HIVEos then suddenly after rebooting kept getting a runtime error... even after reformatting HIVEos, still get the same issue...


root@aa:~# panic: runtime error: invalid memory address or nil pointer dereference                                                                                                                                
        panic: runtime error: invalid memory address or nil pointer dereference                                                                                                                                    
[signal SIGSEGV: segmentation violation code=0x1 addr=0x330 pc=0x636a26]    

I am having the same issue..
Had it running on a 1080 ti Ethos box.

I rebooted and  now I get this error every time.

panic: runtime error: invalid memory address or nil pointer dereference
   panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x330 pc=0x636a26]

does anyone have any suggestions?

Yep, a few posts up... try setting up a swap file to add memory --OR-- add more physical RAM to your system.  Just google "Linux add swap file cli"  or "Linux Ubuntu swap file increase ram cli" or whatever your OS is if it isn't Ubuntu so you can add a swap file thus boosting your virtual memory.   It sounds like you are getting memory error from deficient memory resources allocated either physically or virtually.

in command line in Linux you can do the command "free" without quotations to see how much memory you have allocated and available.

and I'll just add... I wonder if the folks with 1080ti that are getting low hashrate might try again with more physical or virtual memory resources allocated.


Added 1GB swap file then 4GB to total 5gb and 8gb respectively, same issue. Very strange.

someone else had a similar issue and it was recommended to check version or download the most current version.  https://github.com/Bytom/bytom/issues/167

If it's not a version issue then maybe some incompatibility with your system
newbie
Activity: 9
Merit: 0
I had this working on HIVEos then suddenly after rebooting kept getting a runtime error... even after reformatting HIVEos, still get the same issue...


root@aa:~# panic: runtime error: invalid memory address or nil pointer dereference                                                                                                                                
        panic: runtime error: invalid memory address or nil pointer dereference                                                                                                                                    
[signal SIGSEGV: segmentation violation code=0x1 addr=0x330 pc=0x636a26]    

I am having the same issue..
Had it running on a 1080 ti Ethos box.

I rebooted and  now I get this error every time.

panic: runtime error: invalid memory address or nil pointer dereference
   panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x330 pc=0x636a26]

does anyone have any suggestions?

Yep, a few posts up... try setting up a swap file to add memory --OR-- add more physical RAM to your system.  Just google "Linux add swap file cli"  or "Linux Ubuntu swap file increase ram cli" or whatever your OS is if it isn't Ubuntu so you can add a swap file thus boosting your virtual memory.   It sounds like you are getting memory error from deficient memory resources allocated either physically or virtually.

in command line in Linux you can do the command "free" without quotations to see how much memory you have allocated and available.

and I'll just add... I wonder if the folks with 1080ti that are getting low hashrate might try again with more physical or virtual memory resources allocated.


Added 1GB swap file then 4GB to total 5gb and 8gb respectively, same issue. Very strange.
full member
Activity: 1179
Merit: 131
What people fail to realize is that this coin really isn't even that profitable for owners of the B3.  It only brings in about $10 a day.  The benefit of the B3 is that it was only $1600 and it uses 360 watts.  It would take 5 gtx 1080ti's to match the hashrate, making it more profitable to mine something else.  What would really do well would be the v100.
hero member
Activity: 756
Merit: 560
I feel like they're probably more powerful and they're redirecting the majority of the computational power of the device somewhere else but getting the miner to pay for the hardware an power they're siphoning off for personal profit.


When you have no understanding of something, jumping straight into a conspiracy theory is pretty ridiculous. All you would have to do is wireshark the network interface for 10 seconds to see its not sending out secret hashes elsewhere. Please do not fall into the tin foil idocy that pervades these forums nowadays. Try to make statements based on fact.


Heres a lil secret: The B3 uses the Sophon AI chip, which is a more general purpose chip than a standard ASIC and can be used for many other things.
legendary
Activity: 2296
Merit: 1031
I had this working on HIVEos then suddenly after rebooting kept getting a runtime error... even after reformatting HIVEos, still get the same issue...


root@aa:~# panic: runtime error: invalid memory address or nil pointer dereference                                                                                                                                
        panic: runtime error: invalid memory address or nil pointer dereference                                                                                                                                    
[signal SIGSEGV: segmentation violation code=0x1 addr=0x330 pc=0x636a26]    

I am having the same issue..
Had it running on a 1080 ti Ethos box.

I rebooted and  now I get this error every time.

panic: runtime error: invalid memory address or nil pointer dereference
   panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x330 pc=0x636a26]

does anyone have any suggestions?

Yep, a few posts up... try setting up a swap file to add memory --OR-- add more physical RAM to your system.  Just google "Linux add swap file cli"  or "Linux Ubuntu swap file increase ram cli" or whatever your OS is if it isn't Ubuntu so you can add a swap file thus boosting your virtual memory.   It sounds like you are getting memory error from deficient memory resources allocated either physically or virtually.

in command line in Linux you can do the command "free" without quotations to see how much memory you have allocated and available.

and I'll just add... I wonder if the folks with 1080ti that are getting low hashrate might try again with more physical or virtual memory resources allocated.
jr. member
Activity: 57
Merit: 5
I had this working on HIVEos then suddenly after rebooting kept getting a runtime error... even after reformatting HIVEos, still get the same issue...


root@aa:~# panic: runtime error: invalid memory address or nil pointer dereference                                                                                                                                
        panic: runtime error: invalid memory address or nil pointer dereference                                                                                                                                    
[signal SIGSEGV: segmentation violation code=0x1 addr=0x330 pc=0x636a26]    

I am having the same issue..
Had it running on a 1080 ti Ethos box.

I rebooted and  now I get this error every time.

panic: runtime error: invalid memory address or nil pointer dereference
   panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x330 pc=0x636a26]

does anyone have any suggestions?
member
Activity: 531
Merit: 29
newbie
Activity: 9
Merit: 0
I had this working on HIVEos then suddenly after rebooting kept getting a runtime error... even after reformatting HIVEos, still get the same issue...


root@aa:~# panic: runtime error: invalid memory address or nil pointer dereference                                                                                                                               
        panic: runtime error: invalid memory address or nil pointer dereference                                                                                                                                   
[signal SIGSEGV: segmentation violation code=0x1 addr=0x330 pc=0x636a26]   
member
Activity: 246
Merit: 24
hero member
Activity: 2548
Merit: 607
Wow, this could be potentially be the foundation of/for something groundbreaking in the battle against Bitmain dirty practices.
legendary
Activity: 2296
Merit: 1031
yea you mean swap area while installing linux, yes i did that..
its not working for you? whats the error its giving?

I haven't tried it yet.  Just wanted to know.  Thank you for your answer and clarification. 
jr. member
Activity: 504
Merit: 3
jr. member
Activity: 41
Merit: 1
We need an AMD dev to take a look at this.
newbie
Activity: 20
Merit: 0
So we can say this algo good for low - mid end gpu's not high end.
member
Activity: 195
Merit: 15
this is my result with GTX1080Ti (AIO)
135*3=400H/s @150W
newbie
Activity: 47
Merit: 0
yea you mean swap area while installing linux, yes i did that..
its not working for you? whats the error its giving?
legendary
Activity: 2296
Merit: 1031
ok im able to run it, 700+ hashes, with gtx 1070 rig
not much profitable i guess..
which pool its using? uupool right?

Did you have to up swap memory to make it work?  I guess doing a swap file is similar to adding physical or virtual memory as compared to windows.  If you did a swap file what size did you set?  Or... if that wasn't it... what did you have to do to get it to work?
newbie
Activity: 47
Merit: 0
ok im able to run it, 700+ hashes, with gtx 1070 rig
not much profitable i guess..
which pool its using? uupool right?
legendary
Activity: 2296
Merit: 1031
Anyone running the miner successfully on GTX1070 cards or above? Keep running into < unknown error%!(EXTRA string=xxx) > on SMOS.


Same error with 1080ti...

Sounds like a memory thing.  Have you tried allocating more virtual memory or adding more physical memory?  regarding virtual memory... Linux so not sure how to do that or if they do that in linux
jr. member
Activity: 41
Merit: 1
Does this work for 1070s and 1080s?
Pages:
Jump to: