Also the compilation depends on some host tools which were not defined (as in brought into the OpenWrt build and installed into $(STAGING_DIR)/host) so I had to install them myself. Namely libintl and gtk-doc… the latter could be avoided by not compiling docs and patching the config script to not check for the tools.

All in all my jffs2 rootfs image was 5.4 megs which really isn’t that bad. Devices with <8MB are pretty rare nowadays and having full-featured modem support is pretty sweet.

My only gripe is that my firmware "feels dirty" because it is running duplicate softwares. Hotplug2 and udev, ubus and dbus, etc… I understand why OpenWrt uses that software but it seems like trying to trim down udev and dbus would have been a better effort than rewriting from scratch. NIH syndrome for sure.

|/usr/share/apport/apport %p %s %c

This is how Ubuntu is able to detect when a program has crashed/dumped core, and apport is able to send crash reports to launchpad. This also led me to find out that ‘%c’ (another unmentioned ‘pattern element’) is supported in the core_pattern file. Running ‘apport’ with –help reveals what it is:

/usr/share/apport/apport –help
Usage: /usr/share/apport/apport
The core dump is read from stdin.

So:

%c = core file ulimit

Ruslan :

Perhaps, you could change your Makefile for OpenWRT tools?

Not sure what you mean with that; do you want me to suggest libmbim to OpenWRT already?

checking for LIBMBIM_GLIB... yes
checking for MBIMCLI... yes
configure: creating ./config.status
config.status: error: cannot find input file: `Makefile.in'
make[2]: *** [/home/ruslan/OpenWRT_Lanedo_MM/lanedo-openwrt/build_dir/target-mipsel_r2_uClibc-0.9.33.2/libmbim-0.0.1/.configured_] Error 1
make[2]: Leaving directory `/home/ruslan/OpenWRT_Lanedo_MM/lanedo-openwrt/custom-feed/libmbim'
make[1]: *** [package/feeds/custom/libmbim/compile] Error 2
make[1]: Leaving directory `/home/ruslan/OpenWRT_Lanedo_MM/lanedo-openwrt'
make: *** [package/libmbim/compile] Ошибка 2
[ruslan@localhost lanedo-openwrt]$ 

So, I’ve reconfigured the package, and it was compiled successfully

Makefile is here:
http://pastebin.com/5KkN2rdM

Perhaps, you could change your Makefile for OpenWRT tools?

Anyway the firmware is rather big in result. IMHO glib2 is heavy lib for embedded systems. For example its impossible to install something like this one to 4 Mb flash router:( Is it difficult to unbind libqmi and modemmanager from glib2? And possible?

root@OpenWrt:~# udevd
bind failed: No such file or directory
error binding udev control socket
error binding udev control socket
root@OpenWrt:~# dbus
-ash: dbus: not found

Here ls :
http://pastebin.com/V7qHV3W3
Could you show your .config file?

root@OpenWrt:~# mmcli -m 0 --simple-connect="apn=yota.ru"
error: couldn't find the ModemManager process in the bus

Modem E392 is connected, driver qmi_wwan is in place.
Full log of ps and /sys/kernel/debug/usb/devices here:

http://pastebin.com/ecTCMwXd

http://pastebin.com/XiXrVECb

IMHO needs to check Makefile of [b]system-udev [/b]

make[6]: Leaving directory `/home/ruslan/OpenWRT_Lan-ModemManager/lanedo-openwrt/build_dir/target-mipsel_r2_uClibc-0.9.33.2/modemmanager-2013-02-13/docs/reference'
Making all in man
make[6]: Entering directory `/home/ruslan/OpenWRT_Lan-ModemManager/lanedo-openwrt/build_dir/target-mipsel_r2_uClibc-0.9.33.2/modemmanager-2013-02-13/docs/man'
make[6]: Nothing to be done for `all'.
make[6]: Leaving directory `/home/ruslan/OpenWRT_Lan-ModemManager/lanedo-openwrt/build_dir/target-mipsel_r2_uClibc-0.9.33.2/modemmanager-2013-02-13/docs/man'
make[6]: Entering directory `/home/ruslan/OpenWRT_Lan-ModemManager/lanedo-openwrt/build_dir/target-mipsel_r2_uClibc-0.9.33.2/modemmanager-2013-02-13/docs'
make[6]: Nothing to be done for `all-am'.
make[6]: Leaving directory `/home/ruslan/OpenWRT_Lan-ModemManager/lanedo-openwrt/build_dir/target-mipsel_r2_uClibc-0.9.33.2/modemmanager-2013-02-13/docs'
make[5]: Leaving directory `/home/ruslan/OpenWRT_Lan-ModemManager/lanedo-openwrt/build_dir/target-mipsel_r2_uClibc-0.9.33.2/modemmanager-2013-02-13/docs'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/home/ruslan/OpenWRT_Lan-ModemManager/lanedo-openwrt/build_dir/target-mipsel_r2_uClibc-0.9.33.2/modemmanager-2013-02-13'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/home/ruslan/OpenWRT_Lan-ModemManager/lanedo-openwrt/build_dir/target-mipsel_r2_uClibc-0.9.33.2/modemmanager-2013-02-13'
make[2]: *** [/home/ruslan/OpenWRT_Lan-ModemManager/lanedo-openwrt/build_dir/target-mipsel_r2_uClibc-0.9.33.2/modemmanager-2013-02-13/.built] Error 2
make[2]: Leaving directory `/home/ruslan/OpenWRT_Lan-ModemManager/lanedo-openwrt/lanedo-openwrt-packages/net/modemmanager'
make[1]: *** [package/feeds/packages/modemmanager/compile] Error 2
make[1]: Leaving directory `/home/ruslan/OpenWRT_Lan-ModemManager/lanedo-openwrt'
make: *** [package/modemmanager/compile] Ошибка 2
ruslan@debian:~/OpenWRT_Lan-ModemManager/lanedo-openwrt$ 

I’ve Fedora on my desktop, I’ll try to renew it to 18 and compile.

Thanks

 make[7]: Leaving directory `/home/ruslan/OpenWRT_Lan-ModemManager/lanedo-openwrt/build_dir/target-mipsel_r2_uClibc-0.9.33.2/modemmanager-2013-02-13/docs'
