Bug 5519

Summary:	Texas Instruments internal SD card reader not working
Product:	Mageia	Reporter:	Andrew <theamazingchiepoo>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	Normal	CC:	davidwhodgins, gruescubogdan, mageia, marja11, sysadmin-bugs, thierry.vignaud, tmb
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	syslog output after inserting SD card syslog output after inserting SD card

Description Andrew 2012-04-20 20:48:39 CEST

Description of problem:

Memory cards inserted into the Texas Instruments (TI) 6-in-1 Internal Card Reader for Gateway MX6448 (http://support.gateway.com/s/mobile/q106/bladek8f/1013912rsp2.shtml) are not accessible. Drive is never mounted or recognized. "Browse and Configure Hardware" in Mageia Control Center acknowledges it as "5-in-1 Multimedia Card Reader" using module "tifm_7xx1"

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

kernel-desktop-3.3.1-2.mga2 x86_64

How reproducible:

Always

Steps to Reproduce:
1. Insert an SD into card reader slot

Actual result(s):
Nothing happens / card not acknowledged

Expected result(s):
Device should mount

Comment 1 Dave Hodgins 2012-04-21 02:59:14 CEST

If you open a terminal and as root run "tail -f /var/log/syslog",
then insert an sd card, is there any output added to the output
of syslog?

If there is, can you copy/paste those lines into a file, and then
attach that file to this bug report?

CC: (none) => davidwhodgins

Comment 2 Bogdan Gruescu 2012-04-21 06:44:04 CEST

I have had this issue in the past, the fix was to install the package 'sg3_utils'. (after installation, perhaps a reboot is necessary; and if it still doesn't work, try to boot with the SD card inserted).
I am almost sure that even now, this package doesn't get installed by default.

CC: (none) => gruescubogdan

Manuel Hiebel 2012-04-21 10:59:39 CEST

CC: (none) => thierry.vignaud
Component: Release (media or process) => RPM Packages
Source RPM: (none) => ldetect

Comment 3 Thierry Vignaud 2012-04-21 11:05:48 CEST

That has nothing to do with ldetect

Source RPM: ldetect => (none)

Comment 4 Andrew 2012-04-21 18:24:30 CEST

Created attachment 2061 [details]
syslog output after inserting SD card

Strange... drive mounted while in terminal but still produced errors.

Thierry Vignaud 2012-04-21 23:02:31 CEST

CC: (none) => mageia

Thierry Vignaud 2012-04-21 23:02:37 CEST

CC: (none) => tmb

Comment 5 Colin Guthrie 2012-04-22 13:13:43 CEST

You can ignore the cryptab errors.

So did the drive mount OK and was usable?

My own SSD drive seems a bit special and has never really worked well, so I can't test easily.

Comment 6 Andrew 2012-04-24 09:37:16 CEST

Yeah, seems to be fine now. Perhaps it was only during 1st use of the card slot (perhaps it installed something behind the scenes and needed to be rebooted)?

Comment 7 Colin Guthrie 2012-04-24 12:37:23 CEST

I don't think anything extra would need to be installed, but perhaps a new kernel or something has fixed it. I'll mark as fixed for now, but please reopen and try and give more details if/when you have them.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 8 Andrew 2012-05-18 07:37:28 CEST

Created attachment 2338 [details]
syslog output after inserting SD card

Bug revived after clean installing and updating Release Candidate. Resolves itself permanently both after 1st reboot and if the card is ejected and reinserted several times.

Comment 9 Andrew 2012-05-18 07:40:09 CEST

See new attachment. Reopening because bug revived after installing Release Candidate. Seems to occur on clean installations. Tends to fix itself upon rebooting after the card has been inserted at least once or during the same session if the card is inserted and removed enough times.

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 10 Marja Van Waes 2012-05-26 13:08:11 CEST

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 11 Marja Van Waes 2012-08-04 14:12:05 CEST

2 months later, no reply, closing as old.

Please reopen when needed and tell for which version(s) of Mageia this bug is still valid.

If it is valid for both cauldron and Mageia 2, then please put MGA2TOO on the whiteboard and let version remain set to cauldron

Status: REOPENED => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD

Comment 12 Andrew 2013-02-26 09:32:31 CET

Bug no longer present.

Resolution: OLD => FIXED