Bug 1263475
| Summary: | 7.1 no longer recognizes my cell phone | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Todd <ToddAndMargo> | ||||||||||||||
| Component: | usb_modeswitch | Assignee: | Lubomir Rintel <lrintel> | ||||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||||
| Priority: | medium | ||||||||||||||||
| Version: | 7.1 | CC: | aloughla, dcbw, harald, lmiksik, lrintel, mleitner, rkhan, thaller, ToddAndMargo, udev-maint-list, vbenes | ||||||||||||||
| Target Milestone: | rc | Keywords: | OtherQA, Rebase | ||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||
| OS: | Linux | ||||||||||||||||
| Whiteboard: | |||||||||||||||||
| Fixed In Version: | usb_modeswitch-2.4.0-5.el7 | Doc Type: | Bug Fix | ||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2016-11-04 08:31:35 UTC | Type: | Bug | ||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||
| Embargoed: | |||||||||||||||||
| Attachments: |
|
||||||||||||||||
$ rpm -qf /usr/sbin/ModemManager ModemManager-... oops.. sorry $ rpm -qfi /usr/lib/udev/mtp-probe Name : libmtp Hi Harald, My phone is configured as a "Mass Storage Device". Under Fedora 22 it gets a "/dev/sdx" entry when you plug it in. I don't know if you were asking me to run that command or not, but here it is anyway: $ rpm -qfi /usr/lib/udev/mtp-probe Name : libmtp Version : 1.1.6 Release : 3.el7 Architecture: x86_64 Install Date: Fri 21 Aug 2015 07:49:13 PM PDT Group : System Environment/Libraries Size : 471343 License : LGPLv2+ Signature : DSA/SHA1, Wed 14 May 2014 06:44:08 AM PDT, Key ID b0b4183f192a7d7d Source RPM : libmtp-1.1.6-3.el7.src.rpm Build Date : Fri 02 May 2014 03:40:00 PM PDT Build Host : swsvmsrv02.fnal.gov Relocations : (not relocatable) Packager : Scientific Linux Vendor : Scientific Linux URL : http://libmtp.sourceforge.net/ Summary : A software library for MTP media players Description : This package provides a software library for communicating with MTP (Media Transfer Protocol) media players, typically audio players, video players etc. (In reply to Todd from comment #4) > Hi Harald, > > My phone is configured as a "Mass Storage Device". Under Fedora 22 it gets > a "/dev/sdx" entry when you plug it in. That means it's not an MTP device. Are you sure it's not the phone that changed rather than the computer? > I don't know if you were asking me to run that command or not, but here it > is anyway: > > $ rpm -qfi /usr/lib/udev/mtp-probe No, he was mentioning that the helper wasn't part of udev, but libmtp. (In reply to Bastien Nocera from comment #5) > That means it's not an MTP device. Are you sure it's not the phone that > changed rather than the computer? Hi Bastien, I haven't done a firmware update on my phone since it was purchased. What changed was that I upgraded from SL 6.7 (where my phone worked) to SL 7.1 (where it stopped working). The upgrade was a full wipe and re-install. Would you like me to boot into my Fedora 22 USB (where it also works) and collect any data for you? -T still an issue under 7.2 Since this phone doesn't present itself as an MTP device, there's no fix in libmtp that would solve your problem. What's the output of: udevadm monitor -p when plugging the device in? Created attachment 1159031 [details]
udevadm monitor
Hi Bastien,
Still an issue under SL 7.2
I have attached the trace you requested. It contains both the "add" and the "remove" of the device
I will attach the same trace under Fedora Code 24 Beta tomorrow, where my phone is successfully recognized as a mass storage device
This bug has become somewhat of a pain in the neck. Thank you for looking into this! :-)
-T
(In reply to Todd from comment #9) > Created attachment 1159031 [details] > udevadm monitor > > Hi Bastien, > > Still an issue under SL 7.2 > > I have attached the trace you requested. It contains both the "add" and the > "remove" of the device I really don't want to see the remove of the device, it just makes it harder for me to see what the problem is. > I will attach the same trace under Fedora Code 24 Beta tomorrow, where my > phone is successfully recognized as a mass storage device The kernel seems to be finding the "hard disk" device node (/dev/sdc and /dev/sdd). You should be able to mount one of those through the "Disks" application ("gnome-disks" on the command-line). The problem might also have something to do with the usb_modeswitch program, as there's a "virtual disc" with Windows binaries appearing when plugging it in. Reassigning to usb_modeswitch for investigation there, as it's not a libmtp problem. You'll want to check that the disks can indeed be mounted with the disks app, and that the problem is just that it's not getting automounted. Created attachment 1159565 [details]
Fedora Core 24 udevmonitor
This is on Fedora Core 24 Beta, where my cell phone is recognized as a mass storage device
Created attachment 1159568 [details] /var/log/messages upon insert I am uploading that portion of /var/log/messages when the cell phone is inserted. I do believe the error message Write cache: enabled, read cache: enabled, doesn't support DPO or FUA may hold a clue. Also "fdisk -l" only shows my local drives. "ls -al /dev/sd*" shows only my local drives (If you notice sda and sdb reversed, that is bug # 1257018.) ls -al /dev/sd* brw-rw----. 1 root disk 8, 0 May 19 09:00 /dev/sda brw-rw----. 1 root disk 8, 1 May 19 09:00 /dev/sda1 brw-rw----. 1 root disk 8, 16 May 19 09:00 /dev/sdb brw-rw----. 1 root disk 8, 17 May 19 09:00 /dev/sdb1 brw-rw----. 1 root disk 8, 18 May 19 09:00 /dev/sdb2 brw-rw----. 1 root disk 8, 19 May 19 09:00 /dev/sdb3 brw-rw----. 1 root disk 8, 20 May 19 09:00 /dev/sdb4 brw-rw----. 1 root disk 8, 21 May 19 09:01 /dev/sdb5 So there is no where to manually mount this if I wanted to. Is there some other test you'd like me to run? And it does not recognize my wife's new Lenovo TAB 2 A10-70 either. Poop! There goes transferring music and pictures. :'( :'( :'( Additional info: Fedora Core 24 Beta run as a virtual machine (KVM) on this machine does recognize my cell phone. (In reply to Todd from comment #14) > Additional info: Fedora Core 24 Beta run as a virtual machine (KVM) on this > machine does recognize my cell phone. Hi. I'm wondering if usb_modeswitch amd usb_modeswitch-data packages installed and correct? (That would be the case if you chose "Dial-Up" group in installer -- should be default for Workstation installations). Please run "rpm -V usb_modeswitch usb_modeswitch-data" Hi Lubomir, "-V" did nothing, but "-qa" did. $ rpm -V usb_modeswitch usb_modeswitch-data <no rosponse> $ rpm -qa usb_modeswitch usb_modeswitch-data usb_modeswitch-data-20130807-2.el7.noarch usb_modeswitch-1.2.7-6.el7.x86_64 Additional info: SL7.2 does not recognize my wife's Android either. So much for transferring things. :'( If it helps, this is Fedora Core 24, wher my cell phone does work: $ rpm -qa usb_modeswitch usb_modeswitch-data usb_modeswitch-2.3.0-1.fc24.x86_64 usb_modeswitch-data-20160112-1.fc24.noarch EL7's usb_modeswitch is really, really out-of-date. Would you compile up a newer RPM for me to try? Hmmm; you have the necessary packages installed and according to attachment #1159568 [details] the usb_modeswitch gets called correctly. The rules for your device are there; but the phone doesn't switch anyway. Perhaps it's fixed in new usb_modeswitch; please give it a try: (In reply to Todd from comment #17) > EL7's usb_modeswitch is really, really out-of-date. Would you compile up a > newer RPM for me to try? You can get the updated packages from here: https://copr.fedorainfracloud.org/coprs/lkundrak/ModemManager/ (In reply to Todd from comment #16) > Additional info: SL7.2 does not recognize my wife's Android either. So > much for transferring things. :'( That would be the Lenovo TAB 2 A10-70? Logs would help. (In reply to Lubomir Rintel from comment #18) > (In reply to Todd from comment #17) > > EL7's usb_modeswitch is really, really out-of-date. Would you compile up a > > newer RPM for me to try? https://copr-be.cloud.fedoraproject.org/results/lkundrak/ModemManager/epel-7-x86_64/00360914-usb_modeswitch/usb_modeswitch-2.4.0-1.el7.centos.x86_64.rpm Corrected the issue with my camera. Yippee!. Thank you!!! Will you get it pumped into the regular repos? > > You can get the updated packages from here: > https://copr.fedorainfracloud.org/coprs/lkundrak/ModemManager/ > > (In reply to Todd from comment #16) > > Additional info: SL7.2 does not recognize my wife's Android either. So > > much for transferring things. :'( > > That would be the Lenovo TAB 2 A10-70? Logs would help. Yes it is. When I plug in the Tab 2, The Tab 2 gives me a configuration screen with the options of connecting as a 1) Media Device (MTP), or a 2) Camera (PTP), or 3) Build-in CDROM. CDROM is the only one that works. By logs, you mean Linux logs? I will attach what think you are after Created attachment 1177978 [details]
udevadm monitor -p > Tab2.PTP.txt 2>&1
Tab 2 A10-70 inserted in PTP mode
Created attachment 1177979 [details]
udevadm monitor -p > Tab2.MTP.txt 2>&1
Tab 2 A10-70 inserted in MTP mode
Created attachment 1177980 [details]
tab2 as seen in mesasages log
This is what it looks like in /var/log/messages when you active the Tab2 A10-70 as PTP and then switch to MTP
The Tab 2 A10-70 did not work under KVM and Fedora Core 24 either. And "udevadm monitor -p" was completely quiet, so maybe KVM wasn't working (KVM has "issues" with USB support). (In reply to Todd from comment #19) > (In reply to Lubomir Rintel from comment #18) > > (In reply to Todd from comment #17) > > > EL7's usb_modeswitch is really, really out-of-date. Would you compile up a > > > newer RPM for me to try? > > https://copr-be.cloud.fedoraproject.org/results/lkundrak/ModemManager/epel-7- > x86_64/00360914-usb_modeswitch/usb_modeswitch-2.4.0-1.el7.centos.x86_64.rpm > Corrected the issue with my camera. Yippee!. Thank you!!! > > Will you get it pumped into the regular repos? Yes. These will get into Red Hat Enterprise Linux 7.3 which is scheduled later this year. Thanks for the testing. > > (In reply to Todd from comment #16) > > > Additional info: SL7.2 does not recognize my wife's Android either. So > > > much for transferring things. :'( > > > > That would be the Lenovo TAB 2 A10-70? Logs would help. > > Yes it is. When I plug in the Tab 2, The Tab 2 gives me a configuration > screen with the options of connecting as a 1) Media Device (MTP), or a 2) > Camera (PTP), or 3) Build-in CDROM. CDROM is the only one that works. > > By logs, you mean Linux logs? I will attach what think you are after Yes, thanks for the logs. These don't need usb_modewsitch to switch the device to MTP mode, since it's already one by the device itself. What's missing is the TAB 2 A10-70 support in libmtp, which was only added in 1.1.11: https://sourceforge.net/p/libmtp/code/ci/193980978f28ce4c609d4e59077a4b3388470047/ I suggest you open a separate bug against "libmtp" for that one. Unfortunately, it's very unlikely to make it into 7.3, since it's already entering testing phase. Nevertheless there's a good chance the desktop is getting rebased for 7.4, so if you ask for a libmtp rebase there's a good chance the libmtp might be rebased too. For the immediate fix I suggest you just use the Fedora package (if you can't do the rebuild yourself, I can provide a build too). (In reply to Lubomir Rintel from comment #24) > (In reply to Todd from comment #19) > > By logs, you mean Linux logs? I will attach what think you are after > > Yes, thanks for the logs. > > These don't need usb_modewsitch to switch the device to MTP mode, since it's > already one by the device itself. What's missing is the TAB 2 A10-70 support > in libmtp, which was only added in 1.1.11: > > https://sourceforge.net/p/libmtp/code/ci/ > 193980978f28ce4c609d4e59077a4b3388470047/ > > I suggest you open a separate bug against "libmtp" for that one. > Unfortunately, it's very unlikely to make it into 7.3, since it's already > entering testing phase. Nevertheless there's a good chance the desktop is > getting rebased for 7.4, so if you ask for a libmtp rebase there's a good > chance the libmtp might be rebased too. > > For the immediate fix I suggest you just use the Fedora package (if you > can't do the rebuild yourself, I can provide a build too). I can not get the fedora 23 src rpm to rebuild. I would appreciate your build (In reply to Lubomir Rintel from comment #24) > I suggest you open a separate bug against "libmtp" for that one. Okay. https://bugzilla.redhat.com/show_bug.cgi?id=1356288 (In reply to Todd from comment #26) > I can not get the fedora 23 src rpm to rebuild. I would appreciate your > build You can use this one: https://copr-be.cloud.fedoraproject.org/results/lkundrak/ModemManager/epel-7-x86_64/00396620-libmtp/ Todd, any progress here? Does it work now? It has been working since I installed the patch on comment #28. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-2556.html |
Dear Red Hat, I am coming from the community: Scientific Linux 7.1 cat /etc/redhat-release Scientific Linux release 7.1 (Nitrogen) $ uname -r 3.10.0-229.11.1.el7.x86_64 Samsung Convoy 3, Model no.: SCH-u680 Would one of our intrepid heroes please fix this regression for me? SL 7.1 will no longer recognize my cell phone. Bummer. Photos of technical stuff from my travels in the field is part of my business. And, it is so, so annoying to have to shut everything down I am doing to boot into another operating system to retrieve my photos. My cell phone is configured for "Mass Storage Device" And my cell phone DOES work with both SL 6.7 AND Fedora Core 22 on the same computer (Live DVD/USB's). From my messages log, I do believe the money shot is: bus: 2, device: 6 was not an MTP device Then it tries to install my phone as a modem. Many thanks, -T Sep 15 13:52:55 localhost kernel: usb 2-4.4: new high-speed USB device number 6 using ehci-pci Sep 15 13:52:55 localhost kernel: usb 2-4.4: New USB device found, idVendor=04e8, idProduct=6640 Sep 15 13:52:55 localhost kernel: usb 2-4.4: New USB device strings: Mfr=3, Product=2, SerialNumber=0 Sep 15 13:52:55 localhost kernel: usb 2-4.4: Product: OEMSAMSUNG_Brew_SCH-U680 Sep 15 13:52:55 localhost kernel: usb 2-4.4: Manufacturer: SAMSUNG Electronics Co.,Ltd. Sep 15 13:52:55 localhost kernel: cdc_acm 2-4.4:1.0: ttyACM0: USB ACM device Sep 15 13:52:55 localhost mtp-probe: checking bus 2, device 6: "/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-4/2-4.4" Sep 15 13:52:55 localhost mtp-probe: bus: 2, device: 6 was not an MTP device Sep 15 13:52:58 localhost ModemManager[1302]: <info> Creating modem with plugin 'Generic' and '1' ports Sep 15 13:52:58 localhost ModemManager[1302]: <info> Modem for device at '/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-4/2-4.4' successfully created Sep 15 13:52:58 localhost ModemManager[1302]: <warn> couldn't load list of Own Numbers: 'Unknown error' Sep 15 13:52:58 localhost ModemManager[1302]: <info> Modem: state changed (unknown -> disabled) Sep 15 13:53:16 localhost fprintd: ** Message: No devices in use, exit