Please add RTS5169 support in Ubuntu 22.04 (worked perfectly on 20.04 and 18.04)

For diagnostic purposes please proceed as follows:

Open a terminal window
Remove the device if connected and wait half a minute
plug in the device and wait half a minute

Issue the commands

sudo dmesg | tail
uname -a
lsb_release -crid

and copy/paste all output into your question document

jan@Ganymede:~$ sudo dmesg |tail
[sudo] password for jan:
[161287.686388] audit: type=1400 audit(1651615462.807:662):
apparmor="DENIED" operation="open" profile="snap.skype.skype"
name="/sys/devices/virtual/net/lo/speed" pid=4800 comm="skypeforlinux"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[161287.686392] audit: type=1400 audit(1651615462.807:663):
apparmor="DENIED" operation="open" profile="snap.skype.skype"
name="/sys/devices/pci0000:00/0000:00:1c.3/0000:03:00.0/net/enp3s0/speed"
pid=4800 comm="skypeforlinux" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
[161287.686394] audit: type=1400 audit(1651615462.807:664):
apparmor="DENIED" operation="open" profile="snap.skype.skype"
name="/sys/devices/virtual/net/tun0/speed" pid=4800 comm="skypeforlinux"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[162792.432538] usb 3-5: USB disconnect, device number 11
[162857.224396] usb 3-5: new high-speed USB device number 12 using xhci_hcd
[162857.407463] usb 3-5: New USB device found, idVendor=0bda,
idProduct=0165, bcdDevice=61.23
[162857.407467] usb 3-5: New USB device strings: Mfr=1, Product=6,
SerialNumber=3
[162857.407469] usb 3-5: Product: Smart Card Reader Interface
[162857.407470] usb 3-5: Manufacturer: Generic
[162857.407471] usb 3-5: SerialNumber: 20070818000000000
jan@Ganymede:~$ uname -a
Linux Ganymede 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC
2022 x86_64 x86_64 x86_64 GNU/Linux
jan@Ganymede:~$ lsb_release -crid
Distributor ID: Ubuntu
Description: Ubuntu 22.04 LTS
Release: 22.04
Codename: jammy
jan@Ganymede:~$

On Tue, May 3, 2022 at 11:41 AM Manfred Hampl <
<email address hidden>> wrote:

> Your question #701636 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/701636
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> For diagnostic purposes please proceed as follows:
>
> Open a terminal window
> Remove the device if connected and wait half a minute
> plug in the device and wait half a minute
>
> Issue the commands
>
> sudo dmesg | tail
> uname -a
> lsb_release -crid
>
> and copy/paste all output into your question document
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu/+question/701636
>
> You received this question notification because you asked the question.
>

The log shows that the device is recognized.

I suggest that you continue testing:

When you now insert the ID card and try accessing it, what output does

sudo dmesg | tail

show for that attempt?

If you still have an Ubuntu 20.04 system available, what output does "dmesg | tail" show for the two actions on the 20.04 system?

Yes, the device is recognized but it doesn't work.
I no longer have an ubuntu 20.04 but I do have a Debian Bullseye running
where this card reader still works.

On ubuntu 22.04, no LED is lit on the card reader.
On Debian Bullseye, a blue LED is lit when plugged in, and when I insert a
card, a red LED is lit on top to indicate a card is present.

