the removal of ieee80211_tx_frame in kernel 2.6.27 makes it impossible to compile ipw3945.
ipw was deprecated in favor of iwl in kernel back in the .24/.25 days. (I don't have any direct documentation but google for "ipw3945 deprecated" will show you the same info) IMHO, RESO:IVALID, use iwl in kernel.
If that's the case then maybe it should slap some sort of deprecation warning on users who try to install it.
Sure. We could probably just die with "Use iwl in the kernel instead, see http://whatever for details" if someone tries to install for kernel >=2.6.27, and ewarn for >=2.6.26. Does anyone know of any good migration docs for ipw -> iwl? I know it's not really a complicated process (Turn on the appropriate knob in the kernel, emerge iwl3945-ucode, rinse, repeat), but it may be good to help folks out more explicitly.
(In reply to comment #1) > ipw was deprecated in favor of iwl in kernel back in the .24/.25 days. indeed, but, from all accounts, it suffered from many issues, which is why many people (including me) didn't want to migrate (yet). if ipw3945 is also deprecated in gentoo, then the ebuild should make it clear that it is no longer supported as of 2.6.27, and that people must migrate to iwl or stay with a kernel <= 2.6.26.
FTR, I've switched to iwl3945. It universally works better than ipw at this point, on all my hardware.
(In reply to comment #3) > Sure. We could probably just die with "Use iwl in the kernel instead, see > http://whatever for details" if someone tries to install for kernel >=2.6.27, > and ewarn for >=2.6.26. Fine with me. > Does anyone know of any good migration docs for ipw -> iwl? There's none, AFAIK. We want users to unmerge ipw3945{,d,-ucode} and install iwl3945-ucode. I believe there's no need to change baselayout's configuration, as the device name should be handled by udev based on the MAC address which doesn't change.
(In reply to comment #5) > FTR, I've switched to iwl3945. It universally works better than ipw at this > point, on all my hardware. > Agreed. I depart from this bug now. My 2 cents are in =)
Great that it works well for you. In my case, it's quite the opposite. The driver has A LOT of bugs. My card is always in deep sleep (makes me want to break the computer when it happens /_all the time_), doesn't reconnect to the access point if the router reboots, etc etc etc. I wish the good old ipw3945 would just work in kernels >2.6.27. if anyone knows about a patch to make it work again, please tell... I just don't understand how on earth can the ipw driver work flawlessly for me, and all the newer iwl releases be... well... crap.
Luis, unless you report your findings at their Bugzilla [1], your problem won't be fixed. We (the ipw3945 maintainers in Gentoo) are not kernel hackers, so we can't really fix it for you. Merry Christmas with a working wireless :) [1] http://www.intellinuxwireless.org/bugzilla/
Created attachment 177044 [details] Patch to make ipw3945 work with kernels >=2.6.27
Suffering from a lot of issues with iwl3945 here, periodic disconnects from my AP and low bandwidth, so ipw3945 is still the way to go for me. Going to try helping the iwl-devs with some debug info, but until it's fixed I need ipw3945. I've found a patch that just adds the code removed in 2.6.27 to ipw3945.c instead which makes it work and attached it to the bug.
Sorry this took so long, but I finally added this to ipw3945-1.2.2-r1 Thanks for the patch, and I hope the real iwl driver starts working for you soon!
