Networking :: IBM T40 wifi... almost there!

Hi,

I am trying to get an IBM T40 laptop working with wireless on DSL 4.2.5. I have identified the card as an Intel 2100B (centrino) card. I downloaded from intel.com the
Win XP drivers and put w70n501.inf w70n501.cat w70n5.sys and w70n51.sys (don't know if I need all of these?) into /home/dsl/wifi

Then I made a script called wlan.sh:

Code Sample

#/bin/sh
ndiswrapper -e w70n501 > /dev/null
ndiswrapper -i /home/dsl/wifi/w70n501.inf
modprobe wlan
modprobe ndiswrapper
sleep 5
iwconfig wlan0 essid homenet
iwconfig wlan0 enc s:XXXXXXXXXXXXX
iwconfig wlan0 enc open

#IP address configuration
ifconfig wlan0 192.168.1.10
route add default gw 192.168.1.1
echo nameserver 192.168.1.1 > /etc/resolv.conf

(from what I've found on the net...)

and it almost works! Here's the error messages I get with the lines:
ifconfig wlan0 192.168.1.10:
SIOCSIFFLAGS: no such device

route add default gw 192.168.1.1:
route: SIOC[ADD|DEL]RT: Network is unreachable

I also see if I type ifconfig that wlan0 is not listed there... why?

Can someone please help me?

First, do you know if the ipw2100 modules in MyDSL work for your card? They're in system. Be sure to read the info file very closely.

Second, did you try DHCP instead of static IP? Works fine with both of my wireless routers. You won't get ifconfig to show wlan0 until you're assigned an IP anyway: "sudo pump -i wlan0".

(You can add your iwconfig commands on one line -- "iwconfig essid NAME enc s:KEY" etc.)

thanks for your quick reply.

1)when you talk about mydsl extension, I suppose that's an alternative solution?

2)pump -i wlan0 returns:
operation failed

and thanks for the tip of 1 line!

Daniel

Quote

1)when you talk about mydsl extension, I suppose that's an alternative solution?

It's generally my first choice because it means someone's already invented that wheel.

Quote

2)pump -i wlan0 returns: operation failed

Start over from scratch and try broadcasting dhcp (pump) and let your router set your IP. Just set up ndiswrapper manually in a terminal so you can check the output so you'll know if your driver has loaded (you can also do ndiswrapper -l to make sure it's right). Then iwconfig to see if you have any errors (I don't know how well Intel 2100 works in DSL, but some cards don't have full functionality). Then pump.

FWIW, I never run scripts blindly or redirect output to /dev/null until I know whatever I'm doing actually works by verifying output in a terminal.

lucky13, thanks for pointing me in the right direction of the mydsl extension. Managed to get it working by reading the info file.

Thanks to you and to tempestuous for making that extension!

Next Page...
original here.