Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cant synchronyzation. Please return none AVX #1108

Open
Anidana007 opened this issue Mar 2, 2023 · 23 comments
Open

Cant synchronyzation. Please return none AVX #1108

Anidana007 opened this issue Mar 2, 2023 · 23 comments

Comments

@Anidana007
Copy link

Anidana007 commented Mar 2, 2023

Hello!

(shortly: please return support none AVX cpu's!)

In last two days after validation, my node have 3 mining penalty
image

today i found it and start do research

my node was stuck on 5671182 block

and in logs i see this
image

Community manager in discord say - there is bug becouse my cpu from 2007 (XEON E5450) not support AVX

i also have notebook with Atom x7 z8700, notebook from 2017, and i have again this problem too on this
image

you can see chat in discord about this problem https://discord.com/channels/634481767352369162/634481767843364866/1080733442427326564

so, Bus say "there is still hope, devs need to upgrade their runtime's dependency to the next version (which will also bring back support for ARM)"

i start writte this issue, and check consoles again.... my node (same node on notebook and pc - for checking) be in sychronize! start client for view.... yes,

BUT!

i check block in scan.idena and i see....
image

and my node again stuck, but on 5671548 block

i know - many people have this problem now. i do a big stake to my noob in fully fair i can do 3+ validations cusessful. but now i even cant sync and mining or liqudate personalyti without burning idenas

please, return support none avx cpu

@sidenaio
Copy link
Contributor

sidenaio commented Mar 2, 2023

Hi, I've built a node with wasmer 2.3.0, could you try to run this version?
https://github.com/idena-network/idena-go/releases/download/v1.0.2-rc0/idena-node-win-1.0.2-rc0.exe

@Anidana007
Copy link
Author

Anidana007 commented Mar 2, 2023

Hi, I've built a node with wasmer 2.3.0, could you try to run this version? https://github.com/idena-network/idena-go/releases/download/v1.0.2-rc0/idena-node-win-1.0.2-rc0.exe

on pc problem still here
image

@Anidana007
Copy link
Author

still on 1548 block

@Anidana007
Copy link
Author

Anidana007 commented Mar 2, 2023

on notebook

image

looks like for now problem solve for notebook, but i very want mine on my pc!! becouse its more online and more powerfull

@sidenaio
Copy link
Contributor

sidenaio commented Mar 2, 2023

Unfortunately, wasmer requires AVX or SSE 4.2. You can try to emulate AVX on your pc with sde-external.

@Anidana007
Copy link
Author

Unfortunately, wasmer requires AVX or SSE 4.2. You can try to emulate AVX on your pc with sde-external.

uh, its long page..... how to run it for try?

@Anidana007
Copy link
Author

Anidana007 commented Mar 2, 2023

Idena not will be run on none AVX cpu's?

@biterminator
Copy link

@sidenaio @aidenaio @midenaio @mbidenaio
Minimum specification for computer to run Idena v1 should be updated on Idena website.

@romestamo-flx
Copy link

I have the same problem since the update.
image
I don't know about AVX cpu, I'm not home right now.

@Anidana007
Copy link
Author

Anidana007 commented Mar 2, 2023

Unfortunately, wasmer requires AVX or SSE 4.2. You can try to emulate AVX on your pc with sde-external.

al teast i run it with console (with admin right ofcourse) but there some problem what i totaly not understand

image

i very hope devs do something and idena node again will be work

@Anidana007
Copy link
Author

al teast i run it with console (with admin right ofcourse) but there some problem what i totaly not understand

image

i google it, it becouse win7 (my os) not support sde

@Anidana007
Copy link
Author

Anidana007 commented Mar 4, 2023

i try new v1.0.2-rc1 .... it seem like everethyng ok now on my pc!! work fine
tthanks

@Anidana007
Copy link
Author

i have trouble again
image

@midenaio
Copy link
Member

midenaio commented Mar 4, 2023

@Anidana007 please try the new rc2 version with aarch64 support

@ligi
Copy link
Contributor

ligi commented Mar 4, 2023

also saw this error with rc1 - just updated to rc2 and do not see this error anymore. But might also be because I am in "8h mining penalty" again - let's see if it is still gone after the 8h

@Anidana007
Copy link
Author

@Anidana007 please try the new rc2 version with aarch64 support

thanks. i try it. for now - it works. i will see it. if some erors be again, i tell about it.

@sidenaio
Copy link
Contributor

sidenaio commented Mar 5, 2023

Rc1 and rc2 are the same, rc2 just has aarch64 build. Those builds will not help you, because you CPU without SSE 4.2. Probably wasmer has the possibility to support SSE 4.1.

It was just a luck that node was able to mine. There were no wasm transactions and node was able to mine until one wasm transction appeared.

@Anidana007
Copy link
Author

hmmm, maybe.... i still watch to node. still work fine.

@ligi
Copy link
Contributor

ligi commented Mar 5, 2023

Also works fine for me currently - which is a bit strange tbh. when rc2 just added another arch that I do not even use. But the mining penalty is over now and mining rewards came in.
Will keep an eye on it - but if it is really the case it will only fail when I need to process a special block - IMHO there should be code on startup that checks this case (fail early principle)

@Anidana007
Copy link
Author

...its eror again.. =((
image

@Anidana007
Copy link
Author

so, hardfork not be activated if this problem not be solvel?
image

@sidenaio
Copy link
Contributor

sidenaio commented Mar 7, 2023

@Anidana007, hardfork is already activated. It's votes of 1.0.0 nodes.

I've requested the support of SSE 4.1.

@Anidana007
Copy link
Author

......so, no more mining on sse.4.1?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

6 participants