Bugzilla – Bug 116337
wireless lan card doesn't get configured
Last modified: 2006-02-09 16:45:17 UTC
Samsung wireless pcmcia card is detected, but after configuration internet connection doesn't work. With cable no problems with the ethernet card of Fujitsu Siemens Amilo A 7620. Don't know about the configutation files concerned nowadays, but with Yast configuration my wireless internet connection didn't get configured completely. Didn't try pinging absolute addresses but names aren't resolved at all.
Please provide yast2-logs. Does this happen during the installation or afterwards? (please read: http://www.opensuse.org/Bug_Reporting_FAQ#YaST). Also provide more verbose information about yout hardware (lspci, hwinfo). Try to be more verbose either, what exactly did you configure how?
Created attachment 49620 [details] yastlogs
Created attachment 49621 [details] lspci
Created attachment 49622 [details] hwinfo
Samsung 11Mbps WLAN Card was detected during installation and I configured it through the yast dialog. The card's led behaved as if the configuration happened allright. After installation I tried to ping an address but I got the error message "network unreachable". I tried to reconfigure the card with yast but the situation didn't turn any better
Ok, these drivers are detected for the card (y2log-1:813): [$["active":true, "modprobe":true, "modules":[["hostap_cs", ""]]], $["active":false, "modprobe": true, "modules":[["prism2_cs", ""]]], $["active":true, "modprobe":true, "modules":[["orinoco_cs", ""]]]] So hostap_cs and orinoco_cs are loaded, prism2_cs is not. When yast tries to bring the interface up, it says (y2log:1172): 2005-09-10 16:14:17 <1> linux(5518) [YCP] Service.ycp:277 Running service initscript network start 2005-09-10 16:14:17 <3> linux(5518) [bash] ShellCommand.cc(shellcommand):78 [1A ..unusedWEXT auth param 7 value 0x1 - ioctl[SIOCSIWAUTH]: Operation not supported 2005-09-10 16:14:23 <3> linux(5518) [bash] ShellCommand.cc(shellcommand):78 [1Awaiting During the internet test, this was in the kernel log (internet-test/messages): kernel: wifi0: dropped unencrypted TX data frame (drop_unencrypted=1) So Joachim, does this give you an idea what is going on? Olli, I think it would be useful to attach /var/log/messages too.
Created attachment 49718 [details] /var/log/messages var/log/messages attached
It's quite strange that hostap_cs and orinoco_cs are loaded, I would expect only hostap_cs. Martin, does YaST write some module to load into the hwcfg-file or something? Olli, does it help when you add PREFER_WPA_SUPPLICANT='no' to /etc/sysconfig/network/ifcfg-wlan-*?
PREFER_WPA_SUPPLICANT='no' in /etc/sysconfig/network/ifcfg-wlan-* didn't help. I remember in earlier versions all I had to do was to uncomment Samsung card info in a config file (*-ng) in /etc/pcmcia (?) directory and configure with yast. Now, I suppose, the card should be detected automatically (as it seems in the yast configuration dialog) and the card's led behaves as if the card got configured.
No, yast only writes hostap_cs to hwcfg (even that it actually should not do, see bug 116211). I don't know how to help here, Joachim please you try.
I did the following - replaced hostap_cs with prism2_cs at yast hardware dialog for Samsung card. After that KInternet 'current connection' showed there actually seemed to be a wireless connection with ip etc. But Firefox couldn't still find pages. I did the following linux:/home/okl # dhcpcd -d wlan0 **** dhcpcd: already running **** dhcpcd: if not then delete /var/run//dhcpcd-wlan0.pid file linux:/home/okl # rm /var/run/dhcpcd-wlan0.pid linux:/home/okl # dhcpcd -d wlan0 dhcpcd: MAC address = 00:02:78:e1:b0:c0 dhcpcd: your IP address = 81.197.195.33 linux:/home/okl # After that my wireless internet connection worked. This dhcp problem existed often with earlier versions, too. I had to delete dhcpcd-wlan0.pid file and 'dhcpcd -d wlan0'. After that everything worked. A little awkward, though, after every booting.
Do I understand correctly that after booting you get no connection but after restarting dhcpcd it works? Do you have eth0 configured using dhcp as well by chance?
Anything new here?
No further information -> closing as invalid. Please reopen in case the problem still exists.