[ale] Still can't get wireless to work.

[Geoffrey]

Jim wrote:
> So I tried it again. 

Quick short suggestion to try.  Since you set it up manually in YaST, 
set it up to 'start at boot' rather then 'manually.'  See my explanation 
below regarding this.

If this does not work, repost.  We CAN make this thing work.  We might 
get into some fun with iwconfig and iwpriv, fun tools for sure!

> I installed ndiswrapper and loaded the driver, and ndiswrapper reports:
> 
> Installed ndis drivers:
> bcmwl5  driver present, hardware present
> 
> ndiswrapper -m
> Loads the module.
> 
> iwconfig displays:
> wlan0     IEEE 802.11g  ESSID:"linksys"
>          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:0F:66:2A:BB:7E
>          Bit Rate:54 Mb/s   Tx-Power:25 dBm
>          RTS thr:2347 B   Fragment thr:2346 B
>          Encryption key:off
>          Power Management:off
>          Link Quality:100/100  Signal level:-41 dBm  Noise level:-256 dBm
>          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
> 
> When I go into yast and select "network card" it does not detect the 
> wireless card.  I've tried a number of options to set it up manually but 
> nothing worked.

But was it installed via YaST or source?  SuSE will likely not find the 
driver if you didn't install if via YaST.

You will likely need to configure it manually.

> If I do a /etc/init.d/network restart

>    wlan0     device: Broadcom Corporation: Unknown device 4318 (rev 02)
>    wlan0     No configuration found for wlan0
>              Nevertheless the interface will be shut down.

This is telling you it sees the driver, but the Suse configuration files 
don't exist.


>    wlan0     device: Broadcom Corporation: Unknown device 4318 (rev 02)
>    wlan0     No configuration found for wlan0                       unused

Same as above.

> Setting up service network  .  .  .  .  .  .  .  .  .  .  .  .  .  . done.
> 
> So I went into yast and configured it maually, using wlan0, static-0 and 
> module name of Ndiswrapper.
> 
> ifup wlan0
>    wlan0     device: Broadcom Corporation: Unknown device 4318 (rev 02)
>    wlan0     Startmode is 'manual'

Change Startmode to 'start at boot' and restart networking.
> 
> And now I get this when I restart the network:
> 
>    wlan0     device: Broadcom Corporation: Unknown device 4318 (rev 02)
>    wlan0     Startmode is 'manual'                                  skipped

Because you want to set it to start at boot.  This is confusing.  When 
it's configured to start manually, it won't start with the network 
restart.  If you tell it to start at boot, the network script will 
restart it.


-- 
Until later, Geoffrey