10:20 a.m.
I have an Apacer MegaSteno USB 2.0 7-in-1 card reader. One of the neat
things about this is that it claims to support Linux. It tells you what
minimum kernel version you need, and how to modify the kernel config to
allow the kernel to see all three slots on it.
The device worked well under FC1.
While testing FC4t1, I have also discovered the joy of autodetection of
USB drives, USB card readers, and cards plugged into USB card readers,
plus the automounting of all of the above. Awesome!
I have discovered one problem, though. Although automounting of USB
drives works well, inserting a MMC, SD, or CF card into the abovementioned
card reader automounts the first time, but not on subsequent insertions.
I also discovered that after this occurs, nothing else will automount,
either.
When I insert an MMC, SD, or CF card into the reader, gnome-volume-manager
starts using up 100% CPU, so I have to kill it. If I re-run it from the
commandline, automounting starts working again (for other devices) until I
insert an MMC, SD, or CF card again.
If I remove the card reader, insert the card into the card reader, then
plug it back into the USB port, the behaviour is the same.
Regards, Msquared...
10:36 a.m.
Msquared ha scritto:
When I insert an MMC, SD, or CF card into the reader,
gnome-volume-manager
starts using up 100% CPU, so I have to kill it. If I re-run it from the
commandline, automounting starts working again (for other devices) until I
insert an MMC, SD, or CF card again.
If I remove the card reader, insert the card into the card reader, then
plug it back into the USB port, the behaviour is the same.
Regards, Msquared...
Have tried the last version of gnome-volume-control in rawride?
10:45 a.m.
On Apr 1, 2005 11:20 AM, Msquared <sub1.fedoralist(a)msquared.id.au> wrote:
If I remove the card reader, insert the card into the card reader,
then
plug it back into the USB port, the behaviour is the same.
which packages versions of hal dbus gamin and gnome-volume-manager do you have?
rpm -q hal gnome-volume-manager dbus gamin
possibly a gnome-volume-manger specific problem or a deeper problem with hal.
Do the mountpoints and fstab entries get created correctly? If the
mountpoints and fstab entries get created but automounting isnt
working.. then its a gnome-volume-manager problem. when you encounter
the problem look at /etc/fstab and at the mountpoint /media directory
to see if entries for the inserted cards are created. You can do some
highlevel troubleshooting of hal without gnome-volume-manager running
by logging out of gnome and logging into a virtual console (ALT+CTL+F1
for example) commandline interface. On card insertion even at a
virtual console, if hal is working correctly you should see fstab
entries being created and mountpoints under /media/ being created
with every insertion of the media. And conversly the fstab entry and
mountpoints being removed everytime the media is pulled out. If either
the fstab entry or the mountpoint fails to be created on multiple
insertions thats a good indication the problem is with hal (or
deeper).
You could also configure gnome to not automount those devices and test
repeated re-insertion and manual mounting. On insertion.. if hal is
working.. and gamin is working... the device will show up in the
nautilus Computer window. From there you can manually mount the
device. Try to see if the problem only exists if automounting in gnome
is enabled.
-jef
12:09 p.m.
Jeff Spaleta wrote:
On Apr 1, 2005 11:20 AM, Msquared
<sub1.fedoralist(a)msquared.id.au> wrote:
>If I remove the card reader, insert the card into the card reader, then
>plug it back into the USB port, the behaviour is the same.
>
>
which packages versions of hal dbus gamin and gnome-volume-manager do you have?
rpm -q hal gnome-volume-manager dbus gamin
possibly a gnome-volume-manger specific problem or a deeper problem with hal.
Do the mountpoints and fstab entries get created correctly? If the
mountpoints and fstab entries get created but automounting isnt
working.. then its a gnome-volume-manager problem. when you encounter
the problem look at /etc/fstab and at the mountpoint /media directory
to see if entries for the inserted cards are created. You can do some
highlevel troubleshooting of hal without gnome-volume-manager running
by logging out of gnome and logging into a virtual console (ALT+CTL+F1
for example) commandline interface. On card insertion even at a
virtual console, if hal is working correctly you should see fstab
entries being created and mountpoints under /media/ being created
with every insertion of the media. And conversly the fstab entry and
mountpoints being removed everytime the media is pulled out. If either
the fstab entry or the mountpoint fails to be created on multiple
insertions thats a good indication the problem is with hal (or
deeper).
You could also configure gnome to not automount those devices and test
repeated re-insertion and manual mounting. On insertion.. if hal is
working.. and gamin is working... the device will show up in the
nautilus Computer window. From there you can manually mount the
device. Try to see if the problem only exists if automounting in gnome
is enabled.
-jef
I have the same problem with FC3 try to plug your cardreader without any
card and plug one after its detected in dmesg.
http://www.redhat.com/archives/fedora-devel-list/2005-March/msg00321.html
https://bugzilla.redhat.com/beta/show_bug.cgi?id=150175
12:39 p.m.
On Fri, Apr 01, 2005 at 06:36:18PM +0200, Cimmo wrote:
Have tried the last version of gnome-volume-control in rawride?
I have gnome-volume-manager-1.1.3-3 if that's what you are referring it.
Is the rawhide the one I get if I use yum with the development repository
enabled?
>Have tried the last version of gnome-volume-control in rawride?
>
rawhide :-P
Hehe. :o) Mind you, if the packages therein are undergoing much change
and are susceptible to many problems, someone might go aheand and call it
a rawride anyway... ;-)
On Fri, Apr 01, 2005 at 11:45:25AM -0500, Jeff Spaleta wrote:
rpm -q hal gnome-volume-manager dbus gamin
[root@mnemonic ~]# rpm -q hal gnome-volume-manager dbus gamin
hal-0.5.0.cvs20050322b-1
gnome-volume-manager-1.1.3-3
dbus-0.31-2
gamin-0.0.25-4
I'm going to run yum to update them, though. Looks like it wants to
update dbus and gamin.
Woo, just looked at the info on gamin. I hope it's better than fam. I
hate it when asdfi have to killall fam to umount a CD or memory card under
FC1.
Do the mountpoints and fstab entries get created correctly?
Yes. The problem only occurs if automount is turned on inside Removable
Drives and Media Preferences, and only (so far) for cards inserted into
the card reader. USB thumb drives and CDs work fine.
Interesting to note that although mentally I think of the card in the card
reader as removable media, it is automounted when "Mount removable drives
when hot-plugged" is on but "Mount removable media when inserted" is off,
indicating that gnome-volume-manager treats the card as a hot-plug
drive... Something I'll just have to get usd to, I guess. :o)
You could also configure gnome to not automount those devices and
test
repeated re-insertion and manual mounting.
Manual mounting (via mount command, mount panel object, nautilus, etc) all
work fine when no automounting via gnome-volume-manager happening.
the device will show up in the nautilus Computer window.
Woo, I didn't know that happened. Very nice!
From there you can manually mount the device. Try to see if the
problem
only exists if automounting in gnome is enabled.
That is indeed the case.
Regards, Msquared...
1 p.m.
On Apr 1, 2005 1:39 PM, Msquared <sub1.fedoralist(a)msquared.id.au> wrote:
That is indeed the case.
Well it definitely sounds like a gnome-volume-manager specific problem.
I don't have any of these multicard reader object so I'm probably not
going to be much help to you beyond this point. Probably worth filing
with as much specific information as possible.. especially since
everything seems to work except when automounting is active. Make sure
you note in the report the problem only occurs when automount is
active, so far I havent seen any bugzilla ticket that actually narrows
down the problem to just the automounting active case. This could be
a dbus/gnome-volume-manager interaction problem. I'm not sure how to
go about diagnosing that, there is probably someone to get the
messagebus service to emit copious logs for you to capture and
attach.. but i don't know how to do it yet.
you can try updating dbus, reboot just to make sure all the services
are restarted and see if you can reproduce the problem. Latest rawhide
dbus is dbus-0.31-4, but I'm not seeing anything in the package
changelog that would suggest -4 has a fixed applied for anything
compared to -2 so i dont think this is going to be fix.
Whether the situation is a 'mount removable drives' versus 'mount
removable media when inserted' is probably worth filing as a seperate
issue and worth discussion with the developer of gnome-volume-manager
or hal. I THINK g-v-m just gets told whether its a removable media
versus a removable drive and tries to act accordingly. I think hal is
actually the software that tries to make the distinction and then
communicates that distinction via dbus to g-v-m... i could be totally
wrong about that. If its unitutive however its still worth bringing up
as a bugzilla ticket even if the developers end up disagreeing with
you.
-jef
5 a.m.
On Fri, Apr 01, 2005 at 02:00:40PM -0500, Jeff Spaleta wrote:
you can try updating dbus, reboot just to make sure all the services
are restarted and see if you can reproduce the problem.
Tried that, no difference.
Whether the situation is a 'mount removable drives' versus
'mount
removable media when inserted' is probably worth filing as a seperate
issue and worth discussion with the developer of gnome-volume-manager or
hal.
Filed against gvm:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=153264
I figure work from the top down. It looks to me like an issue with gvm,
but if it's really with hal them someone more knowledgeable than myself
can reassign it.
Regards, Msquared...
4:03 a.m.
On Mon, Apr 04, 2005 at 06:00:54PM +0800, Msquared wrote:
> Whether the situation is a 'mount removable drives'
versus 'mount
> removable media when inserted' is probably worth filing as a seperate
> issue and worth discussion with the developer of gnome-volume-manager
> or hal.
Filed against gvm:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=153264
That has been updated to "not a bug". :o) On the other hand, apparently
they're changing things to remove the distinction in the user interface
anyway...
Regards, Msquared...
12:53 p.m.
On Fri, Apr 01, 2005 at 08:09:46PM +0200, dragoran wrote:
I have the same problem with FC3 try to plug your cardreader without
any
card and plug one after its detected in dmesg.
http://www.redhat.com/archives/fedora-devel-list/2005-March/msg00321.html
https://bugzilla.redhat.com/beta/show_bug.cgi?id=150175
My problem is slightly different, because the 100%CPU occurs no matter how
I perform the insertion (card into reader then reader into USB, or reader
into USB then card into reader).
On Fri, Apr 01, 2005 at 08:22:00PM +0200, nodata wrote:
That is exactly the same as mine. I also had to kill -9
gnome-volume-manager to stop it.
I notice a comment from John (J5) Palmieri about 1.3.1, but I can only see
1.1.3. Anyone kmow where 1.3.1 can be found?
Regards, Msquared...
2:27 p.m.
I notice a comment from John (J5) Palmieri about 1.3.1, but I can
only see
1.1.3. Anyone kmow where 1.3.1 can be found?
Regards, Msquared...
http://download.fedora.redhat.com/pub/fedora/linux/core/development/i386/...
2:38 p.m.
On Fri, 2005-04-01 at 22:27 +0200, nodata wrote:
> I notice a comment from John (J5) Palmieri about 1.3.1, but I
can only see
> 1.1.3. Anyone kmow where 1.3.1 can be found?
>
> Regards, Msquared...
http://download.fedora.redhat.com/pub/fedora/linux/core/development/i386/...
Well, I have updated my version with this RPM and the app still spikes
when I insert a card. I have updated the ticket: 151960 on this issue.
Sean
6986
days inactive
6990
days old
13 comments
6 participants
participants (6)
-
Cimmo -
dragoran -
Jef Spaleta -
Msquared -
nodata -
Sean Bruno