make[6]: Leaving directory `/home/ruslan/OpenWRT_Lan-ModemManager/lanedo-openwrt/build_dir/target-mipsel_r2_uClibc-0.9.33.2/modemmanager-2013-02-13/docs'
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory `/home/ruslan/OpenWRT_Lan-ModemManager/lanedo-openwrt/build_dir/target-mipsel_r2_uClibc-0.9.33.2/modemmanager-2013-02-13'
make[4]: *** [all] Error 2
make[4]: Leaving directory `/home/ruslan/OpenWRT_Lan-ModemManager/lanedo-openwrt/build_dir/target-mipsel_r2_uClibc-0.9.33.2/modemmanager-2013-02-13'
make[3]: *** [/home/ruslan/OpenWRT_Lan-ModemManager/lanedo-openwrt/build_dir/target-mipsel_r2_uClibc-0.9.33.2/modemmanager-2013-02-13/.built] Error 2
make[3]: Leaving directory `/home/ruslan/OpenWRT_Lan-ModemManager/lanedo-openwrt/lanedo-openwrt-packages/net/modemmanager'
make[2]: *** [package/feeds/packages/modemmanager/compile] Error 2
make[2]: Leaving directory `/home/ruslan/OpenWRT_Lan-ModemManager/lanedo-openwrt'
make[1]: *** [/home/ruslan/OpenWRT_Lan-ModemManager/lanedo-openwrt/staging_dir/target-mipsel_r2_uClibc-0.9.33.2/stamp/.package_compile] Error 2
make[1]: Leaving directory `/home/ruslan/OpenWRT_Lan-ModemManager/lanedo-openwrt'
make: *** [world] Ошибка 2 
ruslan@debian:~/OpenWRT_Lan-ModemManager/lanedo-openwrt$ 

what could be the problem? What system do you use for compilation? I use Debian GNU/Linux 6.0.3 (squeeze)
Thanks
Ruslan

% Not enumerated chapter
%——————————————————————————-
\include{preface}

or

% First enumerated chapter
%——————————————————————————-

\include{cap1}
\include{cap2}
\include{cap3}
\include{cap4}
\include{cap5}

% Last pages for ToC

With the advantage, that in a different .tex you can have each chapter, doing easier the writting of the book. It’s a beautifull template, thanks you so much

Thanks,

André

http://lists.freedesktop.org/mailman/listinfo/libqmi-devel

