Huawei ME906s-158 (a.k.a. HP lt4132) IPv6 support
Sebastian Sjoholm
sebastian.sjoholm at gmail.com
Thu Jul 6 04:51:42 UTC 2017
Hi,
The LT4120 might have it's own challenges. The website you are referring to
does add udev rule to set the configuration of the modem, as it seems to be
in win8 mode as original, and that the Linux system does not seem to cope
with very well.
This is when it is in default, without any udev rules;
root at SBC01:~# lsusb
Bus 002 Device 004: ID 03f0:9d1d Hewlett-Packard
Bus 002 Device 002: ID 04b4:6570 Cypress Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root at SBC01:~#
root at SBC01:~# lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ci_hdrc/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 2: Dev 6, If 0, Class=Vendor Specific Class, Driver=, 480M
|__ Port 2: Dev 6, If 1, Class=Communications, Driver=cdc_ether,
480M
|__ Port 2: Dev 6, If 2, Class=CDC Data, Driver=cdc_ether, 480M
|__ Port 2: Dev 6, If 3, Class=Vendor Specific Class, Driver=, 480M
|__ Port 2: Dev 6, If 4, Class=Vendor Specific Class, Driver=, 480M
|__ Port 2: Dev 6, If 5, Class=Vendor Specific Class, Driver=, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ci_hdrc/1p, 480M
root at SBC01:~#
Then it seems to make restarts;
root at SBC01:~# dmesg | grep '2-1'
[ 2.243058] usb 2-1: new high-speed USB device number 2 using ci_hdrc
[ 2.413110] hub 2-1:1.0: USB hub found
[ 2.413610] hub 2-1:1.0: 4 ports detected
[ 11.573095] usb 2-1.2: new high-speed USB device number 3 using ci_hdrc
[ 11.780413] cdc_ether 2-1.2:2.0 usb0: register 'cdc_ether' at
usb-ci_hdrc.1-1.2, CDC Ethernet Device, fa:90:91:b8:cd:e0
[ 12.387259] usb 2-1.2: USB disconnect, device number 3
[ 12.387582] cdc_ether 2-1.2:2.0 usb0: unregister 'cdc_ether'
usb-ci_hdrc.1-1.2, CDC Ethernet Device
[ 12.627047] usb 2-1.2: new high-speed USB device number 4 using ci_hdrc
[ 12.755515] cdc_ether 2-1.2:1.1 usb0: register 'cdc_ether' at
usb-ci_hdrc.1-1.2, CDC Ethernet Device, 4a:30:dd:ad:b2:88
[ 23.394912] usb 2-1.2: USB disconnect, device number 4
[ 23.395780] cdc_ether 2-1.2:1.1 usb0: unregister 'cdc_ether'
usb-ci_hdrc.1-1.2, CDC Ethernet Device
[ 31.286092] usb 2-1.2: new high-speed USB device number 5 using ci_hdrc
[ 31.420904] cdc_ether 2-1.2:2.0 usb0: register 'cdc_ether' at
usb-ci_hdrc.1-1.2, CDC Ethernet Device, 02:e8:a5:f0:0e:11
[ 32.162228] usb 2-1.2: USB disconnect, device number 5
[ 32.162553] cdc_ether 2-1.2:2.0 usb0: unregister 'cdc_ether'
usb-ci_hdrc.1-1.2, CDC Ethernet Device
[ 32.364090] usb 2-1.2: new high-speed USB device number 6 using ci_hdrc
[ 32.492943] cdc_ether 2-1.2:1.1 usb0: register 'cdc_ether' at
usb-ci_hdrc.1-1.2, CDC Ethernet Device, a2:0a:ac:e5:fb:9d
[ 43.170223] usb 2-1.2: USB disconnect, device number 6
[ 43.175367] cdc_ether 2-1.2:1.1 usb0: unregister 'cdc_ether'
usb-ci_hdrc.1-1.2, CDC Ethernet Device
[ 51.047280] usb 2-1.2: new high-speed USB device number 7 using ci_hdrc
[ 51.184426] cdc_ether 2-1.2:2.0 usb0: register 'cdc_ether' at
usb-ci_hdrc.1-1.2, CDC Ethernet Device, 92:2b:3d:4c:e2:68
[ 51.921465] usb 2-1.2: USB disconnect, device number 7
[ 51.921793] cdc_ether 2-1.2:2.0 usb0: unregister 'cdc_ether'
usb-ci_hdrc.1-1.2, CDC Ethernet Device
[ 52.213204] usb 2-1.2: new high-speed USB device number 8 using ci_hdrc
[ 52.345228] cdc_ether 2-1.2:1.1 usb0: register 'cdc_ether' at
usb-ci_hdrc.1-1.2, CDC Ethernet Device, a6:71:cf:5c:70:84
[ 63.697457] usb 2-1.2: USB disconnect, device number 8
[ 63.702673] cdc_ether 2-1.2:1.1 usb0: unregister 'cdc_ether'
usb-ci_hdrc.1-1.2, CDC Ethernet Device
[ 71.788063] usb 2-1.2: new high-speed USB device number 9 using ci_hdrc
[ 71.924487] cdc_ether 2-1.2:2.0 usb0: register 'cdc_ether' at
usb-ci_hdrc.1-1.2, CDC Ethernet Device, 4a:93:66:c0:49:51
[ 72.659698] usb 2-1.2: USB disconnect, device number 9
[ 72.659872] cdc_ether 2-1.2:2.0 usb0: unregister 'cdc_ether'
usb-ci_hdrc.1-1.2, CDC Ethernet Device
[ 72.860003] usb 2-1.2: new high-speed USB device number 10 using ci_hdrc
[ 72.991422] cdc_ether 2-1.2:1.1 usb0: register 'cdc_ether' at
usb-ci_hdrc.1-1.2, CDC Ethernet Device, a6:bf:7b:a9:82:9b
[ 84.435733] usb 2-1.2: USB disconnect, device number 10
[ 84.441732] cdc_ether 2-1.2:1.1 usb0: unregister 'cdc_ether'
usb-ci_hdrc.1-1.2, CDC Ethernet Device
[ 92.478853] usb 2-1.2: new high-speed USB device number 11 using ci_hdrc
[ 92.619747] cdc_ether 2-1.2:2.0 usb0: register 'cdc_ether' at
usb-ci_hdrc.1-1.2, CDC Ethernet Device, 76:e9:00:c2:9c:8f
[ 93.347809] usb 2-1.2: USB disconnect, device number 11
[ 93.348140] cdc_ether 2-1.2:2.0 usb0: unregister 'cdc_ether'
usb-ci_hdrc.1-1.2, CDC Ethernet Device
[ 93.614757] usb 2-1.2: new high-speed USB device number 12 using ci_hdrc
[ 93.745144] cdc_ether 2-1.2:1.1 usb0: register 'cdc_ether' at
usb-ci_hdrc.1-1.2, CDC Ethernet Device, ce:5c:33:11:8b:42
root at SBC01:~# lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ci_hdrc/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ci_hdrc/1p, 480M
root at SBC01:~#
With the udev rules it is stable, but it seems to map the ports wrong, as I
get 4 cdc-wdmx devices and no serial ports.
This is with the udev rule (from the website)
root at SBC01:~/xilka# lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ci_hdrc/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 2: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 480M
|__ Port 2: Dev 3, If 1, Class=Vendor Specific Class,
Driver=qmi_wwan, 480M
|__ Port 2: Dev 3, If 2, Class=Vendor Specific Class,
Driver=qmi_wwan, 480M
|__ Port 2: Dev 3, If 3, Class=Vendor Specific Class,
Driver=qmi_wwan, 480M
|__ Port 2: Dev 3, If 4, Class=Vendor Specific Class,
Driver=qmi_wwan, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ci_hdrc/1p, 480M
root at SBC01:~/xilka#
But as I said, I don't have the latest firmware, the HP software does not
install on a windows machine if the modem is not installed, so at the
moment I haven't done much on this.But I can assist in any verification
needed.
Running 4.10.17 kernel at the moment.
Regards,
Sebastian
On Wed, Jul 5, 2017 at 10:03 PM, Reinhard Speyerer <rspmn at arcor.de> wrote:
> On Wed, Jul 05, 2017 at 03:38:00PM +0200, Tore Anderson wrote:
> > * Bjørn Mork
> >
> > > I don't know if this will help Tore much anyway. I did some testing
> > > with the E392 to confirm that I remembered correctly: This modem does
> > > *not* change the output of any command when IPv6 is disabled. The only
> > > visible difference is that IPv6 connections fail. You can still
> > > configure them.
> >
> > Now I've tried running the tool, both the patched version and the
> > original in the MM git repo, on every single /dev/ttyUSB* that show up
> > in all three bConfigurationValues with no special USB serial module
> > loaded and also with option.ko, qcaux.ko, and qcserial.ko. All possible
> > permutations of the above I tried in a scripted manner.
> >
> > Most of the time the tool fails with:
> >
> > E: failed to receive QCDM IPv6 pref command reply
> > E: failed to get IPv6 state
> >
> > Sometimes it instead crashes, saying only:
> >
> > ipv6pref.c:105: qcdm_send: Assertion `errno == 0' failed.
> >
> > It never actually did anything resembling a successful operation. I
> > suppose that means the the tool, patched or not, simply does not support
> > the ME906s-158.
> >
> > > In the current state, with IPv6 enabled, everything works on the E392:
> > >
> > > root at miraculix:/tmp# qmicli -d /dev/cdc-wdm1 --wds-start-network=apn=telenor.smart,ip-type=6
> --wds-follow-network
> >
> > No cigar:
> >
> > $ qmicli -d /dev/cdc-wdm0 --wds-start-network=apn=telenor.smart,ip-type=6
> --wds-follow-network
> > error: couldn't create client for the 'wds' service: CID allocation
> failed in the CTL client: MBIM error: Transaction timed out
> >
> > The other qmicli commands you pasted doesn't work either.
>
> Hi Tore,
>
> according to the Huawei product page given in your previous email the
> ME906s-158 contains a Hisilicon Balong V711 chipset which explains why
> there is no QCDM port and why the QMI-over-MBIM tunneling fails.
>
> >
> > > This behaviour is so different from the symptoms Tore see, that I doubt
> > > there is any relation. Still, it can't harm to test if the attached
> > > patch allows writing anything that NV item... Or it can harm - I never
> > > give out gurantees when it comes to arbitrary NVRAM writes ;-)
> >
> > I really appreciate the input, thank you. But unfortunately I think the
> > conclusion is that there is no hope to make IPv6 work on this modem,
> > unless Huawei or HP support returns to me with some magic trick to
> > enable it.
> >
> > The good news is that HP support agreed to replace my lt4132 with a
> > lt4120, which is a Foxconn device that I hope works better.
>
> Well, at least it seems to contain a Qualcomm Snapdragon chipset and
> another
> lt4120 user has written up the steps to make it work on Linux here
> https://abarouski.blogspot.de/2016/07/configuring-hp-lt4120-
> in-linux-as-i.html
> .
>
> Regards,
> Reinhard
> _______________________________________________
> ModemManager-devel mailing list
> ModemManager-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
>
--
Sebastian Sjöholm
Simborgarvägen 116
SE-18439 Åkersberga
Sverige
Mobile : +46 76 335 0667
Email : sebastian.sjoholm at gmail.com
Skype : ssjoholm
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20170706/e2d5d862/attachment-0001.html>
More information about the ModemManager-devel
mailing list