[opensuse] Trying to bring up wifi
Hi, I just bought a Netgear RangeMax router, and I've been completely unable to connect to it under suse10.2. I set it up under XP (dual-booting from this same laptop after struggling with it for several days using KWiFiManager, iwconfig, etc. ipw3945 (the driver for my laptop's on-board Intel 3945 interface) appears to be running, but iwlist says there's no interface that supports scanning, and iwconfig says there's no interface with wireless extensions. Everything I can find on the web implies that there should be an eth1 (eth0 is the on-board Ethernet interface), but there is no such. I installed KWiFiManager hoping it could help, but all it says is "No Interface" in the titlebar, and "DISABLED" in the status area. If I try to bring up the configuration editor, it asks for the root password, then immediately returns to the main window with no message or error. This same laptop works perfectly when I boot into XP, so I'm obviously not understanding something about setting up under suse. The router is set up as "ad hoc", WPA-PSK (AES). Yast won't allow me to set the passphrase under ad hoc mode; it only accepts it under "managed" mode. Could this be the problem? What could I do to fix it? Can anyone help? John Perry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2007-07-03 at 00:19 -0400, John E. Perry wrote:
Hi,
I just bought a Netgear RangeMax router, and I've been completely unable to connect to it under suse10.2.
I set it up under XP (dual-booting from this same laptop after struggling with it for several days using KWiFiManager, iwconfig, etc.
ipw3945 (the driver for my laptop's on-board Intel 3945 interface) appears to be running, but iwlist says there's no interface that supports scanning, and iwconfig says there's no interface with wireless extensions.
Everything I can find on the web implies that there should be an eth1 (eth0 is the on-board Ethernet interface), but there is no such.
I installed KWiFiManager hoping it could help, but all it says is "No Interface" in the titlebar, and "DISABLED" in the status area. If I try to bring up the configuration editor, it asks for the root password, then immediately returns to the main window with no message or error.
This same laptop works perfectly when I boot into XP, so I'm obviously not understanding something about setting up under suse.
The router is set up as "ad hoc", WPA-PSK (AES). Yast won't allow me to set the passphrase under ad hoc mode; it only accepts it under "managed" mode. Could this be the problem? What could I do to fix it?
Can anyone help?
John Perry
Ok, lets start with the obvious: No eth1 device - so the module (driver) is either not working or the interface is not up. Check that the module is loaded (do all this as su (root user)) (1)
lsmod (this will list the modules loaded, is ipw3945 in there) ps ax (check that ipw3945d in running)
(2) if it is:
ifup eth1
(3) if not: modprobe ipw3945 repeat (1) when successful - do (2) Just this for now. Also check the /var/log/messages log when loading the module, for any errors E-Mail disclaimer: http://www.sunspace.co.za/emaildisclaimer.htm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Thanks, Hans; here are my results. Hans van der Merwe wrote:
Ok, lets start with the obvious:
No eth1 device - so the module (driver) is either not working or the interface is not up. Check that the module is loaded (do all this as su (root user))
(1)
lsmod (this will list the modules loaded, is ipw3945 in there)
ipw3945 191520 0 ieee80211 34632 1 ipw3945 firmware_class 14080 1 ipw3945
ps ax (check that ipw3945d in running)
1908 ? S< 0:00 [ipw3945/0] 1910 ? S< 0:00 [ipw3945/0] 16014 ? S< 0:00 [ipw3945/1] 16015 ? S< 0:00 [ipw3945/1]
(2) if it is:
ifup eth1
Interface eth1 is not available
(3) if not: modprobe ipw3945 repeat (1) when successful - do (2)
Just this for now. Also check the /var/log/messages log when loading the module, for any errors
Jul 3 10:51:54 embelex sudo: john : TTY=pts/5 ; PWD=/home/john ; USER=root ; COMMAND=/sbin/ifup eth1 Jul 3 10:51:54 embelex ifup: Interface eth1 is not available Nothing else in /var/log/messages near this time -- all other messages more than an hour ago. Thanks much! jp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2007-07-03 at 11:03 -0400, John E. Perry wrote:
Thanks, Hans; here are my results.
Hans van der Merwe wrote:
Ok, lets start with the obvious:
No eth1 device - so the module (driver) is either not working or the interface is not up. Check that the module is loaded (do all this as su (root user))
(1)
lsmod (this will list the modules loaded, is ipw3945 in there)
ipw3945 191520 0 ieee80211 34632 1 ipw3945 firmware_class 14080 1 ipw3945
ps ax (check that ipw3945d in running)
1908 ? S< 0:00 [ipw3945/0] 1910 ? S< 0:00 [ipw3945/0] 16014 ? S< 0:00 [ipw3945/1] 16015 ? S< 0:00 [ipw3945/1]
Ah, I see no ipw3945d (notice the d) Its the accompanied userspace app that helps the module (will disappear in time). Try running ipw3945d by hand (as root) E-Mail disclaimer: http://www.sunspace.co.za/emaildisclaimer.htm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hans van der Merwe wrote:
Ah, I see no ipw3945d (notice the d) Its the accompanied userspace app that helps the module (will disappear in time). Try running ipw3945d by hand (as root)
1908 ? S< 0:00 [ipw3945/0] 1910 ? S< 0:00 [ipw3945/0] 16014 ? S< 0:00 [ipw3945/1] 16015 ? S< 0:00 [ipw3945/1] 17706 pts/5 S 0:00 /sbin/ipw3945d Now KWiFiManager shows "Interface eth1" in the titlebar, and a laptop with bargraph, but "AccessPoint: N/A" in the status area. I click on Scan for Networks, and get a window with the rows Network Name | Mode | Quality | WEP Grotto | Managed | 79 | on XP sees 6 other nets in range. For my router, above looks ok to me except that WEP is actually WPA, and Mode is actually ad-hoc, though yast forced me to lie and say Managed in order to give a passphrase. The configuration editor button still asks for root password, then returns to the main window with no message or error. *** Repeating your previous procedure: embelex:/home/john # ifup eth1 Network interface is managed from NetworkManager NetworkManager will be advised to set up eth1 but it cannot be assured from here.
From /var/log/messages:
Jul 3 12:19:39 embelex su: (to root) john on /dev/pts/5 Jul 3 12:19:57 embelex kernel: ipw3945: Detected geography ABG (11 802.11bg channels, 13 802.11a channels) Jul 3 12:19:59 embelex ifup: Network interface is managed from NetworkManager Jul 3 12:19:59 embelex ifup: NetworkManager will be advised to set up eth1 Jul 3 12:19:59 embelex ifup: but it cannot be assured from here. Jul 3 12:23:19 embelex syslog-ng[2901]: STATS: dropped 0 Jul 3 12:23:47 embelex sudo: john : TTY=pts/16 ; PWD=/home/john ; USER=root ; COMMAND=/opt/kde3/bin/kdesu_stub - Jul 3 12:23:47 embelex sudo: john : TTY=pts/16 ; PWD=/home/john ; USER=root ; COMMAND=/opt/kde3/bin/kdesu_stub - Jul 3 12:37:40 embelex ifup: Network interface is managed from NetworkManager Jul 3 12:37:40 embelex ifup: NetworkManager will be advised to set up eth1 Jul 3 12:37:40 embelex ifup: but it cannot be assured from here. *** Still, progress. Thanks. jp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John E. Perry wrote:
... Still, progress. Thanks.
Well, after giving up for a while, during which time my laptop suspended itself to disk, I came back intending to keep trying. When I went to restart my ethernet connection (it never reconnects by itself, I always have to tell it to reconnect), there on the KNetworkManager menu were three wireless networks in range, among which was my own Grotto! It asked for the passphrase, which I gave it, and it connected immediately. Strangely enough (according to what I've understood from Google), KWiFiManager still doesn't work. But it seems I don't need it now. The normal network manager did just fine on its own. Hans van der Merwe, thank you so much for your help! I appears ipw3945d was all I needed, although it took several hours and a suspension for the computer to figure out that it was working :-). John Perry (working across my brand-new wireless lan :-). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2007-07-03 at 22:08 -0400, John E. Perry wrote:
John E. Perry wrote:
... Still, progress. Thanks.
Well, after giving up for a while, during which time my laptop suspended itself to disk, I came back intending to keep trying.
When I went to restart my ethernet connection (it never reconnects by itself, I always have to tell it to reconnect), there on the KNetworkManager menu were three wireless networks in range, among which was my own Grotto! It asked for the passphrase, which I gave it, and it connected immediately.
Strangely enough (according to what I've understood from Google), KWiFiManager still doesn't work. But it seems I don't need it now. The normal network manager did just fine on its own.
Hans van der Merwe, thank you so much for your help! I appears ipw3945d was all I needed, although it took several hours and a suspension for the computer to figure out that it was working :-).
John Perry (working across my brand-new wireless lan :-).
Great, sorry, missed this post - ignore previous E-Mail disclaimer: http://www.sunspace.co.za/emaildisclaimer.htm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John E. Perry wrote:
... Well, after giving up for a while, during which time my laptop suspended itself to disk, I came back intending to keep trying.
... Strangely enough (according to what I've understood from Google), KWiFiManager still doesn't work. But it seems I don't need it now. The normal network manager did just fine on its own.
I appears ipw3945d was all I needed, although it took several hours and a suspension for the computer to figure out that it was working :-).
After thinking about it some more, it occurs to me that kNetworkManager was already functioning soon after I started ipw3945d. I recall reading in my investigations that only one network manager would function at a time, and I was trying to use KWiFiManager when KNetworkManager was in control. If I'd realized that sooner, and looked at kNetworkManager rather than KWiFiManager, I probably would have had complete success much sooner. jp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2007-07-04 at 08:58 -0400, John E. Perry wrote:
John E. Perry wrote:
... Well, after giving up for a while, during which time my laptop suspended itself to disk, I came back intending to keep trying.
... Strangely enough (according to what I've understood from Google), KWiFiManager still doesn't work. But it seems I don't need it now. The normal network manager did just fine on its own.
I appears ipw3945d was all I needed, although it took several hours and a suspension for the computer to figure out that it was working :-).
After thinking about it some more, it occurs to me that kNetworkManager was already functioning soon after I started ipw3945d. I recall reading in my investigations that only one network manager would function at a time, and I was trying to use KWiFiManager when KNetworkManager was in control.
If I'd realized that sooner, and looked at kNetworkManager rather than KWiFiManager, I probably would have had complete success much sooner.
jp
You must still figure out why ipw3945d is not loaded at startup (or at loading of module?) E-Mail disclaimer: http://www.sunspace.co.za/emaildisclaimer.htm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hans van der Merwe wrote:
If I'd realized that sooner, and looked at kNetworkManager rather than KWiFiManager, I probably would have had complete success much sooner.
You must still figure out why ipw3945d is not loaded at startup (or at loading of module?)
Hm. Not being an experienced systems programmer or administrator, I assumed it was up to me to start it up somewhere in an initialization script. So it should have come up on its own with ipw3945? jp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2007-07-04 at 09:33 -0400, John E. Perry wrote:
Hans van der Merwe wrote:
If I'd realized that sooner, and looked at kNetworkManager rather than KWiFiManager, I probably would have had complete success much sooner.
You must still figure out why ipw3945d is not loaded at startup (or at loading of module?)
Hm. Not being an experienced systems programmer or administrator, I assumed it was up to me to start it up somewhere in an initialization script.
So it should have come up on its own with ipw3945?
jp
Mine comes up automagically when ipw3945 module is loaded.
From the README of ipw3945d, it seems that it must be started after the module is loaded, "by hand" - I will check my system.
3. RUNNING BEFORE DRIVER FULLY LOADED The typical method for lauching the daemon is to spawn it from within the modprobe.conf or udev scripts as soon as the ipw3945 module is loaded. This can cause problems on systems where the module is loaded earlier in the boot process than the device is probed, or where the module load is delayed. To support this model, the daemon supports the '--timeout' parameter which can be used to specify how long the daemon should look for the driver before giving up. The default value is 0, which will exit immediately if the driver is not found. A value of -1 will result in the daemon waiting forever. Any other value specifies the number of seconds to wait. The daemon will poll the system once per second looking for the driver's sysfs entries. Example usage: % ipw3945d --timeout=-1 The above will fork the daemon into the background and then wait forever for the module to load. E-Mail disclaimer: http://www.sunspace.co.za/emaildisclaimer.htm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2007-07-04 at 16:07 +0200, Hans van der Merwe wrote:
On Wed, 2007-07-04 at 09:33 -0400, John E. Perry wrote:
Hans van der Merwe wrote:
If I'd realized that sooner, and looked at kNetworkManager rather than KWiFiManager, I probably would have had complete success much sooner.
You must still figure out why ipw3945d is not loaded at startup (or at loading of module?)
Hm. Not being an experienced systems programmer or administrator, I assumed it was up to me to start it up somewhere in an initialization script.
So it should have come up on its own with ipw3945?
jp
Mine comes up automagically when ipw3945 module is loaded.
From the README of ipw3945d, it seems that it must be started after the module is loaded, "by hand" - I will check my system.
3. RUNNING BEFORE DRIVER FULLY LOADED
The typical method for lauching the daemon is to spawn it from within the modprobe.conf or udev scripts as soon as the ipw3945 module is loaded. This can cause problems on systems where the module is loaded earlier in the boot process than the device is probed, or where the module load is delayed.
To support this model, the daemon supports the '--timeout' parameter which can be used to specify how long the daemon should look for the driver before giving up. The default value is 0, which will exit immediately if the driver is not found.
A value of -1 will result in the daemon waiting forever. Any other value specifies the number of seconds to wait. The daemon will poll the system once per second looking for the driver's sysfs entries.
Example usage:
% ipw3945d --timeout=-1
The above will fork the daemon into the background and then wait forever for the module to load.
I checked - I have a file "31-network.rules" in "/etc/udev/rules.d" that adds a rule to execute the script "ipw3945d.sh" in "/lib/udev" when the ipw3945 module is loaded. All very intertwined, but thats how the hotplug system works - so when the ipw3945 hardware is enabled the module is loaded and the script is started. So just check for these file on your system. Good luck Hans E-Mail disclaimer: http://www.sunspace.co.za/emaildisclaimer.htm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 07/04/2007 09:33 AM somebody named John E. Perry wrote:
Hans van der Merwe wrote:
If I'd realized that sooner, and looked at kNetworkManager rather than KWiFiManager, I probably would have had complete success much sooner.
You must still figure out why ipw3945d is not loaded at startup (or at loading of module?)
Hm. Not being an experienced systems programmer or administrator, I assumed it was up to me to start it up somewhere in an initialization script.
So it should have come up on its own with ipw3945?
jp
Have a look at /sbin/ifup... that's where it should happen. And, if I recall, that's where an error you mentioned comes from. -- Abstinence-Only sex education is a little like Just-Hold-It potty training. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2007-07-04 at 10:16 -0400, ken wrote:
On 07/04/2007 09:33 AM somebody named John E. Perry wrote:
Hans van der Merwe wrote:
If I'd realized that sooner, and looked at kNetworkManager rather than KWiFiManager, I probably would have had complete success much sooner.
You must still figure out why ipw3945d is not loaded at startup (or at loading of module?)
Hm. Not being an experienced systems programmer or administrator, I assumed it was up to me to start it up somewhere in an initialization script.
So it should have come up on its own with ipw3945?
jp
Have a look at /sbin/ifup... that's where it should happen. And, if I recall, that's where an error you mentioned comes from.
My understanding (which is very limited) is that the ifup stuff is higher up in the chain these days. With hotplug devices there are a whole new system for loading and unloading modules. It can still be done (forced) with "if" scripts if necessary. E-Mail disclaimer: http://www.sunspace.co.za/emaildisclaimer.htm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2007-07-03 at 12:52 -0400, John E. Perry wrote:
Hans van der Merwe wrote:
Ah, I see no ipw3945d (notice the d) Its the accompanied userspace app that helps the module (will disappear in time). Try running ipw3945d by hand (as root)
1908 ? S< 0:00 [ipw3945/0] 1910 ? S< 0:00 [ipw3945/0] 16014 ? S< 0:00 [ipw3945/1] 16015 ? S< 0:00 [ipw3945/1] 17706 pts/5 S 0:00 /sbin/ipw3945d
Now KWiFiManager shows "Interface eth1" in the titlebar, and a laptop with bargraph, but "AccessPoint: N/A" in the status area. I click on Scan for Networks, and get a window with the rows
Network Name | Mode | Quality | WEP Grotto | Managed | 79 | on
XP sees 6 other nets in range. For my router, above looks ok to me except that WEP is actually WPA, and Mode is actually ad-hoc, though yast forced me to lie and say Managed in order to give a passphrase.
Ok, so eth1 is up (ignore the ifup stuff, Networkmanger manages that) - halfway there. If I am not mistaken NetworkManager does not do Ad-Hoc - anyone else have some input? E-Mail disclaimer: http://www.sunspace.co.za/emaildisclaimer.htm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Hans van der Merwe -
John E. Perry -
ken