Description of problem:
kernels 188.8.131.52-20.fc7 and 184.108.40.206-27.fc7 make pilot-link with libusb support
Version-Release number of selected component (if applicable):
pilot-link-0.12.1 built with libusb support
The same pilot-xfer binary and udev package works with kernel-2.6.21-1.3228.fc7
Steps to Reproduce:
1. Build pilot-link-0.12.1 with libusb support (use './configure --with-python
--enable-libusb --enable-conduits --prefix=/opt/pilot-link/' to install it
separately from F7 pilot-link package)
2. Connect your PalmOS USB device, press Syncronize button
3. Try '/opt/pilot-link/bin/pilot-xfer -l -p usb:' with
kernel-2.6.21-1.3228.fc7, you will get file list in your PDA.
4. Boot 220.127.116.11-27.fc7 and repeat step #3. Nothing happens.
Actual results: No connection with PDA
Expected results: Information exchange with PDA
Two files attached. These are fragments from /var/log/message after 'udevcontrol
log_priority="debug"'. One is for working case, another is not working.
Created attachment 159715 [details]
fragments from /var/log/message after 'udevcontrol log_priority="debug"'
Sorry I forget to mention that to test this case, you need to blacklist visor
module (please, read pilot-link-0.12.1/doc/README.libusb file for more info)
to avoid opening another bug, this bug also applies to F-Spot and digiKam (and
possibly other applications) in regard to being able to communicate with USB
cameras in PTP mode. With kernel 18.104.22.168-3228 such communication simply works,
and with kernel 22.214.171.124-27 it does not. It is _very_ annoying, and is somehow
associated with the 2.6.22 kernel. Is there any information I might provide
which would assist in its resolution? Or are there any tests which might help
(it feels like a permissions issue, but one isn't sure where to start poking first!)
Otherwise, I would suggest that the severity should be high, since it probably
affects any USB connected peripheral.
Created attachment 159761 [details]
dmesg output and /var/log/messages fragments
It seems that some USB stuff is broken in 126.96.36.199-27. I don't know if it is
related or not but with this kernel Nokia E65 cell phone is not mounted
when connected with USB data cable in "Data transfer" mode. In FC5 and in F7
with 188.8.131.52-3228 it mounts without a problem. Above are dmesg outputs and /
var/log/messages files related to working and nonworking kernels. udevcontrol
log_priority="debug" was set for more information.
*** This bug has been marked as a duplicate of 249272 ***
Sorry, I do not agree that this bug has been marked as a duplicate of 249272.
On my computer USB flash drives and CD/DVD drive attached to USB works without
a problem. So, this is a separate bug. If you still think that this is a
duplicate, please, provide some explanations.
Also, please note, this bug was filed earlier, so why THIS bug is duplicate?
(In reply to comment #6)
> *** This bug has been marked as a duplicate of 249272 ***
I agree with Sergui, this bug is concerned with USB communication to an
intelligent peripheral. There is no problem with a USB mass storage device.
Gentlemen, anybody working on that? Any progress? Is there a discussion
somewhere regarding this kernel problem?
Should be all fixed in 184.108.40.206-33, sent to updates-testing this morning
but not pushed out to the repo yet.
Thank you. When will it be available for download? Is there a changelog?
You can get an advance copy directly out of the build system here:
Changelog is in the package itself, or in cvs.
Thank you again. I have installed it and tested. pilot-link with libusb support
seems working perfectly. However there is still an issue with connection Nokia
E65 phone over USB. I confirm that it connects and mounts automatically with
220.127.116.11-3228 kernel but fails with any available 18.104.22.168. Is that another bug
#249272? Any idea? Any other mass storage devices (USB memory, ATA drives
connected with ATA-USB adapter) are mounted automatically. MicroSD from the
mentioned above Nokia E65 connected through USB card reader works as well. Only
when inserted in the phone and the phone connected over USB data cable in "Data
transfer" mode it can not mount automatically.
If this is a different bug, I would close this particular one but I think we
should wait Robin Gape to test this kernel with PTP camera.
I have installed the 22.214.171.124-33 kernel. USB PTP camera functionality is
restored, as far as I can tell. The three test cameras are all recognised, and
pictures (images) can be downloaded and deleted. From my viewpoint the bug may
Thanks to Sergui, Chuck and Jarod and whomsoever fixed the kernel bug.
Thank you Robin. I'm closing this bug.