{"id":27,"date":"2006-05-14T06:21:00","date_gmt":"2006-05-14T11:21:00","guid":{"rendered":"http:\/\/www.rajatswarup.com\/blog\/?p=27"},"modified":"2010-02-10T23:56:30","modified_gmt":"2010-02-11T04:56:30","slug":"inspiron-700m-wireless-configuration-on-kubuntu","status":"publish","type":"post","link":"https:\/\/www.rajatswarup.com\/blog\/2006\/05\/14\/inspiron-700m-wireless-configuration-on-kubuntu\/","title":{"rendered":"Inspiron 700m Wireless configuration on Kubuntu"},"content":{"rendered":"<p>I have a Dell Inspiron 700m.  I have Kubuntu Breezy Badger 5.10 on this box.<br \/>This is how I got the WiFi going on this beauty.<br \/>1. Boot up into windows and get the Intel Driver from <a href=\"http:\/\/downloadfinder.intel.com\/scripts-df-external\/confirm.aspx?ftpDown=ftp:\/\/aiedownload.intel.com\/df-support\/10112\/eng\/Intel%28R%29PROSetWirelessSoftwareVer9.0.4.exe&#038;agr=N&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;ProductID=1784&#038;DwnldId=10112&amp;strOSs=All&#038;OSFullName=All%20Operating%20Systems%E2%8C%A9=eng\">Intels 1st site<\/a> OR <a href=\"http:\/\/downloadfinder.intel.com\/scripts-df-external\/confirm.aspx?httpDown=http:\/\/aiedownload.intel.com\/df-support\/10112\/eng\/Intel%28R%29PROSetWirelessSoftwareVer9.0.4.exe&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;agr=N&#038;ProductID=1784&amp;DwnldId=10112&#038;strOSs=All&amp;OSFullName=All%20Operating%20Systems%E2%8C%A9=eng\">Intels 2nd site<\/a><\/p>\n<p>2. Save the files into a location on the drive which is accessible through linux.<br \/><span style=\";font-family:courier new;font-size:85%;\"  ><\/p>\n<hr \/>\n<p>root@trance:\/home\/trance# ls -al \/media\/hda1\/intel\/wireless_9.0.4_generic_109116\/Drivers\/<br \/>total 8680<br \/>dr-x&#8212;&#8212;  1 root root    4096 2006-05-14 05:42 .<br \/>dr-x&#8212;&#8212;  1 root root    4096 2006-05-14 05:42 ..<br \/>-r&#8212;&#8212;&#8211;  1 root root  188416 2005-12-27 23:53 SetupWLD.EXE<br \/>-r&#8212;&#8212;&#8211;  1 root root    4849 2005-01-25 15:17 SetupWLD.ini<br \/>-r&#8212;&#8212;&#8211;  1 root root      13 2006-02-02 12:38 verfile.tic<br \/>-r&#8212;&#8212;&#8211;  1 root root 1671168 2006-01-27 08:50 W29MLRES.DLL<br \/>-r&#8212;&#8212;&#8211;  1 root root 2956544 2006-01-17 21:34 w29n50.sys<br \/>-r&#8212;&#8212;&#8211;  1 root root   14821 2006-02-02 00:47 w29n51.cat<br \/>-r&#8212;&#8212;&#8211;  1 root root  119785 2006-01-18 15:47 w29n51.INF<br \/>-r&#8212;&#8212;&#8211;  1 root root 3325312 2006-01-17 21:32 w29n51.sys<br \/>-r&#8212;&#8212;&#8211;  1 root root  466944 2006-01-27 08:49 W29NCPA.DLL<br \/>-r&#8212;&#8212;&#8211;  1 root root  122880 2005-12-27 23:53 WLDMLRES.DLL<br \/>root@trance:\/home\/trance#                            <\/span>     <\/p>\n<hr \/>\n<p>3. Go back into Kubuntu and get the ndiwrapper-utils, ndisgtk, ndiswrapper-source using<br \/><span style=\"font-size:85%;\"><\/p>\n<hr \/>\n<p>root@trance:\/home\/trance# sudo apt-get install ndiswrapper ndisgtk ndiswrapper-source<\/span><\/p>\n<hr \/>\n<p>4.  As root ndiswrapper -i will use the windows inf file to install the wireless driver.  ndiswrapper -l lists the driver installed.<location_of_inf_file><br \/>example:<br \/><span style=\"font-size:85%;\"><\/p>\n<hr \/>\n<p>root@trance:\/home\/trance# ndiswrapper -i \/media\/hda1\/intel\/wireless_9.0.4_generic_109116\/Drivers\/w29n51.INF<\/span><br \/><span style=\"font-size:85%;\">root@trance:\/home\/trance# ndiswrapper -l<br \/>Installed ndis drivers:<br \/>w29n51  driver present, hardware present<br \/>root@trance:\/home\/trance#                <\/span><br \/><\/location_of_inf_file><\/p>\n<hr \/>\n<p>5. <span style=\"font-size:85%;\"><span style=\"font-size:100%;\">modprobe ndiswrapper checks if the ndiswrapper kernel module is installed.  An installed module will result in no error.  Then write the config file such that you do not need to go through the earlier steps every time you restart the system.<\/p>\n<p><\/span><\/p>\n<hr \/>\n<p>root@trance:\/home\/trance# modprobe ndiswrapper<br \/>root@trance:\/home\/trance# ndiswrapper -m<br \/>Adding &#8220;alias wlan0 ndiswrapper&#8221; to \/etc\/modprobe.d\/ndiswrapper<\/span><\/p>\n<hr \/>\n<p>6. If some error occurs check the  output of lsmod<br \/><span style=\"font-size:85%;\"><span style=\"font-size:100%;\"><\/span><\/p>\n<hr \/>\n<p>root@trance:\/home\/trance# lsmod | grep ndiswrapper<\/span><\/p>\n<hr \/>\n<p>7. Now that your ndiswrapper is installed and configured.  We now need to start up the wireless interface.  On my box the wireless interface used to show up as eth0, however, it was not configured to use the ndiswrapper so I would get &#8216;segmentation fault&#8217; on doing ifup eth0.<br \/>However, with the drivers set, I checked if all was well.<br \/><span style=\"font-size:85%;\"><\/p>\n<hr \/>\n<p>root@trance:\/home\/trance# iwconfig<br \/>lo        no wireless extensions.<\/p>\n<p>eth1      no wireless extensions.<\/p>\n<p>eth0      IEEE 802.11g  ESSID:&#8221;MySSID&#8221;<br \/>    Mode:Managed  Frequency:2.437 GHz  Access Point: 00:13:46:46:78:28<br \/>    Bit Rate=54 Mb\/s   Tx-Power=20 dBm<br \/>    Retry limit:7   RTS thr:off   Fragment thr:off<br \/>    Encryption key:XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX   Security mode:open<br \/>    Power Management:off<br \/>    Link Quality=97\/100  Signal level=-27 dBm  Noise level=-89 dBm<br \/>    Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0<br \/>    Tx excessive retries:0  Invalid misc:0   Missed beacon:0<\/p>\n<p>sit0      no wireless extensions.<br \/>root@trance:\/home\/trance# ifconfig<br \/>eth0      Link encap:Ethernet  HWaddr 00:13:CE:D9:0D:74<br \/>     inet6 addr: fe80::213:ceff:fed9:d74\/64 Scope:Link<br \/>     UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1<br \/>     RX packets:48 errors:0 dropped:0 overruns:0 frame:0<br \/>     TX packets:1 errors:0 dropped:0 overruns:0 carrier:0<br \/>     collisions:0 txqueuelen:1000<br \/>     RX bytes:236683 (231.1 KiB)  TX bytes:1104 (1.0 KiB)<br \/>     Interrupt:10 Base address:0x8000 Memory:e0206000-e0206fff<\/p>\n<p>eth1      Link encap:Ethernet  HWaddr 00:12:3F:6B:36:2F<br \/>     inet addr:192.168.0.109  Bcast:192.168.0.255  Mask:255.255.255.0<br \/>     inet6 addr: fe80::212:3fff:fe6b:362f\/64 Scope:Link<br \/>     UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1<br \/>     RX packets:3050 errors:0 dropped:0 overruns:0 frame:0<br \/>     TX packets:1534 errors:0 dropped:0 overruns:0 carrier:0<br \/>     collisions:0 txqueuelen:1000<br \/>     RX bytes:3117901 (2.9 MiB)  TX bytes:159050 (155.3 KiB)<br \/>     Interrupt:10<\/p>\n<p>lo        Link encap:Local Loopback<br \/>     inet addr:127.0.0.1  Mask:255.0.0.0<br \/>     inet6 addr: ::1\/128 Scope:Host<br \/>     UP LOOPBACK RUNNING  MTU:16436  Metric:1<br \/>     RX packets:33 errors:0 dropped:0 overruns:0 frame:0<br \/>     TX packets:33 errors:0 dropped:0 overruns:0 carrier:0<br \/>     collisions:0 txqueuelen:0<br \/>     RX bytes:2058 (2.0 KiB)  TX bytes:2058 (2.0 KiB)<\/p>\n<p>root@trance:\/home\/trance# ifup eth0<br \/>There is already a pid file \/var\/run\/dhclient.eth0.pid with pid 0<br \/>Internet Systems Consortium DHCP Client V3.0.2<br \/>Copyright 2004 Internet Systems Consortium.<br \/>All rights reserved.<br \/>For info, please visit http:\/\/www.isc.org\/products\/DHCP<\/p>\n<p>sit0: unknown hardware address type 776<br \/>sit0: unknown hardware address type 776<br \/>Listening on LPF\/eth0\/00:13:ce:d9:0d:74<br \/>Sending on   LPF\/eth0\/00:13:ce:d9:0d:74<br \/>Sending on   Socket\/fallback<br \/>DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3<br \/>ip length 328 disagrees with bytes received 332.<br \/>accepting packet with data after udp payload.<br \/>DHCPOFFER from 192.168.0.1<br \/>DHCPREQUEST on eth0 to 255.255.255.255 port 67<br \/>ip length 328 disagrees with bytes received 332.<br \/>accepting packet with data after udp payload.<br \/>DHCPACK from 192.168.0.1<br \/>bound to 192.168.0.101 &#8212; renewal in 241302 seconds.<br \/>root@trance:\/home\/trance# ifdown eth1<br \/>There is already a pid file \/var\/run\/dhclient.eth1.pid with pid 6390<br \/>killed old client process, removed PID file<br \/>Internet Systems Consortium DHCP Client V3.0.2<br \/>Copyright 2004 Internet Systems Consortium.<br \/>All rights reserved.<br \/>For info, please visit http:\/\/www.isc.org\/products\/DHCP<\/p>\n<p>sit0: unknown hardware address type 776<br \/>sit0: unknown hardware address type 776<br \/>Listening on LPF\/eth1\/00:12:3f:6b:36:2f<br \/>Sending on   LPF\/eth1\/00:12:3f:6b:36:2f<br \/>Sending on   Socket\/fallback<br \/>DHCPRELEASE on eth1 to 192.168.0.1 port 67<br \/>root@trance:\/home\/trance# ping www.google.com<br \/>PING www.l.google.com (64.233.161.99) 56(84) bytes of data.<br \/>64 bytes from 64.233.161.99: icmp_seq=1 ttl=233 time=73.5 ms<br \/>64 bytes from 64.233.161.99: icmp_seq=2 ttl=233 time=51.6 ms<\/p>\n<p>&#8212; www.l.google.com ping statistics &#8212;<br \/>2 packets transmitted, 2 received, 0% packet loss, time 1001ms<br \/>rtt min\/avg\/max\/mdev = 51.688\/62.634\/73.580\/10.946 ms<br \/><\/span><\/p>\n<hr \/>\n<p>8. To make sure that you don&#8217;t have to type iwconfig essid <ssid> key <key> every time you log on. Change you \/etc\/network\/interfaces file to have these few lines at the end of the file.  wireless essid is your wireless network name (SSID) and the key is the WEP key.<\/p>\n<p>iface eth0 inet dhcp<br \/>wireless-essid XXXXXXX<br \/>wireless-key XXXXXXXXXXXXXXXXX<\/p>\n<p>My \/etc\/network\/interfaces of Ubuntu (in FC\/RHL this is the counterpart of the \/etc\/sysconfig\/network-scripts\/ifcfg-ethX)<br \/>looks like:<br \/><span style=\"font-size:85%;\"><\/p>\n<hr \/>\n<p># This file describes the network interfaces available on your system<br \/># and how to activate them. For more information, see interfaces(5).<\/p>\n<p># The loopback network interface<br \/>auto lo<br \/>iface lo inet loopback<\/p>\n<p># This is a list of hotpluggable network interfaces.<br \/># They will be activated automatically by the hotplug subsystem.<br \/>mapping hotplug<br \/>      script grep<br \/>      map eth1<\/p>\n<p># The primary network interface<br \/>auto eth1<br \/>iface eth1 inet dhcp<\/p>\n<p>auto eth0<br \/>allow-hotplug eth0<br \/>iface eth0 inet dhcp<br \/>wireless-essid USC-Trojans<br \/>wireless-key # This file describes the network interfaces available on your system<br \/># and how to activate them. For more information, see interfaces(5).<\/p>\n<p># The loopback network interface<br \/>auto lo<br \/>iface lo inet loopback<\/p>\n<p># This is a list of hotpluggable network interfaces.<br \/># They will be activated automatically by the hotplug subsystem.<br \/>mapping hotplug<br \/>       script grep<br \/>       map eth1<\/p>\n<p># The primary network interface<br \/>auto eth1<br \/>iface eth1 inet dhcp<\/p>\n<p>auto eth0<br \/>allow-hotplug eth0<br \/>iface eth0 inet dhcp<br \/>wireless-essid USC-Trojans<br \/>wireless-key 11111111111111111111111111<br \/><\/span><\/key><\/ssid><\/p>\n<hr \/>\n","protected":false},"excerpt":{"rendered":"<p>I have a Dell Inspiron 700m. I have Kubuntu Breezy Badger 5.10 on this box.This is how I got the WiFi going on this beauty.1. Boot up into windows and get the Intel Driver from Intels 1st site OR Intels 2nd site 2. Save the files into a location on the drive which is accessible [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[230,259],"tags":[299,298,272,468],"class_list":["post-27","post","type-post","status-publish","format-standard","hentry","category-howto","category-wireless","tag-configuration","tag-kubuntu","tag-linux","tag-wireless"],"_links":{"self":[{"href":"https:\/\/www.rajatswarup.com\/blog\/wp-json\/wp\/v2\/posts\/27","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.rajatswarup.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.rajatswarup.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.rajatswarup.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.rajatswarup.com\/blog\/wp-json\/wp\/v2\/comments?post=27"}],"version-history":[{"count":1,"href":"https:\/\/www.rajatswarup.com\/blog\/wp-json\/wp\/v2\/posts\/27\/revisions"}],"predecessor-version":[{"id":144,"href":"https:\/\/www.rajatswarup.com\/blog\/wp-json\/wp\/v2\/posts\/27\/revisions\/144"}],"wp:attachment":[{"href":"https:\/\/www.rajatswarup.com\/blog\/wp-json\/wp\/v2\/media?parent=27"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.rajatswarup.com\/blog\/wp-json\/wp\/v2\/categories?post=27"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.rajatswarup.com\/blog\/wp-json\/wp\/v2\/tags?post=27"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}