GL-MiFi info?!

guest · January 21, 2016, 7:06pm

Still no screen…

root@domino:~# opkg update
root@domino:~# opkg install screen
Unknown package ‘screen’.
Collected errors:

opkg_install_cmd: Cannot install package screen.
root@domino:~#

jw1 · January 21, 2016, 7:09pm

Mmm. It might be missing in Barrier Breaker…

I will need it myself too later on once I have flashed the firmware. I will keep you posted.

alzhao · January 21, 2016, 7:10pm

Opkg update should download the package list, seems your board didn’t. You have to let it connect to the internet first.

Set the Ethernet to WAN first, because it is changed by default to LAN.

guest · January 21, 2016, 7:11pm

It is connected to internet… I’m using it now.

alzhao · January 21, 2016, 7:14pm

so opkg update didn’t drag the repo list done? Then there must be the problem of the firmware.

guest · January 21, 2016, 7:17pm

No nothing happened.

jw1 · January 21, 2016, 7:21pm

I just flashed the firmware from GL-MiFi page in the download section.

I successfully installed screen with the above commands. See the screenshot attached. opkg update should output a lot of sources indicating it is downloading the package lists as you can see in the screenshot.

I suspect your board doesn’t have an internet connection.

Make sure to either hook the ethernet port up to your router with DHCP or make a bridge to your existing WiFi network by selecting WiFi in the web panel under the Network section and entering your WPA/WPA2 key.

Edit: Sorry I didn’t read properly above. I realize now you have a working internet connection. Strange it is working for me…

guest · January 21, 2016, 7:26pm

Strange… I really do have internet (see image)

jw1 · January 21, 2016, 7:30pm

Very strange that opkg update doesn’t work for you.

As a workaround you could try manually downloading with wget and installing from the IPK


cd /tmp
wget http://domino.io/firmware/pi/1.1/packages/packages/screen_4.2.1-2_ar71xx.ipk
opkg install screen_4.2.1-2_ar71xx.ipk

guest · January 21, 2016, 7:53pm

That did the trick for screen…
I’m going to reflash again and see if this will fix the problem.

I guess I’m still in the “jinxed” week mode.

jw1 · January 21, 2016, 7:59pm

I am now having trouble talking to the /dev/ttyUSB* ports with screen.

I tried minicom as well. They all just freeze and die when trying to access any ttyUSB* port.

Also I am getting option1 ttyUSB3: option_instat_callback: error -2 errors in dmesg.

Will keep hacking away at it…

guest · January 21, 2016, 8:21pm

Reflashed and reset.

Yahoooooo…

root@domino:~# opkg update
Downloading http://domino.io/firmware/pi/1.1/packages/base/Packages.gz.
Updated list of available packages in /var/opkg-lists/barrier_breaker_base.
Downloading http://domino.io/firmware/pi/1.1/packages/alljoyn/Packages.gz.
Updated list of available packages in /var/opkg-lists/barrier_breaker_alljoyn.
Downloading http://domino.io/firmware/pi/1.1/packages/luci/Packages.gz.
Updated list of available packages in /var/opkg-lists/barrier_breaker_luci.
Downloading http://domino.io/firmware/pi/1.1/packages/management/Packages.gz.
Updated list of available packages in /var/opkg-lists/barrier_breaker_management.
Downloading http://domino.io/firmware/pi/1.1/packages/oldpackages/Packages.gz.
Updated list of available packages in /var/opkg-lists/barrier_breaker_oldpackages.
Downloading http://domino.io/firmware/pi/1.1/packages/packages/Packages.gz.
Updated list of available packages in /var/opkg-lists/barrier_breaker_packages.
Downloading http://domino.io/firmware/pi/1.1/packages/routing/Packages.gz.
Updated list of available packages in /var/opkg-lists/barrier_breaker_routing.
Downloading http://domino.io/firmware/pi/1.1/packages/telephony/Packages.gz.
Updated list of available packages in /var/opkg-lists/barrier_breaker_telephony.
root@domino:~#
root@domino:~# opkg install screen
Installing screen (4.2.1-2) to root…
Downloading http://domino.io/firmware/pi/1.1/packages/packages/screen_4.2.1-2_ar71xx.ipk.
Configuring screen.
root@domino:~#

