Re: Fwd: D-bus devices cannot produced by NetworkManager when Huawei EM660 Module already is in

[Bluesky_greenleaf <trojanwei gmail com>]

Hi Dan,

Thank you! but it can not fix this problem after trying the following commands such as the usb_modeswitch, udevadm trigger  , the D-BUS for the HW device /org/freedesktop/NetworkManager/Devices/2  is still not coming out.  Notice this 3G device doesnot have the Verizon account

Thanks




~$ sudo usb_modeswitch -v 012d1 -p 1404 -P 1404 

 * usb_modeswitch: tool for controlling "flip flop" mode USB devices
 * Version 1.0.2 (C) Josua Dietze 2009
 * Works with libusb 0.1.12 and probably other versions

Looking for default devices ...
 Found default devices (1)
Accessing device 002 on bus 003 ...
Using endpoints 0x02 (out) and 0x82 (in)
Not a storage device, skipping SCSI inquiry

Device description data (identification)
-------------------------
Manufacturer: HUA�WEI TECHNOLOGIES
     Product: HUAWEI Mobile
  Serial No.: �������������������
-------------------------
Warning: no switching method given.
-> Run lsusb to note any changes. Bye.

$ lsusb
Bus 007 Device 002: ID 04eb:e033 Northstar Systems, Inc. 
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0bda:0151 Realtek Semiconductor Corp. Mass Stroage Device
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 006: ID 050d:705e Belkin Components 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 413c:3016 Dell Computer Corp. Optical 5-Button Wheel Mouse
Bus 004 Device 003: ID 413c:2106 Dell Computer Corp. 
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 12d1:1404 Huawei Technologies Co., Ltd. 
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

On Fri, Mar 5, 2010 at 11:27 PM, Dan Williams <dcbw redhat com> wrote:

On Tue, 2010-03-02 at 10:12 -0800, Bluesky_greenleaf wrote:
>
> Thanks,
> But already try
> sudo udevadm trigger --subsystem-match usb --property-match
> DEVTYPE=usb_device --attr-match idVendor=12d1 --attr-match
> idProduct=1404
> is not useful,D-bus  /org/freedesktop/NetworkManager/Devices/2 is not
> produced.
>
> the conent  of /lib/udev/rules.d/61-option-modem-modeswitch.rules as
> follows,
> ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1404", RUN
> +="modem-modeswitch -v 0x%s{idVendor} -p 0x%s{idProduct} -t
> option-zerocd" is already added, but is also not useful

actually, you want to remove that line as it can cause problems with
Huawei devices.  It was added incorrectly to upstream udev, and has
since been removed.  If you remove that line, and use usb_modeswitch
instead, does that fix the issue?

Dan

