udev: Issue with a rule for a PCIe 4G network deviceChange value of USB “max_sectors” for an entire...

Are there any low-level means to *exit* the Ethereal plane to a plane of my choosing?

Lípínguapua dopo Pêpê

Doesn't the speed of light limit imply the same electron can be annihilated twice?

Setting up a Mathematical Institute of Refereeing?

What should we do with manuals from the 80s?

Can the average speed of a moving body be 0?

What modifiers are added to the attack and damage rolls of this unique longbow from Waterdeep: Dragon Heist?

Go to last file in vim

Weird resistor with dots around it

Graphs for which a calculus student can reasonably compute the arclength

What unique challenges/limitations will I face if I start a career as a pilot at 45 years old?

Is there a fallacy about "appeal to 'big words'"?

What is the prop for Thor's hammer (Mjölnir) made of?

Number in overlapping range

How to prevent criminal gangs from making/buying guns?

Are there really no countries that protect Freedom of Speech as the United States does?

Is there a name for the technique in songs/poems, where the rhyming pattern primes the listener for a certain line, which never comes?

What is the opposite of "hunger level"?

Align rightarrow in table

Match 4 columns and replace 1 in 2 files

Is it OK to draw different current from L1 and L2 on NEMA 14-50?

Why does this Jet Provost strikemaster have a textured leading edge?

Is there a word for returning to unpreparedness?

The oceans and the moon



udev: Issue with a rule for a PCIe 4G network device


Change value of USB “max_sectors” for an entire family of devicesudev, how to prevent further rules to be run?Attributes from various parent devices in a udev ruleWrite udev rule from bitbake recipePersistent names for physical USB ports






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







1















The goal of my rule is having the network interface renamed from "eth0" (or whatever) to "gsm0" and to create a symlink /dev/ATCMD to /dev/ttyUSBX depending on the device we use to issue the AT commands.



I made this rule :



SUBSYSTEMS=="usb", ATTRS{bInterfaceNumber}!="02", GOTO="symlink_huaweiME909_end"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="15c1", SYMLINK+="ATCMD"
LABEL="symlink_huaweiME909_end"
SUBSYSTEM=="net", ACTION=="add", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="15c1", NAME="gsm0"


The renaming of the interface works great but for the symlink part, it's only working at boot. If I manually bring down the gsm0 interface and bring it up again, the symlink is not redirected to /dev/ttyUSBX anymore. It goes from :



lrwxrwxrwx  1 root root           7 Jan  1  1970 ATCMD -> ttyUSB0


to :



lrwxrwxrwx  1 root root          15 Aug 14 11:03 ATCMD -> bus/usb/001/006


The command udevadm info -a -p $(udevadm info -q path -n /dev/ttyUSB0) gives me :



  looking at device '/devices/platform/soc/3f980000.usb/usb1/1-1/1-1:2.2/ttyUSB0/tty/ttyUSB0':
KERNEL=="ttyUSB0"
SUBSYSTEM=="tty"
DRIVER==""

looking at parent device '/devices/platform/soc/3f980000.usb/usb1/1-1/1-1:2.2/ttyUSB0':
KERNELS=="ttyUSB0"
SUBSYSTEMS=="usb-serial"
DRIVERS=="option1"
ATTRS{port_number}=="0"

looking at parent device '/devices/platform/soc/3f980000.usb/usb1/1-1/1-1:2.2':
KERNELS=="1-1:2.2"
SUBSYSTEMS=="usb"
DRIVERS=="option"
ATTRS{interface}=="Huawei Mobile Connect - Modem"
ATTRS{bInterfaceProtocol}=="10"
ATTRS{bInterfaceNumber}=="02"
ATTRS{bInterfaceSubClass}=="06"
ATTRS{bInterfaceClass}=="ff"
ATTRS{bAlternateSetting}==" 0"
ATTRS{authorized}=="1"
ATTRS{bNumEndpoints}=="03"
ATTRS{supports_autosuspend}=="1"

