Welcome to our peer-to-peer forums, where owners help owners. Need help now? Visit eSupport here.

English Community

Linux Operating SystemsOther Linux Discussions
All Forum Topics
Options

4 Posts

11-17-2019

Portugal

4 Signins

34 Page Views

  • Posts: 4
  • Registered: ‎11-17-2019
  • Location: Portugal
  • Views: 34
  • Message 31 of 63

Re: How To: Configure X1 Carbon Gen 7 on Debian (FingerPrint+4G Modem)

2019-12-21, 17:49 PM

I am not able to install the firmwire on my machine

 

[porfirior@porfirio-pc Transferências]$ fwupdmgr --version
client version: 1.3.5
compile-time dependency versions
        gusb:   0.3.1
        efivar: 37
daemon version: 1.3.5
[porfirior@porfirio-pc Transferências]$ fwupdmgr install cbe7b45a2591e9d149e00cd4bbf0ccbe5bb95da7-Synaptics-Prometheus_Config-0021.cab
Decompressing…           [***************************************]
No supported devices found
[porfirior@porfirio-pc Transferências]$ fwupdmgr install e8147f9845bcff8e405e0e046ebb1c6d465e839b-Synaptics-Prometheus-10.01.3073367.cab
Decompressing…           [***************************************]
No supported devices found
Reply
Options

1 Posts

12-21-2019

Austria

1 Signins

26 Page Views

  • Posts: 1
  • Registered: ‎12-21-2019
  • Location: Austria
  • Views: 26
  • Message 32 of 63

Re: How To: Configure X1 Carbon Gen 7 on Debian (FingerPrint+4G Modem)

2019-12-21, 22:06 PM
I had the same isue. After i updated to the last bios version 0.1.26, i was able to apply the update.
Reply
Options

55 Posts

10-15-2019

France

59 Signins

668 Page Views

  • Posts: 55
  • Registered: ‎10-15-2019
  • Location: France
  • Views: 668
  • Message 33 of 63

Re: How To: Configure X1 Carbon Gen 7 on Debian (FingerPrint+4G Modem)

2019-12-22, 21:05 PM

I have upgraded my Kernel to `5.2.0-0.bpo.3-amd641` in order to configure my microphone and fingerprint, is there a tutorial for debian user I can follow out there?

Reply
Options

55 Posts

10-15-2019

France

59 Signins

668 Page Views

  • Posts: 55
  • Registered: ‎10-15-2019
  • Location: France
  • Views: 668
  • Message 34 of 63

Re: How To: Configure X1 Carbon Gen 7 on Debian (FingerPrint+4G Modem)

2019-12-22, 22:53 PM

Hello, I wanted to install the fingerprint on my X1 Carbon Gen 7:

 

- I've upgraded my bios to 1.26

- I've upgraded my kernel to v3.3 using buster backports

- I've builded and installed from source https://gitlab.freedesktop.org/libfprint/libfprint - using the master branch

- I've builded and installed from source https://gitlab.freedesktop.org/libfprint/fprintd  - using the master branch (I also did configure with ./configure --prefix=/usr --enable-pam to configure fprintd as people here recommandation.)

- I've tried to upgrade fwupd from 1.25 to 1.35 but I got stuck trying to compile (/home/dka/workspace/github.com/fwupd/fwupd/build/../libfwupdplugin/fu-quirks.c:351: undefined reference to `xb_silo_query_full') so I sticked to fwupd 1.25.

 

A previous comment said it was not necessary to inject the two CAB if I understand correctly.

 

The bios upgrade was done with:

  

fwupdmgr enable-remote lvfs-testing
fwupdmgr get-devices
fwupdmgr refresh
fwupdmgr get-updates
fwupdmgr update
fwupdmgr disable-remote lvfs-testing

The BIOS got updated to v 1.16  after reboot

 

This is the status of my x1c7:

 

dka@dka:[~]: fwupdmgr --version
client version:	1.2.5
compile-time dependency versions
	gusb:	0.3.0
	efivar:	37
