Linksys WUSB600N ver. 2

[Mickey]

fedora 13

A Linksys  wireless WUSB600 ver. 2

Does anyone know about a Driver for this device , in all wireless sites 
they say a ver.1 is supported but not ver. 2 ?

[JD]

On 08/07/2010 03:56 PM, [e-mail] wrote:
> fedora 13
>
> A Linksys  wireless WUSB600 ver. 2
>
> Does anyone know about a Driver for this device , in all wireless sites
> they say a ver.1 is supported but not ver. 2 ?

The  Linksys WUSB600N  driver is available in the unsupported
section of the vanilla kernel.
The chipset in the WUSB600N is the RalinkTech 2860, so the driver
is the rt2860.

To try it (and I doubt very much it will work), you need to get the 
source rpm
of your kernel version, and configure it manually (make xconfig) and
select the rt2860 from the "staging" drivers.

I myself have the rt2860 mini-pci wireless card. But I am using a version
of the driver from a much earlier kernel (not from the ralink web site),
and it works just fine.

If you want it, I can email you the zipped tarball.

JD

[Ed Greshko]

On 08/08/2010 08:51 AM, JD wrote:
> On 08/07/2010 03:56 PM, [e-mail] wrote:
> > fedora 13
> >
> > A Linksys  wireless WUSB600 ver. 2
> >
> > Does anyone know about a Driver for this device , in all wireless sites
> > they say a ver.1 is supported but not ver. 2 ?
>
> The  Linksys WUSB600N  driver is available in the unsupported
> section of the vanilla kernel.
> The chipset in the WUSB600N is the RalinkTech 2860, so the driver
> is the rt2860.
>
> To try it (and I doubt very much it will work), you need to get the 
> source rpm
> of your kernel version, and configure it manually (make xconfig) and
> select the rt2860 from the "staging" drivers.

That isn't quite accurate....

One can install rt2860 and kmod-rt2860 packages from rpmfusion and cards
based on that chipset should work just fine.   My HP system has that and
I've had no problems with it.

Ed

[Fred Smith]

On Sun, Aug 08, 2010 at 08:58:19AM +0800, Ed Greshko wrote:
> On 08/08/2010 08:51 AM, JD wrote:
> > On 08/07/2010 03:56 PM, [e-mail] wrote:
> > > fedora 13
> > >
> > > A Linksys  wireless WUSB600 ver. 2
> > >
> > > Does anyone know about a Driver for this device , in all wireless sites
> > > they say a ver.1 is supported but not ver. 2 ?
> >
> > The  Linksys WUSB600N  driver is available in the unsupported
> > section of the vanilla kernel.
> > The chipset in the WUSB600N is the RalinkTech 2860, so the driver
> > is the rt2860.
> >
> > To try it (and I doubt very much it will work), you need to get the 
> > source rpm
> > of your kernel version, and configure it manually (make xconfig) and
> > select the rt2860 from the "staging" drivers.
>
> That isn't quite accurate....
>
> One can install rt2860 and kmod-rt2860 packages from rpmfusion and cards
> based on that chipset should work just fine.   My HP system has that and
> I've had no problems with it.

likewise with the rt2860sta in my eeepc 901. Definitely try the
kmod or akmod from rpmfusion!

[JD]

On 08/07/2010 05:58 PM, Ed Greshko wrote:
> On 08/08/2010 08:51 AM, JD wrote:
> > On 08/07/2010 03:56 PM, [e-mail] wrote:
> > > fedora 13
> > >
> > > A Linksys  wireless WUSB600 ver. 2
> > >
> > > Does anyone know about a Driver for this device , in all wireless sites
> > > they say a ver.1 is supported but not ver. 2 ?
> >
> > The  Linksys WUSB600N  driver is available in the unsupported
> > section of the vanilla kernel.
> > The chipset in the WUSB600N is the RalinkTech 2860, so the driver
> > is the rt2860.
> >
> > To try it (and I doubt very much it will work), you need to get the
> > source rpm
> > of your kernel version, and configure it manually (make xconfig) and
> > select the rt2860 from the "staging" drivers.
>
> That isn't quite accurate....
>
> One can install rt2860 and kmod-rt2860 packages from rpmfusion and cards
> based on that chipset should work just fine.   My HP system has that and
> I've had no problems with it.
>
> Ed

Hi Ed,
It's good to hear there is another person using the rt2860.
I just wonder when will the kernel dev team will finally fix
the rt2860 driver already in the staging drivers and make it
work.
What I have heard from some fedorans is that the current driver
source does not comply with the way linux wireless drivers are
designed to make use of the 802.11 stack. So, they have been
hacking at it for many months and still not working driver.

The driver which you are getting from RPMFUSION is not a "blessed"
linux driver - it is the same driver on the ralinktech.com web page.
All you have to do is getthe sources for the rpms you mention and
unpack them to see that the driver in the source package is
2010_01_29_RT2860_Linux_STA_v2.3.0.0.tar.bz2
which is from the ralinktech.com web site.

Cheers,

JD

[Ed Greshko]

On 08/08/2010 09:51 AM, JD wrote:
> It's good to hear there is another person using the rt2860.
> I just wonder when will the kernel dev team will finally fix
> the rt2860 driver already in the staging drivers and make it
> work.
> What I have heard from some fedorans is that the current driver
> source does not comply with the way linux wireless drivers are
> designed to make use of the 802.11 stack. So, they have been
> hacking at it for many months and still not working driver.
>
> The driver which you are getting from RPMFUSION is not a "blessed"
> linux driver - it is the same driver on the ralinktech.com web page.
> All you have to do is getthe sources for the rpms you mention and
> unpack them to see that the driver in the source package is
> 2010_01_29_RT2860_Linux_STA_v2.3.0.0.tar.bz2
> which is from the ralinktech.com web site.

I don't care if it is blessed or not.  I also don't care if it is the
same driver from the ralink site.  As much as possible, I like to take
the path of least resistance.  So, I use the stuff from rpmfusion.  And,
if someone asks me what they should do to get their rt2860 card working
I'd point them there first since the current track record is good.  That
may change, of course, but for now that would be my advice.  I don't
like to point folks to trying to get stuff from "staging" working since
there is generally a good reason why they are in "staging" and past
experience has proven frustrating and unrewarding for me.  YMMV.

[Mickey]

On 08/07/2010 10:27 PM, Ed Greshko wrote:
> On 08/08/2010 09:51 AM, JD wrote:
> > It's good to hear there is another person using the rt2860.
> > I just wonder when will the kernel dev team will finally fix
> > the rt2860 driver already in the staging drivers and make it
> > work.
> > What I have heard from some fedorans is that the current driver
> > source does not comply with the way linux wireless drivers are
> > designed to make use of the 802.11 stack. So, they have been
> > hacking at it for many months and still not working driver.
> >
> > The driver which you are getting from RPMFUSION is not a "blessed"
> > linux driver - it is the same driver on the ralinktech.com web page.
> > All you have to do is getthe sources for the rpms you mention and
> > unpack them to see that the driver in the source package is
> > 2010_01_29_RT2860_Linux_STA_v2.3.0.0.tar.bz2
> > which is from the ralinktech.com web site.
>
> I don't care if it is blessed or not.  I also don't care if it is the
> same driver from the ralink site.  As much as possible, I like to take
> the path of least resistance.  So, I use the stuff from rpmfusion.  And,
> if someone asks me what they should do to get their rt2860 card working
> I'd point them there first since the current track record is good.  That
> may change, of course, but for now that would be my advice.  I don't
> like to point folks to trying to get stuff from "staging" working since
> there is generally a good reason why they are in "staging" and past
> experience has proven frustrating and unrewarding for me.  YMMV.

I hope you guys are aware that the drivers for WUSB600N ver. 1  is 
different than WUSB600n ver. 2 .

I have the ver. 2

[Mickey]

On 08/07/2010 10:27 PM, Ed Greshko wrote:
> On 08/08/2010 09:51 AM, JD wrote:
> > It's good to hear there is another person using the rt2860.
> > I just wonder when will the kernel dev team will finally fix
> > the rt2860 driver already in the staging drivers and make it
> > work.
> > What I have heard from some fedorans is that the current driver
> > source does not comply with the way linux wireless drivers are
> > designed to make use of the 802.11 stack. So, they have been
> > hacking at it for many months and still not working driver.
> >
> > The driver which you are getting from RPMFUSION is not a "blessed"
> > linux driver - it is the same driver on the ralinktech.com web page.
> > All you have to do is getthe sources for the rpms you mention and
> > unpack them to see that the driver in the source package is
> > 2010_01_29_RT2860_Linux_STA_v2.3.0.0.tar.bz2
> > which is from the ralinktech.com web site.
>
> I don't care if it is blessed or not.  I also don't care if it is the
> same driver from the ralink site.  As much as possible, I like to take
> the path of least resistance.  So, I use the stuff from rpmfusion.  And,
> if someone asks me what they should do to get their rt2860 card working
> I'd point them there first since the current track record is good.  That
> may change, of course, but for now that would be my advice.  I don't
> like to point folks to trying to get stuff from "staging" working since
> there is generally a good reason why they are in "staging" and past
> experience has proven frustrating and unrewarding for me.  YMMV.

Well one thing for sure, The RT2860 does NOT WORK with the Ver. 2 of the 
WUSB600N.

That means it has a different chipset than Ver. 1 .

[Ed Greshko]

On 08/08/2010 11:08 PM, [e-mail] wrote:
> Well one thing for sure, The RT2860 does NOT WORK with the Ver. 2 of the 
> WUSB600N.
>
> That means it has a different chipset than Ver. 1 .

FWIW, I don't have a WUSB600N.  I also don't know, and didn't make the
claim that the WUSB600N has a rt2860 chipset.

My responses were solely directed towards indicating that if one did
have a RaLink RT2860 I felt it better to use the rpmfusion packages as
opposed to trying to compile the staging stuff.

If you can believe what you read on the net, :-), the v1 is rt2860 based
while the v2 is rt3572 based.

http://homecommunity.cisco.com/t5/Wireless-Adapters/Is-the-chipset-of-WUSB60...

is one source.

[Mickey]

On 08/08/2010 11:29 AM, Ed Greshko wrote:
> On 08/08/2010 11:08 PM, [e-mail] wrote:
> > Well one thing for sure, The RT2860 does NOT WORK with the Ver. 2 of the
> > WUSB600N.
> >
> > That means it has a different chipset than Ver. 1 .
>
> FWIW, I don't have a WUSB600N.  I also don't know, and didn't make the
> claim that the WUSB600N has a rt2860 chipset.
>
> My responses were solely directed towards indicating that if one did
> have a RaLink RT2860 I felt it better to use the rpmfusion packages as
> opposed to trying to compile the staging stuff.
>
> If you can believe what you read on the net, :-), the v1 is rt2860 based
> while the v2 is rt3572 based.
>
> http://homecommunity.cisco.com/t5/Wireless-Adapters/Is-the-chipset-of-WUSB60...
>
> is one source.

I downloaded the RT3572.tar.gz from Ralink and made the changes 
required, but it won't compile with "make"
I have kernel-headers and kernel-devel installed.

