Hi,

I just followed Joost Kremers' suggestion of switching to udev, so I
installed a 2.6.7 kernel, read the udev doc, and I'm impressed indeed.

So far I fiddled a bit with udev rules, and my USB printer and USB memory
stick work like a charm.

But then, I tried to install a multi-card reader I had some troubles with a
few weeks ago, thinking what with the new kernel, I could maybe give it
another go.

The card reader in itself is an internal one with three slots: one USB, one
for Compact Flash cards (from my Nikon Coolpix camera for example), and a
third one I don't know and don't seem to have a use for.

After installing it, I took a look in /dev and saw four new entries:

sda sdb sdc sdd

When plugging in the USB memory stick, there's an additional

sde sde1

and I can mount the stick OK.

So far I fiddled around enough with udev to get reasonably familiar with it.
And also to notice a strange behaviour from my Flash Card.

When I plug it in, nothing happens. No additional entry to /dev.

BUT... when I boot the computer with the card in the reader, I get the
following entries in /dev:

sda sdb sdb1 sdc sdd

So I tried to mount it manually:

mount -t vfat /dev/sdb1 /mnt/flashcard

.... and it worked!

Except that when I pulled it out from the slot, /dev/sdb1 was still there
and didn't disappear as it should.

Any guess what's wrong here?

Niki Kovacs
--
Whereof one cannot speak, thereof one frequently goes ranting on and on at
ball-breaking length. (Ludwig Wittgenstein, Tractatus Logico-Philosophicus,
first draft)

Kiki Novak <mickey@mouse.com> wrote:
> The card reader in itself is an internal one with three slots: one USB,
> one for Compact Flash cards (from my Nikon Coolpix camera for example),
> and a third one I don't know and don't seem to have a use for.
>
> After installing it, I took a look in /dev and saw four new entries:
>
> sda sdb sdc sdd

> And also to notice a strange behaviour from my Flash Card.
>
> When I plug it in, nothing happens. No additional entry to /dev.
>
> BUT... when I boot the computer with the card in the reader, I get the
> following entries in /dev:
>
> sda sdb sdb1 sdc sdd

Partition tables are read at boot, but can be forced to be reread at other
occasions. Search the net for a script called rescan-scsi-bus.sh

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc2(at)uthyres.com Examples of addresses which go to spammers:
svar@webtelevision.se info@webrider.ru root@localhost

Kiki Novak wrote:
> So far I fiddled around enough with udev to get reasonably familiar with it.
> And also to notice a strange behaviour from my Flash Card.
>
> When I plug it in, nothing happens. No additional entry to /dev.

it could simply be that hotplug doesn't recognise the device. you may need
to add an entry for it in one of the mapfiles, but please don't ask me for
details, as i don't know much about it. :-(

--
Joost Kremers joostkremers@yahoo.com
Selbst in die Unterwelt dringt durch Spalten Licht
EN:SiS(9)

On 2004-10-25, Kiki Novak <mickey@mouse.com> wrote:
<snip Compact Flash anomaly>

Sounds flaky to me... what does /var/log/messages give in both cases?

Well... I just tried my rig again and /dev/sda1 didn't show up, even though
I unplugged and replugged the reader. So I tried mounting /dev/sda, which
gave the usual error messages, *but*, check this out:


[root@ansible /home/wtallman]# list /dev/sd*
brw-rw---- 1 root disk 8, 0 2004-10-25 19:00 /dev/sda
[root@ansible /home/wtallman]# mount -t vfat /dev/sda1 /mnt/reader
mount: special device /dev/sda1 does not exist

Okay, no sda1. Let's check to see what's what.

[root@ansible /home/wtallman]# lsusb
Bus 004 Device 004: ID 05e3:0700 Genesys Logic, Inc. SIIG US2256
CompactFlash Card Reader
Bus 004 Device 002: ID 058f:9254 Alcor Micro Corp. Hub
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 002: ID 0409:0058 NEC Corp. HighSpeed Hub
Bus 001 Device 001: ID 0000:0000

The reader is there, of course. So what happens when I try to mount
sda?

[root@ansible /home/wtallman]# mount -t vfat /dev/sda /mnt/reader
mount: wrong fs type, bad option, bad superblock on /dev/sda,
or too many mounted file systems

As expected, but what does /var/log/messages say?

[root@ansible /home/wtallman]# tail /var/log/messages
Oct 25 19:00:49 ansible kernel: Attached scsi generic sg0 at scsi1, channel
0, id 0, lun 0, type 0
Oct 25 19:00:50 ansible udev[3218]: creating device node '/dev/sda'
Oct 25 19:00:50 ansible udev[3220]: creating device node '/dev/sg0'
Oct 25 19:02:09 ansible kernel: SCSI device sda: 250369 512-byte hdwr
sectors (128 MB)
Oct 25 19:02:09 ansible kernel: sda: assuming Write Enabled
Oct 25 19:02:09 ansible kernel: SCSI device sda: 250369 512-byte hdwr
sectors (128 MB)
Oct 25 19:02:09 ansible kernel: sda: assuming Write Enabled
Oct 25 19:02:09 ansible kernel: sda: sda1
Oct 25 19:02:09 ansible kernel: VFS: Can't find a valid FAT filesystem on
dev sda.
Oct 25 19:02:09 ansible udev[3248]: creating device node '/dev/sda1'
[root@ansible /mnt/reader]#

Aha! Now it's been created!

[root@ansible /home/wtallman]# mount -t vfat /dev/sda1 /mnt/reader
[root@ansible /home/wtallman]# cd /mnt/reader
[root@ansible /mnt/reader]# l
dcim

Dcim is the Compact Flash partition, which should mean that the
device is now present...

[root@ansible /mnt/reader]# list /dev/sd*
brw-rw---- 1 root disk 8, 0 2004-10-25 19:00 /dev/sda
brw-rw---- 1 root disk 8, 1 2004-10-25 19:02 /dev/sda1
[root@ansible /mnt/reader]#

Outstanding!

Anyway, that's my latest experience. HTH
--
Email is wtallman at olypen dot com