Re: [gentoo-user] confused udev?

[Dirk Heinrichs <ext-dirk.heinrichs@nokia.com>]

[-- Attachment #1: Type: text/plain, Size: 3823 bytes --]

Am Donnerstag, 17. November 2005 13:43 schrieb ext Jorge Almeida:

> 	CONFIG_USB_STORAGE=y
> 	(...)

Did you also enable the sub options?

> 	# SCSI device support
> 	#
> 	CONFIG_SCSI=y
> 	CONFIG_SCSI_PROC_FS=y
>
> 	#
> 	# SCSI support type (disk, tape, CD-ROM)
> 	#
> 	CONFIG_BLK_DEV_SD=y

Looks good.

dmesg output for the HD looks good, too.

> 	usb 1-7: new high speed USB device using ehci_hcd and address 4
> 	usb 1-7: device descriptor read/64, error -71
> 	scsi1 : SCSI emulation for USB Mass Storage devices
> 	usb-storage: device found at 4
> 	usb-storage: waiting for device to settle before scanning
> 	usb 1-7: reset high speed USB device using ehci_hcd and address 4
> 	  Vendor: PLEXTOR   Model: PlexFlash-2       Rev: 5.02
> 	    Type:   Direct-Access                      ANSI SCSI revision: 00
> 	    usb 1-7: reset high speed USB device using ehci_hcd and address 4
> 	    usb 1-7: reset high speed USB device using ehci_hcd and address 4
> 	    usb 1-7: reset high speed USB device using ehci_hcd and address 4
> 	    usb 1-7: reset high speed USB device using ehci_hcd and address 4
> 	    usb 1-7: reset high speed USB device using ehci_hcd and address 4
> 	    usb 1-7: reset high speed USB device using ehci_hcd and address 4
> 	    sdb: Write Protect is on
> 	    sdb: Mode Sense: 45 00 80 08
> 	    sdb: assuming drive cache: write through
> 	    Attached scsi removable disk sdb at scsi1, channel 0, id 0, lun 0
> 	    usb-storage: device scan complete

I'm a bit confused about all those resets.

> > What does udevinfo -a -p $(udevinfo -q path -n /dev/sdX) tell you
> > (replace X with the appropriate letter for each device)?
>
> $ udevinfo -a -p $(udevinfo -q path -n /dev/sda)
>
> 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.

OK, here's the interesting part:

>0:0:0:0': BUS=="scsi"
>     ID=="0:0:0:0"
>     DRIVER=="sd"
>     SYSFS{device_blocked}=="0"
>     SYSFS{iocounterbits}=="32"
>     SYSFS{iodone_cnt}=="0x1642"
>     SYSFS{ioerr_cnt}=="0x0"
>     SYSFS{iorequest_cnt}=="0x1642"
>     SYSFS{max_sectors}=="240"
>     SYSFS{model}=="L250R0          "
>     SYSFS{queue_depth}=="1"
>     SYSFS{queue_type}=="none"
>     SYSFS{rev}=="BAH4"
>     SYSFS{scsi_level}=="3"
>     SYSFS{state}=="running"
>     SYSFS{timeout}=="30"
>     SYSFS{type}=="0"
>     SYSFS{vendor}=="Maxtor 6"

That would give the following rule (all in one line):

BUS=="usb", KERNEL=="sd*", SYSFS{model}=="L250R0          ", 
SYSFS{vendor}=="Maxtor 6", NAME="usb/disk%n"

Note the spaces in the model part, don't know wether the wildcard "*" works 
here, too. Feel free to change the name part to whatever you like :-)

>
> After plugging the memstick:
>
> 	$ udevinfo -a -p $(udevinfo -q path -n /dev/sdb)
> 	no record for 'sdb' in database
> 	udevinfo: option requires an argument -- p
> 	Usage: udevinfo [-anpqrVh]
> 	  (etc)

Hmm, this is strange. Did you check if /dev/sdb is really there? I currently 
have no idea what could be wrong. If not already done, could you recompile 
your kernel with all sub options of CONFIG_USB_STORAGE and see if this 
makes any difference with the stick?

Bye...

	Dirk
-- 
Dirk Heinrichs          | Tel:  +49 (0)162 234 3408
Configuration Manager   | Fax:  +49 (0)211 47068 111
Capgemini Deutschland   | Mail: dirk.heinrichs@capgemini.com
Hambornerstraße 55      | Web:  http://www.capgemini.com
D-40472 Düsseldorf      | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: www.keyserver.net

[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]