Thomas Schäfer <tschaefer@xxxxxxxxxxx> writes: > I tried this patch-set today, applied to linux-next-20120727. > > As the RFC "Fixing usb_wwan NULL pointer dereferencing" set from yesterday it > did help to avoid oopses while unplugging the stick. > > That is the good thing. > > But there is still a problem - wwan0 doesn't work. > > /dev/cdc-wdm0 answers to the cli-tool from libqmi. > > /dev/USBX answers to AT-commands via minicom. > > As with kernel 3.4 and 3.5 I use for connecting the "qmi-ifupdown" script > provided by Bjørn some months ago. > > But despite "VERBOSITY=true" and "IF_WWAN_DEBUG=1" I see nothing. > The script quits without output. Ah, right. I don't really use those scripts myself anymore. I just use the qmicli tool from libqmi. And I assume that works for you as well? I tried the script myself now, and the problem is that it makes a few stupid assumptions. The "usb" class has been renamed to "usbmisc" in linux-next. This breaks the script. You need to modify it accordingly. You really had me worried for a while there :-) > After that dhcpcd says only: > err, wwan0: timed out > warn, wwan0: using IPV4ALL address 169.254.41.53 > > The IPv6-variation of the scripts did not work too. Yeah, I guess you still have to use that script for IPv6 connections. That's not yet supported in libqmi. Bjørn -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