daemon version:	1.2.5
dka@dka:[~]: fwupdmgr get-devices
ThinkPad X1 Yoga 4th / Carbon 7th Thunderbolt Controller
  DeviceId:             088f17c8359de6372e576c4932bf358cafd80621
  Guid:                 c7920601-0cda-507f-851e-92229eb1d370
  Summary:              Unmatched performance for high-speed I/O
  Plugin:               thunderbolt
  Flags:                internal|updatable|supported|registered
  Vendor:               Lenovo
  VendorId:             TBT:0x0109
  Version:              43.00
  Icon:                 computer
  Created:              2019-12-23

20QDCTO1WW System Firmware
  DeviceId:             f09b748a98b31bb5c7c64d83f24ddbc80dff7c5f
  Guid:                 4bbc40fa-f81e-4206-bc70-a1f7b744d964
  Plugin:               uefi
  Flags:                internal|updatable|require-ac|supported|registered|needs-reboot
  Checksum:             SHA1(0f89a1a6872c74b3805d5125de142ee5c7b6ee82)
  Checksum:             SHA256(8384b12ac89dd5d35697587d0b84f90193d12b632b6674a137099d128d018b14)
  Version:              0.1.26
  VersionLowest:        0.0.1
  Icon:                 computer
  Created:              2019-12-23
  UpdateState:          success

UEFI Device Firmware
  DeviceId:             f5275562e72a2f6cb4b09e559ff4e2860eff55d8
  Guid:                 32c6986c-23ac-4dff-8d8b-d43a58ec48f7
  Plugin:               uefi
  Flags:                internal|updatable|require-ac|supported|registered|needs-reboot
  Version:              192.47.1524
  VersionLowest:        0.0.1
  Icon:                 audio-card
  Created:              2019-12-23

UEFI Device Firmware
  DeviceId:             c085a3cbf4dc1d60d110b7616816e2ffd279b64e
  Guid:                 f72e048b-65bd-4e71-9071-1ac7045223e5
  Plugin:               uefi
  Flags:                internal|updatable|require-ac|supported|registered|needs-reboot
  Version:              0.1.10
  VersionLowest:        0.1.10
  Icon:                 audio-card
  Created:              2019-12-23

UEFI Device Firmware
  DeviceId:             b596f8dec94a959248534b35641fe2341e27ed06
  Guid:                 9045ae09-34ab-46d6-826d-b02f859dd20b
  Plugin:               uefi
  Flags:                internal|updatable|require-ac|registered|needs-reboot
  Version:              1.0.8343
  VersionLowest:        0.0.1
  Icon:                 audio-card
  Created:              2019-12-23

UEFI Device Firmware
  DeviceId:             f61a138e8240c473a88d703babf7be5bc0e098e6
  Guid:                 db246b7d-a882-4e0e-984f-23ac1b0270db
  Plugin:               uefi
  Flags:                internal|updatable|require-ac|registered|needs-reboot
  Version:              0.73.8
  VersionLowest:        0.73.8
  Icon:                 audio-card
  Created:              2019-12-23

UEFI Device Firmware
  DeviceId:             97d441c3228fe8615f883b166a8809389803f9e2
  Guid:                 68d3b08f-6ed2-43ca-86f0-f1ad6e41b390
  Plugin:               uefi
  Flags:                internal|updatable|require-ac|registered|needs-reboot
  Version:              0.0.26403
  VersionLowest:        0.0.1
  Icon:                 audio-card
  Created:              2019-12-23

INTEL SSDPEKKF010T8L
  DeviceId:             3743975ad7f64f8d6575a9ae49fb3a8856fe186f
  Guid:                 79517f86-8df8-5d6e-a18b-33f0b36a78e9
  Guid:                 68db11e5-b0cf-5bc9-a94e-17e28496e505
  Guid:                 3f235826-4614-56f6-8fd4-b67b346882c9
  Guid:                 691bd9e3-7825-50b0-837e-2cfe70fe7e87
  Summary:              NVM Express Solid State Drive
  Plugin:               nvme
  Flags:                internal|updatable|require-ac|registered|needs-reboot
  Vendor:               Intel Corporation
  VendorId:             NVME:0x8086
  Version:              L12P
  Icon:                 drive-harddisk
  Created:              2019-12-23

