Hi Andy,
It is very much stable, if you want to verify on existing hardware, you can install 20.04 OS and load the previous BRCM driver, works fine.
PID changing from 5840/41/43 is expected as per Hardware configuration, no issue about this, after FW upgrade, it will settle to 5843.
Thanks, Prafulla
On Wed, Jul 20, 2022 at 2:56 PM Andy Chi <email address hidden> wrote:
> ** Attachment added: "lsusb-brcm2.txt" > > https://bugs.launchpad.net/libfprint-2-tod1-broadcom/+bug/1981974/+attachment/5604292/+files/lsusb-brcm2.txt > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1981974 > > Title: > FP identify is not working with broadcom sensor on Jammy > > Status in libfprint-2-tod1-broadcom: > New > > Bug description: > Broadcom Jammy package is provided to canonical team (Andy), attached > the log file shows FP identify operation says that verification is > successful, but Login screen will NOT be unlocked. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/libfprint-2-tod1-broadcom/+bug/1981974/+subscriptions > >
-- Thanks, Prafulla Kota 9866544810
Hi Andy,
It is very much stable, if you want to verify on existing hardware, you can
install 20.04 OS and load the previous BRCM driver, works fine.
PID changing from 5840/41/43 is expected as per Hardware configuration, no
issue about this, after FW upgrade, it will settle to 5843.
Thanks,
Prafulla
On Wed, Jul 20, 2022 at 2:56 PM Andy Chi <email address hidden> wrote:
> ** Attachment added: "lsusb-brcm2.txt" /bugs.launchpad .net/libfprint- 2-tod1- broadcom/ +bug/1981974/ +attachment/ 5604292/ +files/ lsusb-brcm2. txt /bugs.launchpad .net/bugs/ 1981974 2-tod1- broadcom: /bugs.launchpad .net/libfprint- 2-tod1- broadcom/ +bug/1981974/ +subscriptions
>
> https:/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> FP identify is not working with broadcom sensor on Jammy
>
> Status in libfprint-
> New
>
> Bug description:
> Broadcom Jammy package is provided to canonical team (Andy), attached
> the log file shows FP identify operation says that verification is
> successful, but Login screen will NOT be unlocked.
>
> To manage notifications about this bug go to:
>
> https:/
>
>
--
Thanks,
Prafulla Kota
9866544810