I just patched libqmi to allow me to give username and password for the connection. This is essential for some services..
Here is my “Test Patch”
—————————————————————————————————————
index 775824b..134beb9 100644
— a/cli/qmicli-wds.c
+++ b/cli/qmicli-wds.c
@@ -58,7 +58,7 @@ static gboolean noop_flag;
static GOptionEntry entries[] = {
{ “wds-start-network”, 0, 0, G_OPTION_ARG_STRING, &start_network_str,
“Start network”,
- “[APN]”
+ “[APN|Username|Password]”
},
{ “wds-follow-network”, 0, 0, G_OPTION_ARG_NONE, &follow_network_flag,
“Follow the network status until disconnected. Use with `–wds-start-network’”,
@@ -582,6 +582,8 @@ qmicli_wds_run (QmiDevice *device,
QmiClientWds *client,
GCancellable *cancellable)
{
+ gchar **split;
+ QmiWdsAuthentication qmiwdsauth;
/* Initialize context */
ctx = g_slice_new (Context);
ctx->device = g_object_ref (device);
@@ -596,8 +598,18 @@ qmicli_wds_run (QmiDevice *device,

/* Use the input string as APN */
if (start_network_str[0]) {
+ split = g_strsplit (start_network_str, “|”, 3);
input = qmi_message_wds_start_network_input_new ();
- qmi_message_wds_start_network_input_set_apn (input, start_network_str, NULL);
+ if (split[1][0]) {
+ qmi_message_wds_start_network_input_set_username (input, split[1], NULL);
+ qmiwdsauth = QMI_WDS_AUTHENTICATION_PAP;
+ qmi_message_wds_start_network_input_set_authentication_preference (input, qmiwdsauth, NULL);
+ }
+ if (split[2][0]) {
+ qmi_message_wds_start_network_input_set_password (input, split[2], NULL);
+ }
+ qmi_message_wds_start_network_input_set_apn (input, split[0], NULL);
+ g_strfreev (split);
}

g_debug (“Asynchronously starting network…”);
—————————————————————————————————————
I know it has several issues.
But the problem ist, if I try to dial in with:
# qmicli -vvv -d /dev/cdc-wdm0 ‘–wds-start-network=web.vodafone.de|XXXX|XX’
[20 Dec 2012, 10:42:42] [Debug] [/dev/cdc-wdm0] Received message (translated)…
>>>>>> QMUX:
>>>>>> length = 31
>>>>>> flags = 0×80
>>>>>> service = “wds”
>>>>>> client = 4
>>>>>> QMI:
>>>>>> flags = “response”
>>>>>> transaction = 1
>>>>>> tlv_length = 19
>>>>>> message = “Start Network” (0×0020)
>>>>>> TLV:
>>>>>> type = “Result” (0×02)
>>>>>> length = 4
>>>>>> value = 01:00:0E:00
>>>>>> translated = FAILURE: CallFailed
>>>>>> TLV:
>>>>>> type = “Call End Reason” (0×10)
>>>>>> length = 2
>>>>>> value = 01:00
>>>>>> translated = generic-unspecified
>>>>>> TLV:
>>>>>> type = “Verbose Call End Reason” (0×11)
>>>>>> length = 4
>>>>>> value = 77:01:C8:71
>>>>>> translated = [ type = '(null)' reason = '29128' ]

In a non-public channel I could give you the complete log.
Do you have an idea?

Thanks,

André

qmi_wwan is definitely needed to have all the setup running. If you don’t have it loaded, modprobe it to get it loaded.

Then, remember that the ifup is to be done in the virtual interface you configured for openwrt. It was named ‘wdm0′ in my example here, but I think it’s named differently in that forum thread.

And regarding ifup wwan0, just forget what I said about that. You really need to “ifup wdm0″ as you said, as that is the new interface defined by the “qmi4g” protocol handler I wrote.

So, don’t know why you don’t have connectivity, you should

aleksander :
AT^DHCP is the Huawei-specific thingy to check whether the modem is connected or not. You shouldn’t need that when using QMI.
ifup wdm0 is useless, that’s the control port you’re already talking to. Each control QMI port has a corresponding wwan port: once you’re connected you need to ifup that wwan port and dhclient (or equivalent) on it.
Make sure you’re using the correct APN. If you need user/pass for the APN, you’ll need to extend qmi-network, with those.
And qmi_wwan should really be used… Try to modprobe qmi_wwan before plugging in the modem and see if that helps. Note that sending AT commands without qmi_wwan is perfectly valid, they are independent control ports with different protocols.

as for APN, I created /etc/qmi-network.conf with APN=____ and qmi-network scripts uses it. There is no user/password for my APN.

I’m using standard udhcpc and insmod commands from openwrt.

Even if qmi-network status reports that modem is connected, module qmi_wwan is not used.

Is it possible to add some additional logging to qmi_wwan or cdc_wdm modules?

ifup wdm0 is useless, that’s the control port you’re already talking to. Each control QMI port has a corresponding wwan port: once you’re connected you need to ifup that wwan port and dhclient (or equivalent) on it.

Make sure you’re using the correct APN. If you need user/pass for the APN, you’ll need to extend qmi-network, with those.

And qmi_wwan should really be used… Try to modprobe qmi_wwan before plugging in the modem and see if that helps. Note that sending AT commands without qmi_wwan is perfectly valid, they are independent control ports with different protocols.

aleksander :
Once it says ‘connected’ you need to:
ifup wwan0
dhclient wwan0
Hopefully your modem will like DHCP to get the IP.

only ifup wdm0 works for me.

then
neither udhcpc wwan0 nor udhcpc wdm0 works

mt

Hopefully your modem will like DHCP to get the IP.

$ qmi-network /dev/cdc-wdm0 start
Starting network with ‘qmicli -d /dev/cdc-wdm0 –wds-start-network= –client-no-release-cid’…
Saving state… (CID: 45)
Saving state… (PDH: 34039896)
Network started successfully

$ qmi-network /dev/cdc-wdm0 status
Loading previous state…
Previous CID: 45
Previous PDH: 34039896
Getting status with ‘qmicli -d /dev/cdc-wdm0 –wds-get-packet-service-status –client-cid=45 –client-no-release-cid’…
Status: connected

$ifup wdm0

$ ifconfig wwan0
wwan0 Link encap:Ethernet HWaddr 00:A0:C6:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

> “It is probably not more difficult than getting a lsusb -v dump and add whatever needed to make cdc_wdm handle the QMI/wwan control interface.”

Aleksander, if you need any info about the Huawei E392 (like a lsusb -v) just ask and I’ll gladly post it. I’m also reachable via the #openwrt IRC channel (same nick).