Red Hat Bugzilla – Bug 193433
Network card (atmel) does not come back up after suspend
Last modified: 2007-11-30 17:11:34 EST
Description of problem:
I have a NIC (PC-Card, Sitecom WL-011, Atmel based). When I suspend my laptop
and bring it back up the network connection is down and doesn't automagically
come back up. My system is FC5 with all updates installed up until May 28.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. boot laptop with atmel_cs card
3. wake up laptop
Network interface is down.
Network interface should come up.
The network interface comes up again after I unplug and replug the card, but it
is rather inconvenient.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
Retested with FC6. If I properly configure the network interface in
/etc/sysconfig, it comes back up. It's not a bug. Adding it to /etc/sysconfig is
something that might be improved though, I will add a seperate bug report for that.