rt2x00-cvs-2008031110 on kernel 2.6.24.3

Live forum: http://rt2x00.serialmonkey.com/viewtopic.php?t=4665

slops

11-03-2008 18:54:18

I am running fc7 with kernel 2.6.24.3 installed. I am trying to get the above listed drivers to work with my rt2870 usb device. I am getting the following errors when compiling. I have gone in to the config file an removed every thing except for the

# Enable rt2x00 support
CONFIG_RT2X00=y
# Enable rt2x00 debug output
CONFIG_RT2X00_DEBUG=y
# Enable rt2x00 debugfs support
CONFIG_RT2X00_LIB_DEBUGFS=y
# Enable rt2x00 asm file creation
CONFIG_RT2X00_ASM=n

and the

# Enable rt2800usb support
CONFIG_RT2800USB=y
# Enable rt2800usb leds support (requires mac80211 leds)
CONFIG_RT2800USB_LEDS=n

portion of the file. When i do ./config i get nothing back. Then i do a make and this is what i get

CC [M] /root/rt2x00-cvs-2008031110/rt2800usb.o
In file included from /root/rt2x00-cvs-2008031110/rt2800usb.c36
/root/rt2x00-cvs-2008031110/rt2x00.h363 error field ‘conf’ has incomplete typ
e
/root/rt2x00-cvs-2008031110/rt2x00.h390 warning ‘struct ieee80211_vif’ declar
ed inside parameter list
/root/rt2x00-cvs-2008031110/rt2x00.h390 warning its scope is only this defini
tion or declaration, which is probably not what you want
/root/rt2x00-cvs-2008031110/rt2x00.h In function ‘vif_to_intf’
/root/rt2x00-cvs-2008031110/rt2x00.h392 error dereferencing pointer to incomp
lete type
/root/rt2x00-cvs-2008031110/rt2x00.h At top level
/root/rt2x00-cvs-2008031110/rt2x00.h442 error field ‘band’ has incomplete typ
e
/root/rt2x00-cvs-2008031110/rt2x00.h666 error ‘IEEE80211_NUM_BANDS’ undeclare
d here (not in a function)
/root/rt2x00-cvs-2008031110/rt2x00.h667 error field ‘curr_band’ has incomplet
e type
/root/rt2x00-cvs-2008031110/rt2x00.h990 warning ‘struct ieee80211_vif’ declar
ed inside parameter list
/root/rt2x00-cvs-2008031110/rt2x00.h998 warning ‘struct ieee80211_vif’ declar
ed inside parameter list
/root/rt2x00-cvs-2008031110/rt2800usb.c In function ‘rt2800usb_init_registers’
/root/rt2x00-cvs-2008031110/rt2800usb.c684 error ‘AGGREGATION_SIZE’ undeclare
d (first use in this function)
/root/rt2x00-cvs-2008031110/rt2800usb.c684 error (Each undeclared identifier is reported only once
/root/rt2x00-cvs-2008031110/rt2800usb.c684 error for each function it appears in.)
/root/rt2x00-cvs-2008031110/rt2800usb.c In function ‘rt2800usb_set_state’
/root/rt2x00-cvs-2008031110/rt2800usb.c958 error ‘AUTO_WAKEUP_CFG’ undeclared (first use in this function)
/root/rt2x00-cvs-2008031110/rt2800usb.c In function ‘rt2800usb_init_eeprom’
/root/rt2x00-cvs-2008031110/rt2800usb.c1100 error ‘RT2870’ undeclared (first use in this function)
/root/rt2x00-cvs-2008031110/rt2800usb.c In function ‘rt2800usb_beacon_update’
/root/rt2x00-cvs-2008031110/rt2800usb.c1422 error ‘struct ieee80211_tx_contro l’ has no member named ‘vif’
/root/rt2x00-cvs-2008031110/rt2800usb.c At top level
/root/rt2x00-cvs-2008031110/rt2800usb.c1488 warning initialization from incom patible pointer type
/root/rt2x00-cvs-2008031110/rt2800usb.c1492 error unknown field ‘bss_info_cha nged’ specified in initializer
/root/rt2x00-cvs-2008031110/rt2800usb.c1492 warning initialization from incom patible pointer type
make[2] *** [/root/rt2x00-cvs-2008031110/rt2800usb.o] Error 1
make[1] *** [_module_/root/rt2x00-cvs-2008031110] Error 2
make *** [default] Error 2

any help with this would be greatly appreciated
Thanks
Simon

IvD

11-03-2008 19:14:02

http//rt2x00.serialmonkey.com/phpBB2/v ... ght=rt2800

slops

12-03-2008 13:22:18

I have tried those drivers as well and am not able to get them working. Can some one help me. I need to get the card working in monitor mode for now.

Thanks

IvD

12-03-2008 13:44:28

Have you actually _read_ the thread I pointed to you?

This project currently has _NO_ drivers for rt2860 or rt2870.
If you want support for the drivers from the RALINK website then go to the RALINK website and ask support there.

slops

14-04-2008 15:40:22

Is there any update getting the RT2870usb working yet? Sorry to be a pain about this.

IvD

14-04-2008 15:49:09

As you might have noticed No announcements about support has been made yet, from which you can conclude the previous message regarding "currently not supported, but we are working on it" is still in effect.