[gentoo-user] confused udev?

public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed

* [gentoo-user] confused udev?
@ 2005-11-17  9:26 Jorge Almeida
  2005-11-17  9:49 ` Dirk Heinrichs
  0 siblings, 1 reply; 32+ messages in thread
From: Jorge Almeida @ 2005-11-17  9:26 UTC (permalink / raw
  To: gentoo-user

I have a USB memory stick and an external USB box with an IDE disk.
I configured udev to assign device names to both items, or so I thought.
The external box is plugged, the memory stick isn't.
The problem is: the device for the box is not created, and the memstick
device exists but represents the box, not the stick. I read
http://www.reactivated.net/writing_udev_rules.html#identify-sysfs
and
http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/Flash-Memory-HOWTO.html

What else should I do?

The gory details:

	$ ls /etc/udev/rules.d/
	40-my.rules  40-my.rules~  50-udev.rules

	$ cat /etc/udev/rules.d/40-my.rules
	BUS="scsi", SYSFS{vendor}="PLEXTOR ", SYSFS_model="PlexFlash-2*", NAME="plextor_memstick%n"
	BUS="scsi", SYSFS{vendor}="Maxtor 6 ", SYSFS_model="L250R0*", NAME="external_hd%n"

I tried also SYSFS_vendor instead of SYSFS{vendor} ...

	$ mount -t auto /dev/plextor_memstick1 /mnt/maxtor/
	$ ls /mnt/maxtor/
	lost+found

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

^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  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
  0 siblings, 1 reply; 32+ messages in thread
From: Dirk Heinrichs @ 2005-11-17  9:49 UTC (permalink / raw
  To: gentoo-user

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

Am Donnerstag, 17. November 2005 10:26 schrieb ext Jorge Almeida:

> I have a USB memory stick and an external USB box with an IDE disk.
> I configured udev to assign device names to both items, or so I thought.
> The external box is plugged, the memory stick isn't.
> The problem is: the device for the box is not created, and the memstick
> device exists but represents the box, not the stick. I read

Some questions:

What's your udev and kernel version?

Did you configure your kernel to use USB storage (if in doubt, post your 
kernel config)?

Does the system detect the devices when you plug them in (post the last few 
lines of dmesg output after plugging in each device)

What does udevinfo -a -p $(udevinfo -q path -n /dev/sdX) tell you (replace X 
with the appropriate letter for each device)?

Maybe we can sort this out.

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 --]

^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  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     ` Richard Fish
  0 siblings, 2 replies; 32+ messages in thread
From: Jorge Almeida @ 2005-11-17 12:43 UTC (permalink / raw
  To: gentoo-user

On Thu, 17 Nov 2005, Dirk Heinrichs wrote:

> Am Donnerstag, 17. November 2005 10:26 schrieb ext Jorge Almeida:
> 
> > I have a USB memory stick and an external USB box with an IDE disk.
> > I configured udev to assign device names to both items, or so I thought.
> > The external box is plugged, the memory stick isn't.
> > The problem is: the device for the box is not created, and the memstick
> > device exists but represents the box, not the stick. I read
> 
> Some questions:
> 
> What's your udev and kernel version?
> 
sys-fs/udev-070-r1
2.6.13-gentoo-r3

> Did you configure your kernel to use USB storage (if in doubt, post your 
> kernel config)?

Yes, and I can use the devices (write and read files...).

	CONFIG_USB_STORAGE=y
	(...)
	# SCSI device support
	#
	CONFIG_SCSI=y
	CONFIG_SCSI_PROC_FS=y
	
	#
	# SCSI support type (disk, tape, CD-ROM)
	#
	CONFIG_BLK_DEV_SD=y
	
> 
> Does the system detect the devices when you plug them in (post the last few 
> lines of dmesg output after plugging in each device)
> 
ipt_recent v0.3.1: Stephen Frost <sfrost@snowman.net>.
http://snowman.net/projects/ipt_recent/
spurious 8259A interrupt: IRQ7.
EXT3 FS on hda6, internal journal
usb 1-3: 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
  Vendor: Maxtor 6  Model: L250R0            Rev: BAH4
    Type:   Direct-Access                      ANSI SCSI revision: 00
    SCSI device sda: 490234752 512-byte hdwr sectors (251000 MB)
    sda: assuming drive cache: write through
    SCSI device sda: 490234752 512-byte hdwr sectors (251000 MB)
    sda: assuming drive cache: write through
     sda: unknown partition table
     Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
     usb-storage: device scan complete
     SCSI device sda: 490234752 512-byte hdwr sectors (251000 MB)
     sda: assuming drive cache: write through
      sda: sda1
      SCSI device sda: 490234752 512-byte hdwr sectors (251000 MB)
      sda: assuming drive cache: write through
       sda: sda1
       kjournald starting.  Commit interval 5 seconds
       EXT3 FS on sda1, internal journal
       EXT3-fs: mounted filesystem with ordered data mode.
       kjournald starting.  Commit interval 5 seconds
       EXT3 FS on sda1, internal journal
       EXT3-fs: mounted filesystem with ordered data mode.
       kjournald starting.  Commit interval 5 seconds
       EXT3 FS on sda1, internal journal
       EXT3-fs: mounted filesystem with ordered data mode.
       FAT: "conv=auto" option is obsolete, not supported now
       FAT: "posix" option is obsolete, not supported now
       FAT: bogus number of reserved sectors
       VFS: Can't find a valid FAT filesystem on dev sda1.
       kjournald starting.  Commit interval 5 seconds
       EXT3 FS on sda1, internal journal
       EXT3-fs: mounted filesystem with ordered data mode.
       kjournald starting.  Commit interval 5 seconds
       EXT3 FS on sda1, internal journal
       EXT3-fs: mounted filesystem with ordered data mode.

The memstick has a vfat in it (original). The external disk has 1
partition with ext3.
The line in /etc/fstab corresponding to the memstick (the disk doesn't
have one, yet):
	/dev/plextor_memstick1          /mnt/pen        vfat noauto,user,noexec,nodev,rw,noatime,conv=auto,uni_xlate,posix   0 0

Now I plugged the memstick. dmesg says:

	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
	    

> 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.

device '/sys/block/sda' has major:minor 8:0
  looking at class device '/sys/block/sda':
    KERNEL=="sda"
    SUBSYSTEM=="block"
    SYSFS{dev}=="8:0"
    SYSFS{range}=="16"
    SYSFS{removable}=="0"
    SYSFS{size}=="490234752"
    SYSFS{stat}=="     105      547     1975      616     5584   619494  1250606  3500080        0    25620  3500696"

follow the "device"-link to the physical device:
  looking at the device chain at '/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host0/target0:0:0/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"

  looking at the device chain at '/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host0/target0:0:0':
    BUS==""
    ID=="target0:0:0"
    DRIVER=="unknown"

  looking at the device chain at '/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host0':
    BUS==""
    ID=="host0"
    DRIVER=="unknown"

  looking at the device chain at '/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0':
    BUS=="usb"
    ID=="1-3:1.0"
    DRIVER=="usb-storage"
    SYSFS{bAlternateSetting}==" 0"
    SYSFS{bInterfaceClass}=="08"
    SYSFS{bInterfaceNumber}=="00"
    SYSFS{bInterfaceProtocol}=="50"
    SYSFS{bInterfaceSubClass}=="06"
    SYSFS{bNumEndpoints}=="02"
    SYSFS{modalias}=="usb:v067Bp3507d0100dc00dsc00dp00ic08isc06ip50"

  looking at the device chain at '/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-3':
    BUS=="usb"
    ID=="1-3"
    DRIVER=="usb"
    SYSFS{bConfigurationValue}=="1"
    SYSFS{bDeviceClass}=="00"
    SYSFS{bDeviceProtocol}=="00"
    SYSFS{bDeviceSubClass}=="00"
    SYSFS{bMaxPacketSize0}=="64"
    SYSFS{bMaxPower}=="100mA"
    SYSFS{bNumConfigurations}=="1"
    SYSFS{bNumInterfaces}==" 1"
    SYSFS{bcdDevice}=="0100"
    SYSFS{bmAttributes}=="c0"
    SYSFS{configuration}==""
    SYSFS{devnum}=="3"
    SYSFS{idProduct}=="3507"
    SYSFS{idVendor}=="067b"
    SYSFS{manufacturer}=="Prolific Technology Inc."
    SYSFS{maxchild}=="0"
    SYSFS{product}=="Mass Storage Device"
    SYSFS{serial}=="0"
    SYSFS{speed}=="480"
    SYSFS{version}==" 2.00"

  looking at the device chain at '/sys/devices/pci0000:00/0000:00:1d.7/usb1':
    BUS=="usb"
    ID=="usb1"
    DRIVER=="usb"
    SYSFS{bConfigurationValue}=="1"
    SYSFS{bDeviceClass}=="09"
    SYSFS{bDeviceProtocol}=="01"
    SYSFS{bDeviceSubClass}=="00"
    SYSFS{bMaxPacketSize0}=="8"
    SYSFS{bMaxPower}=="  0mA"
    SYSFS{bNumConfigurations}=="1"
    SYSFS{bNumInterfaces}==" 1"
    SYSFS{bcdDevice}=="0206"
    SYSFS{bmAttributes}=="e0"
    SYSFS{configuration}==""
    SYSFS{devnum}=="1"
    SYSFS{idProduct}=="0000"
    SYSFS{idVendor}=="0000"
    SYSFS{manufacturer}=="Linux 2.6.13-gentoo-r3 ehci_hcd"
    SYSFS{maxchild}=="8"
    SYSFS{product}=="Intel Corporation 82801EB/ER _ICH5/ICH5R_ USB2 EHCI Controller"
    SYSFS{serial}=="0000:00:1d.7"
    SYSFS{speed}=="480"
    SYSFS{version}==" 2.00"

  looking at the device chain at '/sys/devices/pci0000:00/0000:00:1d.7':
    BUS=="pci"
    ID=="0000:00:1d.7"
    DRIVER=="ehci_hcd"
    SYSFS{class}=="0x0c0320"
    SYSFS{device}=="0x24dd"
    SYSFS{irq}=="10"
    SYSFS{local_cpus}=="1"
    SYSFS{modalias}=="pci:v00008086d000024DDsv00001462sd00007280bc0Csc03i20"
    SYSFS{subsystem_device}=="0x7280"
    SYSFS{subsystem_vendor}=="0x1462"
    SYSFS{vendor}=="0x8086"

  looking at the device chain at '/sys/devices/pci0000:00':
    BUS==""
    ID=="pci0000:00"
    DRIVER=="unknown"
 
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)
> Maybe we can sort this out.
> 
> Bye...
> 
> 	Dirk
> 
Thanks.


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



^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-17 12:43   ` Jorge Almeida
@ 2005-11-17 13:54     ` Dirk Heinrichs
  2005-11-17 14:14       ` Jorge Almeida
  2005-11-17 14:14     ` Richard Fish
  1 sibling, 1 reply; 32+ messages in thread
From: Dirk Heinrichs @ 2005-11-17 13:54 UTC (permalink / raw
  To: gentoo-user

[-- 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 --]

^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-17 12:43   ` Jorge Almeida
  2005-11-17 13:54     ` Dirk Heinrichs
@ 2005-11-17 14:14     ` Richard Fish
  2005-11-17 16:19       ` Jorge Almeida
  1 sibling, 1 reply; 32+ messages in thread
From: Richard Fish @ 2005-11-17 14:14 UTC (permalink / raw
  To: gentoo-user

On 11/17/05, Jorge Almeida <jalmeida@math.ist.utl.pt> wrote:
>         $ cat /etc/udev/rules.d/40-my.rules
>         BUS="scsi", SYSFS{vendor}="PLEXTOR ", SYSFS_model="PlexFlash-2*", NAME="plextor_memstick%n"
>         BUS="scsi", SYSFS{vendor}="Maxtor 6 ", SYSFS_model="L250R0*", NAME="external_hd%n"

>     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"

Here is a problem...you have an extra space in your vendor string, so
the first rule will not match.

Also, you should be using "==" in your rules, not "=", and
SYSFS{model}, not SYSFS_model.    I think these latter issues are the
reason the plextor rule is matching, because from the udev man page,
"=" does not test for equality, it assigns a value to a key.

So first, cut-n-paste the vendor and model strings from this output
into your rule, and change all of the "=" to "==" (except for the NAME
setting).  Then try setting udev_log=7 in /etc/udev/udev.conf, and
watch /var/log/messages when you plug in the drive.

-Richard

-- 
gentoo-user@gentoo.org mailing list

^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-17 13:54     ` Dirk Heinrichs
@ 2005-11-17 14:14       ` Jorge Almeida
  2005-11-18 10:21         ` Dirk Heinrichs
  0 siblings, 1 reply; 32+ messages in thread
From: Jorge Almeida @ 2005-11-17 14:14 UTC (permalink / raw
  To: gentoo-user

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



^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-17 14:14     ` Richard Fish
@ 2005-11-17 16:19       ` Jorge Almeida
  2005-11-17 17:11         ` Richard Fish
  2005-11-18  6:56         ` Dirk Heinrichs
  0 siblings, 2 replies; 32+ messages in thread
From: Jorge Almeida @ 2005-11-17 16:19 UTC (permalink / raw
  To: gentoo-user

On Thu, 17 Nov 2005, Richard Fish wrote:

> On 11/17/05, Jorge Almeida <jalmeida@math.ist.utl.pt> wrote:
> >         $ cat /etc/udev/rules.d/40-my.rules
> >         BUS="scsi", SYSFS{vendor}="PLEXTOR ", SYSFS_model="PlexFlash-2*", NAME="plextor_memstick%n"
> >         BUS="scsi", SYSFS{vendor}="Maxtor 6 ", SYSFS_model="L250R0*", NAME="external_hd%n"
> 
> >     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"
> 
> Here is a problem...you have an extra space in your vendor string, so
> the first rule will not match.
> 
> Also, you should be using "==" in your rules, not "=", and
> SYSFS{model}, not SYSFS_model.    I think these latter issues are the
> reason the plextor rule is matching, because from the udev man page,
> "=" does not test for equality, it assigns a value to a key.
So much for the rules in
http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/Flash-Memory-HOWTO.html#hotplug
...
> 
> So first, cut-n-paste the vendor and model strings from this output
> into your rule, and change all of the "=" to "==" (except for the NAME
> setting).  Then try setting udev_log=7 in /etc/udev/udev.conf, and
> watch /var/log/messages when you plug in the drive.
> 
Did it. Upon reboot, I had /dev/external_hd and /dev/external_hd1, but
only /dev/plextor_memstick (i.e., no mountable /dev/plextor_memstick1).
I unplugged the stick and turned off the HD case. I plugged back the
stick. Now /dev/plextor_memstick and /dev/plextor_memstick1 exist, as
they should. I turned the case on. Well, no /dev/external_hd...

Moreover:
	$ systool  -vb scsi | grep vendor
	    vendor              = "PLEXTOR "
	
No external disk...
	$ udevinfo -a -p $(udevinfo -q path -n /dev/sda)
	no record for 'sda' in database
	(...)
The same for sdb...

(There's something very wrong either with me or with udev. I'm ready to
accept the former, but I still remember when devfs went out, one year or
so ago, and my USB scanner stopped working.)

> -Richard
> 
Thanks again.

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



^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-17 16:19       ` Jorge Almeida
@ 2005-11-17 17:11         ` Richard Fish
  2005-11-17 17:47           ` Jorge Almeida
  2005-11-18  6:56         ` Dirk Heinrichs
  1 sibling, 1 reply; 32+ messages in thread
From: Richard Fish @ 2005-11-17 17:11 UTC (permalink / raw
  To: gentoo-user

On 11/17/05, Jorge Almeida <jalmeida@math.ist.utl.pt> wrote:
> So much for the rules in
> http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/Flash-Memory-HOWTO.html#hotplug
> ...

Yes, it is terribly out of date, being written when udev was at
version 016!!  That is soooo last month! :->

> Did it. Upon reboot, I had /dev/external_hd and /dev/external_hd1, but
> only /dev/plextor_memstick (i.e., no mountable /dev/plextor_memstick1).
> I unplugged the stick and turned off the HD case. I plugged back the
> stick. Now /dev/plextor_memstick and /dev/plextor_memstick1 exist, as
> they should. I turned the case on. Well, no /dev/external_hd...

Can you post your current rules.  Also, don't forget Dirk's suggestion
regarding BUS=="usb" instead of scsi.

> No external disk...
>         $ udevinfo -a -p $(udevinfo -q path -n /dev/sda)
>         no record for 'sda' in database
>         (...)
> The same for sdb...

Yes, this I would expect now, because you are not creating sdX device
nodes anymore.  You would need to use the device nodes that you are
creating.

You could use the SYMLINK target instead of changing the name.  Something like:

BUS=="usb" ... NAME="%k", SYMLINK="plextor_memstick%n"

This would keep the default sdX device nodes, but give you symlinks
for your persistent names.

-Richard

-- 
gentoo-user@gentoo.org mailing list

^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-17 17:11         ` Richard Fish
@ 2005-11-17 17:47           ` Jorge Almeida
  2005-11-17 18:14             ` Richard Fish
  0 siblings, 1 reply; 32+ messages in thread
From: Jorge Almeida @ 2005-11-17 17:47 UTC (permalink / raw
  To: gentoo-user

On Thu, 17 Nov 2005, Richard Fish wrote:
> 
> Can you post your current rules.  Also, don't forget Dirk's suggestion
> regarding BUS=="usb" instead of scsi.
> 
> You could use the SYMLINK target instead of changing the name.  Something like:
> 
> BUS=="usb" ... NAME="%k", SYMLINK="plextor_memstick%n"
> 
> This would keep the default sdX device nodes, but give you symlinks
> for your persistent names.
> 
> -Richard
> 
> 
Current:
	BUS=="scsi", SYSFS{vendor}=="PLEXTOR*", SYSFS{model}=="PlexFlash-2*", NAME="%k", SYMLINK="plextor_memstick%n"
	BUS=="scsi", SYSFS{vendor}=="Maxtor 6*", SYSFS{model}=="L250R0*", NAME="%k", SYMLINK="external_hd%n"
No change (i.e., still no /dev/external...)
/dev/plextor_memstick and /dev/plextor_memstick1 exist as symlinks.
With "usb" instead of "scsi", also no change. With
NAME="plextor_memstick%n" etc, no change (except that there are dev
nodes, not symlinks)

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



^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-17 17:47           ` Jorge Almeida
@ 2005-11-17 18:14             ` Richard Fish
  2005-11-17 18:23               ` Jorge Almeida
  0 siblings, 1 reply; 32+ messages in thread
From: Richard Fish @ 2005-11-17 18:14 UTC (permalink / raw
  To: gentoo-user

On 11/17/05, Jorge Almeida <jalmeida@math.ist.utl.pt> wrote:
> On Thu, 17 Nov 2005, Richard Fish wrote:
> >
> > Can you post your current rules.  Also, don't forget Dirk's suggestion
> > regarding BUS=="usb" instead of scsi.
> >
> > You could use the SYMLINK target instead of changing the name.  Something like:
> >
> > BUS=="usb" ... NAME="%k", SYMLINK="plextor_memstick%n"
> >
> > This would keep the default sdX device nodes, but give you symlinks
> > for your persistent names.
> >
> > -Richard
> >
> >
> Current:
>         BUS=="scsi", SYSFS{vendor}=="PLEXTOR*", SYSFS{model}=="PlexFlash-2*", NAME="%k", SYMLINK="plextor_memstick%n"
>         BUS=="scsi", SYSFS{vendor}=="Maxtor 6*", SYSFS{model}=="L250R0*", NAME="%k", SYMLINK="external_hd%n"
> No change (i.e., still no /dev/external...)
> /dev/plextor_memstick and /dev/plextor_memstick1 exist as symlinks.
> With "usb" instead of "scsi", also no change. With
> NAME="plextor_memstick%n" etc, no change (except that there are dev
> nodes, not symlinks)

Hmm, looks ok.  Could you set udev_log=7 in /etc/udev/udev.conf, and
post the entries that are added to /var/log/messages when you turn on
the hard drive.

-Richard

-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-17 18:14             ` Richard Fish
@ 2005-11-17 18:23               ` Jorge Almeida
  2005-11-17 20:15                 ` Richard Fish
  0 siblings, 1 reply; 32+ messages in thread
From: Jorge Almeida @ 2005-11-17 18:23 UTC (permalink / raw
  To: gentoo-user

On Thu, 17 Nov 2005, Richard Fish wrote:
> Hmm, looks ok.  Could you set udev_log=7 in /etc/udev/udev.conf, and
> post the entries that are added to /var/log/messages when you turn on
> the hard drive.
> 
$ tail -F /var/log/kernel/current
Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
Nov 17 17:41:51 [kernel] usb-storage: Bulk command transfer result=0
Nov 17 17:41:51 [kernel] usb-storage: Attempting to get CSW...
Nov 17 17:41:51 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer
13 bytes
Nov 17 17:41:51 [kernel] usb-storage: Status code 0; transferred 13/13
Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
Nov 17 17:41:51 [kernel] usb-storage: Bulk status result = 0
Nov 17 17:41:51 [kernel] usb-storage: Bulk Status S 0x53425355 T 0x78 R
0 Stat 0x0
Nov 17 17:41:51 [kernel] usb-storage: scsi cmd done, result=0x0
Nov 17 17:41:51 [kernel] usb-storage: *** thread sleeping.
Nov 17 18:21:25 [kernel] usb 1-3: new high speed USB device using
ehci_hcd and address 20
Nov 17 18:21:25 [kernel] usb 1-3: device descriptor read/all, error -71
Nov 17 18:21:25 [kernel] usb 1-3: new high speed USB device using
ehci_hcd and address 21
Nov 17 18:21:25 [kernel] usb 1-3: string descriptor 0 read error: -71
- Last output repeated 2 times -
Nov 17 18:21:25 [kernel] usb 1-3: new high speed USB
device using ehci_hcd and address 22
Nov 17 18:21:25 [kernel] usb 1-3: string descriptor 0
read error: -71
- Last output repeated 2 times -
Nov 17 18:21:25 [kernel] usb 1-3: new
high speed USB device using ehci_hcd and
address 23
Nov 17 18:21:25 [kernel] usb 1-3: string
descriptor 0 read error: -71


(Using metalog...)


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



^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-17 18:23               ` Jorge Almeida
@ 2005-11-17 20:15                 ` Richard Fish
  2005-11-17 20:49                   ` Jorge Almeida
  0 siblings, 1 reply; 32+ messages in thread
From: Richard Fish @ 2005-11-17 20:15 UTC (permalink / raw
  To: gentoo-user

On 11/17/05, Jorge Almeida <jalmeida@math.ist.utl.pt> wrote:
> On Thu, 17 Nov 2005, Richard Fish wrote:
> > Hmm, looks ok.  Could you set udev_log=7 in /etc/udev/udev.conf, and
> > post the entries that are added to /var/log/messages when you turn on
> > the hard drive.
> >
> $ tail -F /var/log/kernel/current
> Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
> Nov 17 17:41:51 [kernel] usb-storage: Bulk command transfer result=0
> Nov 17 17:41:51 [kernel] usb-storage: Attempting to get CSW...
> Nov 17 17:41:51 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer
> 13 bytes
> Nov 17 17:41:51 [kernel] usb-storage: Status code 0; transferred 13/13
> Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
> Nov 17 17:41:51 [kernel] usb-storage: Bulk status result = 0
> Nov 17 17:41:51 [kernel] usb-storage: Bulk Status S 0x53425355 T 0x78 R
> 0 Stat 0x0
> Nov 17 17:41:51 [kernel] usb-storage: scsi cmd done, result=0x0
> Nov 17 17:41:51 [kernel] usb-storage: *** thread sleeping.
> Nov 17 18:21:25 [kernel] usb 1-3: new high speed USB device using
> ehci_hcd and address 20
> Nov 17 18:21:25 [kernel] usb 1-3: device descriptor read/all, error -71
> Nov 17 18:21:25 [kernel] usb 1-3: new high speed USB device using
> ehci_hcd and address 21
> Nov 17 18:21:25 [kernel] usb 1-3: string descriptor 0 read error: -71
> - Last output repeated 2 times -
> Nov 17 18:21:25 [kernel] usb 1-3: new high speed USB
> device using ehci_hcd and address 22
> Nov 17 18:21:25 [kernel] usb 1-3: string descriptor 0
> read error: -71
> - Last output repeated 2 times -
> Nov 17 18:21:25 [kernel] usb 1-3: new
> high speed USB device using ehci_hcd and
> address 23
> Nov 17 18:21:25 [kernel] usb 1-3: string
> descriptor 0 read error: -71

Ok, something is going wrong in either hardware or kernel land for
this device.  You should be seeing entries like this from the kernel:

Nov 17 13:10:30 carcharias usb 1-3: new high speed USB device using
ehci_hcd and address 5
Nov 17 13:10:30 carcharias scsi2 : SCSI emulation for USB Mass Storage devices
Nov 17 13:10:30 carcharias usb-storage: device found at 5
Nov 17 13:10:30 carcharias usb-storage: waiting for device to settle
before scanning
Nov 17 13:10:35 carcharias Vendor: ST910082  Model: 3A                Rev: 3.02
Nov 17 13:10:35 carcharias Type:   Direct-Access                     
ANSI SCSI revision: 00
Nov 17 13:10:35 carcharias SCSI device sda: 195371568 512-byte hdwr
sectors (100030 MB)

Particularly the last one, about the new SCSI device and it's size, is
important.  If you have USB and the other drivers built as modules,
reload them and try again.  If they are built into your kernel,
reboot.

-Richard

-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-17 20:15                 ` Richard Fish
@ 2005-11-17 20:49                   ` Jorge Almeida
  2005-11-17 21:11                     ` Richard Fish
  0 siblings, 1 reply; 32+ messages in thread
From: Jorge Almeida @ 2005-11-17 20:49 UTC (permalink / raw
  To: gentoo-user

On Thu, 17 Nov 2005, Richard Fish wrote:
> important.  If you have USB and the other drivers built as modules,
> reload them and try again.  If they are built into your kernel,
> reboot.
> 
This is Chaos.

On reboot, /dev/external_hd and /dev/external_hd1 exist. I mounted the
disk with no problems. /dev/plextor_memstick and /dev/plextor_memstick1
don't exist (or rather they appear as broken links). Understandable,
since the stick is not plugged. I plugged it and still no nodes.  I
unmounted the external disk and /dev/external_hd /dev/external_hd1 are
gone! And /dev/plextor_memstick & /dev/plextor_memstick1 didn't came
back.

The messages:
	Nov 17 17:41:51 [kernel] usb-storage: Bulk data transfer result 0x0
	Nov 17 17:41:51 [kernel] usb-storage: Attempting to get CSW...
	Nov 17 17:41:51 [kernel] usb-storage: queuecommand called
	Nov 17 17:41:51 [kernel] usb-storage: *** thread awakened.
	Nov 17 17:41:51 [kernel] usb-storage: Command READ_10 (10 bytes)
	Nov 17 17:41:51 [kernel] usb-storage:  28 00 00 1f 51 eb 00 00 08 00
	Nov 17 17:41:51 [kernel] usb-storage: Bulk Command S 0x43425355 T 0x72 L 4096 F 128 Trg 0 LUN 0 CL 10
	Nov 17 17:41:51 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
	Nov 17 17:41:51 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
	Nov 17 17:41:51 [kernel] usb-storage: Bulk command transfer result=0
	Nov 17 17:41:51 [kernel] usb-storage: usb_stor_bulk_transfer_sglist: xfer 4096 bytes, 1 entries
	Nov 17 17:41:51 [kernel] usb-storage: Status code 0; transferred 4096/4096
	Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
	Nov 17 17:41:51 [kernel] usb-storage: Bulk data transfer result 0x0
	Nov 17 17:41:51 [kernel] usb-storage: Attempting to get CSW...
	Nov 17 17:41:51 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
	Nov 17 17:41:51 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
	Nov 17 17:41:51 [kernel] usb-storage: Bulk status result = 0
	Nov 17 17:41:51 [kernel] usb-storage: Bulk Status S 0x53425355 T 0x72 R 0 Stat 0x0
	Nov 17 17:41:51 [kernel] usb-storage: scsi cmd done, result=0x0
	Nov 17 17:41:51 [kernel] usb-storage: *** thread sleeping.
	Nov 17 17:41:51 [kernel] usb-storage: queuecommand called
	Nov 17 17:41:51 [kernel] usb-storage: *** thread awakened.
	Nov 17 17:41:51 [kernel] usb-storage: Command READ_10 (10 bytes)
	Nov 17 17:41:51 [kernel] usb-storage:  28 00 00 1f 50 6b 00 00 08 00
	Nov 17 17:41:51 [kernel] usb-storage: Bulk Command S 0x43425355 T 0x73 L 4096 F 128 Trg 0 LUN 0 CL 10
	Nov 17 17:41:51 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
	Nov 17 17:41:51 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
	Nov 17 17:41:51 [kernel] usb-storage: Bulk command transfer result=0
	Nov 17 17:41:51 [kernel] usb-storage: usb_stor_bulk_transfer_sglist: xfer 4096 bytes, 1 entries
	Nov 17 17:41:51 [kernel] usb-storage: Status code 0; transferred 4096/4096
	Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
	Nov 17 17:41:51 [kernel] usb-storage: Bulk data transfer result 0x0
	Nov 17 17:41:51 [kernel] usb-storage: Attempting to get CSW...
	Nov 17 17:41:51 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
	Nov 17 17:41:51 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
	Nov 17 17:41:51 [kernel] usb-storage: Bulk status result = 0
	Nov 17 17:41:51 [kernel] usb-storage: Bulk Status S 0x53425355 T 0x73 R 0 Stat 0x0
	Nov 17 17:41:51 [kernel] usb-storage: scsi cmd done, result=0x0
	Nov 17 17:41:51 [kernel] usb-storage: *** thread sleeping.
	Nov 17 17:41:51 [kernel] usb-storage: queuecommand called
	Nov 17 17:41:51 [kernel] usb-storage: *** thread awakened.
	Nov 17 17:41:51 [kernel] usb-storage: Command READ_10 (10 bytes)
	Nov 17 17:41:51 [kernel] usb-storage:  28 00 00 1f 51 f3 00 00 08 00
	Nov 17 17:41:51 [kernel] usb-storage: Bulk Command S 0x43425355 T 0x74 L 4096 F 128 Trg 0 LUN 0 CL 10
	Nov 17 17:41:51 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
	Nov 17 17:41:51 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
	Nov 17 17:41:51 [kernel] usb-storage: Bulk command transfer result=0
	Nov 17 17:41:51 [kernel] usb-storage: usb_stor_bulk_transfer_sglist: xfer 4096 bytes, 1 entries
	Nov 17 17:41:51 [kernel] usb-storage: Status code 0; transferred 4096/4096
	Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
	Nov 17 17:41:51 [kernel] usb-storage: Bulk data transfer result 0x0
	Nov 17 17:41:51 [kernel] usb-storage: Attempting to get CSW...
	Nov 17 17:41:51 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
	Nov 17 17:41:51 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
	Nov 17 17:41:51 [kernel] usb-storage: Bulk status result = 0
	Nov 17 17:41:51 [kernel] usb-storage: Bulk Status S 0x53425355 T 0x74 R 0 Stat 0x0
	Nov 17 17:41:51 [kernel] usb-storage: scsi cmd done, result=0x0
	Nov 17 17:41:51 [kernel] usb-storage: *** thread sleeping.
	Nov 17 17:41:51 [kernel] usb-storage: queuecommand called
	Nov 17 17:41:51 [kernel] usb-storage: *** thread awakened.
	Nov 17 17:41:51 [kernel] usb-storage: Command READ_10 (10 bytes)
	Nov 17 17:41:51 [kernel] usb-storage:  28 00 00 00 00 13 00 00 08 00
	Nov 17 17:41:51 [kernel] usb-storage: Bulk Command S 0x43425355 T 0x75 L 4096 F 128 Trg 0 LUN 0 CL 10
	Nov 17 17:41:51 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
	Nov 17 17:41:51 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
	Nov 17 17:41:51 [kernel] usb-storage: Bulk command transfer result=0
	Nov 17 17:41:51 [kernel] usb-storage: usb_stor_bulk_transfer_sglist: xfer 4096 bytes, 1 entries
	Nov 17 17:41:51 [kernel] usb-storage: Status code 0; transferred 4096/4096
	Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
	Nov 17 17:41:51 [kernel] usb-storage: Bulk data transfer result 0x0
	Nov 17 17:41:51 [kernel] usb-storage: Attempting to get CSW...
	Nov 17 17:41:51 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
	Nov 17 17:41:51 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
	Nov 17 17:41:51 [kernel] usb-storage: Bulk status result = 0
	Nov 17 17:41:51 [kernel] usb-storage: Bulk Status S 0x53425355 T 0x75 R 0 Stat 0x0
	Nov 17 17:41:51 [kernel] usb-storage: scsi cmd done, result=0x0
	Nov 17 17:41:51 [kernel] usb-storage: *** thread sleeping.
	Nov 17 17:41:51 [kernel] usb-storage: queuecommand called
	Nov 17 17:41:51 [kernel] usb-storage: *** thread awakened.
	Nov 17 17:41:51 [kernel] usb-storage: Command READ_10 (10 bytes)
	Nov 17 17:41:51 [kernel] usb-storage:  28 00 00 00 00 1b 00 00 40 00
	Nov 17 17:41:51 [kernel] usb-storage: Bulk Command S 0x43425355 T 0x76 L 32768 F 128 Trg 0 LUN 0 CL 10
	Nov 17 17:41:51 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
	Nov 17 17:41:51 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
	Nov 17 17:41:51 [kernel] usb-storage: Bulk command transfer result=0
	Nov 17 17:41:51 [kernel] usb-storage: usb_stor_bulk_transfer_sglist: xfer 32768 bytes, 4 entries
	Nov 17 17:41:51 [kernel] usb-storage: Status code 0; transferred 32768/32768
	Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
	Nov 17 17:41:51 [kernel] usb-storage: Bulk data transfer result 0x0
	Nov 17 17:41:51 [kernel] usb-storage: Attempting to get CSW...
	Nov 17 17:41:51 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
	Nov 17 17:41:51 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
	Nov 17 17:41:51 [kernel] usb-storage: Bulk status result = 0
	Nov 17 17:41:51 [kernel] usb-storage: Bulk Status S 0x53425355 T 0x76 R 0 Stat 0x0
	Nov 17 17:41:51 [kernel] usb-storage: scsi cmd done, result=0x0
	Nov 17 17:41:51 [kernel] usb-storage: *** thread sleeping.
	Nov 17 17:41:51 [kernel] usb-storage: queuecommand called
	Nov 17 17:41:51 [kernel] usb-storage: *** thread awakened.
	Nov 17 17:41:51 [kernel] usb-storage: Command READ_10 (10 bytes)
	Nov 17 17:41:51 [kernel] usb-storage:  28 00 00 00 02 03 00 00 28 00
	Nov 17 17:41:51 [kernel] usb-storage: Bulk Command S 0x43425355 T 0x77 L 20480 F 128 Trg 0 LUN 0 CL 10
	Nov 17 17:41:51 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
	Nov 17 17:41:51 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
	Nov 17 17:41:51 [kernel] usb-storage: Bulk command transfer result=0
	Nov 17 17:41:51 [kernel] usb-storage: usb_stor_bulk_transfer_sglist: xfer 20480 bytes, 3 entries
	Nov 17 17:41:51 [kernel] usb-storage: Status code 0; transferred 20480/20480
	Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
	Nov 17 17:41:51 [kernel] usb-storage: Bulk data transfer result 0x0
	Nov 17 17:41:51 [kernel] usb-storage: Attempting to get CSW...
	Nov 17 17:41:51 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
	Nov 17 17:41:51 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
	Nov 17 17:41:51 [kernel] usb-storage: Bulk status result = 0
	Nov 17 17:41:51 [kernel] usb-storage: Bulk Status S 0x53425355 T 0x77 R 0 Stat 0x0
	Nov 17 17:41:51 [kernel] usb-storage: scsi cmd done, result=0x0
	Nov 17 17:41:51 [kernel] usb-storage: *** thread sleeping.
	Nov 17 17:41:51 [kernel] usb-storage: queuecommand called
	Nov 17 17:41:51 [kernel] usb-storage: *** thread awakened.
	Nov 17 17:41:51 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
	Nov 17 17:41:51 [kernel] usb-storage: Bulk command transfer result=0
	Nov 17 17:41:51 [kernel] usb-storage: Attempting to get CSW...
	Nov 17 17:41:51 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
	Nov 17 17:41:51 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
	Nov 17 17:41:51 [kernel] usb-storage: Bulk status result = 0
	Nov 17 17:41:51 [kernel] usb-storage: Bulk Status S 0x53425355 T 0x78 R 0 Stat 0x0
	Nov 17 17:41:51 [kernel] usb-storage: scsi cmd done, result=0x0
	Nov 17 17:41:51 [kernel] usb-storage: *** thread sleeping.
	Nov 17 18:21:25 [kernel] usb 1-3: new high speed USB device using ehci_hcd and address 20
	Nov 17 18:21:25 [kernel] usb 1-3: device descriptor read/all, error -71
	Nov 17 18:21:25 [kernel] usb 1-3: new high speed USB device using ehci_hcd and address 21
	Nov 17 18:21:25 [kernel] usb 1-3: string descriptor 0 read error: -71
	                - Last output repeated 2 times -
	Nov 17 18:21:25 [kernel] usb 1-3: new high speed USB device using ehci_hcd and address 22
	Nov 17 18:21:25 [kernel] usb 1-3: string descriptor 0 read error: -71
	                - Last output repeated 2 times -
	Nov 17 18:21:25 [kernel] usb 1-3: new high speed USB device using ehci_hcd and address 23
	Nov 17 18:21:25 [kernel] usb 1-3: string descriptor 0 read error: -71
	                - Last output repeated 2 times -
	Nov 17 18:52:59 [kernel] usb 1-7: USB disconnect, address 11
	Nov 17 20:36:10 [kernel] cdrom: open failed.
	Nov 17 20:36:10 [kernel] cdrom: open failed.
	Nov 17 20:36:10 [kernel] r8169: eth0: link up
	Nov 17 20:36:12 [kernel] ip_tables: (C) 2000-2002 Netfilter core team
	Nov 17 20:36:12 [kernel] ip_conntrack version 2.1 (8191 buckets, 65528 max) - 212 bytes per conntrack
	Nov 17 20:36:13 [kernel] ipt_recent v0.3.1: Stephen Frost <sfrost@snowman.net>.  http://snowman.net/projects/ipt_recent/
	Nov 17 20:35:57 [kernel] usb-storage: queuecommand called
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 32768/32768
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk data transfer result 0x0
	Nov 17 20:35:57 [kernel] usb-storage: Attempting to get CSW...
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk status result = 0
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Status S 0x53425355 T 0x18 R 0 Stat 0x0
	Nov 17 20:35:57 [kernel] usb-storage: scsi cmd done, result=0x0
	Nov 17 20:35:57 [kernel] usb-storage: *** thread sleeping.
	Nov 17 20:35:57 [kernel] usb-storage: queuecommand called
	Nov 17 20:35:57 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk command transfer result=0
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_sglist: xfer 1024 bytes, 1 entries
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 1024/1024
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk data transfer result 0x0
	Nov 17 20:35:57 [kernel] usb-storage: Attempting to get CSW...
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk status result = 0
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Status S 0x53425355 T 0x19 R 0 Stat 0x0
	Nov 17 20:35:57 [kernel] usb-storage: scsi cmd done, result=0x0
	Nov 17 20:35:57 [kernel] usb-storage: *** thread sleeping.
	Nov 17 20:35:57 [kernel] usb-storage: queuecommand called
	Nov 17 20:35:57 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:35:57 [kernel] usb-storage: Command READ_10 (10 bytes)
	Nov 17 20:35:57 [kernel] usb-storage:  28 00 00 00 00 3f 00 00 08 00
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Command S 0x43425355 T 0x1a L 4096 F 128 Trg 0 LUN 0 CL 10
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 4096/4096
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk data transfer result 0x0
	Nov 17 20:35:57 [kernel] usb-storage: Attempting to get CSW...
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk status result = 0
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Status S 0x53425355 T 0x1a R 0 Stat 0x0
	Nov 17 20:35:57 [kernel] usb-storage: scsi cmd done, result=0x0
	Nov 17 20:35:57 [kernel] usb-storage: *** thread sleeping.
	Nov 17 20:35:57 [kernel] usb-storage: queuecommand called
	Nov 17 20:35:57 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:35:57 [kernel] usb-storage: Command READ_10 (10 bytes)
	Nov 17 20:35:57 [kernel] usb-storage:  28 00 00 00 00 47 00 00 08 00
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Command S 0x43425355 T 0x1b L 4096 F 128 Trg 0 LUN 0 CL 10
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk command transfer result=0
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_sglist: xfer 4096 bytes, 1 entries
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 4096/4096
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk data transfer result 0x0
	Nov 17 20:35:57 [kernel] usb-storage: Attempting to get CSW...
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk status result = 0
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Status S 0x53425355 T 0x1b R 0 Stat 0x0
	Nov 17 20:35:57 [kernel] usb-storage: scsi cmd done, result=0x0
	Nov 17 20:35:57 [kernel] usb-storage: *** thread sleeping.
	Nov 17 20:35:57 [kernel] usb-storage: queuecommand called
	Nov 17 20:35:57 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:35:57 [kernel] usb-storage: Command READ_10 (10 bytes)
	Nov 17 20:35:57 [kernel] usb-storage:  28 00 00 00 00 4f 00 00 08 00
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Command S 0x43425355 T 0x1c L 4096 F 128 Trg 0 LUN 0 CL 10
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk command transfer result=0
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 4096/4096
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk data transfer result 0x0
	Nov 17 20:35:57 [kernel] usb-storage: Attempting to get CSW...
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk status result = 0
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Status S 0x53425355 T 0x1c R 0 Stat 0x0
	Nov 17 20:35:57 [kernel] usb-storage: scsi cmd done, result=0x0
	Nov 17 20:35:57 [kernel] usb-storage: *** thread sleeping.
	Nov 17 20:35:57 [kernel] usb-storage: queuecommand called
	Nov 17 20:35:57 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:35:57 [kernel] usb-storage: Command READ_10 (10 bytes)
	Nov 17 20:35:57 [kernel] usb-storage:  28 00 00 00 00 67 00 00 08 00
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Command S 0x43425355 T 0x1d L 4096 F 128 Trg 0 LUN 0 CL 10
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk command transfer result=0
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_sglist: xfer 4096 bytes, 1 entries
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 4096/4096
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk data transfer result 0x0
	Nov 17 20:35:57 [kernel] usb-storage: Attempting to get CSW...
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk status result = 0
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Status S 0x53425355 T 0x1d R 0 Stat 0x0
	Nov 17 20:35:57 [kernel] usb-storage: scsi cmd done, result=0x0
	Nov 17 20:35:57 [kernel] usb-storage: *** thread sleeping.
	Nov 17 20:35:57 [kernel] usb-storage: queuecommand called
	Nov 17 20:35:57 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:35:57 [kernel] usb-storage: Command READ_10 (10 bytes)
	Nov 17 20:35:57 [kernel] usb-storage:  28 00 00 00 10 7f 00 00 08 00
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Command S 0x43425355 T 0x1e L 4096 F 128 Trg 0 LUN 0 CL 10
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk command transfer result=0
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_sglist: xfer 4096 bytes, 1 entries
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 4096/4096
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk data transfer result 0x0
	Nov 17 20:35:57 [kernel] usb-storage: Attempting to get CSW...
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk status result = 0
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Status S 0x53425355 T 0x1e R 0 Stat 0x0
	Nov 17 20:35:57 [kernel] usb-storage: scsi cmd done, result=0x0
	Nov 17 20:35:57 [kernel] usb-storage: *** thread sleeping.
	Nov 17 20:35:57 [kernel] usb-storage: queuecommand called
	Nov 17 20:35:57 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:35:57 [kernel] usb-storage: Command READ_10 (10 bytes)
	Nov 17 20:35:57 [kernel] usb-storage:  28 00 00 00 10 87 00 00 40 00
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Command S 0x43425355 T 0x1f L 32768 F 128 Trg 0 LUN 0 CL 10
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk command transfer result=0
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_sglist: xfer 32768 bytes, 8 entries
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 32768/32768
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk data transfer result 0x0
	Nov 17 20:35:57 [kernel] usb-storage: Attempting to get CSW...
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk status result = 0
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Status S 0x53425355 T 0x1f R 0 Stat 0x0
	Nov 17 20:35:57 [kernel] usb-storage: scsi cmd done, result=0x0
	Nov 17 20:35:57 [kernel] usb-storage: *** thread sleeping.
	Nov 17 20:35:57 [kernel] usb-storage: queuecommand called
	Nov 17 20:35:57 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:35:57 [kernel] usb-storage: Command READ_10 (10 bytes)
	Nov 17 20:35:57 [kernel] usb-storage:  28 00 00 00 10 df 00 00 08 00
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Command S 0x43425355 T 0x20 L 4096 F 128 Trg 0 LUN 0 CL 10
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk command transfer result=0
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_sglist: xfer 4096 bytes, 1 entries
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 4096/4096
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk data transfer result 0x0
	Nov 17 20:35:57 [kernel] usb-storage: Attempting to get CSW...
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk status result = 0
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Status S 0x53425355 T 0x20 R 0 Stat 0x0
	Nov 17 20:35:57 [kernel] usb-storage: scsi cmd done, result=0x0
	Nov 17 20:35:57 [kernel] usb-storage: *** thread sleeping.
	Nov 17 20:35:57 [kernel] usb-storage: queuecommand called
	Nov 17 20:35:57 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:35:57 [kernel] usb-storage: Command READ_10 (10 bytes)
	Nov 17 20:35:57 [kernel] usb-storage:  28 00 00 00 10 e7 00 00 a8 00
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Command S 0x43425355 T 0x21 L 86016 F 128 Trg 0 LUN 0 CL 10
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk command transfer result=0
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_sglist: xfer 86016 bytes, 21 entries
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 86016/86016
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk data transfer result 0x0
	Nov 17 20:35:57 [kernel] usb-storage: Attempting to get CSW...
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk status result = 0
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Status S 0x53425355 T 0x21 R 0 Stat 0x0
	Nov 17 20:35:57 [kernel] usb-storage: scsi cmd done, result=0x0
	Nov 17 20:35:57 [kernel] usb-storage: *** thread sleeping.
	Nov 17 20:35:57 [kernel] usb-storage: queuecommand called
	Nov 17 20:35:57 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk command transfer result=0
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_sglist: xfer 12288 bytes, 3 entries
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 12288/12288
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk data transfer result 0x0
	Nov 17 20:35:57 [kernel] usb-storage: Attempting to get CSW...
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk status result = 0
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Status S 0x53425355 T 0x22 R 0 Stat 0x0
	Nov 17 20:35:57 [kernel] usb-storage: scsi cmd done, result=0x0
	Nov 17 20:35:57 [kernel] usb-storage: *** thread sleeping.
	Nov 17 20:35:57 [kernel] usb-storage: queuecommand called
	Nov 17 20:35:57 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:35:57 [kernel] usb-storage: Command WRITE_10 (10 bytes)
	Nov 17 20:35:57 [kernel] usb-storage:  2a 00 00 00 10 7f 00 00 08 00
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Command S 0x43425355 T 0x23 L 4096 F 0 Trg 0 LUN 0 CL 10
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk command transfer result=0
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_sglist: xfer 4096 bytes, 1 entries
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 4096/4096
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk data transfer result 0x0
	Nov 17 20:35:57 [kernel] usb-storage: Attempting to get CSW...
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk status result = 0
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Status S 0x53425355 T 0x23 R 0 Stat 0x0
	Nov 17 20:35:57 [kernel] usb-storage: scsi cmd done, result=0x0
	Nov 17 20:35:57 [kernel] usb-storage: *** thread sleeping.
	Nov 17 20:35:57 [kernel] kjournald starting.  Commit interval 5 seconds
	Nov 17 20:35:57 [kernel] usb-storage: queuecommand called
	Nov 17 20:35:57 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:35:57 [kernel] usb-storage: Command WRITE_10 (10 bytes)
	Nov 17 20:35:57 [kernel] usb-storage:  2a 00 00 00 00 3f 00 00 08 00
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Command S 0x43425355 T 0x24 L 4096 F 0 Trg 0 LUN 0 CL 10
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk command transfer result=0
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_sglist: xfer 4096 bytes, 1 entries
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 4096/4096
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk data transfer result 0x0
	Nov 17 20:35:57 [kernel] usb-storage: Attempting to get CSW...
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk status result = 0
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Status S 0x53425355 T 0x24 R 0 Stat 0x0
	Nov 17 20:35:57 [kernel] usb-storage: scsi cmd done, result=0x0
	Nov 17 20:35:57 [kernel] usb-storage: *** thread sleeping.
	Nov 17 20:35:57 [kernel] EXT3-fs: recovery complete.
	Nov 17 20:35:57 [kernel] usb-storage: queuecommand called
	Nov 17 20:35:57 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:35:57 [kernel] usb-storage: Command WRITE_10 (10 bytes)
	Nov 17 20:35:57 [kernel] usb-storage:  2a 00 00 00 10 7f 00 00 08 00
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Command S 0x43425355 T 0x25 L 4096 F 0 Trg 0 LUN 0 CL 10
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk command transfer result=0
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_sglist: xfer 4096 bytes, 1 entries
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 4096/4096
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk data transfer result 0x0
	Nov 17 20:35:57 [kernel] usb-storage: Attempting to get CSW...
	Nov 17 20:35:57 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
	Nov 17 20:35:57 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:35:57 [kernel] usb-storage: -- transfer complete
	Nov 17 20:35:57 [kernel] usb-storage: Bulk status result = 0
	Nov 17 20:35:57 [kernel] usb-storage: Bulk Status S 0x53425355 T 0x25 R 0 Stat 0x0
	Nov 17 20:35:57 [kernel] usb-storage: scsi cmd done, result=0x0
	Nov 17 20:35:57 [kernel] usb-storage: *** thread sleeping.
	Nov 17 20:35:57 [kernel] EXT3-fs: mounted filesystem with ordered data mode.
	Nov 17 20:36:03 [kernel] usb-storage: queuecommand called
	Nov 17 20:36:03 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:36:03 [kernel] usb-storage: Status code 0; transferred 4096/4096
	Nov 17 20:36:03 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:36:08 [kernel] usb-storage: queuecommand called
	Nov 17 20:36:08 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:36:08 [kernel] usb-storage: Status code 0; transferred 4096/4096
	Nov 17 20:36:08 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:36:08 [kernel] usb-storage: queuecommand called
	Nov 17 20:36:08 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:36:08 [kernel] usb-storage: Status code 0; transferred 8192/8192
	Nov 17 20:36:08 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:36:08 [kernel] usb-storage: queuecommand called
	Nov 17 20:36:08 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:36:08 [kernel] usb-storage: Status code 0; transferred 4096/4096
	Nov 17 20:36:08 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:36:31 [kernel] usb-storage: queuecommand called
	Nov 17 20:36:31 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:36:31 [kernel] usb-storage: Status code 0; transferred 4096/4096
	Nov 17 20:36:31 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:31 [kernel] usb 1-7: new high speed USB device using ehci_hcd and address 4
	Nov 17 20:37:31 [kernel] usb 1-7: device descriptor read/64, error -71
	Nov 17 20:37:31 [kernel] usb-storage: USB Mass Storage device detected
	Nov 17 20:37:31 [kernel] usb-storage: -- associate_dev
	Nov 17 20:37:31 [kernel] usb-storage: GetMaxLUN command result is 1, data is 0
	Nov 17 20:37:31 [kernel] scsi1 : SCSI emulation for USB Mass Storage devices
	Nov 17 20:37:31 [kernel] usb-storage: *** thread sleeping.
	Nov 17 20:37:31 [kernel] usb-storage: device found at 4
	Nov 17 20:37:31 [kernel] usb-storage: waiting for device to settle before scanning
	Nov 17 20:37:36 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:36 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:36 [kernel] usb-storage: Status code -71; transferred 0/36
	Nov 17 20:37:36 [kernel] usb 1-7: reset high speed USB device using ehci_hcd and address 4
	Nov 17 20:37:37 [kernel] usb-storage: usb_reset_device returns 0
	Nov 17 20:37:37 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:37 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:37 [kernel] usb-storage: Status code -71; transferred 0/36
	Nov 17 20:37:37 [kernel] usb 1-7: reset high speed USB device using ehci_hcd and address 4
	Nov 17 20:37:37 [kernel] usb-storage: usb_reset_device returns 0
	Nov 17 20:37:37 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:37 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 36/36
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:37 [kernel]   Vendor: PLEXTOR   Model: PlexFlash-2       Rev: 5.02
	Nov 17 20:37:37 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 18/18
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:37 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:37 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 18/18
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:37 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:37 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 18/18
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:37 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:37 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:37 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:37 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 8/8
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:37 [kernel] SCSI device sdb: 2052607 512-byte hdwr sectors (1051 MB)
	Nov 17 20:37:37 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:37 [kernel] usb-storage: Status code -71; transferred 0/192
	Nov 17 20:37:37 [kernel] usb 1-7: reset high speed USB device using ehci_hcd and address 4
	Nov 17 20:37:37 [kernel] usb-storage: usb_reset_device returns 0
	Nov 17 20:37:37 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:37 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 8/192
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:37 [kernel] sdb: Write Protect is on
	Nov 17 20:37:37 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:37 [kernel] usb-storage: Status code -71; transferred 0/18
	Nov 17 20:37:37 [kernel] usb 1-7: reset high speed USB device using ehci_hcd and address 4
	Nov 17 20:37:37 [kernel] usb-storage: usb_reset_device returns 0
	Nov 17 20:37:37 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:37 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:37 [kernel] usb-storage: Status code -71; transferred 0/18
	Nov 17 20:37:37 [kernel] usb 1-7: reset high speed USB device using ehci_hcd and address 4
	Nov 17 20:37:37 [kernel] usb-storage: usb_reset_device returns 0
	Nov 17 20:37:37 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:37 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 18/18
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:37 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:37 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:37 [kernel] usb-storage: Status code -71; transferred 0/18
	Nov 17 20:37:37 [kernel] usb 1-7: reset high speed USB device using ehci_hcd and address 4
	Nov 17 20:37:37 [kernel] usb-storage: usb_reset_device returns 0
	Nov 17 20:37:37 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:37 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 18/18
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:37 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:37 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:37 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:37 [kernel] usb-storage: Status code -71; transferred 0/18
	Nov 17 20:37:37 [kernel] usb 1-7: reset high speed USB device using ehci_hcd and address 4
	Nov 17 20:37:38 [kernel] usb-storage: usb_reset_device returns 0
	Nov 17 20:37:38 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:38 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:38 [kernel] usb-storage: Status code -71; transferred 0/18
	Nov 17 20:37:38 [kernel] usb 1-7: reset high speed USB device using ehci_hcd and address 4
	Nov 17 20:37:38 [kernel] usb-storage: usb_reset_device returns 0
	Nov 17 20:37:38 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:38 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:38 [kernel] usb-storage: Status code -71; transferred 0/18
	Nov 17 20:37:38 [kernel] usb 1-7: reset high speed USB device using ehci_hcd and address 4
	Nov 17 20:37:38 [kernel] usb-storage: usb_reset_device returns 0
	Nov 17 20:37:38 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:38 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 18/18
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:38 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:38 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:38 [kernel] usb-storage: Status code -71; transferred 0/18
	Nov 17 20:37:38 [kernel] usb 1-7: reset high speed USB device using ehci_hcd and address 4
	Nov 17 20:37:38 [kernel] usb-storage: usb_reset_device returns 0
	Nov 17 20:37:38 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:38 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:38 [kernel] usb-storage: Status code -32; transferred 0/8
	Nov 17 20:37:38 [kernel] usb-storage: usb_stor_clear_halt: result = 0
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:38 [kernel] usb-storage: Status code -71; transferred 0/18
	Nov 17 20:37:38 [kernel] usb 1-7: reset high speed USB device using ehci_hcd and address 4
	Nov 17 20:37:38 [kernel] usb-storage: usb_reset_device returns 0
	Nov 17 20:37:38 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:38 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:38 [kernel] usb-storage: Status code -32; transferred 0/8
	Nov 17 20:37:38 [kernel] usb-storage: usb_stor_clear_halt: result = 0
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 18/18
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:38 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:38 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:38 [kernel] usb-storage: Status code -32; transferred 0/8
	Nov 17 20:37:38 [kernel] usb-storage: usb_stor_clear_halt: result = 0
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 18/18
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:38 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:38 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:38 [kernel] usb-storage: Status code -71; transferred 0/192
	Nov 17 20:37:38 [kernel] usb 1-7: reset high speed USB device using ehci_hcd and address 4
	Nov 17 20:37:38 [kernel] usb-storage: usb_reset_device returns 0
	Nov 17 20:37:38 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:38 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 31/31
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 8/192
	Nov 17 20:37:38 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:37:38 [kernel] sdb: Write Protect is on
	Nov 17 20:37:38 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:38 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:38 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:38 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:38 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:38 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:38 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:38 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:38 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:38 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:38 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:38 [kernel] usb-storage: queuecommand called
	Nov 17 20:37:38 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:37:38 [kernel] usb-storage: device scan complete
	Nov 17 20:38:54 [kernel] usb-storage: queuecommand called
	Nov 17 20:38:54 [kernel] usb-storage: Status code 0; transferred 4096/4096
	Nov 17 20:38:54 [kernel] usb-storage: Status code 0; transferred 13/13
	Nov 17 20:38:54 [kernel] usb-storage: queuecommand called
	Nov 17 20:38:54 [kernel] usb-storage: Status code -71; transferred 0/31
	Nov 17 20:38:55 [kernel] usb 1-3: reset high speed USB device using ehci_hcd and address 3
	Nov 17 20:38:55 [kernel] usb 1-3: device descriptor read/64, error -71
	Nov 17 20:38:55 [kernel] usb 1-3: device not accepting address 3, error -71
	Nov 17 20:38:55 [kernel] usb 1-3: reset high speed USB device using ehci_hcd and address 3
	Nov 17 20:38:56 [kernel] usb 1-3: device not accepting address 3, error -71
	Nov 17 20:38:56 [kernel] usb 1-3: reset high speed USB device using ehci_hcd and address 3
	Nov 17 20:38:56 [kernel] usb 1-3: device not accepting address 3, error -71
	Nov 17 20:38:56 [kernel] usb 1-3: reset high speed USB device using ehci_hcd and address 3
	Nov 17 20:38:57 [kernel] usb 1-3: device not accepting address 3, error -71
	Nov 17 20:38:57 [kernel] scsi0 (0:0): rejecting I/O to device being removed
	Nov 17 20:38:57 [kernel] usb-storage: -- usb_stor_release_resources
	Nov 17 20:38:57 [kernel] usb-storage: *** thread awakened.
	Nov 17 20:38:57 [kernel] usb 1-3: new high speed USB device using ehci_hcd and address 5
	Nov 17 20:38:57 [kernel] usb 1-3: device descriptor read/all, error -71
	Nov 17 20:38:57 [kernel] usb 1-3: new high speed USB device using ehci_hcd and address 6
	Nov 17 20:38:57 [kernel] usb 1-3: string descriptor 0 read error: -71
	                - Last output repeated 2 times -
	Nov 17 20:38:57 [kernel] usb 1-3: new high speed USB device using ehci_hcd and address 7
	Nov 17 20:38:57 [kernel] usb 1-3: device descriptor read/all, error -71
	Nov 17 20:38:57 [kernel] usb 1-3: new high speed USB device using ehci_hcd and address 8
	Nov 17 20:38:57 [kernel] usb 1-3: string descriptor 0 read error: -71


(Maybe I should stop using computers. MS is not an option...<SIGH>)

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



^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-17 20:49                   ` Jorge Almeida
@ 2005-11-17 21:11                     ` Richard Fish
  2005-11-17 22:04                       ` Jorge Almeida
  2005-11-18  7:03                       ` Dirk Heinrichs
  0 siblings, 2 replies; 32+ messages in thread
From: Richard Fish @ 2005-11-17 21:11 UTC (permalink / raw
  To: gentoo-user

On 11/17/05, Jorge Almeida <jalmeida@math.ist.utl.pt> wrote:
> On Thu, 17 Nov 2005, Richard Fish wrote:
> > important.  If you have USB and the other drivers built as modules,
> > reload them and try again.  If they are built into your kernel,
> > reboot.
> >
> This is Chaos.
>
> On reboot, /dev/external_hd and /dev/external_hd1 exist. I mounted the
> disk with no problems. /dev/plextor_memstick and /dev/plextor_memstick1
> don't exist (or rather they appear as broken links).

Hmm, do you RC_DEVICE_TARBALL set in /etc/conf.d/rc?  That would cause
something like this, and I recommend setting it to "no" for a pure
udev setup.

> Understandable,
> since the stick is not plugged. I plugged it and still no nodes.  I
> unmounted the external disk and /dev/external_hd /dev/external_hd1 are
> gone! And /dev/plextor_memstick & /dev/plextor_memstick1 didn't came
> back.

Your USB bus is really not working right!  Are these devices connected
directly to ports on the PC, or going through a hub?  If there is a
hub, maybe it is broken...

-Richard

-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-17 21:11                     ` Richard Fish
@ 2005-11-17 22:04                       ` Jorge Almeida
  2005-11-17 23:57                         ` Richard Fish
  2005-11-18  7:03                       ` Dirk Heinrichs
  1 sibling, 1 reply; 32+ messages in thread
From: Jorge Almeida @ 2005-11-17 22:04 UTC (permalink / raw
  To: gentoo-user

On Thu, 17 Nov 2005, Richard Fish wrote:
 
> Hmm, do you RC_DEVICE_TARBALL set in /etc/conf.d/rc?  That would cause
> something like this, and I recommend setting it to "no" for a pure
> udev setup.
> 
Yes, it was there since the time it was recommended. I changed it and
rebooted. The memstick nodes are OK (no links) but still no sign of the
external disk. Turning the case switch off and on doesn't bring any
change...
> > Understandable,
> > since the stick is not plugged. I plugged it and still no nodes.  I
> > unmounted the external disk and /dev/external_hd /dev/external_hd1 are
> > gone! And /dev/plextor_memstick & /dev/plextor_memstick1 didn't came
> > back.
> 
> Your USB bus is really not working right!  Are these devices connected
> directly to ports on the PC, or going through a hub?  If there is a
> hub, maybe it is broken...
> 
No hub. I changed the usb port the case is connected to and no change...
I substituted the USB connection by a firewire one. No change...(the
rule starts with BUS=="scsi", so it should be detected).

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



^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-17 22:04                       ` Jorge Almeida
@ 2005-11-17 23:57                         ` Richard Fish
  2005-11-18  8:33                           ` Jorge Almeida
  0 siblings, 1 reply; 32+ messages in thread
From: Richard Fish @ 2005-11-17 23:57 UTC (permalink / raw
  To: gentoo-user

On 11/17/05, Jorge Almeida <jalmeida@math.ist.utl.pt> wrote:
> > Your USB bus is really not working right!  Are these devices connected
> > directly to ports on the PC, or going through a hub?  If there is a
> > hub, maybe it is broken...
> >
> No hub. I changed the usb port the case is connected to and no change...
> I substituted the USB connection by a firewire one. No change...(the
> rule starts with BUS=="scsi", so it should be detected).

I'm not sure what the problem could be then.  Maybe something in your
kernel configuration.  Could you post the output of:

grep "=[ym]" /usr/src/linux/.config

-Richard

-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-17 16:19       ` Jorge Almeida
  2005-11-17 17:11         ` Richard Fish
@ 2005-11-18  6:56         ` Dirk Heinrichs
  2005-11-18  8:36           ` Jorge Almeida
  1 sibling, 1 reply; 32+ messages in thread
From: Dirk Heinrichs @ 2005-11-18  6:56 UTC (permalink / raw
  To: gentoo-user

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

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

> Did it. Upon reboot, I had /dev/external_hd and /dev/external_hd1, but
> only /dev/plextor_memstick (i.e., no mountable /dev/plextor_memstick1).
> I unplugged the stick and turned off the HD case. I plugged back the
> stick. Now /dev/plextor_memstick and /dev/plextor_memstick1 exist, as
> they should. I turned the case on. Well, no /dev/external_hd...

Hmm. Where do you plug in the devices? Into a USB hub, or into the machines 
USB ports directly? If you plug the devices into a hub, and the HD does not 
have an own power supply, the devices may simply not get enough power to 
run troublefree.

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 --]

^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-17 21:11                     ` Richard Fish
  2005-11-17 22:04                       ` Jorge Almeida
@ 2005-11-18  7:03                       ` Dirk Heinrichs
  1 sibling, 0 replies; 32+ messages in thread
From: Dirk Heinrichs @ 2005-11-18  7:03 UTC (permalink / raw
  To: gentoo-user

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

Am Donnerstag, 17. November 2005 22:11 schrieb ext Richard Fish:

> Hmm, do you RC_DEVICE_TARBALL set in /etc/conf.d/rc?  That would cause
> something like this, and I recommend setting it to "no" for a pure
> udev setup.

Then boot into LiveCD, mount your systems root fs (i.e. to /mnt) and delete 
everything in /mnt/dev (except null and console), just to be sure.

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 --]

^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-17 23:57                         ` Richard Fish
@ 2005-11-18  8:33                           ` Jorge Almeida
  0 siblings, 0 replies; 32+ messages in thread
From: Jorge Almeida @ 2005-11-18  8:33 UTC (permalink / raw
  To: gentoo-user

On Thu, 17 Nov 2005, Richard Fish wrote:

> I'm not sure what the problem could be then.  Maybe something in your
> kernel configuration.  Could you post the output of:
> 
> grep "=[ym]" /usr/src/linux/.config
> 
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_LOCK_KERNEL=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_HOTPLUG=y
CONFIG_KOBJECT_UEVENT=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_KALLSYMS=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
CONFIG_KMOD=y
CONFIG_X86_PC=y
CONFIG_MPENTIUM4=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_HPET_TIMER=y
CONFIG_PREEMPT=y
CONFIG_PREEMPT_BKL=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=y
CONFIG_MICROCODE=m
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=y
CONFIG_HIGHMEM4G=y
CONFIG_HIGHMEM=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_HIGHPTE=y
CONFIG_MTRR=y
CONFIG_HAVE_DEC_LOCK=y
CONFIG_SECCOMP=y
CONFIG_HZ_250=y
CONFIG_PM=y
CONFIG_APM=y
CONFIG_APM_RTC_IS_GMT=y
CONFIG_PCI=y
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
CONFIG_ISA_DMA_API=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_MISC=y
CONFIG_NET=y
CONFIG_PACKET=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
CONFIG_IP_FIB_HASH=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_FWMARK=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
CONFIG_NET_IPIP=y
CONFIG_NET_IPGRE=y
CONFIG_SYN_COOKIES=y
CONFIG_INET_TUNNEL=y
CONFIG_IP_TCPDIAG=y
CONFIG_TCP_CONG_BIC=y
CONFIG_NETFILTER=y
CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_TFTP=m
CONFIG_IP_NF_AMANDA=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_IPRANGE=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_PKTTYPE=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_RECENT=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_DSCP=m
CONFIG_IP_NF_MATCH_AH_ESP=m
CONFIG_IP_NF_MATCH_LENGTH=m
CONFIG_IP_NF_MATCH_TCPMSS=m
CONFIG_IP_NF_MATCH_HELPER=m
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_CONNTRACK=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_MATCH_ADDRTYPE=m
CONFIG_IP_NF_MATCH_REALM=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IP_NF_TARGET_TCPMSS=m
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_TARGET_NETMAP=m
CONFIG_IP_NF_TARGET_SAME=m
CONFIG_IP_NF_NAT_FTP=m
CONFIG_IP_NF_NAT_TFTP=m
CONFIG_IP_NF_NAT_AMANDA=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_DSCP=m
CONFIG_IP_NF_TARGET_MARK=m
CONFIG_IP_NF_TARGET_CLASSIFY=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m
CONFIG_LLC=y
CONFIG_ATALK=y
CONFIG_DEV_APPLETALK=y
CONFIG_NET_CLS_ROUTE=y
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=m
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_IDE_GENERIC=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_GENERIC=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_BLK_DEV_PIIX=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_AUTO=y
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y
CONFIG_BLK_DEV_SD=y
CONFIG_SCSI_QLA2XXX=y
CONFIG_IEEE1394=y
CONFIG_IEEE1394_OHCI1394=y
CONFIG_IEEE1394_RAWIO=m
CONFIG_IEEE1394_CMP=m
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
CONFIG_NET_PCI=y
CONFIG_8139TOO=y
CONFIG_R8169=y
CONFIG_INPUT=y
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_EVDEV=m
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=m
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_PCIPS2=y
CONFIG_SERIO_LIBPS2=y
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_CORE=y
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_HW_RANDOM=m
CONFIG_NVRAM=m
CONFIG_RTC=m
CONFIG_GEN_RTC=m
CONFIG_GEN_RTC_X=y
CONFIG_AGP=y
CONFIG_AGP_NVIDIA=y
CONFIG_I2C=m
CONFIG_I2C_CHARDEV=m
CONFIG_I2C_ALGOBIT=m
CONFIG_I2C_ALGOPCF=m
CONFIG_I2C_I801=m
CONFIG_I2C_ISA=m
CONFIG_I2C_SENSOR=m
CONFIG_HWMON=y
CONFIG_SENSORS_ADM1021=m
CONFIG_SENSORS_ASB100=m
CONFIG_SENSORS_DS1621=m
CONFIG_SENSORS_FSCHER=m
CONFIG_SENSORS_GL518SM=m
CONFIG_SENSORS_IT87=m
CONFIG_SENSORS_LM75=m
CONFIG_SENSORS_LM78=m
CONFIG_SENSORS_LM80=m
CONFIG_SENSORS_LM83=m
CONFIG_SENSORS_LM85=m
CONFIG_SENSORS_LM90=m
CONFIG_SENSORS_VIA686A=m
CONFIG_SENSORS_W83781D=m
CONFIG_SENSORS_W83L785TS=m
CONFIG_SENSORS_W83627HF=m
CONFIG_FB=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
CONFIG_FB_SOFT_CURSOR=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_VESA=y
CONFIG_FB_VESA_TNG=y
CONFIG_VIDEO_SELECT=y
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_FB_SPLASH=y
CONFIG_SOUND=y
CONFIG_SND=y
CONFIG_SND_TIMER=y
CONFIG_SND_PCM=y
CONFIG_SND_SEQUENCER=y
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_DUMMY=m
CONFIG_SND_AC97_CODEC=y
CONFIG_SND_INTEL8X0=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB=y
CONFIG_USB_DEVICEFS=y
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_UHCI_HCD=y
CONFIG_USB_STORAGE=y
CONFIG_USB_STORAGE_DEBUG=y
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y
CONFIG_USB_STORAGE_USBAT=y
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y
CONFIG_USB_HID=y
CONFIG_USB_HIDINPUT=y
CONFIG_USB_MON=y
CONFIG_MMC=m
CONFIG_MMC_BLOCK=m
CONFIG_EXT2_FS=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_JBD=y
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
CONFIG_FS_POSIX_ACL=y
CONFIG_INOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=y
CONFIG_UDF_FS=y
CONFIG_UDF_NLS=y
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_NTFS_FS=m
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_RAMFS=y
CONFIG_HFS_FS=y
CONFIG_HFSPLUS_FS=y
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_UTF8=y
CONFIG_PROFILING=y
CONFIG_OPROFILE=y
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_EARLY_PRINTK=y
CONFIG_SECURITY=y
CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_CAPABILITIES=y
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_DES=y
CONFIG_CRYPTO_BLOWFISH=y
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES_586=m
CONFIG_CRYPTO_CAST5=y
CONFIG_CRYPTO_CAST6=y
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_ARC4=y
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_CRC32C=m
CONFIG_CRYPTO_TEST=m
CONFIG_CRC_CCITT=m
CONFIG_CRC32=y
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y

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



^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-18  6:56         ` Dirk Heinrichs
@ 2005-11-18  8:36           ` Jorge Almeida
  0 siblings, 0 replies; 32+ messages in thread
From: Jorge Almeida @ 2005-11-18  8:36 UTC (permalink / raw
  To: gentoo-user

On Fri, 18 Nov 2005, Dirk Heinrichs wrote:

> Am Donnerstag, 17. November 2005 17:19 schrieb ext Jorge Almeida:
> 
> > Did it. Upon reboot, I had /dev/external_hd and /dev/external_hd1, but
> > only /dev/plextor_memstick (i.e., no mountable /dev/plextor_memstick1).
> > I unplugged the stick and turned off the HD case. I plugged back the
> > stick. Now /dev/plextor_memstick and /dev/plextor_memstick1 exist, as
> > they should. I turned the case on. Well, no /dev/external_hd...
> 
> Hmm. Where do you plug in the devices? Into a USB hub, or into the machines 
> USB ports directly? If you plug the devices into a hub, and the HD does not 
> have an own power supply, the devices may simply not get enough power to 
> run troublefree.
> 
Into the ports. The disk case is now connected to a firewire port.
Anyway, the case has its own power supply.

Thanks,

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



^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-17 14:14       ` Jorge Almeida
@ 2005-11-18 10:21         ` Dirk Heinrichs
  2005-11-18 10:29           ` Neil Bothwick
  2005-11-18 10:31           ` Jorge Almeida
  0 siblings, 2 replies; 32+ messages in thread
From: Dirk Heinrichs @ 2005-11-18 10:21 UTC (permalink / raw
  To: gentoo-user

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

Am Donnerstag, 17. November 2005 15:14 schrieb ext Jorge Almeida:

> > 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

This looks like artifacts from an old, static /dev (RC_DEVICE_TARBALL="yes" 
in /etc/conf.d/rc ?). With udev, you should only see sdb and exactly one 
sdbX for each partition on the device, unless your rule contains 
NAME{all_partiotion}="something".

Did you read my former reply to Richards mail about setting 
RC_DEVICE_TARBALL="no" (booting a LiveCD and clean up /dev)?

Otherwise I don't know what else to look at, sorry.

To avoid another reply: Your kernel config also looks good to me.

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 --]

^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  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
  1 sibling, 1 reply; 32+ messages in thread
From: Neil Bothwick @ 2005-11-18 10:29 UTC (permalink / raw
  To: gentoo-user

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

On Fri, 18 Nov 2005 11:21:47 +0100, Dirk Heinrichs wrote:

> Did you read my former reply to Richards mail about setting 
> RC_DEVICE_TARBALL="no" (booting a LiveCD and clean up /dev)?

You don't need to use a live CD for this. Do

mount --bind / /mnt

and the original static /dev/ directory will be available at /mnt/dev.
Remove everything but null and console.


-- 
Neil Bothwick

Work is the curse of the partying class!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-18 10:21         ` Dirk Heinrichs
  2005-11-18 10:29           ` Neil Bothwick
@ 2005-11-18 10:31           ` Jorge Almeida
  2005-11-20  2:21             ` Richard Fish
  1 sibling, 1 reply; 32+ messages in thread
From: Jorge Almeida @ 2005-11-18 10:31 UTC (permalink / raw
  To: gentoo-user

On Fri, 18 Nov 2005, Dirk Heinrichs wrote:
> >
> > $ mount -t vfat /dev/sdb1 /mnt/pen
> > mount: /dev/sdb1: can't read superblock
> 
> This looks like artifacts from an old, static /dev (RC_DEVICE_TARBALL="yes" 
> in /etc/conf.d/rc ?). With udev, you should only see sdb and exactly one 
> sdbX for each partition on the device, unless your rule contains 
> NAME{all_partiotion}="something".
> 
> Did you read my former reply to Richards mail about setting 
> RC_DEVICE_TARBALL="no" (booting a LiveCD and clean up /dev)?
> 
I already set RC_DEVICE_TARBALL="no", following Richards' suggestion. I
didn't boot from a CD and cleaned /dev yet, but I'll give it a try.
Meanwhile, I upgraded the kernel and added a config option (for
firewire) that was missing (for supporting HD's). The nodes
/dev/external_hd and /dev/external_hd1 exist now, but as for the
memstick, only /dev/plextor_memstick (no /dev/plextor_memstick1, meaning
no mounting). Chaos, as I said.
> Otherwise I don't know what else to look at, sorry.
OK, thanks anyway.

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



^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-18 10:29           ` Neil Bothwick
@ 2005-11-18 10:40             ` Dirk Heinrichs
  0 siblings, 0 replies; 32+ messages in thread
From: Dirk Heinrichs @ 2005-11-18 10:40 UTC (permalink / raw
  To: gentoo-user

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

Am Freitag, 18. November 2005 11:29 schrieb ext Neil Bothwick:
> On Fri, 18 Nov 2005 11:21:47 +0100, Dirk Heinrichs wrote:
> > Did you read my former reply to Richards mail about setting
> > RC_DEVICE_TARBALL="no" (booting a LiveCD and clean up /dev)?
>
> You don't need to use a live CD for this. Do
>
> mount --bind / /mnt
>
> and the original static /dev/ directory will be available at /mnt/dev.
> Remove everything but null and console.

Yep, I always forget about the power of bind mounts ;-)

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 --]

^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-18 10:31           ` Jorge Almeida
@ 2005-11-20  2:21             ` Richard Fish
  2005-11-20 11:21               ` Jorge Almeida
  0 siblings, 1 reply; 32+ messages in thread
From: Richard Fish @ 2005-11-20  2:21 UTC (permalink / raw
  To: gentoo-user

On 11/18/05, Jorge Almeida <jalmeida@math.ist.utl.pt> wrote:
> I already set RC_DEVICE_TARBALL="no", following Richards' suggestion. I
> didn't boot from a CD and cleaned /dev yet, but I'll give it a try.
> Meanwhile, I upgraded the kernel and added a config option (for
> firewire) that was missing (for supporting HD's). The nodes
> /dev/external_hd and /dev/external_hd1 exist now, but as for the
> memstick, only /dev/plextor_memstick (no /dev/plextor_memstick1, meaning
> no mounting). Chaos, as I said.

According to the dmesg output you posted earlier, your memory stick is
not partitioned.  This is ok, some are, some are not.  You can confirm
this by taking a look at /proc/partitions when it is inserted, or the
output of "fdisk -l".  So, only getting /dev/plextor_memstick is
probably correct, and you should mount that, not plextor_memstick1.

-Richard

-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-20  2:21             ` Richard Fish
@ 2005-11-20 11:21               ` Jorge Almeida
  2005-11-21 15:18                 ` Richard Fish
  0 siblings, 1 reply; 32+ messages in thread
From: Jorge Almeida @ 2005-11-20 11:21 UTC (permalink / raw
  To: gentoo-user

On Sat, 19 Nov 2005, Richard Fish wrote:
> 
> According to the dmesg output you posted earlier, your memory stick is
> not partitioned.  This is ok, some are, some are not.  You can confirm
> this by taking a look at /proc/partitions when it is inserted, or the
> output of "fdisk -l".  So, only getting /dev/plextor_memstick is
> probably correct, and you should mount that, not plextor_memstick1.
> 
I'm out of office for the weekend, so I can't insert the stick and
confirm. But the stick is partitioned with a unique partition with vfat.
I tried to mount it and mount gave the "no such device" complaint. But I
may be forgetting something.

What about the kernel config? I posted the file as you suggested. Does
it look OK?

Thanks,

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



^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-20 11:21               ` Jorge Almeida
@ 2005-11-21 15:18                 ` Richard Fish
  2005-11-22 11:46                   ` Jorge Almeida
  0 siblings, 1 reply; 32+ messages in thread
From: Richard Fish @ 2005-11-21 15:18 UTC (permalink / raw
  To: gentoo-user

On 11/20/05, Jorge Almeida <jalmeida@math.ist.utl.pt> wrote:
> On Sat, 19 Nov 2005, Richard Fish wrote:
> >
> > According to the dmesg output you posted earlier, your memory stick is
> > not partitioned.  This is ok, some are, some are not.  You can confirm
> > this by taking a look at /proc/partitions when it is inserted, or the
> > output of "fdisk -l".  So, only getting /dev/plextor_memstick is
> > probably correct, and you should mount that, not plextor_memstick1.
> >
> I'm out of office for the weekend, so I can't insert the stick and
> confirm. But the stick is partitioned with a unique partition with vfat.
> I tried to mount it and mount gave the "no such device" complaint. But I
> may be forgetting something.

Earlier you posted:

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

If the key is partitioned, just before the "Attached ..." line, you
should see a listing of the partitions.  For example:

usb-storage: waiting for device to settle before scanning
  Vendor: I-Stick2  Model: IntelligentStick  Rev: 2.00
  Type:   Direct-Access                      ANSI SCSI revision: 02
ready
SCSI device sda: 2047488 512-byte hdwr sectors (1048 MB)
sda: Write Protect is off
sda: Mode Sense: 03 00 00 00
sda: assuming drive cache: write through
SCSI device sda: 2047488 512-byte hdwr sectors (1048 MB)
sda: Write Protect is off
sda: Mode Sense: 03 00 00 00
sda: assuming drive cache: write through
 sda: sda1 sda2
Attached scsi removable disk sda at scsi2, channel 0, id 0, lun 0
usb-storage: device scan complete

So if it really is partitioned, we'll have to figure out why the
kernel is not seeing your partition table.  I would be interested to
see the output of 'fdisk -l /dev/sda' with the stick inserted.

> What about the kernel config? I posted the file as you suggested. Does
> it look OK?

Looks ok to me.

-Richard

-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-21 15:18                 ` Richard Fish
@ 2005-11-22 11:46                   ` Jorge Almeida
  2005-11-23  4:10                     ` Richard Fish
  0 siblings, 1 reply; 32+ messages in thread
From: Jorge Almeida @ 2005-11-22 11:46 UTC (permalink / raw
  To: gentoo-user

On Mon, 21 Nov 2005, Richard Fish wrote:

> 
> So if it really is partitioned, we'll have to figure out why the
> kernel is not seeing your partition table.  I would be interested to
> see the output of 'fdisk -l /dev/sda' with the stick inserted.
> 
No /dev/sda. But there exists /dev/plextor_memstick. However:
	root@jmaa ~ $ fdisk -l plextor_memstick
	~
	root@jmaa ~ $ mount -t auto /dev/plextor_memstick /mnt/pen
	mount: block device /dev/plextor_memstick is write-protected, mounting
	read-only
	mount: you must specify the filesystem type
	~
	root@jmaa ~ $ ls /mnt/pen
	~
	root@jmaa ~ $ umount /mnt/pen
	umount: /mnt/pen: not mounted
	~
	root@jmaa ~ $ fdisk -l plextor_memstick
	~
	root@jmaa ~ $ mount -t vfat /dev/plextor_memstick /mnt/pen
	mount: wrong fs type, bad option, bad superblock on
	/dev/plextor_memstick, missing codepage or other error
	In some cases useful info is found in syslog - try
	dmesg | tail  or so

Well, let's try again. I remove the stick and plug it again. Now there
are both /dev/plextor_memstick and /dev/plextor_memstick1 !

	root@jmaa ~ $ mount /mnt/pen
	~
	root@jmaa ~ $ ls /mnt/pen
	teste  teste~
	root@jmaa ~ $ cat /etc/fstab|grep pen
	/dev/plextor_memstick1          /mnt/pen        vfat noauto,user,noexec,nodev,rw,noatime,conv=auto,uni_xlate,posix   0 0
	root@jmaa ~ $ umount /mnt/pen
	~
	root@jmaa ~ $ fdisk -l /dev/plextor_memstick
	Disk /dev/plextor_memstick: 1050 MB, 1050934784 bytes
	129 heads, 19 sectors/track, 837 cylinders
	Units = cylinders of 2451 * 512 = 1254912 bytes
	
	                Device Boot      Start         End      Blocks   Id  System
	/dev/plextor_memstick1   *           1         838     1026294    e  W95 FAT16 (LBA)
	Partition 1 has different physical/logical endings:
	     phys=(842, 128, 19) logical=(837, 58, 18)

So, there is really a partition. This is the original partitioning. I
didn't change it because I want to keep it vfat, in case I need to use
it on a Mac (or even on a Windows PC, who knows?).

Would it be a good idea to reformat the disk using fdisk? Maybe the
problem lies with crappy windows tools?


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



^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-22 11:46                   ` Jorge Almeida
@ 2005-11-23  4:10                     ` Richard Fish
  2005-11-23  9:32                       ` Jorge Almeida
  0 siblings, 1 reply; 32+ messages in thread
From: Richard Fish @ 2005-11-23  4:10 UTC (permalink / raw
  To: gentoo-user

On 11/22/05, Jorge Almeida <jalmeida@math.ist.utl.pt> wrote:
>         root@jmaa ~ $ fdisk -l /dev/plextor_memstick
>         Disk /dev/plextor_memstick: 1050 MB, 1050934784 bytes
>         129 heads, 19 sectors/track, 837 cylinders
>         Units = cylinders of 2451 * 512 = 1254912 bytes
>
>                         Device Boot      Start         End      Blocks   Id  System
>         /dev/plextor_memstick1   *           1         838     1026294    e  W95 FAT16 (LBA)
>         Partition 1 has different physical/logical endings:
>              phys=(842, 128, 19) logical=(837, 58, 18)
>
> So, there is really a partition. This is the original partitioning. I
> didn't change it because I want to keep it vfat, in case I need to use
> it on a Mac (or even on a Windows PC, who knows?).

Ok, do dmesg and /proc/partitions agree that there is a partition
there?  If not, then the problem is that the kernel is not recognizing
your partition table.  I would suggest:

<insert the key>
dd if=/dev/zero of=/dev/sda bs=512 count=1
<remove then re-insert the key>
fdisk /dev/sdb
<create single partition, type 'b'>
mkfs.vfat -n MYKEY -F 32 /dev/sda1

FAIR WARNING: the above _will_ destroy all data on the key!!

After this, I things should work normally...I hope.

-Richard

-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-23  4:10                     ` Richard Fish
@ 2005-11-23  9:32                       ` Jorge Almeida
  2005-11-23 15:07                         ` Richard Fish
  0 siblings, 1 reply; 32+ messages in thread
From: Jorge Almeida @ 2005-11-23  9:32 UTC (permalink / raw
  To: gentoo-user

On Tue, 22 Nov 2005, Richard Fish wrote:
> 
> Ok, do dmesg and /proc/partitions agree that there is a partition
> there?  If not, then the problem is that the kernel is not recognizing
No...
> your partition table.  I would suggest:
> 
> <insert the key>
> dd if=/dev/zero of=/dev/sda bs=512 count=1
> <remove then re-insert the key>
> fdisk /dev/sdb
> <create single partition, type 'b'>
> mkfs.vfat -n MYKEY -F 32 /dev/sda1
> 
Done it. All well, apparently. But then I remove the key and insert it
again. No joy. (See dmesg). I remove it and insert it again. It works,
this time. This is just totally unreliable. I guess I'll boot from
KNOPPIX, to see whether it may be a kernel problem...

(...)
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x2a R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
Attached scsi removable disk sda at scsi4, channel 0, id 0, lun 0
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (1:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (2:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (3:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (4:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (5:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (6:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (7:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: device scan complete
ieee1394: Current remote IRM is not 1394a-2000 compliant, resetting...
ieee1394: Error parsing configrom for node 0-00:1023
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
ieee1394: Node resumed: ID:BUS[0-00:1023]  GUID[0050770e00071002]
scsi5 : SCSI emulation for IEEE-1394 SBP-2 Devices
ieee1394: sbp2: Logged into SBP-2 device
ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048]
  Vendor: Maxtor 6  Model: L250R0            Rev:     
  Type:   Direct-Access-RBC                  ANSI SCSI revision: 04
SCSI device sdb: 490234752 512-byte hdwr sectors (251000 MB)
sdb: asking for cache data failed
sdb: assuming drive cache: write through
SCSI device sdb: 490234752 512-byte hdwr sectors (251000 MB)
sdb: asking for cache data failed
sdb: assuming drive cache: write through
 sdb: sdb1
Attached scsi disk sdb at scsi5, channel 0, id 0, lun 0

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

^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-23  9:32                       ` Jorge Almeida
@ 2005-11-23 15:07                         ` Richard Fish
  2005-11-23 21:13                           ` Jorge Almeida
  0 siblings, 1 reply; 32+ messages in thread
From: Richard Fish @ 2005-11-23 15:07 UTC (permalink / raw
  To: gentoo-user

On 11/23/05, Jorge Almeida <jalmeida@math.ist.utl.pt> wrote:
> this time. This is just totally unreliable. I guess I'll boot from
> KNOPPIX, to see whether it may be a kernel problem...

Yes, do that.  And if it works I guess you will need to start
comparing the Knoppix kernel configuration to yours.  Maybe your
hardware requires ACPI and/or IO-APIC support to function
correctly...I don't know.

-Richard

-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 32+ messages in thread

* Re: [gentoo-user] confused udev?
  2005-11-23 15:07                         ` Richard Fish
@ 2005-11-23 21:13                           ` Jorge Almeida
  0 siblings, 0 replies; 32+ messages in thread
From: Jorge Almeida @ 2005-11-23 21:13 UTC (permalink / raw
  To: gentoo-user

On Wed, 23 Nov 2005, Richard Fish wrote:

> On 11/23/05, Jorge Almeida <jalmeida@math.ist.utl.pt> wrote:
> > this time. This is just totally unreliable. I guess I'll boot from
> > KNOPPIX, to see whether it may be a kernel problem...
> 
> Yes, do that.  And if it works I guess you will need to start
> comparing the Knoppix kernel configuration to yours.  Maybe your
> hardware requires ACPI and/or IO-APIC support to function
> correctly...I don't know.
> 
ACPI didn't seem to change anything. But I did reformat the key with
fdisk, making a new empty DOS partition table and then making a
partition and fs following your instructions. It seems to be OK now---at
least  both devices are recognized when I insert the key (meaning: no
need to insert it twice). Maybe the problem was with the original
partition table (and zeroing the first block didn't fix it...).

Thank you for all your support.

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



^ permalink raw reply	[flat|nested] 32+ messages in thread

end of thread, other threads:[~2005-11-23 21:23 UTC | newest]

Thread overview: 32+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox