Red Hat Bugzilla – Bug 858368
pcsc-tools and coolkey no longer reading Broadcom Corp 5880
Last modified: 2013-08-01 06:03:23 EDT
Description of problem: Was using my Broadcom Corp 5880 with my CAC card very happily for a couple weeks in Fedora 17. Noticed today it won't work.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run pcsc_scan
2. cat /var/logs/messages
Actual results: No detection of card while in reader, Errors in messages
Expected results: Detection of card while in reader
Additional info: Today I updated all of my packages and also added an ATT PC networking card (PC, not USB). I'm not sure if this might have done something. I've rebooted multiple times with and without the PC card connected and the Broadcom Corp 5880 still will not read.
Andrew, please follow http://pcsclite.alioth.debian.org/pcsclite.html#support and generates a pcscd log.
Created attachment 614339 [details]
[agd@enyo ~]$ /usr/sbin/pcscd --version
pcsc-lite version 1.8.3.
Copyright (C) 1999-2002 by David Corcoran <email@example.com>.
Copyright (C) 2001-2011 by Ludovic Rousseau <firstname.lastname@example.org>.
Copyright (C) 2003-2004 by Damien Sauveron <email@example.com>.
Report bugs to <firstname.lastname@example.org>.
Enabled features: Linux x86_64-redhat-linux-gnu serial usb libudev usbdropdir=/usr/lib64/pcsc/drivers ipcdir=/var/run/pcscd configdir=/etc/reader.conf.d
Is your reader a dual interface reader for contact and contactless cards?
Please follow http://pcsclite.alioth.debian.org/ccid.html#CCID_compliant and attach the output.txt file.
Created attachment 614403 [details]
CCID sudo ./src/parse > output.txt
tar xjvf ccid-1.4.7.tar.bz2
sudo ./src/parse > output.txt
You can see I have two card readers in there now, I'm using a SGT USB card reader because I can't get the Broadcom 5880 to work.
You only have a contact interface on this reader.
If the reader sudenly stopped working (without changing anything in the software layer) I guess it is just broken.
In your first message you write about "Errors in messages" but I cannot find anything related to that.
Maybe you can send the error messages you see in /var/logs/messages?
I guess it could be broke, that would make me really sad. I've got a warranty under Dell so I'll see if I can get them to send me a replacement.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.