dka@dka:[~]: lsusb | grep synaptic -i
Bus 001 Device 011: ID 06cb:00bd Synaptics, Inc. 
dka@dka:[~]: sudo dmidecode -t bios -q BIOS Information Vendor: LENOVO Version: N2HET43W (1.26 ) Release Date: 12/09/2019 Address: 0xE0000 Runtime Size: 128 kB ROM Size: 32 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 3.5"/720 kB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.26 Firmware Revision: 1.10 BIOS Language Information Language Description Format: Abbreviated Installable Languages: 1 en-US Currently Installed Language: en-US

When I run fprintd-list I have

 

dka@dka:[~]: fprintd-list dka
No devices found

 

I have tried to build the master on the 5 december 2019 state , I still have No devices found

 

Did I forgot anything?

 

EDIT

 

I have tried with the two provided cab and that is the result

dka@dka:[~/Downloads]: fwupdmgr install cbe7b45a2591e9d149e00cd4bbf0ccbe5bb95da7-Synaptics-Prometheus_Config-0021.cab
Decompressing…           [***************************************]
No supported devices found
dka@dka:[~/Downloads]: fwupdmgr install e8147f9845bcff8e405e0e046ebb1c6d465e839b-Synaptics-Prometheus-10.01.3073367.cab
Decompressing…           [***************************************]
No supported devices found
dka@dka:[~/Downloads]: fwupdmgr --version
client version:	1.2.5
compile-time dependency versions
	gusb:	0.3.0
	efivar:	37
daemon version:	1.2.5

@MarkRHPearson it is now Christmas, it would be nice to have a fully working Linux on my Lenovo X1 Carbon Gen 7. I feel like I am close but I don't know where to seek anymore.

Reply
Answer
Options

55 Posts

10-15-2019

France

59 Signins

668 Page Views

  • Posts: 55
  • Registered: ‎10-15-2019
  • Location: France
  • Views: 668
  • Message 35 of 63

Re: How To: Configure X1 Carbon Gen 7 on Debian (FingerPrint+4G Modem)

2019-12-23, 19:13 PM

Hello, for some reason my previous post was deleted so here it is again:

 

How I have tried to get fingerprint reader running?

 

Step 1 \ Upgrade fwupd to latest 1.35

 

I have tried to upgrade to latest but I failed to because of build errors I couldn't solved. I was not able to fix so I kept fwupd v1.25 for the rest, let me know if that's a requirement

 

This is how I tried to cimpile ^=1.35:

git clone git@github.com:fwupd/fwupd.git \
   && cd fwupd \
   && git submodule update --init --recursive \
   && meson build \
   && ninja -C build

ninja -C build produce errors such as:

  • undefined reference to xb_builder_source_ctx_get_bytes
  • argument builder: Unresolved type: 'JsonBuilder*'

This is the result of the logs:

