Help needed for Intel PRO/Wireless 2100
Looking for some help from anyone who has gotten the Intel PRO/Wireless 2100 card working to establish a wireless internet connection. Per the document in file://usr/share/doc/packages/wireless-tools/README.firmware I downloaded the 96377_96377.zip file and installed per the instructions (although I'm still not sure that's the right file). The card is detected by YAST, but I'm unable to get a connection though it with any known good WAPs. If I try 'ping yahoo.com -I eth1' I get 'connect: No such device'. The laptop I'm using is a Dell Latitude D600. I'm more than happy to provide any addtional information. Thanks. -- Cheers, Trey --- There is an innocence in admiration; it is found in those to whom it has not yet occurred that they, too, might be admired some day. - Friedrich Nietzsche 17:37:06 up 5 days, 17 min, 1 user, load average: 0.11, 0.08, 0.03 Linux salamander 2.6.6 #1 SMP Mon May 10 00:12:20 PDT 2004 i686 unknown unknown GNU/Linux
Trey Sizemore wrote:
Looking for some help from anyone who has gotten the Intel PRO/Wireless 2100 card working to establish a wireless internet connection. Per the document in file://usr/share/doc/packages/wireless-tools/README.firmware I downloaded the 96377_96377.zip file and installed per the instructions (although I'm still not sure that's the right file). The card is detected by YAST, but I'm unable to get a connection though it with any known good WAPs. If I try 'ping yahoo.com -I eth1' I get 'connect: No such device'.
The laptop I'm using is a Dell Latitude D600. I'm more than happy to provide any addtional information.
Thanks.
The output of (as root) >ifconfig and >iwconfig would be a start.
On Fri, 2004-05-21 at 17:14 -0600, jim barnes wrote:
The output of (as root) >ifconfig and >iwconfig would be a start.
Good point. Sorry, here's the output: linux:/home/trey # ifconfig eth0 Link encap:Ethernet HWaddr 00:0D:56:DD:11:14 inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::20d:56ff:fedd:1114/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:212 errors:0 dropped:0 overruns:0 frame:0 TX packets:222 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:152375 (148.8 Kb) TX bytes:21242 (20.7 Kb) Interrupt:11 eth1 Link encap:Ethernet HWaddr 00:0C:F1:15:E0:49 inet6 addr: fe80::20c:f1ff:fe15:e049/64 Scope:Link UP BROADCAST NOTRAILERS MULTICAST MTU:1500 Metric:1 RX packets:3 errors:0 dropped:0 overruns:0 frame:0 TX packets:2 errors:0 dropped:0 overruns:0 carrier:1 collisions:0 txqueuelen:1000 RX bytes:710 (710.0 b) TX bytes:1184 (1.1 Kb) Interrupt:11 Base address:0x7000 Memory:fafef000-fafeffff lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:126 errors:0 dropped:0 overruns:0 frame:0 TX packets:126 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 -AND- linux:/home/trey # iwconfig lo no wireless extensions. eth0 no wireless extensions. eth1 IEEE 802.11b ESSID:"theether" Nickname:"laptop" Mode:Managed Channel:0 Access Point: 00:00:00:00:00:00 Bit Rate=0kb/s Tx-Power=0 dBm Retry:on RTS thr=2304 B Fragment thr:off Encryption key:5454-5454-54 Security mode:restricted Power Management:off Link Quality:0/100 Signal level:-30 dBm Noise level:-98 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 sit0 no wireless extensions. Thanks.
Trey Sizemore wrote:
On Fri, 2004-05-21 at 17:14 -0600, jim barnes wrote:
The output of (as root) >ifconfig and >iwconfig would be a start.
Good point. Sorry, here's the output:
linux:/home/trey # ifconfig eth0 Link encap:Ethernet HWaddr 00:0D:56:DD:11:14 inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::20d:56ff:fedd:1114/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:212 errors:0 dropped:0 overruns:0 frame:0 TX packets:222 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:152375 (148.8 Kb) TX bytes:21242 (20.7 Kb) Interrupt:11
Ok, loose the eth0 configuration, delete it via yast. Are you doing dhcp or static on eth1? It should have an IP now. You might also turn off WEP until your connection has been verified.
On Fri, 2004-05-21 at 21:11, jim barnes wrote:
Ok, loose the eth0 configuration, delete it via yast. Are you doing dhcp or static on eth1? It should have an IP now. You might also turn off WEP until your connection has been verified.
I deleted the eth0 config. I'm using DHCP on eth1. I turned off WEP. When I run 'ifdown eth1' then 'ifup eth1' I get: ERROR: command 'iwconfig eth1 mode Master' returned Error for wireless request "Set Mode" (8B06) : SET failed on device eth1 ; Input/output error. -- Cheers, Trey --- Thieves respect property; they merely wish the property to become their property that they may more perfectly respect it. -- G.K. Chesterton, "The Man Who Was Thursday" 21:40:45 up 5 days, 4:20, 1 user, load average: 0.00, 0.05, 0.01 Linux salamander 2.6.6 #1 SMP Mon May 10 00:12:20 PDT 2004 i686 unknown unknown GNU/Linux
Trey Sizemore wrote:
On Fri, 2004-05-21 at 21:11, jim barnes wrote:
Ok, loose the eth0 configuration, delete it via yast. Are you doing dhcp or static on eth1? It should have an IP now. You might also turn off WEP until your connection has been verified.
I deleted the eth0 config. I'm using DHCP on eth1. I turned off WEP.
When I run 'ifdown eth1' then 'ifup eth1' I get:
ERROR: command 'iwconfig eth1 mode Master' returned Error for wireless request "Set Mode" (8B06) : SET failed on device eth1 ; Input/output error.
Let's back up a bit now. Is this a 9.1 install? Your signature is confusing me somewhat. usr/share/doc/packages/wireless-tools/README.firmware on my (9.1) install calls for 80940_80940.zip. Did you install ipw211-0.44 or later to require 96377_96377.zip?
On Fri, 2004-05-21 at 22:15, jim barnes wrote:
Let's back up a bit now. Is this a 9.1 install? Your signature is confusing me somewhat.
I'm responding from my desktop as I don't have internet access on the laptop running SUSE 9.1 now.
usr/share/doc/packages/wireless-tools/README.firmware on my (9.1) install calls for 80940_80940.zip. Did you install ipw211-0.44 or later to require 96377_96377.zip?
Yes, I did. Should I go back and get the 80940_80940.zip package? I had assumed that the numbering had changed since the release. -- Cheers, Trey --- The beauty of the soul shines out when a man bears with composure one heavy mischance after another, not because he does not feel them, but because he is a man of high and heroic temper. - Aristotle 22:29:23 up 5 days, 5:09, 1 user, load average: 0.00, 0.01, 0.03 Linux salamander 2.6.6 #1 SMP Mon May 10 00:12:20 PDT 2004 i686 unknown unknown GNU/Linux
Trey Sizemore wrote:
On Fri, 2004-05-21 at 22:15, jim barnes wrote:
Let's back up a bit now. Is this a 9.1 install? Your signature is confusing me somewhat.
I'm responding from my desktop as I don't have internet access on the laptop running SUSE 9.1 now.
usr/share/doc/packages/wireless-tools/README.firmware on my (9.1) install calls for 80940_80940.zip. Did you install ipw211-0.44 or later to require 96377_96377.zip?
Yes, I did. Should I go back and get the 80940_80940.zip package? I had assumed that the numbering had changed since the release.
80940_80940.zip worked for me with a stock install. Don't know about later driver releases. Maybe your driver didn't update as you thought it had. Lots of info here on the subject: (if you haven't already) ipw2100.sourceforge.net/
On Fri, 2004-05-21 at 22:41, jim barnes wrote:
80940_80940.zip worked for me with a stock install. Don't know about later driver releases. Maybe your driver didn't update as you thought it had.
Lots of info here on the subject: (if you haven't already)
ipw2100.sourceforge.net/
Thanks, I now have the interface up (eth1) and have it set for static IP. It sees the access point according to KWiFiManager and I have a good signal strength. However, I don't have a valid connection to the internet...I can't ping and mozilla can't find sites. Could this be that since I have been accessing the net via eth0 I need to now say use eth1? -- Cheers, Trey --- men fear thought as they fear nothing else on earth --more than ruin --more even than death. thought is subversive and revolutionary, destructive and terrible, thought is merciless to privilege, established institutions, and comfortable habit. thought looks into the pit of hell and is not afraid. thought is great and swift and free, the light of the world, and the chief glory of man. - bertrand russell 23:38:51 up 5 days, 6:18, 1 user, load average: 0.15, 0.09, 0.04 Linux salamander 2.6.6 #1 SMP Mon May 10 00:12:20 PDT 2004 i686 unknown unknown GNU/Linux
Trey Sizemore wrote:
On Fri, 2004-05-21 at 22:41, jim barnes wrote:
80940_80940.zip worked for me with a stock install. Don't know about later driver releases. Maybe your driver didn't update as you thought it had.
Lots of info here on the subject: (if you haven't already)
ipw2100.sourceforge.net/
Thanks, I now have the interface up (eth1) and have it set for static IP. It sees the access point according to KWiFiManager and I have a good signal strength. However, I don't have a valid connection to the internet...I can't ping and mozilla can't find sites.
Could this be that since I have been accessing the net via eth0 I need to now say use eth1?
I believe it will default to eth1 Back to yast and make sure default route points to your access point's IP. -or- edit /etc/sysconfig/network/route to contain "default 192.168.0.1" without the quotes. And then >rcnetwork restart as root.
route will show the details.
Thanks, I now have the interface up (eth1) and have it set for static IP. It sees the access point according to KWiFiManager and I have a good signal strength. However, I don't have a valid connection to the internet...I can't ping and mozilla can't find sites.
Could this be that since I have been accessing the net via eth0 I need to now say use eth1?
I believe it will default to eth1
Back to yast and make sure default route points to your access point's IP.
-or- edit /etc/sysconfig/network/route to contain "default 192.168.0.1" without the quotes. And then >rcnetwork restart as root.
route will show the details.
And also of course the DNS server field must have an entry...either your access point or your isp's DNS ip's as applicble.
On Sat, 2004-05-22 at 00:15, jim barnes wrote:
I believe it will default to eth1
Back to yast and make sure default route points to your access point's IP.
-or- edit /etc/sysconfig/network/route to contain "default 192.168.0.1" without the quotes. And then >rcnetwork restart as root.
I don't have a file /etc/sysconfig/network/route ?????
route will show the details.
My current route looks like (having to type manually :-( ): Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth1 My desktop machine (also using the router) looks like this: Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0 Thanks. -- Cheers, Trey --- No lake so still but that it has its wave; No circle so perfect but that it has a blur. I would change things for you if I could; As I can't, you must take them as they are. -Han fei Tzu 08:49:54 up 5 days, 15:29, 1 user, load average: 0.01, 0.04, 0.00 Linux salamander 2.6.6 #1 SMP Mon May 10 00:12:20 PDT 2004 i686 unknown unknown GNU/Linux
On Sat, 2004-05-22 at 00:15, jim barnes wrote:
I believe it will default to eth1
Back to yast and make sure default route points to your access point's IP.
-or- edit /etc/sysconfig/network/route to contain "default 192.168.0.1" without the quotes. And then >rcnetwork restart as root.
I don't have a file /etc/sysconfig/network/route ?????
route will show the details.
My current route looks like (having to type manually :-( ):
Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth1
My desktop machine (also using the router) looks like this:
Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
Thanks. when you were told route would provide the answer you were meant to type "route -n" at an xterm or whatever terminal oyu use
On Saturday 22 May 2004 13:59, Trey Sizemore wrote: prompt you will then get an output like this .. "ds9:/ # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 10.0.0.2 0.0.0.0 UG 0 0 0 eth0 ds9:/ # " (Damm word wrap) -- G6NJR Pete otherwise known as "Quinton 11" A Linux Only area Happy bug hunting M$ clan Pete,,,,, :-)
On Sat, 2004-05-22 at 18:04 +0100, peter Nikolic wrote:
when you were told route would provide the answer you were meant to type "route -n" at an xterm or whatever terminal oyu use prompt you will then get an output like this .. "ds9:/ # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 10.0.0.2 0.0.0.0 UG 0 0 0 eth0 ds9:/ # "
(Damm word wrap)
That was what I did. I just had to retype it at the time from the laptop output to my desktop because I didn't have internet access on the laptop at that time. My output appears similar although the formatting seems to be lost in your reply. Anyway, on the last boot of the laptop it appears working now. The next step is to get WEP enabled again. -Trey
participants (3)
-
jim barnes -
peter Nikolic -
Trey Sizemore