From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: usb storage not a block device ???
Date: Sat, 21 Jan 2006 08:50:26 +0000 [thread overview]
Message-ID: <200601211150.27108.arvidjaar@mail.ru> (raw)
In-Reply-To: <587eff0d932a21c31376b5be9f94c3dc@137.204.189.222>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Saturday 21 January 2006 11:14, G.ridolfi wrote:
> Data: 20/01/06 19:55 Moshe Yudkowsky
>
> > Giovanni Ridolfi
> >
> > > I cannot find any << SUBSYSTEM="block" >> in what the kernel reads
> > >
> > > :-(
> > >
> > > # udevinfo -a -p
> >
> > I suggest you "modprobe usb_storage" and then see if you get "block."
>
> # modprobe usb_storage
> # dmesg
> Initializing USB Mass Storage driver...
> usbcore: registered new driver usb-storage
> USB Mass Storage support registered.
> usb 4-1: new high speed USB device using ehci_hcd and address 3
> scsi0 : SCSI emulation for USB Mass Storage devices
> usb-storage: device found at 3
> usb-storage: waiting for device to settle before scanning
>
And now you have to load sd_mod that is missing in lsmod output you sent
earlier. Once upon a time it was done by hotplug. I do not know if Gentoo is
still using hotplug or converted hotplug rules to udev. In the latter case we
(Mandriva community) found a bug that SCSI subsystem requires wait_for_sysfs
otherwise it cannot probe device type and does not load proper module. I,e,
from current udev rules here:
# disks & magneto-optical disk:
ACTION="add", SUBSYSTEM="scsi", WAIT_FOR_SYSFS="type", SYSFS{type}="[07]",
\
RUN+="/sbin/modprobe sd_mod"
> However /dev/muvo is created but...
> #ls -l
> crw-rw-r-- 1 root root 189, 387 2006-01-21 08:49 /dev/muvoTXFM
>
> Still is not a block device.
[...]
> # udevinfo -a -p /sys/devices/pci0001\:10/0001\:10\:1b.2/usb4/4-1/4-1\:1.0/
>
Irrelevant. This is created by usbhid. If you want to rename (that I strongly
NOT recommend) or give alias to your USB stick your old rule should work, use
SYMLINK
SYSFS{product}="MuVo TX FM", SYMLINK+="muvoTXFM", KERNEL="sd*"
BTW with your all rule you will never see /dev/sda at all because you change
the name from default to custom.
Also udev already creates persistent (are they really BTW?) rules for you:
{pts/1}% LC_ALL=C ll /dev/disk/by-id
total 0
lrwxrwxrwx 1 root root 9 Jan 21 11:12 ata-IC25N020ATDA04-0_63A63GY1081
- -> ../../hda
lrwxrwxrwx 1 root root 10 Jan 21 11:12 ata-IC25N020ATDA04-0_63A63GY1081-part1
- -> ../../hda1
lrwxrwxrwx 1 root root 10 Jan 21 11:12 ata-IC25N020ATDA04-0_63A63GY1081-part2
- -> ../../hda2
lrwxrwxrwx 1 root root 9 Jan 21 11:12 usb-USB_128MB_241F41AFDD0D006D
- -> ../../sda
lrwxrwxrwx 1 root root 10 Jan 21 11:12 usb-USB_128MB_241F41AFDD0D006D-part1
- -> ../../sda1
may be you just can use them?
- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFD0fXTR6LMutpd94wRAqm/AJ0QzMrPI6KzHQbWvZN4Kc2BDGiBVACfUoIc
C5I8UYxZe1SwfMgBBLYdZwo=MvTc
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2006-01-21 8:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 9:59 usb storage not a block device ??? G.ridolfi
2006-01-19 12:59 ` Alexander E. Patrakov
2006-01-19 18:36 ` Moshe Yudkowsky
2006-01-20 8:55 ` G.ridolfi
2006-01-20 10:04 ` Alexander E. Patrakov
2006-01-20 11:46 ` Kay Sievers
2006-01-20 13:23 ` G.ridolfi
2006-01-20 18:55 ` Moshe Yudkowsky
2006-01-21 8:14 ` G.ridolfi
2006-01-21 8:50 ` Andrey Borzenkov [this message]
2006-01-21 10:15 ` G.ridolfi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200601211150.27108.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).