SliTaz Forum

Libbit4xpki strange problem

(5 posts) (3 voices)

• Started 7 months ago by gibor
• Latest reply from BradleyMcLean245
• This topic is not a support question

Tags:

No tags yet.

1. 

   gibor
   

   offline

   Moderator

   Hi, the drivers for the CNS reader in Italy are provided here
   https://swdownload1.agenziaentrate.gov.it/pub/sanita/libbit4xpki-idemia-amd64.1.4.10-647.deb
   Well on the same S.O. But run with two different kernels (both 64bit) in one case it works, in the other it doesn't.
   I can't figure out where the incompatibility (cannot execute binary file: Invalid executable format) might originate.
   I am attaching some command line tests, in the hope that someone can suggest me what I am doing wrong in the kernel configuration
   libbit4xpki-idemia-amd64.1.4.10-647.deb
   kernel that does not run
   tux@slitaz:~$ uname -a
   Linux slitaz 5.15.0-slitaz64 #10 SMP Wed Dec 27 19:16:15 CET 2023 x86_64 GNU/Linux

   tux@slitaz:~$ file /usr/share/bit4id/x/pinmanager/bin/python.exe
   /usr/share/bit4id/x/pinmanager/bin/python.exe: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=f6eef9ea560556194c72caf9c3ccaf889dbdc106, stripped

   tux@slitaz:~$ /usr/share/bit4id/x/pinmanager/bin/python.exe -m crtmgr.gui
   -sh: /usr/share/bit4id/x/pinmanager/bin/python.exe: cannot execute binary file: Formato eseguibile non valido

   bash /usr/share/bit4id/x/pinmanager/bin/python.exe -m crtmgr.gui
   /usr/share/bit4id/x/pinmanager/bin/python.exe: /usr/share/bit4id/x/pinmanager/bin/python.exe: impossibile eseguire il file binario
   -----------------------------------------------------------------------------------------------------------------------
   kernel that works
   tux@slitaz:~$ uname -a
   Linux slitaz 3.16.55-slitaz64 #8 SMP Fri Mar 25 18:55:30 CET 2022 x86_64 GNU/Linux
   tux@slitaz:~$ file /usr/share/bit4id/x/pinmanager/bin/python.exe
   /usr/share/bit4id/x/pinmanager/bin/python.exe: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=f6eef9ea560556194c72caf9c3ccaf889dbdc106, stripped
   tux@slitaz:~$ /usr/share/bit4id/x/pinmanager/bin/python.exe -m crtmgr.gui
   Traceback (most recent call last):
   File "src\crtmgr\util.py", line 225, in <module>
   File "/usr/local/lib/python2.7/logging/handlers.py", line 118, in __init__
   File "/usr/local/lib/python2.7/logging/handlers.py", line 65, in __init__
   File "/usr/local/lib/python2.7/logging/__init__.py", line 893, in __init__
   File "/usr/local/lib/python2.7/logging/__init__.py", line 912, in _open
   IOError: [Errno 2] No such file or directory: '/4log/crtmgr.log'
   INFO:crtmgr.log:Log started...
   “
   tux@slitaz:~$
   Executed correctly!

   -------------------------------------------------------------------------

   Italiano

   Salve, i driver per il lettore CNS in Italia vengono forniti qui
   https://swdownload1.agenziaentrate.gov.it/pub/sanita/libbit4xpki-idemia-amd64.1.4.10-647.deb
   ebbene sullo stesso S.O. Ma eseguito con due kernel diversi (entrambi a 64bit) in un caso funziona, nell'altro no.
   Non riesco a capire dove possa avere origine l'incompatibilità (cannot execute binary file: Formato eseguibile non valido)
   vi allego alcuni test da riga di comando, nella speranza che qualcuno mi possa suggerire cosa sbaglio nella configurazione del kernel
   libbit4xpki-idemia-amd64.1.4.10-647.deb
   kernel che non esegue
   tux@slitaz:~$ uname -a
   Linux slitaz 5.15.0-slitaz64 #10 SMP Wed Dec 27 19:16:15 CET 2023 x86_64 GNU/Linux

   tux@slitaz:~$ file /usr/share/bit4id/x/pinmanager/bin/python.exe
   /usr/share/bit4id/x/pinmanager/bin/python.exe: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=f6eef9ea560556194c72caf9c3ccaf889dbdc106, stripped

   tux@slitaz:~$ /usr/share/bit4id/x/pinmanager/bin/python.exe -m crtmgr.gui
   -sh: /usr/share/bit4id/x/pinmanager/bin/python.exe: cannot execute binary file: Formato eseguibile non valido

   bash /usr/share/bit4id/x/pinmanager/bin/python.exe -m crtmgr.gui
   /usr/share/bit4id/x/pinmanager/bin/python.exe: /usr/share/bit4id/x/pinmanager/bin/python.exe: impossibile eseguire il file binario

   kernel che funziona
   tux@slitaz:~$ uname -a
   Linux slitaz 3.16.55-slitaz64 #8 SMP Fri Mar 25 18:55:30 CET 2022 x86_64 GNU/Linux
   tux@slitaz:~$ file /usr/share/bit4id/x/pinmanager/bin/python.exe
   /usr/share/bit4id/x/pinmanager/bin/python.exe: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=f6eef9ea560556194c72caf9c3ccaf889dbdc106, stripped
   tux@slitaz:~$ /usr/share/bit4id/x/pinmanager/bin/python.exe -m crtmgr.gui
   Traceback (most recent call last):
   File "src\crtmgr\util.py", line 225, in <module>
   File "/usr/local/lib/python2.7/logging/handlers.py", line 118, in __init__
   File "/usr/local/lib/python2.7/logging/handlers.py", line 65, in __init__
   File "/usr/local/lib/python2.7/logging/__init__.py", line 893, in __init__
   File "/usr/local/lib/python2.7/logging/__init__.py", line 912, in _open
   IOError: [Errno 2] No such file or directory: '/4log/crtmgr.log'
   INFO:crtmgr.log:Log started...
   “
   tux@slitaz:~$
   Eseguito correttamente!

   Posted 7 months ago #
