Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 141706

Summary: pcmcia doesn't start up
Product: [Fedora] Fedora Reporter: S. Kim Ebert <the_s_dude>
Component: pcmcia-csAssignee: Dave Jones <davej>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 2CC: notting, pfrields
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:07:29 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 S. Kim Ebert 2004-12-03 00:43:31 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET 
CLR 1.1.4322)

Description of problem:
After installing FC2 onto my Toshiba laptop, I cannot use my network 
functions.

I installed FC2 using NSF server.

pcmcia doesn't start.
PCMCIA Reports: no ports.

crdctrl doesn't work.

I'm assuming that my network card doesn't work because PCMCIA doesn't 
start up.

I didn't find this bug looking through the database, but I assume I 
just misunderstood the other pcmcia bugs, or missed it.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Start computer
2.
3.
    

Actual Results:  Network doesn't start.
PCMCIA doesn't start.
crdcntl doesn't work.

Expected Results:  Network, pcmcia, crdcntl all work.

Additional info:

Comment 1 S. Kim Ebert 2004-12-04 00:26:42 UTC

*** This bug has been marked as a duplicate of 111017 ***

Comment 2 Red Hat Bugzilla 2006-02-21 19:07:29 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.