I will now attach files from 2.6.17-11 that show the device working properly:
Linux novosirj-laptop 2.6.17-11-generic #2 SMP Thu Feb 1 19:52:28 UTC 2007 i686 GNU/Linux ** Summary changed: - USB fingerprint reader broken in 2.6.20-13, worked fine in 2.6.17-11 + USB device detection problems in 2.6.20 ** Description changed: Binary package hint: linux-image-2.6.20-13-generic + Still present in: linux-image-2.6.20-14-generic Upgraded to Kubuntu Feisty Fawn 7.04, kernel 2.6.20-13 installed. pam_bioapi was working fine under 2.6.17-11, but immediately after upgrade, I am experiencing USB problems. Attempting to login, the pam module causes the following to be printed to stdout: [ 357.656000] hub 1-2.3:1.0: hub_port_status failed (err = -71) [ 357.656000] hub 1-2.3:1.0: cannot disable port 1 (err = -71) [ 357.660000] hub 1-2.3:1.0: hub_port_status failed (err = -71) [ 357.768000] hub 1-2:1.0: port 3 disabled by hub (EMI?), re-enabling... - This worked a total of one time (not the first time I tried it either, + This works very occasionally (not the first time I tried it either, somewhere around the 20-30th time that the module was used) and not - again. The machine consistently prints that error and falls back to - password auth every time. + consistently. Other than that, the machine consistently prints that + error and falls back to password auth every time. - The only special boot option I have is pci=assign-busses as dmesg - recommends it: + The only special boot options I have tried are pci=assign-busses and + pci=routeirq as dmesg recommends them: Apr 3 18:19:43 novosirj-laptop kernel: [ 0.205402] PCI: Bus #04 (-#07) is hidden behind transparent bridge #03 (-#04) (try 'pci=assi gn-busses') Apr 3 18:19:43 novosirj-laptop kernel: [ 0.205404] Please report the result to linux-kernel to fix this permanently - ...but this has apparently no effect. A recompile of the module also had - no effect. + ...but this has apparently no effect, except appeared to make things + slightly worse. A recompile of the module also had no effect. Another bit of information is that this DOES continue to work if I boot back into the still-installed linux-image-2.6.17-11. This makes me think it may not be related to an installed base of libraries. Please advise me if I may need to provide more information. ** Attachment added: "dmesg from machine with working USB in 2.6.17-11" http://librarian.launchpad.net/7286006/dmesg-working.log -- USB device detection problems in 2.6.20 https://bugs.launchpad.net/bugs/102659 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
