[opensuse] Intel 3945 Wireless Problem opensuse 10.3
One problem down, one to go. I can't seem to connect to my (or any other) wifi network with my laptop. I have an Intel 3945 ABG card in my laptop. It is loaded with the ipw3945d Regulatory Daemon, ipw3945-kmp-default, ipw-firmware, the iwl3945-ucode and iwlifi-kmp-default files in YaST. I have network setup to be user controlled using KNetworkmanager. Though previously hidden, I have my SSID open with no password. I can see my network but cannot connect. The KNetworkmanager progress bar gets to 28% then quits. I also tried this on a few of my neighbors' open wifi networks and I can't get to them either. On a previous attempt to setup 10.3 on this laptop, I was intermittently able to get on the wifi. 10.2 had no issues. I've googled but not found much to help out. Ideas? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Kai Ponte wrote:
One problem down, one to go.
I can't seem to connect to my (or any other) wifi network with my laptop.
I have an Intel 3945 ABG card in my laptop. It is loaded with the ipw3945d Regulatory Daemon, ipw3945-kmp-default, ipw-firmware, the iwl3945-ucode and iwlifi-kmp-default files in YaST.
I have network setup to be user controlled using KNetworkmanager. Though previously hidden, I have my SSID open with no password.
I can see my network but cannot connect. The KNetworkmanager progress bar gets to 28% then quits.
I also tried this on a few of my neighbors' open wifi networks and I can't get to them either.
On a previous attempt to setup 10.3 on this laptop, I was intermittently able to get on the wifi. 10.2 had no issues.
I've googled but not found much to help out.
Kai, KNetworkmanager has some "issues," to put it mildly. Try this. Delete the card in Yast, choose "finish," and go back into the Yast option for network devices. Redefine the card, but DON'T choose KNetworkmanager. Define the card with your ID etc. for your router there. See if that works. Fred -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 07 February 2008 09:18:29 pm Fred A. Miller wrote:
I've googled but not found much to help out.
Kai, KNetworkmanager has some "issues," to put it mildly. Try this. Delete the card in Yast, choose "finish," and go back into the Yast option for network devices. Redefine the card, but DON'T choose KNetworkmanager. Define the card with your ID etc. for your router there. See if that works.
LOL! Apparently that - and a few reboots - has worked. I wonder what they - um - fixed for 10.3. KNetworkmanager has not given me any issues in 9.2 through 10.2. I hope it is louder for version 11. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Kai Ponte wrote:
On Thursday 07 February 2008 09:18:29 pm Fred A. Miller wrote:
I've googled but not found much to help out. Kai, KNetworkmanager has some "issues," to put it mildly. Try this. Delete the card in Yast, choose "finish," and go back into the Yast option for network devices. Redefine the card, but DON'T choose KNetworkmanager. Define the card with your ID etc. for your router there. See if that works.
LOL!
Apparently that - and a few reboots - has worked.
GOOD! At least you can now get online.
I wonder what they - um - fixed for 10.3. KNetworkmanager has not given me any issues in 9.2 through 10.2.
I hope it is louder for version 11.
I don't know what happened. One thing that KNetworkmanger SHOULD do, without question, is to be able to see the MAC address of hidden access points, just like XP and Vista do. Maybe it's in the stack that Knetworkmanager accesses, I don't know, but there are problems. Fred -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 08 February 2008 03:01:47 pm Fred A. Miller wrote:
Kai Ponte wrote:
On Thursday 07 February 2008 09:18:29 pm Fred A. Miller wrote:
I've googled but not found much to help out.
Kai, KNetworkmanager has some "issues," to put it mildly. Try this. Delete the card in Yast, choose "finish," and go back into the Yast option for network devices. Redefine the card, but DON'T choose KNetworkmanager. Define the card with your ID etc. for your router there. See if that works.
LOL!
Apparently that - and a few reboots - has worked.
GOOD! At least you can now get online.
I wonder what they - um - fixed for 10.3. KNetworkmanager has not given me any issues in 9.2 through 10.2.
I hope it is louder for version 11.
I don't know what happened. One thing that KNetworkmanger SHOULD do, without question, is to be able to see the MAC address of hidden access points, just like XP and Vista do. Maybe it's in the stack that Knetworkmanager accesses, I don't know, but there are problems.
I was thinking of contacting the KDE developers on this. Sure enough, I rebooted my workstation this morning and it did not auto-connect to my SSID. (I had it on all night downloading then seeding the openSUSE 11.0 Alpha torrent on KTorrent.) Of course, I have absolutely no issues with wired connections. This is odd, since my laptop comes with a broadcom ethernet card, and I'd read about problems with that over the years. In fact, when I ordered the laptop, I made sure it came with a Intel wifi chip. Oh, on a related note - I tried this last night at home. I fired up VMWare and loaded my XP image. (I created this a few years back.) I then loaded the Cisco VPN client inside of XP and connected to my corporate network. I then tested - sure enough, the host system was still on my home network, while the virtual machine was on the corporate WAN. I then loaded Remote Desktop and connected successfully to my Vista desktop followed by tightVNC connected to my openSUSE server. All is good now. This means I can connect remotely to my work without having to interrupt my connection to my home network. Now on to upgrading my wife's Win2K machine. I think I'll start by making a VM image of that machine (there's some tool to do this) and then encapsulating it inside an openSUSE system. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 7 Feb 2008 19:35:55 -0800
Kai Ponte
One problem down, one to go.
I can't seem to connect to my (or any other) wifi network with my laptop.
I have an Intel 3945 ABG card in my laptop. It is loaded with the ipw3945d Regulatory Daemon, ipw3945-kmp-default, ipw-firmware, the iwl3945-ucode and iwlifi-kmp-default files in YaST.
I have network setup to be user controlled using KNetworkmanager. Though previously hidden, I have my SSID open with no password.
I can see my network but cannot connect. The KNetworkmanager progress bar gets to 28% then quits.
I also tried this on a few of my neighbors' open wifi networks and I can't get to them either.
On a previous attempt to setup 10.3 on this laptop, I was intermittently able to get on the wifi. 10.2 had no issues.
I've googled but not found much to help out.
Ideas?
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
In my experience using openSUSE 10.3 on my T61p with the ipw3945, I have to toggle the wifi switch while KNetworkmanager is starting to spin in order to get it to connect. I've been hoping that a driver update will correct the problem. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jay Vollmer a écrit :
In my experience using openSUSE 10.3 on my T61p with the ipw3945, I have to toggle the wifi switch while KNetworkmanager is starting to spin in order to get it to connect.
I've been hoping that a driver update will correct the problem.
I just install an intel 3945 card and it worked out of the box... I just had to go to yast, software, search for 3945, installed stuff and go to yast network card. Then the card was found and yast added an other utility software (had no 3945 in the name) and voilà, I have a very good wireless connexion jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2008-02-07 at 19:35 -0800, Kai Ponte wrote:
One problem down, one to go.
I can't seem to connect to my (or any other) wifi network with my laptop.
I have an Intel 3945 ABG card in my laptop. It is loaded with the ipw3945d Regulatory Daemon, ipw3945-kmp-default, ipw-firmware, the iwl3945-ucode and iwlifi-kmp-default files in YaST.
I have network setup to be user controlled using KNetworkmanager. Though previously hidden, I have my SSID open with no password.
I can see my network but cannot connect. The KNetworkmanager progress bar gets to 28% then quits.
I also tried this on a few of my neighbors' open wifi networks and I can't get to them either.
On a previous attempt to setup 10.3 on this laptop, I was intermittently able to get on the wifi. 10.2 had no issues.
I've googled but not found much to help out.
Ideas?
Both myself and a coworker had the same problem on our new Dell Latitude D630 laptops. Fresh installs of 10.3. We could see an access point but could not connect the majority of the time. When we were able to connect, signal strength in the Gnome Network Manager applet would be in the low teens, speed would never be above 24 Mbs and overall performance would be extremely poor. After much troubleshoot I discovered that during installation both the ipw3945 and the iwl3945 kernel modules got installed. Yast chose the ipw3945 module when setting up the wireless. From some of the messages I've seen when Googleing Intel 3945, there seem to be some significant issues with the ipw3945 kernel driver. The fix is to in YAST, select Configure on the Wireless Card. Select the Hardware Tab, then change the Kernel Module in the Module Name Drop down list from the ipw3945 to the iwl3945. Save the settings and exit out of YAST. Reboot the laptop. If the iwl3945 kernel module is not in the list install it first then reboot and change. According to the chatter, some of the features of the iwl3945 module are done yet. Like illuminating the blue Wifi light and displaying the connection speed in the Network manager. But other than those cosmetic issues, it is reliable and works every time I boot. I have no trouble going between the office wireless and my home wireless, or using any other wifi connection I have tried. Give it shot and let us know how it works. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Chuck Stuettgen wrote:
The fix is to in YAST, select Configure on the Wireless Card. Select the Hardware Tab, then change the Kernel Module in the Module Name Drop down list from the ipw3945 to the iwl3945. Save the settings and exit out of YAST. Reboot the laptop.
If the iwl3945 kernel module is not in the list install it first then reboot and change.
Ack, that is a good fix - except for the reboots; absolutely no need for any of that, just rmmod the ipw3945 and you're good to go. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 08 February 2008 09:46:55 pm Joe Sloan wrote:
Chuck Stuettgen wrote:
The fix is to in YAST, select Configure on the Wireless Card. Select the Hardware Tab, then change the Kernel Module in the Module Name Drop down list from the ipw3945 to the iwl3945. Save the settings and exit out of YAST. Reboot the laptop.
If the iwl3945 kernel module is not in the list install it first then reboot and change.
That worked great! Thanks.
Ack, that is a good fix - except for the reboots; absolutely no need for any of that, just rmmod the ipw3945 and you're good to go.
I would have no idea how to do that. Joe - I'm (obviously) not making it to SCALE today. I'll see if I get there tomorrow. -- kai -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Kai Ponte wrote:
On Friday 08 February 2008 09:46:55 pm Joe Sloan wrote:
Chuck Stuettgen wrote:
The fix is to in YAST, select Configure on the Wireless Card. Select the Hardware Tab, then change the Kernel Module in the Module Name Drop down list from the ipw3945 to the iwl3945. Save the settings and exit out of YAST. Reboot the laptop.
If the iwl3945 kernel module is not in the list install it first then reboot and change.
That worked great! Thanks.
Ack, that is a good fix - except for the reboots; absolutely no need for any of that, just rmmod the ipw3945 and you're good to go.
I would have no idea how to do that.
Joe - I'm (obviously) not making it to SCALE today.
I'll see if I get there tomorrow.
Ah, too bad - I picked up a few things of interest, but it mostly struck me as small and disorganized. Maybe I've been spoiled by the grand extravaganza that is Linux World Expo. I'm looking forward to that, 6 months from now in San Francisco. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 09 February 2008 04:54:37 pm Joe Sloan wrote:
Kai Ponte wrote:
On Friday 08 February 2008 09:46:55 pm Joe Sloan wrote:
Chuck Stuettgen wrote:
The fix is to in YAST, select Configure on the Wireless Card. Select the Hardware Tab, then change the Kernel Module in the Module Name Drop down list from the ipw3945 to the iwl3945. Save the settings and exit out of YAST. Reboot the laptop.
If the iwl3945 kernel module is not in the list install it first then reboot and change.
That worked great! Thanks.
Ack, that is a good fix - except for the reboots; absolutely no need for any of that, just rmmod the ipw3945 and you're good to go.
I would have no idea how to do that.
Joe - I'm (obviously) not making it to SCALE today.
I'll see if I get there tomorrow.
Ah, too bad - I picked up a few things of interest, but it mostly struck me as small and disorganized. Maybe I've been spoiled by the grand extravaganza that is Linux World Expo. I'm looking forward to that, 6 months from now in San Francisco.
Oh, that's too bad. My beautiful bride gave me permission to go tomorrow AM. However, I think I'll pass then. Maybe next year. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joe Sloan wrote:
Chuck Stuettgen wrote:
The fix is to in YAST, select Configure on the Wireless Card. Select the Hardware Tab, then change the Kernel Module in the Module Name Drop down list from the ipw3945 to the iwl3945. Save the settings and exit out of YAST. Reboot the laptop.
If the iwl3945 kernel module is not in the list install it first then reboot and change.
Ack, that is a good fix - except for the reboots; absolutely no need for any of that, just rmmod the ipw3945 and you're good to go.
Here's something I just found and points to where the "real" problem with hidden sites is, when for awhile I assumed it was KNetworkmanager....so did others. For almost 2 weeks, I've been using the ipw3945 driver and the standard ifup method to connect. I just changed from that driver to the iwl3945 driver, stopped the ipw driver and used Yast to setup using the iwl driver with KNetworkmanager.....just to see what happend. I've NOT been able to see hidden sites, including my own at home, with KNetworkmanager.......now I can. So, it would appear that this problem that plagues some others with different chipsets have a problem with the driver, NOT KNetworkmanager. Thanks to Chuck Stuettgen for pointing this out!! Fred -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Fred A. Miller wrote:
Here's something I just found and points to where the "real" problem with hidden sites is, when for awhile I assumed it was KNetworkmanager....so did others.
For almost 2 weeks, I've been using the ipw3945 driver and the standard ifup method to connect. I just changed from that driver to the iwl3945 driver, stopped the ipw driver and used Yast to setup using the iwl driver with KNetworkmanager.....just to see what happend. I've NOT been able to see hidden sites, including my own at home, with KNetworkmanager.......now I can.
There's not much point in hiding the SSID, as it doesn't do much to stop attackers. It also means that a neighbour, looking for a clear spot to put his WiFi, might chose the same channel as yours. The best way to get WiFi security, is to use WPA (WPA2 if possible), which is very secure. WEP is not. I've also got my home WiFi (WPA2) on the outside of my firewall, so SSH, with public key authentication or OpenVPN are required to reach my network. -- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 09 February 2008 01:58:41 pm James Knott wrote:
There's not much point in hiding the SSID, as it doesn't do much to stop attackers. It also means that a neighbour, looking for a clear spot to put his WiFi, might chose the same channel as yours. The best way to get WiFi security, is to use WPA (WPA2 if possible), which is very secure. WEP is not. I've also got my home WiFi (WPA2) on the outside of my firewall, so SSH, with public key authentication or OpenVPN are required to reach my network.
Know what I do too? I also have only three available IP addresses. I found this out when I tried to connect my newest laptop and it wouldn't assign me an IP address. I'd forgotten that I only .100 and .101 available. Now I have .100 through .102 available (and taken). No sense in having ip addresses available when no one *should* be using them. The iwl drivers seems to have done the trick! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Fred A. Miller a écrit :
For almost 2 weeks, I've been using the ipw3945 driver and the standard ifup method to connect. I just changed from that driver to the iwl3945
can somebody document this on the wiki? just search for 3945 and fix any page you want. I applicable, give a link to the bugzilla entry only noting there are two drivers may be of use (I use the ipw myself, installed by yast, and have nothing to complain), one can try the other if necessary :-)) thanks jdd -- http://www.dodin.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
jdd wrote:
Fred A. Miller a écrit :
For almost 2 weeks, I've been using the ipw3945 driver and the standard ifup method to connect. I just changed from that driver to the iwl3945
can somebody document this on the wiki? just search for 3945 and fix any page you want. I applicable, give a link to the bugzilla entry
only noting there are two drivers may be of use (I use the ipw myself, installed by yast, and have nothing to complain), one can try the other if necessary :-))
I spoke too soon. :( I was on a site and it all looked like a "go" with KNetworkmanger. No.....NOT so lucky. Maybe the problem is in Knetworkmanager after all. Fred -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 09 February 2008 05:05:29 pm Fred A. Miller wrote:
jdd wrote:
Fred A. Miller a écrit :
For almost 2 weeks, I've been using the ipw3945 driver and the standard ifup method to connect. I just changed from that driver to the iwl3945
can somebody document this on the wiki? just search for 3945 and fix any page you want. I applicable, give a link to the bugzilla entry
only noting there are two drivers may be of use (I use the ipw myself, installed by yast, and have nothing to complain), one can try the other if necessary :-))
I spoke too soon. :( I was on a site and it all looked like a "go" with KNetworkmanger. No.....NOT so lucky. Maybe the problem is in Knetworkmanager after all.
What do you mean you were "on a site" ? Did the network suddenly drop? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (7)
-
Chuck Stuettgen -
Fred A. Miller -
James Knott -
Jay Vollmer -
jdd -
Joe Sloan -
Kai Ponte