Re: Unable to access USB mass storage device with xhci. okay with ehci

2015-04-16 Thread Steve Bangert
On Thu, 2015-04-16 at 13:49 +0200, Hans de Goede wrote: > Hi, > > On 09-04-15 20:30, Steve Bangert wrote: > > On Thu, 2015-04-09 at 16:49 +0200, Hans de Goede wrote: > >> Hi, > >> > >> On 09-04-15 15:27, Steve Bangert wrote: > >>> On Wed, 2015-04-08 at 10:56 -0400, Alan Stern wrote: > On Wed,

Re: Unable to access USB mass storage device with xhci. okay with ehci

2015-04-16 Thread Hans de Goede
Hi, On 09-04-15 20:30, Steve Bangert wrote: On Thu, 2015-04-09 at 16:49 +0200, Hans de Goede wrote: Hi, On 09-04-15 15:27, Steve Bangert wrote: On Wed, 2015-04-08 at 10:56 -0400, Alan Stern wrote: On Wed, 8 Apr 2015, Steve Bangert wrote: What i did was not correct, usb-storage.quirks=174c:

Re: Unable to access USB mass storage device with xhci. okay with ehci

2015-04-09 Thread Alan Stern
On Thu, 9 Apr 2015, Steve Bangert wrote: > > Still, I can imagine the uas-detect.h code setting the > > US_FL_MAX_SECTORS_64 flags bit and then the uas driver calling > > blk_queue_max_hw_sectors() the way we do in > > scsiglue.c:slave_configure(). > > Alan, would this approach create/implement d

Re: Unable to access USB mass storage device with xhci. okay with ehci

2015-04-09 Thread Steve Bangert
On Thu, 2015-04-09 at 11:07 -0400, Alan Stern wrote: > On Thu, 9 Apr 2015, Hans de Goede wrote: > > > > uas.c was patched (see attached), the quirk line was temporarily removed > > > > Thanks for testing this. > > > > > and i now have access to the drive using xhci and uas. usbmon trace is > > >

Re: Unable to access USB mass storage device with xhci. okay with ehci

2015-04-09 Thread Steve Bangert
On Thu, 2015-04-09 at 16:49 +0200, Hans de Goede wrote: > Hi, > > On 09-04-15 15:27, Steve Bangert wrote: > > On Wed, 2015-04-08 at 10:56 -0400, Alan Stern wrote: > >> On Wed, 8 Apr 2015, Steve Bangert wrote: > >> > >>> What i did was not correct, usb-storage.quirks=174c:55aa:u was added to > >>>

Re: Unable to access USB mass storage device with xhci. okay with ehci

2015-04-09 Thread Alan Stern
On Thu, 9 Apr 2015, Hans de Goede wrote: > > uas.c was patched (see attached), the quirk line was temporarily removed > > Thanks for testing this. > > > and i now have access to the drive using xhci and uas. usbmon trace is > > attached. > > What exactly do you mean with "i now have access to t

Re: Unable to access USB mass storage device with xhci. okay with ehci

2015-04-09 Thread Hans de Goede
Hi, On 09-04-15 15:27, Steve Bangert wrote: On Wed, 2015-04-08 at 10:56 -0400, Alan Stern wrote: On Wed, 8 Apr 2015, Steve Bangert wrote: What i did was not correct, usb-storage.quirks=174c:55aa:u was added to /etc/default/grub file after GRUB_CMDLINE_LINUX="rhgb quiet", using the grub-config

Re: Unable to access USB mass storage device with xhci. okay with ehci

2015-04-08 Thread Alan Stern
On Wed, 8 Apr 2015, Steve Bangert wrote: > What i did was not correct, usb-storage.quirks=174c:55aa:u was added to > /etc/default/grub file after GRUB_CMDLINE_LINUX="rhgb quiet", using > the grub-configurator tool > followed by a reboot and i now have a working usb storage device > using xhci. Her

Re: Unable to access USB mass storage device with xhci. okay with ehci

2015-04-06 Thread Alan Stern
On Sun, 5 Apr 2015, Steve Bangert wrote: > > To do this, you need to set the usb-storage "quirks" module parameter > > to "174c:55aa:u". The 'u' quirk means to ignore the possibility of > > using UAS. > > > Here's dmesg using the kernel command line you provided: > > I can provide the full dme

Re: Unable to access USB mass storage device with xhci. okay with ehci

2015-04-05 Thread Steve Bangert
On Sun, 2015-04-05 at 10:31 -0400, Alan Stern wrote: > On Sun, 5 Apr 2015, Steve Bangert wrote: > > > On Sat, 2015-04-04 at 15:48 -0400, Alan Stern wrote: > > > > > > > > Is that really all? Was there a "UAS is blacklisted for this device" > > > line in the kernel log? It looks like the usb-

Re: Unable to access USB mass storage device with xhci. okay with ehci

2015-04-05 Thread Alan Stern
On Sun, 5 Apr 2015, Steve Bangert wrote: > On Sat, 2015-04-04 at 15:48 -0400, Alan Stern wrote: > > > > > Is that really all? Was there a "UAS is blacklisted for this device" > > line in the kernel log? It looks like the usb-storage driver didn't do > > anything at all with the device. > >

Re: Unable to access USB mass storage device with xhci. okay with ehci

2015-04-05 Thread Steve Bangert
On Sat, 2015-04-04 at 15:48 -0400, Alan Stern wrote: > > Is that really all? Was there a "UAS is blacklisted for this device" > line in the kernel log? It looks like the usb-storage driver didn't do > anything at all with the device. Yes that's it. Using xhci at super speed, blacklisting uas

Re: Unable to access USB mass storage device with xhci. okay with ehci

2015-04-04 Thread Alan Stern
On Fri, 3 Apr 2015, Steve Bangert wrote: > On Fri, 2015-04-03 at 09:59 -0400, Alan Stern wrote: > > On Fri, 3 Apr 2015, Steve Bangert wrote: > > > > > Alan or Mathias, > > > > > > Machine is a 64 bit Dell Inspiron with Intel chips running Fedora 3.19.3 > > > kernel > > > > > > Disabling the u

Re: Unable to access USB mass storage device with xhci. okay with ehci

2015-04-03 Thread Alan Stern
On Fri, 3 Apr 2015, Steve Bangert wrote: > Alan or Mathias, > > Machine is a 64 bit Dell Inspiron with Intel chips running Fedora 3.19.3 > kernel > > Disabling the uas driver is no help. Any help is appreciated. Can you post a usbmon trace with uas disabled? And a similar usbmon trace using

Unable to access USB mass storage device with xhci. okay with ehci

2015-04-03 Thread Steve Bangert
Alan or Mathias, Machine is a 64 bit Dell Inspiron with Intel chips running Fedora 3.19.3 kernel Disabling the uas driver is no help. Any help is appreciated. Steve lspci -v 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) (prog-if 30 [XHCI])