USB card reader does not work in Linux. Prolific driver missing?












0














When I plug the reader into USB port then it is not recognized by the system and the red LED in it keeps on glowing (as opposed to the situation when it is running properly and the LED is only glowing and blinking for some time and then fades away).



I have no idea how could I make the reader running in Linux (OpenSuse).
When I run lsusb in the command line I see that there is a new entry after plugging in the said device




Bus 003 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port




The new entries of the output of dmesg after plugging in the device are



[  475.196212] usb 1-4: new full-speed USB device number 2 using xhci_hcd
[ 475.345247] usb 1-4: New USB device found, idVendor=067b, idProduct=2303
[ 475.345254] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 475.345259] usb 1-4: Product: USB-Serial Controller
[ 475.345263] usb 1-4: Manufacturer: Prolific Technology Inc.
[ 475.889794] usbcore: registered new interface driver usbserial
[ 475.889807] usbcore: registered new interface driver usbserial_generic
[ 475.889817] usbserial: USB Serial support registered for generic
[ 475.890487] usbcore: registered new interface driver pl2303
[ 475.890507] usbserial: USB Serial support registered for pl2303
[ 475.890533] pl2303 1-4:1.0: pl2303 converter detected
[ 475.891894] usb 1-4: pl2303 converter now attached to ttyUSB0


The output of modinfo pl2303 is:



filename:       /lib/modules/user/kernel/drivers/usb/serial/pl2303.ko
license: GPL
description: Prolific PL2303 USB to serial adaptor driver
suserelease: openSUSE Leap 15.0
srcversion: F4D092C5854E6E51A3C7F32
alias: usb:v0B8Cp2303d*dc*dsc*dp*ic*isc*ip*in*
[ many lines follwoing the same pattern ]
alias: usb:v067Bp2303d*dc*dsc*dp*ic*isc*ip*in*
depends: usbserial,usbcore
retpoline: Y
intree: Y
vermagic: user SMP mod_unload modversions retpoline


How can I check whether "the load patterns match the USB info"?



How can I get proper drivers for Linux if I only have them for Windows?



What might be other reasons why the device cannot be used from other apps?










share|improve this question
























  • btw, the kernel driver (exposing the serial port) should be there: /lib/modules/$(uname -r)/kernel/drivers/usb/serial/pl2303.ko. If not, then an other kernel with the driver enabled has to be used.
    – A.B
    Dec 22 '18 at 1:43










  • (corrected my 1st comment) I remember that to get my pl2303 based cheap SIM card reader used on Debian, I needed openct as backend for pcsclite. I don't remember any generic scsi. It exposed a serial port. openct was dropped so it became difficult to use it on debian 8 and quite impossible on debian 9. You should consider getting a more modern reader. eg: ccid.apdu.fr/ccid/section.html (ideally with extended apdu support, as seen there: Extended APDU status per reader )
    – A.B
    Dec 22 '18 at 1:58












  • This should help setting up openct+pcsc (as long as you find the software for suse, and that pcsc still uses openct as backend): Using cheap SIM card readers.
    – A.B
    Dec 22 '18 at 2:16












  • Please don't grep dmesg output, you'll loose all error messages. Instead, edit question with all new lines in dmesg that appear after you plug in the device. This will tell you (and us) if there are any errors, and if a driver loads. If the driver doesn't load, next step is to modinfo pl2303 and see if the load patterns match the USB info.
    – dirkt
    Dec 22 '18 at 20:50
















0














When I plug the reader into USB port then it is not recognized by the system and the red LED in it keeps on glowing (as opposed to the situation when it is running properly and the LED is only glowing and blinking for some time and then fades away).



I have no idea how could I make the reader running in Linux (OpenSuse).
When I run lsusb in the command line I see that there is a new entry after plugging in the said device




Bus 003 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port




The new entries of the output of dmesg after plugging in the device are



