4-in1 Card Reader, HAL, dbus, and/or udev

marnold · 07-13-2007, 03:37 PM

The last remaining thing that I need to get working in Slack 12 is my SanDisk 8-in-1 card reader. Here is what is happening so far:

1) On boot up the reader is found. The extra LUNs are scanned for and all four are found.
2) If I put a Compact Flash card in the reader, KDE pops a box up asking me what to do with it. All works as it should.
3) If I put a Secure Digital card in the reader, I get this in /var/log/messages (as it should):

Code:

Jul 13 15:14:09 skyron kernel: sd 0:0:0:2: [sdc] 3970048 512-byte hardware sectors (2033 MB)
Jul 13 15:14:09 skyron kernel: sd 0:0:0:2: [sdc] Write Protect is off
Jul 13 15:14:09 skyron kernel: sd 0:0:0:2: [sdc] 3970048 512-byte hardware sectors (2033 MB)
Jul 13 15:14:09 skyron kernel: sd 0:0:0:2: [sdc] Write Protect is off
Jul 13 15:14:09 skyron kernel:  sdc: sdc1

The problem is that no box ever pops up in KDE asking me what to do with it. I don't know where the problem is. I've been doing a bunch of Googling and crawling around /etc, but I can't seem to figure it out. Is the issue with HAL? dbus? udev? Obviously a rule needs to be written, but a rule for what and where is the problem.

Thanks in advance,
Matt

onebuck · 07-14-2007, 08:29 AM

Hi,

Check out the Writing udev rules in the New 'Slackware-Links' Wiki. This should help you in writing the rules for priority.

marnold · 07-14-2007, 09:35 AM

Quote:

Originally Posted by onebuck

Check out the Writing udev rules in the New 'Slackware-Links' Wiki. This should help you in writing the rules for priority.

I'm familiar with udev rules, but is this really a udev issue? When I insert a Compact Flash card, this appears in /var/log/messages:

Code:

Jul 14 09:18:27 skyron kernel: sd 0:0:0:0: [sda] 1001952 512-byte hardware sectors (513 MB)
Jul 14 09:18:27 skyron kernel: sd 0:0:0:0: [sda] Write Protect is off
Jul 14 09:18:27 skyron kernel: sd 0:0:0:0: [sda] 1001952 512-byte hardware sectors (513 MB)
Jul 14 09:18:27 skyron kernel: sd 0:0:0:0: [sda] Write Protect is off
Jul 14 09:18:27 skyron kernel:  sda: sda1
Jul 14 09:18:31 skyron hald: mounted /dev/sda1 on behalf of uid 1000

Note that it's the same stuff as in my first message except for the last line. HAL automatically mounts the Compact Flash, but does nothing with the Secure Digital. I see in 50-udev.rules were the sd* devices are created and removable media are put in the plugdev group. I've got that so far. It creates /dev/sdc and /dev/sdc1 which I need to access the Secure Digital card, but there it ends. 90-hal.rules seems to pass everything off to HAL. Is HAL dropping the ball then?

marnold · 07-14-2007, 09:51 AM

For the time being, I have added this line to my fstab:

Code:

/dev/sdc1        /media/sd        vfat        noauto,user      0   0

At least now I can mount it manually until I can figure out how to make HAL deal with it.

*Update* Actually, now that I added it to my fstab, HAL automatically mounts Secure Digital cards to /media/sd. Not exactly the same thing, but it works.

randomsel · 07-14-2007, 11:02 AM

right, and it shows on your desktop (if you activated that option). Same happens with remote smbfs in the fstab (I'm liking HAL at the moment

)

marnold · 07-14-2007, 11:13 AM

Quote:

Originally Posted by randomsel

right, and it shows on your desktop (if you activated that option). Same happens with remote smbfs in the fstab (I'm liking HAL at the moment

)

Well, I've gotten the problem narrowed down further. The problem only happens with my 2G card. I tried it with a 1G and a 256M card and HAL/udev/etc. work fine. I'm not sure if it's my reader, the card, or something that HAL/dbus/etc. doesn't like. My guess is that the problem is that my reader was made long before there was such a thing as 2G cards. I hope this won't cause issues otherwise . . .

*Update* Well, according to SanDisk technical support, my reader should work just fine with a 2G card. The reader is in fact the SanDisk Imagemate 8-in-1, model SDDR-88. The card itself is SanDisk as well.