Re: How to Test NetworkManager 0.9
Em Wednesday 08 June 2011, David Narvaez escreveu: > Hi, Hi, > My ultimate goal is to test KDE's NetworkManager client which is now > being developed for NM 0.9. I fetched NM's git code and compiled and > installed the master branch over the binaries that my distro has for > NM which is version 0.8.2. At that point, I have no KDE NetworkManager > installed. I then run nm-tool and I can't see any available wireless > network. Am I missing any step to get NM 0.9 working? I'm not even > sure if I should be able to list available wireless networks without > installing KDE's Network Management code, should I? You need to install NetworkManager 0.9 and then compile the nm09 branch from KDE's networkmanagement repository: git clone git://anongit.kde.org/networkmanagement cd networkmanagement git checkout nm09 mkdir build cd build cmake -DCMAKE_INSTALL_PREFIX=/usr .. make make install You can send e-mails about KDE's NM client (I call it Plasma NM) to our mailing list: http://mail.kde.org/mailman/listinfo/kde-networkmanager -- Lamarque V. Souza http://www.geographicguide.com/brazil.htm Linux User #57137 - http://counter.li.org/ http://planetkde.org/pt-br ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
How to Test NetworkManager 0.9
Hi, My ultimate goal is to test KDE's NetworkManager client which is now being developed for NM 0.9. I fetched NM's git code and compiled and installed the master branch over the binaries that my distro has for NM which is version 0.8.2. At that point, I have no KDE NetworkManager installed. I then run nm-tool and I can't see any available wireless network. Am I missing any step to get NM 0.9 working? I'm not even sure if I should be able to list available wireless networks without installing KDE's Network Management code, should I? Thanks. David E. Narvaez ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Add a "primary" attribute to provider in the mobile broadband provider info database
Any chance of pushing this? -Jason On Fri, May 27, 2011 at 8:07 AM, Dan Williams wrote: > On Thu, 2011-05-26 at 15:24 -0400, Jason Glasgow wrote: > > I've noticed that some providers (e.g. AldiTalk/MedionMobile, blau.de, > > E-Plus, simyo Internet, NetCologne in Germany, or 3 in Sweden) all > > share the same set of PLMNs in the mobile broadband provider info > > (MBPI) database. This means that looking up a provider in the database > > based on the PLMN yields more than one provider. After talking to > > some providers, it appears that in certain instances one can read the > > SPN file from the SIM card and use this to disambiguate between the > > different provider entries in the database. > > > > > > Other carriers though have indicated that sometimes the SPN file on > > the SIM is empty (or non existent), and in that case one should select > > the 'primary' or default provider. > > > > > > I propose that we add an attribute to the provider entity to indicate > > that it is the 'primary' provider for a given set of PLMNs. > > > > > > Attached is a patch that defines the attribute and applies it to a few > > providers. > > > > > > Thoughts? > > I think it's a fine idea. Anyone have objections? > > Dan > > > > > -Jason > > ___ > > networkmanager-list mailing list > > networkmanager-list@gnome.org > > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [PATCH] ModemManager: Enhancements to Icera error reporting and access technology reporting
Thanks Aleksander! New patch file is attached.
Eric
On Tue, Jun 7, 2011 at 2:56 AM, Aleksander Morgado wrote:
> Hi Eric,
>
> > The additional error detail allows us to know that a connection failed
> > because of an invalid APN. Also, when handling access technology
> > changes, report the technology in use if we're connected. Finally,
> > avoid using CFUN=0 when disabling the modem.
>
> A small thing to fix in the patch.
>
> All callbacks receiving a response from the AT serial port should check
> if the modem has already been removed, so in
> query_network_error_code_done(), this check is needed just before trying
> to parse any reply:
>
>/* If the modem has already been removed, return without
> * scheduling callback */
>if (mm_callback_info_check_modem_removed (info))
>return;
>
> See
>
> http://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=9323daec015ecad65c39b6020b62e864c027d858
>
> Cheers!
>
> --
> Aleksander
>
>
From d145ada9a31ed043d3f9da09c3abf7a1c5f7aff6 Mon Sep 17 00:00:00 2001
From: Eric Shienbrood
Date: Mon, 6 Jun 2011 15:09:15 -0400
Subject: [PATCH] Icera enhancements.
- For connection failures, get additional error detail. Currently,
the only error codes that are mapped are the 3GPP TS 24.008 codes
for "Unknown or missing access point name" and "Requested service
option not subscribed" (which is sometimes returned for an invalid
APN).
- In Samsung plugin, for disable, don't use CFUN=0, since it prevents
some useful operations from being performed, e.g., getting PIN lock
status. Use CFUN=4 instead, which turns off the radios.
- In handling %NWSTATE messages, give the access mode in the connection
state field precedence over what's in the access technology field, so
that when connected, the actual technology in use is what gets
reported.
---
plugins/Makefile.am|3 ++
plugins/mm-modem-icera.c | 65
plugins/mm-modem-samsung-gsm.c |8 -
3 files changed, 61 insertions(+), 15 deletions(-)
diff --git a/plugins/Makefile.am b/plugins/Makefile.am
index c7a7a3d..4abb026 100644
--- a/plugins/Makefile.am
+++ b/plugins/Makefile.am
@@ -394,6 +394,9 @@ libmm_plugin_cinterion_la_LDFLAGS = \
-module \
-avoid-version
+libmm_plugin_samsung_la_LIBADD = \
+ $(builddir)/libicera-utils.la
+
udevrulesdir = $(UDEV_BASE_DIR)/rules.d
udevrules_DATA = \
77-mm-ericsson-mbm.rules \
diff --git a/plugins/mm-modem-icera.c b/plugins/mm-modem-icera.c
index b093b34..fd597c0 100644
--- a/plugins/mm-modem-icera.c
+++ b/plugins/mm-modem-icera.c
@@ -192,11 +192,13 @@ nwstate_to_act (const char *str)
return MM_MODEM_GSM_ACCESS_TECH_UMTS;
else if (!strcmp (str, "3g"))
return MM_MODEM_GSM_ACCESS_TECH_UMTS;
-else if (!strcmp (str, "3G-HSDPA"))
+else if (!strcmp (str, "R99"))
+return MM_MODEM_GSM_ACCESS_TECH_UMTS;
+else if (!strcmp (str, "3G-HSDPA") || !strcmp (str, "HSDPA"))
return MM_MODEM_GSM_ACCESS_TECH_HSDPA;
-else if (!strcmp (str, "3G-HSUPA"))
+else if (!strcmp (str, "3G-HSUPA") || !strcmp (str, "HSUPA"))
return MM_MODEM_GSM_ACCESS_TECH_HSUPA;
-else if (!strcmp (str, "3G-HSDPA-HSUPA"))
+else if (!strcmp (str, "3G-HSDPA-HSUPA") || !strcmp (str, "HSDPA-HSUPA"))
return MM_MODEM_GSM_ACCESS_TECH_HSPA;
return MM_MODEM_GSM_ACCESS_TECH_UNKNOWN;
@@ -219,7 +221,9 @@ nwstate_changed (MMAtSerialPort *port,
g_free (str);
}
-str = g_match_info_fetch (info, 3);
+str = g_match_info_fetch (info, 4);
+if (!str || strcmp (str, "-") == 0)
+ str = g_match_info_fetch (info, 3);
if (str) {
act = nwstate_to_act (str);
g_free (str);
@@ -357,13 +361,50 @@ icera_disconnect_done (MMModem *modem,
}
static void
+query_network_error_code_done (MMAtSerialPort *port,
+ GString *response,
+ GError *error,
+ gpointer user_data)
+{
+MMModemIcera *self = MM_MODEM_ICERA (user_data);
+MMModemIceraPrivate *priv = MM_MODEM_ICERA_GET_PRIVATE (self);
+MMCallbackInfo *info = priv->connect_pending_data;
+gboolean mobile_error = FALSE;
+
+/* If the modem has already been removed, return without
+ * scheduling callback */
+if (mm_callback_info_check_modem_removed (info))
+return;
+
+if (info && g_str_has_prefix (response->str, "%IER: ")) {
+int nw_activation_err;
+if (sscanf (response->str + 6, "%*d,%*d,%d", &nw_activation_err)) {
+/* 3GPP TS 24.008 Annex G error codes:
+ * 27 - Unknown or missing access point name
+ * 33 - Requested service option not subscribed
+ */
+if (nw_activation_err == 27 || nw_activation_err == 33) {
+info->error =
+mm_mobile_error_for_code(MM_MOBILE_ERROR_GPRS_NOT_SUBSCRIBED);
+mobile_error = TRUE;
+
Re: UMTS Device - T Mobile Web And Walk
Hi, no there was no device node created named like /dev/hso0, but the sysfs interface was created. Inside the sysfs path i don't see the "file" "dev", which should contain the device node information. So udev has no idea how to create this device node. Dan: What does ls -l /dev/hso0 show for your device? --snip-- #cd /sys/class/net/hso0/ /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/net/hso0 $ ls -l -r--r--r--1 root root 4096 Jun 7 09:46 addr_assign_type -r--r--r--1 root root 4096 Jun 7 2011 addr_len -r--r--r--1 root root 4096 Jun 7 09:46 address -r--r--r--1 root root 4096 Jun 7 09:46 broadcast -r--r--r--1 root root 4096 Jun 7 09:46 carrier -r--r--r--1 root root 4096 Jun 7 09:46 dev_id lrwxrwxrwx1 root root 0 Jun 7 09:46 device -> ../../../1-1.1:1.0 -r--r--r--1 root root 4096 Jun 7 09:46 dormant -r--r--r--1 root root 4096 Jun 7 09:46 duplex -r--r--r--1 root root 4096 Jun 7 09:46 features -rw-r--r--1 root root 4096 Jun 7 2011 flags -rw-r--r--1 root root 4096 Jun 7 09:46 ifalias -r--r--r--1 root root 4096 Jun 7 2011 ifindex -r--r--r--1 root root 4096 Jun 7 09:46 iflink -r--r--r--1 root root 4096 Jun 7 09:46 link_mode -rw-r--r--1 root root 4096 Jun 7 09:46 mtu -r--r--r--1 root root 4096 Jun 7 09:46 operstate drwxr-xr-x2 root root 0 Jun 7 09:46 power drwxr-xr-x4 root root 0 Jun 7 09:46 queues -r--r--r--1 root root 4096 Jun 7 09:46 speed drwxr-xr-x2 root root 0 Jun 7 09:46 statistics lrwxrwxrwx1 root root 0 Jun 7 2011 subsystem -> ../../../../../../../../../class/net -rw-r--r--1 root root 4096 Jun 7 09:46 tx_queue_len -r--r--r--1 root root 4096 Jun 7 2011 type -rw-r--r--1 root root 4096 Jun 7 2011 uevent /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/net/hso0 $ ls device/dev ls: device/dev: No such file or directory --snip-- Harald Am Montag, 6. Juni 2011, 23:48:42 schrieb Dan Williams: > Just to confirm, you do *not* have a /dev/hso0? Do you > have /sys/class/net/hso0 after plugging the device in? > > I just tried out my iCON 452 and it does provide the hso0 interface that > we'd expect, and that's what ModemManager expects too. > > Dan > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
