I'm not sure if this list allows attachments.
I send two log files attached:
ndis.txt -- System logs (ModemManager in debug mode) of an unsuccessful NDIS 
Huawei connection attempt.
attachmodem-txt -- ModemManager logs where the usb modem is not detected the 
first time it is plugged in the computer, the second time the MM detects it.

If you need more logs don't hesitate to ask for them.

________________________________________
De: Aleksander Morgado [aleksan...@lanedo.com]
Enviado el: miércoles, 20 de febrero de 2013 15:40
Para: Gonzalez Calabozo, Jose Maria
CC: networkmanager-list@gnome.org
Asunto: Re: [MM] Problem Huawei E303

> Thanks for your fast response! and thanks for the new NewtorkManager 
> packages. I have installed them and they seem to work fine.
>
> I was using a Git version from the 18th. This morning I have updated my local 
> version with the latest version from the repository.
>
> I have tried with the Huawei e303 modem and it tries to create an NDIS 
> connection, but it doesn't work.
> So I have removed the net interface from mm-plugin-huawei.c
>
> --- a/plugins/huawei/mm-plugin-huawei.c
> +++ b/plugins/huawei/mm-plugin-huawei.c
> @@ -492,7 +492,7 @@ grab_port (MMPlugin *self,
>  G_MODULE_EXPORT MMPlugin *
>  mm_plugin_create (void)
>  {
> -    static const gchar *subsystems[] = { "tty", "net", "usb", NULL };
> +    static const gchar *subsystems[] = { "tty", "usb", NULL };
>      static const guint16 vendor_ids[] = { 0x12d1, 0 };
>      static const MMAsyncMethod custom_init = {
>          .async  = G_CALLBACK (huawei_custom_init),
>
> Now it always try to connect through pppd and it always works :) I haven't 
> the port problem that the previous version has.
> Has anyone been able to connect through NDIS with a Huawei modem? With which 
> model?
>

Can you send us debug logs of MM while we try to use the NDIS port? We
added support for net ports very recently in the Huawei plugin, actually
Huawei themselves started that work and they tested it with different
modems.


> I have found another issue that I am not sure if it is a bug or not. It seems 
> that the ModemManager cannot detect the first time that I insert the modem.
> After try with many ports it prints the next lines:
> ModemManager[7749]: <debug> [1361368039.448167] [mm-serial-port.c:994] 
> mm_serial_port_close(): (ttyUSB0) device open count is 0 (close)
> ModemManager[7749]: <debug> [1361368039.448198] [mm-serial-port.c:1010] 
> mm_serial_port_close(): (ttyUSB0) closing serial port...
> ModemManager[7749]: <debug> [1361368039.449123] [mm-serial-port.c:1041] 
> mm_serial_port_close(): (ttyUSB0) serial port closed
> ModemManager[7749]: <debug> [1361368039.449164] [mm-serial-port.c:1109] 
> mm_serial_port_close_force(): (ttyUSB0) forced to close port
> ModemManager[7749]: <debug> [1361368039.449231] [mm-plugin-manager.c:352] 
> plugin_supports_port_ready(): (Plugin Manager) (Huawei) [ttyUSB0] found best 
> plugin for port
> ModemManager[7749]: <debug> [1361368039.449274] [mm-plugin-manager.c:238] 
> port_probe_context_finished(): (Plugin Manager) 'ttyUSB0' port probe 
> finished, last one in device, but minimum probing time not consumed yet 
> ('24.443516' seconds elapsed)
>
> But If I unplug and plug it again it will recognize the modem.
>

Ah, my heisenbug. Yes, I've been the whole morning trying to reproduce
it after I saw it yesterday. We configure a timeout to be run 2s after
we initialize the device probing, but for some reason it doesn't get
fired. Nice to see that I'm not the only one seeing it, will try to
track it down these days. Do you have a full debug log of this issue
happening? Or just that snippet?

--
Aleksander

Este correo electrónico y, en su caso, cualquier fichero anexo al mismo, 
contiene información de carácter confidencial exclusivamente dirigida a su 
destinatario o destinatarios. Si no es vd. el destinatario indicado, queda 
notificado que la lectura, utilización, divulgación y/o copia sin autorización 
está prohibida en virtud de la legislación vigente. En el caso de haber 
recibido este correo electrónico por error, se ruega notificar inmediatamente 
esta circunstancia mediante reenvío a la dirección electrónica del remitente.
Evite imprimir este mensaje si no es estrictamente necesario.

This email and any file attached to it (when applicable) contain(s) 
confidential information that is exclusively addressed to its recipient(s). If 
you are not the indicated recipient, you are informed that reading, using, 
disseminating and/or copying it without authorisation is forbidden in 
accordance with the legislation in effect. If you have received this email by 
mistake, please immediately notify the sender of the situation by resending it 
to their email address.
Avoid printing this message if it is not absolutely necessary.
_______________________________________________
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Reply via email to