Hi all, I write this just as a confirm that no progress has been done with gsm_modem link issue... PS. Anyway good news: seems usb-linux developers are ready to merge my/our option.c patch. I'm not usual at submitting patches at all: this is my first patch... But after reading various documentation ...

Well, no log files referring to my huawei because it was in use (connected to internet on this same PC) when I installed new usb_modeswitch version... I had also removed all log files before reinstall. Anyway ttyUSB logs related to Huawei dongle were regularly created even before your last version.....

Ok, seems we have a little progress now! :) With that new version finally link_list file is filled with 2020:4000 ids... Although still no gsmmodem is created, nor any logs related to ttyUSB ports inquiring. # cat /var/lib/usb_modeswitch/link_list 2020:4000 # ls -l /dev/gs* /bin/ls: impossibile acce...

Well, I can just confirm there aren't any other log file... As well as I haven't any other line added to link_list file...

Unfortunately no expected changes... As usual follows log file: USB_ModeSwitch log from Mon May 18 23:51:32 CEST 2015 Use global config file: /etc/usb_modeswitch.conf Raw args from udev: /2-4.1 Use top device dir /sys/bus/usb/devices/2-4.1 Check class of first interface ... Interface class is 08. --...

Ah, If I well understood, we are in that case: first usb device interface has class "0x02", MBIM interface... and not 0xff (vendor specific). Let's take a look one more time to usb-devices output (copied from previous posts...): T: Bus=02 Lev=02 Prnt=04 Port=00 Cnt=01 Dev#= 11 Spd=480 MxCh...

Thank you! I didn't use a specific config file such as "/etc/usb_modeswitch.d/2020:0002" Instead I had edited "/usr/share/usb_modeswitch/2020:0002", but this one was replaced at re-install time so now I have: # cat /usr/share/usb_modeswitch/2020\:0002 # Mediatek MT6229, Micromax ...

Nope... I've noticed thoose files even before and contain just Huawei-E353 VId/PId (12d1:1506) # cat /var/lib/usb_modeswitch/bind_list 12d1:1506 [root@darkstar ~]# cat /var/lib/usb_modeswitch/link_list 12d1:1506 Nothing related to 2020:4000 Olicard ids. I thought usb_modeswitch had to automatically ...

$ grep sym /lib/udev/rules.d/40-usb_modeswitch.rules # Adds a symlink "gsmmodem[n]" to the lowest ttyUSB port with interrupt KERNEL=="ttyUSB*", ATTRS{bNumConfigurations}=="*", PROGRAM="usb_modeswitch --symlink-name %p %s{idVendor} %s{idProduct} %E{PRODUCT}", ...

I've tried it, but still no gsmmodem link is created... nor any ttyUSB logs in /var/

Ok, I've done a little patch... let me know if I well understood your suggest: # cat gsmmodem_symlink.patch --- usb-modeswitch-2.2.1/usb_modeswitch.tcl 2015-05-13 23:59:15.921409091 +0200 +++ usb_modeswitch.tcl 2015-05-14 00:06:12.796437393 +0200 @@ -736,7 +736,7 @@ proc {SymLinkName} {path} { -glob...

I understood, but the problem is how to edit dispatcher script...

I mean, I am still not able to understand why ttyUSB log files ar not created, and why no ttyUSB port is linked to a new /dev/gsmmodem_1 symlink...

That is the matter...

I'm using this slackware package: usb_modeswitch-2.2.1-i486-1" I've rebuilt it with Volkerding slackbuild... (changing $VERSION var etc...). Perhaps it is the make argument static that creates a binary version of dispatcher... The following commands are used by slackbuild script to compile usb_...

Logging was already enabled, but Olicard there aren't any ttyUSB related logs files in /var/log/. Let's clean all old logs: # rm /var/log/usb_modeswitch_* Then let's try to re-plugin olicard dongle... and see what dmesg reports. [ 8480.942782] usb 2-4.1: new high-speed USB device number 12 using ehc...

usb_modeswitch.sh wrapper recalls usb_modeswitch dispatcher as follows: --symlink-name) device_in "link_list" $v_id $p_id if [ "$?" = "1" ]; then if [ -e "/usr/sbin/usb_modeswitch_dispatcher" ]; then exec usb_modeswitch_dispatcher $1 $2 2>>/dev/null fi fi exit...