linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: linux-modules@vger.kernel.org
Cc: Hans de Goede <hdegoede@redhat.com>
Subject: [solved] Re: uas module not loaded automatically
Date: Mon, 06 Oct 2014 08:39:02 +0200	[thread overview]
Message-ID: <54323906.1050808@web.de> (raw)
In-Reply-To: <5431258D.3020904@web.de>

[-- Attachment #1: Type: text/plain, Size: 654 bytes --]

On 2014-10-05 13:03, Jan Kiszka wrote:
> Hi all,
> 
> I'm migrating this conversation over from LKML as it is probably a kmod
> issue. I've just retried the scenario with kmod 18 (from OpenSUSE
> Factory) and can still confirm it. Please see below for details.

Mystery solved:

/etc/modprobe.d/50-blacklist.conf:
# uas has been confirmed to be hopelessly broken
# Bug bnc#770301
blacklist uas

I'll check with my distro if this is gone in their next release when
they switch to a UAS-enabled kernel. The official kernel for their
current release still has it disabled, the problem only occurred when
moving to a newer kernel.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2014-10-06  6:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <54303DF6.4050203@web.de>
     [not found] ` <54310A74.3090404@redhat.com>
     [not found]   ` <54310C04.5060008@web.de>
     [not found]     ` <54310DF9.8070904@redhat.com>
     [not found]       ` <54310FFF.10504@web.de>
     [not found]         ` <543112A6.8070503@redhat.com>
     [not found]           ` <543113FF.7050900@web.de>
     [not found]             ` <54311549.4070808@redhat.com>
2014-10-05 11:03               ` uas module not loaded automatically Jan Kiszka
2014-10-06  6:39                 ` Jan Kiszka [this message]
2014-10-06 22:43                   ` [solved] " Lucas De Marchi

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=54323906.1050808@web.de \
    --to=jan.kiszka@web.de \
    --cc=hdegoede@redhat.com \
    --cc=linux-modules@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).