linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Fraser <davidf@sjsoft.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: error with Acrox USB2.0 8in1 CardReader
Date: Wed, 13 Oct 2004 09:47:22 +0000	[thread overview]
Message-ID: <416CF9AA.2050905@sjsoft.com> (raw)
In-Reply-To: <416CF4D8.7010501@sjsoft.com>

David Fraser wrote:

> Hi
>
> I have had problems connecting to my Acrox USB2.0 8in1 CardReader. I 
> am using Fedora Core 3 development builds.
> It fails to connect at all at first, and gives the following log 
> messages:
>
> Oct 13 09:54:39 scir kernel: usb 1-4: new high speed USB device using 
> address 2
> Oct 13 09:54:39 scir kernel: usb 1-4: device not accepting address 2, 
> error -71
> Oct 13 09:54:39 scir kernel: usb 1-4: new high speed USB device using 
> address 3
> Oct 13 09:54:39 scir kernel: usb 1-4: device not accepting address 3, 
> error -71
>
> unless I rmmod ehci_hcd. Then I get the following:
>
> Oct 13 11:15:02 scir kernel: usb 3-2: new full speed USB device using 
> address 3
> Oct 13 11:15:02 scir kernel: scsi0 : SCSI emulation for USB Mass 
> Storage devices
> Oct 13 11:15:07 scir wait_for_sysfs[9070]: error: wait_for_sysfs needs 
> an update to handle the device 
> '/devices/pci0000:00/0000:00:02.1/usb3/3-2/3-2:1.0' properly, please
> report to <linux-hotplug-devel@lists.sourceforge.net 
> <mailto:linux-hotplug-devel@lists.sourceforge.net>>
> Oct 13 11:15:14 scir kernel:   Vendor: SMSC      Model: 223 U 
> HS-CF      Rev: 1.95
> Oct 13 11:15:14 scir kernel:   Type:   
> Direct-Access                     ANSI SCSI revision: 02
> Oct 13 11:15:14 scir scsi.agent[9106]: disk at 
> /devices/pci0000:00/0000:00:02.1/usb3/3-2/3-2:1.0/host0/0:0:0:0
> Oct 13 11:15:50 scir kernel: Attached scsi removable disk sda at 
> scsi0, channel 0, id 0, lun 0
> Oct 13 11:15:50 scir udev: creating device node '/dev/sda'
> Oct 13 11:15:51 scir kernel: Device not ready.  Make sure there is a 
> disc in the drive.
> Oct 13 11:15:51 scir kernel: Device not ready.  Make sure there is a 
> disc in the drive.
>
> So following the instructions I am reporting it here :-)
> There is also a seemingly related discussion here:
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id\x124027
>
> Do I need to provide any more information, or is there an update to 
> hotplug that should fix this?
>
> Regards
> David
>
> PS Am not subscribed to the mailing list so hope this gets through, 
> will check the archives in case am not cc'd on reply.
>
After reading the archives, I thought this might be helpful:
[root@scir ~]# ls -l /sys/devices/pci0000:00/0000:00:02.1/usb3/3-2/3-2:1.0
total 0
-r--r--r--  1 root root 4096 Oct 13 11:15 bAlternateSetting
-r--r--r--  1 root root 4096 Oct 13 11:15 bInterfaceClass
-r--r--r--  1 root root 4096 Oct 13 11:15 bInterfaceNumber
-r--r--r--  1 root root 4096 Oct 13 11:15 bInterfaceProtocol
-r--r--r--  1 root root 4096 Oct 13 11:15 bInterfaceSubClass
-r--r--r--  1 root root 4096 Oct 13 11:15 bNumEndpoints
-rw-r--r--  1 root root 4096 Oct 13 11:15 detach_state
drwxr-xr-x  4 root root    0 Oct 13 11:15 host0
-r--r--r--  1 root root 4096 Oct 13 11:15 iInterface
drwxr-xr-x  2 root root    0 Oct 13 11:15 power

[root@scir ~]# tree /sys/devices/pci0000:00/0000:00:02.1/usb3/3-2/
/sys/devices/pci0000:00/0000:00:02.1/usb3/3-2/
|-- 3-2:1.0
|   |-- bAlternateSetting
|   |-- bInterfaceClass
|   |-- bInterfaceNumber
|   |-- bInterfaceProtocol
|   |-- bInterfaceSubClass
|   |-- bNumEndpoints
|   |-- detach_state
|   |-- host0
|   |   |-- 0:0:0:0
|   |   |   |-- block -> ../../../../../../../../block/sda
|   |   |   |-- delete
|   |   |   |-- detach_state
|   |   |   |-- device_blocked
|   |   |   |-- max_sectors
|   |   |   |-- model
|   |   |   |-- power
|   |   |   |   `-- state
|   |   |   |-- queue_depth
|   |   |   |-- rescan
|   |   |   |-- rev
|   |   |   |-- scsi_level
|   |   |   |-- state
|   |   |   |-- timeout
|   |   |   |-- type
|   |   |   `-- vendor
|   |   |-- detach_state
|   |   `-- power
|   |       `-- state
|   |-- iInterface
|   `-- power
|       `-- state
|-- bConfigurationValue
|-- bDeviceClass
|-- bDeviceProtocol
|-- bDeviceSubClass
|-- bMaxPower
|-- bNumConfigurations
|-- bNumInterfaces
|-- bcdDevice
|-- bmAttributes
|-- detach_state
|-- devnum
|-- idProduct
|-- idVendor
|-- manufacturer
|-- maxchild
|-- power
|   `-- state
|-- product
|-- serial
|-- speed
`-- version



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  reply	other threads:[~2004-10-13  9:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-13  9:26 error with Acrox USB2.0 8in1 CardReader David Fraser
2004-10-13  9:47 ` David Fraser [this message]
2004-10-13 15:14 ` David Brownell
2004-10-13 20:37 ` David Fraser
2004-10-14  5:39 ` David Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=416CF9AA.2050905@sjsoft.com \
    --to=davidf@sjsoft.com \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).