ipw3945 alternative: Intel's iwlwifi

morbus · Posted: Wed Feb 14, 2007 8:07 pm Post subject:

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

rmh3093 · Posted: Wed Feb 14, 2007 8:20 pm Post subject:

morbus · Posted: Thu Feb 15, 2007 7:22 am Post subject:

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

Lloeki · Guru Joined: 14 Jun 2006 Posts: 437 Location: France

Lloeki · Guru Joined: 14 Jun 2006 Posts: 437 Location: France

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...

morbus · Posted: Thu Feb 15, 2007 9:21 am Post subject:

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 · Guru Joined: 14 Jun 2006 Posts: 437 Location: France

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.
_________________
Moved to using Arch Linux
Life is meant to be lived, not given up...
HOLY COW I'M TOTALLY GOING SO FAST OH F***

rmh3093 · Posted: Thu Feb 15, 2007 2:44 pm Post subject:

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.
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger.

rmh3093 · Posted: Thu Feb 15, 2007 3:21 pm Post subject:

rmh3093 · Posted: Thu Feb 15, 2007 4:38 pm Post subject:

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
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger.

morbus · Posted: Thu Feb 15, 2007 5:01 pm Post subject:

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 · Posted: Thu Feb 15, 2007 5:11 pm Post subject:

rmh3093 · Posted: Thu Feb 15, 2007 10:21 pm Post subject:

ok the latest revision of the d80211 ebuild DOES NOT touch /usr/src/linux, and iwlwifi complies with the headers in /usr/include/d80211
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger.

aslvrstn · n00b Joined: 16 Jan 2006 Posts: 31

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 · Posted: Fri Feb 16, 2007 3:34 am Post subject:

is your /usr/src/linux symlink pointing to the kernel you are running
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger.

Lloeki · Guru Joined: 14 Jun 2006 Posts: 437 Location: France

VinzC · Posted: Fri Feb 16, 2007 10:13 am Post subject:

morbus · Posted: Fri Feb 16, 2007 11:02 am Post subject:

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 · Posted: Fri Feb 16, 2007 12:40 pm Post subject:

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
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger.

rmh3093 · Posted: Fri Feb 16, 2007 6:29 pm Post subject:

Lloeki · Guru Joined: 14 Jun 2006 Posts: 437 Location: France

rmh3093 · Posted: Sat Feb 17, 2007 12:51 pm Post subject:

so are the location of all the files OK for everyone?
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger.

Lloeki · Guru Joined: 14 Jun 2006 Posts: 437 Location: France

fine by me. again, many thanks for the hard work rmh3093.
_________________
Moved to using Arch Linux
Life is meant to be lived, not given up...
HOLY COW I'M TOTALLY GOING SO FAST OH F***

rmh3093 · Posted: Sat Feb 17, 2007 1:10 pm Post subject:

aslvrstn · n00b Joined: 16 Jan 2006 Posts: 31

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.