controlvault2-nfc-enable
controlvault2-nfc-enable copied to clipboard
Ubuntu 22.10 on Latitude E7470 crashing
Hello, I've been using the plugin in an older version some time with older Ubuntu versions for the German identity card. I always had to enable the python script and disable it afterwards, because a removal of the card wasn't detected. That wasn't perfect, but it worked. I installed a newer system on a fresh hard drive and wanted to get the NFC reader working again, but this time I can't get it working at all. Using pcsc_scan shows me a German identity card and I have to turn the reader off and on to recognize a card as before. But using an app "AusweisApp2" for authentication with the NFC card, the reader seems to crash. It looks working but nothing happens. I'm not able to interact by the python script anymore, before I interrupt the waiting process. And the ready gets really warm. After some waiting I'm able to turn it off again using the python script.
Is there any possibility to debug this behaviour? Is there a specific firmware recommend?
This is lspci of my reader:
Bus 001 Device 032: ID 0a5c:5834 Broadcom Corp. 5880
Thank you!
But using an app "AusweisApp2" for authentication with the NFC card, the reader seems to crash. Could you confirm that it works on Windows? Have you tried ./nfc.py reset before enabling the card reader?
Is there a specific firmware recommend? I'd say "take the latest firmware" from Dell site.
Is there any possibility to debug this behaviour? Try pcsc-spy first: https://manpages.ubuntu.com/manpages/focal/man1/pcsc-spy.1.html There is also a "Log" section on the official PCSClite site: https://pcsclite.apdu.fr/
Beside that dumping the USB traffic between the application and the device should be possible. Windows version of the "illustrated dumping guide" would be this one: https://desowin.org/usbpcap/tour.html For Linux it's this one: https://wiki.wireshark.org/CaptureSetup/USB#linux
I would guess there might be some problems within the PCSC (or some hardware quirks that might need to be worked around) or some firmware upgrade changed the reader's behavior when it comes to card data routing.