Bug 131503 - Wireless network fails to start on boot
Summary: Wireless network fails to start on boot
Status: VERIFIED FIXED
: 131504 (view as bug list)
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Network (show other bugs)
Version: Final
Hardware: i686 SuSE Linux 10.0
: P5 - None : Normal
Target Milestone: ---
Assignee: Joachim Gleissner
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-30 07:33 UTC by o-Dzin Tridral
Modified: 2007-06-05 10:05 UTC (History)
0 users

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


Attachments
Discussion on the Suse mailing list (28.34 KB, text/plain)
2005-11-02 11:32 UTC, o-Dzin Tridral
Details

Note You need to log in before you can comment on or make changes to this bug.
Description o-Dzin Tridral 2005-10-30 07:33:39 UTC
Wireless network fails to start on boot - needs to be restarted manually after booting.

Workaround: Disable WEP key, then wireless network starts at boot time.

I would like to be able to re-enable WEP key

This has been discussed at some length on the suse-linux-e and opensuse mailing lists.  I can provide details taken from those discussions if required.
Comment 1 Danny Al-Gaaf 2005-11-02 10:59:16 UTC
*** Bug 131504 has been marked as a duplicate of this bug. ***
Comment 2 Joachim Gleissner 2005-11-02 11:14:36 UTC
I didn't follow the discussion, please provide the details.
Comment 3 o-Dzin Tridral 2005-11-02 11:32:07 UTC
Created attachment 56240 [details]
Discussion on the Suse mailing list

Hope this helps.
Comment 4 Joachim Gleissner 2005-11-02 11:45:38 UTC
Not really, I need /var/log/messages and the ifcfg-file (it's in /etc/sysconfig/network). Could you attach them? You can disguise your encryption key if you want.
Comment 5 o-Dzin Tridral 2005-11-02 13:44:57 UTC
This is the ifcfg file.  I don't have access to the /var/log/messages at the moment.  Are there particular messages i can search for?

BOOTPROTO='dhcp'

BROADCAST=''

IPADDR=''

MTU=''

NAME='Intel PRO/Wireless 2200BG'

NETMASK=''

NETWORK=''

REMOTE_IPADDR=''

STARTMODE='auto'

UNIQUE='JNkJ.gwcg9bJFGV0'

USERCONTROL='yes'

WIRELESS_AP=''

WIRELESS_AUTH_MODE='open'

WIRELESS_BITRATE='auto'

WIRELESS_CA_CERT=''
WIRELESS_CHANNEL=''

WIRELESS_CLIENT_CERT=''

WIRELESS_DEFAULT_KEY='0'

WIRELESS_ESSID='xxxxxxxx'

WIRELESS_FREQUENCY=''

WIRELESS_KEY=''

WIRELESS_KEY_0='xxxxxxxx'

WIRELESS_KEY_1=''

WIRELESS_KEY_2=''

WIRELESS_KEY_3=''

WIRELESS_KEY_LENGTH='128'

WIRELESS_MODE='Managed'

WIRELESS_NICK=''

WIRELESS_NWID=''

WIRELESS_POWER='yes'

IRELESS_WPA_IDENTITY=''

WIRELESS_WPA_PASSWORD=''

WIRELESS_WPA_PSK=''

_nm_name='bus-pci-0000:02:02.0'
Comment 6 Joachim Gleissner 2005-11-02 14:49:50 UTC
I'm interested in potential error messages by ifup. Could you check whether adding PREFER_WPA_SUPPLICANT='no' to your ifcfg-file makes any difference?
Comment 7 o-Dzin Tridral 2005-11-02 14:54:10 UTC
I will check.  It might take a while because I will have to re-enable security on the router then change the setup on Suse, then reboot ... There are three other laptops that use the same router, so I'll have to check this at a time that is convenient to everyone else!

Thanks for looking into this.  I'll get back to you as soon as I can.
Comment 8 Stefan Behlert 2005-11-24 10:48:41 UTC
Anything new here?
Comment 9 o-Dzin Tridral 2005-11-24 11:03:30 UTC
Sorry, I've had no time to test.  There's not been a convenient moment for me to try this out.  I'll get back to you as soon as I can
Comment 10 François Obada Pathirannahalage 2005-12-19 10:36:32 UTC
(In reply to comment #6)
> I'm interested in potential error messages by ifup. Could you check whether
> adding PREFER_WPA_SUPPLICANT='no' to your ifcfg-file makes any difference?
> 

It does make a huge difference as the network startup works again, both when the system is up or in the boot process. Thank you :)

electron:/home/titoxx69 # modprobe -r ipw2200
electron:/home/titoxx69 # modprobe ipw2200
electron:/home/titoxx69 # ifup eth1
    eth1      device: Intel Corporation PRO/Wireless 2200BG (rev 05)
    eth1      configuration: wlan-id-00:0e:35:1c:xx:xx
Starting DHCP Client Daemon on eth1... . IP/Netmask: 192.168.0.2 / 255.255.255.0
Comment 11 Joachim Gleissner 2006-02-09 16:38:49 UTC
Thanks for testing. I've changed the default back to not prefer wpa_supplicant in 10.1.