servicelesno.blogg.se

Lenovo x1 carbon fingerprint reader not working
Lenovo x1 carbon fingerprint reader not working












lenovo x1 carbon fingerprint reader not working

Login (You may not need this if you are using i3wm): auth sufficient pam_thinkfinger.soĪuth required pam_unix.so use_first_pass nullok_secure Entries in each of these files are listed below The files being System_Local_Login, Su, Sudo, i3lock. Obviously, you will need to sudo to make the changes. you need to edit the following files in /etc/pam.d/. If you are an alias to the “root”, then you will need to enrol the root’s fingerprint and verify it using fprintd. Also, I’ve used I3Lock instead of xscreensaver. I think I preferred i3lock and Fprint because they seemed to be much easier to configure.Īfter you have enrolled and verified your fingerprint using fprint. I’ve used Fprint (instead of ThinkFinger) to lock and unlock my screen. ↳ ThinkPad X20/X30/X40 Series incl.This post is just a scribble for me to remember how to configure and use the fingerprint reader on my X1-Carbon more effectively with Arch-Linux.↳ ThinkPad SL and L Series until L420/L520.↳ Forum Notices, Questions and Suggestions.FORUM RULES, HOW-TOs and FREQUENTLY ASKED QUESTIONS.And since the drivers are the same for thousands of other units-that means hardware failures. I think most o fus have been around computers long enough to know, they don't just "stop" for no good reason. I'm starting to wonder if I should send it to Camp Lenovo and tell them to either find the cold solder joints, or replace the hardware wholesale. And tonight, after I turned it back on (with the Lenovo control applet) it turned itself back OFF again after a few minutes. But once in a while-when the computer wakes again, the WiFi radio is OFF. It was ON when suspended (by F4 or cover close) and normally comes back ON with the connection intact. Tonight, the fingerprint reader is working fine-but the WiFi radio has played hide and seek a couple of times this week. No reason to think the OS wasn't detecting it, after all, the OS knew it was there after the cold boot, why should it "lose" the device during operations-unless there was a driver failure, or something similar? Last week the computer pulled that trick AGAIN for the first time in a long time. I've worked with these connectors before. I opened the wrist rest 6? 8? weeks ago to "de-creak" it and checked the connection at that time-solid. Thanks, but it was and presumably still is firmly attached.














Lenovo x1 carbon fingerprint reader not working