This is the output on Debian:
jan@pcjan:~$ sudo dmesg | tail
[1293897.671365] usb 3-6: Product: Smart Card Reader Interface
[1293897.671368] usb 3-6: Manufacturer: Generic
[1293897.671371] usb 3-6: SerialNumber: 20070818000000000
[1294113.706087] usb 3-6: USB disconnect, device number 4
[1294136.513073] usb 3-6: new high-speed USB device number 5 using xhci_hcd
[1294136.696913] usb 3-6: New USB device found, idVendor=0bda,
idProduct=0165, bcdDevice=61.23
[1294136.696921] usb 3-6: New USB device strings: Mfr=1, Product=6,
SerialNumber=3
[1294136.696926] usb 3-6: Product: Smart Card Reader Interface
[1294136.696929] usb 3-6: Manufacturer: Generic
[1294136.696932] usb 3-6: SerialNumber: 20070818000000000
jan@pcjan:~$ sudo dmesg | tail
[1293897.671365] usb 3-6: Product: Smart Card Reader Interface
[1293897.671368] usb 3-6: Manufacturer: Generic
[1293897.671371] usb 3-6: SerialNumber: 20070818000000000
[1294113.706087] usb 3-6: USB disconnect, device number 4
[1294136.513073] usb 3-6: new high-speed USB device number 5 using xhci_hcd
[1294136.696913] usb 3-6: New USB device found, idVendor=0bda,
idProduct=0165, bcdDevice=61.23
[1294136.696921] usb 3-6: New USB device strings: Mfr=1, Product=6,
SerialNumber=3
[1294136.696926] usb 3-6: Product: Smart Card Reader Interface
[1294136.696929] usb 3-6: Manufacturer: Generic
[1294136.696932] usb 3-6: SerialNumber: 20070818000000000

first one is without my ID card plugged in, 2nd with.

On Wed, May 4, 2022 at 8:51 AM Manfred Hampl <
<email address hidden>> wrote:

> Your question #701636 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/701636
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> The log shows that the device is recognized.
>
> I suggest that you continue testing:
>
> When you now insert the ID card and try accessing it, what output does
>
> sudo dmesg | tail
>
> show for that attempt?
>
> If you still have an Ubuntu 20.04 system available, what output does
> "dmesg | tail" show for the two actions on the 20.04 system?
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu/+question/701636
>
> You received this question notification because you asked the question.
>

Is there anything in the dmesg log when you have the reader already connected and insert the ID card afterwards?

No, there's no output from dmesg following the insertion of my ID card.
I've checked multiple times using the 'sudo dmesg | tail' command, I've
tailed /var/log/messages and /var/log/syslog but the only thing I actually
see is when I plug in the device.
That being said, on Debian 11 (and previously Ubuntu 20.04) I can use the
card reader to authenticate using my ID. There's nothing wrong with the
hardware.

The card reader is only used for memory cards but to read a national ID
card. I don't know if that's the reason, just an FYI.

On Wed, May 4, 2022 at 6:21 PM Manfred Hampl <
<email address hidden>> wrote:

> Your question #701636 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/701636
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> Is there anything in the dmesg log when you have the reader already
> connected and insert the ID card afterwards?
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu/+question/701636
>
> You received this question notification because you asked the question.
>

Correction, I mistyped my answer.
The card reader is only *not* used for memory cards but to read a national
ID card. I don't know if that's the reason, just an FYI.

On Wed, May 4, 2022 at 11:10 PM Jan Rubbrecht <email address hidden>
wrote:

> No, there's no output from dmesg following the insertion of my ID card.
> I've checked multiple times using the 'sudo dmesg | tail' command, I've
> tailed /var/log/messages and /var/log/syslog but the only thing I actually
> see is when I plug in the device.
> That being said, on Debian 11 (and previously Ubuntu 20.04) I can use the
> card reader to authenticate using my ID. There's nothing wrong with the
> hardware.
>
> The card reader is only used for memory cards but to read a national ID
> card. I don't know if that's the reason, just an FYI.
>
> On Wed, May 4, 2022 at 6:21 PM Manfred Hampl <
> <email address hidden>> wrote:
>
>> Your question #701636 on Ubuntu changed:
>> https://answers.launchpad.net/ubuntu/+question/701636
>>
>> Status: Open => Needs information
>>
>> Manfred Hampl requested more information:
>> Is there anything in the dmesg log when you have the reader already
>> connected and insert the ID card afterwards?
>>
>> --
>> To answer this request for more information, you can either reply to
>> this email or enter your reply at the following page:
>> https://answers.launchpad.net/ubuntu/+question/701636
>>
>> You received this question notification because you asked the question.
>>
>

I am sorry, but I am running out of ideas.

The only question open is whether this is caused by differences in the kernel version or the program version.

Which kernel version does your Debian system have?
Maybe this is a problem caused by differences between the kernel version in Ubuntu 20.04 and Debian versus the one in Ubuntu 22.04 (probably 5.15.0-*).

AND