This is the last few lines of the compile, It is to large to show all of 
output.

In file included from 
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/rtmp_os.h:42,
                  from 
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/rt_config.h:72,
                  from 
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/common/crypt_md5.c:28:
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/os/rt_linux.h:166: 
error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before 
‘NDIS_PHYSICAL_ADDRESS’
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/os/rt_linux.h:167: 
error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/os/rt_linux.h:277: 
error: expected specifier-qualifier-list before ‘mm_segment_t’
In file included from 
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/chip/rt2870.h:41,
                  from 
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/rtmp_chip.h:47,
                  from 
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/rt_config.h:75,
                  from 
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/common/crypt_md5.c:28:
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/chip/mac_usb.h:201: 
error: expected specifier-qualifier-list before ‘dma_addr_t’
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/chip/mac_usb.h:228: 
error: expected specifier-qualifier-list before ‘dma_addr_t’
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/chip/mac_usb.h:251: 
error: expected specifier-qualifier-list before ‘dma_addr_t’
In file included from 
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/rtmp.h:49,
                  from 
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/rt_config.h:99,
                  from 
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/common/crypt_md5.c:28:
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/wsc.h: 
In function ‘WscCheckWSCHeader’:
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/wsc.h:106: 
warning: implicit declaration of function ‘get_unaligned’
In file included from 
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/rt_config.h:99,
                  from 
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/common/crypt_md5.c:28:
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/rtmp.h: 
At top level:
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/rtmp.h:626: 
error: expected specifier-qualifier-list before ‘NDIS_PHYSICAL_ADDRESS’
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/rtmp.h:642: 
error: expected specifier-qualifier-list before ‘NDIS_PHYSICAL_ADDRESS’
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/rtmp.h:6175: 
error: expected declaration specifiers or ‘...’ before 
‘PNDIS_PHYSICAL_ADDRESS’
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/rtmp.h:6183: 
error: expected declaration specifiers or ‘...’ before 
‘PNDIS_PHYSICAL_ADDRESS’
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/rtmp.h:6190: 
error: expected declaration specifiers or ‘...’ before 
‘NDIS_PHYSICAL_ADDRESS’
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/rtmp.h:6197: 
error: expected declaration specifiers or ‘...’ before 
‘PNDIS_PHYSICAL_ADDRESS’
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/rtmp.h:6204: 
error: expected declaration specifiers or ‘...’ before 
‘PNDIS_PHYSICAL_ADDRESS’
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/rtmp.h:6210: 
error: expected declaration specifiers or ‘...’ before 
‘NDIS_PHYSICAL_ADDRESS’
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/include/rtmp.h:6221: 
error: expected declaration specifiers or ‘...’ before 
‘PNDIS_PHYSICAL_ADDRESS’
make[1]: *** 
[/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/common/crypt_md5.o] 
Error 1
make[1]: Leaving directory 
`/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/os/linux'
make: *** [LINUX] Error 2

[JD]

On 08/08/2010 09:18 AM, [e-mail] wrote:
> On 08/08/2010 11:29 AM, Ed Greshko wrote:
> > On 08/08/2010 11:08 PM, [e-mail] wrote:
> > > Well one thing for sure, The RT2860 does NOT WORK with the Ver. 2 of the
> > > WUSB600N.
> > >
> > > That means it has a different chipset than Ver. 1 .
> >
> > FWIW, I don't have a WUSB600N.  I also don't know, and didn't make the
> > claim that the WUSB600N has a rt2860 chipset.
> >
> > My responses were solely directed towards indicating that if one did
> > have a RaLink RT2860 I felt it better to use the rpmfusion packages as
> > opposed to trying to compile the staging stuff.
> >
> > If you can believe what you read on the net, :-), the v1 is rt2860 based
> > while the v2 is rt3572 based.
> >
> > http://homecommunity.cisco.com/t5/Wireless-Adapters/Is-the-chipset-of-WUSB60...
> >
> > is one source.
>
> I downloaded the RT3572.tar.gz from Ralink and made the changes
> required, but it won't compile with "make"
> I have kernel-headers and kernel-devel installed.

Download the driver from here (very long url).
It will ask you to fill out name and email address ... blah...blah...

http://www.ralinktech.com/license_us.php?n=2&p=0&t=U0wyRnpjMlYwY3k4e...

[Mickey]

On 08/08/2010 01:24 PM, JD wrote:
> On 08/08/2010 09:18 AM, [e-mail] wrote:
> > On 08/08/2010 11:29 AM, Ed Greshko wrote:
> > > On 08/08/2010 11:08 PM, [e-mail] wrote:
> > > > Well one thing for sure, The RT2860 does NOT WORK with the Ver. 2 of the
> > > > WUSB600N.
> > > >
> > > > That means it has a different chipset than Ver. 1 .
> > >
> > > FWIW, I don't have a WUSB600N.  I also don't know, and didn't make the
> > > claim that the WUSB600N has a rt2860 chipset.
> > >
> > > My responses were solely directed towards indicating that if one did
> > > have a RaLink RT2860 I felt it better to use the rpmfusion packages as
> > > opposed to trying to compile the staging stuff.
> > >
> > > If you can believe what you read on the net, :-), the v1 is rt2860 based
> > > while the v2 is rt3572 based.
> > >
> > > http://homecommunity.cisco.com/t5/Wireless-Adapters/Is-the-chipset-of-WUSB60...
> > >
> > > is one source.
> >
> > I downloaded the RT3572.tar.gz from Ralink and made the changes
> > required, but it won't compile with "make"
> > I have kernel-headers and kernel-devel installed.
>
> Download the driver from here (very long url).
> It will ask you to fill out name and email address ... blah...blah...
>
> http://www.ralinktech.com/license_us.php?n=2&p=0&t=U0wyRnpjMlYwY3k4e...

That is the driver I downloaded.

[Ed Greshko]

On 08/09/2010 12:18 AM, [e-mail] wrote:
> I downloaded the RT3572.tar.gz from Ralink and made the changes 
> required, but it won't compile with "make"
> I have kernel-headers and kernel-devel installed.

Did you first try without making changes?

What changes did you make?

[Mickey]

On 08/08/2010 07:04 PM, Ed Greshko wrote:
> On 08/09/2010 12:18 AM, [e-mail] wrote:
> > I downloaded the RT3572.tar.gz from Ralink and made the changes
> > required, but it won't compile with "make"
> > I have kernel-headers and kernel-devel installed.
>
> Did you first try without making changes?
>
> What changes did you make?

The compile didn't even get this far before changes were made below.

Added {USB_DEVICE(0×1737,0×0079)}, /* Linksys WUSB600N v2 */        to   
/common/rtusb_dev_id.c     file

And modify     /os/linux/config.mk     file

# Support Wpa_Supplicant
HAS_WPA_SUPPLICANT=y

# Support Native WpaSupplicant for Network Maganger
HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y

the modification were like the website shows;

http://chron1x.wordpress.com/2010/03/16/how-to-get-linksys-wusb600n-v2-runni...

[Ed Greshko]

On 08/09/2010 07:23 AM, [e-mail] wrote:
> The compile didn't even get this far before changes were made below.
>
> Added {USB_DEVICE(0×1737,0×0079)}, /* Linksys WUSB600N v2 */        to   
> /common/rtusb_dev_id.c     file
>
> And modify     /os/linux/config.mk     file
>
> # Support Wpa_Supplicant
> HAS_WPA_SUPPLICANT=y
>
> # Support Native WpaSupplicant for Network Maganger
> HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y

Compiles just fine here before and after the changes...

F13, 2.6.33.6-147.fc13.i686.PAE

Are you 32 or 64 bit?

[JD]

On 08/08/2010 04:36 PM, Ed Greshko wrote:
> On 08/09/2010 07:23 AM, [e-mail] wrote:
> > The compile didn't even get this far before changes were made below.
> >
> > Added {USB_DEVICE(0×1737,0×0079)}, /* Linksys WUSB600N v2 */        to
> > /common/rtusb_dev_id.c     file
> >
> > And modify     /os/linux/config.mk     file
> >
> > # Support Wpa_Supplicant
> > HAS_WPA_SUPPLICANT=y
> >
> > # Support Native WpaSupplicant for Network Maganger
> > HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y
>
> Compiles just fine here before and after the changes...
>
> F13, 2.6.33.6-147.fc13.i686.PAE
>
> Are you 32 or 64 bit?

Also, be sure that /lib/modules/`uname -r`/build
symlink points to the directory /usr/src/kernels/`uname -r`
Of course, assuming that you have installed kernel-devel-`uname-r`  rpm.

[Mickey]

On 08/08/2010 07:46 PM, JD wrote:
> On 08/08/2010 04:36 PM, Ed Greshko wrote:
> > On 08/09/2010 07:23 AM, [e-mail] wrote:
> > > The compile didn't even get this far before changes were made below.
> > >
> > > Added {USB_DEVICE(0×1737,0×0079)}, /* Linksys WUSB600N v2 */        to
> > > /common/rtusb_dev_id.c     file
> > >
> > > And modify     /os/linux/config.mk     file
> > > # Support Wpa_Supplicant
> > >
> > > HAS_WPA_SUPPLICANT=y
> > >
> > > # Support Native WpaSupplicant for Network Maganger
> > > HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y
> >
> > Compiles just fine here before and after the changes...
> >
> > F13, 2.6.33.6-147.fc13.i686.PAE
> >
> > Are you 32 or 64 bit?
>
> Also, be sure that /lib/modules/`uname -r`/build
> symlink points to the directory /usr/src/kernels/`uname -r`
> Of course, assuming that you have installed kernel-devel-`uname-r`  rpm.

The kernel-devel kernel-headers are installed.

And /build does point to /usr/src/kernel

[Ed Greshko]

On 08/09/2010 08:06 PM, [e-mail] wrote:
> On 08/08/2010 07:46 PM, JD wrote:
> > On 08/08/2010 04:36 PM, Ed Greshko wrote:
> > > On 08/09/2010 07:23 AM, [e-mail] wrote:
> > > > The compile didn't even get this far before changes were made below.
> > > >
> > > > Added {USB_DEVICE(0×1737,0×0079)}, /* Linksys WUSB600N v2 */        to
> > > > /common/rtusb_dev_id.c     file
> > > >
> > > > And modify     /os/linux/config.mk     file
> > > > # Support Wpa_Supplicant
> > > >
> > > > HAS_WPA_SUPPLICANT=y
> > > >
> > > > # Support Native WpaSupplicant for Network Maganger
> > > > HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y
> > >
> > > Compiles just fine here before and after the changes...
> > >
> > > F13, 2.6.33.6-147.fc13.i686.PAE
> > >
> > > Are you 32 or 64 bit?
> >
> > Also, be sure that /lib/modules/`uname -r`/build
> > symlink points to the directory /usr/src/kernels/`uname -r`
> > Of course, assuming that you have installed kernel-devel-`uname-r`  rpm.
>
> The kernel-devel kernel-headers are installed.
>
> And /build does point to /usr/src/kernel

Well....  If all of that is OK and since you are on 32 bit it should be
similar to what I have.  I forgot if you mentioned what level of fedora
you're running....

The only thing I could think of is that you are missing a devel package
that is needed.

I know you pasted a few lines from the end of the compile....but the
question is are those the "first" errors encountered?  Maybe it would be
a good idea to put the entire compile output on fpaste.org.

[Mickey]

On 08/09/2010 08:16 AM, Ed Greshko wrote:
> On 08/09/2010 08:06 PM, [e-mail] wrote:
> > On 08/08/2010 07:46 PM, JD wrote:
> > > On 08/08/2010 04:36 PM, Ed Greshko wrote:
> > > > On 08/09/2010 07:23 AM, [e-mail] wrote:
> > > > > The compile didn't even get this far before changes were made below.
> > > > >
> > > > > Added {USB_DEVICE(0×1737,0×0079)}, /* Linksys WUSB600N v2 */        to
> > > > > /common/rtusb_dev_id.c     file
> > > > >
> > > > > And modify     /os/linux/config.mk     file
> > > > >  # Support Wpa_Supplicant
> > > > >
> > > > > HAS_WPA_SUPPLICANT=y
> > > > >
> > > > > # Support Native WpaSupplicant for Network Maganger
> > > > > HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y
> > > >
> > > > Compiles just fine here before and after the changes...
> > > >
> > > > F13, 2.6.33.6-147.fc13.i686.PAE
> > > >
> > > > Are you 32 or 64 bit?
> > >
> > > Also, be sure that /lib/modules/`uname -r`/build
> > > symlink points to the directory /usr/src/kernels/`uname -r`
> > > Of course, assuming that you have installed kernel-devel-`uname-r`  rpm.
> >
> > The kernel-devel kernel-headers are installed.
> >
> > And /build does point to /usr/src/kernel
>
> Well....  If all of that is OK and since you are on 32 bit it should be
> similar to what I have.  I forgot if you mentioned what level of fedora
> you're running....
>
> The only thing I could think of is that you are missing a devel package
> that is needed.
>
> I know you pasted a few lines from the end of the compile....but the
> question is are those the "first" errors encountered?  Maybe it would be
> a good idea to put the entire compile output on fpaste.org.

Ed I can't get the complete output showing of 'make' to show in console, 
what command can I use to send it a /home/jim/rt.txt

I have tried ;

make > /home/jim/rt.txt

But all I get is 4 lines of output

[Ed Greshko]

On 08/09/2010 08:48 PM, [e-mail] wrote:
> Ed I can't get the complete output showing of 'make' to show in console, 
> what command can I use to send it a /home/jim/rt.txt
>
> I have tried ;
>
> make > /home/jim/rt.txt
>
> But all I get is 4 lines of output

make &>/home/jim/rt.txt

[Mickey]

On 08/09/2010 08:57 AM, Ed Greshko wrote:
> On 08/09/2010 08:48 PM, [e-mail] wrote:
> > Ed I can't get the complete output showing of 'make' to show in console,
> > what command can I use to send it a /home/jim/rt.txt
> >
> > I have tried ;
> >
> > make>  /home/jim/rt.txt
> >
> > But all I get is 4 lines of output
>
> make&>/home/jim/rt.txt

Ed I pasted the complete 'make' out to fpaste.org, who reads it there ?

Filename is "RT3572 by Jim Tate"

[Mickey]

On 08/09/2010 09:19 AM, [e-mail] wrote:
> On 08/09/2010 08:57 AM, Ed Greshko wrote:
> > On 08/09/2010 08:48 PM, [e-mail] wrote:
> > > Ed I can't get the complete output showing of 'make' to show in 
> > > console,
> > > what command can I use to send it a /home/jim/rt.txt
> > >
> > > I have tried ;
> > >
> > > make>  /home/jim/rt.txt
> > >
> > > But all I get is 4 lines of output
> >
> > make&>/home/jim/rt.txt
>
> Ed I pasted the complete 'make' out to fpaste.org, who reads it there ?
>
> Filename is "RT3572 by Jim Tate"

The website is http://fpaste.org/Yvb0/

[Mickey]

On 08/09/2010 08:06 AM, [e-mail] wrote:
> On 08/08/2010 07:46 PM, JD wrote:
> > On 08/08/2010 04:36 PM, Ed Greshko wrote:
> > > On 08/09/2010 07:23 AM, [e-mail] wrote:
> > > > The compile didn't even get this far before changes were made below.
> > > >
> > > > Added {USB_DEVICE(0×1737,0×0079)}, /* Linksys WUSB600N v2 */        to
> > > > /common/rtusb_dev_id.c     file
> > > >
> > > > And modify     /os/linux/config.mk     file
> > > >  # Support Wpa_Supplicant
> > > >
> > > > HAS_WPA_SUPPLICANT=y
> > > >
> > > > # Support Native WpaSupplicant for Network Maganger
> > > > HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y
> > >
> > > Compiles just fine here before and after the changes...
> > >
> > > F13, 2.6.33.6-147.fc13.i686.PAE
> > >
> > > Are you 32 or 64 bit?
> >
> > Also, be sure that /lib/modules/`uname -r`/build
> > symlink points to the directory /usr/src/kernels/`uname -r`
> > Of course, assuming that you have installed kernel-devel-`uname-r`  rpm.
>
> The kernel-devel kernel-headers are installed.
>
> And /build does point to /usr/src/kernel

Here is a copy of the Make file,
Is there a possibility that the kernel2.6.33.6-147.2.4.fc13.i686 is the 
wrong kernel to compile this Make file with.

RT28xx_MODE = STA
TARGET = LINUX
CHIPSET = 3572
OSABL = NO

#RT28xx_DIR = home directory of RT28xx source code
RT28xx_DIR = $(shell pwd)
RTMP_SRC_DIR = $(RT28xx_DIR)/RT$(CHIPSET)

#PLATFORM: Target platform
PLATFORM = PC
#PLATFORM = 5VT
#PLATFORM = IKANOS_V160
#PLATFORM = IKANOS_V180
#PLATFORM = SIGMA
#PLATFORM = SIGMA_8622
#PLATFORM = STAR
#PLATFORM = IXP
#PLATFORM = INF_TWINPASS
#PLATFORM = INF_DANUBE
#PLATFORM = INF_AR9
#PLATFORM = INF_VR9
#PLATFORM = BRCM_6358
#PLATFORM = INF_AMAZON_SE
#PLATFORM = CAVM_OCTEON
#PLATFORM = CMPC
#PLATFORM = RALINK_2880
#PLATFORM = RALINK_3052
#PLATFORM = SMDK
#PLATFORM = RMI
#PLATFORM = RMI_64
#PLATFORM = KODAK_DC
#PLATFORM = DM6446
#PLATFORM = FREESCALE8377
#PLATFORM = BL2348
#PLATFORM = BLUBB
#PLATFORM = BLPMP
#PLATFORM = MT85XX
#PLATFORM = NXP_TV550
#PLATFORM = MVL5

ifeq ($(TARGET),LINUX)
MAKE = make
endif

ifeq ($(PLATFORM),5VT)
LINUX_SRC = /project/stable/5vt/ralink-2860-sdk/linux-2.6.17
CROSS_COMPILE = /opt/crosstool/uClibc_v5te_le_gcc_4_1_1/bin/arm-linux-
endif

ifeq ($(PLATFORM),IKANOS_V160)
LINUX_SRC = /home/sample/projects/LX_2618_RG_5_3_00r4_SRC/linux-2.6.18
CROSS_COMPILE = mips-linux-
endif

ifeq ($(PLATFORM),IKANOS_V180)
LINUX_SRC = 
/home/sample/projects/LX_BSP_VX180_5_4_0r1_ALPHA_26DEC07/linux-2.6.18
CROSS_COMPILE = mips-linux-
endif

ifeq ($(PLATFORM),SIGMA)
LINUX_SRC = /root/sigma/smp86xx_kernel_source_2.7.172.0/linux-2.6.15
CROSS_COMPILE = 
/root/sigma/smp86xx_toolchain_2.7.172.0/build_mipsel_nofpu/staging_dir/bin/mipsel-linux-
endif

ifeq ($(PLATFORM),SIGMA_8622)
LINUX_SRC = /home/snowpin/armutils_2.5.120.1/build_arm/linux-2.4.22-em86xx
CROSS_COMPILE = /home/snowpin/armutils_2.5.120.1/toolchain/bin/arm-elf-
CROSS_COMPILE_INCLUDE = 
/home/snowpin/armutils_2.5.120.1/toolchain/lib/gcc-lib/arm-elf/2.95.3
endif

ifeq ($(PLATFORM),STAR)
LINUX_SRC = /opt/star/kernel/linux-2.4.27-star
CROSS_COMPILE = /opt/star/tools/arm-linux/bin/arm-linux-
endif

ifeq ($(PLATFORM),RMI)
LINUX_SRC = /opt/rmi/1.7.0/linux/src/
CROSS_COMPILE = /opt/rmi/1.7.0/mipscross/nptl/bin/mips64-unknown-linux-gnu-
endif

ifeq ($(PLATFORM),RMI_64)
LINUX_SRC = /opt/rmi/1.7.0/linux_64/src/
CROSS_COMPILE = /opt/rmi/1.7.0/mipscross/nptl/bin/mips64-unknown-linux-gnu-
endif

ifeq ($(PLATFORM), RALINK_2880)
LINUX_SRC = /project/stable/RT288x/RT288x_SDK/source/linux-2.4.x
CROSS_COMPILE = /opt/buildroot-gdb/bin/mipsel-linux-
endif

ifeq ($(PLATFORM),RALINK_3052)
LINUX_SRC = /home/peter/ap_soc/SDK_3_3_0_0/RT288x_SDK/source/linux-2.6.21.x
CROSS_COMPILE = /opt/buildroot-gcc342/bin/mipsel-linux-uclibc-
endif

ifeq ($(PLATFORM),FREESCALE8377)
LINUX_SRC = /opt/ltib-mpc8377_rds-20090309/rpm/BUILD/linux-2.6.25
CROSS_COMPILE = 
/opt/freescale/usr/local/gcc-4.2.187-eglibc-2.5.187/powerpc-linux-gnu/bin/powerpc-linux-gnu-
endif

ifeq ($(PLATFORM),BL2348)
LINUX_SRC = /home/sample/Customers/BroadLight/bl234x-linux-2.6.21-small-v29
CROSS_COMPILE = mips-wrs-linux-gnu-
endif

ifeq ($(PLATFORM),BLUBB)
LINUX_SRC = /home/sample/Customers/BroadLight/UBB/gmp20/linux-2.6.21-small
CROSS_COMPILE = mips-wrs-linux-gnu-
endif

ifeq ($(PLATFORM),BLPMP)
LINUX_SRC = 
/home/sample/Customers/BroadLight/UBB/pmp16/bl234x-linux-2.6.21-small-v30.2
CROSS_COMPILE = mips-wrs-linux-gnu-
endif

ifeq ($(PLATFORM),PC)
# Linux 2.6
LINUX_SRC = /lib/modules/$(shell uname -r)/build
# Linux 2.4 Change to your local setting
#LINUX_SRC = /usr/src/linux-2.4
LINUX_SRC_MODULE = /lib/modules/$(shell uname 
-r)/kernel/drivers/net/wireless/
CROSS_COMPILE =
endif

ifeq ($(PLATFORM),IXP)
LINUX_SRC = /project/stable/Gmtek/snapgear-uclibc/linux-2.6.x
CROSS_COMPILE = arm-linux-
endif

ifeq ($(PLATFORM),INF_TWINPASS)
# Linux 2.6
#LINUX_SRC = /lib/modules/$(shell uname -r)/build
# Linux 2.4 Change to your local setting
LINUX_SRC = 
/project/stable/twinpass/release/2.0.1/source/kernel/opensource/linux-2.4.31/
CROSS_COMPILE = mips-linux-
endif

ifeq ($(PLATFORM),INF_DANUBE)
LINUX_SRC = /opt/danube/sdk/linux-2.6.16.x
CROSS_COMPILE = mips-linux-
ROOTDIR = /opt/danube/sdk
export ROOTDIR
endif

ifeq ($(PLATFORM),INF_AR9)
LINUX_SRC = /root/ar9/xR9_BSP1.2.2.0/source/kernel/opensource/linux-2.6.20/
CROSS_COMPILE = /root/ar9/ifx-lxdb26-1.0.2/gcc-3.4.4/toolchain-mips/bin/
endif

ifeq ($(PLATFORM),INF_VR9)
LINUX_SRC = 
/home/public/lantiq/VR9/UGW-4.2/build_dir/linux-ifxcpe_platform_vr9/linux-2.6.20.19
CROSS_COMPILE = 
/home/public/lantiq/VR9/UGW-4.2/staging_dir/toolchain-mips_gcc-3.4.6_uClibc-0.9.29/bin/mips-linux-
endif

ifeq ($(PLATFORM),BRCM_6358)
LINUX_SRC =
CROSS_COMPILE =
endif

ifeq ($(PLATFORM),INF_AMAZON_SE)
# Linux 2.6
#LINUX_SRC = /lib/modules/$(shell uname -r)/build
# Linux 2.4 Change to your local setting
LINUX_SRC = /backup/ifx/3.6.2.2/source/kernel/opensource/linux-2.4.31
#CROSS_COMPILE = mips-linux-
#LINUX_SRC = /project/Infineon/3.6.2.2/source/kernel/opensource/linux-2.4.31
CROSS_COMPILE = 
/opt/uclibc-toolchain/ifx-lxdb-1-2-3-external/gcc-3.3.6/toolchain-mips/R0208V35/mips-linux-uclibc/bin/
endif

ifeq ($(PLATFORM),ST)
LINUX_SRC = /opt/STM/STLinux-2.2/devkit/sources/kernel/linux0039
CROSS_COMPILE = /opt/STM/STLinux-2.2/devkit/sh4/bin/sh4-linux-
ARCH := sh
export ARCH
endif

ifeq ($(PLATFORM),CAVM_OCTEON)
OCTEON_ROOT = /usr/local/Cavium_Networks/OCTEON-SDK
LINUX_SRC = $(OCTEON_ROOT)/linux/kernel_2.6/linux
CROSS_COMPILE = mips64-octeon-linux-gnu-
endif

ifeq ($(PLATFORM),CMPC)
LINUX_SRC = /opt/fvt_11N_SDK_0807/fvt131x_SDK_11n/linux-2.6.17
CROSS_COMPILE =
endif

ifeq ($(PLATFORM),SMDK)
LINUX_SRC = /home/bhushan/itcenter/may28/linux-2.6-samsung
CROSS_COMPILE = /usr/local/arm/4.2.2-eabi/usr/bin/arm-linux-
endif

ifeq ($(PLATFORM),KODAK_DC)
SKD_SRC = C:/SigmaTel/DC1250_SDK_v1-9/sdk
CROSS_COMPILE = $(cc)
endif

ifeq ($(PLATFORM),DM6446)
LINUX_SRC = /home/fonchi/work/soc/ti-davinci
endif

ifeq ($(PLATFORM),MT85XX)
LINUX_SRC = /home/john/MTK/BDP_Linux/linux-2.6.27
CROSS_COMPILE = armv6z-mediatek-linux-gnueabi-
endif

ifeq ($(PLATFORM),NXP_TV550)
LINUX_SRC = /data/tv550/kernel/linux-2.6.28.9
LINUX_SRC_MODULE = /data/tv550/kernel/linux-2.6.28.9/drivers/net/wireless
CROSS_COMPILE = /opt/embeddedalley/nxp_tv550/bin/mipsel-linux-
endif

ifeq ($(PLATFORM),MVL5)
LINUX_SRC = /home2/charlestu/AP-VT3426/linux-2.6.18
CROSS_COMPILE = /opt/montavista/pro/devkit/arm/v5t_le_mvl5/bin/arm_v5t_le-
endif

export OSABL RT28xx_DIR RT28xx_MODE LINUX_SRC CROSS_COMPILE 
CROSS_COMPILE_INCLUDE PLATFORM RELEASE CHIPSET RTMP_SRC_DIR 
LINUX_SRC_MODULE TARGET

# The targets that may be used.
PHONY += all build_tools test UCOS THREADX LINUX release prerelease 
clean uninstall install libwapi osabl

all: build_tools $(TARGET)

build_tools:
     $(MAKE) -C tools
     $(RT28xx_DIR)/tools/bin2h

test:
     $(MAKE) -C tools test

LINUX:
ifneq (,$(findstring 2.4,$(LINUX_SRC)))

cp -f os/linux/Makefile.4 $(RT28xx_DIR)/os/linux/Makefile
     $(MAKE) -C $(RT28xx_DIR)/os/linux/

cp -f $(RT28xx_DIR)/os/linux/rt$(CHIPSET)sta.o /tftpboot
else
     cp -f os/linux/Makefile.6 $(RT28xx_DIR)/os/linux/Makefile
ifeq ($(PLATFORM),DM6446)
     $(MAKE)  ARCH=arm CROSS_COMPILE=arm_v5t_le- -C  $(LINUX_SRC) 
SUBDIRS=$(RT28xx_DIR)/os/linux modules
else
ifeq ($(PLATFORM),FREESCALE8377)
     $(MAKE) ARCH=powerpc CROSS_COMPILE=$(CROSS_COMPILE) -C  
$(LINUX_SRC) SUBDIRS=$(RT28xx_DIR)/os/linux modules
else
     $(MAKE) -C $(LINUX_SRC) SUBDIRS=$(RT28xx_DIR)/os/linux modules
endif
endif

endif

clean:
ifeq ($(TARGET), LINUX)
ifneq (,$(findstring 2.4,$(LINUX_SRC)))
     cp -f os/linux/Makefile.4 os/linux/Makefile
else
     cp -f os/linux/Makefile.6 os/linux/Makefile
endif
     $(MAKE) -C os/linux clean
     rm -rf os/linux/Makefile
endif

uninstall:
ifeq ($(TARGET), LINUX)
ifneq (,$(findstring 2.4,$(LINUX_SRC)))
     $(MAKE) -C $(RT28xx_DIR)/os/linux -f Makefile.4 uninstall
else
     $(MAKE) -C $(RT28xx_DIR)/os/linux -f Makefile.6 uninstall
endif
endif

install:
ifeq ($(TARGET), LINUX)
ifneq (,$(findstring 2.4,$(LINUX_SRC)))
     $(MAKE) -C $(RT28xx_DIR)/os/linux -f Makefile.4 install
else
     $(MAKE) -C $(RT28xx_DIR)/os/linux -f Makefile.6 install
endif
endif

[Ed Greshko]

On 08/09/2010 08:21 PM, [e-mail] wrote:
> Here is a copy of the Make file,
> Is there a possibility that the kernel2.6.33.6-147.2.4.fc13.i686 is the 
> wrong kernel to compile this Make file with.

Yes....

I just updated my system and now believe I have the same error you do. 
The first indication is...

cc1: error:
/lib/modules/2.6.33.6-147.2.4.fc13.i686.PAE/build/include/linux/modversions.h:
No such file or directory

But the differences start a bit earlier.....

The make on the earlier kernel has this....

make -C tools
make[1]: Entering directory
`/home/egreshko/src/2010_0709_RT3572_Linux_STA_v2.4.
0.1/tools'
gcc -g bin2h.c -o bin2h
make[1]: Leaving directory
`/home/egreshko/src/2010_0709_RT3572_Linux_STA_v2.4.0
.1/tools'
/home/egreshko/src/2010_0709_RT3572_Linux_STA_v2.4.0.1/tools/bin2h
cp -f os/linux/Makefile.6
/home/egreshko/src/2010_0709_RT3572_Linux_STA_v2.4.0.1
/os/linux/Makefile
make -C /lib/modules/2.6.33.6-147.fc13.i686.PAE/build
SUBDIRS=/home/egreshko/src
/2010_0709_RT3572_Linux_STA_v2.4.0.1/os/linux modules

While the failing kernel build has this....

make[1]: Entering directory
`/home/egreshko/src/2010_0709_RT3572_Linux_STA_v2.4.
0.1/tools'
gcc -g bin2h.c -o bin2h
make[1]: Leaving directory
`/home/egreshko/src/2010_0709_RT3572_Linux_STA_v2.4.0
.1/tools'
/home/egreshko/src/2010_0709_RT3572_Linux_STA_v2.4.0.1/tools/bin2h
cp -f os/linux/Makefile.4
/home/egreshko/src/2010_0709_RT3572_Linux_STA_v2.4.0.1
/os/linux/Makefile
make -C /home/egreshko/src/2010_0709_RT3572_Linux_STA_v2.4.0.1/os/linux/
make[1]: Entering directory
`/home/egreshko/src/2010_0709_RT3572_Linux_STA_v2.4.
0.1/os/linux'

Unfortunately it is late in the day and I don't have the time now to
figure out what is "broken".

[Ed Greshko]

On 08/09/2010 09:30 PM, Ed Greshko wrote:
> Unfortunately it is late in the day and I don't have the time now to
> figure out what is "broken".

Ah hah....

I see the problem....but not sure how to fix yet.....

In the Makefile you see..... at line 236

ifneq (,$(findstring 2.4,$(LINUX_SRC)))

Well....the current kernel is 2.6.33.6-147.2.4.fc13.i686.PAE which
contains the string 2.4 so the build thinks this is a 2.4 kernel build!

My wife and cats are yelling at me......

[Mickey]

On 08/09/2010 09:50 AM, Ed Greshko wrote:
> On 08/09/2010 09:30 PM, Ed Greshko wrote:
> > Unfortunately it is late in the day and I don't have the time now to
> > figure out what is "broken".
>
> Ah hah....
>
> I see the problem....but not sure how to fix yet.....
>
> In the Makefile you see..... at line 236
>
> ifneq (,$(findstring 2.4,$(LINUX_SRC)))
>
> Well....the current kernel is 2.6.33.6-147.2.4.fc13.i686.PAE which
> contains the string 2.4 so the build thinks this is a 2.4 kernel build!
>
> My wife and cats are yelling at me......

