The attached file is an extract from syslog that includes debug output from udev when I manually use usb_modeswitch to switch the K3520-Z's mode, i.e. when I issue the command
You will notice that initially there is a lot of activity removing the storage device that no longer exists. Then udev starts looking for rules for the new device. First it finds a matching entry in /lib/udev/rules.d/40-usb_modeswitch.rules at line 9. That line is
This is the rule that causes /lib/udev/usb_modeswitch to load the option driver if it not already loaded and to add the dongle to the devices managed by the option driver.
All of that activity would have appeared in the syslog extract in my previous comment if usb_modeswitch had successfully switched the dongle's mode at udev's instigation.
One other thing that you will find in the attached syslog extract is the following entry made by usb_modeswitch:
May 9 09:37:07 dell-desktop usb_modeswitch: switching device 19d2:2000 on 007/004
Bear this in mind when reading my next comment in which I shall show the extract from syslog that includes debug output from udev when the K3770 is connected to the system.
The attached file is an extract from syslog that includes debug output from udev when I manually use usb_modeswitch to switch the K3520-Z's mode, i.e. when I issue the command
usb_modeswitch --default-vendor 0x19d2 --default-product 0x2000 --message-content "55534243123456 780000000000000 61e000000000000 000000000000000 000" --message- content2= "55534243123456 790000000000000 61b000000020000 000000000000000 000" --message- content3= "55534243123456 702000000080000 c85010101180101 010101000000000 000" --need-response --target-vendor 0x19d2 --target-product 0x0055 -s 20 -D
You will notice that initially there is a lot of activity removing the storage device that no longer exists. Then udev starts looking for rules for the new device. First it finds a matching entry in /lib/udev/ rules.d/ 40-usb_ modeswitch. rules at line 9. That line is
KERNEL=="ttyUSB*", ATTRS{bNumConfi gurations} =="*", PROGRAM= "usb_modeswitch --symlink-name %p %s{idVendor} %s{idProduct} %E{PRODUCT}", SYMLINK="%c"
Then it finds another matching entry in /lib/udev/ rules.d/ 40-usb_ modeswitch. rules at line 16. That line is
ATTR{bInterface Class}= ="ff", ATTR{bInterface Number} =="00", ATTRS{bNumConfi gurations} =="*", RUN+="usb_ modeswitch --driver-bind %p %s{idVendor} %s{idProduct} %E{PRODUCT}"
This is the rule that causes /lib/udev/ usb_modeswitch to load the option driver if it not already loaded and to add the dongle to the devices managed by the option driver.
All of that activity would have appeared in the syslog extract in my previous comment if usb_modeswitch had successfully switched the dongle's mode at udev's instigation.
One other thing that you will find in the attached syslog extract is the following entry made by usb_modeswitch:
May 9 09:37:07 dell-desktop usb_modeswitch: switching device 19d2:2000 on 007/004
Bear this in mind when reading my next comment in which I shall show the extract from syslog that includes debug output from udev when the K3770 is connected to the system.