IwlWifi on Intel 3945 Works better than ipw3945

-
Hmm.. after a long line of trial and errors (and blunders) i am posting this off my wifi connection on my linux boot.. :) on my way in kicking Vista offff my laptop..

anyway, since i plan on doing this all over again, here are the steps:
get the binaries of iwlwifi (http://intellinuxwireless.org/)
iwlwifi-1.2.25.tgz
mac80211-10.0.4.tgz (did not need this)
iwlwifi-3945-ucode-2.14.1.5.tgz

Get the kernel source:
sudo apt-get install kernel-source-2.6.22

unziped the kernel, had to play a bit of stupid tricks such as
sudo ln -s /usr/src/linux-source-2.6.22/ /lib/modules/2.6.22-14-generic/source
+ copy the .config and build files from kernel-header-generic in /usr/src/... to the source directory..
then buidl iwlwifi:
a simple "sudo make",
copy the firmware:
cp iwlwifi-4965-ucode-4.44.1.20/iwlwifi-4965-1.ucode /lib/firmware/
and the same for 3945

sudo make install
blacklisting the ipw3945 driver:
/etc/modprobe.d/blacklist add the line:
blacklist ipw3945

edited my /etc/network/interfaces with:
auto wlan0_rename
iface wlan0_rename inet dhcp
wpa-driver wext
wpa-ssid $(MySSID)
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk $(PSKin Hex)

Replace the $(MySSID) with the SSID
and the $(PSKinHex) is generated by wpa_passphrase [passphrase]

I dont like the name wlan0_rename, I guess i got to do something in udev.. but anyway, leaving it as it is... too late in night+got a shoulder ache :(

Platform: ThinkPad X61
OS: Ubuntu 7.10


The boot seems for somereason takes a bit for ever..
[ 26.398329] PCI: Setting latency timer of device 0000:00:1b.0 to 64
[ 26.539397] IBM TrackPoint firmware: 0x0e, buttons: 3/3
[ 26.557696] input: TPPS/2 IBM TrackPoint as /class/input/input3
[ 60.462181] lp: driver loaded but no devices found
[ 60.528904] Adding 7809472k swap on /dev/sda3. Priority:-1 extents:1 across:
7809472k
[ 60.912183] EXT3 FS on sda6, internal journal
[ 61.476135] kjournald starting. Commit interval 5 seconds
[ 61.487567] EXT3 FS on sda5, internal journal
[ 61.487572] EXT3-fs: mounted filesystem with ordered data mode.
[ 62.178371] ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ
17
[ 62.178498] PM: Writing back config space on device 0000:03:00.0 at offset 1
(was 100102, writing 100106)
[ 62.292507] iwl3945: Tunable channels: 11 802.11bg, 13 802.11a channels
[ 62.487276] NET: Registered protocol family 17
[ 64.193798] wlan0_rename: Initial auth_alg=0
[ 64.193802] wlan0_rename: authenticate with AP XYZ....

that is like a 40 second sleep.. :( darn..

LEDs dont blink either..

Comments

Anonymous said…
Hey man, post about OMAP 3440!
2:47 PM CST
Nishanth Menon said…
Julio,
your wish is my command... watch out for my posts ahead..
8:58 PM CST
Anonymous said…
Go to https://help.ubuntu.com/community/WifiDocs/Driver/iwlwifi_Intel_3945_4965/gutsy
for help on reconfiguring udev as well
5:24 AM CST
Nishanth Menon said…
Marlin, Many thanks... i did seem to have missed the persistent-rules part..
5:38 AM CST
Post a Comment

Popular posts from this blog

simpler alternative to minicom

-
Tired of setting up and switching ports in minicom and want something simple? welcome to picocom setup a script such as ~/bin/ttyUSB0 picocom -f n -p n -b 115200 -i -r -l /dev/ttyUSB0 and next time, just run ttyUSB0 and viola u have a terminal.. ctrl+a followed by ctrl+q quits..
Read more

Quick and Dirty userspace testing of regulator with virtual consumer

-
Writing a driver for a new regulator is usually fun, until you need to test the darned thing. Many of the users of the regulator is probably not yet ready in an development environment and need to test cant wait. I had recently a similar situation and found CONFIG_REGULATOR_VIRTUAL_CONSUMER You'd probably register and provide and regulator supply, but without a driver using it in a controlled environment (read shell script or so), it is hard to poke holes completely into your driver. Steps are rather simple. Assumption - you already have a regulator registered in the system and you are aware of the regulator name - You can also figure out it's name by the following (an example from 3.9-rc8 on Beagle-XM): # head /sys/class/regulator/*/name ==> /sys/class/regulator/regulator.0/name /sys/class/regulator/regulator.1/name /sys/class/regulator/regulator.2/name /sys/class/regulator/regulator.3/name /sys/class/regulator/regulator.4/name /sys/class/regulator/regulator.5/...
Read more

Setting up Email forwarding System for GIT

-
Image
The post is a derivative of the omapzoom wiki page . Disclaimer: my mastery of the wiki tags are dismal.. apologies... some day i hope to have time to post it here Many new developers have been stumped when they need to use git-send-email in corporate environment – usually, if not as a norm, ms exchange servers form the backbone of such an email server system. This page was written based on one of such requirements. To get started, we shall consider common scenarios: a) Setting up a mail forwarding system with postfix on ubuntu b) Setting up a mail forwarding system on a fedora machine c) Using msmtp for using gmail a. to send a patch using a gmail ID b. to send a patch using your corporate ID but through gmail Postfix on Ubuntu – mail forwarding For setting up postfix, you need: a) A mail relay server which will allow your machine to talk to it -> speak to your IT representatives/ other developers sitting next to you b) Super user privileges on the machine you are working on. Step...
Read more