Red Hat Bugzilla – Bug 502903
am-utils was needed after default network install
Last modified: 2013-03-05 22:58:26 EST
Description of problem:
I used the network install CD to do a clean install of Fedora 11 Preview on an HP pavilion a375c which as a "multi-media card reader". (Memory stick/ MS Pro, etc)
After installation linux inserting a memory stick had no effect. I didn't know how to get the contents of the MS. I though it might be a mount issue, so I installed (yum install) am-utils. Then it worked properly. When I insert the MS, an icon appears on my desktop and I can navigate through the MS filesystem.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Do a clean installation of F11 Preview network install using defaults
2. Insert a memory stick into the card reader
3. Wait for the icon to appear on the desktop
No icon appeared
Icon for MS should have appeared so I could navigate the filesystem on it.
Please pick a meaningful component instead of "0xFFFF" which is a piece of software having absolutely nothing to do with your problem! Reassigning.
(In reply to comment #1)
> Please pick a meaningful component instead of "0xFFFF" which is a piece of
> software having absolutely nothing to do with your problem! Reassigning.
Yes, I apologize for that. Though I didn't pick 0xFFFF. I didn't pick anything as I have no idea whatsoever which component is responsible. Should am-utils have been selected for installation automatically? Which component decides that? When I asked about it in the fedora emai list, I was told am-utils shouldn't be required and that I should open a bug... this is it. I reported what I know.
Feel free to close the bug as "insufficient data provided". My feelings won't be hurt. :-)
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
Yes, Fedora 11 wasn't an option when I reported the bug. I found it after installing the Preview release a couple of weeks ago.
I did a clean install of Fedora 11 today and did not have this problem, so I recommend this bug be closed.