** Attachment added: "/var/log/messages during connection attempt (relates to
attachment #2)"
http://launchpadlibrarian.net/30421380/messages.log
** Summary changed:
- karmic: connection through usb GSM stick stopped working
+ karmic: huawei gsm modem not working anymore
** Description changed:
-
I'm using a Fonic Surfstick (Huawei E220 usb id 12d1:1003) which works fine
under Jaunty
but connections cannot be established under current karmic with all updates
installed as of
today.
- pppd does not report anything suspicious and obtains two DNS entries. Those
however
- are not written to /etc/resolv.conf and the connection does not complete for
some reason.
- This is also indicated by the network-manager panel icon which remains in the
animated 'connecting' state.
+ Looking at the output of /var/log/messages and /var/log/daemon.log it appears
that
+ network-manager (or modem-manager?) is stuck after completion of stage 4.
+ It stops at after reaching "(IP4 Configure Get) complete" and never starts
with
+ Stage 5.
- pppd does report that it cannot determine the remote ip, but that is also the
case under the
- jaunty and does not really matter anyway. The route is set as expected
(everything routed through
- the default ppp remote ip 10.64.64.64)
+ At this point the usb modem already reports a stable connection.
- plugging the card in my desktop PC running jaunty everything works as
expected. Using the
- guided setup from network-manager the provider (FONIC) is selected and PIN
entered. Connection
- works out of the box.
+ I would have added the output of `modem-manager debug` but I don't know how to
+ start the modem-manager in debug mode. If anyone provides info I can log that
+ as well.
+
+ I should mention that this works fine on my desktop PC running Jaunty.
** Tags added: gsm huawei modem
** Also affects: network-manager
Importance: Undecided
Status: New
** Also affects: modemmanager
Importance: Undecided
Status: New
--
karmic: huawei gsm modem not working anymore
https://bugs.launchpad.net/bugs/413989
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