That is weird making a "Make" file for a 2.4 kernel in 2010 .

If I changed it line 236 to 2.6.33.6-147.2.4.fc13.i686 , Would that work ?

[Ed Greshko]

On 08/09/2010 09:50 PM, Ed Greshko wrote:
> My wife and cats are yelling at me......

Escaped for a few minutes.....

OK.....  To "fix" the build problem.....

In both 2010_0709_RT3572_Linux_STA_v2.4.0.1/Makefile and os/linux/config.mk

find the lines that have "findstring 2.4" and replace it with
"findstring 2.9"

Actually in config.mk you should probably only need to change it one
place....after the line

ifeq ($(PLATFORM),PC)

Ed

[Mickey]

On 08/09/2010 10:15 AM, Ed Greshko wrote:
> "findstring 2.9"

Ed the "findstring 2.9", shouldn't that be 2.6 ?

This error in /common/rtusb_dev_id.c       rtusb_dev_id.c:104:29: error: 
invalid digit "9" , does 104:29 mean line and character number ?

If so , line# 104 is,  {USB_DEVICE(0×1737,0×0079)}, /* Linksys WUSB600N 
v2*/    That is the line I pasted in , for the adapter.

/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/common/rtusb_dev_id.c:104:29: 
error: invalid digit "9" in octal constant
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/common/rtusb_dev_id.c:104: 
error: expected ‘)’ before numeric constant
make[1]: *** 
[/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/common/rtusb_dev_id.o] 
Error 1
make[1]: Leaving directory 
`/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/os/linux'
make: *** [LINUX] Error 2

[Ed Greshko]

On 08/10/2010 12:11 AM, [e-mail] wrote:
> On 08/09/2010 10:15 AM, Ed Greshko wrote:
> > "findstring 2.9"
>
> Ed the "findstring 2.9", shouldn't that be 2.6 ?

NO....NO....and HELL NO!!!!

If the match happens....it will do its 2.4 thing.  So, 2.6 and 2.4 will
match 2.6.33.6-147.2.4.fc13.i686
since  both 2.4 and 2.6 exist in that string!!!!!

Hell....make it 9999.99999!!!

The idea is to make in NOT MATCH....

As I just said....

1.  It compiled for me and not for you....because I was using
2.6.33.6-147.fc13.i686.PAE originally.  There is no 2.4 in there, right?

2.  I updated my system to the same kernel....as yours...and the compile
failed and I get the same error EXACTLY.

3.  I made the changes I've already told you....and it *complies just
fine here*.....

So, make my changes....or not.  Up to you....
> This error in /common/rtusb_dev_id.c       rtusb_dev_id.c:104:29: error: 
> invalid digit "9" , does 104:29 mean line and character number ?
>
> If so , line# 104 is,  {USB_DEVICE(0×1737,0×0079)}, /* Linksys WUSB600N 
> v2*/    That is the line I pasted in , for the adapter.
>
> /home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/common/rtusb_dev_id.c:104:29: 
> error: invalid digit "9" in octal constant
> /home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/common/rtusb_dev_id.c:104: 
> error: expected ‘)’ before numeric constant
> make[1]: *** 
> [/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/common/rtusb_dev_id.o] 
> Error 1
> make[1]: Leaving directory 
> `/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/os/linux'
> make: *** [LINUX] Error 2

