NetworkManager and Huawei E220/E270

[Joerg Bergmann]

In fedora 11, I have problems with the Huawei E220/E270 3G
USB stick (vendor 12d1, product 1003).
As I have learned, the problem seems to be with the
NetworkManager. Here is the relevant debug info:

[root at T40 ~]# /sbin/service NetworkManager stopNetworkManager-Daemon 
beenden:                             [  OK  ]
[root at T40 ~]# NM_SERIAL_DEBUG=1 NM_PPP_DEBUG=1 /usr/sbin/NetworkManager 
--no-daemon
NetworkManager: <info>  starting...
-- Error received: File exists
-- Original message: type=0x14 length=56 flags=<REQUEST,ACK,ATOMIC> 
sequence-nr=1248531737 pid=4196836
NetworkManager: <WARN>  nm_generic_enable_loopback(): error -17 returned 
from rtnl_addr_add():
Sucess

NetworkManager: <info>  (eth0): new Ethernet device (driver: 'e100')
NetworkManager: <info>  (eth0): exported as 
/org/freedesktop/Hal/devices/net_00_0d_60_60_60_cf
NetworkManager: <info>  (wlan1): driver supports SSID scans (scan_capa 
0x01).
NetworkManager: <info>  (wlan1): new 802.11 WiFi device (driver: 
'b43-pci-bridge')
NetworkManager: <info>  (wlan1): exported as 
/org/freedesktop/Hal/devices/net_00_14_a5_4d_8f_16
NetworkManager: <info>  (ttyS0): ignoring due to lack of mobile 
broadband capabilties
NetworkManager: <info>  (eth0): device state change: 1 -> 2
NetworkManager: <info>  (eth0): bringing up device.
NetworkManager: <info>  (eth0): preparing device.
NetworkManager: <info>  (eth0): deactivating device (reason: 2).
NetworkManager: <info>  (wlan1): device state change: 1 -> 2
NetworkManager: <info>  (wlan1): bringing up device.
NetworkManager: <info>  (wlan1): preparing device.
NetworkManager: <info>  (wlan1): deactivating device (reason: 2).
NetworkManager: <info>  (wlan1): device state change: 2 -> 3
NetworkManager: <info>  (wlan1): supplicant interface state:  starting 
-> ready
NetworkManager: <info>  (ttyUSB1): ignoring due to lack of mobile 
broadband capabilties
NetworkManager: <info>  (ttyUSB0): found serial port (udev:  hal:GSM)
NetworkManager: <info>  (ttyUSB0): ignoring due to lack of probed mobile 
broadband capabilties

Any hints? Any suggestions?

Joerg