[  475.196212] usb 1-4: new full-speed USB device number 2 using xhci_hcd
[ 475.345247] usb 1-4: New USB device found, idVendor=067b, idProduct=2303
[ 475.345254] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 475.345259] usb 1-4: Product: USB-Serial Controller
[ 475.345263] usb 1-4: Manufacturer: Prolific Technology Inc.
[ 475.889794] usbcore: registered new interface driver usbserial
[ 475.889807] usbcore: registered new interface driver usbserial_generic
[ 475.889817] usbserial: USB Serial support registered for generic
[ 475.890487] usbcore: registered new interface driver pl2303
[ 475.890507] usbserial: USB Serial support registered for pl2303
[ 475.890533] pl2303 1-4:1.0: pl2303 converter detected
[ 475.891894] usb 1-4: pl2303 converter now attached to ttyUSB0


The output of modinfo pl2303 is:



filename:       /lib/modules/user/kernel/drivers/usb/serial/pl2303.ko
license: GPL
description: Prolific PL2303 USB to serial adaptor driver
suserelease: openSUSE Leap 15.0
srcversion: F4D092C5854E6E51A3C7F32
alias: usb:v0B8Cp2303d*dc*dsc*dp*ic*isc*ip*in*
[ many lines follwoing the same pattern ]
alias: usb:v067Bp2303d*dc*dsc*dp*ic*isc*ip*in*
depends: usbserial,usbcore
retpoline: Y
intree: Y
vermagic: user SMP mod_unload modversions retpoline


How can I check whether "the load patterns match the USB info"?



How can I get proper drivers for Linux if I only have them for Windows?



What might be other reasons why the device cannot be used from other apps?










share|improve this question
























  • btw, the kernel driver (exposing the serial port) should be there: /lib/modules/$(uname -r)/kernel/drivers/usb/serial/pl2303.ko. If not, then an other kernel with the driver enabled has to be used.
    – A.B
    Dec 22 '18 at 1:43










  • (corrected my 1st comment) I remember that to get my pl2303 based cheap SIM card reader used on Debian, I needed openct as backend for pcsclite. I don't remember any generic scsi. It exposed a serial port. openct was dropped so it became difficult to use it on debian 8 and quite impossible on debian 9. You should consider getting a more modern reader. eg: ccid.apdu.fr/ccid/section.html (ideally with extended apdu support, as seen there: Extended APDU status per reader )
    – A.B
    Dec 22 '18 at 1:58












  • This should help setting up openct+pcsc (as long as you find the software for suse, and that pcsc still uses openct as backend): Using cheap SIM card readers.
    – A.B
    Dec 22 '18 at 2:16












  • Please don't grep dmesg output, you'll loose all error messages. Instead, edit question with all new lines in dmesg that appear after you plug in the device. This will tell you (and us) if there are any errors, and if a driver loads. If the driver doesn't load, next step is to modinfo pl2303 and see if the load patterns match the USB info.
    – dirkt
    Dec 22 '18 at 20:50














0












0








0







When I plug the reader into USB port then it is not recognized by the system and the red LED in it keeps on glowing (as opposed to the situation when it is running properly and the LED is only glowing and blinking for some time and then fades away).



I have no idea how could I make the reader running in Linux (OpenSuse).
When I run lsusb in the command line I see that there is a new entry after plugging in the said device




Bus 003 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port




The new entries of the output of dmesg after plugging in the device are



[  475.196212] usb 1-4: new full-speed USB device number 2 using xhci_hcd
[ 475.345247] usb 1-4: New USB device found, idVendor=067b, idProduct=2303
[ 475.345254] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 475.345259] usb 1-4: Product: USB-Serial Controller
[ 475.345263] usb 1-4: Manufacturer: Prolific Technology Inc.
[ 475.889794] usbcore: registered new interface driver usbserial
[ 475.889807] usbcore: registered new interface driver usbserial_generic
[ 475.889817] usbserial: USB Serial support registered for generic
[ 475.890487] usbcore: registered new interface driver pl2303
[ 475.890507] usbserial: USB Serial support registered for pl2303
[ 475.890533] pl2303 1-4:1.0: pl2303 converter detected
[ 475.891894] usb 1-4: pl2303 converter now attached to ttyUSB0


The output of modinfo pl2303 is:



