Am 05.11.2013 16:59, schrieb Larry Finger:
On 11/05/2013 09:54 AM, Stefan Seyfried wrote:
Am 04.11.2013 21:50, schrieb Larry Finger:
If people use NetworkManager, the new names are a problem in only one case that I know about. If the wireless driver fails to register as a wireless device, the new naming system knows they are network devices, concludes that they are ethernet types, and gives them a name of en.... rather than wl... When this happens, NM will not connect to the device.
really? I don't think this is related to the name, the driver is probably just broken? Or did it start to work once you fixed the udev rule to name it "wlan0"?
When a new udev rule was added to name it wlanX, then it started to work.
Ok, I would not have imagined that. In the end it means that there is broken legacy code somewhere in NM that looks for interface names instead of properties... :-( But for users hit by this problem, it is important to have a solution.
I always since years have named my interfaces "cable" and "air" (in order to find buggy software that relies on "ethX" or "wlanX") and have not had a problem with networkmanager and such because of this.
I agree that the root cause is a buggy driver, but those won't be fixed by 13.1 release, which is why I brought up the point here.
Yes, that's surely important to know if someone comes for help with WLAN problems. I personally would not have thought of this as a problem, so it's good to know for debugging issues and possibly helping people. -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org