Wireless connection prolem on my Medion MD41300 laptop with internal Intersil ISL3890 PrismGT/PrismDuette Wireless PCI card.
In Suse 9.2 and 9.3 wireless worked correctly. Wired or Wireless choosen via Profiles set up in Profile Management. I have know installed Suse Linux 10.0, configured in the same way the network cards with module prim54 and set up the Profile management but the wireless card is not working. After I have selected profile Wireless the command Iwconfig shows that eth2 is the only wireless device. (IEEE 802.11b/g, Mode:Managed, Frequency 20452 GHz, Access Point 00.00.00.00.00.00) The command if config shows eth2 with proper hw address, IP address and also lo the loopback. The command ifdown eth2 shows device: Intersil Corporation Intersil ISL3890 [PrismGT/PrismDuette], Configuration: wlan-id-<mac-address-wireless-card> The command ifup eth2 shows again device:... and configuration ... followed by : starting WPA-supplicant WPA_driver_prism54_set_coutermeasure ----- Not yet implemented. I don't know what this means since I use WEP and Not WPA. The only strange thing during network configuration was that I could not select my wireless network card out of the displayed list under hardware details nor was I able to search for it. The system came allways with other cards and modules. Never with my card and module name prism54. What can I do now, besides reinstall 9.3 -- Regards, Frans Leerink
Hi! On Mon, Jan 09, Frans Leerink wrote:
In Suse 9.2 and 9.3 wireless worked correctly. Wired or Wireless choosen via Profiles set up in Profile Management.
I have know installed Suse Linux 10.0, configured in the same way the network cards with module prim54 and set up the Profile management but the wireless card is not working.
After I have selected profile Wireless the command Iwconfig shows that eth2 is the only wireless device. (IEEE 802.11b/g, Mode:Managed, Frequency 20452 GHz, Access Point 00.00.00.00.00.00)
The command if config shows eth2 with proper hw address, IP address and also lo the loopback.
The command ifdown eth2 shows device: Intersil Corporation Intersil ISL3890 [PrismGT/PrismDuette], Configuration: wlan-id-<mac-address-wireless-card>
The command ifup eth2 shows again device:... and configuration ... followed by : starting WPA-supplicant WPA_driver_prism54_set_coutermeasure ----- Not yet implemented.
I don't know what this means since I use WEP and Not WPA.
wpa_supplicant can also handle non-WPA connections. Unfortunatley the prism54 driver has no complete support for wpa_supplicant, so the connection fails. There will be a sysconfig update soon that will fix this issue besides others. You can also work-around the problem by adding PREFER_WPA_SUPPLICANT='no' to /etc/sysconfig/network/ifcfg-wlan-* .
The only strange thing during network configuration was that I could not select my wireless network card out of the displayed list under hardware details nor was I able to search for it. The system came allways with other cards and modules. Never with my card and module name prism54.
Hm. Could you post the output of 'hwinfo --netcard'?
Frans Leerink
cu... -- Joachim Gleißner
On Tuesday 10 January 2006 11:23, Joachim Gleissner wrote:
The command ifdown eth2 shows device: Intersil Corporation Intersil ISL3890 [PrismGT/PrismDuette], Configuration: wlan-id-<mac-address-wireless-card>
The command ifup eth2 shows again device:... and configuration ... followed by : starting WPA-supplicant WPA_driver_prism54_set_coutermeasure ----- Not yet implemented.
I don't know what this means since I use WEP and Not WPA.
wpa_supplicant can also handle non-WPA connections. Unfortunatley the prism54 driver has no complete support for wpa_supplicant, so the connection fails. There will be a sysconfig update soon that will fix this issue besides others. You can also work-around the problem by adding
PREFER_WPA_SUPPLICANT='no'
to /etc/sysconfig/network/ifcfg-wlan-* .
I have done this and after reconfiguring the networkcard in yast my wireless card is working again. Thanks so much.
The only strange thing during network configuration was that I could not select my wireless network card out of the displayed list under hardware details nor was I able to search for it. The system came allways with other cards and modules. Never with my card and module name prism54.
Hm. Could you post the output of 'hwinfo --netcard'?
31: PCI 306.0: 0282 WLAN controller [Created at pci.277] UDI: /org/freedesktop/Hal/devices/pci_1260_3890 Unique ID: mY_N.Z7e7L9Q6ex5 Parent ID: 6NW+.c7JTK_YUBi2 SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:03:06.0 SysFS BusID: 0000:03:06.0 Hardware Class: network Model: "Z-Com XG-600 and clones Wireless Adapter" Vendor: pci 0x1260 "Intersil Corporation" Device: pci 0x3890 "Intersil ISL3890 [Prism GT/Prism Duette]" SubVendor: pci 0x17cf "Z-Com, Inc." SubDevice: pci 0x0014 "Z-Com XG-600 and clones Wireless Adapter" Revision: 0x01 Driver: "prism54" Device File: eth2 Features: WLAN Memory Range: 0xd2004000-0xd2005fff (rw,non-prefetchable) IRQ: 11 (52591 events) HW Address: 00:60:b3:1e:5a:fd WLAN channels: 34 36 38 40 42 44 46 48 52 56 60 64 1 2 3 4 5 6 7 8 9 10 11 12 13 14 WLAN frequencies: 5.17 5.18 5.19 5.2 5.21 5.22 5.23 5.24 5.26 5.28 5.3 5.32 2. 412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 2.48 4 WLAN bitrates: 1 2 5.5 11 6 9 12 18 24 36 48 54 WLAN encryption modes: WEP40 WEP104 WEP256 WLAN authentication modes: open sharedkey Module Alias: "pci:v00001260d00003890sv000017CFsd00000014bc02sc80i00" Driver Info #0: Driver Status: prism54 is active Driver Activation Cmd: "modprobe prism54" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #19 (PCI bridge) I have tried to find the card with intersil ISL3890, intersil, prism54, prismgt and a lot of other names connexant, prism nitro in the seach field since the displayed cards did not give a link for me. I have never seen the name Z-Com XG-600 in relation to my wireless adapter. -- Regards, Frans Leerink
Hi! Am Dienstag, 10. Januar 2006 22:52 schrieb Frans Leerink:
On Tuesday 10 January 2006 11:23, Joachim Gleissner wrote:
wpa_supplicant can also handle non-WPA connections. Unfortunatley the prism54 driver has no complete support for wpa_supplicant, so the connection fails. There will be a sysconfig update soon that will fix this issue besides others. You can also work-around the problem by adding
PREFER_WPA_SUPPLICANT='no'
to /etc/sysconfig/network/ifcfg-wlan-* .
I have done this and after reconfiguring the networkcard in yast my wireless card is working again. Thanks so much.
Same for ipw2200 cards when using WEP. The question is, why these issues were marked as resolved in novell's bugzilla? This was reported well before SuSE 10 final and is impossible to overcome for unexperienced users without help. WLAN is a crucial functionality for every recent notebook and the "fix" would be that easy to introduce. Maybe somebody can enlighten me as to why this issue was not addressed by SuSE and marked as resolved. Sven
participants (3)
-
Frans Leerink -
Joachim Gleissner -
Sven Burmeister