View previous topic :: View next topic |
Author |
Message |
VinzC Watchman
Joined: 17 Apr 2004 Posts: 5098 Location: Dark side of the mood
|
Posted: Sat Feb 10, 2007 7:28 pm Post subject: ipw3945 alternative: Intel's iwlwifi |
|
|
Hi.
I created this thread for all those who want to share their experience with Intel's new WiFi driver for Linux. Be aware however that requests for support might not be addressed immediately.
May the (Source)Forge be with you.
Current status
The driver is now fully included in the 2.6.24 branch. All you need from portage is the firmware, net-wireless/iwl3945-ucode.
2008
Since the inclusion into the mainstream kernel branch, the driver can no longer pretend to be experimental... Topic updated.
May, 2007 - Here are update ebuilds, not patches, from Gentoo overlays.
Feb. 13th, 2007 - Let's rock with rmh3093 series of kernel patches (iwlwifi version 0.6) and morbus' ebuild for the microcode: _________________ Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739!
Last edited by VinzC on Wed Mar 19, 2008 9:03 am; edited 4 times in total |
|
Back to top |
|
|
morbus Tux's lil' helper
Joined: 10 May 2004 Posts: 139 Location: Munich
|
|
Back to top |
|
|
Waninkoko Guru
Joined: 13 May 2005 Posts: 549
|
Posted: Sun Feb 11, 2007 12:59 pm Post subject: |
|
|
I installed it but I cannot associate with any AP |
|
Back to top |
|
|
VinzC Watchman
Joined: 17 Apr 2004 Posts: 5098 Location: Dark side of the mood
|
Posted: Sun Feb 11, 2007 1:11 pm Post subject: |
|
|
Waninkoko,
I'd advise to start with unencrypted APs then with WEP then WPA. Which version did you try? Have you noticed any lockups or whatever like Lloeki did? _________________ Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739! |
|
Back to top |
|
|
Waninkoko Guru
Joined: 13 May 2005 Posts: 549
|
Posted: Sun Feb 11, 2007 2:01 pm Post subject: |
|
|
I tried with unencrypted and WEP encrypted APs and I cannot associate. I used 0.05 version. I didn't experience any lockup at the moment.
dmesg says:
Code: | iwlwifi: Detected Intel PRO/Wireless 3945ABG Network Connection
iwlwifi: Channel 14 [2.4Ghz] is Tx only -- skipping.
iwlwifi: Channel 183 [5.2Ghz] is Tx only -- skipping.
iwlwifi: Channel 184 [5.2Ghz] is Tx only -- skipping.
iwlwifi: Channel 185 [5.2Ghz] is Tx only -- skipping.
iwlwifi: Channel 187 [5.2Ghz] is Tx only -- skipping.
iwlwifi: Channel 188 [5.2Ghz] is Tx only -- skipping.
iwlwifi: Channel 189 [5.2Ghz] is Tx only -- skipping.
iwlwifi: Channel 192 [5.2Ghz] is Tx only -- skipping.
iwlwifi: Channel 196 [5.2Ghz] is Tx only -- skipping.
iwlwifi: Channel 7 [5.2Ghz] is Tx only -- skipping.
iwlwifi: Channel 8 [5.2Ghz] is Tx only -- skipping.
iwlwifi: Channel 11 [5.2Ghz] is Tx only -- skipping.
iwlwifi: Channel 12 [5.2Ghz] is Tx only -- skipping.
iwlwifi: Channel 16 [5.2Ghz] is Tx only -- skipping.
iwlwifi: Channel 145 [5.2Ghz] is Tx only -- skipping.
iwlwifi: Channel 149 [5.2Ghz] is Tx only -- skipping.
iwlwifi: Channel 153 [5.2Ghz] is Tx only -- skipping.
iwlwifi: Channel 157 [5.2Ghz] is Tx only -- skipping.
iwlwifi: Channel 161 [5.2Ghz] is Tx only -- skipping.
iwlwifi: Channel 165 [5.2Ghz] is Tx only -- skipping.
iwlwifi: Tunable channels: 13 802.11bg, 23 802.11a channels
iwlwifi: XXXY start rate scale
wmaster0: Selected rate control algorithm 'iwlwifi rate-scale'
eth0: Does not support passive scan, disabled
hwcrypto disabled!
wlan0_rename: starting scan
wlan0_rename: scan completed
wlan0_rename: starting scan
wlan0_rename: scan completed
hwcrypto disabled!
wlan0_rename: Initial auth_alg=0
wlan0_rename: authenticate with AP 00:16:b6:39:88:16
wlan0_rename: authenticate with AP 00:16:b6:39:88:16
wlan0_rename: authenticate with AP 00:16:b6:39:88:16
wlan0_rename: authentication with AP 00:16:b6:39:88:16 timed out |
|
|
Back to top |
|
|
morbus Tux's lil' helper
Joined: 10 May 2004 Posts: 139 Location: Munich
|
Posted: Sun Feb 11, 2007 2:33 pm Post subject: |
|
|
Well I can confirm that it works! Great, but it's kinda slow and... uncomfortable to load! |
|
Back to top |
|
|
morbus Tux's lil' helper
Joined: 10 May 2004 Posts: 139 Location: Munich
|
Posted: Sun Feb 11, 2007 2:37 pm Post subject: |
|
|
Waninkoko wrote: | I tried with unencrypted and WEP encrypted APs and I cannot associate. I used 0.05 version. I didn't experience any lockup at the moment.
|
I don't really know how the driver works, but did you set essid, channel and the AP accordingly? |
|
Back to top |
|
|
Waninkoko Guru
Joined: 13 May 2005 Posts: 549
|
Posted: Sun Feb 11, 2007 3:02 pm Post subject: |
|
|
morbus wrote: | Waninkoko wrote: | I tried with unencrypted and WEP encrypted APs and I cannot associate. I used 0.05 version. I didn't experience any lockup at the moment.
|
I don't really know how the driver works, but did you set essid, channel and the AP accordingly? |
Yes. |
|
Back to top |
|
|
morbus Tux's lil' helper
Joined: 10 May 2004 Posts: 139 Location: Munich
|
Posted: Sun Feb 11, 2007 3:10 pm Post subject: |
|
|
For the folks who want to further test the driver: I made an ebuild for the iwlwifi-ucode:
https://bugs.gentoo.org/show_bug.cgi?id=166356
the d80211 stack and the driver itself are still needed. |
|
Back to top |
|
|
rmh3093 Advocate
Joined: 06 Aug 2003 Posts: 2138 Location: Albany, NY
|
Posted: Sun Feb 11, 2007 5:19 pm Post subject: |
|
|
hmm, cool.... the nic driver compiled for me but d80211 didnt work with the latest -mm sources so I will have to play with that... let you know once I get it all working... maybe i will make kernel patches _________________ Do not meddle in the affairs of wizards, for they are subtle and quick to anger. |
|
Back to top |
|
|
Lloeki Guru
Joined: 14 Jun 2006 Posts: 437 Location: France
|
Posted: Sun Feb 11, 2007 5:42 pm Post subject: |
|
|
just for the sake of completeness, I reiterate here what I said on the other thread:
I wrote: | d80211 patched and built without issues against kernel suspend2-2.6.19-r1, microcode copied in /lib/firmware, driver compiled seemingly without issues, loading it causes a bad lock (keyboard gets stuck, mouse still moves, after some minutes, things (namely, X) start crashing). conclusion: for now, iwlwifi is HIGHLY UNSAFE to use. |
FWIW, I tried it multiple times, with different kernel settings, with both ./load and modprobe, and without luck. but hey, this is 0.0.5
anyway, it'd be great to have a iwlwifi-driver ebuild along with the microcode one. I think the load/unload can easily be 'ported' to gentoo config (/etc/modules.d, and stuff...).
regarding the d80211, this feels harder to make an ebuild, as it's in fact a patch to the kernel source. it's only logical, since it's in the process of being integrated by upstream into vanilla kernel, so I wonder if it's worth working on an ebuild for it. _________________ Moved to using Arch Linux
Life is meant to be lived, not given up...
HOLY COW I'M TOTALLY GOING SO FAST OH F*** |
|
Back to top |
|
|
rmh3093 Advocate
Joined: 06 Aug 2003 Posts: 2138 Location: Albany, NY
|
Posted: Sun Feb 11, 2007 6:09 pm Post subject: |
|
|
Lloeki wrote: | just for the sake of completeness, I reiterate here what I said on the other thread:
I wrote: | d80211 patched and built without issues against kernel suspend2-2.6.19-r1, microcode copied in /lib/firmware, driver compiled seemingly without issues, loading it causes a bad lock (keyboard gets stuck, mouse still moves, after some minutes, things (namely, X) start crashing). conclusion: for now, iwlwifi is HIGHLY UNSAFE to use. |
FWIW, I tried it multiple times, with different kernel settings, with both ./load and modprobe, and without luck. but hey, this is 0.0.5
anyway, it'd be great to have a iwlwifi-driver ebuild along with the microcode one. I think the load/unload can easily be 'ported' to gentoo config (/etc/modules.d, and stuff...).
regarding the d80211, this feels harder to make an ebuild, as it's in fact a patch to the kernel source. it's only logical, since it's in the process of being integrated by upstream into vanilla kernel, so I wonder if it's worth working on an ebuild for it. |
the linux-mod eclass will make this a module for portage in 2 seconds _________________ Do not meddle in the affairs of wizards, for they are subtle and quick to anger. |
|
Back to top |
|
|
numerodix l33t
Joined: 18 Jul 2002 Posts: 743 Location: nl.eu
|
Posted: Sun Feb 11, 2007 8:45 pm Post subject: |
|
|
Wait, what is the point of two drivers for the same card? _________________ undvd - ripping dvds should be as simple as unzip |
|
Back to top |
|
|
Lloeki Guru
Joined: 14 Jun 2006 Posts: 437 Location: France
|
Posted: Sun Feb 11, 2007 9:07 pm Post subject: |
|
|
ipw3945 is three part:
- a microcode (embedded microsystem) that is uploaded on the card, closed source
- a regulatory daemon, closed source
- a kernel driver, open source
it uses the ieee80211 stack
iwl is two part:
- a microcode, closed source
- a kernel driver, open source
it uses the new d80211 stack, which has more generic features centralized
this gives much more room for improvements, bug fixes, general trustness, and future inclusion upstream in vanilla kernel (like for ipw2100/2200 drivers) _________________ Moved to using Arch Linux
Life is meant to be lived, not given up...
HOLY COW I'M TOTALLY GOING SO FAST OH F*** |
|
Back to top |
|
|
numerodix l33t
Joined: 18 Jul 2002 Posts: 743 Location: nl.eu
|
Posted: Sun Feb 11, 2007 9:41 pm Post subject: |
|
|
So is the new stack only used by iwl? I mean will the ipw2100(2200) cards also use it or? _________________ undvd - ripping dvds should be as simple as unzip |
|
Back to top |
|
|
morbus Tux's lil' helper
Joined: 10 May 2004 Posts: 139 Location: Munich
|
|
Back to top |
|
|
rmh3093 Advocate
Joined: 06 Aug 2003 Posts: 2138 Location: Albany, NY
|
|
Back to top |
|
|
VinzC Watchman
Joined: 17 Apr 2004 Posts: 5098 Location: Dark side of the mood
|
Posted: Tue Feb 13, 2007 3:22 pm Post subject: |
|
|
rmh3093, Lord Of Kernel Patches... Respects, man _________________ Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739! |
|
Back to top |
|
|
VinzC Watchman
Joined: 17 Apr 2004 Posts: 5098 Location: Dark side of the mood
|
Posted: Tue Feb 13, 2007 3:31 pm Post subject: |
|
|
As a suggestion, I'm going to centralize all your patches/ebuild submissions from the thread entry. That way everybody can have a clear idea on what's going on, what to do and what version to install. Bear with my available time, however . _________________ Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739! |
|
Back to top |
|
|
rmh3093 Advocate
Joined: 06 Aug 2003 Posts: 2138 Location: Albany, NY
|
Posted: Tue Feb 13, 2007 4:52 pm Post subject: |
|
|
VinzC wrote: | As a suggestion, I'm going to centralize all your patches/ebuild submissions from the thread entry. That way everybody can have a clear idea on what's going on, what to do and what version to install. Bear with my available time, however . |
i have a good ebuild for iwlwifi... and working on one now for d80211, once I should have them working soon (first drafts at least) _________________ Do not meddle in the affairs of wizards, for they are subtle and quick to anger. |
|
Back to top |
|
|
rmh3093 Advocate
Joined: 06 Aug 2003 Posts: 2138 Location: Albany, NY
|
Posted: Tue Feb 13, 2007 6:01 pm Post subject: |
|
|
Ok here are the test ebuilds for iwlwifi,iwlwifi-ucode,d80211....
Code: | svn co http://opensvn.csie.org/rmh3093/iwlwifi |
_________________ Do not meddle in the affairs of wizards, for they are subtle and quick to anger. |
|
Back to top |
|
|
Lloeki Guru
Joined: 14 Jun 2006 Posts: 437 Location: France
|
Posted: Tue Feb 13, 2007 6:12 pm Post subject: |
|
|
d80211 fails at install stage:
Code: | >>> Install d80211-1.0.0 into /var/tmp/portage/net-wireless/d80211-1.0.0/image/ category net-wireless
* Installing compatible/net/d80211/80211 module
install: cannot stat `compatible/net/d80211/80211.ko': No such file or directory
|
whatever, rmh3093, you did a great job. thanks a lot for those ebuilds. _________________ Moved to using Arch Linux
Life is meant to be lived, not given up...
HOLY COW I'M TOTALLY GOING SO FAST OH F*** |
|
Back to top |
|
|
rmh3093 Advocate
Joined: 06 Aug 2003 Posts: 2138 Location: Albany, NY
|
Posted: Tue Feb 13, 2007 6:25 pm Post subject: |
|
|
Lloeki wrote: | d80211 fails at install stage:
Code: | >>> Install d80211-1.0.0 into /var/tmp/portage/net-wireless/d80211-1.0.0/image/ category net-wireless
* Installing compatible/net/d80211/80211 module
install: cannot stat `compatible/net/d80211/80211.ko': No such file or directory
|
whatever, rmh3093, you did a great job. thanks a lot for those ebuilds. |
what arch is your is your pc?
EDIT: do you see it compile the modules or no? _________________ Do not meddle in the affairs of wizards, for they are subtle and quick to anger.
Last edited by rmh3093 on Tue Feb 13, 2007 6:26 pm; edited 1 time in total |
|
Back to top |
|
|
Lloeki Guru
Joined: 14 Jun 2006 Posts: 437 Location: France
|
Posted: Tue Feb 13, 2007 6:25 pm Post subject: |
|
|
x86_64. interesting part seems to be here, right after the last patch:
Code: | + Applying: patches/delayed_work.patch
Add delayed_work structure compatibility.
make: Entering directory `/usr/src/linux-2.6.19-suspend2-r2'
Building modules, stage 2.
MODPOST 0 modules
make: Leaving directory `/usr/src/linux-2.6.19-suspend2-r2'
>>> Source compiled.
|
_________________ Moved to using Arch Linux
Life is meant to be lived, not given up...
HOLY COW I'M TOTALLY GOING SO FAST OH F*** |
|
Back to top |
|
|
rmh3093 Advocate
Joined: 06 Aug 2003 Posts: 2138 Location: Albany, NY
|
Posted: Tue Feb 13, 2007 6:28 pm Post subject: |
|
|
Lloeki wrote: | x86_64. interesting part seems to be here, right after the last patch:
Code: | + Applying: patches/delayed_work.patch
Add delayed_work structure compatibility.
make: Entering directory `/usr/src/linux-2.6.19-suspend2-r2'
Building modules, stage 2.
MODPOST 0 modules
make: Leaving directory `/usr/src/linux-2.6.19-suspend2-r2'
>>> Source compiled.
|
|
what happens if you change "set_arch_to_kernel" to "set_arch_to_portage" or what if you comment out "set_arch_to_kernel" completly _________________ Do not meddle in the affairs of wizards, for they are subtle and quick to anger. |
|
Back to top |
|
|
|