Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 511089

Summary:	pcmcia wireless card is not usable after hibernation
Product:	Red Hat Enterprise Linux 5	Reporter:	Vladimir Benes <vbenes>
Component:	pm-utils	Assignee:	Jaroslav Škarvada <jskarvad>
Status:	CLOSED CANTFIX	QA Contact:	desktop-bugs <desktop-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.4	CC:	cmeadors, jskarvad
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-03-06 09:33:34 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vladimir Benes 2009-07-13 15:37:52 UTC

Description of problem:
I am unable to use pcmcia wireless card after hibernation without plugging it out and in again

Version-Release number of selected component (if applicable):
pm-utils-0.99.3-10
pcmciautils-014-5
kernel-2.6.18-157
rt61-firmware-1.2-5

How reproducible:


Steps to Reproduce:
1.install firmware to pcmcia wifi card
2.connect to wireless network
3.hibernate
4.wake up
  
Actual results:
have to plug it out and in again to be able to use it

Expected results:
automatic connection to previously connected network if in range

Additional info:

Comment 2 RHEL Program Management 2009-11-06 19:21:14 UTC

This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".

Comment 3 Jaroslav Škarvada 2010-12-17 11:17:01 UTC

Still the issue?

Comment 4 Jaroslav Škarvada 2012-03-06 09:33:34 UTC

Closing as cantfix, because there is not enough information about this problem (i.e. the problem could be in kernel, firmware, networkmanager, ...), nor it is verified that the problem still exists (it is possible it was resolved by e.g. previous kernel update).