Bug 1133655 - Kernel won't enable PCMCIA slot [NEEDINFO]
Summary: Kernel won't enable PCMCIA slot
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: i686
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-25 17:49 UTC by hawkfeather
Modified: 2014-11-17 13:26 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-11-17 13:26:36 UTC
Type: Bug
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)
Output from requested commands [lspci, lsusb, dmesg] (62.42 KB, text/plain)
2014-08-25 18:50 UTC, hawkfeather
no flags Details
Output from lspci -nnvv, dmesg, and lsusb when running kernel 3.15.10-201.fc20.i686 (65.66 KB, text/plain)
2014-08-31 05:46 UTC, hawkfeather
no flags Details

Description hawkfeather 2014-08-25 17:49:33 UTC
Description of problem:
PCMCIA devices aren't recognized by the OS


Version-Release number of selected component (if applicable):
kernel-3.15.10-200.fc20.i686

How reproducible:
Always

Steps to Reproduce:
1. Boot system
2. Insert PCMCIA device
3. Look for device to activate \ check output of `lspci -vv`

Actual results:
Device isn't recognized - no difference in behavior\output than when there's no device present at all

Expected results:
For the PCMCIA device to activate

Additional info:
No related *.service file or any other type of controlling file that I know of can be found

Comment 1 Josh Boyer 2014-08-25 17:56:17 UTC
Please provide the output of lspci -nnvv, dmesg, and lsusb as plain text attachments

Comment 2 hawkfeather 2014-08-25 18:50:06 UTC
Created attachment 930626 [details]
Output from requested commands [lspci, lsusb, dmesg]

Attached please find the information you requested. Hope it's useful, and thanx for any help you can provide.

Comment 3 hawkfeather 2014-08-31 05:46:37 UTC
Created attachment 933047 [details]
Output from lspci -nnvv, dmesg, and lsusb when running kernel 3.15.10-201.fc20.i686

Comment 4 hawkfeather 2014-08-31 05:52:57 UTC
I'm checking in again to let you know that the new build of the Fedora kernel 3.15.10 [3.15.10-201.fc20.i686] has the same issue as the previous build, which is that the PCMCIA slot is disabled. I'm attaching a file containing the new output from lspci -nnvv, dmesg, and lsusb.

Comment 5 Justin M. Forbes 2014-11-13 15:58:00 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.17.2-200.fc20.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21.

If you experience different issues, please open a new bug report for those.

Comment 6 hawkfeather 2014-11-17 05:45:17 UTC
(In reply to Justin M. Forbes from comment #5)
> *********** MASS BUG UPDATE **************
> 
> We apologize for the inconvenience.  There is a large number of bugs to go
> through and several of them have gone stale.  Due to this, we are doing a
> mass bug update across all of the Fedora 20 kernel bugs.
> 
> Fedora 20 has now been rebased to 3.17.2-200.fc20.  Please test this kernel
> update (or newer) and let us know if you issue has been resolved or if it is
> still present with the newer kernel.
> 
> If you have moved on to Fedora 21, and are still experiencing this issue,
> please change the version to Fedora 21.
> 
> If you experience different issues, please open a new bug report for those.

I haven't tried this new kernel release yet, but I'm happy to say that this issue has been resolved by the last several Fedora kernel releases.


Note You need to log in before you can comment on or make changes to this bug.