On Tue, Feb 17, 2015 at 5:50 PM, Sami Farin <hvtaifwkbgefbaei@xxxxxxxxx> wrote: > On Tue, Feb 17, 2015 at 17:32:40 +0100, Aleksander Morgado wrote: >> On Tue, Feb 17, 2015 at 4:32 PM, Sami Farin <hvtaifwkbgefbaei@xxxxxxxxx> wrote: >> > I have this USB ID 12d1:157d, Sonera Opengate LTE. >> > It says all is okay but no packets are moving. >> > With the SIM card in Lumia I get 50/25 Mbit/s. >> > >> > linux 3.19, Fedora 21, usb-modeswitch-2.2.1, usb_modeswitch-data 20150115, Asus P8Z68-V PRO GEN3, >> > NetworkManager-1.0.0-4.fc22, libmbim-1.12.0-1.fc22, ModemManager-1.4.4-1 >> > (tried USB 2 and USB 3 ports). >> > >> > In NetworkManager, setting "Use only 4G" does not work, it switches back to "Any". >> > >> >> That setting doesn't do anything any more with ModemManager 1.x. Plus, >> MBIM modems won't allow to lock e.g. to 4G-only, so that's why it >> always goes back to "Any". > > Maybe if some thing, like NetworkManager told that to me.. would be nice. > There are plans to remove that from the connection settings (where it currently is) and let e.g. the gnome-control-center be able to allow switching modes and capabilities directly (without being tied to a connection setting). > Dovado advertizes 4G bandlocking support [e.g. in their Pro model] for Huawei E3372, > I don't know what tricks they do.. > The modem supports it, sure; it's just the MBIM protocol the one which doesn't. There may be ways to do it, e.g. directly over AT commands using a TTY or embedding AT in MBIM. ModemManager won't do that (yet) when using MBIM, though. > ... >> > Saving state... (TRID: 6) >> > Attaching to packet service with 'mbimcli -d /dev/cdc-wdm0 --attach-packet-service --no-open=6 --no-close'... >> > Saving state... (TRID: 7) >> > Starting network with 'mbimcli -d /dev/cdc-wdm0 --connect= --no-open=7 --no-close'... >> > error: couldn't parse input string, missing arguments >> >> You didn't configure APN to use in mbim-network. You need to setup a >> /etc/mbim-network.conf file with the APN to use. > > Well, I am just trying all kinds of things, I have two weeks to test this > modem and return it if it does not work. > Besides, mbim-network does not seem to have documentation. > Yeah, no real docs for mbim-network; never thought it would end up being used that much. >> > Network start failed >> > [/dev/cdc-wdm0] Session not closed: TRID: '7' >> > Saving state... (TRID: 7) >> > >> > # mbim-network /dev/cdc-wdm0 status >> > Loading previous state... >> > Previous Transaction ID: 7 >> > Getting status with 'mbimcli -d /dev/cdc-wdm0 --query-connection-state --no-close --no-open=7'... >> > error: operation failed: Transaction timed out >> > Saving state... (TRID: 8) >> > error: couldn't get connection status >> > >> >> This is likely an error due to the leftover logic in mbim-network. > > I don't mind, if NetworkManager sets things correctly. > >> > >> > # mmcli -m 1 --simple-status >> > >> > /org/freedesktop/ModemManager1/Modem/1 >> > ------------------------- >> > Status | state: 'connected' >> > | signal quality: '80' (recent) >> > | bands: 'unknown' >> > | access tech: 'lte' >> > ------------------------- >> > 3GPP | registration: 'home' >> > | operator code: '24491' >> > | operator name: 'FI SONERA' >> > | subscription: 'unknown' >> > >> > >> >> That status looks ok in ModemManager. > > That's good. > Isn't there any debug features for CDC? I'd like to see something in dmesg > when I get 200 errors a second.. > Try to gather usbmon traces, that should help. -- Aleksander https://aleksander.es -- 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
