Bug 115138 - Samsung wlan pcmcia card must be configured again and again
Summary: Samsung wlan pcmcia card must be configured again and again
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Network (show other bugs)
Version: Beta 4
Hardware: i386 Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Joachim Gleissner
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-03 14:45 UTC by Olli Lehto
Modified: 2006-02-09 16:54 UTC (History)
0 users

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
/var/log/messages (27.91 KB, application/x-gzip)
2005-09-05 09:10 UTC, Olli Lehto
Details
/var/log/YaST2/ directory (308.04 KB, application/x-gzip)
2005-09-05 09:12 UTC, Olli Lehto
Details
rcnetwork status/start responses (1.11 KB, text/plain)
2005-09-05 09:54 UTC, Olli Lehto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Olli Lehto 2005-09-03 14:45:52 UTC
Fujitsu-Siemens Amilo A 7620  laptop.
Installation program recognizes the wlan card and asks values for configuration.
After installation I got a message  that new hardware found (Samsung wlan card).
After configuration ok. But after every booting web browser can't find pages
until the card is configured again.
Comment 1 Joachim Gleissner 2005-09-04 09:30:07 UTC
Are you using netapplet by chance? 
Comment 2 Olli Lehto 2005-09-04 13:07:52 UTC
I don't think so. Web browsing is my only net traffic. I go to
system-yast-network device, where Samsung wlan card seems to be configured - I
choose edit-next-next... After that web browsing goes fine again. But after
booting the same process with yast must be done again. Sounds very much like
layman experience - yes , at the moment I don't think myself very technically
oriented-I just wait evereything goes the usual way as before. This seems to be
the first SuSE version that recognizes the wlan card during installation and
offers the opportunity to configer it as well right away. But the internet
connection test fails. And after installation it appears the wlan configuration
wasn't done at all during installation- the system recognizes the card as new
hardware (even twice, I remember). After booting the configuration seems to be
there (from thw view of yast network device interface (the settings are there as
set (the hex key etc). But you have to run the configuration through to get web
browsing work. The command "dhcpd -d wlan0" didn't work the usual way either, it
got stuck with the first line of messages (don't remember now what it was,
unfortunately). I think the problem may be connected with dhcp, somehow.
Comment 3 Olli Lehto 2005-09-04 13:31:08 UTC
I checked the response to "dhcpcd -d wlan0" when after booting the web browser
doesn't find pages - "dhcpcd: MAC address = 00:02:78:e1:b0:c0" and gets stuck
with this message. 

The following is the yast network card configuration opening dialog:
------------------------------------------------------------------
Network Card Configuration Overview    
  Samsung 11mbps WLAN Card          DHCP
  Fujitsu Siemens VT6102 [Rhine-II] Not configured

Samsung 11Mbps WLAN Card
  Device Name: wlan-id-00:02:78:e1:b0:c0
  IP address assigned using DHCP
  Started automatically at boot
-------------------------------------------------------------------
  I just run through the configuration with next-button and after that
everything seems to be ok again.
Comment 4 Joachim Gleissner 2005-09-05 08:11:37 UTC
Please attach /var/log/messages. 
Comment 5 Olli Lehto 2005-09-05 09:10:51 UTC
Created attachment 48753 [details]
/var/log/messages
Comment 6 Olli Lehto 2005-09-05 09:12:16 UTC
Created attachment 48754 [details]
/var/log/YaST2/ directory
Comment 7 Joachim Gleissner 2005-09-05 09:27:11 UTC
The messages show that you often are disassociated and reassociated, but  
that's another story. Could you please also attach 'rcnetwork status' and 
'rcnetwork start wlan0' output (directly after booting)? 
Comment 8 Olli Lehto 2005-09-05 09:54:18 UTC
Created attachment 48762 [details]
rcnetwork status/start responses
Comment 9 Olli Lehto 2005-09-05 16:55:43 UTC
I'm getting acquainted with the new way SuSE handles wireless connection
configuration... I was guessing that somehow the problem is connected with WEP
encryption. I configured encryption with a 128 WEP key. But when I after booting
looked at Wireless LAN - Dialog (KInternet tool)I saw that it showed "encryption
no". After reconfiguration it showed  "encryption on" and everything worked again.
So, it seems, the encryption information is losen or ignored when the system
boots and dhcp cannot solve the web addresses.

By the way "safe settings" = Failsafe boot choice ?

I tried Failsafe and acpi=off option, but they didn't help.
Comment 10 Joachim Gleissner 2005-11-07 15:16:08 UTC
Do you get a stable connection when avoiding usage of wpa_supplicant? You can configure that by adding PREFER_WPA_SUPPLICANT='no' to /etc/sysconfig/network/ifcfg-wlan-* .
Comment 11 Stefan Behlert 2005-11-24 10:58:26 UTC
Anything new here?
Comment 12 Joachim Gleissner 2006-02-09 16:54:01 UTC
No further information -> closing as invalid. Please reopen in case the problem still exists.