* 3.11.10: rtl8192cu device name, kernel crash
@ 2014-01-05 0:13 Herbert Rosmanith
2014-01-05 3:54 ` Greg KH
0 siblings, 1 reply; 2+ messages in thread
From: Herbert Rosmanith @ 2014-01-05 0:13 UTC (permalink / raw)
To: linux-kernel
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.
Additionally, iwconfig and ifconfig cannot decide upon the device name.
While iwconfig sees "wlp0s29f7u4u4u2", ifconfig is a bit short-sighted and
only sees "wlp0s29f7".
The problem is that none of the two devicenames can be used for configuring it:
# dhclient -d wlp0s29f7
...
SIOCSIFADDR: No such device
wlp0s29f7: ERROR while getting interface flags: No such device
wlp0s29f7: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
and:
# dhclient -d wlp0s29f7u4u4u2
...
Bind socket to interface: No such device
Renaming "wlp0s29f7u4u4u2" back to "wlan1" will make the adapter known to
dhclient/ifconfig (finally udev can do something useful), but not without
crashing the system in between: I added the mac-addr. to the
persistent-net udev-rules, did a /etc/init.d/udev restart,
and removed the adapter from the usb hub. Instantly, the system froze, I had to
push the power button to get it back. This was the 2nd time the system
crashed, the first time on the console: it was some kernel panic. As the system
didn't react anymore, I did not bother to write down the lengthy panic message.
By the way, kernel version is 3.11.10.
As the device is handled by the rtl8192cu module, which is not in the
staging directory, it is considered stable, isn't it?
cheers,
herp
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: 3.11.10: rtl8192cu device name, kernel crash
2014-01-05 0:13 3.11.10: rtl8192cu device name, kernel crash Herbert Rosmanith
@ 2014-01-05 3:54 ` Greg KH
0 siblings, 0 replies; 2+ messages in thread
From: Greg KH @ 2014-01-05 3:54 UTC (permalink / raw)
To: Herbert Rosmanith; +Cc: linux-kernel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-01-05 3:53 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-01-05 0:13 3.11.10: rtl8192cu device name, kernel crash Herbert Rosmanith
2014-01-05 3:54 ` Greg KH
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.