Which version of pcsc-tools does your Debian system have? (I assume that you are using that package for accessing the reader and the media inserted into it)
Ubuntu 20.04 comes with 1.5.5-1 and Ubuntu 22.04 has 1.6.0-1

On Debian I'm running kernel 5.10.0-13-amd64 (working)
On Ubuntu I'm on 5.15.0-27-generic (not working).

I did receive a kernel update (from 5.15.0.25 to 5.15.0.27) and now both
blue and red LEDs light up initially when I plug in the device or at boot.
No further signs of it working though.

With regard to pcsc:
On Debian:
dpkg --list |grep pcsc
ii libpcsclite1:amd64 1.9.1-1
                                                               amd64
 Middleware to access a smart card using PC/SC (library)
ii pcscd 1.9.1-1
                                                               amd64
 Middleware to access a smart card using PC/SC (daemon side)

On Ubuntu:
dpkg --list |grep pcsc
ii libpcsclite1:amd64 1.9.5-3
                                           amd64 Middleware to
access a smart card using PC/SC (library)
ii pcscd 1.9.5-3
                                           amd64 Middleware to
access a smart card using PC/SC (daemon side)

On Thu, May 5, 2022 at 9:31 AM Manfred Hampl <
<email address hidden>> wrote:

> Your question #701636 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/701636
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> I am sorry, but I am running out of ideas.
>
> The only question open is whether this is caused by differences in the
> kernel version or the program version.
>
> Which kernel version does your Debian system have?
> Maybe this is a problem caused by differences between the kernel version
> in Ubuntu 20.04 and Debian versus the one in Ubuntu 22.04 (probably
> 5.15.0-*).
>
> AND
>
> Which version of pcsc-tools does your Debian system have? (I assume that
> you are using that package for accessing the reader and the media inserted
> into it)
> Ubuntu 20.04 comes with 1.5.5-1 and Ubuntu 22.04 has 1.6.0-1
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/ubuntu/+question/701636/+confirm?answer_id=7
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+question/701636
>
> You received this question notification because you asked the question.
>

Do you still have an older kernel installed on you Ubuntu 22.04 system (lower than 5.10)?
Then you could try selecting that version from the grub menu for testing.

No I don't, only have 5.15.0-25 and -27 on this computer. I've installed
Ubuntu 22.04 the day it became officially available and cleaned out my
computer with it.

These are the ones available to me:
$ apt-cache search linux-headers-5
linux-headers-5.15.0-1002-gke - Linux kernel headers for version 5.15.0 on
64 bit x86 SMP
linux-headers-5.15.0-1002-ibm - Linux kernel headers for version 5.15.0 on
64 bit x86 SMP
linux-headers-5.15.0-1002-oracle - Oracle Linux kernel headers for version
5.15.0 on 64 bit x86 SMP
linux-headers-5.15.0-1003-azure - Linux kernel headers for version 5.15.0
on 64 bit x86 SMP
linux-headers-5.15.0-1003-gcp - Linux kernel headers for version 5.15.0 on
64 bit x86 SMP
linux-headers-5.15.0-1004-aws - Linux kernel headers for version 5.15.0 on
64 bit x86 SMP
linux-headers-5.15.0-1004-intel-iotg - Linux kernel headers for version
5.15.0 on 64 bit x86 SMP
linux-headers-5.15.0-1004-kvm - Linux kernel headers for version 5.15.0 on
64 bit x86 SMP
linux-headers-5.15.0-24-lowlatency - Linux kernel headers for version
5.15.0 on 64 bit x86 SMP
linux-headers-5.15.0-25 - Header files related to Linux kernel version
5.15.0
linux-headers-5.15.0-25-generic - Linux kernel headers for version 5.15.0
on 64 bit x86 SMP
linux-headers-5.17.0-1003-oem - Linux kernel headers for version 5.17.0 on
64 bit x86 SMP
linux-headers-5.15.0-1003-gke - Linux kernel headers for version 5.15.0 on
64 bit x86 SMP
linux-headers-5.15.0-1003-ibm - Linux kernel headers for version 5.15.0 on
64 bit x86 SMP
linux-headers-5.15.0-1003-oracle - Oracle Linux kernel headers for version
5.15.0 on 64 bit x86 SMP
linux-headers-5.15.0-1004-gcp - Linux kernel headers for version 5.15.0 on
64 bit x86 SMP
linux-headers-5.15.0-1005-aws - Linux kernel headers for version 5.15.0 on
64 bit x86 SMP
linux-headers-5.15.0-1005-azure - Linux kernel headers for version 5.15.0
on 64 bit x86 SMP
linux-headers-5.15.0-1005-kvm - Linux kernel headers for version 5.15.0 on
64 bit x86 SMP
linux-headers-5.15.0-27 - Header files related to Linux kernel version
5.15.0
linux-headers-5.15.0-27-generic - Linux kernel headers for version 5.15.0
on 64 bit x86 SMP
linux-headers-5.15.0-27-lowlatency - Linux kernel headers for version
5.15.0 on 64 bit x86 SMP

