public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-usb@vger.kernel.org
Subject: Re: MT7601U with on-board storage reports incorrect capacity
Date: Fri, 10 Jan 2025 00:44:15 +0200	[thread overview]
Message-ID: <8270ca72-a08e-41dd-8daf-d4e00be3d279@gmail.com> (raw)
In-Reply-To: <c0194169-0406-4450-908f-8537c464d122@rowland.harvard.edu>

On 09/01/2025 21:38, Alan Stern wrote:
> On Thu, Jan 09, 2025 at 08:57:29PM +0200, Bitterblue Smith wrote:
>> On 09/01/2025 17:34, Alan Stern wrote:
>>> On Thu, Jan 09, 2025 at 04:02:58PM +0200, Bitterblue Smith wrote:
>>>> Hi,
>>>>
>>>> I have this wifi device with on-board storage for the Windows driver:
>>>>
>>>> New USB device found, idVendor=148f, idProduct=2878, bcdDevice= 0.01
>>>>
>>>> After switching to wifi mode, we can see it's a MT7601U:
>>>>
>>>> New USB device found, idVendor=148f, idProduct=7601, bcdDevice= 0.00
>>>>
>>>> The problem with this one is that it can't be mounted, nothing happens
>>>> for a long time. I'm testing with kernel 6.12.8-arch1-1 but it's been
>>>> like this for at least two years. 
>>>>
>>>> The problem seems to be that reading from the "end" of the device
>>>> takes 17 seconds. I assume the reason for that is the fake capacity:
> 
>>>> How can this be fixed?
> 
>>> Probably your best approach is to tell usb-storage to ignore the device 
>>> completely.  You can do this with a suitable module parameter for the 
>>> usb-storage driver.  For example, add:
>>>
>>> 	usb-storage.quirks=148f:7601:i
>>>
>>> on the kernel's boot command line (or put a similar entry in an 
>>> /etc/modprobe.d/*.conf file if usb-storage is a loadable kernel module 
>>> on your system).  Of course, then you wouldn't be able to mount the 
>>> device or access the Windows driver files on it, but I imagine you don't 
>>> care about them very much while you're running Linux.
> 
>> Haha, so it's hopeless. Thank you for the detailed explanation.
> 
> Not hopeless at	all.  The module parameter approach really should work,	
> at least to the	extent of getting rid of those annoying	17-second-long 
> waits.
> 
> Alan Stern

But it's fine. usb_modeswitch switches it right away.

      reply	other threads:[~2025-01-09 22:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09 14:02 MT7601U with on-board storage reports incorrect capacity Bitterblue Smith
2025-01-09 15:34 ` Alan Stern
2025-01-09 18:57   ` Bitterblue Smith
2025-01-09 19:38     ` Alan Stern
2025-01-09 22:44       ` Bitterblue Smith [this message]

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=8270ca72-a08e-41dd-8daf-d4e00be3d279@gmail.com \
    --to=rtl8821cerfe2@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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