try to convince my wife to switch to linux on her laptop with suse 9.2 and toshiba satelite m35-s3592 works fine but wireless conection is not working here is output of iwconfig eth1 IEEE 802.11b ESSID:"NYBKLNY" Nickname:"linux" Mode:Managed Frequency:2.437 GHz Access Point: 00:0F:66:37:54:B3 Bit Rate=11 Mb/s Tx-Power=32 dBm Retry:on RTS thr=2304 B Fragment thr:off Encryption key:D68A-E0A3-EEA6-4155-D894-4DE6-8D Security mode:open Power Management:off Link Quality=100/100 Signal level=-35 dBm Noise level=-98 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:11 Missed beacon:0 ifconfig -a eth0 Link encap:Ethernet HWaddr 00:08:0D:E3:C8:CB inet6 addr: fe80::208:dff:fee3:c8cb/64 Scope:Link UP BROADCAST NOTRAILERS MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:5900 (5.7 Kb) eth1 Link encap:Ethernet HWaddr 00:04:23:84:BA:1B inet6 addr: fe80::204:23ff:fe84:ba1b/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:4 dropped:4 overruns:0 frame:0 TX packets:16 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:9344 (9.1 Kb) Interrupt:11 Base address:0x8000 Memory:c2005000-c2005fff my wireless is eth1 i get 100% signal but no ip get assigned i tried to assigned manually i can ping it from same laptop but not from outside and i have no internet if i get this working i am sure she is a convert
On Sunday 21 November 2004 11:24 am, boricua Orman wrote:
try to convince my wife to switch to linux on her laptop with suse 9.2 and toshiba satelite m35-s3592
works fine but wireless conection is not working
here is output of iwconfig eth1 IEEE 802.11b ESSID:"NYBKLNY" Nickname:"linux" Mode:Managed Frequency:2.437 GHz Access Point: 00:0F:66:37:54:B3 Bit Rate=11 Mb/s Tx-Power=32 dBm Retry:on RTS thr=2304 B Fragment thr:off Encryption key:D68A-E0A3-EEA6-4155-D894-4DE6-8D Security mode:open Power Management:off Link Quality=100/100 Signal level=-35 dBm Noise level=-98 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:11 Missed beacon:0
ifconfig -a eth0 Link encap:Ethernet HWaddr 00:08:0D:E3:C8:CB inet6 addr: fe80::208:dff:fee3:c8cb/64 Scope:Link UP BROADCAST NOTRAILERS MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:5900 (5.7 Kb)
eth1 Link encap:Ethernet HWaddr 00:04:23:84:BA:1B inet6 addr: fe80::204:23ff:fe84:ba1b/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:4 dropped:4 overruns:0 frame:0 TX packets:16 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:9344 (9.1 Kb) Interrupt:11 Base address:0x8000 Memory:c2005000-c2005fff
my wireless is eth1
i get 100% signal but no ip get assigned i tried to assigned manually i can ping it from same laptop but not from outside
and i have no internet
if i get this working i am sure she is a convert
Have you tried ifconfig eth0 down ifconfig eth1 up dhcpcd eth1 ? Richard -- Old age ain't for Sissies!
and i have no internet
if i get this working i am sure she is a convert
Have you tried ifconfig eth0 down ifconfig eth1 up dhcpcd eth1 ?
Richard
i did try that but it did not help when i do hdcpcd eth1 i see in /var/log/messages eth1 no ipv6 routers present time out waiting for a valid dhcpcd server
Quoting boricua Orman
and i have no internet
if i get this working i am sure she is a convert
Have you tried ifconfig eth0 down ifconfig eth1 up dhcpcd eth1 ?
Richard
i did try that but it did not help
when i do hdcpcd eth1 i see in /var/log/messages eth1 no ipv6 routers present time out waiting for a valid dhcpcd server
You can ignore the ipv6 message for the moment, unless your DHCP server is ipv6 only, an unlikely occurrence. What does the syslog show when you load the driver? ("modprobe ipw2100"; if this does nothing, remove it, "rmmod ipw2100", and load it again). Jeffrey
ting for a valid dhcpcd server
You can ignore the ipv6 message for the moment, unless your DHCP server is ipv6 only, an unlikely occurrence. What does the syslog show when you load the driver? ("modprobe ipw2100"; if this does nothing, remove it, "rmmod ipw2100", and load it again).
Jeffrey
Nov 22 06:49:51 linux kernel: eth1: Using hotplug firmware load. Nov 22 06:49:51 linux kernel: eth1: Bound to 0000:02:0a.0 Nov 22 06:49:52 linux kernel: eth1: Associated with '04Z409048210' at 1Mbps, channel 6 (BSSID=00:00:00:00:00:00) Nov 22 06:50:01 linux kernel: eth1: Association lost. Nov 22 06:50:02 linux kernel: eth1: Associated with 'NYBKLNY' at 11Mbps, channel 6 (BSSID=00:e0:98:c9:09:6c) Nov 22 06:50:12 linux kernel: eth1: no IPv6 routers present
Quoting boricua Orman
ting for a valid dhcpcd server
You can ignore the ipv6 message for the moment, unless your DHCP server is ipv6 only, an unlikely occurrence. What does the syslog show when you load the driver? ("modprobe ipw2100"; if this does nothing, remove it, "rmmod ipw2100", and load it again).
Jeffrey
Nov 22 06:49:51 linux kernel: eth1: Using hotplug firmware load. Nov 22 06:49:51 linux kernel: eth1: Bound to 0000:02:0a.0 Nov 22 06:49:52 linux kernel: eth1: Associated with '04Z409048210' at 1Mbps, channel 6 (BSSID=00:00:00:00:00:00) Nov 22 06:50:01 linux kernel: eth1: Association lost. Nov 22 06:50:02 linux kernel: eth1: Associated with 'NYBKLNY' at 11Mbps, channel 6 (BSSID=00:e0:98:c9:09:6c) Nov 22 06:50:12 linux kernel: eth1: no IPv6 routers present
What about where the module is loaded? Oh, you are using the ipw2100 driver not linuxant (sp?) or ndiswrapper. Jeffrey
Nov 22 06:49:51 linux kernel: eth1: Using hotplug firmware load. Nov 22 06:49:51 linux kernel: eth1: Bound to 0000:02:0a.0 Nov 22 06:49:52 linux kernel: eth1: Associated with '04Z409048210' at 1Mbps, channel 6 (BSSID=00:00:00:00:00:00) Nov 22 06:50:01 linux kernel: eth1: Association lost. Nov 22 06:50:02 linux kernel: eth1: Associated with 'NYBKLNY' at 11Mbps, channel 6 (BSSID=00:e0:98:c9:09:6c) Nov 22 06:50:12 linux kernel: eth1: no IPv6 routers present
What about where the module is loaded? i
not sure what you mean where the module is loaded? Oh, you are using the ipw2100
driver not linuxant (sp?) or ndiswrapper.
not sure what you mean by that either
Quoting boricua@pepino.is-a-geek.org
Nov 22 06:49:51 linux kernel: eth1: Using hotplug firmware load. Nov 22 06:49:51 linux kernel: eth1: Bound to 0000:02:0a.0 Nov 22 06:49:52 linux kernel: eth1: Associated with '04Z409048210' at 1Mbps, channel 6 (BSSID=00:00:00:00:00:00) Nov 22 06:50:01 linux kernel: eth1: Association lost. Nov 22 06:50:02 linux kernel: eth1: Associated with 'NYBKLNY' at 11Mbps, channel 6 (BSSID=00:e0:98:c9:09:6c) Nov 22 06:50:12 linux kernel: eth1: no IPv6 routers present
What about where the module is loaded? i
not sure what you mean where the module is loaded?
What is in syslog when you load the driver for the the wireless card?
Oh, you are using the ipw2100
driver not linuxant (sp?) or ndiswrapper.
not sure what you mean by that either
There are at least three different drivers for the IPW2100 card: the ipw2100 currently under development (IIRC, this ships with SuSE 9.2), the linuxant wrapper that uses the Windows driver, and the ndiswrapper, an open source project similar to the linuxant wrapper. The latter two use the NDIS API of the Windows driver and wrap a Linux driver around it. To help you get your wireless card running, we need to know which driver you are using. What is the output of "grep ipw2100 /var/log/messages"? Jeffrey
On Mon, Nov 22, 2004 at 11:52:57AM -0600, Jeffrey L. Taylor wrote:
Quoting boricua@pepino.is-a-geek.org
: Nov 22 06:49:51 linux kernel: eth1: Using hotplug firmware load. Nov 22 06:49:51 linux kernel: eth1: Bound to 0000:02:0a.0 Nov 22 06:49:52 linux kernel: eth1: Associated with '04Z409048210' at 1Mbps, channel 6 (BSSID=00:00:00:00:00:00) Nov 22 06:50:01 linux kernel: eth1: Association lost. Nov 22 06:50:02 linux kernel: eth1: Associated with 'NYBKLNY' at 11Mbps, channel 6 (BSSID=00:e0:98:c9:09:6c) Nov 22 06:50:12 linux kernel: eth1: no IPv6 routers present
What about where the module is loaded? i
not sure what you mean where the module is loaded?
What is in syslog when you load the driver for the the wireless card?
Oh, you are using the ipw2100
driver not linuxant (sp?) or ndiswrapper.
not sure what you mean by that either
There are at least three different drivers for the IPW2100 card: the ipw2100 currently under development (IIRC, this ships with SuSE 9.2), the linuxant wrapper that uses the Windows driver, and the ndiswrapper, an open source project similar to the linuxant wrapper. The latter two use the NDIS API of the Windows driver and wrap a Linux driver around it. To help you get your wireless card running, we need to know which driver you are using. What is the output of "grep ipw2100 /var/log/messages"?
Jeffredoes thi
does this help Nov 22 06:49:51 linux kernel: ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, 0.55 Nov 22 06:49:51 linux kernel: ipw2100: Copyright(c) 2003-2004 Intel Corporation Nov 22 06:49:51 linux kernel: ACPI: PCI interrupt 0000:02:0a.0[A] -> GSI 11 (level, low) -> IRQ 11 Nov 22 06:49:51 linux kernel: ipw2100: 0000:02:0a.0: Detected at mem: 0xC2005000-0xC2005FFF -> f0fd0000, irq: 11 Nov 22 06:49:51 linux kernel: eth1: Using hotplug firmware load. Nov 22 06:49:51 linux kernel: eth1: Bound to 0000:02:0a.0 Nov 22 06:49:52 linux kernel: eth1: Associated with '04Z409048210' at 1Mbps, channel 6 (BSSID=00:00:00:00:00:00) Nov 22 06:50:01 linux kernel: eth1: Association lost. Nov 22 06:50:02 linux kernel: eth1: Associated with 'NYBKLNY' at 11Mbps, channel 6 (BSSID=00:e0:98:c9:09:6c) Nov 22 06:50:12 linux kernel: eth1: no IPv6 routers present y
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Quoting boricua@pepino.is-a-geek.org
does this help
Nov 22 06:49:51 linux kernel: ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, 0.55 Nov 22 06:49:51 linux kernel: ipw2100: Copyright(c) 2003-2004 Intel Corporation Nov 22 06:49:51 linux kernel: ACPI: PCI interrupt 0000:02:0a.0[A] -> GSI 11 (level, low) -> IRQ 11 Nov 22 06:49:51 linux kernel: ipw2100: 0000:02:0a.0: Detected at mem: 0xC2005000-0xC2005FFF -> f0fd0000, irq: 11 Nov 22 06:49:51 linux kernel: eth1: Using hotplug firmware load. Nov 22 06:49:51 linux kernel: eth1: Bound to 0000:02:0a.0 Nov 22 06:49:52 linux kernel: eth1: Associated with '04Z409048210' at 1Mbps, channel 6 (BSSID=00:00:00:00:00:00) Nov 22 06:50:01 linux kernel: eth1: Association lost. Nov 22 06:50:02 linux kernel: eth1: Associated with 'NYBKLNY' at 11Mbps, channel 6 (BSSID=00:e0:98:c9:09:6c) Nov 22 06:50:12 linux kernel: eth1: no IPv6 routers present
Yes it does. The lines above look good. This version is several months old. My first suggestion is to uninstall the driver thru YaST, rpm, or whatever. If not a separate package, do this: cd /lib/modules/ find . -name "ieee80211*.ko" find . -name "ipw2100.ko" Delete any modules/drivers found. IIRC, these are in the extra/ directory. Go to ipw2100.sf.net, download, make, and install the latest version (1.0.1 at the moment). You will also need to download and install the firmware. The directions are on the site. Be aware that the firmware is closed source, binary only, and you will need to agree to a license. You will need the kernel sources to compile it. The new drivers will be installed in different place, "kernel/drivers/net/wireless/ipw2100/". You do not want to have two versions of the driver in the kernel modules directory tree. My second suggestion is to check routing ("route -n"). If safe, take any firewall down. (I.e., do try this at home or work. Trying it in a coffeehouse/bar/dive where the hackers hang out can be hazardous to the health of your laptop.) Take any other network interface down, e.g. eth0. Try setting the IP address manually. Try pinging the access point. If this all works, try "traceroute google.com" or "traceroute 216.239.37.99" if you don't have DNS working. HTH, Jeffrey
cd /lib/modules/ find . -name "ieee80211*.ko" find . -name "ipw2100.ko"
Delete any modules/drivers found. IIRC, these are in the extra/ directory.
Go to ipw2100.sf.net, download, make, and install the latest version (1.0.1 at the moment). You will also need to download and install the firmware. The directions are on the site. Be aware that the firmware is closed source, binary only, and you will need to agree to a license. You will need the kernel sources to compile it. The new drivers will be installed in different place, "kernel/drivers/net/wireless/ipw2100/". You do not want to have two versions of the driver in the kernel modules directory tree.
My second suggestion is to check routing ("route -n"). If safe, take any firewall down. (I.e., do try this at home or work. Trying it in a coffeehouse/bar/dive where the hackers hang out can be hazardous to the health of your laptop.) Take any other network interface down, e.g. eth0. Try setting the IP address manually. Try pinging the access point. If this all works, try "traceroute google.com" or "traceroute 216.239.37.99" if you don't have DNS working.
HTH, Jeffrey
update did not solve still same problem
This is going to sound silly, but I would try enabling power management. I have the ipw2200 in my system, and sometimes it won't work unless I have the power management on. It can be turned on by using the following command: iwconfig eth1 power on A quick type of "iwconfig eth1" afterwards should show that the command took effect. Mike Sacco -----Original Message----- From: boricua Orman [mailto:boricua@pepino.is-a-geek.org] Sent: Monday, November 22, 2004 6:53 PM To: Jeffrey L. Taylor Cc: suse Subject: Re: [SLE] wireless card ipw2100
cd /lib/modules/ find . -name "ieee80211*.ko" find . -name "ipw2100.ko"
Delete any modules/drivers found. IIRC, these are in the extra/ directory.
Go to ipw2100.sf.net, download, make, and install the latest version (1.0.1 at the moment). You will also need to download and install the firmware. The directions are on the site. Be aware that the firmware is closed source, binary only, and you will need to agree to a license. You will need the kernel sources to compile it. The new drivers will be installed in different place, "kernel/drivers/net/wireless/ipw2100/". You do not want to have two versions of the driver in the kernel modules directory tree.
My second suggestion is to check routing ("route -n"). If safe, take any firewall down. (I.e., do try this at home or work. Trying it in a coffeehouse/bar/dive where the hackers hang out can be hazardous to the health of your laptop.) Take any other network interface down, e.g. eth0. Try setting the IP address manually. Try pinging the access point. If this all works, try "traceroute google.com" or "traceroute 216.239.37.99" if you don't have DNS working.
HTH, Jeffrey
update did not solve still same problem -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Tue, 2004-11-23 at 00:29 -0500, Michael Sacco wrote:
This is going to sound silly, but I would try enabling power management. I have the ipw2200 in my system, and sometimes it won't work unless I have the power management on. It can be turned on by using the following command:
iwconfig eth1 power on
A quick type of "iwconfig eth1" afterwards should show that the command took
stays on for a second and back to off
This is going to sound silly, but I would try enabling power management. I have the ipw2200 in my system, and sometimes it won't work unless I have
Strange... Well, if I were you guys, and I really wanted it up and running, I would download the ndiswrapper and use that module then. I had to set that up when I was using 9.1 because the ipw2200 was not supported out of the box. http://ndiswrapper.sourceforge.net/ is the website, and there is pretty straight-forward documentation. The install is relatively quick, you don't need to recompile the kernel. Rather, you just compile the module for the kernel you are already using. Testing this will also help pin down what the problem is. If ndiswrapper works, then it's most likely the ipw2100 module. If ndiswrapper does not work, then it's most likely a setup issue. Mike Sacco -----Original Message----- From: boricua Orman [mailto:boricua@pepino.is-a-geek.org] Sent: Tuesday, November 23, 2004 7:14 PM To: Michael Sacco Cc: suse Subject: RE: [SLE] wireless card ipw2100 On Tue, 2004-11-23 at 00:29 -0500, Michael Sacco wrote: the
power management on. It can be turned on by using the following command:
iwconfig eth1 power on
A quick type of "iwconfig eth1" afterwards should show that the command took
stays on for a second and back to off -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
2100 not there http://ndiswrapper.sourceforge.net/wiki/index.php/List On Wed, 2004-11-24 at 00:47 -0500, Michael Sacco wrote:
Strange...
Well, if I were you guys, and I really wanted it up and running, I would download the ndiswrapper and use that module then. I had to set that up when I was using 9.1 because the ipw2200 was not supported out of the box. http://ndiswrapper.sourceforge.net/ is the website, and there is pretty straight-forward documentation. The install is relatively quick, you don't need to recompile the kernel. Rather, you just compile the module for the kernel you are already using.
Testing this will also help pin down what the problem is. If ndiswrapper works, then it's most likely the ipw2100 module. If ndiswrapper does not work, then it's most likely a setup issue.
Mike Sacco
-----Original Message----- From: boricua Orman [mailto:boricua@pepino.is-a-geek.org] Sent: Tuesday, November 23, 2004 7:14 PM To: Michael Sacco Cc: suse Subject: RE: [SLE] wireless card ipw2100
This is going to sound silly, but I would try enabling power management. I have the ipw2200 in my system, and sometimes it won't work unless I have
On Tue, 2004-11-23 at 00:29 -0500, Michael Sacco wrote: the
power management on. It can be turned on by using the following command:
iwconfig eth1 power on
A quick type of "iwconfig eth1" afterwards should show that the command took
stays on for a second and back to off
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (5)
-
boricua Orman
-
boricua@pepino.is-a-geek.org
-
Jeffrey L. Taylor
-
Michael Sacco
-
Richard