Bug 31692 - Built in Realtek card reader in Asus laptop doesn't work
Summary: Built in Realtek card reader in Asus laptop doesn't work
Status: RESOLVED OBSOLETE
Alias: None
Product: Drivers
Classification: Unclassified
Component: MMC/SD (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_mmc-sd
URL: https://bugs.launchpad.net/ubuntu/+so...
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-22 18:41 UTC by njin
Modified: 2013-12-23 11:47 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.35 - 2.6.38
Subsystem:
Regression: No
Bisected commit-id:

Attachments
AcpiTables (352.77 KB, text/plain)
2011-03-22 18:41 UTC, njin 		Details
BootDmesg (96.50 KB, text/plain)
2011-03-22 18:42 UTC, njin 		Details
CurrentDmesg (3.56 KB, text/plain)
2011-03-22 18:42 UTC, njin 		Details
Lspci (21.42 KB, text/plain)
2011-03-22 18:43 UTC, njin 		Details
UdevLog (330.05 KB, text/plain)
2011-03-22 18:44 UTC, njin 		Details
Add an attachment (proposed patch, testcase, etc.)

Description njin 2011-03-22 18:41:39 UTC 
Created attachment 51622 [details]
AcpiTables

I own Asus G73JW-A1 with Windows 7 and Ubuntu 10.10. My notebook has an 8 in 1 Realtek slot card reader, which works perfectly in Windows but not in Ubuntu.
These are identifier and vendor and device id: 05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device [10ec:5209] (rev 01)
10ec:5209.
I have tried make it work adding usb-storage, tifm_core, tifm_mode and pciehp pciehp-force=1 to /etc/modules file but nothing has changed.
Reading the difference between dmesg output with an sd card inside or not, this hotplug issue compares:
[ 56.991564] pci 0000:05:00.0: no hotplug settings from platform.
Comment 1 njin 2011-03-22 18:42:24 UTC 
Created attachment 51632 [details]
BootDmesg
Comment 2 njin 2011-03-22 18:42:58 UTC 
Created attachment 51642 [details]
CurrentDmesg
Comment 3 njin 2011-03-22 18:43:26 UTC 
Created attachment 51652 [details]
Lspci
Comment 4 njin 2011-03-22 18:44:05 UTC 
Created attachment 51662 [details]
UdevLog
Note You need to log in before you can comment on or make changes to this bug.