[JD]

On 08/09/2010 06:50 AM, Ed Greshko wrote:
> On 08/09/2010 09:30 PM, Ed Greshko wrote:
> > Unfortunately it is late in the day and I don't have the time now to
> > figure out what is "broken".
>
> Ah hah....
>
> I see the problem....but not sure how to fix yet.....
>
> In the Makefile you see..... at line 236
>
> ifneq (,$(findstring 2.4,$(LINUX_SRC)))
>
> Well....the current kernel is 2.6.33.6-147.2.4.fc13.i686.PAE which
> contains the string 2.4 so the build thinks this is a 2.4 kernel build!
>
> My wife and cats are yelling at me......

Hi Ed, and Mr. binary :)

I did not keep the original build output from mr. binary ...

Did the compilation error message look like this:

...... 
/2010_0709_RT3572_Linux_STA_v2.4.0.1/os/linux/../../common/cmm_mac_usb.c:52: 
error: implicit declaration of function ‘usb_buffer_alloc’

If so, then it has nothing to do with
ifneq (,$(findstring 2.4,$(LINUX_SRC)))

at all.

It has to do with the fact that usb_buffer_alloc function is no longer 
present in the kernel sources of the linux version you are compiling for.
Nor is it present in my kernel source 2.6.35-git1

It was present in

kernel-2.6.32.16-150.fc12.src/linux-2.6.32/drivers/usb/core/usb.c

and exported via header file

kernel-2.6.32.16-150.fc12.src/linux-2.6.32/include/linux/usb.h

This function was taken out sometime kernel 2.6.32.16-150

This is the problem with ralinktech. They do not keep up with
linux kernel changes. They think one hat fits all is the way to go.
Unlike, for example, VirtualBox - which has a separate release for
several kernel revisions of Fedora.

[Mickey]

On 08/09/2010 11:59 AM, JD wrote:
> On 08/09/2010 06:50 AM, Ed Greshko wrote:
> > On 08/09/2010 09:30 PM, Ed Greshko wrote:
> > > Unfortunately it is late in the day and I don't have the time now to
> > > figure out what is "broken".
> >
> > Ah hah....
> >
> > I see the problem....but not sure how to fix yet.....
> >
> > In the Makefile you see..... at line 236
> >
> > ifneq (,$(findstring 2.4,$(LINUX_SRC)))
> >
> > Well....the current kernel is 2.6.33.6-147.2.4.fc13.i686.PAE which
> > contains the string 2.4 so the build thinks this is a 2.4 kernel build!
> >
> > My wife and cats are yelling at me......
>
> Hi Ed, and Mr. binary :)
>
> I did not keep the original build output from mr. binary ...
>
> Did the compilation error message look like this:
>
> ......
> /2010_0709_RT3572_Linux_STA_v2.4.0.1/os/linux/../../common/cmm_mac_usb.c:52:
> error: implicit declaration of function ‘usb_buffer_alloc’
>
> If so, then it has nothing to do with
> ifneq (,$(findstring 2.4,$(LINUX_SRC)))
>
> at all.
>
> It has to do with the fact that usb_buffer_alloc function is no longer
> present in the kernel sources of the linux version you are compiling for.
> Nor is it present in my kernel source 2.6.35-git1
>
> It was present in
>
> kernel-2.6.32.16-150.fc12.src/linux-2.6.32/drivers/usb/core/usb.c
>
> and exported via header file
>
> kernel-2.6.32.16-150.fc12.src/linux-2.6.32/include/linux/usb.h
>
> This function was taken out sometime kernel 2.6.32.16-150
>
> This is the problem with ralinktech. They do not keep up with
> linux kernel changes. They think one hat fits all is the way to go.
> Unlike, for example, VirtualBox - which has a separate release for
> several kernel revisions of Fedora.

Does that mean I have to scrap the compile ideal and wait for them to 
come out with a Linux  driver ?

[JD]

On 08/09/2010 09:14 AM, [e-mail] wrote:
> On 08/09/2010 11:59 AM, JD wrote:
> > On 08/09/2010 06:50 AM, Ed Greshko wrote:
> > > On 08/09/2010 09:30 PM, Ed Greshko wrote:
> > > > Unfortunately it is late in the day and I don't have the time now to
> > > > figure out what is "broken".
> > >
> > > Ah hah....
> > >
> > > I see the problem....but not sure how to fix yet.....
> > >
> > > In the Makefile you see..... at line 236
> > >
> > > ifneq (,$(findstring 2.4,$(LINUX_SRC)))
> > >
> > > Well....the current kernel is 2.6.33.6-147.2.4.fc13.i686.PAE which
> > > contains the string 2.4 so the build thinks this is a 2.4 kernel build!
> > >
> > > My wife and cats are yelling at me......
> >
> > Hi Ed, and Mr. binary :)
> >
> > I did not keep the original build output from mr. binary ...
> >
> > Did the compilation error message look like this:
> >
> > ......
> > /2010_0709_RT3572_Linux_STA_v2.4.0.1/os/linux/../../common/cmm_mac_usb.c:52:
> > error: implicit declaration of function ‘usb_buffer_alloc’
> >
> > If so, then it has nothing to do with
> > ifneq (,$(findstring 2.4,$(LINUX_SRC)))
> >
> > at all.
> >
> > It has to do with the fact that usb_buffer_alloc function is no longer
> > present in the kernel sources of the linux version you are compiling for.
> > Nor is it present in my kernel source 2.6.35-git1
> >
> > It was present in
> >
> > kernel-2.6.32.16-150.fc12.src/linux-2.6.32/drivers/usb/core/usb.c
> >
> > and exported via header file
> >
> > kernel-2.6.32.16-150.fc12.src/linux-2.6.32/include/linux/usb.h
> >
> > This function was taken out sometime kernel 2.6.32.16-150
> >
> > This is the problem with ralinktech. They do not keep up with
> > linux kernel changes. They think one hat fits all is the way to go.
> > Unlike, for example, VirtualBox - which has a separate release for
> > several kernel revisions of Fedora.
>
> Does that mean I have to scrap the compile ideal and wait for them to
> come out with a Linux  driver ?

Don't hold your breath.
What is your kernel version?

[Mickey]

On 08/09/2010 12:27 PM, JD wrote:
> On 08/09/2010 09:14 AM, [e-mail] wrote:
> > On 08/09/2010 11:59 AM, JD wrote:
> > >  On 08/09/2010 06:50 AM, Ed Greshko wrote:
> > > >  On 08/09/2010 09:30 PM, Ed Greshko wrote:
> > > > > Unfortunately it is late in the day and I don't have the time now to
> > > > > figure out what is "broken".
> > > >
> > > > Ah hah....
> > > >
> > > > I see the problem....but not sure how to fix yet.....
> > > >
> > > > In the Makefile you see..... at line 236
> > > >
> > > > ifneq (,$(findstring 2.4,$(LINUX_SRC)))
> > > >
> > > > Well....the current kernel is 2.6.33.6-147.2.4.fc13.i686.PAE which
> > > > contains the string 2.4 so the build thinks this is a 2.4 kernel build!
> > > >
> > > > My wife and cats are yelling at me......
> > >
> > > Hi Ed, and Mr. binary :)
> > >
> > > I did not keep the original build output from mr. binary ...
> > >
> > > Did the compilation error message look like this:
> > >
> > > ......
> > > /2010_0709_RT3572_Linux_STA_v2.4.0.1/os/linux/../../common/cmm_mac_usb.c:52:
> > > error: implicit declaration of function ‘usb_buffer_alloc’
> > >
> > > If so, then it has nothing to do with
> > > ifneq (,$(findstring 2.4,$(LINUX_SRC)))
> > >
> > > at all.
> > >
> > > It has to do with the fact that usb_buffer_alloc function is no longer
> > > present in the kernel sources of the linux version you are compiling for.
> > > Nor is it present in my kernel source 2.6.35-git1
> > >
> > > It was present in
> > >
> > > kernel-2.6.32.16-150.fc12.src/linux-2.6.32/drivers/usb/core/usb.c
> > >
> > > and exported via header file
> > >
> > > kernel-2.6.32.16-150.fc12.src/linux-2.6.32/include/linux/usb.h
> > >
> > > This function was taken out sometime kernel 2.6.32.16-150
> > >
> > > This is the problem with ralinktech. They do not keep up with
> > > linux kernel changes. They think one hat fits all is the way to go.
> > > Unlike, for example, VirtualBox - which has a separate release for
> > > several kernel revisions of Fedora.
> >
> > Does that mean I have to scrap the compile ideal and wait for them to
> > come out with a Linux  driver ?
>
> Don't hold your breath.
> What is your kernel version?