looking at parent device '/devices/platform/soc/3f980000.usb/usb1/1-1':
KERNELS=="1-1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceClass}=="00"
ATTRS{rx_lanes}=="1"
ATTRS{manufacturer}=="Huawei Technologies Co., Ltd."
ATTRS{bmAttributes}=="a0"
ATTRS{bConfigurationValue}=="2"
ATTRS{version}==" 2.00"
ATTRS{devnum}=="2"
ATTRS{bMaxPower}=="2mA"
ATTRS{idProduct}=="15c1"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{urbnum}=="953"
ATTRS{bDeviceSubClass}=="00"
ATTRS{maxchild}=="0"
ATTRS{bcdDevice}=="0102"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{idVendor}=="12d1"
ATTRS{product}=="HUAWEI Mobile V7R11"
ATTRS{speed}=="480"
ATTRS{removable}=="unknown"
ATTRS{ltm_capable}=="no"
ATTRS{serial}=="0123456789ABCDEF"
ATTRS{bNumConfigurations}=="3"
ATTRS{busnum}=="1"
ATTRS{authorized}=="1"
ATTRS{tx_lanes}=="1"
ATTRS{quirks}=="0x0"
ATTRS{configuration}==""
ATTRS{devpath}=="1"
ATTRS{bDeviceProtocol}=="ff"
ATTRS{bNumInterfaces}==" 7"

looking at parent device '/devices/platform/soc/3f980000.usb/usb1':
KERNELS=="usb1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceClass}=="09"
ATTRS{rx_lanes}=="1"
ATTRS{manufacturer}=="Linux 4.19.57 dwc_otg_hcd"
ATTRS{bmAttributes}=="e0"
ATTRS{bConfigurationValue}=="1"
ATTRS{version}==" 2.00"
ATTRS{devnum}=="1"
ATTRS{bMaxPower}=="0mA"
ATTRS{idProduct}=="0002"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{urbnum}=="25"
ATTRS{bDeviceSubClass}=="00"
ATTRS{maxchild}=="1"
ATTRS{bcdDevice}=="0419"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{idVendor}=="1d6b"
ATTRS{product}=="DWC OTG Controller"
ATTRS{speed}=="480"
ATTRS{authorized_default}=="1"
ATTRS{interface_authorized_default}=="1"
ATTRS{removable}=="unknown"
ATTRS{ltm_capable}=="no"
ATTRS{serial}=="3f980000.usb"
ATTRS{bNumConfigurations}=="1"
ATTRS{busnum}=="1"
ATTRS{authorized}=="1"
ATTRS{tx_lanes}=="1"
ATTRS{quirks}=="0x0"
ATTRS{configuration}==""
ATTRS{devpath}=="0"
ATTRS{bDeviceProtocol}=="01"
ATTRS{bNumInterfaces}==" 1"


and some more things after this.



Thank you for your help!



EDIT1: This rule works perfectly on kernel 4.1 but has this issue on 4.19



"SOLUTION":
I reworked my rule as follow and it's working better. I still have some minor issues when I bring down the gsm0 interface.



SUBSYSTEMS=="usb", ATTRS{bInterfaceNumber}!="02", GOTO="symlink_huaweiME909_end"
SUBSYSTEM=="tty", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="15c1", SYMLINK+="ATCMD"
LABEL="symlink_huaweiME909_end"
SUBSYSTEM=="net", ACTION=="add", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="15c1", NAME="gsm0"









share|improve this question









New contributor



