lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Sat, 4 Jan 2014 19:54:01 -0800
From:	Greg KH <>
To:	Herbert Rosmanith <>
Subject: Re: 3.11.10: rtl8192cu device name, kernel crash

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

> 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
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists