l put the details in your merge request about that.
Louis-Alexis
From: ModemManager-devel on
behalf of Louis-Alexis Eyraud
Sent: 12 August 2020 14:10
To: Aleksander Morgado
Cc: ModemManager (development)
Subject: Re: Help on an invalid modem case
Hi Aleks
20 13:33
> To: Louis-Alexis Eyraud
> Cc: ModemManager (development) <
> modemmanager-devel@lists.freedesktop.org>
> Subject: Re: Help on an invalid modem case
>
> Hey Louis-Alexis,
>
> > sorry for the delay, I was on holiday the past weeks.
> > I've r
: Aleksander Morgado
Sent: 12 August 2020 13:33
To: Louis-Alexis Eyraud
Cc: ModemManager (development)
Subject: Re: Help on an invalid modem case
Hey Louis-Alexis,
> sorry for the delay, I was on holiday the past weeks.
> I've retrieved the "faulty" 3G modem device from my office. Fo
Hey Louis-Alexis,
> sorry for the delay, I was on holiday the past weeks.
> I've retrieved the "faulty" 3G modem device from my office. For information,
> the exact model is Huawei e352u-21 (other e352 variants I tested do not seem
> to provoke the issue).
>
> I did a more standard setup at home
ned,
feel free to contact me privately to give you access to this setup.
Regards,
From: Aleksander Morgado
Sent: 07 July 2020 08:44
To: Louis-Alexis Eyraud
Cc: ModemManager (development)
Subject: Re: Help on an invalid modem case
Hey Louis-Alexis,
>
>
Hey Louis-Alexis,
>
> logs for the E3372h device.
>
in this case, we see two interfaces, and both flagged wrongly as PPP:
USB if#0 ---> ttyUSB0 ---> ff/2/18 ---> PPP
USB if#1 ---> ttyUSB1 ---> ff/2/1 ---> PPP
The reason for ttyUSB1 flagged as PPP is legit, that is ok, because
ff/2/1 implies bei
Hey,
>
> I tried the udev rules you suggest and the serial timeouts occurrences
> disappear for the device.
> Even if the attached log don't show it, the device got connected to the
> network after multiple attempts. The connection is stable and functional now
> (over half an hour when I'm writ
Hey Lars,
> >> here are the logs you ask:
> >>- mmcli and lsusb output logs
> >>- the matching Modem Manager debug logs
> >>
> >> Hope it helps.
> >>
> >
> > It does help yes. I can see how we're using the wrong ttyUSB for data,
> > and I believe I know why this happens; we're mixing up th
On 7/6/2020 18:10, Aleksander Morgado wrote:
Hey!
here are the logs you ask:
- mmcli and lsusb output logs
- the matching Modem Manager debug logs
Hope it helps.
It does help yes. I can see how we're using the wrong ttyUSB for data,
and I believe I know why this happens; we're mixing
Hey again,
> > here are the logs you ask:
> > - mmcli and lsusb output logs
> > - the matching Modem Manager debug logs
> >
> > Hope it helps.
> >
>
> It does help yes. I can see how we're using the wrong ttyUSB for data,
> and I believe I know why this happens; we're mixing up the
> huawei-sp
Hey!
>
> here are the logs you ask:
> - mmcli and lsusb output logs
> - the matching Modem Manager debug logs
>
> Hope it helps.
>
It does help yes. I can see how we're using the wrong ttyUSB for data,
and I believe I know why this happens; we're mixing up the
huawei-specific GETPORTMODE logi
Hey,
> my team and I are using for testing purposes an 3G USB modem (Huawei E352)
> that has an unexpected behaviour with ModemManager 1.12.10 and later stable
> versions (1.12.12 and 1.14.0).
> The 3G modem is used as a broadband one and every time it disconnects, it
> encounters AT serial timeo
12 matches
Mail list logo
