Bugzilla – Bug 162750
double network card entry in yast2 (hostap vs prism drivers)
Last modified: 2007-03-13 12:09:16 UTC
After fresh installation of beta9 I setup my internal wlan-card for WEP with ifup (NetworkManager don't work at the moment) After restart my system network doen't work I start yast again and I see double entry of my wlan card (see attachment) The second entry isn't configured.. If i setup this card again.. it works. couriously /etc/sysconfig/network .. -rw------- 1 root root 918 2006-04-01 15:58 ifcfg-wlan-bus-pci-0000:02:02.0 -rw------- 1 root root 918 2006-04-01 15:58 ifcfg-wlan-id-00:20:e0:8f:a0:58 ..
Created attachment 76045 [details] yast network bug
attach /var/log/YaST2/* please
Created attachment 76244 [details] /var/log/YaST2/*
It seems that the card works with module hostap_pci but yast decides to use prism2_pci because it is first in the list :(
btw i can reproduce it with 10.1 RC 1 after install and restart I have 2 entries..
with factory install today (update) I have only one entry for my wlan-card. The prism2_pci is loaded and works with ifup. (NetworkManager don't work here...) Should I use the hostap_pci driver?
also with final 10.1 I have 2 wlan entries
The bug also happens with wired network adapters. I've just installed SUSE Linux 10.1 (final) and I got the exact same issue with a Marvell 88E8001 Gigabit (integrated in a Shuttle SB83G5 motherboard). The 2nd copy of the adapter appeared after the 2nd reboot after a fresh installation (right after the 1st online update). As recommended, I selected everything but the kernel update for this 1st update. In Yast, I had to remove the 1st entry and configure the 2nd one in order to have a network connection again. The problem has not occured anymore since then. Let me know is you need more information.
Reassigning to the new maintainer of yast2-network.
I can't reproduce this problem with fresh install openSUSE Beta 2 at the moment.
sorry.. I can reproduce it now with opensuse beta2
I got it - reproduced in alpha10.3 bugfix will come
fixed in yast2-network-2.15.16 please check it, if you can reproduce it with => version, reopen this bug