Yeah, your right about that.

2.6.33.6-147.2.4.fc13.i686

Can it also be compiled on a X86_64

[JD]

On 08/09/2010 09:31 AM, [e-mail] wrote:
> Yeah, your right about that.
>
> 2.6.33.6-147.2.4.fc13.i686
>
> Can it also be compiled on a X86_64

I do not think so. 2.6.33.6-147.2.4.fc13.i686 does not have this 
function defined either.

If you download the source rpm of 2.6.33.6-147.2.4.fc13 from
http://mirrors.kernel.org/fedora/updates/13/SRPMS/kernel-2.6.33.6-147.2.4.fc...
and run:
rpm -ivh kernel-2.6.33.6-147.2.4.fc13.src.rpm
then
cd ~/rpmbuild/SPECS
rpmbuild -bp kernel.spec
cd ../BUILD/
cd kernel-2.6.33/linux-2.6.33/staging
mv rt2860 rt2860.orig

At this point you will need my working rt2860 source code.

If you want to, I will email it to you personal email address.

you will then untar it in the staging dir you see above.

After you untar it,
cd ../..
cp /boot/config-2.6.33.6-147.2.4.fc13.i686  .config
make oldconfig
make xconfig
in xconfig,  scroll down til you see "staging" below "drivers"
click on staging
on the right hand side, scroll down and check rt2860

save (click on the floppy icon at top left)
exit from xconfig gui

make all

sudo make modules_install install

reboot into the newly built kernel (press return as soon as you get the 
grub boot screen)

From the grub menu, select the new kernel you just built (should be at 
the top).

Let me know.

[Ed Greshko]

On 08/09/2010 11:59 PM, JD wrote:
> On 08/09/2010 06:50 AM, Ed Greshko wrote:
> > On 08/09/2010 09:30 PM, Ed Greshko wrote:
> > > Unfortunately it is late in the day and I don't have the time now to
> > > figure out what is "broken".
> >
> > Ah hah....
> >
> > I see the problem....but not sure how to fix yet.....
> >
> > In the Makefile you see..... at line 236
> >
> > ifneq (,$(findstring 2.4,$(LINUX_SRC)))
> >
> > Well....the current kernel is 2.6.33.6-147.2.4.fc13.i686.PAE which
> > contains the string 2.4 so the build thinks this is a 2.4 kernel build!
> >
> > My wife and cats are yelling at me......
>
> Hi Ed, and Mr. binary :)
>
> I did not keep the original build output from mr. binary ...
>
> Did the compilation error message look like this:

No....  It did not....

You are taking this down the wrong road.  I have a perfectly built
module on the latest kernel.

So, I am done.  If you guys want to screw around and do something
else....be my guest.

Don't make life harder than it is.

Good night....and good luck.
> ...... 
> /2010_0709_RT3572_Linux_STA_v2.4.0.1/os/linux/../../common/cmm_mac_usb.c:52: 
> error: implicit declaration of function ‘usb_buffer_alloc’
>
> If so, then it has nothing to do with
> ifneq (,$(findstring 2.4,$(LINUX_SRC)))
>
> at all.
>
> It has to do with the fact that usb_buffer_alloc function is no longer 
> present in the kernel sources of the linux version you are compiling for.
> Nor is it present in my kernel source 2.6.35-git1
>
> It was present in
>
> kernel-2.6.32.16-150.fc12.src/linux-2.6.32/drivers/usb/core/usb.c
>
> and exported via header file
>
> kernel-2.6.32.16-150.fc12.src/linux-2.6.32/include/linux/usb.h
>
> This function was taken out sometime kernel 2.6.32.16-150
>
> This is the problem with ralinktech. They do not keep up with
> linux kernel changes. They think one hat fits all is the way to go.
> Unlike, for example, VirtualBox - which has a separate release for
> several kernel revisions of Fedora.

[JD]

On 08/09/2010 09:57 AM, Ed Greshko wrote:
> No....  It did not....

OK, Mr. binary - so what was the original compilation error message
that prompted you to start this thread?

Also, do you or do you not want to work with a working rt2860 driver
which I offered to send you?

[Mickey]

On 08/09/2010 02:01 PM, JD wrote:
> On 08/09/2010 09:57 AM, Ed Greshko wrote:
> > No....  It did not....
>
> OK, Mr. binary - so what was the original compilation error message
> that prompted you to start this thread?
>
> Also, do you or do you not want to work with a working rt2860 driver
> which I offered to send you?

I really would like for all of us  to work together on this, I'm sure 
you two gurus can put your heads together and solve it , so all Fedora users
would have it to use.

So please, Ed, JD  put your differences aside and work together.  I'm 
sure each of you will learn something new.

I really do appreciate you guys helping me.

[Ed Greshko]

On 08/10/2010 02:39 AM, [e-mail] wrote:
> On 08/09/2010 02:01 PM, JD wrote:
> > On 08/09/2010 09:57 AM, Ed Greshko wrote:
> > > No....  It did not....
> >
> > OK, Mr. binary - so what was the original compilation error message
> > that prompted you to start this thread?
> >
> > Also, do you or do you not want to work with a working rt2860 driver
> > which I offered to send you?
>
> I really would like for all of us  to work together on this, I'm sure 
> you two gurus can put your heads together and solve it , so all Fedora users
> would have it to use.
>
> So please, Ed, JD  put your differences aside and work together.  I'm 
> sure each of you will learn something new.
>
> I really do appreciate you guys helping me.

One more time.....

Did you make the changes I asked you to and try to recompile again?

It isn't a matter of differences.

I reproduced your problem....exactly....according to your compile output
that you posted on fpaste.org.

I then took the time to troubleshoot the Makefile process...and found
exactly what the problem was...I then made changes to the Makefile and
the other file....and I have successfully compiled the driver from the
exactly same source code tar file that you downloaded.

So....I have *actually* done it.  I am not sitting around speculating on
what may be the problem.

Again....

1.  I reproduced exactly your problem on my system.
2.  I found a fix for it.
3.  I successfully compiled.
4.  I told you what the how to fix it.

What more would you like?

It is 3:30AM here in Taiwan.  The only reason I'm writing this is my cat
woke me....

Have a look at

http://fpaste.org/WaSp/

Proof enough?

[JD]

On 08/09/2010 12:51 PM, Ed Greshko wrote:
> On 08/10/2010 02:39 AM, [e-mail] wrote:
> > On 08/09/2010 02:01 PM, JD wrote:
> > > On 08/09/2010 09:57 AM, Ed Greshko wrote:
> > > > No....  It did not....
> > >
> > > OK, Mr. binary - so what was the original compilation error message
> > > that prompted you to start this thread?
> > >
> > > Also, do you or do you not want to work with a working rt2860 driver
> > > which I offered to send you?
> >
> > I really would like for all of us  to work together on this, I'm sure
> > you two gurus can put your heads together and solve it , so all Fedora users
> > would have it to use.
> >
> > So please, Ed, JD  put your differences aside and work together.  I'm
> > sure each of you will learn something new.
> >
> > I really do appreciate you guys helping me.
>
> One more time.....
>
> Did you make the changes I asked you to and try to recompile again?
>
> It isn't a matter of differences.
>
> I reproduced your problem....exactly....according to your compile output
> that you posted on fpaste.org.
>
> I then took the time to troubleshoot the Makefile process...and found
> exactly what the problem was...I then made changes to the Makefile and
> the other file....and I have successfully compiled the driver from the
> exactly same source code tar file that you downloaded.
>
> So....I have *actually* done it.  I am not sitting around speculating on
> what may be the problem.
>
> Again....
> I reproduced exactly your problem on my system.
> I found a fix for it.
> I successfully compiled.
> I told you what the how to fix it.
>
> What more would you like?
>
> It is 3:30AM here in Taiwan.  The only reason I'm writing this is my cat
> woke me....
>
> Have a look at
>
> http://fpaste.org/WaSp/
>
> Proof enough?

Ed, perhaps his kernel differs from the one you are using.
I believe he is using the vanilla fedora kernel, and not the
rpmfusion kernel. Is this the case, Mr. BinaryNut?

[Mickey]

On 08/09/2010 04:29 PM, JD wrote:
> On 08/09/2010 12:51 PM, Ed Greshko wrote:
> > On 08/10/2010 02:39 AM, [e-mail] wrote:
> > > On 08/09/2010 02:01 PM, JD wrote:
> > > >  On 08/09/2010 09:57 AM, Ed Greshko wrote:
> > > > > No....  It did not....
> > > >
> > > > OK, Mr. binary - so what was the original compilation error message
> > > > that prompted you to start this thread?
> > > >
> > > > Also, do you or do you not want to work with a working rt2860 driver
> > > > which I offered to send you?
> > >
> > > I really would like for all of us  to work together on this, I'm sure
> > > you two gurus can put your heads together and solve it , so all Fedora users
> > > would have it to use.
> > >
> > > So please, Ed, JD  put your differences aside and work together.  I'm
> > > sure each of you will learn something new.
> > >
> > > I really do appreciate you guys helping me.
> >
> > One more time.....
> >
> > Did you make the changes I asked you to and try to recompile again?
> >
> > It isn't a matter of differences.
> >
> > I reproduced your problem....exactly....according to your compile output
> > that you posted on fpaste.org.
> >
> > I then took the time to troubleshoot the Makefile process...and found
> > exactly what the problem was...I then made changes to the Makefile and
> > the other file....and I have successfully compiled the driver from the
> > exactly same source code tar file that you downloaded.
> >
> > So....I have *actually* done it.  I am not sitting around speculating on
> > what may be the problem.
> >
> > Again....
> > I reproduced exactly your problem on my system.
> > I found a fix for it.
> > I successfully compiled.
> > I told you what the how to fix it.
> >
> > What more would you like?
> >
> > It is 3:30AM here in Taiwan.  The only reason I'm writing this is my cat
> > woke me....
> >
> > Have a look at
> >
> > http://fpaste.org/WaSp/
> >
> > Proof enough?
>
> Ed, perhaps his kernel differs from the one you are using.
> I believe he is using the vanilla fedora kernel, and not the
> rpmfusion kernel. Is this the case, Mr. BinaryNut?

