Re: Where and how to install D02HW in ConnectionManager?

[Jacobs Shannon <shanen yahoo co jp>]

More time to experiment with this again, and still feel like I'm
overlooking something extremely obvious... Fresh run at the bar
time. Today I started from the information on this webpage:

https://wiki.ubuntu.com/NetworkManager/Hardware/3G

Completely different computer today, but still using Ubuntu 8.10. My
new idea was to start with the configuration file from another
country where the device is supposed to work without problems. I
decided to use Tele2 in Sweden as my source (partly based on some
information from yet another webpage). That part of the idea seemed
to be easy to implement. The only things that seemed to call for
changing were the phone number, the password, and the APN. I gave it
a fresh name (emobile in Japan), and it seemed to be saved in the
correct place on my menu of possible connections. However, when I
attempt to use it, the result as reported in the daemon.log file is:

Feb 13 14:50:57 r52HH-shanen NetworkManager: <info>  Activation
(ttyUSB0) Stage 1 of 5 (Device Prepare) complete. 
Feb 13 14:50:57 r52HH-shanen NetworkManager: <info>  (ttyUSB0):
powering up... 
Feb 13 14:51:05 r52HH-shanen NetworkManager: <WARN> 
automatic_registration_response(): Automatic registration failed:
not registered and not searching. 
Feb 13 14:51:05 r52HH-shanen NetworkManager: <info>  (ttyUSB0):
device state change: 4 -> 9 
Feb 13 14:51:05 r52HH-shanen NetworkManager: <debug>
[1234504265.530513] nm_serial_device_close(): Closing device
'ttyUSB0' 
Feb 13 14:51:05 r52HH-shanen NetworkManager: <info>  Marking
connection 'emobile in Japan' invalid. 
Feb 13 14:51:05 r52HH-shanen NetworkManager: <info>  Activation
(ttyUSB0) failed. 
Feb 13 14:51:05 r52HH-shanen NetworkManager: <info>  (ttyUSB0):
device state change: 9 -> 3 
Feb 13 14:51:05 r52HH-shanen NetworkManager: <info>  (ttyUSB0):
deactivating device (reason: 0). 
Feb 13 14:51:05 r52HH-shanen NetworkManager:
nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx
>= 0' failed
Feb 13 14:51:05 r52HH-shanen NetworkManager:
nm_system_device_flush_ip4_addresses_with_iface: assertion
`iface_idx >= 0' failed
Feb 13 14:51:21 r52HH-shanen NetworkManager: <info>  (eth0): carrier
now OFF (device state 8) 
Feb 13 14:51:21 r52HH-shanen NetworkManager: <info>  (eth0): device
state change: 8 -> 2 
Feb 13 14:51:21 r52HH-shanen NetworkManager: <info>  (eth0):
deactivating device (reason: 0). 
Feb 13 14:51:21 r52HH-shanen NetworkManager: <info>  eth0: canceled
DHCP transaction, dhcp client pid 6097 
Feb 13 14:51:21 r52HH-shanen NetworkManager: <WARN> 
check_one_route(): (eth0) error -34 returned from rtnl_route_del():
Sucess  
Feb 13 14:51:21 r52HH-shanen avahi-daemon[5506]: Withdrawing address
record for 9.68.40.146 on eth0.
Feb 13 14:51:21 r52HH-shanen avahi-daemon[5506]: Leaving mDNS
multicast group on interface eth0.IPv4 with address 9.68.40.146.
Feb 13 14:51:21 r52HH-shanen avahi-daemon[5506]: Interface eth0.IPv4
no longer relevant for mDNS.
Feb 13 14:51:30 r52HH-shanen NetworkManager: <info>  Activation
(ttyUSB0) starting connection 'emobile in Japan' 
Feb 13 14:51:30 r52HH-shanen NetworkManager: <info>  (ttyUSB0):
device state change: 3 -> 4 
Feb 13 14:51:30 r52HH-shanen NetworkManager: <info>  Activation
(ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... 
Feb 13 14:51:30 r52HH-shanen NetworkManager: <info>  Activation
(ttyUSB0) Stage 1 of 5 (Device Prepare) started... 
Feb 13 14:51:30 r52HH-shanen NetworkManager: <debug>
[1234504290.485461] nm_serial_device_open(): (ttyUSB0) opening
device... 
Feb 13 14:51:30 r52HH-shanen NetworkManager: <info>  Activation
(ttyUSB0) Stage 1 of 5 (Device Prepare) complete. 
Feb 13 14:51:30 r52HH-shanen NetworkManager: <info>  (ttyUSB0):
powering up... 
Feb 13 14:51:38 r52HH-shanen NetworkManager: <WARN> 
automatic_registration_response(): Automatic registration failed:
not registered and not searching. 
Feb 13 14:51:38 r52HH-shanen NetworkManager: <info>  (ttyUSB0):
device state change: 4 -> 9 
Feb 13 14:51:38 r52HH-shanen NetworkManager: <debug>
[1234504298.392522] nm_serial_device_close(): Closing device
'ttyUSB0' 
Feb 13 14:51:38 r52HH-shanen NetworkManager: <info>  Marking
connection 'emobile in Japan' invalid. 
Feb 13 14:51:38 r52HH-shanen NetworkManager: <info>  Activation
(ttyUSB0) failed. 
Feb 13 14:51:38 r52HH-shanen NetworkManager: <info>  (ttyUSB0):
device state change: 9 -> 3 
Feb 13 14:51:38 r52HH-shanen NetworkManager: <info>  (ttyUSB0):
deactivating device (reason: 0). 
Feb 13 14:51:38 r52HH-shanen NetworkManager:
nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx
>= 0' failed
Feb 13 14:51:38 r52HH-shanen NetworkManager:
nm_system_device_flush_ip4_addresses_with_iface: assertion
`iface_idx >= 0' failed

Intuitively obvious to the most casual observer? If I'm
understanding it correctly, this part of the extended tail actually
starts with the disconnection from the wired network, then shows the
ConnectionManager failing mightily, but contains no information
about the pon connection that I'm using now via the same D02HW
device. 

Based on the total reading and some unknown number of webpages, my
feeling is that this is *NOT* a hard thing to do, but I'm not
looking quite in the right direction. I also feel like someone
around this specific mailing list might be able to tell me where to
look, but so far I haven't been able to get the message.


--------------------------------------
Power up the Internet with Yahoo! Toolbar.
http://pr.mail.yahoo.co.jp/toolbar/