Signing certificate...
[50/446] Linking target libfwupdplugin/libfwupdplugin.so.1.0.0.
FAILED: libfwupdplugin/libfwupdplugin.so.1.0.0 
cc  -o libfwupdplugin/libfwupdplugin.so.1.0.0 'libfwupdplugin/0205040@@fwupdplugin@sha/fu-archive.c.o' 'libfwupdplugin/0205040@@fwupdplugin@sha/fu-chunk.c.o' 'libfwupdplugin/0205040@@fwupdplugin@sha/fu-common.c.o' 'libfwupdplugin/0205040@@fwupdplugin@sha/fu-common-cab.c.o' 'libfwupdplugin/0205040@@fwupdplugin@sha/fu-common-guid.c.o' 'libfwupdplugin/0205040@@fwupdplugin@sha/fu-common-version.c.o' 'libfwupdplugin/0205040@@fwupdplugin@sha/fu-device-locker.c.o' 'libfwupdplugin/0205040@@fwupdplugin@sha/fu-device.c.o' 'libfwupdplugin/0205040@@fwupdplugin@sha/fu-dfu-firmware.c.o' 'libfwupdplugin/0205040@@fwupdplugin@sha/fu-firmware.c.o' 'libfwupdplugin/0205040@@fwupdplugin@sha/fu-firmware-common.c.o' 'libfwupdplugin/0205040@@fwupdplugin@sha/fu-firmware-image.c.o' 'libfwupdplugin/0205040@@fwupdplugin@sha/fu-hwids.c.o' 'libfwupdplugin/0205040@@fwupdplugin@sha/fu-ihex-firmware.c.o' 'libfwupdplugin/0205040@@fwupdplugin@sha/fu-io-channel.c.o' 'libfwupdplugin/0205040@@fwupdplugin@sha/fu-plugin.c.o' 'libfwupdplugin/0205040@@fwupdplugin@sha/fu-quirks.c.o' 'libfwupdplugin/0205040@@fwupdplugin@sha/fu-smbios.c.o' 'libfwupdplugin/0205040@@fwupdplugin@sha/fu-srec-firmware.c.o' 'libfwupdplugin/0205040@@fwupdplugin@sha/fu-udev-device.c.o' 'libfwupdplugin/0205040@@fwupdplugin@sha/fu-usb-device.c.o' -Wl,--no-undefined -Wl,--as-needed -shared -fPIC -Wl,--start-group -Wl,-soname,libfwupdplugin.so.1 -Wl,-z,relro -Wl,-z,defs -Wl,-z,now libfwupd/libfwupd.so.2.0.0 -Wl,--version-script,/home/dka/workspace/github.com/fwupd/fwupd/libfwupdplugin/fwupdplugin.map /usr/lib/x86_64-linux-gnu/libxmlb.so /usr/lib/x86_64-linux-gnu/libgio-2.0.so /usr/lib/x86_64-linux-gnu/libgobject-2.0.so /usr/lib/x86_64-linux-gnu/libglib-2.0.so /usr/lib/x86_64-linux-gnu/libgusb.so /usr/lib/x86_64-linux-gnu/libusb-1.0.so /usr/lib/x86_64-linux-gnu/libgudev-1.0.so -Wl,--export-dynamic /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so -pthread /usr/lib/x86_64-linux-gnu/libarchive.so /usr/lib/x86_64-linux-gnu/libjson-glib-1.0.so /usr/lib/x86_64-linux-gnu/libgcab-1.0.so -Wl,--end-group '-Wl,-rpath,$ORIGIN/../libfwupd' -Wl,-rpath-link,/home/dka/workspace/github.com/fwupd/fwupd/build/libfwupd  
/usr/bin/ld: libfwupdplugin/0205040@@fwupdplugin@sha/fu-quirks.c.o: in function `fu_quirks_convert_quirk_to_xml_cb':
/home/dka/workspace/github.com/fwupd/fwupd/build/../libfwupdplugin/fu-quirks.c:93: undefined reference to `xb_builder_source_ctx_get_bytes'
/usr/bin/ld: libfwupdplugin/0205040@@fwupdplugin@sha/fu-quirks.c.o: in function `fu_quirks_add_quirks_for_path':
/home/dka/workspace/github.com/fwupd/fwupd/build/../libfwupdplugin/fu-quirks.c:177: undefined reference to `xb_builder_source_add_adapter'
/usr/bin/ld: libfwupdplugin/0205040@@fwupdplugin@sha/fu-quirks.c.o: in function `fu_quirks_lookup_by_id':
/home/dka/workspace/github.com/fwupd/fwupd/build/../libfwupdplugin/fu-quirks.c:289: undefined reference to `xb_silo_query_first_full'
/usr/bin/ld: libfwupdplugin/0205040@@fwupdplugin@sha/fu-quirks.c.o: in function `fu_quirks_lookup_by_id_iter':
/home/dka/workspace/github.com/fwupd/fwupd/build/../libfwupdplugin/fu-quirks.c:351: undefined reference to `xb_silo_query_full'
collect2: error: ld returned 1 exit status
[59/446] Generating Fwupd-2.0.gir with a custom command.
g-ir-scanner: link: cc -o /home/dka/workspace/github.com/fwupd/fwupd/build/tmp-introspectl9xmlhz4/Fwupd-2.0 /home/dka/workspace/github.com/fwupd/fwupd/build/tmp-introspectl9xmlhz4/Fwupd-2.0.o -L. -Wl,-rpath,. -Wl,--no-as-needed -L/home/dka/workspace/github.com/fwupd/fwupd/build/libfwupd -Wl,-rpath,/home/dka/workspace/github.com/fwupd/fwupd/build/libfwupd -lfwupd -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lsoup-2.4 -ljson-glib-1.0 -lgio-2.0 -lgobject-2.0 -Wl,--export-dynamic -lgmodule-2.0 -pthread -lglib-2.0
libfwupd/fwupd-release.c:1537: Warning: Fwupd: fwupd_release_to_json: argument builder: Unresolved type: 'JsonBuilder*'
libfwupd/fwupd-device.c:1796: Warning: Fwupd: fwupd_device_to_json: argument builder: Unresolved type: 'JsonBuilder*'
ninja: build stopped: subcommand failed.