Yes that is Correct.

[Mickey]

On 08/09/2010 04:29 PM, JD wrote:
> On 08/09/2010 12:51 PM, Ed Greshko wrote:
> > On 08/10/2010 02:39 AM, [e-mail] wrote:
> > > On 08/09/2010 02:01 PM, JD wrote:
> > > >  On 08/09/2010 09:57 AM, Ed Greshko wrote:
> > > > > No....  It did not....
> > > >
> > > > OK, Mr. binary - so what was the original compilation error message
> > > > that prompted you to start this thread?
> > > >
> > > > Also, do you or do you not want to work with a working rt2860 driver
> > > > which I offered to send you?
> > >
> > > I really would like for all of us  to work together on this, I'm sure
> > > you two gurus can put your heads together and solve it , so all Fedora users
> > > would have it to use.
> > >
> > > So please, Ed, JD  put your differences aside and work together.  I'm
> > > sure each of you will learn something new.
> > >
> > > I really do appreciate you guys helping me.
> >
> > One more time.....
> >
> > Did you make the changes I asked you to and try to recompile again?
> >
> > It isn't a matter of differences.
> >
> > I reproduced your problem....exactly....according to your compile output
> > that you posted on fpaste.org.
> >
> > I then took the time to troubleshoot the Makefile process...and found
> > exactly what the problem was...I then made changes to the Makefile and
> > the other file....and I have successfully compiled the driver from the
> > exactly same source code tar file that you downloaded.
> >
> > So....I have *actually* done it.  I am not sitting around speculating on
> > what may be the problem.
> >
> > Again....
> > I reproduced exactly your problem on my system.
> > I found a fix for it.
> > I successfully compiled.
> > I told you what the how to fix it.
> >
> > What more would you like?
> >
> > It is 3:30AM here in Taiwan.  The only reason I'm writing this is my cat
> > woke me....
> >
> > Have a look at
> >
> > http://fpaste.org/WaSp/
> >
> > Proof enough?
>
> Ed, perhaps his kernel differs from the one you are using.
> I believe he is using the vanilla fedora kernel, and not the
> rpmfusion kernel. Is this the case, Mr. BinaryNut?

I tried to install that kernel-src rpm and this is the output I get.

uname -a
Linux inspiron 2.6.33.6-147.2.4.fc13.i686 #1 SMP Fri Jul 23 17:27:40 UTC 
2010 i686 i686 i386 GNU/Linux

yum localinstall --nogpg kernel-2.6.33.6-147.2.4.fc13.src.rpm
Loaded plugins: presto, refresh-packagekit, remove-with-leaves
Setting up Local Package Process
Examining kernel-2.6.33.6-147.2.4.fc13.src.rpm: 
kernel-2.6.33.6-147.2.4.fc13.src
Cannot add package kernel-2.6.33.6-147.2.4.fc13.src.rpm to transaction. 
Not a compatible architecture: src

[JD]

On 08/09/2010 02:01 PM, [e-mail] wrote:
> On 08/09/2010 04:29 PM, JD wrote:
> > On 08/09/2010 12:51 PM, Ed Greshko wrote:
> > > On 08/10/2010 02:39 AM, [e-mail] wrote:
> > > >  On 08/09/2010 02:01 PM, JD wrote:
> > > > >   On 08/09/2010 09:57 AM, Ed Greshko wrote:
> > > > > > No....  It did not....
> > > > >
> > > > > OK, Mr. binary - so what was the original compilation error message
> > > > > that prompted you to start this thread?
> > > > >
> > > > > Also, do you or do you not want to work with a working rt2860 driver
> > > > > which I offered to send you?
> > > >
> > > > I really would like for all of us  to work together on this, I'm sure
> > > > you two gurus can put your heads together and solve it , so all Fedora users
> > > > would have it to use.
> > > >
> > > > So please, Ed, JD  put your differences aside and work together.  I'm
> > > > sure each of you will learn something new.
> > > >
> > > > I really do appreciate you guys helping me.
> > >
> > > One more time.....
> > >
> > > Did you make the changes I asked you to and try to recompile again?
> > >
> > > It isn't a matter of differences.
> > >
> > > I reproduced your problem....exactly....according to your compile output
> > > that you posted on fpaste.org.
> > >
> > > I then took the time to troubleshoot the Makefile process...and found
> > > exactly what the problem was...I then made changes to the Makefile and
> > > the other file....and I have successfully compiled the driver from the
> > > exactly same source code tar file that you downloaded.
> > >
> > > So....I have *actually* done it.  I am not sitting around speculating on
> > > what may be the problem.
> > >
> > > Again....
> > > I reproduced exactly your problem on my system.
> > > I found a fix for it.
> > > I successfully compiled.
> > > I told you what the how to fix it.
> > >
> > > What more would you like?
> > >
> > > It is 3:30AM here in Taiwan.  The only reason I'm writing this is my cat
> > > woke me....
> > >
> > > Have a look at
> > >
> > > http://fpaste.org/WaSp/
> > >
> > > Proof enough?
> >
> > Ed, perhaps his kernel differs from the one you are using.
> > I believe he is using the vanilla fedora kernel, and not the
> > rpmfusion kernel. Is this the case, Mr. BinaryNut?
>
> I tried to install that kernel-src rpm and this is the output I get.
>
> uname -a
> Linux inspiron 2.6.33.6-147.2.4.fc13.i686 #1 SMP Fri Jul 23 17:27:40 UTC
> 2010 i686 i686 i386 GNU/Linux
>
> yum localinstall --nogpg kernel-2.6.33.6-147.2.4.fc13.src.rpm
> Loaded plugins: presto, refresh-packagekit, remove-with-leaves
> Setting up Local Package Process
> Examining kernel-2.6.33.6-147.2.4.fc13.src.rpm:
> kernel-2.6.33.6-147.2.4.fc13.src
> Cannot add package kernel-2.6.33.6-147.2.4.fc13.src.rpm to transaction.
> Not a compatible architecture: src

That's not how you bring in the source rpm
do this:
cd ~/rpmbuild/SRPMS
wget -c -ndH 
http://mirrors.kernel.org/fedora/updates/13/SRPMS/kernel-2.6.33.6-147.2.4.fc...
rpm -ivh kernel-2.6.33.6-147.2.4.fc13.src.rpm
cd ../SPECS
rpmbuild -bp kernel.spec
cd ../BUILD/kernel-2.6.33.6/linux-2.6.33.6
cp /boot/config--2.6.33.6-147.2.4.fc13*  .config
make oldconfig
make xconfig
wait for the gui to come up
scroll down to the middle scroll bar down to Staging Drivers area, just 
above Filesystems
Click on Staging
On the right side scroll down to Ralink 2870/3070 which is compatible 
with your chipset.
Select it.
Click on the floppy icon at top left
quit
make all
sudo make modules_install install
reboot and in the grub screen, press any key to stop autoboot,
and select the kernel you just built - it will be at the top.

Let us know f it worked.

If it does not work, then you have to fall back on Ed's way of
installing the kmod stuff from rpmfusion.

[Mickey]

On 08/09/2010 03:51 PM, Ed Greshko wrote:
> On 08/10/2010 02:39 AM, [e-mail] wrote:
> > On 08/09/2010 02:01 PM, JD wrote:
> > > On 08/09/2010 09:57 AM, Ed Greshko wrote:
> > > > No....  It did not....
> > >
> > > OK, Mr. binary - so what was the original compilation error message
> > > that prompted you to start this thread?
> > >
> > > Also, do you or do you not want to work with a working rt2860 driver
> > > which I offered to send you?
> >
> > I really would like for all of us  to work together on this, I'm sure
> > you two gurus can put your heads together and solve it , so all Fedora users
> > would have it to use.
> >
> > So please, Ed, JD  put your differences aside and work together.  I'm
> > sure each of you will learn something new.
> >
> > I really do appreciate you guys helping me.
>
> One more time.....
>
> Did you make the changes I asked you to and try to recompile again?
>
> It isn't a matter of differences.
>
> I reproduced your problem....exactly....according to your compile output
> that you posted on fpaste.org.
>
> I then took the time to troubleshoot the Makefile process...and found
> exactly what the problem was...I then made changes to the Makefile and
> the other file....and I have successfully compiled the driver from the
> exactly same source code tar file that you downloaded.
>
> So....I have *actually* done it.  I am not sitting around speculating on
> what may be the problem.
>
> Again....
> I reproduced exactly your problem on my system.
> I found a fix for it.
> I successfully compiled.
> I told you what the how to fix it.
>
> What more would you like?
>
> It is 3:30AM here in Taiwan.  The only reason I'm writing this is my cat
> woke me....
>
> Have a look at
>
> http://fpaste.org/WaSp/
>
> Proof enough?

Yes I made the changes and the latest "make" dump is at  
http://fpaste.org/bAoE/

[Ed Greshko]

On 08/10/2010 04:53 AM, [e-mail] wrote:
> Yes I made the changes and the latest "make" dump is at  
> http://fpaste.org/bAoE/

I do not believe you made the correct changes....

The line 6 from your pastbin shows...

cp -f os/linux/Makefile.4
/home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/os/linux/Makefile

Notice "Makefile.4"....

This indicates that the build is still trying to do a kernel 2.4 build!

Would you accept a tar file emailed directly from me to try?

[Mickey]

On 08/09/2010 06:10 PM, Ed Greshko wrote:
> On 08/10/2010 04:53 AM, [e-mail] wrote:
> > Yes I made the changes and the latest "make" dump is at
> > http://fpaste.org/bAoE/
>
> I do not believe you made the correct changes....
>
> The line 6 from your pastbin shows...
>
> cp -f os/linux/Makefile.4
> /home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/os/linux/Makefile
>
> Notice "Makefile.4"....
>
> This indicates that the build is still trying to do a kernel 2.4 build!
>
> Would you accept a tar file emailed directly from me to try?

Yes,
Is it another RT3572.tar ?

[Ed Greshko]

On 08/10/2010 06:20 AM, [e-mail] wrote:
> On 08/09/2010 06:10 PM, Ed Greshko wrote:
> > On 08/10/2010 04:53 AM, [e-mail] wrote:
> > > Yes I made the changes and the latest "make" dump is at
> > > http://fpaste.org/bAoE/
> >
> > I do not believe you made the correct changes....
> >
> > The line 6 from your pastbin shows...
> >
> > cp -f os/linux/Makefile.4
> > /home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/os/linux/Makefile
> >
> > Notice "Makefile.4"....
> >
> > This indicates that the build is still trying to do a kernel 2.4 build!
> >
> > Would you accept a tar file emailed directly from me to try?
>
> Yes,
> Is it another RT3572.tar ?

No....it is just the same one with the proper modifications.

[Ed Greshko]

On 08/10/2010 06:20 AM, [e-mail] wrote:
> On 08/09/2010 06:10 PM, Ed Greshko wrote:
> > On 08/10/2010 04:53 AM, [e-mail] wrote:
> > > Yes I made the changes and the latest "make" dump is at
> > > http://fpaste.org/bAoE/
> >
> > I do not believe you made the correct changes....
> >
> > The line 6 from your pastbin shows...
> >
> > cp -f os/linux/Makefile.4
> > /home/jim/Downloads/RT3572/2010_0709_RT3572_Linux_STA_v2.4.0.1/os/linux/Makefile
> >
> > Notice "Makefile.4"....
> >
> > This indicates that the build is still trying to do a kernel 2.4 build!
> >
> > Would you accept a tar file emailed directly from me to try?
>
> Yes,
> Is it another RT3572.tar ?

I have just emailed to you a file named wusb600-drivers.tar.gz.  It is
the same file as you've downloaded from realtek with the exception that
2 files have been edited as previously described.

I changed the name of the base directory to wusb600-drivers to avoid
conflicting with the original file.  Untar, change to the
directory...and type make.

[Mickey]

PERFECT !!!!!  THANK YOU VERY MUCH  ED !!     And thank you JD for 
Your help.

ED I would like to put this out on a couple of Fedora Help Forums , 
there are many people out there that have tackled this with no success.

Could you send me the changes, to what files you did, and any comments.

Would you like to see the Output ?

I see it will allow me to do WPA now, my older adapter would only do WEP

Thank you again
Jim Tate

[Mickey]

On 08/09/2010 08:35 PM, [e-mail] wrote:
> PERFECT !!!!!  THANK YOU VERY MUCH  ED !!     And thank you JD for 
> Your help.
>
> ED I would like to put this out on a couple of Fedora Help Forums , 
> there are many people out there that have tackled this with no success.
>
> Could you send me the changes, to what files you did, and any comments.
>
> Would you like to see the Output ?
>
> I see it will allow me to do WPA now, my older adapter would only do WEP
>
> Thank you again
> Jim Tate

I forgot to ask,  Will this compile okay on X86_64  vanilla Kernel ?

[Ed Greshko]

On 08/10/2010 08:38 AM, [e-mail] wrote:
> I forgot to ask,  Will this compile okay on X86_64  vanilla Kernel ?

My guess is yes...assuming you have all the needed headers and such
installed.

I can't say that it will with 100% certainty since I don't have a x86_64
vanilla kernel system.

Whenever I wonder..."Will this work" I simply try it.  It answers all my
questions without the needless time spent on speculation.

[Mickey]

Ed I put a post on http://www.linuxquestions.org/questions/fedora-35/

Subj: Getting the Linksys WUSB600N ver. 2 working on Fedora   ,  8-10-2010

I tried to make it as simple as possible, by just posting the two 
modified files, if you want to comment on it.

[Ed Greshko]

On 08/10/2010 08:35 AM, [e-mail] wrote:
> PERFECT !!!!!  THANK YOU VERY MUCH  ED !!     And thank you JD for 
> Your help.
>
> ED I would like to put this out on a couple of Fedora Help Forums , 
> there are many people out there that have tackled this with no success.

You are welcome.   Folks should be reminded from time to time about
Occam's razor.  To paraphrase, the simplest explanation is usually the
correct one.
> Could you send me the changes, to what files you did, and any comments.

It is there.....

[egreshko@f13 wusb600-drivers]$ pwd
/home/egreshko/src/wusb600-drivers
[egreshko@f13 wusb600-drivers]$ diff Makefile Makefile-orig
236c236
< ifneq (,$(findstring 2.9,$(LINUX_SRC)))
---
> ifneq (,$(findstring 2.4,$(LINUX_SRC)))

258c258
< ifneq (,$(findstring 2.9,$(LINUX_SRC)))
---
> ifneq (,$(findstring 2.4,$(LINUX_SRC)))

269c269
< ifneq (,$(findstring 2.9,$(LINUX_SRC)))
---
> ifneq (,$(findstring 2.4,$(LINUX_SRC)))

278c278
< ifneq (,$(findstring 2.9,$(LINUX_SRC)))
---
> ifneq (,$(findstring 2.4,$(LINUX_SRC)))

and

[egreshko@f13 linux]$ diff config.mk config.mk-orig
11c11
< HAS_WPA_SUPPLICANT=y
---
> HAS_WPA_SUPPLICANT=n

14c14
< HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y
---
> HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=n

400c400
<     ifneq (,$(findstring 2.9,$(LINUX_SRC)))
---
> ifneq (,$(findstring 2.4,$(LINUX_SRC)))

458c458
<     ifneq (,$(findstring 2.9,$(LINUX_SRC)))
---
> ifneq (,$(findstring 2.4,$(LINUX_SRC)))

Comment....

The *key* (as previously noted) is the string 2.4 is being matched in
the current kernel name.  So, 2.4 in the ifneq statement needs to be
changed so it *does not* match since this is in reality a 2.6 kernel. 
Maybe I confused you since I changed it to 2.9 because I am too lazy to
change it to 9999.9999 or something equally unlikely to be in the kernel
name.

Also, FWIW, only the first change in the findstring line of config.mk is
really needed.  I, again, was too lazy to change it back.
> Would you like to see the Output ?

No thank you.  I've seen the correct output too many times.
> I see it will allow me to do WPA now, my older adapter would only do WEP
>
> Thank you again
> Jim Tate

[Mickey]

I was running the rpm -ivh  and all of a sudden I get this, I didn't 
install a Group mockbuild

warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
[root@inspiron Downloads]#

[JD]

On 08/09/2010 02:22 PM, [e-mail] wrote:
> I was running the rpm -ivh  and all of a sudden I get this, I didn't
> install a Group mockbuild
>
> warning: group mockbuild does not exist - using root
> warning: user mockbuild does not exist - using root
> warning: group mockbuild does not exist - using root
> warning: user mockbuild does not exist - using root
> warning: group mockbuild does not exist - using root
> warning: user mockbuild does not exist - using root
> warning: group mockbuild does not exist - using root
> warning: user mockbuild does not exist - using root
> warning: group mockbuild does not exist - using root
> warning: user mockbuild does not exist - using root
> warning: group mockbuild does not exist - using root
> [root@inspiron Downloads]#

Ignore it it is only a warning.
Proceed as I emailed you.

[JD]

On 08/09/2010 05:06 AM, [e-mail] wrote:
> On 08/08/2010 07:46 PM, JD wrote:
> > On 08/08/2010 04:36 PM, Ed Greshko wrote:
> > > On 08/09/2010 07:23 AM, [e-mail] wrote:
> > > > The compile didn't even get this far before changes were made below.
> > > >
> > > > Added {USB_DEVICE(0×1737,0×0079)}, /* Linksys WUSB600N v2 */        to
> > > > /common/rtusb_dev_id.c     file
> > > >
> > > > And modify     /os/linux/config.mk     file
> > > >  # Support Wpa_Supplicant
> > > >
> > > > HAS_WPA_SUPPLICANT=y
> > > >
> > > > # Support Native WpaSupplicant for Network Maganger
> > > > HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y
> > >
> > > Compiles just fine here before and after the changes...
> > >
> > > F13, 2.6.33.6-147.fc13.i686.PAE
> > >
> > > Are you 32 or 64 bit?
> >
> > Also, be sure that /lib/modules/`uname -r`/build
> > symlink points to the directory /usr/src/kernels/`uname -r`
> > Of course, assuming that you have installed kernel-devel-`uname-r`  rpm.
>
> The kernel-devel kernel-headers are installed.
>
> And /build does point to /usr/src/kernel

/lib/modules/build must point to /usr/src/kernels/2.6.33.....etc

/usr/src/kernel does not exist.

[Mickey]

On 08/09/2010 09:42 AM, JD wrote:
> On 08/09/2010 05:06 AM, [e-mail] wrote:
> > On 08/08/2010 07:46 PM, JD wrote:
> > >  On 08/08/2010 04:36 PM, Ed Greshko wrote:
> > > >  On 08/09/2010 07:23 AM, [e-mail] wrote:
> > > > > The compile didn't even get this far before changes were made below.
> > > > >
> > > > > Added {USB_DEVICE(0×1737,0×0079)}, /* Linksys WUSB600N v2 */        to
> > > > > /common/rtusb_dev_id.c     file
> > > > >
> > > > > And modify     /os/linux/config.mk     file
> > > > >   # Support Wpa_Supplicant
> > > > >
> > > > > HAS_WPA_SUPPLICANT=y
> > > > >
> > > > > # Support Native WpaSupplicant for Network Maganger
> > > > > HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y
> > > >
> > > > Compiles just fine here before and after the changes...
> > > >
> > > > F13, 2.6.33.6-147.fc13.i686.PAE
> > > >
> > > > Are you 32 or 64 bit?
> > >
> > > Also, be sure that /lib/modules/`uname -r`/build
> > > symlink points to the directory /usr/src/kernels/`uname -r`
> > > Of course, assuming that you have installed kernel-devel-`uname-r`  rpm.
> >
> > The kernel-devel kernel-headers are installed.
> >
> > And /build does point to /usr/src/kernel
>
> /lib/modules/build must point to /usr/src/kernels/2.6.33.....etc
>
> /usr/src/kernel does not exist.

Yes it is there
/usr/src/kernels/2.6.33.6-147.2.4.fc13.i686

[Mickey]

On 08/08/2010 07:36 PM, Ed Greshko wrote:
> On 08/09/2010 07:23 AM, [e-mail] wrote:
> > The compile didn't even get this far before changes were made below.
> >
> > Added {USB_DEVICE(0×1737,0×0079)}, /* Linksys WUSB600N v2 */        to
> > /common/rtusb_dev_id.c     file
> >
> > And modify     /os/linux/config.mk     file
> >
> > # Support Wpa_Supplicant
> > HAS_WPA_SUPPLICANT=y
> >
> > # Support Native WpaSupplicant for Network Maganger
> > HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y
>
> Compiles just fine here before and after the changes...
>
> F13, 2.6.33.6-147.fc13.i686.PAE
>
> Are you 32 or 64 bit?

i'm compiling on a 32 bit laptop,   but if I can get this adapter to 
work I want to compile it on a 64 bit PC .

[Mickey]

On 08/07/2010 08:58 PM, Ed Greshko wrote:
> On 08/08/2010 08:51 AM, JD wrote:
> > On 08/07/2010 03:56 PM, [e-mail] wrote:
> > > fedora 13
> > >
> > > A Linksys  wireless WUSB600 ver. 2
> > >
> > > Does anyone know about a Driver for this device , in all wireless sites
> > > they say a ver.1 is supported but not ver. 2 ?
> >
> > The  Linksys WUSB600N  driver is available in the unsupported
> > section of the vanilla kernel.
> > The chipset in the WUSB600N is the RalinkTech 2860, so the driver
> > is the rt2860.
> >
> > To try it (and I doubt very much it will work), you need to get the
> > source rpm
> > of your kernel version, and configure it manually (make xconfig) and
> > select the rt2860 from the "staging" drivers.
>
> That isn't quite accurate....
>
> One can install rt2860 and kmod-rt2860 packages from rpmfusion and cards
> based on that chipset should work just fine.   My HP system has that and
> I've had no problems with it.
>
> Ed

Do you have the ver. 1 or 2 of the WUSB600N ?