Bugzilla – Bug 113196
Wireless card settings lost after install
Last modified: 2005-08-27 09:39:41 UTC
I installed beta 3 onto a machine with a D-Link DWL-520 Wireless PCI Adapter and the install correctly identified it and allowed to configure it. After install though all the settings (WEP key, ESSID, etc...) were lost. Re-entering them in YaST brought it right up again so the hardware support is there. I didn't check to see if /etc/sysconfig/network/ifcfg-eth1 was empty before I reset the card in yast, unfortunately. hwinfo output: 19: PCI 0c.0: 0282 WLAN controller [Created at pci.277] UDI: /org/freedesktop/Hal/devices/pci_1260_3873 Unique ID: JNkJ.nI+R8uDdh37 SysFS ID: /devices/pci0000:00/0000:00:0c.0 SysFS BusID: 0000:00:0c.0 Hardware Class: network Model: "D-Link DWL-520 Wireless PCI Adapter" Vendor: pci 0x1260 "Intersil Corporation" Device: pci 0x3873 "Prism 2.5 Wavelan chipset" SubVendor: pci 0x1186 "D-Link System Inc" SubDevice: pci 0x3501 "DWL-520 Wireless PCI Adapter" Revision: 0x01 Driver: "orinoco_pci" Device File: eth1 Features: WLAN Memory Range: 0xee000000-0xee000fff (rw,prefetchable) IRQ: 11 (2526 events) HW Address: 00:05:5d:ee:ed:05 Link detected: yes WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 WLAN bitrates: 1 2 5.5 11 WLAN encryption modes: WEP40 WEP104 WLAN authentication modes: open sharedkey Module Alias: "pci:v00001260d00003873sv00001186sd00003501bc02sc80i00" Driver Info #0: Driver Status: orinoco_pci is active Driver Activation Cmd: "modprobe orinoco_pci" Driver Info #1: Driver Status: hostap_pci is active Driver Activation Cmd: "modprobe hostap_pci" Driver Info #2: Driver Status: prism2_pci is active Driver Activation Cmd: "modprobe prism2_pci" Config Status: cfg=no, avail=yes, need=no, active=unknown
Please provide YaST2 logs, see: http://www.opensuse.org/index.php/Bug_Reporting_FAQ#YaST
Created attachment 47789 [details] Yast logs
According to the logs this is really weird. The network proposal let you configure the wifi card but then failed to write the settings. Apparently the code thought it was back in the proposal dialog but the wifi dialog was still shown. Usually this happens when the programmer obviously mismatches UI::OpenDialog and UI::CloseDialog and then yast is so confused that continuing is impossible. But in this case everything got in sync right at the next step, the online update question. ... Aha, Open/CloseDialog was missing around the wifi setup, that explains it. It will be fixed in yast2-network-2.12.13.