How can I pass the build from source of  fwupd latest version ?

$ fwupdmgr --version # curent version installed 
fwupdmgr --version
client version:	1.2.5
compile-time dependency versions
	gusb:	0.3.0
	efivar:	37
daemon version:	1.2.5
  • Operating system and version: Debian 10
  • How did you install fwupd (ex: from source, pacman, apt-get, etc): from source
  • Have you tried rebooting? yes
  • Are you using an NVMe disk? no
  • Is secure boot enabled (only for the UEFI plugin)? yes

 

Step 2 \ Upgrade bios to 1.26

 

I did it successfully upgrade my bios to 1.26 using:

 

fwupdmgr enable-remote lvfs-testing
fwupdmgr get-devices
fwupdmgr refresh
fwupdmgr get-updates
fwupdmgr update
fwupdmgr disable-remote lvfs-testing

 

 

Step 3 \ Upagrde Kernel to v5.3

 

I did it successfully upgrade the kernel using backport:

 

uname -a
Linux dka 5.3.0-0.bpo.2-amd64 #1 SMP Debian 5.3.9-2~bpo10+1 (2019-11-13) x86_64 GNU/Linux

 

Step 4 \ Build libfprint from source

 

I did successfully build test and install without any error, but I had to solve a bunch of dependencies first.

 

Step 5 \ Build fprintd from source

 

Same as libprint, no hassle, just many dependencies to solve first, I did build test and install without any error.

 

Note that I added --prefix=/usr --enable-pam to the configure step in order to respect the recommendation from this post.

 

Step 6 \ Test

 

 

$ lsusb  | grep Synaptic
Bus 001 Device 011: ID 06cb:00bd Synaptics, Inc. 

$ fwupdmgr --version
client version:	1.2.5
compile-time dependency versions
	gusb:	0.3.0
	efivar:	37
daemon version:	1.2.5

$  dmidecode -t bios -q
BIOS Information
	Vendor: LENOVO
	Version: N2HET43W (1.26 )
	Release Date: 12/09/2019
	Address: 0xE0000
	Runtime Size: 128 kB
	ROM Size: 32 MB
	Characteristics:
		PCI is supported
		PNP is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		Boot from CD is supported
		Selectable boot is supported
		EDD is supported
		3.5"/720 kB floppy services are supported (int 13h)
		Print screen service is supported (int 5h)
		8042 keyboard services are supported (int 9h)
		Serial services are supported (int 14h)
		Printer services are supported (int 17h)
		CGA/mono video services are supported (int 10h)
		ACPI is supported
		USB legacy is supported
		BIOS boot specification is supported
		Targeted content distribution is supported
		UEFI is supported
	BIOS Revision: 1.26
	Firmware Revision: 1.10

BIOS Language Information
	Language Description Format: Abbreviated
	Installable Languages: 1
		en-US
	Currently Installed Language: en-US

