Description of problem: Via lsusb phone can be either identified as ID o5c6:1000 Qualcomm or ID 1004:6000 LG Electronics when hot plugging. Mostly as the Qualcomm device. Version-Release number of selected component (if applicable):DeviceKit-disks-devel-009-3.fc12 (x86_64) How reproducible: Every time. Steps to Reproduce: 1.Set phone as USB device. 2.Plug USB cable in. 3. Actual results: Cannot access USB files on phone. Palimpsest does not list the device. Expected results: Access USB files. Additional info:If computer is started with phone connected, bootup hangs. Looks like gdm never starts or fails.
and why is this a udev problem?
can you run # udevadm control --log-priority=debug and then plug in the phone and attach the udev messages in /var/log/messages
Might be udev, might be kernel, not sure. But it's not DeviceKit, as that's dead.
Created attachment 388617 [details] Messages from udevadm control --log-priority=debug
I filed this bug against DeviceKit because the phone worked fine in F10. After I upgraded to F12, no phone. No joy from the forums, so I assumed that udev was missing a rule. So I decided to write my own. While researching how to do that I learned about DeviceKit. Aha! No DeviceKit in F10. DeviceKit is in F12. So I figured DeviceKit must be the chigger in the woodpile. If I'm wrong, then my apologies to the fine gentleman working on DeviceKit!
udev does: /sbin/modprobe -b usb:v05C6p1000d0000dc00dsc00dp00ic08isc06ip50 modem-modeswitch -v 0x05c6 -p 0x1000 -t option-zerocd you could try to comment out the modeswitch command in /lib/udev/rules.d/61-option-modem-modeswitch.rules
you might also want to play with usb_modeswitch
I commented that line in /lib/udev/rules.d/61-option-modem-modeswitch.rules and that seems to have done the trick while hotplugging. Icon comes up on the desktop and Palimpsest can see the drive. Still have the problem of boot hanging while the phone is connected at start-up but I can live with that. Thanks!
The problem here is that this USB ID is *also* the USB ID of a popular Option NV 3G modem (the iCON 7.2) before the modem is modeswitched. So even if you move to usb_modeswitch, you'll still have the problem where the LG phone is modeswitched by usb_modeswitch most likely. Qualcomm makes the chipset that's in both the LG phone and the Option NV modem, and apparently both vendors didnt' bother to change the USB ID before the modeswitch occurs. So we have two hugely different devices with the same pre-switch USB ID.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.