filename:       /lib/modules/user/kernel/drivers/usb/serial/pl2303.ko
license: GPL
description: Prolific PL2303 USB to serial adaptor driver
suserelease: openSUSE Leap 15.0
srcversion: F4D092C5854E6E51A3C7F32
alias: usb:v0B8Cp2303d*dc*dsc*dp*ic*isc*ip*in*
[ many lines follwoing the same pattern ]
alias: usb:v067Bp2303d*dc*dsc*dp*ic*isc*ip*in*
depends: usbserial,usbcore
retpoline: Y
intree: Y
vermagic: user SMP mod_unload modversions retpoline


How can I check whether "the load patterns match the USB info"?



How can I get proper drivers for Linux if I only have them for Windows?



What might be other reasons why the device cannot be used from other apps?










share|improve this question















When I plug the reader into USB port then it is not recognized by the system and the red LED in it keeps on glowing (as opposed to the situation when it is running properly and the LED is only glowing and blinking for some time and then fades away).



I have no idea how could I make the reader running in Linux (OpenSuse).
When I run lsusb in the command line I see that there is a new entry after plugging in the said device




Bus 003 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port




The new entries of the output of dmesg after plugging in the device are



[  475.196212] usb 1-4: new full-speed USB device number 2 using xhci_hcd
[ 475.345247] usb 1-4: New USB device found, idVendor=067b, idProduct=2303
[ 475.345254] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 475.345259] usb 1-4: Product: USB-Serial Controller
[ 475.345263] usb 1-4: Manufacturer: Prolific Technology Inc.
[ 475.889794] usbcore: registered new interface driver usbserial
[ 475.889807] usbcore: registered new interface driver usbserial_generic
[ 475.889817] usbserial: USB Serial support registered for generic
[ 475.890487] usbcore: registered new interface driver pl2303
[ 475.890507] usbserial: USB Serial support registered for pl2303
[ 475.890533] pl2303 1-4:1.0: pl2303 converter detected
[ 475.891894] usb 1-4: pl2303 converter now attached to ttyUSB0


The output of modinfo pl2303 is:



filename:       /lib/modules/user/kernel/drivers/usb/serial/pl2303.ko
license: GPL
description: Prolific PL2303 USB to serial adaptor driver
suserelease: openSUSE Leap 15.0
srcversion: F4D092C5854E6E51A3C7F32
alias: usb:v0B8Cp2303d*dc*dsc*dp*ic*isc*ip*in*
[ many lines follwoing the same pattern ]
alias: usb:v067Bp2303d*dc*dsc*dp*ic*isc*ip*in*
depends: usbserial,usbcore
retpoline: Y
intree: Y
vermagic: user SMP mod_unload modversions retpoline


How can I check whether "the load patterns match the USB info"?



How can I get proper drivers for Linux if I only have them for Windows?



What might be other reasons why the device cannot be used from other apps?







drivers usb opensuse






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 23 '18 at 0:15

























asked Dec 21 '18 at 23:49









MK.

11