$ fwupdmgr get-devices
ThinkPad X1 Yoga 4th / Carbon 7th Thunderbolt Controller
DeviceId: 088f17c8359de6372e576c4932bf358cafd80621
Guid: c7920601-0cda-507f-851e-92229eb1d370
Summary: Unmatched performance for high-speed I/O
Plugin: thunderbolt
Flags: internal|updatable|supported|registered
Vendor: Lenovo
VendorId: TBT:0x0109
Version: 43.00
Icon: computer
Created: 2019-12-23

20QDCTO1WW System Firmware
DeviceId: f09b748a98b31bb5c7c64d83f24ddbc80dff7c5f
Guid: 4bbc40fa-f81e-4206-bc70-a1f7b744d964
Plugin: uefi
Flags: internal|updatable|require-ac|supported|registered|needs-reboot
Checksum: SHA1(0f89a1a6872c74b3805d5125de142ee5c7b6ee82)
Checksum: SHA256(8384b12ac89dd5d35697587d0b84f90193d12b632b6674a137099d128d018b14)
Version: 0.1.26
VersionLowest: 0.0.1
Icon: computer
Created: 2019-12-23
UpdateState: success

UEFI Device Firmware
DeviceId: f5275562e72a2f6cb4b09e559ff4e2860eff55d8
Guid: 32c6986c-23ac-4dff-8d8b-d43a58ec48f7
Plugin: uefi
Flags: internal|updatable|require-ac|supported|registered|needs-reboot
Version: 192.47.1524
VersionLowest: 0.0.1
Icon: audio-card
Created: 2019-12-23

UEFI Device Firmware
DeviceId: c085a3cbf4dc1d60d110b7616816e2ffd279b64e
Guid: f72e048b-65bd-4e71-9071-1ac7045223e5
Plugin: uefi
Flags: internal|updatable|require-ac|supported|registered|needs-reboot
Version: 0.1.10
VersionLowest: 0.1.10
Icon: audio-card
Created: 2019-12-23

UEFI Device Firmware
DeviceId: b596f8dec94a959248534b35641fe2341e27ed06
Guid: 9045ae09-34ab-46d6-826d-b02f859dd20b
Plugin: uefi
Flags: internal|updatable|require-ac|registered|needs-reboot
Version: 1.0.8343
VersionLowest: 0.0.1
Icon: audio-card
Created: 2019-12-23

UEFI Device Firmware
DeviceId: f61a138e8240c473a88d703babf7be5bc0e098e6
Guid: db246b7d-a882-4e0e-984f-23ac1b0270db
Plugin: uefi
Flags: internal|updatable|require-ac|registered|needs-reboot
Version: 0.73.8
VersionLowest: 0.73.8
Icon: audio-card
Created: 2019-12-23

UEFI Device Firmware
DeviceId: 97d441c3228fe8615f883b166a8809389803f9e2
Guid: 68d3b08f-6ed2-43ca-86f0-f1ad6e41b390
Plugin: uefi
Flags: internal|updatable|require-ac|registered|needs-reboot
Version: 0.0.26403
VersionLowest: 0.0.1
Icon: audio-card
Created: 2019-12-23

INTEL SSDPEKKF010T8L
DeviceId: 3743975ad7f64f8d6575a9ae49fb3a8856fe186f
Guid: 79517f86-8df8-5d6e-a18b-33f0b36a78e9
Guid: 68db11e5-b0cf-5bc9-a94e-17e28496e505
Guid: 3f235826-4614-56f6-8fd4-b67b346882c9
Guid: 691bd9e3-7825-50b0-837e-2cfe70fe7e87
Summary: NVM Express Solid State Drive
Plugin: nvme
Flags: internal|updatable|require-ac|registered|needs-reboot
Vendor: Intel Corporation
VendorId: NVME:0x8086
Version: L12P
Icon: drive-harddisk
Created: 2019-12-23

$ fprintd-list dka No devices found

 

It seems that even after building from source as recommended by MarkRHPearson then it is not recognized.

 

I also tried to rebuild fprintd using the version from the 5th december 2019 of the master branch, but didn't got any improvement.

 

