> > So the real problem here is that the Cinterion modem sends a NUL byte
> > before the CONNECT response:
> >
> > > [mm-at-serial-port.c:298] debug_log(): (ttyS1): --> 'ATD*99***1#'
> > > modem-manager[2621]: [1317807408.548825]
> > > [mm-at-serial-port.c:298] debug_log(): (ttyS1): <-- '\0'
>
On Thu, 2011-10-13 at 22:12 +0200, Aleksander Morgado wrote:
> Hi,
>
> So the real problem here is that the Cinterion modem sends a NUL byte
> before the CONNECT response:
>
> > [mm-at-serial-port.c:298] debug_log(): (ttyS1): --> 'ATD*99***1#'
> > modem-manager[2621]: [1317807408.548825]
> > [m
Hi Aleksander,
The attached patch solved the problem. Thanks!
Cheers,
Tom
On 13/10/11 22:12, Aleksander Morgado wrote:
Hi,
So the real problem here is that the Cinterion modem sends a NUL byte
before the CONNECT response:
[mm-at-serial-port.c:298] debug_log(): (ttyS1): --> 'ATD*99***1#'
m
Hi,
So the real problem here is that the Cinterion modem sends a NUL byte
before the CONNECT response:
> [mm-at-serial-port.c:298] debug_log(): (ttyS1): --> 'ATD*99***1#'
> modem-manager[2621]: [1317807408.548825]
> [mm-at-serial-port.c:298] debug_log(): (ttyS1): <-- '\0'
> modem-manager[2621]:
Hi Aleksander,
On 06/10/11 10:05, Aleksander Morgado wrote:
Hey Thomas,
To reproduce, i do the following:
1 ) stop NM, MM and disconnect the modem from power supply
2 ) connect the modem to power supply
3 ) start MM: modem-manager --debug --log-level=DEBUG
4 ) start NM: /etc/init.d/network-m
Hey Thomas,
>
> To reproduce, i do the following:
>
> 1 ) stop NM, MM and disconnect the modem from power supply
> 2 ) connect the modem to power supply
> 3 ) start MM: modem-manager --debug --log-level=DEBUG
> 4 ) start NM: /etc/init.d/network-manager start
> 5 ) nmcli con up uuid baa2af1b-e21e