2. 

   gibor
   

   offline

   Moderator

   Risolto cambiando la versione in Bit4id_AOC_Middleware
   https://cdn.bit4id.com/es/AOC/middleware/Bit4id_AOC_Middleware.zip

   Credo che il problema precedente sia legato al python incorporato che è in versione a 32bit. Non riesco a capire lo stesso come mai sia eseguito correttamente con un kernel, visto che il sistema non è assolutamente un multilib.
   

   Attachments

   1. 2024-02-11_2041.jpg (67.6 KB, 93 downloads) 7 months old

   Posted 7 months ago #
3. 

   Rantanplan
   

   offline

   Member

   Bonjour Gibor,
   J'ai comparé les répertoires /usr/lib/python2.7/site-packages/keybinder des versions rolling et current.

   Le fichier _keybinder.la n'est pas dans la version current.

   Je ne sais pas si ça aide.
   Et je suppose que tu as déjà noté cette différence.

   Bon courage.

   ------------------Italiano----------------------

   Ciao Gibor,

   Ho confrontato le directory /usr/lib/python2.7/site-packages/keybinder della versione rolling e della current.

   Il file _keybinder.la non è presente nella versione current.

   Non so se questo può essere d'aiuto.
   Immagino che abbiate già notato questa differenza.

   Buona fortuna.

   Posted 7 months ago #
4. 

   gibor
   

   offline

   Moderator

   Per eseguire un binario a 32bit con un kernel a 64bit, sembra che debba per forza essere presente nel config file questa voce
   CONFIG_IA32_EMULATION=y
   appena posso proverò a ricompilarlo, visto che i kernel di slitaz ufficiali non mi supportano questo tipo di hardware.

   @Rantanplan
   Tutte le versioni di slitaz (per adesso) sono a 32bit. Alcune chiamate a 64 hanno solo il kernel a 64bit, ma la distribuzione rimane per intero a 32.
   -------------------------------------------------------------------------
   To run a 32bit binary with a 64bit kernel, it seems that there has to be this entry in the config file
   CONFIG_IA32_EMULATION=y
   as soon as I can I'll try to recompile it, since the official slitaz kernels don't support this kind of hardware for me.

   @Rantanplan
   All versions of slitaz (for now) are 32bit. Some 64 calls have only the 64bit kernel, but the whole distribution remains at 32bit.

   Posted 7 months ago #
5. 

   BradleyMcLean245
   

   offline

   Member

   so complicated

   Posted 6 months ago #

RSS feed for this topic

Reply

You must log in to post.