Re: reconnect after sleeping
I am sorry, I think I did not send all the logs. I am attaching a file with all the process. thanks again. Manuel El 4 de agosto de 2009 14:33, Manuel José Contreras Maya < manuel.jose.contreras.m...@gmail.com> escribió: > Thanks Dan, these are the logs from when I sent the machine to sleep to the > reboot I had to do to get the connection again. Thanks for your help. > > Manuel > > > Aug 4 14:14:59 jeronimo NetworkManager: starting... > Aug 4 14:14:59 jeronimo NetworkManager: > nm_generic_enable_loopback(): error -17 returned from > rtnl_addr_add():#012Sucess#012 > Aug 4 14:14:59 jeronimo NetworkManager: Found radio killswitch > /org/freedesktop/Hal/devices/computer_rfkill_eeepc_wlan_wlan > Aug 4 14:14:59 jeronimo NetworkManager: (eth0): new Ethernet > device (driver: 'ATL1E') > Aug 4 14:14:59 jeronimo NetworkManager: (eth0): exported as > /org/freedesktop/Hal/devices/net_00_24_8c_7b_27_b7 > Aug 4 14:14:59 jeronimo NetworkManager: (wlan1): driver does not > support SSID scans (scan_capa 0x00). > Aug 4 14:14:59 jeronimo NetworkManager: (wlan1): new 802.11 WiFi > device (driver: 'ath_pci') > Aug 4 14:14:59 jeronimo NetworkManager: (wlan1): exported as > /org/freedesktop/Hal/devices/net_00_22_43_80_ce_22_0 > Aug 4 14:14:59 jeronimo NetworkManager: Trying to start the system > settings daemon... > Aug 4 14:14:59 jeronimo NetworkManager: > killswitch_getpower_reply(): Error getting killswitch power: Method > "GetPower" with signature "" on interface > "org.freedesktop.Hal.Device.KillSwitch" doesn't exist#012. > Aug 4 14:15:00 jeronimo nm-system-settings: Loaded plugin ifcfg-rh: (c) > 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager > mailing list. > Aug 4 14:15:00 jeronimo bluetoothd[2454]: Bluetooth daemon > Aug 4 14:15:01 jeronimo nm-system-settings:ifcfg-rh: parsing > /etc/sysconfig/network-scripts/ifcfg-wlan2 ... > Aug 4 14:15:01 jeronimo nm-system-settings:ifcfg-rh: error: > Invalid WEP key length. > Aug 4 14:15:01 jeronimo nm-system-settings:ifcfg-rh: parsing > /etc/sysconfig/network-scripts/ifcfg-eth0 ... > Aug 4 14:15:02 jeronimo kernel: Bluetooth: Core ver 2.13 > Aug 4 14:15:02 jeronimo kernel: NET: Registered protocol family 31 > Aug 4 14:15:02 jeronimo kernel: Bluetooth: HCI device and connection > manager initialized > Aug 4 14:15:02 jeronimo kernel: Bluetooth: HCI socket layer initialized > Aug 4 14:15:02 jeronimo bluetoothd[2454]: Starting SDP server > Aug 4 14:15:03 jeronimo kernel: Bluetooth: L2CAP ver 2.11 > Aug 4 14:15:03 jeronimo kernel: Bluetooth: L2CAP socket layer initialized > Aug 4 14:15:03 jeronimo bluetoothd[2454]: Parsing > /etc/bluetooth/input.conf failed: No such file or directory > Aug 4 14:15:03 jeronimo bluetoothd[2454]: Parsing > /etc/bluetooth/network.conf failed: No such file or directory > Aug 4 14:15:03 jeronimo kernel: Bluetooth: BNEP (Ethernet Emulation) ver > 1.3 > Aug 4 14:15:03 jeronimo kernel: Bluetooth: BNEP filters: protocol > multicast > Aug 4 14:15:03 jeronimo kernel: Bridge firewalling registered > Aug 4 14:15:03 jeronimo bluetoothd[2454]: bridge pan0 created > Aug 4 14:15:03 jeronimo bluetoothd[2454]: Parsing > /etc/bluetooth/audio.conf failed: No such file or directory > Aug 4 14:15:03 jeronimo kernel: Bluetooth: SCO (Voice Link) ver 0.6 > Aug 4 14:15:03 jeronimo kernel: Bluetooth: SCO socket layer initialized > Aug 4 14:15:03 jeronimo nm-system-settings:ifcfg-rh: read > connection 'System eth0' > Aug 4 14:15:03 jeronimo nm-system-settings:ifcfg-rh: Ignoring > connection 'System eth0' and its device because NM_CONTROLLED was false. > Aug 4 14:15:03 jeronimo NetworkManager: (eth0): now unmanaged > Aug 4 14:15:03 jeronimo nm-system-settings:ifcfg-rh: parsing > /etc/sysconfig/network-scripts/ifcfg-ethAgenteel ... > Aug 4 14:15:03 jeronimo nm-system-settings:ifcfg-rh: read > connection 'System ethAgenteel' > Aug 4 14:15:03 jeronimo nm-system-settings:ifcfg-rh: parsing > /etc/sysconfig/network-scripts/ifcfg-wlan1 ... > Aug 4 14:15:03 jeronimo nm-system-settings:ifcfg-rh: error: > Invalid WEP key length. > Aug 4 14:15:03 jeronimo nm-system-settings:ifcfg-rh: parsing > /etc/sysconfig/network-scripts/ifcfg-lo ... > Aug 4 14:15:03 jeronimo NetworkManager: (wlan1): device state > change: 1 -> 2 > Aug 4 14:15:04 jeronimo NetworkManager: (wlan1): preparing device. > Aug 4 14:15:04 jeronimo NetworkManager: (wlan1): deactivating > device (reason: 2). > Aug 4 14:15:04 jeronimo NetworkManager: check_one_route(): (wlan1) > error -34 returned from rtnl_route_del(): Sucess#012 > Aug 4 1
Re: reconnect after sleeping
scanning -> associating Aug 4 14:18:32 jeronimo NetworkManager: (wlan1): supplicant connection state: associating -> associated Aug 4 14:18:32 jeronimo NetworkManager: (wlan1): supplicant connection state: associated -> completed Aug 4 14:18:32 jeronimo NetworkManager: Activation (wlan1/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'ARNULFO'. Aug 4 14:18:32 jeronimo NetworkManager: Activation (wlan1) Stage 3 of 5 (IP Configure Start) scheduled. Aug 4 14:18:32 jeronimo NetworkManager: Activation (wlan1) Stage 3 of 5 (IP Configure Start) started... Aug 4 14:18:32 jeronimo NetworkManager: (wlan1): device state change: 5 -> 7 Aug 4 14:18:32 jeronimo NetworkManager: Activation (wlan1) Stage 4 of 5 (IP Configure Get) scheduled... Aug 4 14:18:32 jeronimo NetworkManager: Activation (wlan1) Stage 3 of 5 (IP Configure Start) complete. Aug 4 14:18:32 jeronimo NetworkManager: Activation (wlan1) Stage 4 of 5 (IP Configure Get) started... Aug 4 14:18:32 jeronimo NetworkManager: Activation (wlan1) Stage 5 of 5 (IP Configure Commit) scheduled... Aug 4 14:18:32 jeronimo NetworkManager: Activation (wlan1) Stage 4 of 5 (IP Configure Get) complete. Aug 4 14:18:32 jeronimo NetworkManager: Activation (wlan1) Stage 5 of 5 (IP Configure Commit) started... Aug 4 14:18:32 jeronimo avahi-daemon[2731]: Joining mDNS multicast group on interface wlan1.IPv4 with address 192.168.78.25. Aug 4 14:18:32 jeronimo avahi-daemon[2731]: New relevant interface wlan1.IPv4 for mDNS. Aug 4 14:18:32 jeronimo avahi-daemon[2731]: Registering new address record for 192.168.78.25 on wlan1.IPv4. Aug 4 14:18:33 jeronimo NetworkManager: (wlan1): device state change: 7 -> 8 Aug 4 14:18:33 jeronimo NetworkManager: Policy set 'Auto ARNULFO' (wlan1) as default for routing and DNS. Aug 4 14:18:33 jeronimo NetworkManager: Activation (wlan1) successful, device activated. Aug 4 14:18:33 jeronimo NetworkManager: Activation (wlan1) Stage 5 of 5 (IP Configure Commit) complete El 4 de agosto de 2009 11:47, Dan Williams escribió: > On Sat, 2009-08-01 at 13:50 -0500, Manuel José Contreras Maya wrote: > > Hello all, > > > > I wrote to this list a few weeks ago explaining a problem I had with > > an atheros card. I managed to install madwifi and things are much > > better now. I had to change as well the "channel" of my router from 6 > > to 10 to make it work. That is solved . > > > > The only thing is not working is when the machine goes to sleep and > > comes back there is no way to make the connection again. I have > > restarted the network service but it does not help. My machine is an > > Eee PC 1000HA running Fedora 10. With a card > > 01:00.0 Ethernet controller: Atheros Communications Inc. AR242x > > 802.11abg Wireless PCI Express Adapter (rev 01) > > Is NM being told to go to sleep and wake up properly? If so, you'll see > these messages in the logs: > > NetworkManager: Sleeping... > NetworkManager: Waking up... > > Can you provide some logs from /var/log/messages or /var/log/daemon.log > that show the wake-up sequence? > > Dan > > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
reconnect after sleeping
Hello all, I wrote to this list a few weeks ago explaining a problem I had with an atheros card. I managed to install madwifi and things are much better now. I had to change as well the "channel" of my router from 6 to 10 to make it work. That is solved [?]. The only thing is not working is when the machine goes to sleep and comes back there is no way to make the connection again. I have restarted the network service but it does not help. My machine is an Eee PC 1000HA running Fedora 10. With a card 01:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01) Do you know if there is a way to solve this? Cheers, Manuel <<330.gif>>___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
weird behaviour
Hello everyone, I have got a netbook Eee pc asus 100ha. I installed Fedora 10 but NetworkManager has a weird behavior when connecting to my wireless router. 1. It is very difficult to make the connection, it takes sometimes 45 secs and sometimes it does not connect. 2. Once connected the connection is REALLY SLOW and the browser gets a time out and here comes the weird part: - if a open a tty (ctrl-alt-f2) and use wget, yum, ftp or whatsoever that access the web it works nicely and fast but in gnome everything is bad and slow, even ta terminal using the same programs (e.g. wget) hangs in "resolving host" (a few times gets the page after 30 secs). Please help me, I can send all the extra info an logs that you need. This are the versions I have: NetworkManager-glib-0.7.1-1.fc10.i386 NetworkManager-openvpn-0.7.0.99-1.fc10.i386 NetworkManager-0.7.1-1.fc10.i386 NetworkManager-vpnc-0.7.0.99-1.fc10.i386 NetworkManager-gnome-0.7.1-1.fc10.i386 Cheers, Manuel ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
