Red Hat Bugzilla – Bug 151861
Internal USB card reader not functioning
Last modified: 2015-01-04 17:17:56 EST
Description of problem:
I have an internal USB 7 in 1 card reader. Under previous kernels (such as
2.6.10-1.1063 and 1.1105), I have managed to get this working by adding into
and then mkinitrd to the kernel, reboot and all worked.
The current kernels (from around 2.6.11) seem to have stopped this device working.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Insert an SD card into the reader
The card should be read
Using hal-0.5.0-cvs200505018-1 & hotplug-2004_09_23-3
Created attachment 112235 [details]
*** Bug 151848 has been marked as a duplicate of this bug. ***
Paul, I need /proc/bus/usb/devices, too, if you please.
Created attachment 112248 [details]
Update to latest mkinitrd (sorry, can't remember the rpm name!) makes no
difference. USB reader recognised but won't load cards.
Created attachment 112353 [details]
dmesg file after latest updates
Update to current kernel (1225_FC4) does not resolve this problem
kernel 1238_FC4 allowed the card in the reader to be mounted once and then would
fail to mount again. 1240_FC4 won't allow the reader to get that far. This is wierd!
Mass update of -test bugs to update version to fc4.
(Please retest on final release, and report results if you have not already done
What information is needed?
[This comment has been added as a mass update for all FC4 kernel bugs.
If you have migrated this bug from an FC3 bug today, ignore this comment.]
Please retest your problem with todays 2.6.12-1.1398_FC4 update.
If your problem involved being unable to boot, or some hardware not being
detected correctly, please make sure your /etc/modprobe.conf is correct *BEFORE*
installing any kernel updates.
If in doubt, you can recreate this file using..
mv /etc/sysconfig/hwconf /etc/sysconfig/hwconf.bak
mv /etc/modprobe.conf /etc/modprobe.conf.bak
Mass update to all FC4 bugs:
An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream
kernel (220.127.116.11). As there were ~3500 changes upstream between this and the
previous kernel, it's possible your bug has been fixed already.
Please retest with this update, and update this bug if necessary.
Retested. No go. However, after unplugging it, switch off, plug back in - it
works fine. Not sure what that means though. Possibly kudzu picking it up again?
Anyway, it's working now, so I'll close the bug.