Michael Klinosky wrote:
> Mikkel:
>> After thinking about this, (and sleeping on it... :-) I am leaning
>> towards a udev problem. Do you have any local rules? Anything
>> besides the standard udev rules? Because it looks like your reader
>> is matching more then one rule, and I would think that if it is a
>> problem in the standard rules, more people would be running into it...
>
> I know nothing of this subject. So, if you're asking if I modified a
> rule list - definitely not.
>
Modified, or added a local rule set. (Or had an extra rule set
left from an upgrade...) For example, I have a 10-gpsd.rules that I
added to take care of hotplugging my GPS.
> I searched the linux websites to learn about it (tldp and LQ); I found
> some info (but didn't read it yet). Here is the pertinent section (I
> think) of my /etc/udev/rules.d/50-udev.rules:
>
> # usb devices
> KERNEL=="usb/dabusb*", MODE="0660"
> KERNEL=="usb/mdc800*", MODE="0660"
> KERNEL=="usb/rio500", MODE="0660"
>
These rules just set permissions. There are other rules as well.
# Persistent block device stuff:
KERNEL=="sd*[!0-9]|sr*", ENV{ID_SERIAL}=="",
IMPORT{program}="/lib/udev/usb_id -x"
And all the SCSI device rules as well. Because USB storage devices
are handled as SCSI devices.
What may help is to get more information from udev. Try something
like this, as root:
udevcontrol log_priority=debug
[plug in reader]
[wait for partitions to be mounted]
[unmount partitions]
[unplug reader]
udevcontrol log_priority=err
Then post the logs for this. From there, we will hopefully have
enough information to post a good bug report.
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