11












  • btw, the kernel driver (exposing the serial port) should be there: /lib/modules/$(uname -r)/kernel/drivers/usb/serial/pl2303.ko. If not, then an other kernel with the driver enabled has to be used.
    – A.B
    Dec 22 '18 at 1:43










  • (corrected my 1st comment) I remember that to get my pl2303 based cheap SIM card reader used on Debian, I needed openct as backend for pcsclite. I don't remember any generic scsi. It exposed a serial port. openct was dropped so it became difficult to use it on debian 8 and quite impossible on debian 9. You should consider getting a more modern reader. eg: ccid.apdu.fr/ccid/section.html (ideally with extended apdu support, as seen there: Extended APDU status per reader )
    – A.B
    Dec 22 '18 at 1:58












  • This should help setting up openct+pcsc (as long as you find the software for suse, and that pcsc still uses openct as backend): Using cheap SIM card readers.
    – A.B
    Dec 22 '18 at 2:16












  • Please don't grep dmesg output, you'll loose all error messages. Instead, edit question with all new lines in dmesg that appear after you plug in the device. This will tell you (and us) if there are any errors, and if a driver loads. If the driver doesn't load, next step is to modinfo pl2303 and see if the load patterns match the USB info.
    – dirkt
    Dec 22 '18 at 20:50


















  • btw, the kernel driver (exposing the serial port) should be there: /lib/modules/$(uname -r)/kernel/drivers/usb/serial/pl2303.ko. If not, then an other kernel with the driver enabled has to be used.
    – A.B
    Dec 22 '18 at 1:43










  • (corrected my 1st comment) I remember that to get my pl2303 based cheap SIM card reader used on Debian, I needed openct as backend for pcsclite. I don't remember any generic scsi. It exposed a serial port. openct was dropped so it became difficult to use it on debian 8 and quite impossible on debian 9. You should consider getting a more modern reader. eg: ccid.apdu.fr/ccid/section.html (ideally with extended apdu support, as seen there: Extended APDU status per reader )
    – A.B
    Dec 22 '18 at 1:58












  • This should help setting up openct+pcsc (as long as you find the software for suse, and that pcsc still uses openct as backend): Using cheap SIM card readers.
    – A.B
    Dec 22 '18 at 2:16












  • Please don't grep dmesg output, you'll loose all error messages. Instead, edit question with all new lines in dmesg that appear after you plug in the device. This will tell you (and us) if there are any errors, and if a driver loads. If the driver doesn't load, next step is to modinfo pl2303 and see if the load patterns match the USB info.
    – dirkt
    Dec 22 '18 at 20:50
















btw, the kernel driver (exposing the serial port) should be there: /lib/modules/$(uname -r)/kernel/drivers/usb/serial/pl2303.ko. If not, then an other kernel with the driver enabled has to be used.
– A.B
Dec 22 '18 at 1:43




btw, the kernel driver (exposing the serial port) should be there: /lib/modules/$(uname -r)/kernel/drivers/usb/serial/pl2303.ko. If not, then an other kernel with the driver enabled has to be used.
– A.B
Dec 22 '18 at 1:43












(corrected my 1st comment) I remember that to get my pl2303 based cheap SIM card reader used on Debian, I needed openct as backend for pcsclite. I don't remember any generic scsi. It exposed a serial port. openct was dropped so it became difficult to use it on debian 8 and quite impossible on debian 9. You should consider getting a more modern reader. eg: ccid.apdu.fr/ccid/section.html (ideally with extended apdu support, as seen there: Extended APDU status per reader )
– A.B
Dec 22 '18 at 1:58






(corrected my 1st comment) I remember that to get my pl2303 based cheap SIM card reader used on Debian, I needed openct as backend for pcsclite. I don't remember any generic scsi. It exposed a serial port. openct was dropped so it became difficult to use it on debian 8 and quite impossible on debian 9. You should consider getting a more modern reader. eg: ccid.apdu.fr/ccid/section.html (ideally with extended apdu support, as seen there: Extended APDU status per reader )
– A.B
Dec 22 '18 at 1:58














This should help setting up openct+pcsc (as long as you find the software for suse, and that pcsc still uses openct as backend): Using cheap SIM card readers.
– A.B
Dec 22 '18 at 2:16






This should help setting up openct+pcsc (as long as you find the software for suse, and that pcsc still uses openct as backend): Using cheap SIM card readers.
– A.B
Dec 22 '18 at 2:16














Please don't grep dmesg output, you'll loose all error messages. Instead, edit question with all new lines in dmesg that appear after you plug in the device. This will tell you (and us) if there are any errors, and if a driver loads. If the driver doesn't load, next step is to modinfo pl2303 and see if the load patterns match the USB info.
– dirkt
Dec 22 '18 at 20:50




Please don't grep dmesg output, you'll loose all error messages. Instead, edit question with all new lines in dmesg that appear after you plug in the device. This will tell you (and us) if there are any errors, and if a driver loads. If the driver doesn't load, next step is to modinfo pl2303 and see if the load patterns match the USB info.
– dirkt
Dec 22 '18 at 20:50










0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f490422%2fusb-card-reader-does-not-work-in-linux-prolific-driver-missing%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f490422%2fusb-card-reader-does-not-work-in-linux-prolific-driver-missing%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Morgemoulin

Scott Moir

Souastre