Can you try using other USB2.0 mass storage devices on the same port to see if 
they can work? It seems possiblly the ehci hardware issue.  

Thanks
Guoqing

----- ??? -----
?: Ben Middleton <ben at drn.org>
??: ???, 2009 ? 4? 29?, ??0:03
??: Re: [driver-usb] External USB 500GB Lacie disk not recognised
???: driver-usb at opensolaris.org

> Thanks both of you for your swift feedback.
> 
> Prior to editing scsa2usb.conf:
> 
> $ dmesg
> 
> pr 28 13:43:45 duke usba: [ID 912658 kern.info] USB 2.0 device 
> (usb59f,951) operating at hi speed (USB 2.x) on USB 2.0 root hub: 
> storage at 1, scsa2usb1 at bus address 2
> Apr 28 13:43:45 duke usba: [ID 349649 kern.info]        LaCie  Hard 
> Drive USB 152D203380B6
> Apr 28 13:43:45 duke genunix: [ID 936769 kern.info] scsa2usb1 is 
> /pci at 0,0/pci1043,8277 at 1a,7/storage at 1Apr 28 13:43:45 duke genunix: 
> [ID 408114 kern.info] /pci at 0,0/pci1043,8277 at 1a,7/storage at 1 
> (scsa2usb1) online
> Apr 28 13:44:02 duke scsi: [ID 193665 kern.info] sd9 at scsa2usb1: 
> target 0 lun 0
> Apr 28 13:44:02 duke genunix: [ID 936769 kern.info] sd9 is 
> /pci at 0,0/pci1043,8277 at 1a,7/storage at 1/disk at 0,0Apr 28 13:46:39 duke 
> genunix: [ID 408114 kern.info] 
> /pci at 0,0/pci1043,8277 at 1a,7/storage at 1/disk at 0,0 (sd9) online
> 
> Apr 28 15:25:14 duke usba: [ID 912658 kern.info] USB 2.0 device 
> (usb59f,951) operating at hi speed (USB 2.x) on USB 2.0 root hub: 
> storage at 2, scsa2usb0 at bus address 3
> Apr 28 15:25:14 duke usba: [ID 349649 kern.info]        LaCie  Hard 
> Drive USB 152D203380B6
> Apr 28 15:25:14 duke genunix: [ID 936769 kern.info] scsa2usb0 is 
> /pci at 0,0/pci1043,8277 at 1a,7/storage at 2Apr 28 15:25:14 duke genunix: 
> [ID 408114 kern.info] /pci at 0,0/pci1043,8277 at 1a,7/storage at 2 
> (scsa2usb0) online
> Apr 28 15:25:31 duke scsi: [ID 193665 kern.info] sd8 at scsa2usb0: 
> target 0 lun 0
> Apr 28 15:25:31 duke genunix: [ID 936769 kern.info] sd8 is 
> /pci at 0,0/pci1043,8277 at 1a,7/storage at 2/disk at 0,0Apr 28 15:28:09 duke 
> genunix: [ID 408114 kern.info] 
> /pci at 0,0/pci1043,8277 at 1a,7/storage at 2/disk at 0,0 (sd8) online
> 
> 
> 
> After editing scsa2usb to read:
> 
> attribute-override-list = "vid=* reduced-cmd-support=true";
> 
> 
> $ dmesg
> 
> Apr 28 16:48:35 duke usba: [ID 691482 kern.warning] WARNING: 
> /pci at 0,0/pci1043,8277 at 1a,7 (ehci0): Connecting device on port 1 failed
> Apr 28 16:48:48 duke usba: [ID 691482 kern.warning] WARNING: 
> /pci at 0,0/pci1043,8277 at 1a,7 (ehci0): Connecting device on port 2 failed
> 
> 
> And neither disk is listed as connected in cfgadm
> 
> $ cfgadm
> 
> usb3/1                         unknown      disconnected 
> unconfigured ok
> usb3/2                         unknown      disconnected 
> unconfigured ok
> 
> 
> Even more peculiar is that I don't seem to be able to undo this 
> change now. i.e. if I comment out the attribute-override-list 
> setting and reboot, both USB disks are complaining with:
> 
> $ dmesg
> 
> Apr 28 17:02:14 duke usba: [ID 691482 kern.warning] WARNING: 
> /pci at 0,0/pci1043,8277 at 1a,7 (ehci0): Connecting device on port 1 failed
> Apr 28 17:02:17 duke usba: [ID 691482 kern.warning] WARNING: 
> /pci at 0,0/pci1043,8277 at 1a,7 (ehci0): Connecting device on port 2 failed
> 
> Any ideas?
> 
> Ben
> -- 
> This message posted from opensolaris.org
> _______________________________________________
> driver-usb mailing list
> driver-usb at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/driver-usb
>

Reply via email to