I forgot to send it to the list also!
Hi Dan, AAAH, this looks verbose !!!!!! : This happens when I try to connect with my 'Vodafone' Profile: NetworkManager: <info> Activation (ttyHS0) starting connection 'Vodafone (D2)' NetworkManager: <info> (ttyHS0): device state change: 3 -> 4 NetworkManager: <info> Activation (ttyHS0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: <info> Activation (ttyHS0) Stage 1 of 5 (Device Prepare) started... NetworkManager: <debug> [1234989563.668144] nm_serial_device_open(): (ttyHS0) opening device... NetworkManager: <info> Activation (ttyHS0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: <debug> [1234989563.775937] nm_serial_debug(): Sending: 'ATZ E0 V1 X4 &C1 +FCLASS=0 ' NetworkManager: <debug> [1234989563.811010] nm_serial_debug(): Got: 'ATZ E0 V' NetworkManager: <debug> [1234989563.811969] nm_serial_debug(): Got: 'ATZ E0 V1 ' NetworkManager: <debug> [1234989563.813964] nm_serial_debug(): Got: 'ATZ E0 V1 X4' NetworkManager: <debug> [1234989563.815982] nm_serial_debug(): Got: 'ATZ E0 V1 X4 ' NetworkManager: <debug> [1234989563.817964] nm_serial_debug(): Got: 'ATZ E0 V1 X4 ' NetworkManager: <debug> [1234989563.821695] nm_serial_debug(): Got: 'ATZ E0 V1 X4 C' NetworkManager: <debug> [1234989563.822050] nm_serial_debug(): Got: 'ATZ E0 V1 X4 CA' NetworkManager: <debug> [1234989563.823958] nm_serial_debug(): Got: 'ATZ E0 V1 X4 CA=' NetworkManager: <WARN> init_done(): Modem initialization timed out NetworkManager: <info> (ttyHS0): device state change: 4 -> 9 NetworkManager: <debug> [1234989574.004563] nm_serial_device_close(): Closing device 'ttyHS0' NetworkManager: <info> Marking connection 'Vodafone (D2)' invalid. NetworkManager: <info> Activation (ttyHS0) failed. NetworkManager: <info> (ttyHS0): device state change: 9 -> 3 NetworkManager: <info> (ttyHS0): deactivating device (reason: 0). NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed NetworkManager: <debug> [1234989598.028116] periodic_update(): Roamed from BSSID 00:1A:4F:95:5D:BC (TIMBUKTU) to (none) ((none)) This happens on startup: NetworkManager: <info> starting... NetworkManager: <info> eth0: driver is 'tg3'. NetworkManager: <info> Found new Ethernet device 'eth0'. NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_1f_29_87_87_d6 NetworkManager: <info> eth1: driver is 'wl'. NetworkManager: <info> eth1: driver does not support SSID scans (scan_capa 0x00). NetworkManager: <info> Found new 802.11 WiFi device 'eth1'. NetworkManager: <info> (eth1): exported as /org/freedesktop/Hal/devices/net_00_21_00_03_11_f4 NetworkManager: <info> ttyHS0: driver is 'hso'. NetworkManager: <debug> [1234989502.979939] setup_monitor_device(): No monitoring udi provided NetworkManager: <info> Found new Modem device 'ttyHS0'. NetworkManager: <info> (ttyHS0): exported as /org/freedesktop/Hal/devices/usb_device_af0_7011_Serial_Number_if0_serial_unknown_0 NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) 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> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) NetworkManager: <info> (eth1): device state change: 1 -> 2 NetworkManager: <info> (eth1): preparing device. NetworkManager: <info> (eth1): deactivating device (reason: 2). NetworkManager: <WARN> nm_device_wifi_disable_encryption(): error setting key for device eth1: Invalid argument NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) NetworkManager: <info> (ttyHS0): device state change: 1 -> 2 NetworkManager: <info> (ttyHS0): deactivating device (reason: 2). NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed NetworkManager: <info> (eth1): device state change: 2 -> 3 NetworkManager: <info> (ttyHS0): device state change: 2 -> 3 NetworkManager: <info> (eth1): supplicant interface state change: 1 -> 2. Knud On Wed, Feb 18, 2009 at 8:50 PM, Dan Williams <[email protected]> wrote: > On Wed, 2009-02-18 at 17:44 +0100, Knud Müller wrote: >> Hi, >> >> a few days ago i realized that my intrepid cannot connect with my umts >> card to the internet. I havent used it for weeks, so I started >> searching what has changed. I found out that there are no ttyUSB >> devices anylonger but ttyHS devices appeared (and dmesg told me when i >> plug/unplug). I think its one of the new kernels with hso. Network >> Manager still recognizes the card when I remove all configurations but >> is unable to connect. Ive installed HSOconnect and I can connect so >> generally NM should also be able to. I think HSOconnect is great but >> as I use the vpn to my cisco in NM and it works brilliantly I really >> like to either get back to the old dev/ttyUSB times or let NM do it >> with hso. >> >> How can I find out what is going wrong with NM and is there any log? >> Is someone having similar problems? > > Depends on what version of NetworkManager you're using; NM certainly > does support the 'hso' driver and newer Option cards (I have 3 and I > make sure they all work). If you're using the 20081018 snapshot series > that shipped with 8.10 there may be bugs in that that have since been > fixed. I did fix a few earlier this week that will be in NM 0.7.1 > related to PIN handling. > > You might be able to turn on serial debugging to help figure out what's > going wrong too. Stop the NetworkManager service, then open a terminal, > become root, then run: > > NM_SERIAL_DEBUG=1 /usr/sbin/NetworkManager --no-daemon > > and then try to connect. After it fails, grab the log output and reply > with it to this list, and we can see if that sheds some light on the > situation. > > Dan > > > _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