If you know a way to go back further, I don't mind trying but it exceeds my
current knowledge right now.

On Fri, May 6, 2022 at 9:36 AM Manfred Hampl <
<email address hidden>> wrote:

> Your question #701636 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/701636
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> Do you still have an older kernel installed on you Ubuntu 22.04 system
> (lower than 5.1)?
> Then you could try selecting that version from the grub menu for testing.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/ubuntu/+question/701636/+confirm?answer_id=9
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+question/701636
>
> You received this question notification because you asked the question.
>

As already written above, I am at my wits' end.

A web search for some of the messages seen in your system brings up a post where "sudo apt install libccid" (respectively the equivalent for a different operating system) helped.

If that does not solve your problem, then I recommend creating a bug report.

Remark: I do not understand the multitude of kernel header packages that you have installed. In my opinion the combination of all different -oem, -gke, -ibm, -oracle, -gcs, -aws and -azure versions does not make any sense.

I guess I'll create a bug then. That libccid was already installed
$ sudo apt install libccid
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
libccid is already the newest version (1.5.0-2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Sorry if I was confusing before, but those linux-headers that I showed are
not all installed on my system. That's what I got from an apt-cache search.
This is what's in my /boot:
$ ls /boot
efi
grub
config-5.15.0-25-generic
config-5.15.0-27-generic
initrd.img
initrd.img-5.15.0-25-generic
initrd.img-5.15.0-27-generic
initrd.img.old
memtest86+.bin
memtest86+.elf
memtest86+_multiboot.bin
System.map-5.15.0-25-generic
System.map-5.15.0-27-generic
vmlinuz
vmlinuz-5.15.0-25-generic
vmlinuz-5.15.0-27-generic
vmlinuz.old

Thanks for all your help and suggestions though, much appreciated.

Cheers,
Jan

On Sat, May 7, 2022 at 7:56 PM Manfred Hampl <
<email address hidden>> wrote:

> Your question #701636 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/701636
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> As already written above, I am at my wits' end.
>
> A web search for some of the messages seen in your system brings up a
> port where "sudo apt install libccid" (respectively the equivalent for a
> different operating system) helped.
>
> If that does not solve your problem, then I recommend creating a bug
> report.
>
> Remark: I do not understand the multitude of kernel header packages that
> you have installed. In my opinion the combination of all different -oem,
> -gke, -ibm, -oracle, -gcs, -aws and -azure versions does not make any
> sense.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/ubuntu/+question/701636/+confirm?answer_id=11
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+question/701636
>
> You received this question notification because you asked the question.
>

Apologies in advance if this is a stupid question, but did you check whether the pcscd service was running in 22.04?

I ran into a similar problem where cardreaders were not being recognized on a new 22.04 install but then realized that pcscd service was not running or started by default. Perhaps it's a change in Ubuntu 22.04 compared to previous versions? Who knows.

After starting pcscd (and enabling it, for future reboots) the following readers are now being detected with opensc-tool --atr, opensc-tool --list-readers and pcsc_scan.

- Omnikey 3121
- ACR
- Gemalto

systemctl status pcscd
systemctl stop pcscd
systemctl enable pcscd
systemctl start pcscd
systemctl status pcscd

I confirm running

sudo systemctl start pcscd

fixes the issue for me.