After upgrading to gentoo-sources-2.6.24, I cannot compile net-wireless/rt2500-1.1.0_pre2007071515 : >>> Compiling source in /var/tmp/portage/net-wireless/rt2500-1.1.0_pre2007071515/work/rt2500-cvs-2007071515 ... * Preparing rt2500 module make: Entering directory `/usr/src/linux-2.6.24-gentoo' CC [M] /var/tmp/portage/net-wireless/rt2500-1.1.0_pre2007071515/work/rt2500-cvs-2007071515/Module/rtmp_main.o CC [M] /var/tmp/portage/net-wireless/rt2500-1.1.0_pre2007071515/work/rt2500-cvs-2007071515/Module/mlme.o CC [M] /var/tmp/portage/net-wireless/rt2500-1.1.0_pre2007071515/work/rt2500-cvs-2007071515/Module/connect.o /var/tmp/portage/net-wireless/rt2500-1.1.0_pre2007071515/work/rt2500-cvs-2007071515/Module/rtmp_main.c: In function 'RT2500_probe': /var/tmp/portage/net-wireless/rt2500-1.1.0_pre2007071515/work/rt2500-cvs-2007071515/Module/rtmp_main.c:254: error: implicit declaration of function 'SET_MODULE_OWNER' /var/tmp/portage/net-wireless/rt2500-1.1.0_pre2007071515/work/rt2500-cvs-2007071515/Module/rtmp_main.c: In function 'RT2500_open': /var/tmp/portage/net-wireless/rt2500-1.1.0_pre2007071515/work/rt2500-cvs-2007071515/Module/rtmp_main.c:395: error: 'SA_SHIRQ' undeclared (first use in this function) /var/tmp/portage/net-wireless/rt2500-1.1.0_pre2007071515/work/rt2500-cvs-2007071515/Module/rtmp_main.c:395: error: (Each undeclared identifier is reported only once /var/tmp/portage/net-wireless/rt2500-1.1.0_pre2007071515/work/rt2500-cvs-2007071515/Module/rtmp_main.c:395: error: for each function it appears in.) make[1]: *** [/var/tmp/portage/net-wireless/rt2500-1.1.0_pre2007071515/work/rt2500-cvs-2007071515/Module/rtmp_main.o] Error 1 make[1]: *** Waiting for unfinished jobs.... make: *** [_module_/var/tmp/portage/net-wireless/rt2500-1.1.0_pre2007071515/work/rt2500-cvs-2007071515/Module] Error 2 make: Leaving directory `/usr/src/linux-2.6.24-gentoo' But I succeeded to compile the current CVS version of rt2500 (but I don't know what is the state of this version).
Any mysterious reason why don't you use the in-kernel RT2X00 driver? This sounds like WONTFIX.
Because in-kernel RT2X00 driver doesn't support Ad-hoc mode.
in-kernel RT2X00 driver can't find my AP. I have installed driver rt2500-cvs-daily.tar.gz using overlay ebuild. .[32;01m*.[0m Determining the location of the kernel source code .[32;01m*.[0m Found kernel source directory: .[32;01m*.[0m /usr/src/linux .[32;01m*.[0m Found kernel object directory: .[32;01m*.[0m /lib/modules/2.6.24/build .[32;01m*.[0m Found sources for kernel version: .[32;01m*.[0m 2.6.24 .[32;01m*.[0m Checking for suitable kernel configuration options... .[A.[203C .[34;01m[ .[32;01mok.[34;01m ].[0m >>> Unpacking source... >>> Unpacking rt2500-cvs-daily.tar.gz to /cache/portage/net-wireless/rt2500-1.1.0_pre2008012713/work >>> Source unpacked. >>> Compiling source in /cache/portage/net-wireless/rt2500-1.1.0_pre2008012713/work/rt2500-cvs-2008012713 ... .[32;01m*.[0m Preparing rt2500 module make: Entering directory `/cache/src/linux-2.6.24' CC [M] /cache/portage/net-wireless/rt2500-1.1.0_pre2008012713/work/rt2500-cvs-2008012713/Module/rtmp_main.o CC [M] /cache/portage/net-wireless/rt2500-1.1.0_pre2008012713/work/rt2500-cvs-2008012713/Module/mlme.o CC [M] /cache/portage/net-wireless/rt2500-1.1.0_pre2008012713/work/rt2500-cvs-2008012713/Module/connect.o CC [M] /cache/portage/net-wireless/rt2500-1.1.0_pre2008012713/work/rt2500-cvs-2008012713/Module/sync.o CC [M] /cache/portage/net-wireless/rt2500-1.1.0_pre2008012713/work/rt2500-cvs-2008012713/Module/assoc.o CC [M] /cache/portage/net-wireless/rt2500-1.1.0_pre2008012713/work/rt2500-cvs-2008012713/Module/auth.o CC [M] /cache/portage/net-wireless/rt2500-1.1.0_pre2008012713/work/rt2500-cvs-2008012713/Module/auth_rsp.o CC [M] /cache/portage/net-wireless/rt2500-1.1.0_pre2008012713/work/rt2500-cvs-2008012713/Module/rtmp_data.o CC [M] /cache/portage/net-wireless/rt2500-1.1.0_pre2008012713/work/rt2500-cvs-2008012713/Module/rtmp_init.o CC [M] /cache/portage/net-wireless/rt2500-1.1.0_pre2008012713/work/rt2500-cvs-2008012713/Module/sanity.o CC [M] /cache/portage/net-wireless/rt2500-1.1.0_pre2008012713/work/rt2500-cvs-2008012713/Module/rtmp_wep.o CC [M] /cache/portage/net-wireless/rt2500-1.1.0_pre2008012713/work/rt2500-cvs-2008012713/Module/wpa.o CC [M] /cache/portage/net-wireless/rt2500-1.1.0_pre2008012713/work/rt2500-cvs-2008012713/Module/md5.o CC [M] /cache/portage/net-wireless/rt2500-1.1.0_pre2008012713/work/rt2500-cvs-2008012713/Module/rtmp_tkip.o CC [M] /cache/portage/net-wireless/rt2500-1.1.0_pre2008012713/work/rt2500-cvs-2008012713/Module/rtmp_info.o CC [M] /cache/portage/net-wireless/rt2500-1.1.0_pre2008012713/work/rt2500-cvs-2008012713/Module/rt2x00debug.o CC [M] /cache/portage/net-wireless/rt2500-1.1.0_pre2008012713/work/rt2500-cvs-2008012713/Module/eeprom.o LD [M] /cache/portage/net-wireless/rt2500-1.1.0_pre2008012713/work/rt2500-cvs-2008012713/Module/rt2500.o Building modules, stage 2. MODPOST 1 modules CC /cache/portage/net-wireless/rt2500-1.1.0_pre2008012713/work/rt2500-cvs-2008012713/Module/rt2500.mod.o LD [M] /cache/portage/net-wireless/rt2500-1.1.0_pre2008012713/work/rt2500-cvs-2008012713/Module/rt2500.ko make: Leaving directory `/cache/src/linux-2.6.24' >>> Source compiled. >>> Test phase [not enabled]: net-wireless/rt2500-1.1.0_pre2008012713 >>> Install rt2500-1.1.0_pre2008012713 into /cache/portage/net-wireless/rt2500-1.1.0_pre2008012713/image/ category net-wireless .[32;01m*.[0m Installing rt2500 module .[32;01m*.[0m Preparing file for modules.d ... .[A.[203C .[34;01m[ .[32;01mok.[34;01m ].[0m >>> Completed installing rt2500-1.1.0_pre2008012713 into /cache/portage/net-wireless/rt2500-1.1.0_pre2008012713/image/ strip: x86_64-pc-linux-gnu-strip --strip-unneeded -R .comment lib/modules/2.6.24/net/rt2500.ko .[32;01m*.[0m Updating module dependencies for 2.6.24 ... .[A.[203C .[34;01m[ .[32;01mok.[34;01m ].[0m .[32;01m*.[0m Adding module to moduledb.
this can be fixed by unconditionally replacing SA_SHIRQ with IRQF_SHARED this unconditional change is compatible with 2.6.18 onwards which should be sufficient
quick reminder; 2.6.24 will go stable soon
(In reply to comment #1) > Any mysterious reason why don't you use the in-kernel RT2X00 driver? This > sounds like WONTFIX. > Yes, because it's buggy. Quote from rt2x00.serialmonkey.com: http://rt2x00.serialmonkey.com/wiki/index.php?title=Main_Page#News "News rt2x00 enters mainline kernel - January 2008 Hi All, two days ago, January 24th, Linux Kernel 2.6.24 was released. This is the first mainline kernel that includes (sadly a somewhat buggy) rt2x00 release." From the daily-cvs tarball Changelog: Version: CVS * Tag all (ok, most) log messages with module name. * Handle private ioctls ok when more than one adapter attached. * 2.6 kernels now use /etc/modprobe.d/ralink for module alias. * Forward compatibility for 2.6.24. If the in-kernel rt2x00 was so great, why would they fix rt2500 to compile on 2.6.24 kernels? I've tried it, and it is constantly losing it's connection, then re-establishing the connection, which obviously causes issues with any daemon that has "need net" in it's init script ie named, netmount, mythbackend, ntp-client, ntpd, saslauthd, sshd, etc. runscript.sh doesn't always successfully restart the daemon after the disconnect/reconnect cycles, but that's another issue. I didn't ever have this issue with the rt2500 driver.
WRT comment #6 You can disregard my whinning. Turns out my AP need a firmware upgrade which included ieee802.11i WPA2 compliant code. After that, the in-kernel rt2x00pci driver works perfectly - no more deauthentication/reauthentication cycles. I guess wpa_supplicant has issues with old or non-compliant WPA code on AP base stations.
removed from tree, wontfix
