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

202 Posts

11-07-2009

United States of America

190 Signins

1404 Page Views

  • Posts: 202
  • Registered: ‎11-07-2009
  • Location: United States of America
  • Views: 1404
  • Message 21 of 63

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

2019-12-18, 21:23 PM

Build with the lastest libfprint and fprintd v2 will work without any problem. The trick part is fprintd v2 will install to /usr/local folder by default so you might need do some modification. It seems fprintd v1 is needed too because v2 does not have all files needed by pam.

 

Right now on my side you can register, scan etc but cannot log in with gdm. Maybe gdm is still looking for v1 files.

 

Reply
Options

8 Posts

12-18-2019

Poland

25 Signins

193 Page Views

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

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

2019-12-19, 10:19 AM

dbao Bypassing the default installation path is not a big issue, as it's always possible to use --prefix=/usr  option when running configure. I had missing policy errors when running fprintd installed in /usr/local. Have you been using the firmware capsule posted above? I'm still getting an error from device which sounds more like firmware issue rather than one from fprintd

Reply
Options

202 Posts

11-07-2009

United States of America

190 Signins

1404 Page Views

  • Posts: 202
  • Registered: ‎11-07-2009
  • Location: United States of America
  • Views: 1404
  • Message 23 of 63

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

2019-12-19, 17:18 PM

what I did was:

 

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

Reply
Options

8 Posts

12-18-2019

Poland

25 Signins

193 Page Views

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

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

2019-12-19, 17:26 PM

As it turned out the issue was me manually downloading and installing the firmware from .cab posted above and skipping config file. After that, everything stared working like a charm.

 

There is one caveat. When configuring fprintd the pam part can be skipped easily so you won't be able to harness full potential of fingerprint auth. In order to ensure pam_fprintd.so is built along with other stuff it's required to have libopamgt0 and libopamgt-dev packages installed, and then running configure with --enable-pam flag.

 

After that the library will be installed as well, and can be used to allow authentication using GDM, sudo etc. Now I can say everything is working on my X1 Carbon Gen 7 :)

Reply
Options

2 Posts

09-30-2019

Romania

9 Signins

140 Page Views

  • Posts: 2
  • Registered: ‎09-30-2019
  • Location: Romania
  • Views: 140
  • Message 25 of 63

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

2019-12-20, 15:41 PM

After checking this thread I've decided to give ubuntu another try. So far I've been running WSL2 and it was decent but it doesn't compare to the real deal.

 

The audio fix works great!

The 4G LTE Fix ( I have troubles with the instructions, I haven't managed singing the module + transferring it, maybe you guys have a set of instruction more clear? )

 

The fingerpint fix, I think I've reached a dead end atm.

adrian@adrian-home:~/setup/fprintd$ fprintd-list adrian
found 1 devices
Device at /net/reactivated/Fprint/Device/0
Using device /net/reactivated/Fprint/Device/0
User adrian has no fingers enrolled for Synaptics Sensors.

adrian@adrian-home:~/setup/fprintd$ fprintd-verify
Using device /net/reactivated/Fprint/Device/0
failed to claim device: Open failed with error: The driver encountered a protocol error with the device.

adrian@adrian-home:~/setup/fprintd$ fprintd-enroll adrian
Using device /net/reactivated/Fprint/Device/0
failed to claim device: Open failed with error: The driver encountered a protocol error with the device.

Have you guys encountered this?

Reply
Options

860 Posts

07-22-2019

Canada

532 Signins

6451 Page Views

  • Posts: 860
  • Registered: ‎07-22-2019
  • Location: Canada
  • Views: 6451
  • Message 26 of 63

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

2019-12-20, 20:00 PM

Just catching up with this thread....I'll try and field as many questions as I can

 

@justyn - I have been talking to Ubuntu about fingerprint support but don't have anything confirmed. Fingers crossed we can get it into that release.

@BigDong - I haven't started the conversation with Debian maintainers there. I really want to get the latest audio into debian first which is going to be a bit of a beast of an exercise. I'm holding off slightly until I have a better idea from the RedHat and Ubuntu teams how they approach the exercise - I personally use debian mostly, but getting things into the distro is still a challenge :)