Carton_ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




























    1















    The goal of my rule is having the network interface renamed from "eth0" (or whatever) to "gsm0" and to create a symlink /dev/ATCMD to /dev/ttyUSBX depending on the device we use to issue the AT commands.



    I made this rule :



    SUBSYSTEMS=="usb", ATTRS{bInterfaceNumber}!="02", GOTO="symlink_huaweiME909_end"
    SUBSYSTEMS=="usb", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="15c1", SYMLINK+="ATCMD"
    LABEL="symlink_huaweiME909_end"
    SUBSYSTEM=="net", ACTION=="add", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="15c1", NAME="gsm0"


    The renaming of the interface works great but for the symlink part, it's only working at boot. If I manually bring down the gsm0 interface and bring it up again, the symlink is not redirected to /dev/ttyUSBX anymore. It goes from :



    lrwxrwxrwx  1 root root           7 Jan  1  1970 ATCMD -> ttyUSB0


    to :



    lrwxrwxrwx  1 root root          15 Aug 14 11:03 ATCMD -> bus/usb/001/006


    The command udevadm info -a -p $(udevadm info -q path -n /dev/ttyUSB0) gives me :



      looking at device '/devices/platform/soc/3f980000.usb/usb1/1-1/1-1:2.2/ttyUSB0/tty/ttyUSB0':
    KERNEL=="ttyUSB0"
    SUBSYSTEM=="tty"
    DRIVER==""

    looking at parent device '/devices/platform/soc/3f980000.usb/usb1/1-1/1-1:2.2/ttyUSB0':
    KERNELS=="ttyUSB0"
    SUBSYSTEMS=="usb-serial"
    DRIVERS=="option1"
    ATTRS{port_number}=="0"

    looking at parent device '/devices/platform/soc/3f980000.usb/usb1/1-1/1-1:2.2':
    KERNELS=="1-1:2.2"
    SUBSYSTEMS=="usb"
    DRIVERS=="option"
    ATTRS{interface}=="Huawei Mobile Connect - Modem"
    ATTRS{bInterfaceProtocol}=="10"
    ATTRS{bInterfaceNumber}=="02"
    ATTRS{bInterfaceSubClass}=="06"
    ATTRS{bInterfaceClass}=="ff"
    ATTRS{bAlternateSetting}==" 0"
    ATTRS{authorized}=="1"
    ATTRS{bNumEndpoints}=="03"
    ATTRS{supports_autosuspend}=="1"

    looking at parent device '/devices/platform/soc/3f980000.usb/usb1/1-1':
    KERNELS=="1-1"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{bDeviceClass}=="00"
    ATTRS{rx_lanes}=="1"
    ATTRS{manufacturer}=="Huawei Technologies Co., Ltd."
    ATTRS{bmAttributes}=="a0"
    ATTRS{bConfigurationValue}=="2"
    ATTRS{version}==" 2.00"
    ATTRS{devnum}=="2"
    ATTRS{bMaxPower}=="2mA"
    ATTRS{idProduct}=="15c1"
    ATTRS{avoid_reset_quirk}=="0"
    ATTRS{urbnum}=="953"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{maxchild}=="0"
    ATTRS{bcdDevice}=="0102"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{idVendor}=="12d1"
    ATTRS{product}=="HUAWEI Mobile V7R11"
    ATTRS{speed}=="480"
    ATTRS{removable}=="unknown"
    ATTRS{ltm_capable}=="no"
    ATTRS{serial}=="0123456789ABCDEF"
    ATTRS{bNumConfigurations}=="3"
    ATTRS{busnum}=="1"
    ATTRS{authorized}=="1"
    ATTRS{tx_lanes}=="1"
    ATTRS{quirks}=="0x0"
    ATTRS{configuration}==""
    ATTRS{devpath}=="1"
    ATTRS{bDeviceProtocol}=="ff"
    ATTRS{bNumInterfaces}==" 7"

    looking at parent device '/devices/platform/soc/3f980000.usb/usb1':
    KERNELS=="usb1"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{bDeviceClass}=="09"
    ATTRS{rx_lanes}=="1"
    ATTRS{manufacturer}=="Linux 4.19.57 dwc_otg_hcd"
    ATTRS{bmAttributes}=="e0"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{version}==" 2.00"
    ATTRS{devnum}=="1"
    ATTRS{bMaxPower}=="0mA"
    ATTRS{idProduct}=="0002"
    ATTRS{avoid_reset_quirk}=="0"
    ATTRS{urbnum}=="25"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{maxchild}=="1"
    ATTRS{bcdDevice}=="0419"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{idVendor}=="1d6b"
    ATTRS{product}=="DWC OTG Controller"
    ATTRS{speed}=="480"
    ATTRS{authorized_default}=="1"
    ATTRS{interface_authorized_default}=="1"
    ATTRS{removable}=="unknown"
    ATTRS{ltm_capable}=="no"
    ATTRS{serial}=="3f980000.usb"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{busnum}=="1"
    ATTRS{authorized}=="1"
    ATTRS{tx_lanes}=="1"
    ATTRS{quirks}=="0x0"
    ATTRS{configuration}==""
    ATTRS{devpath}=="0"
    ATTRS{bDeviceProtocol}=="01"
    ATTRS{bNumInterfaces}==" 1"


    and some more things after this.



    Thank you for your help!



    EDIT1: This rule works perfectly on kernel 4.1 but has this issue on 4.19



    "SOLUTION":
    I reworked my rule as follow and it's working better. I still have some minor issues when I bring down the gsm0 interface.



    SUBSYSTEMS=="usb", ATTRS{bInterfaceNumber}!="02", GOTO="symlink_huaweiME909_end"
    SUBSYSTEM=="tty", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="15c1", SYMLINK+="ATCMD"
    LABEL="symlink_huaweiME909_end"
    SUBSYSTEM=="net", ACTION=="add", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="15c1", NAME="gsm0"









    share|improve this question









    New contributor



    Carton_ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.
























      1












      1








      1








      The goal of my rule is having the network interface renamed from "eth0" (or whatever) to "gsm0" and to create a symlink /dev/ATCMD to /dev/ttyUSBX depending on the device we use to issue the AT commands.



      I made this rule :



      SUBSYSTEMS=="usb", ATTRS{bInterfaceNumber}!="02", GOTO="symlink_huaweiME909_end"
      SUBSYSTEMS=="usb", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="15c1", SYMLINK+="ATCMD"
      LABEL="symlink_huaweiME909_end"
      SUBSYSTEM=="net", ACTION=="add", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="15c1", NAME="gsm0"


      The renaming of the interface works great but for the symlink part, it's only working at boot. If I manually bring down the gsm0 interface and bring it up again, the symlink is not redirected to /dev/ttyUSBX anymore. It goes from :



      lrwxrwxrwx  1 root root           7 Jan  1  1970 ATCMD -> ttyUSB0


      to :



      lrwxrwxrwx  1 root root          15 Aug 14 11:03 ATCMD -> bus/usb/001/006


      The command udevadm info -a -p $(udevadm info -q path -n /dev/ttyUSB0) gives me :



        looking at device '/devices/platform/soc/3f980000.usb/usb1/1-1/1-1:2.2/ttyUSB0/tty/ttyUSB0':
      KERNEL=="ttyUSB0"
      SUBSYSTEM=="tty"
      DRIVER==""

      looking at parent device '/devices/platform/soc/3f980000.usb/usb1/1-1/1-1:2.2/ttyUSB0':
      KERNELS=="ttyUSB0"
      SUBSYSTEMS=="usb-serial"
      DRIVERS=="option1"
      ATTRS{port_number}=="0"

      looking at parent device '/devices/platform/soc/3f980000.usb/usb1/1-1/1-1:2.2':
      KERNELS=="1-1:2.2"
      SUBSYSTEMS=="usb"
      DRIVERS=="option"
      ATTRS{interface}=="Huawei Mobile Connect - Modem"
      ATTRS{bInterfaceProtocol}=="10"
      ATTRS{bInterfaceNumber}=="02"
      ATTRS{bInterfaceSubClass}=="06"
      ATTRS{bInterfaceClass}=="ff"
      ATTRS{bAlternateSetting}==" 0"
      ATTRS{authorized}=="1"
      ATTRS{bNumEndpoints}=="03"
      ATTRS{supports_autosuspend}=="1"

      looking at parent device '/devices/platform/soc/3f980000.usb/usb1/1-1':
      KERNELS=="1-1"
      SUBSYSTEMS=="usb"
      DRIVERS=="usb"
      ATTRS{bDeviceClass}=="00"
      ATTRS{rx_lanes}=="1"
      ATTRS{manufacturer}=="Huawei Technologies Co., Ltd."
      ATTRS{bmAttributes}=="a0"
      ATTRS{bConfigurationValue}=="2"
      ATTRS{version}==" 2.00"
      ATTRS{devnum}=="2"
      ATTRS{bMaxPower}=="2mA"
      ATTRS{idProduct}=="15c1"
      ATTRS{avoid_reset_quirk}=="0"
      ATTRS{urbnum}=="953"
      ATTRS{bDeviceSubClass}=="00"
      ATTRS{maxchild}=="0"
      ATTRS{bcdDevice}=="0102"
      ATTRS{bMaxPacketSize0}=="64"
      ATTRS{idVendor}=="12d1"
      ATTRS{product}=="HUAWEI Mobile V7R11"
      ATTRS{speed}=="480"
      ATTRS{removable}=="unknown"
      ATTRS{ltm_capable}=="no"
      ATTRS{serial}=="0123456789ABCDEF"
      ATTRS{bNumConfigurations}=="3"
      ATTRS{busnum}=="1"
      ATTRS{authorized}=="1"
      ATTRS{tx_lanes}=="1"
      ATTRS{quirks}=="0x0"
      ATTRS{configuration}==""
      ATTRS{devpath}=="1"
      ATTRS{bDeviceProtocol}=="ff"
      ATTRS{bNumInterfaces}==" 7"

      looking at parent device '/devices/platform/soc/3f980000.usb/usb1':
      KERNELS=="usb1"
      SUBSYSTEMS=="usb"
      DRIVERS=="usb"
      ATTRS{bDeviceClass}=="09"
      ATTRS{rx_lanes}=="1"
      ATTRS{manufacturer}=="Linux 4.19.57 dwc_otg_hcd"
      ATTRS{bmAttributes}=="e0"
      ATTRS{bConfigurationValue}=="1"
      ATTRS{version}==" 2.00"
      ATTRS{devnum}=="1"
      ATTRS{bMaxPower}=="0mA"
      ATTRS{idProduct}=="0002"
      ATTRS{avoid_reset_quirk}=="0"
      ATTRS{urbnum}=="25"
      ATTRS{bDeviceSubClass}=="00"
      ATTRS{maxchild}=="1"
      ATTRS{bcdDevice}=="0419"
      ATTRS{bMaxPacketSize0}=="64"
      ATTRS{idVendor}=="1d6b"
      ATTRS{product}=="DWC OTG Controller"
      ATTRS{speed}=="480"
      ATTRS{authorized_default}=="1"
      ATTRS{interface_authorized_default}=="1"
      ATTRS{removable}=="unknown"
      ATTRS{ltm_capable}=="no"
      ATTRS{serial}=="3f980000.usb"
      ATTRS{bNumConfigurations}=="1"
      ATTRS{busnum}=="1"
      ATTRS{authorized}=="1"
      ATTRS{tx_lanes}=="1"
      ATTRS{quirks}=="0x0"
      ATTRS{configuration}==""
      ATTRS{devpath}=="0"
      ATTRS{bDeviceProtocol}=="01"
      ATTRS{bNumInterfaces}==" 1"


      and some more things after this.



      Thank you for your help!



      EDIT1: This rule works perfectly on kernel 4.1 but has this issue on 4.19



      "SOLUTION":
      I reworked my rule as follow and it's working better. I still have some minor issues when I bring down the gsm0 interface.



      SUBSYSTEMS=="usb", ATTRS{bInterfaceNumber}!="02", GOTO="symlink_huaweiME909_end"
      SUBSYSTEM=="tty", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="15c1", SYMLINK+="ATCMD"
      LABEL="symlink_huaweiME909_end"
      SUBSYSTEM=="net", ACTION=="add", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="15c1", NAME="gsm0"









      share|improve this question









      New contributor



      Carton_ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      The goal of my rule is having the network interface renamed from "eth0" (or whatever) to "gsm0" and to create a symlink /dev/ATCMD to /dev/ttyUSBX depending on the device we use to issue the AT commands.



      I made this rule :



      SUBSYSTEMS=="usb", ATTRS{bInterfaceNumber}!="02", GOTO="symlink_huaweiME909_end"
      SUBSYSTEMS=="usb", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="15c1", SYMLINK+="ATCMD"
      LABEL="symlink_huaweiME909_end"
      SUBSYSTEM=="net", ACTION=="add", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="15c1", NAME="gsm0"


      The renaming of the interface works great but for the symlink part, it's only working at boot. If I manually bring down the gsm0 interface and bring it up again, the symlink is not redirected to /dev/ttyUSBX anymore. It goes from :



      lrwxrwxrwx  1 root root           7 Jan  1  1970 ATCMD -> ttyUSB0


      to :



      lrwxrwxrwx  1 root root          15 Aug 14 11:03 ATCMD -> bus/usb/001/006


      The command udevadm info -a -p $(udevadm info -q path -n /dev/ttyUSB0) gives me :



        looking at device '/devices/platform/soc/3f980000.usb/usb1/1-1/1-1:2.2/ttyUSB0/tty/ttyUSB0':
      KERNEL=="ttyUSB0"
      SUBSYSTEM=="tty"
      DRIVER==""

      looking at parent device '/devices/platform/soc/3f980000.usb/usb1/1-1/1-1:2.2/ttyUSB0':
      KERNELS=="ttyUSB0"
      SUBSYSTEMS=="usb-serial"
      DRIVERS=="option1"
      ATTRS{port_number}=="0"

      looking at parent device '/devices/platform/soc/3f980000.usb/usb1/1-1/1-1:2.2':
      KERNELS=="1-1:2.2"
      SUBSYSTEMS=="usb"
      DRIVERS=="option"
      ATTRS{interface}=="Huawei Mobile Connect - Modem"
      ATTRS{bInterfaceProtocol}=="10"
      ATTRS{bInterfaceNumber}=="02"
      ATTRS{bInterfaceSubClass}=="06"
      ATTRS{bInterfaceClass}=="ff"
      ATTRS{bAlternateSetting}==" 0"
      ATTRS{authorized}=="1"
      ATTRS{bNumEndpoints}=="03"
      ATTRS{supports_autosuspend}=="1"

      looking at parent device '/devices/platform/soc/3f980000.usb/usb1/1-1':
      KERNELS=="1-1"
      SUBSYSTEMS=="usb"
      DRIVERS=="usb"
      ATTRS{bDeviceClass}=="00"
      ATTRS{rx_lanes}=="1"
      ATTRS{manufacturer}=="Huawei Technologies Co., Ltd."
      ATTRS{bmAttributes}=="a0"
      ATTRS{bConfigurationValue}=="2"
      ATTRS{version}==" 2.00"
      ATTRS{devnum}=="2"
      ATTRS{bMaxPower}=="2mA"
      ATTRS{idProduct}=="15c1"
      ATTRS{avoid_reset_quirk}=="0"
      ATTRS{urbnum}=="953"
      ATTRS{bDeviceSubClass}=="00"
      ATTRS{maxchild}=="0"
      ATTRS{bcdDevice}=="0102"
      ATTRS{bMaxPacketSize0}=="64"
      ATTRS{idVendor}=="12d1"
      ATTRS{product}=="HUAWEI Mobile V7R11"
      ATTRS{speed}=="480"
      ATTRS{removable}=="unknown"
      ATTRS{ltm_capable}=="no"
      ATTRS{serial}=="0123456789ABCDEF"
      ATTRS{bNumConfigurations}=="3"
      ATTRS{busnum}=="1"
      ATTRS{authorized}=="1"
      ATTRS{tx_lanes}=="1"
      ATTRS{quirks}=="0x0"
      ATTRS{configuration}==""
      ATTRS{devpath}=="1"
      ATTRS{bDeviceProtocol}=="ff"
      ATTRS{bNumInterfaces}==" 7"

      looking at parent device '/devices/platform/soc/3f980000.usb/usb1':
      KERNELS=="usb1"
      SUBSYSTEMS=="usb"
      DRIVERS=="usb"
      ATTRS{bDeviceClass}=="09"
      ATTRS{rx_lanes}=="1"
      ATTRS{manufacturer}=="Linux 4.19.57 dwc_otg_hcd"
      ATTRS{bmAttributes}=="e0"
      ATTRS{bConfigurationValue}=="1"
      ATTRS{version}==" 2.00"
      ATTRS{devnum}=="1"
      ATTRS{bMaxPower}=="0mA"
      ATTRS{idProduct}=="0002"
      ATTRS{avoid_reset_quirk}=="0"
      ATTRS{urbnum}=="25"
      ATTRS{bDeviceSubClass}=="00"
      ATTRS{maxchild}=="1"
      ATTRS{bcdDevice}=="0419"
      ATTRS{bMaxPacketSize0}=="64"
      ATTRS{idVendor}=="1d6b"
      ATTRS{product}=="DWC OTG Controller"
      ATTRS{speed}=="480"
      ATTRS{authorized_default}=="1"
      ATTRS{interface_authorized_default}=="1"
      ATTRS{removable}=="unknown"
      ATTRS{ltm_capable}=="no"
      ATTRS{serial}=="3f980000.usb"
      ATTRS{bNumConfigurations}=="1"
      ATTRS{busnum}=="1"
      ATTRS{authorized}=="1"
      ATTRS{tx_lanes}=="1"
      ATTRS{quirks}=="0x0"
      ATTRS{configuration}==""
      ATTRS{devpath}=="0"
      ATTRS{bDeviceProtocol}=="01"
      ATTRS{bNumInterfaces}==" 1"


      and some more things after this.



      Thank you for your help!



      EDIT1: This rule works perfectly on kernel 4.1 but has this issue on 4.19



      "SOLUTION":
      I reworked my rule as follow and it's working better. I still have some minor issues when I bring down the gsm0 interface.



      SUBSYSTEMS=="usb", ATTRS{bInterfaceNumber}!="02", GOTO="symlink_huaweiME909_end"
      SUBSYSTEM=="tty", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="15c1", SYMLINK+="ATCMD"
      LABEL="symlink_huaweiME909_end"
      SUBSYSTEM=="net", ACTION=="add", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="15c1", NAME="gsm0"






      udev yocto






      share|improve this question









      New contributor



      Carton_ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.










      share|improve this question









      New contributor



      Carton_ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.








      share|improve this question




      share|improve this question








      edited yesterday







      Carton_













      New contributor



      Carton_ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.








      asked yesterday









      Carton_Carton_

      62 bronze badges




      62 bronze badges




      New contributor



      Carton_ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.




      New contributor




      Carton_ is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.



























          0






          active

          oldest

          votes














          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });






          Carton_ is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f535519%2fudev-issue-with-a-rule-for-a-pcie-4g-network-device%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          Carton_ is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          Carton_ is a new contributor. Be nice, and check out our Code of Conduct.













          Carton_ is a new contributor. Be nice, and check out our Code of Conduct.












          Carton_ is a new contributor. Be nice, and check out our Code of Conduct.
















          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f535519%2fudev-issue-with-a-rule-for-a-pcie-4g-network-device%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

          Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

          Ciclooctatetraenă Vezi și | Bibliografie | Meniu de navigare637866text4148569-500570979m