Bugzilla – Bug 141953
Strange configuration with Zydas USB WLAN Adapter
Last modified: 2006-01-27 08:59:26 UTC
I´ve a Fiberline WL 430U network adapter with the Zydas ZD1211 chipset. I downloaded and installed the kernel module successfully. When I plugged in the adapter I was asked if I want to configure the device. I chose yes, but in the list of known network adapters there was no entry for the adapter. So I chose "add" and selected "wireless" and "USB". I went through all the steps and in the end there was a "ethernet adapter" in the list. I´ve also a wlan2 interface and I can use it with KWifiManager. What is strange IMHO is the name of the device in the list (should be "wireless adapter" or similar), the fact that it isn´t detected (it should be there and perhaps ask which kernel module should be used), and the fact that the device is just "wlan-bus-usb". I´ve another device which just works when connected to the USB port where I configured it to be, this one works on every port. So IMHO there´s something wrong with the way (WLAN) devices are detected if there´s no built-in kernel module for them. I´ve attached the YaST2 logs.
Created attachment 62269 [details] YaST2 logs
Please also provide `hwinfo --network'
r098089:/home/michael # hwinfo --network 19: None 00.0: 10701 Ethernet [Created at net.111] UDI: /org/freedesktop/Hal/devices/net_00_02_a5_b8_1b_0f Unique ID: usDW.ndpeucax6V1 Parent ID: rBUF.SPbcKWAadaA SysFS ID: /class/net/eth0 SysFS Device Link: /devices/pci0000:00/0000:00:1e.0/0000:02:08.0 Hardware Class: network interface Model: "Ethernet network interface" Driver: "e100" Device File: eth0 HW Address: 00:02:a5:b8:1b:0f Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #13 (Ethernet controller) 20: None 00.0: 10700 Loopback [Created at net.111] Unique ID: ZsBS.GQNx7L4uPNA SysFS ID: /class/net/lo Hardware Class: network interface Model: "Loopback network interface" Device File: lo Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown 21: None 00.0: 10781 Network Interface [Created at net.111] Unique ID: wl2P.nfEXJulusj6 SysFS ID: /class/net/sit0 Hardware Class: network interface Model: "Network Interface" Device File: sit0 Config Status: cfg=new, avail=yes, need=no, active=unknown 22: None 02.0: 1070a WLAN [Created at net.111] UDI: /org/freedesktop/Hal/devices/net_00_11_f6_7f_70_7d Unique ID: 4vk+.QXn1l67RSa1 Parent ID: FKGF.1HPlSPIKalC SysFS ID: /class/net/wlan2 SysFS Device Link: /devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1:1.0 Hardware Class: network interface Model: "WLAN network interface" Device File: wlan2 HW Address: 00:11:f6:7f:70:7d Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #17 (Unclassified device)
What is the interface name for your Fiberline Wlan Adapter? What does ifup say if you call it with that interface name? Please also provide output of lshal.
The interface name is "wlan2". Even if there´s no wlan0 or wlan1. r098089:/home/michael # ifup wlan2 wlan2 wlan2 configuration: wlan-bus-usb wlan2 warning: using NO encryption DHCP client is already running on wlan2 I attached the output from lshal
Created attachment 62659 [details] Output of lshal
So it works as expected. Read /usr/share/doc/packages/sysconfig/README.Persistent_Interface_Names to learn why your interface name is wlan2. What is your problem? 1) That the device is not detected (and therefore not in the list of network devices in YaST)? 2) The handling of undetected devices in YaST? 3) Other functional problems?
IMHO there are several things which don´t work as expected. The first thing is that YaST2 doesn´t remove the udev rules when I remove a network card in the "network" module. I´ve had 2 old entries for network cards which I don´t use any more in the persistant rules file and so I got "wlan2". IMHO a rule doesn´t make sense when the device is removed. 1 and 2 apply as well (the adapter isn´t shwn in the list)
For 10.0 this won't be fixed. In 10.0 YaST does not deal with udev rules at all. For upcoming releases we could think about that. Martin, feel free to close this as WONTFIX, or make it a 10.1 bug.
Would be nice if you could fix thin in 10.1
Sorry for posing twice I just forgot this. If you transfer it to 10.1 it would be nice to split it into 2 bugs: 1) The udev rules aren´t deleted by YaST 2) The device isn´t shown in the list of network devices even if a kernel module was present
*** Bug 142876 has been marked as a duplicate of this bug. ***
Since this applies IMHO to ther things as well (hardware configurations in /etc/sysconfig) I´ll submit a bug for 10.1 So I think you can close this one.
Transferred to bug 145001.