ipw3945 alternative: Intel's iwlwifi

Message

morbus · Post by **morbus** » Wed Feb 14, 2007 8:07 pm

First thing: Change uname -r into ${KV_FULL} in src_install. This could install into non-existant/non-relevant directories.

rmh3093 · Post by **rmh3093** » Wed Feb 14, 2007 8:20 pm

morbus wrote:First thing: Change uname -r into ${KV_FULL} in src_install. This could install into non-existant/non-relevant directories.

ok done

morbus · Post by **morbus** » Thu Feb 15, 2007 7:22 am

I couldn't find the fix-headers patch in your overlay so I couldn't further test it.

P.S.: You have to check whether NEW_LEDS is enabled, else loading the 80211 module will fail due to unresolved symbols. So just add

Code: Select all

pkg_setup() {
	if use led; then
		local CONFIG_CHECK="NEW_LEDS"
		local NEW_LEDS_ERROR="In order to use the Leds you have to enable NEW_LEDS and recompile your kernel!"
	fi
	
	linux-mod_pkg_setup
}

In your d80211 ebuild.

Lloeki · Post by **Lloeki** » Thu Feb 15, 2007 8:43 am

I couldn't find the fix-headers patch in your overlay so I couldn't further test it.

same here.

Code: Select all

>>> /usr/src/d80211/aes_ccm.h

wow, now headers are instelled in /usr/src? how unexpected. why so?

Lloeki · Post by **Lloeki** » Thu Feb 15, 2007 9:09 am

