You are not logged in.

#1 2015-12-13 21:40:07

Kurolox
Member
Registered: 2015-09-15
Posts: 36

[Solved] USB printer is not being detected by lsusb

I'm trying to configure my laser printer in my computer (Samsung M2022), so I started to read the CUPS wiki page. After installing all the packages that I needed, running lsusb doesn't show the printer at all.

[kuro@ArchKuro ~]$ lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 004: ID 1532:011a Razer USA, Ltd 
Bus 005 Device 003: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0
Bus 005 Device 002: ID 2109:0811 VIA Labs, Inc. Hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 006: ID 1af3:0001  
Bus 001 Device 005: ID 17a0:0310 Samson Technologies Corp. Meteor condenser microphone
Bus 001 Device 004: ID 28de:1142  
Bus 001 Device 003: ID 045e:076d Microsoft Corp. LifeCam HD-5000
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Just for being sure, I connected other printer with the same cable, and that one was detected by lsusb.

Bus 002 Device 015: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus CX3900/DX4000/DX4050]

I couldn't find anything related to this in the wiki. I guess it's something big considering lsusb should detect the printer even if it's not configured. Between other things, this is what I've done:

- Enabling and starting org.cups.cupsd.service
- Downloaded the recommended drivers for my printer (splix)
- Blacklisted usblp even when it's not needed

I still need to try the printer under a windows installation to discard hardware problems. Meanwhile, what could I do to troubleshoot the printer?

Last edited by Kurolox (2015-12-14 17:18:03)

Offline

#2 2015-12-13 22:04:59

lucke
Member
From: Poland
Registered: 2004-11-30
Posts: 4,018

Re: [Solved] USB printer is not being detected by lsusb

Is the printer on? Does dmesg show anything at all when you connect it?

Offline

#3 2015-12-14 06:21:00

Kurolox
Member
Registered: 2015-09-15
Posts: 36

Re: [Solved] USB printer is not being detected by lsusb

Yes, the printer is on. Seems like dmesg doesn't show nothing, but I can't add the log right now. I also tried installing the drivers from the printer webpage, but seems like system-config-printer doesn't exist and I can't install it from aur because there are some conflicts with files. I'll keep trying things.

Edit: This is what dmesg show when I connect the printer.

[ 2568.927871] usb 5-1.4: new high-speed USB device number 17 using xhci_hcd
[ 2568.994811] usb 5-1.4: device descriptor read/64, error -71
[ 2569.164877] usb 5-1.4: device descriptor read/64, error -71
[ 2569.334702] usb 5-1.4: new high-speed USB device number 18 using xhci_hcd
[ 2569.401579] usb 5-1.4: device descriptor read/64, error -71
[ 2569.571688] usb 5-1.4: device descriptor read/64, error -71
[ 2569.741613] usb 5-1.4: new high-speed USB device number 19 using xhci_hcd
[ 2569.741889] usb 5-1.4: Device not responding to setup address.
[ 2569.945232] usb 5-1.4: Device not responding to setup address.
[ 2570.148376] usb 5-1.4: device not accepting address 19, error -71
[ 2570.215053] usb 5-1.4: new high-speed USB device number 20 using xhci_hcd
[ 2570.215468] usb 5-1.4: Device not responding to setup address.
[ 2570.418751] usb 5-1.4: Device not responding to setup address.
[ 2570.621882] usb 5-1.4: device not accepting address 20, error -71
[ 2570.622062] usb 5-1-port4: unable to enumerate USB device

Last edited by Kurolox (2015-12-14 06:28:23)

Offline

#4 2015-12-14 17:18:59

Kurolox
Member
Registered: 2015-09-15
Posts: 36

Re: [Solved] USB printer is not being detected by lsusb

Solved. For some reason, the cable was the culprit. I swapped it and everything worked like a charm. I don't understand why, because that faulty cable was able to detect the other printer, but whatever.

Offline

Board footer

Powered by FluxBB