Bug 755326

Summary:	sdricoh_cs module not loaded automatically
Product:	[Fedora] Fedora	Reporter:	Robert Foreman <robert.foreman>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	16	CC:	gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-11-24 18:39:01 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Robert Foreman 2011-11-20 17:45:52 UTC

Description of problem:
sdricoh_cs kernel module not loaded for Ricoh Co Ltd MMC/SD Host Controller

Steps to Reproduce:
1. Install Fedora 16 on system with Ricoh Co Ltd MMC/SD Host Controller
2. lsmod | grep ricoh
  
Actual results:
SD slot doesn't function properly until sdricoh_cs module is loaded

Expected results:
Should be loaded automatically

Additional info:
Placed sdricoh_cs.modules in /etc/sysconfig/modules/ with modprobe sdricoh_cs as a workaround.

Comment 1 Josh Boyer 2011-11-22 18:09:05 UTC

Can you provide the output of dmesg before and after you load the module and lspci -vvv from this machine?  The module only supports two device IDs so perhaps you just have one that isn't explicitly listed yet.

Comment 2 Robert Foreman 2011-11-24 15:30:50 UTC

Now I can't reproduce even without the sdricoh_cs module loaded, but I've applied all the recent updates since opening this bug report. It may have been a dbus thing. Before the updates and without loading the sdricoh_cs module I wasn't seeing any dbus messages using dbus-monitor when inserting and SD card. Now I am.

Comment 3 Josh Boyer 2011-11-24 18:39:01 UTC

Hm.  OK.  If you see the issue again, please reopen the bug.