[SOLVED] USB device being ejected by the kernel when plugged in
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
USB device being ejected by the kernel when plugged in
Dear
I have a question on the Slackware distribution from version 14.2, because every time I plug in a Gertec PPC920 USB PINPAD the Kernel ejects the device as if it is no longer plugged in.
I did tests on Linux Slackware 14.1 and also other distributions like Linux Mint 19 and work without problems, already with Slackware 14.2 and also with the current version of Slackware the problem occurs.
Monitoring the UDEV we can see:
root@darkstar:/u# udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
[ 900.329260] usb 3-2: new full-speed USB device number 7 using uhci_hcd
[ 900.499278] usb 3-2: Dual-Role OTG device on non-HNP port
[ 900.502284] usb 3-2: New USB device found, idVendor=1753, idProduct=c902, bcdDevice= 0.01
[ 900.502288] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 900.502292] usb 3-2: Product: PPC920 Pinpad Terminal
[ 900.502295] usb 3-2: Manufacturer: GERTEC
[ 900.505428] cdc_acm 3-2:1.0: ttyACM0: USB ACM device
[ 900.507994] usb 3-2: USB disconnect, device number 7
By doing several tests, I realize that I have a problem with Slackware packaging.
Using 2 computers for the tests, follow the results:
1. Computer with USB only 1.10 - No USB device works with this device.
2. Computer with USB 2.0 and 3.0 - Some USB ports work only with this device.
Now using Linux Mint 19 - Live on the same computers
1. Computer with USB only 1.10 - All USB ports working with the device.
2. Computer with USB 2.0 and 3.0 - Also all USB ports working with the device.
Slackware simply ejects the device and ignores any rule it places for the usb device.
--------------------- LINUX MINT 19 LIVE ---------------------
root@mint:~# udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
[ 1163.335657] usb 2-1: new full-speed USB device number 4 using uhci_hcd
[ 1163.523543] usb 2-1: New USB device found, idVendor=1753, idProduct=c902
[ 1163.523548] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1163.523552] usb 2-1: Product: PPC920 Pinpad Terminal
[ 1163.523556] usb 2-1: Manufacturer: GERTEC
[ 1163.526705] cdc_acm 2-1:1.0: ttyACM0: USB ACM device
If it included the pound/hash symbol (#) in front of it, then making that change does nothing. Those are used to "comment out" lines in kernel configs (along with many other configs and some scripting languages).
Anything in your kernel config that has a # in front of it won't be considered when compiling the kernel.
I'm not sure if you put it there as a copy/paste (which means recompiling won't change anything) or to indicate something else and in reality, they do not exist in the configs (in which case, recompiling would remove that feature). If you're curious, you can designate text as "code" using [code][/code] tags.
Code:
# CONFIG_USB_OTG = y
Code:
# CONFIG_USB_OTG is not set
This can be used to make it easy to differentiate between output from a console/file/command vs just text that's being typed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.