guest · January 21, 2016, 8:38pm

re: Also I am getting option1 ttyUSB3: option_instat_callback: error -2 errors in dmesg.
Same here.

guest · January 21, 2016, 8:46pm

Looks like the GSM modem does get attached.

root@domino:~# dmesg | grep tty
[ 0.000000] Kernel command line: board=DOMINO console=ttyATH0,115200 mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,16000k(firmware),64k(art)ro rootfstype=squashfs,jffs2 noinitrd
[ 0.660000] ar933x-uart: ttyATH0 at MMIO 0x18020000 (irq = 11) is a AR933X UART
[ 0.660000] console [ttyATH0] enabled, bootconsole disabled
[ 20.200000] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB0
[ 20.210000] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB1
[ 20.230000] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB2
[ 20.240000] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB3
[ 20.270000] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB4
[ 853.500000] option1 ttyUSB3: option_instat_callback: error -2
[ 856.510000] option1 ttyUSB3: option_instat_callback: error -2
[ 858.260000] option1 ttyUSB3: option_instat_callback: error -2
[ 860.850000] option1 ttyUSB3: option_instat_callback: error -2
[ 862.530000] option1 ttyUSB3: option_instat_callback: error -2
[ 865.360000] option1 ttyUSB3: option_instat_callback: error -2
[ 867.100000] option1 ttyUSB3: option_instat_callback: error -2
[ 870.060000] option1 ttyUSB3: option_instat_callback: error -2
[ 871.810000] option1 ttyUSB3: option_instat_callback: error -2
[ 874.610000] option1 ttyUSB3: option_instat_callback: error -2
[ 876.370000] option1 ttyUSB3: option_instat_callback: error -2
[ 879.300000] option1 ttyUSB3: option_instat_callback: error -2
[ 881.050000] option1 ttyUSB4: option_instat_callback: error -2
[ 892.800000] option1 ttyUSB4: option_instat_callback: error -2
[ 905.050000] option1 ttyUSB4: option_instat_callback: error -2
[ 906.980000] option1 ttyUSB4: option_instat_callback: error -2
[ 1910.920000] option1 ttyUSB4: option_instat_callback: error -2
[ 1913.590000] option1 ttyUSB3: option_instat_cal

jw1 · January 21, 2016, 9:05pm

Yup it gets attached.

/dev/ttyUSB3 is supposed to be the AT command interface including the one that can handle PPP connections.

/dev/ttyUSB2 is an AT interface only to configure the modem but not for PPP connections

/dev/ttyUSB1 is supposedly the NMEA (GPS) interface

and

/dev/ttyUSB4 is the QMI interface

(All this you can find in that document that is up for download in the GL-MiFi download section for the Quectel board.)

I am not able to talk to any of the ttyUSB* ports using either screen or minicom.

Both just freeze up and I cannot CTRL-C out of it but have to close my terminal window. Not sure if the processes still hang.

I have already tried setting port speeds using numerous variations of the stty command but yet to no avail…

I suspect some driver is throwing off the ttyUSB* ports or I am missing something else.

guest · January 21, 2016, 9:31pm

I’m able to exit minicom with CTRL + A Z.
screen does hang for me too.

alzhao · January 21, 2016, 9:40pm

Hi Guest,

We met this error from time to time, there are some possible reasons:

The sim card connection is not good. Not sure if this is the case because your slot had problems.
please connect antennas, not sure if this really matters but pls always connect.
Are you using EC20 or UC20? For UC20, ttyUSB3 is for data; for EC20, ttyUSB2 is for data. please set this correct in /etc/config/network
set the correct APN and other parameters, like username, password, service type correct.

jw1 · January 21, 2016, 9:46pm

Ahhh! Thanks Alfie.

My bad here. I have no sim installed at the moment.

That should fix things.

alzhao · January 21, 2016, 9:49pm

the settings of EC20 and UC20 as attached.

guest · January 21, 2016, 10:04pm

Hmm I do have a sim installed. Will make the necessary settings in /etc/config/network