Re: Huawei E220 can't connect on Ubuntu 11.10

[Aleksander Morgado <aleksander lanedo com>]

Hey Dan,

>>
>> On Ubuntu 11.10 there is problem with connection via modem Huawei E220.
>>
>> On Ubuntu 11.10 the NetworkManager is in version 0.9.1.90-0ubuntu5.1
>> On Ubunto 11.04 there is version 0.8.4~git.20110319t175609.d14809b-0ubuntu3
>>
>> The issue for Ubuntu was submitted:
>> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/868034
>>
>> I suspect that this problem could be related to NetworkManager.
>> One of the most interesting comment is available at:
>> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/868034/comments/86
>>
>> Could you please take a look at this bug?
> 
> Looks like https://bugzilla.gnome.org/show_bug.cgi?id=662113 to me.
> 
> What would be helpful would be to test this with the latest
> NetworkManager, from git head. You'll need libnl3 3.2.3 for that,
> which is not yet in Ubuntu (or to patch the configure.ac file to avoid
> blocking the build for that). There's preliminary packages for libnl3
> 3.2.3 in the daily builds PPA for NetworkManager for Ubuntu:
> http://launchpad.net/~network-manager/+archive/trunk. You may want to
> test this, which also includes a very recent snapshot from git (from
> the 10th of December). The problem is, these packages are largely
> untested, so no garantees that anything is fixed, or that it doesn't
> break your system. This is further complicated by the fact that
> reverting from libnl3 3.2.3 might not be all that easy, but it's
> definitely possible.
> 
> I'm updating the Ubuntu bug report now to add a procedure for testing.
> 

This issue seems to have been tracked up to commit dc89c0. With that
patch on, the modems get rebooted when they start to get commands in the
secondary port. From what I saw in the logs, we do enable unsolicited
messages in the secondary port during modem enable with AT^CURC=1, and
then we also send commands to it (AT+CREG/CGREG=2, to enable unsolicited
registration messages), which is the time when the hang & reboot happens.

I would suggest to revert that commit until a better solution is found
and ideally make a new stable release.

Also, did we try to completely avoid sending any command to the
secondary port once unsolicited messages were enabled on it? I can try
to hack such behaviour and then ask bug reporters to test it.

-- 
Aleksander