Wireless Card Needs Yast Start After Each Reboot

This is a new finding of a problem that I reported in a separate posting (http://tinyurl.com/6hvevd).

Main problem:
0) After each start or reboot, my wireless card (D-Link, Airplus DWL-G520, rev-B) doesn't connect to the network

When the problem started:
1) April 12, 2008, after an automated upgrade (forgot the upgrade) was installed

Workaround solution:
1) After each reboot, if the wireless card is configured and setup from (YAST->Network Devices->Network Cards), it connects to the network (This MUST be done after each start or reboot).

System information:
1) OpenSuSE 10.3 (Linux kernel: 2.6.22.17-0.1)
2) Wireless driver: madwifi-0.9.3.3-0.1.i586 (this is the latest from Madwifi)

Steps to reproduce of the problem and its temporary solution:
1) Restart the Linux PC
2) Start Google or Ping to a node in the network, it doesn't connect
3) Open "YAST->Network Devices->Network Cards" under "Overview" tab and select the card (D-Link Airplus....)
4) Click in the "Configure" button below to open the configuration window for that card
5) Under address tab, the radio button "Dynamic Address" is selected, change it to "Statically assigned IP address" and then back to "Dynamic Address" button. (This step is ONLY necessary to have a change before saving the configuration)
6) Click on the "Next" and proceed to "Finish" and save the configuration

After saving the above YAST configuration, the network connection establishes and works fine. But after reboot or restart, the problem reappears.

Please help me to find a solution for this.

Note that, I have done many trials to find the solution but there was no luck yet:
1) Deleted and reinstalled the Madwifi driver
2) Assigned the card interface with a "Static IP address"

First check this: in Yast --> system --> runlevels --> is Network daemon running -- should be

Apart from that:

Try this, might help, might not:
Reboot and it won't start. Open a console and enter su to become root. Then enter ifup ath0. If that works report back and we'll make it permanent.

If it doesn't work try this:
Reboot and it won't start. Open a console and enter su to become root. Then enter modprobe ath_pci. Then eter ifup ath0. If that works report back and we'll make it permanent.

Swerdna

First check this: in Yast --> system --> runlevels --> is Network daemon running -- should be
[/b]

(Thanks for the idea........)
Yes, the daemon is running.

Apart from that:

Try this, might help, might not:
Reboot and it won't start. Open a console and enter su to become root. Then enter ifup ath0. If that works report back and we'll make it permanent.
[/b]

No, it diidn't work. Here is the console output:
/*****
Linux-2000:~ # ifup ath0
ath0 device: Atheros Communications, Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01)
ath0 warning: using NO encryption
DHCP client is already running on ath0
*****/

If it doesn't work try this:
Reboot and it won't start. Open a console and enter su to become root. Then enter modprobe ath_pci. Then eter ifup ath0. If that works report back and we'll make it permanent.
[/b]

Yes, it worked. Here is the console output:
/******
Linux-2000:~ # modprobe ath_pci
(no output here = driver started without any problem)

Linux-2000:~ # ifup ath0
ath0 device: Atheros Communications, Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01)
ath0 warning: using NO encryption
Starting DHCP Client Daemon on ath0... . . . . . IP/Netmask: 192.168.0.105 / 255.255.255.0 ('Linux-2000')
******/

Now I understand that the network configuration is missing these two commands at startup. Which file needs these two lines ?

Probably you need to add ath_pci to MODULES_LOADED_ON_BOOT in the kernel configuration. Either edit /etc/sysconfig/kernel or do it via YaST.

Probably you need to add ath_pci to MODULES_LOADED_ON_BOOT in the kernel configuration. Either edit /etc/sysconfig/kernel or do it via YaST.
[/b]

As suggested, added ath_pci to MODULES_LOADED_ON_BOOT, but no luck.
I must have to manually issue the commands:
1) modprobe ath_pci
and
2) ifup ath0

before the network get connected.
(PLEASE HELP !!!!!!!!!!!,)

As suggested, added ath_pci to MODULES_LOADED_ON_BOOT, but no luck.
I must have to manually issue the commands:
1) modprobe ath_pci
and
2) ifup ath0

before the network get connected.
(PLEASE HELP !!!!!!!!!!!,)
[/b]

There's a boot script at /etc/init.d/boot.local. Edit those two lines into that file. I have to do just like that to get my ndiswrwpper started.

There's a boot script at /etc/init.d/boot.local. Edit those two lines into that file. I have to do just like that to get my ndiswrwpper started.
[/b]

Thanks for the solution. IT WORKS !!!!!
However, (when I issued these two commands from console) I found that the ifup ath0 sometimes doesn't complete properly. But if I repeat modprobe ath_pci couple of times and then issue ifup ath0, it works fine. For that reason, I introduced sleep 5 (5 second delay) after each command in the script as below:

modprobe ath_pci
sleep 5
ifup ath0
sleep 5

I don't know whether these "delay" introduction would cause any problem, but apparently, I don't notice anything unusual after couple of reboots.

Score one for the good guys