On Thu, 21 Sep 2017, Kris Lindgren wrote:
> >> > Those Hardware Error messages are annoying, aren't they? Other people
> >> > have complained about them in the past. Would you mind testing a patch
> >> > that should eliminate them?
> >> >
> >> > Alan Stern
> >>
> >> Yes, I can test another patch
On Thu, Sep 21, 2017 at 9:25 AM, Alan Stern wrote:
> On Wed, 20 Sep 2017, Kris Lindgren wrote:
>
>> On Wed, Sep 20, 2017 at 3:00 PM, Alan Stern
>> wrote:
>> > On Wed, 20 Sep 2017, Kris Lindgren wrote:
>> >
>> >> Hi Alan,
>> >>
>> >> Sorry for the delay. This did indeed solve the problem. I reb
On Wed, 20 Sep 2017, Kris Lindgren wrote:
> On Wed, Sep 20, 2017 at 3:00 PM, Alan Stern wrote:
> > On Wed, 20 Sep 2017, Kris Lindgren wrote:
> >
> >> Hi Alan,
> >>
> >> Sorry for the delay. This did indeed solve the problem. I rebuilt
> >> the kernel with that patch applied and without any spec
On Wed, Sep 20, 2017 at 3:00 PM, Alan Stern wrote:
> On Wed, 20 Sep 2017, Kris Lindgren wrote:
>
>> Hi Alan,
>>
>> Sorry for the delay. This did indeed solve the problem. I rebuilt
>> the kernel with that patch applied and without any special quirks
>> loaded against the usb_storage driver, the
On Wed, 20 Sep 2017, Kris Lindgren wrote:
> Hi Alan,
>
> Sorry for the delay. This did indeed solve the problem. I rebuilt
> the kernel with that patch applied and without any special quirks
> loaded against the usb_storage driver, the drive mounts without issue.
>
> dmesg output:
> [ 1343.583
On Mon, Sep 18, 2017 at 1:14 PM, Alan Stern wrote:
> On Mon, 18 Sep 2017, Kris Lindgren wrote:
>
>> So I upgrade to 17.04 which is using the 4.10 kernel.
>>
>> Without any modification the filesystem fails to mount.
>>
>> Unloading the usb_storage module and reloading it with
>> quirks=0bc2:3332:w
On Mon, 18 Sep 2017, Kris Lindgren wrote:
> So I upgrade to 17.04 which is using the 4.10 kernel.
>
> Without any modification the filesystem fails to mount.
>
> Unloading the usb_storage module and reloading it with
> quirks=0bc2:3332:w allows the drive to be succesfully mounted and used
> with
On Mon, Sep 18, 2017 at 11:05 AM, Alan Stern wrote:
> On Mon, 18 Sep 2017, Kris Lindgren wrote:
>
>> >> What happens if you plug the disk drive into a regular Linux desktop
>> >> computer? Remember, if an unusual_uas.h entry is added, it will affect
>> >> those machines too.
>> >
>> > I will need
On Mon, 18 Sep 2017, Kris Lindgren wrote:
> >> What happens if you plug the disk drive into a regular Linux desktop
> >> computer? Remember, if an unusual_uas.h entry is added, it will affect
> >> those machines too.
> >
> > I will need to get back to you on this. All of my other machines
> > ru
On Sun, Sep 17, 2017 at 7:02 PM, Kris Lindgren wrote:
> On Sun, Sep 17, 2017 at 3:41 PM, Alan Stern wrote:
>> Please use Reply-To-All so that your message gets sent to the mailing
>> and not just to me.
>>
>> Also, please don't top-post.
>>
>> On Sun, 17 Sep 2017, Kris Lindgren wrote:
>>
>>> Sorr
On Sun, Sep 17, 2017 at 3:41 PM, Alan Stern wrote:
> Please use Reply-To-All so that your message gets sent to the mailing
> and not just to me.
>
> Also, please don't top-post.
>
> On Sun, 17 Sep 2017, Kris Lindgren wrote:
>
>> Sorry, Let me be more specific and answer your questions.
>>
>> Witho
Please use Reply-To-All so that your message gets sent to the mailing
and not just to me.
Also, please don't top-post.
On Sun, 17 Sep 2017, Kris Lindgren wrote:
> Sorry, Let me be more specific and answer your questions.
>
> Without any changes, I plugin the drive, it will fail with sector 0
>
On Sat, 16 Sep 2017, Kris Lindgren wrote:
> Hello all,
>
> I have a Seagate External HDD PN: 9sean2-500 that works fine on USB2.0
> ports (and older kernels) however when connected to usb3.0 port on
> newer kernels, the drive fails any write access.
This bug report seems to be a little confused.
Hello all,
I have a Seagate External HDD PN: 9sean2-500 that works fine on USB2.0
ports (and older kernels) however when connected to usb3.0 port on
newer kernels, the drive fails any write access.
dmesg
[ 7232.155430] usb 1-1: new high-speed USB device number 3 using xhci_hcd
[ 7232.366548] usb-
Hi David,
On 21-03-16 10:08, David Webb wrote:
I am sorry but the 't' option (i.e. US_FL_NO_ATA_1X) may not be robust enough.
Yesterday after leaving the system running for a few hours the usb disk would
no longer connect.
Today when I restarted the system with the 't' option, again the disk wo
I am sorry but the 't' option (i.e. US_FL_NO_ATA_1X) may not be robust enough.
Yesterday after leaving the system running for a few hours the usb disk would
no longer connect.
Today when I restarted the system with the 't' option, again the disk would
not connect.
I then tried repeatedly disc
I recently purchased a "Seagate 2TB Expansion Desktop Drive" from a UK store.
The unix command 'lsusb -v' shows:
idVendor 0x0bc2 Seagate RSS LLC
idProduct 0x331a
When plugged in this failed to install correctly. The first few lines of the
error messages (journalctl -f )
17 matches
Mail list logo
