| Summary: | HP Laseserjet 3005P USB port not recognized when switch on | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | papoteur <yvesbrungard> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | doktor5000, makowski.mageia, marja11, pkg-bugs, tmb |
| Version: | 5 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | NEEDHELP | ||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Bug Depends on: | |||
| Bug Blocks: | 18367 | ||
|
Description
papoteur
2016-01-05 12:33:54 CET
Could be a buggy usb hub. Try the same with the printer connected directly to the laptop CC:
(none) =>
tmb OK, I just tried: same problem 332156.251451] usb 1-2.3: USB disconnect, device number 70 [332156.251455] usb 1-2.3.1: USB disconnect, device number 71 [332182.033032] usb 1-3: new high-speed USB device number 73 using xhci_hcd [332182.197264] usb 1-3: New USB device found, idVendor=0424, idProduct=2502 [332182.197268] usb 1-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [332182.197762] hub 1-3:1.0: USB hub found [332182.197784] hub 1-3:1.0: 2 ports detected [332182.471338] usb 1-3.1: new full-speed USB device number 74 using xhci_hcd [332182.544383] usb 1-3.1: device descriptor read/64, error -32 [332182.718499] usb 1-3.1: device descriptor read/64, error -32 [332182.892559] usb 1-3.1: new full-speed USB device number 75 using xhci_hcd [332182.965680] usb 1-3.1: device descriptor read/64, error -32 [332183.139760] usb 1-3.1: device descriptor read/64, error -32 [332183.313835] usb 1-3.1: new full-speed USB device number 76 using xhci_hcd [332183.313925] usb 1-3.1: Device not responding to setup address. [332183.515191] usb 1-3.1: Device not responding to setup address. [332183.716134] usb 1-3.1: device not accepting address 76, error -71 [332183.789185] usb 1-3.1: new full-speed USB device number 77 using xhci_hcd [332183.789364] usb 1-3.1: Device not responding to setup address. [332183.990340] usb 1-3.1: Device not responding to setup address. [332184.191388] usb 1-3.1: device not accepting address 77, error -71 [332184.191424] usb 1-3-port1: unable to enumerate USB device Adding packagers in CC to help triaging this printer driver or hardware issue. CC:
(none) =>
doktor5000, pkg-bugs Seems more like hardware issue, as connecting the powered printer via hub seems to work. @papoteur: Can you try to attach it directly to the laptop on another port, preferrably not via usb 3.0 port ? I tried on another computer and with a direct connection. For what I know, there is no USB3 here. I was the case with the laptop (previously). When switching on, same error: [ 152.275031] usb 1-8: new high-speed USB device number 4 using ehci-pci [ 152.425464] usb 1-8: New USB device found, idVendor=0424, idProduct=2502 [ 152.425468] usb 1-8: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 152.425764] hub 1-8:1.0: USB hub found [ 152.425805] hub 1-8:1.0: 2 ports detected [ 152.705304] usb 1-8.1: new full-speed USB device number 5 using ehci-pci [ 152.785334] usb 1-8.1: device descriptor read/64, error -32 [ 152.975384] usb 1-8.1: device descriptor read/64, error -32 [ 153.165449] usb 1-8.1: new full-speed USB device number 6 using ehci-pci [ 153.245478] usb 1-8.1: device descriptor read/64, error -32 [ 153.435691] usb 1-8.1: device descriptor read/64, error -32 [ 153.625757] usb 1-8.1: new full-speed USB device number 7 using ehci-pci [ 154.045790] usb 1-8.1: device not accepting address 7, error -32 [ 154.125933] usb 1-8.1: new full-speed USB device number 8 using ehci-pci [ 154.546034] usb 1-8.1: device not accepting address 8, error -32 [ 154.546206] usb 1-8-port1: unable to enumerate USB device Then unpluging [ 466.811588] usb 1-8: USB disconnect, device number 4 Then plugging again [ 485.609738] usb 1-8: new high-speed USB device number 9 using ehci-pci [ 485.760150] usb 1-8: New USB device found, idVendor=0424, idProduct=2502 [ 485.760154] usb 1-8: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 485.760451] hub 1-8:1.0: USB hub found [ 485.760495] hub 1-8:1.0: 2 ports detected [ 486.039976] usb 1-8.1: new high-speed USB device number 10 using ehci-pci [ 486.150911] usb 1-8.1: New USB device found, idVendor=03f0, idProduct=7317 [ 486.150915] usb 1-8.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 486.150917] usb 1-8.1: Product: HP LaserJet P3005 [ 486.150918] usb 1-8.1: Manufacturer: Hewlett-Packard [ 486.150920] usb 1-8.1: SerialNumber: CNK1T82846 [ 486.157590] WARNING! power/level is deprecated; use power/control instead [ 486.202163] usblp 1-8.1:1.0: usblp0: USB Bidirectional printer dev 10 if 0 alt 1 proto 2 vid 0x03F0 pid 0x7317 [ 486.202188] usbcore: registered new interface driver usblp Thus, it seems related to hardware, but I don't know if the hardware is failing, has particular behaviour which is not managed by Linux tools or is buggy. I can't compare with behaviour under Windows, I never used it except with net interface.
Marja Van Waes
2016-05-05 10:22:15 CEST
Blocks:
(none) =>
18367
On the 25th of July, Phillipem uploaded the following packages to
Cauldron's core/updates_testing:
system-config-printer-1.5.7-5.mga6.i586
system-config-printer-applet-1.5.7-5.mga6.i586
system-config-printer-udev-1.5.7-5.mga6.i586
system-config-printer-libs-1.5.7-5.mga6.noarch
system-config-printer-1.5.7-5.mga6.x86_64
system-config-printer-applet-1.5.7-5.mga6.x86_64
system-config-printer-udev-1.5.7-5.mga6.x86_64
@ Anyone reading this:
* If this bug is valid for you in cauldron, then please test whether updating your system-config-printer packages to version 1.5.7-5.mga6 fixes the problem and report back in this bug report.
* If you do not have this bug in cauldron, but you do run cauldron, then please update those packages, too, and report in bug 18367 whether they work as expected.CC:
(none) =>
makowski.mageia, marja11 Is this bug report still valid? Keywords:
(none) =>
NEEDINFO Hello, Perhaps, but for now, I use this printer on Lan, thus, I don't hit this bug anymore. Thus I close. Status:
NEW =>
RESOLVED |