MC7455 not working
Steven Pease
spease at suitabletech.com
Wed Mar 23 10:06:27 UTC 2016
Hi Aleksander,
I used Arch Build System to grab the existing package builds of libqmi and
ModemManager and built 1.14 and 1.5.990 respectively from
https://www.freedesktop.org/software/. I still got similar output using
kernel 4.4.5.
I then tried installing linux-mainline which on Arch is kernel 4.5. After
running simple-connect, I noticed "mmcli -b 0" indicated the wwp0s29f7u5i8
interface and an IPv4 configuration of dhcp with IP address, gateway, etc.
I could not get a dhcp client to work, but manually setting an address with
"ip addr" and doing a ping through the interface with "ping -i
wwp0s29f7u5i8 8.8.8.8" did yield results. Is this the correct behavior?
>From googling around I found this:
https://mail.gnome.org/archives/networkmanager-list/2015-December/msg00042.html
I guess this means that MC7455 will only work in kernel 4.5 due to better
raw-ip support?
Thanks.
- Steven
On Tue, Mar 22, 2016 at 12:57 AM, Aleksander Morgado <
aleksander at aleksander.es> wrote:
> Hey Steven,
>
>
> On Tue, Mar 22, 2016 at 6:44 AM, Steven Pease <spease at suitabletech.com>
> wrote:
> > Hi,
> > I'm trying to get the MC7455 working with kernel 4.4.5 or 4.4.6. My
> > workstation is running Arch which is using kernel 4.4.5 and
> > ModemManager 1.4.12. In the following, the modem is the only modem on
> > the system at index 1 since this is the second try following a reboot.
> >
> > I'm trying to get an internet connect (IPV4) going over the modem. The
> > IMEI and Phone # appear to be correct although I've X'd them out.
>
> You won't be able to get a proper connection unless you use
> ModemManager from git master or the new 1.6-rc1 tagged last week. This
> is because the MC7455 requires the "raw-ip" only setup.
>
> BUT not having that newer MM isn't the only issue. See below.
>
> >
> > $ mmcli -m 1
> > /org/freedesktop/ModemManager1/Modem/1 (device id
> > '3abb9e13c07a07a53a0e4f5881b52cd195f21502')
> > -------------------------
> > Hardware | manufacturer: 'Sierra Wireless, Incorporated'
> > | model: 'MC7455'
> > | revision: 'SWI9X30C_02.04.07.00 r4823
> > CARMD-EV-FRMWR2 2015/11/04 06:51:37'
> > | supported: 'gsm-umts, lte'
> > | current: 'gsm-umts, lte'
> > | equipment id: 'XXXXXXXXXXXXXXX'
> > -------------------------
> > System | device:
> '/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-5'
> > | drivers: 'qmi_wwan, qcserial'
> > | plugin: 'Gobi'
> > | primary port: 'ttyUSB2'
> > | ports: 'ttyUSB0 (qcdm), ttyUSB2 (at),
> > wwp0s29f7u5i10 (net), wwp0s29f7u5i8 (net)'
>
> You're missing here the cdc-wdm ports to talk QMI. Is this a
> self-compiled kernel? Is the cdc-wdm driver enabled in the build?
>
>
> > -------------------------
> > Numbers | own : 'XXXXXXXXXXX'
> > -------------------------
> > Status | lock: 'none'
> > | unlock retries: 'unknown'
> > | state: 'disabled'
> > | power state: 'on'
> > | access tech: 'unknown'
> > | signal quality: '0' (cached)
> > -------------------------
> > Modes | supported: 'allowed: 2g, 3g, 4g; preferred: none'
> > | current: 'allowed: 2g, 3g, 4g; preferred: none'
> > -------------------------
> > Bands | supported: 'unknown'
> > | current: 'unknown'
> > -------------------------
> > IP | supported: 'ipv4, ipv6, ipv4v6'
> > -------------------------
> > 3GPP | imei: 'XXXXXXXXXXXXXXX'
> > | enabled locks: 'none'
> > | operator id: 'unknown'
> > | operator name: 'unknown'
> > | subscription: 'unknown'
> > | registration: 'unknown'
> > -------------------------
> > SIM | path: '/org/freedesktop/ModemManager1/SIM/1'
> >
> > -------------------------
> > Bearers | paths: 'none'
> >
> > $ mmcli -m 1 --simple-connect="apn=broadband,ip-type=ipv4v6" --verbose
> > --timeout=1500
> > [21 Mar 2016, 22:31:19] [Debug] Forcing request to be run asynchronously
> > [21 Mar 2016, 22:31:19] [Debug] Assuming '1' is the modem index
> > [21 Mar 2016, 22:31:19] [Debug] ModemManager process found at ':1.31'
> > [21 Mar 2016, 22:31:19] [Debug] Modem found at
> > '/org/freedesktop/ModemManager1/Modem/1'
> >
> > [21 Mar 2016, 22:31:19] [Debug] Asynchronously connecting the modem...
> > successfully connected the modem
> >
> > $ mmcli -b 1
> > Bearer '/org/freedesktop/ModemManager1/Bearer/1'
> > -------------------------
> > Status | connected: 'yes'
> > | suspended: 'no'
> > | interface: 'ttyUSB2'
> > | IP timeout: '20'
>
> This should have listed one of the WWANs, but it's not there because
> the QMI implementation isn't managing the modem, due to the lack of
> cdc-wdm port.
>
> > -------------------------
> > Properties | apn: 'broadband'
> > | roaming: 'allowed'
> > | IP type: 'ipv4v6'
> > | user: 'none'
> > | password: 'none'
> > | number: 'none'
> > | Rm protocol: 'unknown'
> > -------------------------
> > IPv4 configuration | method: 'ppp'
> > | address: 'unknown'
> > | prefix: '0'
> > | gateway: 'unknown'
> > | DNS: none
> > -------------------------
> > IPv6 configuration | method: 'ppp'
> > | address: 'unknown'
> > | prefix: '0'
> > | gateway: 'unknown'
> > | DNS: none
> >
> > Trying to get a lease from either wwan interface fails:
> >
> > $ sudo dhcpcd wwp0s29f7u5i8
> > wwp0s29f7u5i8: waiting for carrier
> > wwp0s29f7u5i8: carrier acquired
> > wwp0s29f7u5i8: adding address fe80::aa33:9c69:b4fa:2796
> > DUID XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX
> > wwp0s29f7u5i8: IAID df:90:dc:bc
> > wwp0s29f7u5i8: soliciting a DHCP lease
> > wwp0s29f7u5i8: soliciting an IPv6 router
> > wwp0s29f7u5i8: no IPv6 Routers available
> > timed out
> > dhcpcd exited
> >
> > $ sudo dhcpcd wwp0s29f7u5i10
> > wwp0s29f7u5i10: waiting for carrier
> > wwp0s29f7u5i10: carrier acquired
> > wwp0s29f7u5i10: adding address fe80::f614:fdf:279f:ae6c
> > DUID XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX
> > wwp0s29f7u5i10: IAID 67:d6:ab:9b
> > wwp0s29f7u5i10: soliciting a DHCP lease
> > wwp0s29f7u5i10: soliciting an IPv6 router
> > wwp0s29f7u5i10: no IPv6 Routers available
> > timed out
> > dhcpcd exited
> >
>
> No, you cannot do this if the bearer info doesn't list a WWAN.
>
> > I'm guessing I need to get MM to start the bearer on wwp0s29f7u5i10
> > instead of ttyUSB2, but so far I haven't figured out how to do this.
>
> This should be automatic, only if MM grabbed all the required ports.
>
> --
> Aleksander
> https://aleksander.es
>
--
- Steven
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20160323/bd91a24f/attachment.html>
More information about the ModemManager-devel
mailing list