Skip to content

138a:0090 is not working anymore on Ubuntu 20.04 #91

Open

Description

@kecsap

I get the "Exception: Failed: 04af" error when the python3-validity.service starts. Maybe the binary blobs need an update?
There is a newer driver at the Lenovo site:

https://download.lenovo.com/pccbbs/mobiles/n1cgn09w.exe

Activity

  1. Nyamkhuub commented on Aug 4, 2021

    @Nyamkhuub

    Interestingly, I can't enroll my fingerprint on Ubuntu 20.04. I got this exception:

    0401
    Traceback (most recent call last):
    File "/usr/lib/python-validity/dbus-service", line 161, in run
    sensor.enroll(usr, index, update_cb)
    File "/usr/lib/python3/dist-packages/validitysensor/sensor.py", line 828, in enroll
    self.create_enrollment()
    File "/usr/lib/python3/dist-packages/validitysensor/sensor.py", line 749, in create_enrollment
    assert_status(tls.app(pack('<BL', 0x69, 1)))
    File "/usr/lib/python3/dist-packages/validitysensor/util.py", line 12, in assert_status
    raise Exception('Failed: %04x' % s)
    Exception: Failed: 0401
    

    if you have solution for it, please let me know

  2. bookshiyi commented on Dec 4, 2021

    @bookshiyi

    same issue, Ubuntu 20.04 and 138a:0090.

    $ fprintd-enroll 
    Impossible to enroll: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available
    
  3. osbre commented on Apr 14, 2022

    @osbre

    Restarting it solved this problem:

    sudo systemctl restart python3-validity
  4. Nyamkhuub commented on Apr 22, 2022

    @Nyamkhuub

    Restarting it solved this problem:

    sudo systemctl restart python3-validity

    What is your laptop model?

  5. osbre commented on Apr 22, 2022

    @osbre

    Restarting it solved this problem:

    sudo systemctl restart python3-validity

    What is your laptop model?

    ThinkPad T470 with Elementary OS (Based on Ubuntu 20.04)

  6. ipstone commented on Nov 17, 2023

    @ipstone

    hey @osbre , can you confirm it's working for you /fingerprint setup/function properly? Somewhere else I read, it seems that this finger-printer reader isn't supported:
    #71

    I am using a thinkpad carbon x1 gen4, with also 138a:0090, I am on ubuntu 22.04, I am encountering the same problem as listed in this issue. Perhaps it works on elementary OS?

    thanks

  7. richri commented on Oct 13, 2025

    @richri

    @ipstone did you make any progress on this issue with your hardware? I have exactly the same Model (Thinkpad X1 Carbon Gen 4, fingerprint chip is 138a:0090).

    Like the op @kecsap, I also get the error "Exception: Failed: 04af"

    From what I see, the initialization process fails, when the Service ist startet. Even starting the initializer manually via validity-sensors-tools.initializer fails.

    I read somewhere, that for the 138a:0090 chips sometime a separate factory reset ist necessary, although it seems to me, that the initializer also issues this reset.

    # validity-sensors-tools.initializer 
    Found device <DEVICE ID 138a:0090 on Bus 001 Address 006>
    Downloading https://download.lenovo.com/pccbbs/mobiles/n1cgn08w.exe to extract 6_07f_Lenovo.xpfwext
    Extracting "Synaptics Metallica MOH Touch Fingerprint Reader Driver" - setup data version 5.5.7
     - "app/WBF_Drivers/6_07f_Lenovo.xpfwext"
    Done.
    Found firmware at /tmp/tmpfsou70ei/app/WBF_Drivers/6_07f_Lenovo.xpfwext
    The device will be now reset to factory and associated to the current laptop.
    Press Enter to continue (or Ctrl+C to cancel)...
    Opening device 0x90
    Factory reset...
    Sleeping...
    Pairing the sensor with device 20FCS0RG0E
    Opening device 0x90
    Initializing flash...
    Detected Flash IC: W25Q80B, 1048576 bytes
    Sleeping...
    Try 1 failed with error: Flash is already partitioned
    Opening device 0x90
    Initializing flash...
    Detected Flash IC: W25Q80B, 1048576 bytes
    Sleeping...
    

    What strikes me is the message about the flash already being partitioned. So in my eyes the firmware reset does not seem to work properly.

    I also tried resetting the fingerprint reader in BIOS. Also after that, the initializer complains about the already partitioned flash.

    Recently @uunicorn comited a version 0.15. In the comments in the files (a6bbc21) I see that it addresses partitioning for the 138a:0090 devices, but event using version 0.15 did not help in my case.

  8. rabbitambulance-ra commented on Mar 20, 2026

    @rabbitambulance-ra

    none of the above solutions worked for me, so i had my clanker sort this out for me earlier today on my X1 Yoga Gen 1 with a Synaptics Metallica 138a:0090: https://github.com/rabbitambulance-ra/libfprint/tree/vfs0090

    maybe this will help others. if it helps you, please thumbs up, heart, rocket, or whatever feelings you are feeling. if it doesn't, go ahead and thumbs down, or frown, or whatever helps make you feel better...

  9. kecsap commented on Jun 15, 2026

    @kecsap
    Author

    none of the above solutions worked for me, so i had my clanker sort this out for me earlier today on my X1 Yoga Gen 1 with a Synaptics Metallica 138a:0090: https://github.com/rabbitambulance-ra/libfprint/tree/vfs0090

    maybe this will help others. if it helps you, please thumbs up, heart, rocket, or whatever feelings you are feeling. if it doesn't, go ahead and thumbs down, or frown, or whatever helps make you feel better...

    Thank you very much! Actually, I hacked my device together for recent Ubuntu versions, but it stopped to work again a while ago. Now I updated Ubuntu 26.04 and with your repo and a simple install a few older-custombuilt packages, it started to work instantly. Lemme test now for a longer time.

  10. udaemon commented on Jul 8, 2026

    @udaemon

    @rabbitambulance-ra thanks for your work on this!
    I went through your github instructions several times but, unfortunately, I don't really know where to start.
    as I understand, I'm to gather the

    • product-name,
    • product-serial and
    • windows-sid

    to do the bootstrap-part.
    I'm not new to this problem and somehow even got it working, but this time I can't get any further.
    Can you please point me to how to get the needed information?
    Thanks!

  11. rabbitambulance-ra commented on Jul 8, 2026

    @rabbitambulance-ra

    I went through your github instructions several times but, unfortunately, I don't really know where to start.
    Can you please point me to how to get the needed information?

    @udaemon, it's been a while since I worked on this, so I'm going off somewhat fuzzy memory.

    The key thing, to the best of my recollection, is to get a Windows VM working in your Linux instace. From there you should be able to enroll fingerprints in Windows, and those will be written to the Synaptics Metallica onboard cryptographic hardware module storage. Test this in the Windows VM a few times and make sure it works. If it doesn't, then you have issues that I've not run into nor accounted for, so it makes no sense to keep going until you are able to sort that out.

    Once fingerprint reader is working under the Windows VM, you don't need to do anything to initialize and enroll on the Linux side. Just building python-validity should give you binaries which will allow you do CLI fingerprint read tests, as python-validity will be now reading the fingerprint data from the hardware, which was itself written during the Windows enrollment sesion.

    You'll want to try these and see if they are working post Windows VM-side enrollment:

    fprintd-list <user>
    fprintd-verify <user>
    

    Assuming CLI tests succeed, you are ready to configure your distro, shell, and X/Wayland and window manager to use fingerprint reader as auth method. If they fail, but Windows VM still works, then your hardware is sufficiently different to mine that additional debugging and updates might be needed to the underlying code.

    If, however, you are unable to get the fingerprint reader working in the Windows VM at all, then you may need to blow away the stored fingerprint data in the respective BIOS menu, and then try again in the Windows VM. (I had issues like this when I originally tried initializing Synaptics Metallica from the Linux side.)

    This is the best I can do with the hazy memory of all this. Hopefully it helps point you in the right direction.

  12. udaemon commented on Jul 8, 2026

    @udaemon

    thanks for your quick reply!
    as far as I can see the latest driver (n1cgn11w) is just a driver, i. e. not software. do you remember to have enrolled fingers with a special software by the manufacturer or did you use the windows "hello" function?
    unfortunately, the latter doesn't work here with the mentioned driver installed. ah, and I'm using a vm with windows 10. maybe I should try to upgrade (?).

  13. rabbitambulance-ra commented on Jul 8, 2026

    @rabbitambulance-ra

    @udaemon, I'm pretty sure I just used Windows Hello, and didn't need to download any special utilities and software beyond maybe the Synaptic Metallica Windows drivers.

    Just as an example, looking at Drivers & Software on Lenovo's Support site for my Yoga Gen 1 and filtering on Windows 11 x64, there's the "Synaptics Fingerprint Reader Driver for Windows 11 (Version 21H2 or later), 10 (Version 1709 or later) - ThinkPad" and no other special fingerprint reader software. This is almost certainly what I installed in the Windows VM (if anything at all) to get Hello enrollment to work.

    I would

    1. try upgrading the fingerrprint driver to latest,
    2. make sure you are forwarding all hardware peripherals from real hardware to the VM (requires an Extension Pack if using VirtualBox, enabling the USB Controller, and adding a USB Device Filter), and
    3. try erasing the fingerprint crypto module storage in BIOS.

    If none of those work, unfortunately I don't have any other clever suggestions for you.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions