You are not logged in.

#1 2011-01-13 17:00:34

s8dtvt
Member
From: Vietnam
Registered: 2011-01-13
Posts: 15
Website

[SOVLED]-Cannot reconnect to network after suspend to ram

Hi everyone, I'm new in Arch. I just install minimal KDE system with wicd and kernel 2.6.36. Everything seem to work well until I suspend computer. When I resume, wicd cannot reconnect to wifi network.
I tried to use: "/etc/rc.d/network restart" but it not work and when I try to use wicd, it show: "Unable get IP".
I also google it but not found any solution.
Please help,
Thanks in advance!
here is my "rc.conf":

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
#   in the hardware clock being left untouched (useful for virtualization)
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.UTF-8"
HARDWARECLOCK="localtime"
TIMEZONE="Asia/Ho_Chi_Minh"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(atl1e pcspkr snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-codec snd-hda-intel soundcore)

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="king-of-dragon"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
# 
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#

#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
#eth0="dhcp"
INTERFACES=(!eth0 !eth1)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
 
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"

# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(@syslog-ng dbus !hal laptop-mode @network @wicd @alsa !netfs crond kdm fam samba)

btw, I also tried to enable and disable ethX in INTERFACE, network in DAEMON but still not effect.
I only connect to network after reboot computer.
Add a question: after hibernate, computer is reboot, not resume when i press power button.
So, I think wicd run well and the problem come from power managerment.

Last edited by s8dtvt (2011-01-14 07:08:03)

Offline

#2 2011-01-13 17:45:40

skunktrader
Member
From: Brisbane, Australia
Registered: 2010-02-14
Posts: 1,538

Re: [SOVLED]-Cannot reconnect to network after suspend to ram

I don't think this will fix your problem, but as far as I know, you should NEVER have both network and wicd daemons running at the same time.

Online

#3 2011-01-13 18:02:43

s8dtvt
Member
From: Vietnam
Registered: 2011-01-13
Posts: 15
Website

Re: [SOVLED]-Cannot reconnect to network after suspend to ram

At first time, I disable network, but it not effect, so I tried enable but still not work. And now I think I will disable it again as wiki.
Thanks.
anyway, I still think this is problem of power managerment.
Here is output of lspci:

[duclong@king-of-dragon ~]$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 09)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 09)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
02:00.0 Ethernet controller: Atheros Communications AR8121/AR8113/AR8114 Gigabit or Fast Ethernet (rev b0)
03:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)

Last edited by s8dtvt (2011-01-13 18:21:10)

Offline

#4 2011-01-13 19:47:05

ANOKNUSA
Member
Registered: 2010-10-22
Posts: 2,141

Re: [SOVLED]-Cannot reconnect to network after suspend to ram

This is also just a guess--it may not help--but you say you just installed Arch for the first time, with KDE.  You don't mention KDE suffering from any problems, yet you have hal disabled in your DAEMONS array.  So are you using the testing version of KDE? If not, hal is required to make everything  work properly.  Otherwise, I don't see any errors in your lspci output.  That's really all I can tell you since, after going to find the link to another thread I saw regarding a similar issue, I found that you were that thread's author.  The forum mods here ask that you not start multiple threads for a single issue, especially when one of those threads is already receiving replies.  All that said, welcome to Arch! smile

Offline

#5 2011-01-13 20:30:43

s8dtvt
Member
From: Vietnam
Registered: 2011-01-13
Posts: 15
Website

Re: [SOVLED]-Cannot reconnect to network after suspend to ram

Oh, well, I seem wrong when think this cause power managerment. I replace wicd by networkmanager + gnome-network-applet, and it was solved.
Anyway, as you said, I created other thread name: "computer reboot instead of resume after suspend to disk" but because I just only want to resume from hibernate, not using reconnect network again as this thread. May be I write not clearly smile)
until now I haven't hibernate correctly, so:
Is that thread opened or continued closing? And should I creat new one or not?
Thanks.

Last edited by s8dtvt (2011-01-14 06:55:15)

Offline

Board footer

Powered by FluxBB