*** This bug is a duplicate of bug 290177 ***
https://bugs.launchpad.net/bugs/290177
looking at the log this seems to be a dupe of bug 290177 ... i attached
a patch for that issue there. Please test.
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Medium
Status: Con
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Confirmed
--
0.7 "New" 3G config dialogue broke my Huawei E220 support
https://bugs.launchpad.net/bugs/289690
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
I can confirm Peter:s problem with the PIN code. And judging from the amount of
questions about network manager and 3G on the swedish forum I know we are not
the only ones.
But I don't know if it has anything to do with the original access right
problems? Maybe it should be a separate bug?
--
Thanks for the tip. I'll give it a try. It doesn't solve the underlying
problem though, namely that NM 0.7 still seems to have some quirks that
needs ironing out in PIN handling. I can get online so it's just a minor
annoyance, I'll try your tip in the mean time.
--
0.7 "New" 3G config dialogue b
It is possible to run the above "wvdial pin" through udev. It works for
me.
The udev rule should look like: (Called
/etc/udev/rules.d/86-telia.rules)
ACTION=="add", SUBSYSTEMS=="usb", ATTRS{idVendor}=="12d1",
ATTRS{idProduct}=="1001", RUN+="/usr/bin/wvdial pin"
Maybe idVendor and/or idProduct
the command 'wvdial pin' simply unlocks the device, this is the command used:
(my pin replaced with )
[Dialer pin]
Modem = /dev/ttyUSB0
Baud = 460800
Init1 =AT+Cpin=
--
0.7 "New" 3G config dialogue broke my Huawei E220 support
https://bugs.launchpad.net/bugs/289690
You received this bu
so what command does wvdial send when you do the pin stuff there?
--
0.7 "New" 3G config dialogue broke my Huawei E220 support
https://bugs.launchpad.net/bugs/289690
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
OK.
Here is the nm-serial.txt
Tried first to connect E220 and login, did not work. Then deleted auto
gsm profile and created a new one, wrote PIN code in the profile and
tried to connect. Didn't work. Then did wvdial pin to unlock pin and
tried to connect, worked on second attempt. (First fail ma
ok, please do this instead:
# become root
sudo su
#now run like above:
NM_SERIAL_DEBUG=1 NetworkManager --no-daemon 2>&1 | tee /tmp/nm-serial.txt
then attach the nm-serial.txt (there should be quite a bunch more output
when trying to dial).
--
0.7 "New" 3G config dialogue broke my Huawei E220
hmm .. somehow the serial debug didnt work. wierd. there should be more
stuff from modem communication.
--
0.7 "New" 3G config dialogue broke my Huawei E220 support
https://bugs.launchpad.net/bugs/289690
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
OK
Here is the output after just connecting E220 without unlocking PIN
first, trying to connect:
NetworkManager: ttyUSB0: driver is 'option'.
NetworkManager: [1225549631.683082] setup_monitor_device(): No
monitoring udi provided
NetworkManager: Found new Modem device 'ttyUSB0'.
NetworkManag
please stop NM:
sudo /etc/init.d/NetworkManager stop
then start it on the terminal like:
NM_SERIAL_DEBUG=1 sudo NetworkManager --no-daemon
please reproduce and attach the output here.
--
0.7 "New" 3G config dialogue broke my Huawei E220 support
https://bugs.launchpad.net/bugs/289690
You recei
OK, tried removing libmbca0, delete the Netcom profile and reboot - made
no difference.
Able to connect with auto connection profile, but only after I unlock
PIN via wvdial first. Seems NM still is not able to unlock my E220 PIN
on its own.
--
0.7 "New" 3G config dialogue broke my Huawei E220 su
ok, please try:
1. remove device
2. remove libmbca0 package
3. remove your current connection in connection-editor
4. restart
5. plugin your device and use the use the "auto connection" for your mobile
device.
Does that work better?
--
0.7 "New" 3G config dialogue broke my Huawei E220 support
I tried to fill in my PIN, but there seems to be two problems with it:
1) If connection is a "System setting" (i.e. system-wide) network-
manager refuses to remember PIN.
2) If connection is NOT "system setting", network-manager remembers PIN
but is unable to unlock device (E220)
I can now get
did you try to fill in your pin etc. in the connection editor? If that
doesn't help, please remove the current connection from connection
editor, then remove the libmbca0 package and plug in your device again.
Now there should be a "auto GSM" connection in the network-manager tray
applet. Try that
16 matches
Mail list logo
