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

Illegal instruction (virtualized CPU under Proxmox 8) #49

Closed
dawidthegreat opened this issue Apr 26, 2024 · 5 comments
Closed

Illegal instruction (virtualized CPU under Proxmox 8) #49

dawidthegreat opened this issue Apr 26, 2024 · 5 comments

Comments

@dawidthegreat
Copy link

Downloading https://ocrs-models.s3-accelerate.amazonaws.com/text-detection.rten...
Downloading https://ocrs-models.s3-accelerate.amazonaws.com/text-recognition.rten...
Illegal instruction

Running a jpg and get illegal instruction with the two files above. Have tried on more than one OC/Machine.

@robertknight
Copy link
Owner

What operating system and version are you using, and what CPU(s) do the machines have? I'm aware of a reported issue when running older versions of the library under Rosetta emulation on Apple Silicon. See robertknight/rten#35. The workaround for the moment is to compile natively for Arm.

@dawidthegreat
Copy link
Author

The OS's have been:

Ubuntu 24.04
Ubuntu 22.04
Centos 7

CPU's are virtualised on Proxmox 8. I'll try on a bare metal machine and see if I still get the error.

@dawidthegreat
Copy link
Author

It was fixed by changing the cpu type to host on proxmox virtualisation. It is based on qemu so should be applicable on machines using that. Result is perfect, the text recognition is superb.

@robertknight
Copy link
Owner

Thanks for the info. Ocrs uses AVX-2 / FMA instructions if available on x64 CPUs, so there might be an issue with misdetecting whether they are available in this virtualized environment.

@robertknight robertknight changed the title Illegal instruction Illegal instruction (virtualized CPU under Proxmox 8) Apr 26, 2024
@dawidthegreat
Copy link
Author

Possibly, it was on the default CPU which is X86-64-V2-AES, a virtualised CPU. By selecting host from the menu solved the issue I guess by pass through functionality.

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

No branches or pull requests

2 participants