Problem with EM160 with newifid2

Hardware Questions and Recommendations
1

hi, i'm new and i'm italian. i don't speech very well english. I've a problem to connect Quectel EM160 to newifid2 with usb port. I followed the guides on the openwrt site step by step to connect in QMI mode but the router cannot find the device directory. Ho controllato che il modem fosse inpostato in QMI mode attraverto i comandi AT. I've do this:
AT
OK
ATI
Quectel
EM160R-GL
Revision: EM160RGLAUR02A03M4G

OK
AT+QCFG="usbnet"
+QCFG: "usbnet",0
Through the dmsg command the router replied this:
[ 15.776812] PPP generic driver version 2.4.2
[ 15.782803] NET: Registered protocol family 24
[ 15.794215] usbcore: registered new interface driver qmi_wwan
[ 15.802113] usbcore: registered new interface driver rndis_host
[ 15.816388] usbcore: registered new interface driver uas
[ 15.826569] usbcore: registered new interface driver cdc_mbim
[ 15.841138] usbcore: registered new interface driver option
[ 15.846964] usbserial: USB Serial support registered for GSM modem (1-port)
[ 15.857425] kmodloader: done loading kernel modules from /etc/modules.d/*
[ 22.994716] mtk_soc_eth 1e100000.ethernet: PPE started
[ 23.005671] br-lan: port 1(eth0.1) entered blocking state
[ 23.011132] br-lan: port 1(eth0.1) entered disabled state
[ 23.017285] device eth0.1 entered promiscuous mode
[ 23.022187] device eth0 entered promiscuous mode
[ 23.030830] br-lan: port 1(eth0.1) entered blocking state
[ 23.036326] br-lan: port 1(eth0.1) entered forwarding state
[ 23.042507] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
[ 24.041625] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready

Through this command I received this other response:
root@OpenWrt:~# cat /sys/kernel/debug/usb/devices

T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 2
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev= 4.14
S: Manufacturer=Linux 4.14.209 xhci-hcd
S: Product=xHCI Host Controller
S: SerialNumber=1e1c0000.xhci
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms

T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=5000 MxCh= 1
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 3.00 Cls=09(hub ) Sub=00 Prot=03 MxPS= 9 #Cfgs= 1
P: Vendor=1d6b ProdID=0003 Rev= 4.14
S: Manufacturer=Linux 4.14.209 xhci-hcd
S: Product=xHCI Host Controller
S: SerialNumber=1e1c0000.xhci
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms

T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=5000 MxCh= 0
D: Ver= 3.20 Cls=ef(misc ) Sub=02 Prot=01 MxPS= 9 #Cfgs= 1
P: Vendor=2c7c ProdID=0620 Rev= 4.09
S: Manufacturer=Quectel
S: Product=EM160R-GL
S: SerialNumber=e31cedc1
C:* #Ifs= 5 Cfg#= 1 Atr=a0 MxPwr=896mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=30 Driver=(none)
E: Ad=81(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E: Ad=01(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)
E: Ad=83(I) Atr=03(Int.) MxPS= 10 Ivl=32ms
E: Ad=82(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)
E: Ad=85(I) Atr=03(Int.) MxPS= 10 Ivl=32ms
E: Ad=84(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E: Ad=03(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)
E: Ad=87(I) Atr=03(Int.) MxPS= 10 Ivl=32ms
E: Ad=86(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E: Ad=04(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E: Ad=88(I) Atr=03(Int.) MxPS= 8 Ivl=32ms
E: Ad=8e(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E: Ad=0f(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms

can someone help me? I don't know how to proceed
Thanks in advance

2

Consider using this OpenWrt based firmware.

3

I'll try, thank you so much

4

@AndrewZ There aren't any Fw for my newifi D2 in the site

5

Then ask in their forum and the firmware will be built if necessary.

6

The firmware does not contain some kernel modules. Use this manual:

7

Which shows us that you have installed all the recommended kernel modules.

The problem is that your modem is very new, and so far unknown by the drivers. This output shows a typical newer Qualcomm modem with 5 vendor specfic functions:

Interfaces 0 to 3 are serial functions and should be handled by the "option" driver. Interface 4 is RMNET/QMI and should be handled by qmi_wwan. I'll prepare and submit the necessary patches, but it witll take a few weeks before they trickle down from mainline Linux to stable to OpenWrt.

You can temporarily work around the missing ID in the drivers by manipulating the "new_id", "bind" and "unbind" sysfs attributes of the drivers. Try something like (untested):

 echo "2c7c 0620 0 0408 ea42" >  /sys/bus/usb-serial/drivers/option1/new_id
 echo "2c7c 0620" >  /sys/bus/usb/drivers/qmi_wwan/new_id

It might work in that order... The challenge is that you need two drivers handling vendor specific functions. Mapping them to the correct functions is essential. You can fix it using the "unbind" and "bind" attributes, but that is a bit cumbersome.

Or wait for the patches to go in.

8

@bmork thank you so much for the advice. I will try as you say, if I can't I will wait for the patch.

9

@AndrewZ I have found this firmware and work very well. It's openwrt based. https://drive.google.com/file/d/1AK3JDN80vABzNExYA1bd-TM5Fu80Ezof/view?usp=sharing

10

This is an old version of the firmware I recommended, from unknown source, better to ask for the proper version as suggested earlier

11

Linux v5.4.89 is now released with the EM160 support patches, so the next kernel update should bring it to OpenWrt

12

Thank you so much for the support!!!!

13

Anyone know anything about "support" EM160?