public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jorge Almeida <jalmeida@math.ist.utl.pt>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] confused udev?
Date: Thu, 17 Nov 2005 14:14:58 +0000 (WET)	[thread overview]
Message-ID: <Pine.LNX.4.63.0511171405360.3944@weber.math.ist.utl.pt> (raw)
In-Reply-To: <200511171454.37956.ext-dirk.heinrichs@nokia.com>

On Thu, 17 Nov 2005, Dirk Heinrichs wrote:

> Am Donnerstag, 17. November 2005 13:43 schrieb ext Jorge Almeida:
> 
> > 	CONFIG_USB_STORAGE=y
> > 	(...)
> 
> Did you also enable the sub options?
No, since none appeared to have much to do with my devices.
> 
> 
> > 	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.
> 
> 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"

Is it really BUS=="usb" rather than BUS=="scsi"?
> 
> 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 

/dev/sdb and /dev/sdb1 exist, but don't seem to be much help.
	$ ls /dev|grep sdb
	sdb
	sdb1
	sdb10
	sdb11
	sdb12
	sdb13
	sdb14
	sdb15
	sdb2
	sdb3
	sdb4
	sdb5
	sdb6
	sdb7
	sdb8
	sdb9
	
$ mount -t vfat /dev/sdb1 /mnt/pen
mount: /dev/sdb1: can't read superblock

> 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?
> 
Will try it...
> Bye...
> 
> 	Dirk
> 
Thanks,

Jorge 
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-11-17 14:23 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-17  9:26 [gentoo-user] confused udev? Jorge Almeida
2005-11-17  9:49 ` Dirk Heinrichs
2005-11-17 12:43   ` Jorge Almeida
2005-11-17 13:54     ` Dirk Heinrichs
2005-11-17 14:14       ` Jorge Almeida [this message]
2005-11-18 10:21         ` Dirk Heinrichs
2005-11-18 10:29           ` Neil Bothwick
2005-11-18 10:40             ` Dirk Heinrichs
2005-11-18 10:31           ` Jorge Almeida
2005-11-20  2:21             ` Richard Fish
2005-11-20 11:21               ` Jorge Almeida
2005-11-21 15:18                 ` Richard Fish
2005-11-22 11:46                   ` Jorge Almeida
2005-11-23  4:10                     ` Richard Fish
2005-11-23  9:32                       ` Jorge Almeida
2005-11-23 15:07                         ` Richard Fish
2005-11-23 21:13                           ` Jorge Almeida
2005-11-17 14:14     ` Richard Fish
2005-11-17 16:19       ` Jorge Almeida
2005-11-17 17:11         ` Richard Fish
2005-11-17 17:47           ` Jorge Almeida
2005-11-17 18:14             ` Richard Fish
2005-11-17 18:23               ` Jorge Almeida
2005-11-17 20:15                 ` Richard Fish
2005-11-17 20:49                   ` Jorge Almeida
2005-11-17 21:11                     ` Richard Fish
2005-11-17 22:04                       ` Jorge Almeida
2005-11-17 23:57                         ` Richard Fish
2005-11-18  8:33                           ` Jorge Almeida
2005-11-18  7:03                       ` Dirk Heinrichs
2005-11-18  6:56         ` Dirk Heinrichs
2005-11-18  8:36           ` Jorge Almeida

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=Pine.LNX.4.63.0511171405360.3944@weber.math.ist.utl.pt \
    --to=jalmeida@math.ist.utl.pt \
    --cc=gentoo-user@lists.gentoo.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