My config file is named: /etc/system/config/network/ifcfg-wlan-wlan0
Is that normal? Running YaST and going into System/sysconfig Editor the card shows up under Hardware/Network as wlan-wlan0 and clicking on the various variables displays the values that are seen in the file.
When I boot up both KWiFiManager and the KNetworkManager are running with icons in the tray.
I notice that if I have the network working (from doing it manually) and then run KNetworkManager that it kills it.
When the system comes up if I do a iwconfig wlan0 the information that is reported does not match that in the ifcfg-wlan-wlan0 file.
If I do the three iwconfig commands to set the key, mode and ESSID, KWiFiManger still cannot connect to the access point. It comes back with a "invalid WEP key specification". It does however list the ESSID, MAC and channel of the AP. Once again doing a dhclient wlan0 brings everything up hunky dory.
Does the NetworkManager pull info from someplace other than the ifcfg-wlan-wlan0 file?
On 6/2/06, Phil Wright <
[EMAIL PROTECTED]> wrote:
Ah ha! Made some more progress. Found the page for the 9.1 64-bit Suse install and was able to install the correct 64-bit driver.
After doing all the ndiswrapper commands and the modprobe ndiswrapper the NetworkManager tool popped up and noted that it saw my local wireless network which is run off a WRT56G router.
For the life of me though I couldn't figure out how to get NetworkManager to config the wireless info and WEP settings to connect. I ended up falling back to the shell and typing in the commands manually.
I used:iwconfig wlan0 essid ESSID
iwconfig wlan0 mode Managed
iwconfig wlan0 key restricted XXXXXXXX
and then:
dhclient wlan0I then added ndiswrapper to the MODULES_LOADED_ON_BOOT in the sysconfig Editor.
All of these commands came from that first wiki page you referenced.
On reboot however it doesn't seem to be working. Sigh. Back to poking at it.On 6/2/06, Phil Wright < [EMAIL PROTECTED]> wrote:Great info their Mark. Appreciate it.
Unfortunately it didn't quite get me going. I see these lines in the messages log.
Jun 2 18:10:32 presario kernel: ndiswrapper: module not supported by Novell, setting U taint flag.
Jun 2 18:10:32 presario kernel: ndiswrapper version 1.10 loaded (preempt=no,smp=no)
Jun 2 18:10:32 presario loadndisdriver: loadndisdriver: load_driver(361): couldn't load driver bcmwl5
Jun 2 18:10:32 presario kernel: ndiswrapper (check_nt_hdr:149): Windows driver is not 64-bit; bad magic: 010B
Jun 2 18:10:32 presario kernel: ndiswrapper (load_sys_files:213): couldn't prepare driver 'bcmwl5'
Jun 2 18:10:32 presario kernel: ndiswrapper (load_wrap_driver:111): loadndiswrapper failed (65280); check system log for messages from 'loadndisdriver'
Looks like it is 64-bit issue. I used the .sys file that Windows Device Manager said was being loaded. There were two different .inf files with the difference being an 'a' on the end. I used the one that matched the driver ( bcmwl5.sys & bcmwl5.inf).
Any ideas? I'm way past the limits of my knowledge on Linux devices.
PhilOn 6/2/06, Mark Schlosser < [EMAIL PROTECTED]> wrote:Phil,Using ndiswrapper I've always had great success with my R3000 and wireless. Following the instructions detailed by the ndiswrapper wiki entry on Installation always works for me, and was fairly easy to follow when I was just starting up with Linux as a desktop OS.There is a section on that wiki speaking directly to different distributions. I know the Ubuntu entry on installation works great for my situation, and I'm sure the SUSE one should work great for you (it says it was tested on 10.1, so you should be golden).Hope that helped,Mark
On 6/2/06, Phil Wright < [EMAIL PROTECTED]> wrote:Hello,
Pretty much a linux newbie here. I've installed various Linux distros over the years at various times for web servers, CVS servers and other similar functions but never really tried to use it as a desktop.
So I have an R3000 Presario that I just installed the 10.1 64-bit release of Suse on. Of course the wireless isn't working. Any chance there is a straightforward newbie-level description on how to get it working. The Hardware Information app in the Control Center lists the Broadcom wireless hardware but it doesn't show up under the Network Manager app. I'm guessing that appropriate drivers are missing.
I looked over the archives and saw some mention of getting it to work under older releases with NDIS drivers and lots of kernel voodoo.
Barring an easy way to get the built-in wireless working are there any PCMCIA wireless cards that are likely to be "plug and play"? I would happily make do with a temporary solution until there is an updated release that has builtin support.
Thanks for any info.
Phil
(Apologies if this comes through twice. I hadn't gone all the way through the subscription verification process the first time I sent it and I am guessing it probably went into /dev/null.)
_______________________________________________
LinuxR3000 mailing list
[email protected]
http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000
Wiki at http://prinsig.se/weekee/
--
Mark Schlosser
[EMAIL PROTECTED]
_______________________________________________
LinuxR3000 mailing list
[email protected]
http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000
Wiki at http://prinsig.se/weekee/
_______________________________________________ LinuxR3000 mailing list [email protected] http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000 Wiki at http://prinsig.se/weekee/