I feel I am close, but can't solve it yet. Any idea on what is happening wrong?

 

Thanks for putting much effort in trying to make Linux a better place, I wish to all the Lenovo team and users a merry Christmas!

 

 

0 person found this solution to be helpful.

This helped me too

Reply
Options

8 Posts

12-18-2019

Poland

25 Signins

193 Page Views

  • Posts: 8
  • Registered: ‎12-18-2019
  • Location: Poland
  • Views: 193
  • Message 36 of 63

Re: How To: Configure X1 Carbon Gen 7 on Debian (FingerPrint+4G Modem)

2019-12-23, 20:04 PM

You need to have recent 1.3.5 version of fwupdmgr in order to install new firmware for Synaptics. It won't notice the new firmware otherwise and hence the device won't be discoverable by fprintd which is currently the case.

 

Regarding firmware build, I was able to build it successfully but hopefully you don't have to go through the whole building madness. The new fwupd is available on snapcraft, and since you're using debian you should be able to take full advantage of snaps. If you're not familiar with snaps yet, here is the list of commands you need :)

 

# as root
apt remove fwupd apt install snapd snap install fwupd

Once that's done and you verify the client/daemon verison is correct replay the fwupdmgr command suggested by dbao. Then provided building libfprint and fprintd went fine everything should be ok :)

Reply
Options

55 Posts

10-15-2019

France

59 Signins

668 Page Views

  • Posts: 55
  • Registered: ‎10-15-2019
  • Location: France
  • Views: 668
  • Message 37 of 63

Re: How To: Configure X1 Carbon Gen 7 on Debian (FingerPrint+4G Modem)

2019-12-23, 20:09 PM

Using the simple sid backport method I was able to build fwupd 1.3.5 and install it succesfully,

 

I then did :

 

fwupdmgr enable-remote lvfs-testing
fwupdmgr get-devices
fwupdmgr refresh
fwupdmgr get-updates
fwupdmgr update
fwupdmgr disable-remote lvfs-testing

and the firware got downloaded succesfully.

 

I am now seing my fingerprint:

 

dka@dka:[~/tmp/tmp2]: fprintd-list dka
found 1 devices
Device at /net/reactivated/Fprint/Device/0
Using device /net/reactivated/Fprint/Device/0
User dka has no fingers enrolled for Synaptics Sensors.

That's awesome. I cannot use it because I didn't found any way to use it.

 

It takes too much time to boot

Looking at /var/log/syslog, I have  

 

dka@dka:[~]: sudo cat /var/log/syslog  | grep fprint
Dec 23 22:08:40 dka dbus-daemon[850]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.589' (uid=10000 pid=9339 comm="fprintd-list dla ")
Dec 23 22:09:17 dka systemd[1]: fprintd.service: Succeeded.
Dec 23 22:19:45 dka dbus-daemon[915]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.42' (uid=10000 pid=2349 comm="fprintd-verify ")
Dec 23 22:19:45 dka fprintd[2350]: Device responded with error: 789
Dec 23 22:19:45 dka fprintd[2350]: Ignoring device due to initialization error: The driver encountered a protocol error with the device.
Dec 23 22:20:15 dka systemd[1]: fprintd.service: Succeeded.
Dec 23 22:20:18 dka dbus-daemon[915]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.47' (uid=10000 pid=2363 comm="fprintd-list dka ")
Dec 23 22:21:07 dka systemd[1]: fprintd.service: Succeeded.

While the PC was waiting for me to authenticate, the fingerprint took from 22:19:01 to 22:21:07, so almost 2 minutes to be ready for usage.

 

There is not GUI on Debian 10

I have checked but I didn't find any GUI for finger print on Debian buster, making it harder to configure.

 

All I could find was fingerprint-gui v1.09, I did the instruction for Debian explained in this tutorial https://www.addictivetips.com/ubuntu-linux-tips/enable-fingerprint-scanner-support-on-linux/

 

After launching the sofware as me or as root, I have "No Devices Found!" on the list on finger print device, I can't choose a device and click next so it is useless and I have installed that ugly remote ppa.

 