@dominiksito - thanks for the list.

 - Video: Interesting on the video config, I'll have to look into that one as I've not seen issues in that area.

 - Audio:  there is a lot of progress and it's looking a lot more user friendly, but requires a 5.5 kernel. I was testing it this morning (latest kernel, alsa, ucm config, firmware etc) and I'm hoping to put together a guide to updating for those who like building their own kernel. On my todo list is to see if I can get this backported into some of the distro's now it's stabilising but I've got some work to do there first.

 - 4G modem: sadly I'm not allowed to comment on that one....legally Lenovo's recommendation is not to hack it as it's not been certified.

 

@dominiksito, dbao, goodless

 - Fingerprint reader: I need to return to this one, just not had time. It looks like a libfprint problem as dbao identifies and the firmware does work when you get it right...but I don't have any great insight yet. I'll have another stab at it soon but it may be after the christmas holidays at this point. 

Note Benjamin Berg, the maintainer has a copr repository with his builds which is useful if you're running Fedora:

https://copr.fedorainfracloud.org/coprs/benzea/fprintd

You may be able to take the libs from the location this points at and install them in another distro (be careful of locations)....I've not tried it myself and I'm dubious if it's a good idea.

 

Mark

 

 

Reply
Options

4 Posts

11-17-2019

Portugal

4 Signins

34 Page Views

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

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

2019-12-20, 22:01 PM

Seems like the fingerprint device is not present?

 

[porfirior@porfirio-pc ~]$ fwupdmgr get-devices
20QDCTO1WW
│
├─Thunderbolt Controller:
│     Device ID:           f084a6cda7a409d7f3d224f593e81eb86a919b9d
│     Summary:             Unmatched performance for high-speed I/O
│     Current version:     43.00
│     Vendor:              Lenovo (TBT:0x0109)
│     GUIDs:               c7920601-0cda-507f-851e-92229eb1d370
│                          70931c8b-ee82-52c9-bc3d-f85e64379bf9
│     Device Flags:        • Internal device
│                          • Updatable
│                          • Requires AC power
│                          • Supported on remote server
│                          • Device stages updates
│   
├─SAMSUNG MZVLB256HBHQ-000L7:
│     Device ID:           3743975ad7f64f8d6575a9ae49fb3a8856fe186f
│     Summary:             NVM Express Solid State Drive
│     Current version:     4M2QEXH7
│     Vendor:              Samsung Electronics Co Ltd (NVME:0x144D)
│     GUIDs:               6e54c992-d302-59ab-b454-2d26ddd63e6d
│                          47335265-a509-51f7-841e-1c94911af66b
│                          1b3b43f9-e0b0-5978-a89b-6f0866124233
│     Device Flags:        • Internal device
│                          • Updatable
│                          • Requires AC power
│                          • Needs a reboot after installation
│                          • Device is usable for the duration of the update
│   
├─System Firmware:
│     Device ID:           f09b748a98b31bb5c7c64d83f24ddbc80dff7c5f
│     Current version:     0.1.26
│     Minimum Version:     0.0.1
│     Vendor:              LENOVO
│     GUID:                4bbc40fa-f81e-4206-bc70-a1f7b744d964
│     Device Flags:        • Internal device
│                          • Updatable
│                          • Requires AC power
│                          • Supported on remote server
│                          • Needs a reboot after installation
│                          • Cryptographic hash verification is available
│                          • Device is usable for the duration of the update
│   
├─Touchpad:
│     Device ID:           2bd025a21741529fac39d6f088b9debfee7d4c9a
│     Current version:     1.3.3013337
│     Bootloader Version:  8.0
│     Vendor:              Synaptics Inc (HIDRAW:0x06CB)
│     GUIDs:               4150912a-f249-5f7e-bfa7-2d49e9c9de8c
│                          9c27eba7-52a4-5e6f-b28c-b5d9a3991e35
│                          19326b41-711b-5b64-89a0-6c86f3139bf1
│                          54ed5b90-c4f7-5551-a4cc-e6ac9957a4a8
│     Device Flags:        • Internal device
│                          • Updatable
│                          • Supported on remote server
│   
├─UEFI Device Firmware:
│     Device ID:           0ec6a2d51c2c55a649247d119ffb8e229168d6c9
│     Current version:     192.47.1524
│     Minimum Version:     0.0.1
│     GUID:                c3e4be53-e714-4ea1-bb9c-7fe13a98b556
│     Device Flags:        • Internal device
│                          • Updatable
│                          • Requires AC power
│                          • Supported on remote server
│                          • Needs a reboot after installation
│                          • Device is usable for the duration of the update
│   
├─UEFI Device Firmware:
│     Device ID:           c085a3cbf4dc1d60d110b7616816e2ffd279b64e
│     Current version:     0.1.10
│     Minimum Version:     0.1.10
│     GUID:                f72e048b-65bd-4e71-9071-1ac7045223e5
│     Device Flags:        • Internal device
│                          • Updatable
│                          • Requires AC power
│                          • Supported on remote server
│                          • Needs a reboot after installation
│                          • Device is usable for the duration of the update
│   
├─UEFI Device Firmware:
│     Device ID:           b596f8dec94a959248534b35641fe2341e27ed06
│     Current version:     1.0.8343
│     Minimum Version:     0.0.1
│     GUID:                9045ae09-34ab-46d6-826d-b02f859dd20b
│     Device Flags:        • Internal device
│                          • Updatable
│                          • Requires AC power
│                          • Needs a reboot after installation
│                          • Device is usable for the duration of the update
│   
└─UEFI Device Firmware:
      Device ID:           f61a138e8240c473a88d703babf7be5bc0e098e6
      Current version:     0.73.8
      Minimum Version:     0.73.8
      GUID:                db246b7d-a882-4e0e-984f-23ac1b0270db
      Device Flags:        • Internal device
                           • Updatable
                           • Requires AC power
                           • Needs a reboot after installation
                           • Device is usable for the duration of the update
