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



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




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]