Apparently there is some pam configuration

 

Someone recommended me to configure my /etc/pam.d/common-auth like follow so I can use the fingerprint for login, su, sudo, ... :

 

#
# /etc/pam.d/common-auth - authentication settings common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of the authentication modules that define
# the central authentication scheme for use on the system
# (e.g., /etc/shadow, LDAP, Kerberos, etc.).  The default is to use the
# traditional Unix authentication mechanisms.
#
# As of pam 1.0.1-6, this file is managed by pam-auth-update by default.
# To take advantage of this, it is recommended that you configure any
# local modules either before or after the default block, and use
# pam-auth-update to manage selection of other modules.  See
# pam-auth-update(8) for details.

# here are the per-package modules (the "Primary" block)
auth	[success=3 default=ignore]	pam_fprintd.so max_tries=1 timeout=10
auth	[success=2 default=ignore]	pam_unix.so nullok_secure
auth	[success=1 default=ignore]	pam_ldap.so minimum_uid=10000 use_first_pass
# here's the fallback if no module succeeds
auth	requisite			pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
auth	required			pam_permit.so
# and here are more per-package modules (the "Additional" block)
auth	optional			pam_cap.so 
# end of pam-auth-update config

I needed to add at the bottom of /etc/pam.d/common-auth:

 

# and here are more per-package modules (the "Additional" block)
auth	optional			pam_cap.so 

And at the top of /etc/pam.d/common-auth (with success the proper ordering, here it's 3)

auth	[success=3 default=ignore]	pam_fprintd.so max_tries=1 timeout=10

 

Nothing worked

 

Of course, that didn't work, and the fingerprint still takes over 2 minutes to boot, so it doesn't make the testing any easier.

 

Did anybody experience such an issue? How can I tell the fingerprint reader to boot before and how can I use it for case such as :

 

- login

- root login

- me login

- sudo

- su

Reply
Options

191 Posts

11-07-2009

United States of America

178 Signins

1359 Page Views

  • Posts: 191
  • Registered: ‎11-07-2009
  • Location: United States of America
  • Views: 1359
  • Message 38 of 63

Re: How To: Configure X1 Carbon Gen 7 on Debian (FingerPrint+4G Modem)

2019-12-23, 21:45 PM

I believe fprintd v2 has pam bug, not firmware. GDM cannot communicate with fp at all.

Reply
Options

55 Posts

10-15-2019

France

59 Signins

668 Page Views

  • Posts: 55
  • Registered: ‎10-15-2019
  • Location: France
  • Views: 668
  • Message 39 of 63

Re: How To: Configure X1 Carbon Gen 7 on Debian (FingerPrint+4G Modem)

2019-12-23, 22:01 PM

I am looking for a way to use the fingerprint in a real case (sudo, su, login, etc...)

 

I am able to use the fingerprint from the command line but fingerprint-gui was the only option proposed on the web and it was on ppa which is kind of bad.

 

How can I use the finger print for authenticating somwhere (except against fprintd-verify)? 


Still running on Debian 10.

Reply
Options

55 Posts

10-15-2019

France

59 Signins

668 Page Views

  • Posts: 55
  • Registered: ‎10-15-2019
  • Location: France
  • Views: 668
  • Message 40 of 63

Re: How To: Configure X1 Carbon Gen 7 on Debian (FingerPrint+4G Modem)

2019-12-23, 23:09 PM
I finally found how to use it after having the firmware properly installed. You need to apt-get install libpam-fprintd and then edit /etc/pam.d/common-auth and add

auth [success=3 default=ignore] pam_fprintd.so max_tries=1 timeout=10

This will use the fingerprint for login and bash login.

That's awesome to get it run for christmas eve. I am happy to have the best laptop in the wolrd running linux at 100%.

Thanks all for the amazing job.
Reply
Forum Home

Community Guidelines

Please review our Guidelines before posting.

Learn More

Check out current deals!

Go Shop
X

Save

X

Delete

X

No, I don’t want to share ideas Yes, I agree to these terms