Re: OpenWRT - MC7455 (MBIM) not working as expected.
I'll try OpenWrt again when the kernel hits 4.4.16... not sure if/when that will happen. This (https://itunes.apple.com/app/apple-store/id922793622?pt=814382=8=how_i_email) is how I Email now > > On Jan 26, 2017 at 8:49 AM, (mailto:aleksan...@aleksander.es)> wrote: > > > > On Thu, Jan 26, 2017 at 2:38 PM, Bjørn Mork(mailto:bj...@mork.no)> wrote: > >> I built LEDE (kernel 4.4.42) with MM, and it is working in MBIM mode. > >> wwan > >> interface is assigned an address as before, but, this time the internet > >> is > >> reachable. > > > > Great! Thanks for testing this. > > > Nice! > > -- > Aleksander > https://aleksander.es > ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: OpenWRT - MC7455 (MBIM) not working as expected.
LEDE kernel for my particular device is 4.4.42, I'll try to compile with MM in the next day or two and report my findings. Clearly it is not an issue on Ubuntu 16.10. This (https://itunes.apple.com/app/apple-store/id922793622?pt=814382=8=how_i_email) is how I Email now > > On Jan 25, 2017 at 3:17 PM,wrote: > > > > Aleksander Morgado (mailto:aleksan...@aleksander.es)> writes: > > On Wed, Jan 25, 2017 at 6:49 PM (x-apple-data-detectors://2), Mark > > Wahlert wrote: > >> Did you have an opportunity to check which kernel version you've had MBIM > >> > >> working with successfully? > > > > I tested with 4.4.14. Maybe I was just lucky enough to be testing with > > a slow system and I didn't hit the bug fixed by Bjørn's patch? > > Note that I never noticed this issue on my previous laptop (a 2008 model > Thinkpad X301), and it wasn't *that* slow :) > > But I could just have been lucky because I had every possible debug > message enabled, and the "fix" is simply a very short additional delay > during probing. You don't need to add much extra code there to achieve > the same effect. > > The reason I brought it up, is that I saw another report of similar > failure on a Linksys WRT1900ACS recently. So I'm open for the thought > that newer wifi routers are powerful enough to make it a problem. I > didn't initially believe so. > > Anyway, I'm really curious to know if the patch solves the problem. > Because I'm still not certain that this is the case. > > > Bjørn >___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: OpenWRT - MC7455 (MBIM) not working as expected.
Aleksander Morgadowrites: > On Wed, Jan 25, 2017 at 6:49 PM, Mark Wahlert wrote: >> Did you have an opportunity to check which kernel version you've had MBIM >> working with successfully? > > I tested with 4.4.14. Maybe I was just lucky enough to be testing with > a slow system and I didn't hit the bug fixed by Bjørn's patch? Note that I never noticed this issue on my previous laptop (a 2008 model Thinkpad X301), and it wasn't *that* slow :) But I could just have been lucky because I had every possible debug message enabled, and the "fix" is simply a very short additional delay during probing. You don't need to add much extra code there to achieve the same effect. The reason I brought it up, is that I saw another report of similar failure on a Linksys WRT1900ACS recently. So I'm open for the thought that newer wifi routers are powerful enough to make it a problem. I didn't initially believe so. Anyway, I'm really curious to know if the patch solves the problem. Because I'm still not certain that this is the case. Bjørn ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: OpenWRT - MC7455 (MBIM) not working as expected.
On Wed, Jan 25, 2017 at 6:49 PM, Mark Wahlertwrote: > Did you have an opportunity to check which kernel version you've had MBIM > working with successfully? I tested with 4.4.14. Maybe I was just lucky enough to be testing with a slow system and I didn't hit the bug fixed by Bjørn's patch? -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: OpenWRT - MC7455 (MBIM) not working as expected.
Did you have an opportunity to check which kernel version you've had MBIM working with successfully? Thanks! This (https://itunes.apple.com/app/apple-store/id922793622?pt=814382=8=how_i_email) is how I Email now > > On Jan 24, 2017 at 8:57 AM, (mailto:aleksan...@aleksander.es)> wrote: > > > > On Tue, Jan 24, 2017 at 2:30 PM, Bjørn Mork(mailto:bj...@mork.no)> wrote: > >> Aleksander - have you had the mc7455 working in OpenWrt in MBIM? > > > > Yes; I had it working, although I should check which kernel version I > was running. Will do that later today. > > > Just a side note: It might work without the "fix" I referred to, > > depending on the speed of the host hardware. It will work fine on a > > slow router, but fail on a fast one. The exact meaning of "fast" and > > "slow" is not known. > > > > Yes, it's yucky. > > What would you call an old Raspberry Pi B? > > -- > Aleksander > https://aleksander.es > ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: OpenWRT - MC7455 (MBIM) not working as expected.
On Tue, Jan 24, 2017 at 2:30 PM, Bjørn Morkwrote: >> Aleksander - have you had the mc7455 working in OpenWrt in MBIM? > Yes; I had it working, although I should check which kernel version I was running. Will do that later today. > Just a side note: It might work without the "fix" I referred to, > depending on the speed of the host hardware. It will work fine on a > slow router, but fail on a fast one. The exact meaning of "fast" and > "slow" is not known. > > Yes, it's yucky. What would you call an old Raspberry Pi B? -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: OpenWRT - MC7455 (MBIM) not working as expected.
Mark Wahlertwrites: > Aleksander - have you had the mc7455 working in OpenWrt in MBIM? Just a side note: It might work without the "fix" I referred to, depending on the speed of the host hardware. It will work fine on a slow router, but fail on a fast one. The exact meaning of "fast" and "slow" is not known. Yes, it's yucky. Bjørn ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: OpenWRT - MC7455 (MBIM) not working as expected.
I've explicitly defined the apn in /etc/config/network. I will try to compile LEDE. Aleksander - have you had the mc7455 working in OpenWrt in MBIM? This (https://itunes.apple.com/app/apple-store/id922793622?pt=814382=8=how_i_email) is how I Email now > > On Jan 24, 2017 at 8:12 AM,wrote: > > > > Mark Wahlert > writes: > > > I've built OpenWrt from trunk so I'm not sure that 4.4.16 is an > > option? You guys would know better than me. > > OpenWrt isn't very up-to-date at the momemt. You'll have to change the > kernel version yourself, or use LEDE. > > > In MBIM wwan gets an IP (from a completely different subnet than when > > in QMI mode), but I'm unable to reach the internet. > > Maybe you are using different APNs in MBIM and QMI mode? This could > easily happen if you depend on defaults in either mode. You should > always explicitly name the APN you want to connect to. > > > Bjørn > ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: OpenWRT - MC7455 (MBIM) not working as expected.
Mark Wahlertwrites: > I've built OpenWrt from trunk so I'm not sure that 4.4.16 is an > option? You guys would know better than me. OpenWrt isn't very up-to-date at the momemt. You'll have to change the kernel version yourself, or use LEDE. > In MBIM wwan gets an IP (from a completely different subnet than when > in QMI mode), but I'm unable to reach the internet. Maybe you are using different APNs in MBIM and QMI mode? This could easily happen if you depend on defaults in either mode. You should always explicitly name the APN you want to connect to. Bjørn ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: OpenWRT - MC7455 (MBIM) not working as expected.
I've built OpenWrt from trunk so I'm not sure that 4.4.16 is an option?You guys would know better than me. In MBIM wwan gets an IP (from a completely different subnet than when in QMI mode), but I'm unable to reach the internet. This (https://itunes.apple.com/app/apple-store/id922793622?pt=814382=8=how_i_email) is how I Email now > > On Jan 24, 2017 at 7:51 AM,wrote: > > > > Aleksander Morgado (mailto:aleksan...@aleksander.es)> writes: > > > Hey, > > > > [1485259217.322211] [mm-bearer-mbim.c:319] > > ip_configuration_query_ready(): IPv4 configuration available: > > 'address, gateway, dns, mtu' > > [1485259217.322293] [mm-bearer-mbim.c:325] > > ip_configuration_query_ready(): IP addresses (1) > > [1485259217.322813] [mm-bearer-mbim.c:329] > > ip_configuration_query_ready(): IP [0]: '25.32.16.100/29' > > [1485259217.322992] [mm-bearer-mbim.c:338] > > ip_configuration_query_ready(): Gateway: '25.32.16.101' > > [1485259217.323082] [mm-bearer-mbim.c:346] > > ip_configuration_query_ready(): DNS addresses (2) > > [1485259217.323212] [mm-bearer-mbim.c:351] > > ip_configuration_query_ready(): DNS [0]: '68.28.104.132' > > [1485259217.323363] [mm-bearer-mbim.c:351] > > ip_configuration_query_ready(): DNS [1]: '68.28.105.132' > > [1485259217.323455] [mm-bearer-mbim.c:359] > > ip_configuration_query_ready(): MTU: '1500' > > [1485259217.323524] [mm-bearer-mbim.c:365] > > ip_configuration_query_ready(): IPv6 configuration available: 'none' > > [1485259217.323961] [mm-port.c:94] mm_port_set_connected(): > > (wwan0): port now connected > > > > It all looks good here. > > > > Didn't you get the wwan network interface configured with those settings? > > Note that the backport of 61f602d84a60 ("cdc_ncm: workaround for EM7455 > "silent" data interface") went into v4.4.16. So v4.4.14 might just be > slightly too old to work with the MC7455. > > The current 4.4 stable release is v4.4.44. And as Greg so mildly puts > it: "All users of the 4.4 kernel series must upgrade.". > > Worth trying. At least if the problem is that the MC7455 cannot send or > receive any IP packets after successfully connecting. > > > > Bjørn > ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: OpenWRT - MC7455 (MBIM) not working as expected.
On Mon, Jan 23, 2017 at 3:10 PM, Aleksander Morgadowrote: > It would also be a good idea to retrieve ModemManager debug logs; you > can modify the MM daemon init file and add --debug > --log-file=/var/log/mm.log to get them. I realize this may not be very clear. In the case of the procd init file, adding the options is done with "procd_append_param" as follows: # vim /etc/init.d/modemmanager ... procd_set_param command /usr/sbin/ModemManager procd_append_param command --log-file=/var/log/mm.log procd_append_param command --debug -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: OpenWRT - MC7455 (MBIM) not working as expected.
Hey, On Mon, Jan 23, 2017 at 2:20 PM, Mark Wahlertwrote: > Hello. I've built OpenWrt from trunk (Kernel 4.4.14) including ModemManager > and its dependencies. > > With my mc7455 in QMI mode, PPP interface is established and the internet is > accessible. > > With modem in MBIM mode, expected interface (not PPP) is brought online - > although strangely with an IP from an entirely different network (than when > in QMI), and the internet is not reachable. > > Please bear with me - I'm new to all of this. Some outputs attached: > > Found 1 modems: > /org/freedesktop/ModemManager1/Modem/0 [Sierra] MBIM [1199:9071] > > /org/freedesktop/ModemManager1/Modem/0 (device id > '1404de2498fc8078e94bc55ab5ac5e4872bbf081') > - > Hardware | manufacturer: 'Sierra' >| model: 'MBIM [1199:9071]' >| revision: 'SWI9X30C_02.20.03.00' >| supported: 'gsm-umts, lte' >|current: 'gsm-umts, lte' >| equipment id: 'XX' > - > System | device: > '/sys/devices/platform/ehci-platform.1/usb2/2-1' >|drivers: 'che l' >| plugin: 'Sierra' >| primary port: 'cdc-wdm0' >| ports: 'ttyUSB0 (qcdm), ttyUSB1 (at), cdc-wdm0 (mbim), > wwan0 (net)' > - > Numbers | own : 'unknown' > - > Status | lock: 'none' >| unlock retries: 'sim-pin2 (3)' >| state: 'registered' >|power state: 'on' >|access tech: 'lte' >| signal quality: '19' (cached) > - > Modes| supported: 'allowed: 3g, 4g; preferred: none' >|current: 'allowed: 3g, 4g; preferred: none' > - > Bands| supported: 'unknown' >|current: 'unknown' > - > IP | supported: 'ipv4, ipv6, ipv4v6' > - > 3GPP | imei: 'X' >| enabled locks: 'fixed-dialing' >|operator id: '310120' >| operator name: 'Sprint' >| subscription: 'unknown' >| registration: 'home' > - > SIM | path: '/org/freedesktop/ModemManager1/SIM/0' > > - > Bearers | paths: '/org/freedesktop/ModemManager1/Bearer/4' > > config interface 'wwan' > option device '/sys/devices/platform/ehci-platform.1/usb2/2-1' > option proto 'modemmanager' > option apn 'X.XX.X' > option lowpower '1' > > wwan0 Link encap:Ethernet HWaddr 5A:60:06:DC:00:57 > inet addr:XX.XX.XXX.XX Bcast:XX.XX.XXX.XX Mask:255.255.255.252 > inet6 addr: fe80::5860:6ff:fedc:57/64 Scope:Link > UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:817 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:51020 (49.8 KiB) > > default via XX.XX.XXX.XX dev wwan0 src XX.XX.XXX.XX > XX.XX.XXX.XX/29 dev wwan0 src XX.XX.XXX.XX > > For comparison sake - the modem works as expected in both QMI and MBIM mode > on Ubuntu 16.10 which has raw-ip support in the updated qmi_wwan driver. > I'd still expect OpenWrt with kernel 4.4 to work properly in MBIM. > > Thank you for any help you can provide. It looks like "mmcli" is saying the modem is "registered" (i.e. not connected). Could you also validate that by checking the bearer info, e.g. "mmcli -b 4"? Maybe the modem was connected briefly and then we didn't handle a network disconnection properly, or something. It would also be a good idea to retrieve ModemManager debug logs; you can modify the MM daemon init file and add --debug --log-file=/var/log/mm.log to get them. -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
