linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev errors for usb modems after kernel upgrade
Date: Wed, 05 Dec 2012 15:19:15 +0000	[thread overview]
Message-ID: <20121205151915.GE2686@kroah.com> (raw)
In-Reply-To: <CALEWwHtrc+6+LoNJYD+WJcpDX90XgzMpmdGYLtZnuuSDVkLJng@mail.gmail.com>

On Wed, Dec 05, 2012 at 01:24:50PM +0200, Deniz Eren wrote:
> Hi;
> 
> After upgrading my kernel from 2.6.18 to 3.5.3. I started to get udev
> errors when I plug in my usb modem device(errors are below). I think
> this is causing my usb_modeswitch not to work properly. Same error
> occurs for usb-storage devices too. Can you provide a solution or what
> is the cause?
> 
> udev version: 095

Try also updating your version of udev, 095 is very old, and matched up
with what 2.6.18 was.  Now that you have a newer kernel, there's no
reason to use such an old udev.

good luck,

greg k-h

      reply	other threads:[~2012-12-05 15:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-05 11:24 udev errors for usb modems after kernel upgrade Deniz Eren
2012-12-05 15:19 ` Greg KH [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=20121205151915.GE2686@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-hotplug@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 read-only IMAP folder(s) and NNTP newsgroup(s).