Reply
Options

202 Posts

11-07-2009

United States of America

190 Signins

1404 Page Views

  • Posts: 202
  • Registered: ‎11-07-2009
  • Location: United States of America
  • Views: 1404
  • Message 28 of 63

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

2019-12-21, 1:46 AM

This post has nothing to do with Lenovo, 47CFR allow end user to modify radio without obtaining a license as long as output power is less than 1W:

 

Here is how to sign:

 

1) compile xmm7360_usb-master and install xmm7360_usb.ko
there is ssl error but kernel moduel is installed but will not work
checK:


modinfo -n xmm7360_usb
/lib/modules/zzzz/extra/xmm7360_usb.ko

 

zzzz is your kernel info, use same zzzz in step 2

 

2) sign kernel module xmm7360_usb.ko

create directory sign, enter sign, log as root
openssl req -new -x509 -newkey rsa:2048 -keyout MOK.priv -outform DER -out MOK.der -nodes -days 36500 -subj "/CN=xmm7360_usb/"
/usr/src/kernels/zzzz/scripts/sign-file sha256 ./MOK.priv ./MOK.der $(modinfo -n xmm7360_usb)


now inject sign key
mokutil --import MOK.der

this time will ask for a passwd, you can use any but need same passwd after reboot and import MOK key to BIOS

Reboot, after bluescreen, select import MOK, select MOK, view MOK and sign
now boot as normal

 

latest kernel does not need any modprobe or rc.local script to start. Reboot it will automatically enable modem.

 

Reply
Options

202 Posts

11-07-2009

United States of America

190 Signins

1404 Page Views

  • Posts: 202
  • Registered: ‎11-07-2009
  • Location: United States of America
  • Views: 1404
  • Message 29 of 63

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

2019-12-21, 1:50 AM
Follow this:

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

not just to inject cab
Reply
Options

8 Posts

12-18-2019

Poland

25 Signins

193 Page Views

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

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

2019-12-21, 9:46 AM

You can inject .CAB file but you have to inject both of them:

https://fwupd.org/lvfs/devices/com.synaptics.prometheus.firmware

https://fwupd.org/lvfs/devices/com.synaptics.prometheus.config

 

Regarding fprintd you have to make sure it's installed in /usr instead of /usr/local as default. On some distros you will have issues with device claiming and registering them for DBUS (due to missing policy files which are not in correct dir).

 

And again I strongly dissagree with having to compile 5.5 kernel in order to have sound support. Currently I cannot see any performance diff between linux and windows installation. 

 

Also I'm not sure what's the big deal about the LTE driver. If it's possible to run it earlier why not? Especially that releasing linux driver is probably not even in works?

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