All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Herbert Rosmanith <lkml@wildsau.enemy.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3.11.10: rtl8192cu device name, kernel crash
Date: Sat, 4 Jan 2014 19:54:01 -0800	[thread overview]
Message-ID: <20140105035401.GA11255@kroah.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1401050108340.14069@wildsau.enemy.org>

On Sun, Jan 05, 2014 at 01:13:53AM +0100, Herbert Rosmanith wrote:
> 
> hello list,
> 
> this afternoon I bought a new usb/wlan adapter, which identifies 
> itself as:
> 
>     # lsusb
>     ...
>     Bus 001 Device 017: ID 0bda:8178 Realtek Semiconductor Corp. RTL8192CU 802.11n WLAN Adapter
> 
> the first thing I noticed is that the device name is renamed:
> 
>     [ 4444.688299] systemd-udevd[3090]: renamed network interface wlan1 to wlp0s29f7u4u4u2
> 
> Excellent! I always hated that userfriendly and easy to remember names like "wlan1".
> Finally I have a more sophisticated name, "wlp0s29f7u4u4u2" that strictly follows
> The Tao Of Terribly Silly Device Naming.

Your distro does that, take it up with them.  Usually there's an option
to keep the "old" naming scheme somewhere, it should be documented
somewhere.

> By the way, kernel version is 3.11.10.

Which is pretty old, does 3.12 work better?

> As the device is handled by the rtl8192cu module, which is not in the 
> staging directory, it is considered stable, isn't it?

It might help to cc: the wireless developers about wireless driver
issues to get a better response...

greg k-h

      reply	other threads:[~2014-01-05  3:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-05  0:13 3.11.10: rtl8192cu device name, kernel crash Herbert Rosmanith
2014-01-05  3:54 ` 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=20140105035401.GA11255@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@wildsau.enemy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.