Bug 532394
| Summary: | sansa clip usb un-recognized; fails to mount | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | abrouwers |
| Component: | kernel | Assignee: | Pete Zaitcev <zaitcev> |
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 12 | CC: | davidz, dougsland, gansalmon, itamar, kernel-maint, zaitcev |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-12-08 16:33:55 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
abrouwers
2009-11-02 03:02:04 UTC
Doesn't even get to binding the usb-storage driver -> kernel (or hardware) problem. Reassigning. Sorry - my mistake. I suppose you are right - it doesn't even get a device node assigned properly. I have booted a Fedora 11 liveCD, and plugged the same mp3 player, into the same USB port on the same laptop (with the same cable :) , and it indeed detects and mounts the device automatically: [liveuser@localhost ~]$ dmesg | tail sd 6:0:0:0: [sdb] Mode Sense: 04 00 00 00 sd 6:0:0:0: [sdb] Assuming drive cache: write through sd 6:0:0:0: [sdb] 1986048 512-byte hardware sectors: (1.01 GB/969 MiB) sd 6:0:0:0: [sdb] Write Protect is off sd 6:0:0:0: [sdb] Mode Sense: 04 00 00 00 sd 6:0:0:0: [sdb] Assuming drive cache: write through sdb: sd 6:0:0:0: [sdb] Attached SCSI removable disk sd 6:0:0:0: Attached scsi generic sg2 type 0 SELinux: initialized (dev sdb, type vfat), uses genfs_contexts At this point, the device mounts itself, and the display on the mp3 player appears normal, with "Connected," instead of the dead "writing" state with F12. I thought I'd also attach my current config; I've re-installed using RC4, and still notice this unique behavior. For reference: [andrew@thinkpad ~]$ rpm -qa | egrep 'usb|kernel' | grep -v xorg | sort kernel-2.6.31.5-127.fc12.x86_64 kernel-firmware-2.6.31.5-127.fc12.noarch libusb-0.1.12-22.fc12.x86_64 libusb1-1.0.3-1.fc12.x86_64 usbutils-0.86-2.fc12.x86_64 Is it possible that libusb1 is at fault? Again, I've confirmed that the hardware works in 2 other distros (both pre libusb1, come to think of it) on the same hardware, so I am confident the issue is software related. This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping I've attempted to update to udev from testing-updates, and the mp3 player is still unrecognized upon hotplugging. I've grabbed live media from the newest ubuntu and openSUSE (as my suspicions were of libusb1), and my player was recognized and auto-mounted in each, so I still think that it's kernel, or a difference in udev rules. I've since updated to 2.6.31.6 in fedora, with no luck. This laptop also has a slackware64 installation; on my custom 2.6.32 kernel, completely vanilla, the mp3 player mounts perfectly with the same exact hardware/cable etc.: scsi 3:0:0:0: Direct-Access SanDisk Sansa Clip 1GB v01. PQ: 0 ANSI: 0 usb-storage: device scan complete sd 3:0:0:0: [sdb] 1986048 512-byte logical blocks: (1.01 GB/969 MiB) sd 3:0:0:0: [sdb] Write Protect is off sd 3:0:0:0: [sdb] Mode Sense: 04 00 00 00 sd 3:0:0:0: [sdb] Assuming drive cache: write through sd 3:0:0:0: [sdb] Assuming drive cache: write through sdb: sd 3:0:0:0: [sdb] Assuming drive cache: write through sd 3:0:0:0: [sdb] Attached SCSI removable disk This is completely specific to fedora's kernel, and not related at all to the hardware. Awesome, thanks for excluding the hardware with the help of the other kernel! May I get the usbmon traces from both 2.6.32 and 2.6.31.6? Comparing the two is bound to show us clearly what is afoot. I think it would be easiest to rebuild usbmon userland from source, available from my webpage. I am certain Slackware doesn't ship it. This way you don't need to tinker with debugfs and other painful stuff from ./Documentation/usb/usbmon.txt. http://people.redhat.com/zaitcev/linux/usbmon-5.4.tar.gz Hello Pete, Thanks for your comment. Unfortunately, after about a month and a half of waiting, I've removed my Fedora installation. I grew tired of rebooting liveCD's just to charge the MP3 player. This bug should be closed, as I won't be able to provide any more information. Thanks anyway. |