after some checks, not only headers are installed in /usr/src (I really don't think they belong to here), but some are now installed in the kernel tree...

Code: Select all

--- /lib/modules/2.6.19-suspend2-r2/source/
--- /lib/modules/2.6.19-suspend2-r2/source/include/
--- /lib/modules/2.6.19-suspend2-r2/source/include/net/
>>> /lib/modules/2.6.19-suspend2-r2/source/include/net/d80211_common.h
>>> /lib/modules/2.6.19-suspend2-r2/source/include/net/d80211.h
>>> /lib/modules/2.6.19-suspend2-r2/source/include/net/d80211_mgmt.h
>>> /lib/modules/2.6.19-suspend2-r2/source/include/net/d80211_shared.h
--- /lib/modules/2.6.19-suspend2-r2/source/include/linux/
>>> /lib/modules/2.6.19-suspend2-r2/source/include/linux/ieee80211.h

this, IMHO, can lead to problems. esp if we consider that at least one of the files already exist:

# tar tvjf linux-2.6.19.tar.bz2 |grep ieee80211.h
-rw-r--r-- git/git 1827 2006-11-29 22:57 linux-2.6.19/drivers/net/wireless/zd1211rw/zd_ieee80211.h
-rw-r--r-- git/git 38759 2006-11-29 22:57 linux-2.6.19/include/net/ieee80211.h

and that they differ by many defs. (just diff them, you'll see).

morbus · Post by **morbus** » Thu Feb 15, 2007 9:21 am

Mmh. As you can see (in scripts/patch_kernel) the way intended by Intel is indeed to install all the headers in the linux sources. So I'm wondering whether we shouldn't do the same, even if it's bad style...

Lloeki · Post by **Lloeki** » Thu Feb 15, 2007 12:42 pm

had I wanted to touch the kernel source, I would have run 'make patch_kernel', which works just fine...
had I wanted an ebuild to touch the kernel tree, I'd wrap make patch_kernel into it, and not spending time messing with our own hack.
the kind of 'overlapping' I mentioned above is enough to warrant a block in any other ebuild. it was also why we despised the ieee80211 ebuilds that required intervention in the kernel source.

therefore, I suggest that either we make a 'clean' ebuild, or wait for d80211 to come in -mm and vanilla, and depend on correct kernel config in iwlwifi ebuilds (like ipw3945 1.2.0 which depends on in-kernel ieee80211) and cope with manually patching the tree till then.

rmh3093 · Post by **rmh3093** » Thu Feb 15, 2007 2:44 pm

i put it in the kernel source for now because that was the only way I could get things working smoothly... it dosent have to stay that way.... any help/suggestions are welcome as always

EDIT: I wanted to make it functional before I worried about making it pretty.

rmh3093 · Post by **rmh3093** » Thu Feb 15, 2007 3:21 pm

morbus wrote:I couldn't find the fix-headers patch in your overlay so I couldn't further test it.

oops, must have forgot to add that file before committing... its there now

morbus wrote:P.S.: You have to check whether NEW_LEDS is enabled, else loading the 80211 module will fail due to unresolved symbols. So just add
Code: Select all
pkg_setup() {
	if use led; then
		local CONFIG_CHECK="NEW_LEDS"
		local NEW_LEDS_ERROR="In order to use the Leds you have to enable NEW_LEDS and recompile your kernel!"
	fi
	
	linux-mod_pkg_setup
}

Added in d80211-1.0.1-r2

rmh3093 · Post by **rmh3093** » Thu Feb 15, 2007 4:38 pm

has anyone actually authenticated with an AP yet with this driver? I can see all sorts of networks in networkmanager or using 'iwlist scan' but they have no signal strength

morbus · Post by **morbus** » Thu Feb 15, 2007 5:01 pm

Yeah I have. And the ebuilds in your overlay work at least compile cleanly.

I think you have to set channel, essid and the ap's mac address manually. you have to bring up your device manually. and then repeat these steps in a random order until the authentication succeeds *g*. But the bandwidth is for some reason way too low for me ATM.

rmh3093 · Post by **rmh3093** » Thu Feb 15, 2007 5:11 pm

morbus wrote:Yeah I have. And the ebuilds in your overlay work at least compile cleanly.

I think you have to set channel, essid and the ap's mac address manually. you have to bring up your device manually. and then repeat these steps in a random order until the authentication succeeds *g*. But the bandwidth is for some reason way too low for me ATM.

yeah i can authenticate and get an IP with dhcpcd but no more communication after that, I also cant connect in 802.11g mode, only b, and after I get my IP addy the rate drops to 1Mbs

rmh3093 · Post by **rmh3093** » Thu Feb 15, 2007 10:21 pm

ok the latest revision of the d80211 ebuild DOES NOT touch /usr/src/linux, and iwlwifi complies with the headers in /usr/include/d80211

aslvrstn · Post by **aslvrstn** » Fri Feb 16, 2007 3:17 am

iwlwifi and all dependencies compiled correctly, but whenever I try to modprobe d80211 or iwlwifi, I get "Module not found". What am I doing wrong?

rmh3093 · Post by **rmh3093** » Fri Feb 16, 2007 3:34 am

is your /usr/src/linux symlink pointing to the kernel you are running

Lloeki · Post by **Lloeki** » Fri Feb 16, 2007 7:10 am

ok the latest revision of the d80211 ebuild DOES NOT touch /usr/src/linux, and iwlwifi complies with the headers in /usr/include/d80211

Tested: ebuilds work for me.
Thanks A LOT rmh3093

EDIT: driver seems to work if I rmmod ipw3945 (ie ipw3945(d) already init'd the card), but hardlocks if modprobe'd first. thankfully, udev-104-r10 seems to makes modules blacklistable again (http://gentoo-portage.com/sys-fs/udev/ChangeLog#ptabs on 10 Feb, see bug #130766 too)

VinzC · Post by **VinzC** » Fri Feb 16, 2007 10:13 am

Lloeki wrote:thankfully, udev-104-r10 seems to makes modules blacklistable again (http://gentoo-portage.com/sys-fs/udev/ChangeLog#ptabs on 10 Feb, see bug #130766 too)

That *is* good news. Do you know if the modprobe wrapper also happens to take care of module insertion/removal instructions like in /etc/modules.d/ipw3945d?

morbus · Post by **morbus** » Fri Feb 16, 2007 11:02 am

iwlwifi-0.0.8 (just rename the ebuild) was release and I'm writing this post using the iwlwifi driver!

The bandwith still dropped to 1Mb/s but it's at least usable...

rmh3093 · Post by **rmh3093** » Fri Feb 16, 2007 12:40 pm

those warnings you getr when you build wilwifi is becase d80211 is build out of kernel tree.... idk how to get rid of them.... it has to do with .tmp_version

rmh3093 · Post by **rmh3093** » Fri Feb 16, 2007 6:29 pm

morbus wrote:iwlwifi-0.0.8 (just rename the ebuild) was release and I'm writing this post using the iwlwifi driver!

The bandwith still dropped to 1Mb/s but it's at least usable...

forgot to commit that last night damn, already had an 0.0.8 ebuild.... both d80211 and iwlwifi ebuilds have debugging support now too

Lloeki · Post by **Lloeki** » Sat Feb 17, 2007 12:06 pm

VinzC wrote:Do you know if the modprobe wrapper also happens to take care of module insertion/removal instructions like in /etc/modules.d/ipw3945d?

that never stopped working for me.

rmh3093 wrote:WARNING: "ieee80211_free_hw" [/var/tmp/portage/net-wireless/iwlwifi-0.0.7/work/iwlwifi-0.0.7/compatible/iwlwifi.ko] undefined!

Code: Select all

WARNING: "ieee80211_free_hw" [/var/tmp/portage/net-wireless/iwlwifi-0.0.7/work/iwlwifi-0.0.7/compatible/iwlwifi.ko] undefined!

those warnings? you have the same kind when you build some ipw3945 versions with external ieee80211. ipw3945 ebuild has a ewarn/einfo that says 'don't care'.

rmh3093 · Post by **rmh3093** » Sat Feb 17, 2007 12:51 pm

so are the location of all the files OK for everyone?

Lloeki · Post by **Lloeki** » Sat Feb 17, 2007 1:03 pm

fine by me. again, many thanks for the hard work rmh3093.

rmh3093 · Post by **rmh3093** » Sat Feb 17, 2007 1:10 pm

Lloeki wrote:fine by me. again, many thanks for the hard work rmh3093.

well you guys should all turn on debugging and and jump in the #ipw2100 freenode channel and help them fix the rate drop

aslvrstn · Post by **aslvrstn** » Wed Feb 28, 2007 7:19 pm

So I've had everything compiled for a while, and I've been playing around with it for the past week, but, depending on how lucky I am, I can only get to either modprobing iwlwifi, sometimes able to scan for APs, but I can never associate. If anyone could post a recap, it would be greatly appreciated.