* Re: usb storage not a block device ???
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
` (8 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Alexander E. Patrakov @ 2006-01-19 12:59 UTC (permalink / raw)
To: linux-hotplug
G.ridolfi wrote:
>Hello everybody
>
>I' running Debian GNU/Linux unstable
>
>udev 0.080-1, linux-image-2.6.15-2
>
>My rule for the mp3 player and usb storage
>Creative MuVo TXFM _partially_ fails in
>creating the device.
>Udev creates a "c" device but not a *block* device .
>
>
Sorry, I don't completely understand. Please provide the output of: ls
-l /dev/what-udev-created.
>a) "sd*" devices in /dev/ directory are missing
>b) udevinfo -a -p does not return any
> message like kernel="sd" or subsystem="vfat"
>
>How can udev and I create a block device?
>
>
You mentioned that you have some special rule for that player. Can we
see it? Do things work without it? Do other USB storage devices work?
--
Alexander E. Patrakov
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: usb storage not a block device ???
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
` (7 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Moshe Yudkowsky @ 2006-01-19 18:36 UTC (permalink / raw)
To: linux-hotplug
Alexander E. Patrakov wrote:
> G.ridolfi wrote:
>
>> Hello everybody
>> I' running Debian GNU/Linux unstable
>>
>> udev 0.080-1, linux-image-2.6.15-2
>>
>> My rule for the mp3 player and usb storage
>> Creative MuVo TXFM _partially_ fails in
>> creating the device. Udev creates a "c" device but not a *block* device .
>>
>>
> Sorry, I don't completely understand. Please provide the output of: ls
> -l /dev/what-udev-created.
Block devices are created by a kernel module such as usb_storage. You
probably ought to include the output of "lsmod" in your next email.
--
Moshe Yudkowsky
work: http://www.Disaggregate.com
book: http://www.PebbleAndAvalanche.com
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: usb storage not a block device ???
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
` (6 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: G.ridolfi @ 2006-01-20 8:55 UTC (permalink / raw)
To: linux-hotplug
Data: 19/01/06 19:36 Moshe Yudkowsky wrote
>
> Alexander E. Patrakov wrote:
> > G.ridolfi wrote:
> >
> >> Hello everybody
> >> I' running Debian GNU/Linux unstable
> >>
> >> udev 0.080-1, linux-image-2.6.15-2
> >>
> >> My rule for the mp3 player and usb storage
> >> Creative MuVo TXFM _partially_ fails in
> >> creating the device. Udev creates a "c" device but not a *block* device
.
> >>
> >>
> > Sorry, I don't completely understand. Please provide the output of: ls
> > -l /dev/what-udev-created.
crw-rw-r-- 1 root root 189, 386 2006-01-19 22:05 /dev/muvoTXFM
^
Isn't /dev/muvoTXFM a console device?
>
> Block devices are created by a kernel module such as usb_storage. You
> probably ought to include the output of "lsmod" in your next email.
here it is:
Module Size Used by
uinput 10400 2
ipv6 296836 10
ipt_limit 2464 8
iptable_mangle 2976 0
ipt_LOG 7072 8
ipt_MASQUERADE 3712 0
ipt_TOS 2688 0
ipt_REJECT 6528 1
ip_conntrack_irc 7340 0
ipt_state 1952 6
iptable_filter 3168 1
ip_tables 22048 8
ipt_limit,iptable_mangle,ipt_LOG,ipt_MASQUERADE,ipt_TOS,ipt_REJECT,ipt_state,iptable_filter
ip_nat_ftp 3840 0
ip_nat 21264 2 ipt_MASQUERADE,ip_nat_ftp
ip_conntrack_ftp 8496 1 ip_nat_ftp
ip_conntrack 63824 6
ipt_MASQUERADE,ip_conntrack_irc,ipt_state,ip_nat_ftp,ip_nat,ip_conntrack_ftp
nfnetlink 7448 2 ip_nat,ip_conntrack
sungem 37188 0
sungem_phy 10080 1 sungem
ohci1394 40564 0
vfat 14688 0
fat 59836 1 vfat
ehci_hcd 36712 0
ohci_hcd 23780 0
uhci_hcd 44496 0
usbhid 55108 0
usbcore 147136 5 ehci_hcd,ohci_hcd,uhci_hcd,usbhid
therm_adt746x 13352 0
sr_mod 20420 0
snd_powermac 51552 2
snd_pcm_oss 63648 1
snd_mixer_oss 21536 1 snd_pcm_oss
snd_pcm 102788 2 snd_powermac,snd_pcm_oss
snd_timer 27620 1 snd_pcm
snd 67412 7
snd_powermac,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore 11172 2 snd
snd_page_alloc 11656 1 snd_pcm
sbp2 26340 0
scsi_mod 170276 2 sr_mod,sbp2
ieee1394 428176 2 ohci1394,sbp2
ide_cd 47588 0
cdrom 44028 2 sr_mod,ide_cd
joydev 11872 0
ext3 154632 4
jbd 68564 1 ext3
mbcache 10980 1 ext3
ide_disk 19648 6
evdev 11808 9
> > You mentioned that you have some special rule for that player.
> > Can we see it?
Here it is:
----- file: /etc/udev/rules.d/010-muvo.rules -------
# MuVo TXFM
#
BUS="usb", SYSFS{product}="MuVo TX FM", NAME="muvoTXFM",
OPTIONS+="all_partitions"
------------------------eof ---------
> > Do things work without it?
Well, obviously kernel and udev recognised the device ...
I can see it in the output of "dmesg" and in /var/log/messages
The diff between `ls -lR /dev/` before and after the pluging-in
of MuVo reveals that a new console device created in
/dev/bus/usb/004:
crw-rw-r-- 1 root root 189, 389 2006-01-19 22:30 006
^
Then I don't know how I could have access to the pen.
> > Do other USB storage devices work?
I haven't tried yet.
However I can read and write MuVo with both MacOSX and winxp.
Will the output of udevinfo help in any way?
Giovanni
--
Email.it, the professional e-mail, gratis per te: http://www.email.it/f
Sponsor:
Problemi di Liquidità? Con Logos Finanziaria 30.000 € in 24 ore a
dipendenti e lavoratori autonomi con rimborsi fino a 120 mesi clicca qui
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid)07&d 060120
-------------------------------------------------------
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_______________________________________________
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
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: usb storage not a block device ???
2006-01-19 9:59 usb storage not a block device ??? G.ridolfi
` (2 preceding siblings ...)
2006-01-20 8:55 ` G.ridolfi
@ 2006-01-20 10:04 ` Alexander E. Patrakov
2006-01-20 11:46 ` Kay Sievers
` (5 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Alexander E. Patrakov @ 2006-01-20 10:04 UTC (permalink / raw)
To: linux-hotplug
G.ridolfi wrote:
>crw-rw-r-- 1 root root 189, 386 2006-01-19 22:05 /dev/muvoTXFM
>^
>Isn't /dev/muvoTXFM a console device?
>
>
What happens here is that your rule matches several devices, including
the wrong "usb generic" one.
>BUS="usb", SYSFS{product}="MuVo TX FM", NAME="muvoTXFM",
>OPTIONS+="all_partitions"
>
>
I'd suggest adding KERNEL="sd*", or, if you use the slow "ub" driver,
KERNEL="ub*" in front of this rule.
--
Alexander E. Patrakov
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: usb storage not a block device ???
2006-01-19 9:59 usb storage not a block device ??? G.ridolfi
` (3 preceding siblings ...)
2006-01-20 10:04 ` Alexander E. Patrakov
@ 2006-01-20 11:46 ` Kay Sievers
2006-01-20 13:23 ` G.ridolfi
` (4 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Kay Sievers @ 2006-01-20 11:46 UTC (permalink / raw)
To: linux-hotplug
On Fri, Jan 20, 2006 at 03:04:23PM +0500, Alexander E. Patrakov wrote:
> G.ridolfi wrote:
>
> >crw-rw-r-- 1 root root 189, 386 2006-01-19 22:05 /dev/muvoTXFM
> >^
> >Isn't /dev/muvoTXFM a console device?
> >
> >
> What happens here is that your rule matches several devices, including
> the wrong "usb generic" one.
>
> >BUS="usb", SYSFS{product}="MuVo TX FM", NAME="muvoTXFM",
> >OPTIONS+="all_partitions"
> >
> >
> I'd suggest adding KERNEL="sd*", or, if you use the slow "ub" driver,
> KERNEL="ub*" in front of this rule.
Just match on SUBSYSTEM="block".
Kay
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: usb storage not a block device ???
2006-01-19 9:59 usb storage not a block device ??? G.ridolfi
` (4 preceding siblings ...)
2006-01-20 11:46 ` Kay Sievers
@ 2006-01-20 13:23 ` G.ridolfi
2006-01-20 18:55 ` Moshe Yudkowsky
` (3 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: G.ridolfi @ 2006-01-20 13:23 UTC (permalink / raw)
To: linux-hotplug
Data: 20/01/06 12:48 Kay Sievers wrote:
>
> On Fri, Jan 20, 2006 at 03:04:23PM +0500, Alexander E. Patrakov wrote:
> > G.ridolfi wrote:
> >
> > >crw-rw-r-- 1 root root 189, 386 2006-01-19 22:05 /dev/muvoTXFM
> > >^
> > >Isn't /dev/muvoTXFM a console device?
> > >
> > >
> > What happens here is that your rule matches several devices, including
> > the wrong "usb generic" one.
> >
> > >BUS="usb", SYSFS{product}="MuVo TX FM", NAME="muvoTXFM",
> > >OPTIONS+="all_partitions"
> > >
> > >
> > I'd suggest adding KERNEL="sd*", or, if you use the slow "ub" driver,
> > KERNEL="ub*" in front of this rule.
I changed the rule according to your suggestion:
------rule
BUS="usb", SYSFS{product}="MuVo TX FM", NAME="muvoTXFM", KERNEL="sd*"
-------
#/etc/init.d/udev restart
# ls -lR /dev/ > ls-before
Inserted MuVo
# ls -lr /dev/> ls-after
# diff ls-before ls-after:
[two files were recreated when I inserted MuVo: xconsole and
/dev/bus/usb/004 ]
4c4
< prw-r----- 1 root adm 0 2006-01-20 11:55 xconsole
---
> prw-r----- 1 root adm 0 2006-01-20 11:57 xconsole
186c186
< drwxr-xr-x 2 root root 60 2006-01-20 11:55 004
---
> drwxr-xr-x 2 root root 80 2006-01-20 11:57 004
[a new file was created:/dev/bus/usb/004/004:]
192a193
> crw-rw-r-- 1 root root 189, 387 2006-01-20 11:57 004
But I cannot acces MuVo
>
> Just match on SUBSYSTEM="block".
>
I cannot find any << SUBSYSTEM="block" >> in what the kernel reads
:-(
# udevinfo -a -p
udevinfo starts with the device the node belongs to and then walks up the
device chain, to print for every device found, all possibly useful
attributes
in the udev key format.
Only attributes within one device section may be used together in one rule,
to match the device for which the node will be created.
looking at device '/devices/pci0001:10/0001:10:1b.2/usb4/4-1/4-1:1.0':
KERNEL="4-1:1.0"
SUBSYSTEM="usb"
SYSFS{interface}="Internal Flash Device"
SYSFS{modalias}="usb:v041Ep4120d1123dc00dsc00dp00ic08isc06ip50"
SYSFS{bInterfaceProtocol}="50"
SYSFS{bInterfaceSubClass}="06"
SYSFS{bInterfaceClass}="08"
SYSFS{bNumEndpoints}="02"
SYSFS{bAlternateSetting}=" 0"
SYSFS{bInterfaceNumber}="00"
looking at device '/devices/pci0001:10/0001:10:1b.2/usb4/4-1':
ID="4-1"
BUS="usb"
DRIVER="usb"
SYSFS{configuration}="Media"
SYSFS{serial}="0002F5CF71A10D83"
SYSFS{product}="MuVo TX FM"
SYSFS{manufacturer}="CREATIVE"
SYSFS{maxchild}="0"
SYSFS{version}=" 2.00"
SYSFS{devnum}="2"
SYSFS{speed}="480"
SYSFS{bMaxPacketSize0}="64"
SYSFS{bNumConfigurations}="1"
SYSFS{bDeviceProtocol}="00"
SYSFS{bDeviceSubClass}="00"
SYSFS{bDeviceClass}="00"
SYSFS{bcdDevice}="1123"
SYSFS{idProduct}="4120"
SYSFS{idVendor}="041e"
SYSFS{bMaxPower}="100mA"
SYSFS{bmAttributes}="80"
SYSFS{bConfigurationValue}="1"
SYSFS{bNumInterfaces}=" 1"
looking at device '/devices/pci0001:10/0001:10:1b.2/usb4':
ID="usb4"
BUS="usb"
DRIVER="usb"
SYSFS{configuration}=""
SYSFS{serial}="0001:10:1b.2"
SYSFS{product}="EHCI Host Controller"
SYSFS{manufacturer}="Linux 2.6.15-1-powerpc ehci_hcd"
SYSFS{maxchild}="5"
SYSFS{version}=" 2.00"
SYSFS{devnum}="1"
SYSFS{speed}="480"
SYSFS{bMaxPacketSize0}="64"
SYSFS{bNumConfigurations}="1"
SYSFS{bDeviceProtocol}="01"
SYSFS{bDeviceSubClass}="00"
SYSFS{bDeviceClass}="09"
SYSFS{bcdDevice}="0206"
SYSFS{idProduct}="0000"
SYSFS{idVendor}="0000"
SYSFS{bMaxPower}=" 0mA"
SYSFS{bmAttributes}="c0"
SYSFS{bConfigurationValue}="1"
SYSFS{bNumInterfaces}=" 1"
looking at device '/devices/pci0001:10/0001:10:1b.2':
ID="0001:10:1b.2"
BUS="pci"
DRIVER="ehci_hcd"
SYSFS{devspec}="/pci@f2000000/usb@1b_2"
SYSFS{modalias}="pci:v00001033d000000E0sv00001033sd000000E0bc0Csc03i20"
SYSFS{local_cpus}="1"
SYSFS{irq}="63"
SYSFS{class}="0x0c0320"
SYSFS{subsystem_device}="0x00e0"
SYSFS{subsystem_vendor}="0x1033"
SYSFS{device}="0x00e0"
SYSFS{vendor}="0x1033"
looking at device '/devices/pci0001:10':
ID="pci0001:10"
BUS=""
DRIVER=""
----------------------
Giovanni
--
Email.it, the professional e-mail, gratis per te: http://www.email.it/f
Sponsor:
Suonerie polifoniche, loghi, sfondi colorati, giochi multimediali, ecco
tutto quello che trovi nella sezione email.it dedicata ai cellulari
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid116&d 060120
-------------------------------------------------------
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_______________________________________________
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
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: usb storage not a block device ???
2006-01-19 9:59 usb storage not a block device ??? G.ridolfi
` (5 preceding siblings ...)
2006-01-20 13:23 ` G.ridolfi
@ 2006-01-20 18:55 ` Moshe Yudkowsky
2006-01-21 8:14 ` G.ridolfi
` (2 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Moshe Yudkowsky @ 2006-01-20 18:55 UTC (permalink / raw)
To: linux-hotplug
> 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."
--
Moshe Yudkowsky
work: http://www.Disaggregate.com
book: http://www.PebbleAndAvalanche.com
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: usb storage not a block device ???
2006-01-19 9:59 usb storage not a block device ??? G.ridolfi
` (6 preceding siblings ...)
2006-01-20 18:55 ` Moshe Yudkowsky
@ 2006-01-21 8:14 ` G.ridolfi
2006-01-21 8:50 ` Andrey Borzenkov
2006-01-21 10:15 ` G.ridolfi
9 siblings, 0 replies; 11+ messages in thread
From: G.ridolfi @ 2006-01-21 8:14 UTC (permalink / raw)
To: linux-hotplug
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
#tail /var/log/messages:
Jan 21 08:46:01 localhost kernel: Initializing USB Mass Storage driver...
Jan 21 08:46:01 localhost kernel: usbcore: registered new driver usb-storage
Jan 21 08:46:01 localhost kernel: USB Mass Storage support registered.
Jan 21 08:46:05 localhost kernel: usb 4-1: new high speed USB device using
ehci_hcd and address 3
Jan 21 08:46:06 localhost kernel: scsi0 : SCSI emulation for USB Mass
Storage devices
Jan 21 08:46:11 localhost kernel: Vendor: CREATIVE Model: MuVo TX FM
Rev: 1123
Jan 21 08:46:11 localhost kernel: Type: Direct-Access
ANSI SCSI revision: 04
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.
Also the indormation of udevinfo are the same I got without "modprobe
usb_storage"
--------------------- I got another usb storage device.
# dmesg
usb 4-1: new high speed USB device using ehci_hcd and address 5
hub 4-1:1.0: USB hub found
hub 4-1:1.0: 1 port detected
usb 4-1.1: new high speed USB device using ehci_hcd and address 6
ehci_hcd 0001:10:1b.2: qh eec19180 (#00) state 4
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 6
usb-storage: waiting for device to settle before scanning
Vendor: EUDAR Model: Marchi2.0 Rev: P1.0
Type: Direct-Access ANSI SCSI revision: 00
usb-storage: device scan complete
# udevinfo -a -p /sys/devices/pci0001\:10/0001\:10\:1b.2/usb4/4-1/4-1\:1.0/
udevinfo starts with the device the node belongs to and then walks up the
device chain, to print for every device found, all possibly useful
attributes
in the udev key format.
Only attributes within one device section may be used together in one rule,
to match the device for which the node will be created.
looking at device '/devices/pci0001:10/0001:10:1b.2/usb4/4-1/4-1:1.0':
KERNEL="4-1:1.0"
SUBSYSTEM="usb"
SYSFS{modalias}="usb:v067Bp2515d0001dc09dsc00dp01ic09isc00ip00"
SYSFS{bInterfaceProtocol}="00"
SYSFS{bInterfaceSubClass}="00"
SYSFS{bInterfaceClass}="09"
SYSFS{bNumEndpoints}="01"
SYSFS{bAlternateSetting}=" 0"
SYSFS{bInterfaceNumber}="00"
looking at device '/devices/pci0001:10/0001:10:1b.2/usb4/4-1':
ID="4-1"
BUS="usb"
DRIVER="usb"
SYSFS{configuration}=""
SYSFS{product}="USB Embedded Hub"
SYSFS{manufacturer}="EUDAR Technology Inc."
SYSFS{maxchild}="1"
SYSFS{version}=" 2.00"
SYSFS{devnum}="5"
SYSFS{speed}="480"
SYSFS{bMaxPacketSize0}="64"
SYSFS{bNumConfigurations}="1"
SYSFS{bDeviceProtocol}="01"
SYSFS{bDeviceSubClass}="00"
SYSFS{bDeviceClass}="09"
SYSFS{bcdDevice}="0001"
SYSFS{idProduct}="2515"
SYSFS{idVendor}="067b"
SYSFS{bMaxPower}="100mA"
SYSFS{bmAttributes}="c0"
SYSFS{bConfigurationValue}="1"
SYSFS{bNumInterfaces}=" 1"
looking at device '/devices/pci0001:10/0001:10:1b.2/usb4':
ID="usb4"
BUS="usb"
DRIVER="usb"
SYSFS{configuration}=""
SYSFS{serial}="0001:10:1b.2"
SYSFS{product}="EHCI Host Controller"
SYSFS{manufacturer}="Linux 2.6.15-1-powerpc ehci_hcd"
SYSFS{maxchild}="5"
SYSFS{version}=" 2.00"
SYSFS{devnum}="1"
SYSFS{speed}="480"
SYSFS{bMaxPacketSize0}="64"
SYSFS{bNumConfigurations}="1"
SYSFS{bDeviceProtocol}="01"
SYSFS{bDeviceSubClass}="00"
SYSFS{bDeviceClass}="09"
SYSFS{bcdDevice}="0206"
SYSFS{idProduct}="0000"
SYSFS{idVendor}="0000"
SYSFS{bMaxPower}=" 0mA"
SYSFS{bmAttributes}="c0"
SYSFS{bConfigurationValue}="1"
SYSFS{bNumInterfaces}=" 1"
looking at device '/devices/pci0001:10/0001:10:1b.2':
ID="0001:10:1b.2"
BUS="pci"
DRIVER="ehci_hcd"
SYSFS{devspec}="/pci@f2000000/usb@1b_2"
SYSFS{modalias}="pci:v00001033d000000E0sv00001033sd000000E0bc0Csc03i20"
SYSFS{local_cpus}="1"
SYSFS{irq}="63"
SYSFS{class}="0x0c0320"
SYSFS{subsystem_device}="0x00e0"
SYSFS{subsystem_vendor}="0x1033"
SYSFS{device}="0x00e0"
SYSFS{vendor}="0x1033"
looking at device '/devices/pci0001:10':
ID="pci0001:10"
BUS=""
DRIVER=""
No "sd" or "block" information and I don't know where and if a device
has been created to access the EUDAR.
Giovanni
--
Email.it, the professional e-mail, gratis per te: http://www.email.it/f
Sponsor:
Tutte le città a prezzi irresistibili: scegli tra più di 24.000 alberghi in
tutto il mondo, trova quello che vuoi!
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?midF48&d 060121
-------------------------------------------------------
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_______________________________________________
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
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: usb storage not a block device ???
2006-01-19 9:59 usb storage not a block device ??? G.ridolfi
` (7 preceding siblings ...)
2006-01-21 8:14 ` G.ridolfi
@ 2006-01-21 8:50 ` Andrey Borzenkov
2006-01-21 10:15 ` G.ridolfi
9 siblings, 0 replies; 11+ messages in thread
From: Andrey Borzenkov @ 2006-01-21 8:50 UTC (permalink / raw)
To: linux-hotplug
-----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
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: usb storage not a block device ???
2006-01-19 9:59 usb storage not a block device ??? G.ridolfi
` (8 preceding siblings ...)
2006-01-21 8:50 ` Andrey Borzenkov
@ 2006-01-21 10:15 ` G.ridolfi
9 siblings, 0 replies; 11+ messages in thread
From: G.ridolfi @ 2006-01-21 10:15 UTC (permalink / raw)
To: linux-hotplug
Data: 21/01/06 09:51 Da: Andrey Borzenkov
> 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
> > >
> > > 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.
Oh yes!!!!
I've just mounted and read mboth the storage devices! Thank you very
very much Andrey!
:-) me happy.
> 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"
>
I tried to add these lines to /etc/udev.rules
then
# rmmod sd_mod usb_storage
# /etc/init.d/udev restart
then I plugged in the usb, but nothing happened
So I
# modprobe usb_storage ;modprobe sd_mod
and I can access the device
Could you please suggest me in which rule I shall write your code.
> > However /dev/muvo is created but...
>
> Irrelevant. This is created by usbhid. If you want to rename (that I
> strongly NOT recommend)
I strongly agreee with you /now/ ;) The device is detected when inserted
and I can mount it and access to it via a gnome applet.
I removed my rule ;)
> 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?
>
Well I don't have such a /dev(/disk/by-id) directory with the symlinks
Thank you again,
Giovanni
--
Email.it, the professional e-mail, gratis per te: http://www.email.it/f
Sponsor:
Trova la tua anima gemella con Meetic. Iscriviti subito gratis: potrai
trovare migliaia di single in linea e chattare con loro!
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid@48&d 060121
-------------------------------------------------------
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_______________________________________________
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
^ permalink raw reply [flat|nested] 11+ messages in thread