>
> ACTION!="add", GOTO="option_zerocd_end"
> SUBSYSTEM=="usb", ATTR{bDeviceClass}!="ff",
> ENV{DEVTYPE}=="usb_device", GOTO="option_zerocd_disable"
> SUBSYSTEM=="scsi", ENV{DEVTYPE}=="scsi_device",
> GOTO="option_zerocd_disable"
> GOTO="option_zerocd_end"
>
> LABEL="option_zerocd_disable"
>
> ATTRS{idVendor}=="0af0", ATTRS{idProduct}=="6911", RUN
> +="modem-modeswitch -v 0x%s{idVendor} -p 0x%s{idProduct} -t
> option-zerocd"
> .....
> .....
> ATTRS{idVendor}=="0af0", ATTRS{idProduct}=="d033", RUN
> +="modem-modeswitch -v 0x%s{idVendor} -p 0x%s{idProduct} -t
> option-zerocd"
> ATTRS{idVendor}=="0af0", ATTRS{idProduct}=="7301", RUN
> +="modem-modeswitch -v 0x%s{idVendor} -p 0x%s{idProduct} -t
> option-zerocd"
> ATTRS{idVendor}=="0af0", ATTRS{idProduct}=="7361", RUN
> +="modem-modeswitch -v 0x%s{idVendor} -p 0x%s{idProduct} -t
> option-zerocd"
> ATTRS{idVendor}=="0af0", ATTRS{idProduct}=="7401", RUN
> +="modem-modeswitch -v 0x%s{idVendor} -p 0x%s{idProduct} -t
> option-zerocd"
> ATTRS{idVendor}=="0af0", ATTRS{idProduct}=="7501", RUN
> +="modem-modeswitch -v 0x%s{idVendor} -p 0x%s{idProduct} -t
> option-zerocd"
> ATTRS{idVendor}=="0af0", ATTRS{idProduct}=="7601", RUN
> +="modem-modeswitch -v 0x%s{idVendor} -p 0x%s{idProduct} -t
> option-zerocd"
> ATTRS{idVendor}=="0af0", ATTRS{idProduct}=="7901", RUN
> +="modem-modeswitch -v 0x%s{idVendor} -p 0x%s{idProduct} -t
> option-zerocd"
> ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1446", RUN
> +="modem-modeswitch -v 0x%s{idVendor} -p 0x%s{idProduct} -t
> option-zerocd"
>
>
> LABEL="option_zerocd_end"
>
>
>
> On Mon, Mar 1, 2010 at 11:33 PM, Dan Williams <dcbw redhat com> wrote:
>
>         On Tue, 2010-03-02 at 06:57 +0300, Andrey Borzenkov wrote:
>         > On Tuesday 02 of March 2010 05:12:35 Wei wrote:
>         > > One questions:
>         > >
>         > > When the HuaWei EM660 CDMA card is already inserted into
>         PC, that is
>         > > $ls /dev/ttyUSB*
>         > > /dev/ttyUSB0  /dev/ttyUSB1  /dev/ttyUSB2  /dev/ttyUSB3
>          /dev/ttyUSB4
>         > > the /dev/ttyUSB1  /dev/ttyUSB2  /dev/ttyUSB3  /dev/ttyUSB4
>         for CDMA
>         > > USB modem of EM660
>         > >
>         > > if the card is pluged out, then plugged into the PC,
>         > > the NetworkManger can detect, and report a new D-bus
>         device, for
>         > > examples, /org/freedesktop/NetworkManager/Devices/2.
>         > >
>         > > But if the reboot the PC, the card is still in the PC, no
>         the action
>         > > of plug out and in,
>         > > NetworkManger cannot the produce the D-BUS
>         > > /org/freedesktop/NetworkManager/Devices/2.
>         > >
>         > > also
>         > > $sudo usb_modeswitch -v 012d1 -p 1404 -P 1404
>         > > $modprobe usbserial vendor=0x12d1 produce=xxxxx
>         > > has done, it is not useful.
>         > >
>         > > Why? If the action of plugging in and out is not done, how
>         can write
>         > > the script to realize it to produce card D-bus
>         > > /org/freedesktop/NetworkManager/Devices/2 ?
>         > >
>         >
>         > Try (as root)
>         >
>         > udevadm trigger --subsystem-match usb --property-match
>         > DEVTYPE=usb_device --attr-match idVendor=12d1 --attr-match
>         > idProduct=1404
>         >
>         > (this is one line of course).
>
>
>         One more check:  what is the contents of this file?
>
>         /lib/udev/rules.d/61-option-modem-modeswitch.rules
>
>         Upstream udev carried a rule there for a while which could
>         negatively
>         impact Huawei and ZTE devices, which has since been removed
>         after we
>         found out it was wrong.
>
>
>         Dan
>
>
>         _______________________________________________
>         NetworkManager-list mailing list
>         NetworkManager-list gnome org
>         http://mail.gnome.org/mailman/listinfo/networkmanager-list
>
>
>
>
> _______________________________________________
> NetworkManager-list mailing list
> NetworkManager-list gnome org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list