Error compiling drivers for Ralink RT2870
up vote
14
down vote
favorite
Im trying to install drivers for a rosewill RNX-N600UBE wireless card (Ralink RT2870 chipset) on Kali Linux. I downloaded the drivers form their website and unpacked/unzipped them, but now when i try to run the 'make' command i get this error.
/home/fox/System/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux/../../os/linux/rt_linux.c:1156:20: error: incompatible types when assigning to type ‘int’ from type ‘kuid_t’
/home/fox/System/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux/../../os/linux/rt_linux.c:1157:20: error: incompatible types when assigning to type ‘int’ from type ‘kgid_t’
make[4]: *** [/home/fox/System/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux/../../os/linux/rt_linux.o] Error 1
make[3]: *** [_module_/home/fox/System/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux] Error 2
make[2]: *** [sub-make] Error 2
make[1]: *** [all] Error 2
linux compiling drivers wifi
add a comment |
up vote
14
down vote
favorite
Im trying to install drivers for a rosewill RNX-N600UBE wireless card (Ralink RT2870 chipset) on Kali Linux. I downloaded the drivers form their website and unpacked/unzipped them, but now when i try to run the 'make' command i get this error.
/home/fox/System/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux/../../os/linux/rt_linux.c:1156:20: error: incompatible types when assigning to type ‘int’ from type ‘kuid_t’
/home/fox/System/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux/../../os/linux/rt_linux.c:1157:20: error: incompatible types when assigning to type ‘int’ from type ‘kgid_t’
make[4]: *** [/home/fox/System/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux/../../os/linux/rt_linux.o] Error 1
make[3]: *** [_module_/home/fox/System/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux] Error 2
make[2]: *** [sub-make] Error 2
make[1]: *** [all] Error 2
linux compiling drivers wifi
I think you might need a different version of something, maybe the compiler?
– PlasmaPower
Apr 16 '14 at 13:43
As a side-note, why would someone new to Linux fiddle with Kali? Thats a distro for security tests and attacks, packed with low level tools. Surely not meant for an unexperienced linux user
– MestreLion
Oct 19 at 5:05
add a comment |
up vote
14
down vote
favorite
up vote
14
down vote
favorite
Im trying to install drivers for a rosewill RNX-N600UBE wireless card (Ralink RT2870 chipset) on Kali Linux. I downloaded the drivers form their website and unpacked/unzipped them, but now when i try to run the 'make' command i get this error.
/home/fox/System/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux/../../os/linux/rt_linux.c:1156:20: error: incompatible types when assigning to type ‘int’ from type ‘kuid_t’
/home/fox/System/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux/../../os/linux/rt_linux.c:1157:20: error: incompatible types when assigning to type ‘int’ from type ‘kgid_t’
make[4]: *** [/home/fox/System/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux/../../os/linux/rt_linux.o] Error 1
make[3]: *** [_module_/home/fox/System/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux] Error 2
make[2]: *** [sub-make] Error 2
make[1]: *** [all] Error 2
linux compiling drivers wifi
Im trying to install drivers for a rosewill RNX-N600UBE wireless card (Ralink RT2870 chipset) on Kali Linux. I downloaded the drivers form their website and unpacked/unzipped them, but now when i try to run the 'make' command i get this error.
/home/fox/System/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux/../../os/linux/rt_linux.c:1156:20: error: incompatible types when assigning to type ‘int’ from type ‘kuid_t’
/home/fox/System/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux/../../os/linux/rt_linux.c:1157:20: error: incompatible types when assigning to type ‘int’ from type ‘kgid_t’
make[4]: *** [/home/fox/System/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux/../../os/linux/rt_linux.o] Error 1
make[3]: *** [_module_/home/fox/System/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux] Error 2
make[2]: *** [sub-make] Error 2
make[1]: *** [all] Error 2
linux compiling drivers wifi
linux compiling drivers wifi
edited Nov 24 at 20:13
Rui F Ribeiro
38.3k1476127
38.3k1476127
asked Apr 16 '14 at 10:26
Fox
71113
71113
I think you might need a different version of something, maybe the compiler?
– PlasmaPower
Apr 16 '14 at 13:43
As a side-note, why would someone new to Linux fiddle with Kali? Thats a distro for security tests and attacks, packed with low level tools. Surely not meant for an unexperienced linux user
– MestreLion
Oct 19 at 5:05
add a comment |
I think you might need a different version of something, maybe the compiler?
– PlasmaPower
Apr 16 '14 at 13:43
As a side-note, why would someone new to Linux fiddle with Kali? Thats a distro for security tests and attacks, packed with low level tools. Surely not meant for an unexperienced linux user
– MestreLion
Oct 19 at 5:05
I think you might need a different version of something, maybe the compiler?
– PlasmaPower
Apr 16 '14 at 13:43
I think you might need a different version of something, maybe the compiler?
– PlasmaPower
Apr 16 '14 at 13:43
As a side-note, why would someone new to Linux fiddle with Kali? Thats a distro for security tests and attacks, packed with low level tools. Surely not meant for an unexperienced linux user
– MestreLion
Oct 19 at 5:05
As a side-note, why would someone new to Linux fiddle with Kali? Thats a distro for security tests and attacks, packed with low level tools. Surely not meant for an unexperienced linux user
– MestreLion
Oct 19 at 5:05
add a comment |
4 Answers
4
active
oldest
votes
up vote
19
down vote
The issue is that one of the kernel headers / interfaces changed in a recent 3.x kernel. Where a UID / GID values were originally referred to as regular integers, they are now structs with a single element. Any code relying on the older definition now will fail to compile until updated to match the new kernel headers.
I'm currently experimenting with patching a similar error in virtualbox-guest-utils for my Ubuntu install; in theory locating and replacing instances of ->i_uid =
with ->i_uid.val =
or ->i_gid =
with ->i_gid.val =
on the line numbers reported in the error should fix the problem (but I can't guarantee that at this time as compilation is now failing on a different, unrelated, error for me).
Your best bet is contacting the original author of your code for an updated version of the source that works with the newer kernels.
7
Tested! This DOES work! I changedcurrent_fsuid()
tocurrent_fsuid().val
– Jonathan
Apr 27 '15 at 0:09
1
For me, I also had to changecurrent_fsgid()
tocurrent_fsgid().val
– sand_storm_of_code.txt
Oct 14 '15 at 11:22
@JonathanLeaders touché Thanks. However, the patch convertingint
tokuid_t
also seems to do the trick.
– enthusiasticgeek
Oct 16 '15 at 16:00
worked like a charm! Thank you!
– XMight
Mar 24 '17 at 17:39
add a comment |
up vote
10
down vote
I found a fix to the compilation errors in another driver on this website:
http://www.arnelborja.com/compiling-rt2870-wifi-driver-in-fedora/
below is the patch content:
--- include/os/rt_linux.h 2013-09-12 13:27:14.000000000 +0800
+++ include/os/rt_linux.h.patched 2014-03-23 11:45:03.907628847 +0800
@@ -279,8 +279,8 @@ typedef struct file* RTMP_OS_FD;
typedef struct _OS_FS_INFO_
{
- int fsuid;
- int fsgid;
+ kuid_t fsuid;
+ kgid_t fsgid;
mm_segment_t fs;
} OS_FS_INFO;
1
This is a good, working solution for the MT7601U driver, used for the Mediatek/Ralink 148F:7601 chipset, as well. (Yes, I'm just adding these keywords for SEO reasons.)
– billyjmc
Mar 30 '15 at 3:29
for my kernel 4.13.16-302.fc27.x86_64 on Fedora 27, this don't work anymore. Fails with compiling error.
– kmonsoor
Dec 9 '17 at 12:27
@billyjmc: just note that, as-is, this solution does not work for kernels < 3.5, wherekuid_t
andkgid_t
were introduced. For those,k
must be dropped, as inuid_t fsuid;
andgid_t fsgid;
– MestreLion
Oct 19 at 5:10
add a comment |
up vote
2
down vote
make
only reports the errors but they are in fact errors from your compiler (probably gcc):
error: incompatible types when assigning to type ‘int’ from type ‘kuid_t’
Basically, your code is buggy or inappropriate for your platform but make
functions correctly.
add a comment |
up vote
1
down vote
This solution worked for me. The procedure I followed was:
I followed the steps for my distribution (Debian Jessie) from here.
I saved de driver for Linux of the manufacturer (which comes with the equipment in the CDROM), and I unzipped it to a folder.
In the folder, I typed
make
(asroot
), and I got an error. So, I did the modification above, and it worked.I typed
make install
(asroot
), I rebooted the computer, and the wireless interface was recognized. I configured it and it worked. ;)
My system is: Debian Jessie, kernel 3.16.0-4-amd64, using gnome.
add a comment |
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
19
down vote
The issue is that one of the kernel headers / interfaces changed in a recent 3.x kernel. Where a UID / GID values were originally referred to as regular integers, they are now structs with a single element. Any code relying on the older definition now will fail to compile until updated to match the new kernel headers.
I'm currently experimenting with patching a similar error in virtualbox-guest-utils for my Ubuntu install; in theory locating and replacing instances of ->i_uid =
with ->i_uid.val =
or ->i_gid =
with ->i_gid.val =
on the line numbers reported in the error should fix the problem (but I can't guarantee that at this time as compilation is now failing on a different, unrelated, error for me).
Your best bet is contacting the original author of your code for an updated version of the source that works with the newer kernels.
7
Tested! This DOES work! I changedcurrent_fsuid()
tocurrent_fsuid().val
– Jonathan
Apr 27 '15 at 0:09
1
For me, I also had to changecurrent_fsgid()
tocurrent_fsgid().val
– sand_storm_of_code.txt
Oct 14 '15 at 11:22
@JonathanLeaders touché Thanks. However, the patch convertingint
tokuid_t
also seems to do the trick.
– enthusiasticgeek
Oct 16 '15 at 16:00
worked like a charm! Thank you!
– XMight
Mar 24 '17 at 17:39
add a comment |
up vote
19
down vote
The issue is that one of the kernel headers / interfaces changed in a recent 3.x kernel. Where a UID / GID values were originally referred to as regular integers, they are now structs with a single element. Any code relying on the older definition now will fail to compile until updated to match the new kernel headers.
I'm currently experimenting with patching a similar error in virtualbox-guest-utils for my Ubuntu install; in theory locating and replacing instances of ->i_uid =
with ->i_uid.val =
or ->i_gid =
with ->i_gid.val =
on the line numbers reported in the error should fix the problem (but I can't guarantee that at this time as compilation is now failing on a different, unrelated, error for me).
Your best bet is contacting the original author of your code for an updated version of the source that works with the newer kernels.
7
Tested! This DOES work! I changedcurrent_fsuid()
tocurrent_fsuid().val
– Jonathan
Apr 27 '15 at 0:09
1
For me, I also had to changecurrent_fsgid()
tocurrent_fsgid().val
– sand_storm_of_code.txt
Oct 14 '15 at 11:22
@JonathanLeaders touché Thanks. However, the patch convertingint
tokuid_t
also seems to do the trick.
– enthusiasticgeek
Oct 16 '15 at 16:00
worked like a charm! Thank you!
– XMight
Mar 24 '17 at 17:39
add a comment |
up vote
19
down vote
up vote
19
down vote
The issue is that one of the kernel headers / interfaces changed in a recent 3.x kernel. Where a UID / GID values were originally referred to as regular integers, they are now structs with a single element. Any code relying on the older definition now will fail to compile until updated to match the new kernel headers.
I'm currently experimenting with patching a similar error in virtualbox-guest-utils for my Ubuntu install; in theory locating and replacing instances of ->i_uid =
with ->i_uid.val =
or ->i_gid =
with ->i_gid.val =
on the line numbers reported in the error should fix the problem (but I can't guarantee that at this time as compilation is now failing on a different, unrelated, error for me).
Your best bet is contacting the original author of your code for an updated version of the source that works with the newer kernels.
The issue is that one of the kernel headers / interfaces changed in a recent 3.x kernel. Where a UID / GID values were originally referred to as regular integers, they are now structs with a single element. Any code relying on the older definition now will fail to compile until updated to match the new kernel headers.
I'm currently experimenting with patching a similar error in virtualbox-guest-utils for my Ubuntu install; in theory locating and replacing instances of ->i_uid =
with ->i_uid.val =
or ->i_gid =
with ->i_gid.val =
on the line numbers reported in the error should fix the problem (but I can't guarantee that at this time as compilation is now failing on a different, unrelated, error for me).
Your best bet is contacting the original author of your code for an updated version of the source that works with the newer kernels.
answered Jul 24 '14 at 14:06
Jason Musgrove
46634
46634
7
Tested! This DOES work! I changedcurrent_fsuid()
tocurrent_fsuid().val
– Jonathan
Apr 27 '15 at 0:09
1
For me, I also had to changecurrent_fsgid()
tocurrent_fsgid().val
– sand_storm_of_code.txt
Oct 14 '15 at 11:22
@JonathanLeaders touché Thanks. However, the patch convertingint
tokuid_t
also seems to do the trick.
– enthusiasticgeek
Oct 16 '15 at 16:00
worked like a charm! Thank you!
– XMight
Mar 24 '17 at 17:39
add a comment |
7
Tested! This DOES work! I changedcurrent_fsuid()
tocurrent_fsuid().val
– Jonathan
Apr 27 '15 at 0:09
1
For me, I also had to changecurrent_fsgid()
tocurrent_fsgid().val
– sand_storm_of_code.txt
Oct 14 '15 at 11:22
@JonathanLeaders touché Thanks. However, the patch convertingint
tokuid_t
also seems to do the trick.
– enthusiasticgeek
Oct 16 '15 at 16:00
worked like a charm! Thank you!
– XMight
Mar 24 '17 at 17:39
7
7
Tested! This DOES work! I changed
current_fsuid()
to current_fsuid().val
– Jonathan
Apr 27 '15 at 0:09
Tested! This DOES work! I changed
current_fsuid()
to current_fsuid().val
– Jonathan
Apr 27 '15 at 0:09
1
1
For me, I also had to change
current_fsgid()
to current_fsgid().val
– sand_storm_of_code.txt
Oct 14 '15 at 11:22
For me, I also had to change
current_fsgid()
to current_fsgid().val
– sand_storm_of_code.txt
Oct 14 '15 at 11:22
@JonathanLeaders touché Thanks. However, the patch converting
int
to kuid_t
also seems to do the trick.– enthusiasticgeek
Oct 16 '15 at 16:00
@JonathanLeaders touché Thanks. However, the patch converting
int
to kuid_t
also seems to do the trick.– enthusiasticgeek
Oct 16 '15 at 16:00
worked like a charm! Thank you!
– XMight
Mar 24 '17 at 17:39
worked like a charm! Thank you!
– XMight
Mar 24 '17 at 17:39
add a comment |
up vote
10
down vote
I found a fix to the compilation errors in another driver on this website:
http://www.arnelborja.com/compiling-rt2870-wifi-driver-in-fedora/
below is the patch content:
--- include/os/rt_linux.h 2013-09-12 13:27:14.000000000 +0800
+++ include/os/rt_linux.h.patched 2014-03-23 11:45:03.907628847 +0800
@@ -279,8 +279,8 @@ typedef struct file* RTMP_OS_FD;
typedef struct _OS_FS_INFO_
{
- int fsuid;
- int fsgid;
+ kuid_t fsuid;
+ kgid_t fsgid;
mm_segment_t fs;
} OS_FS_INFO;
1
This is a good, working solution for the MT7601U driver, used for the Mediatek/Ralink 148F:7601 chipset, as well. (Yes, I'm just adding these keywords for SEO reasons.)
– billyjmc
Mar 30 '15 at 3:29
for my kernel 4.13.16-302.fc27.x86_64 on Fedora 27, this don't work anymore. Fails with compiling error.
– kmonsoor
Dec 9 '17 at 12:27
@billyjmc: just note that, as-is, this solution does not work for kernels < 3.5, wherekuid_t
andkgid_t
were introduced. For those,k
must be dropped, as inuid_t fsuid;
andgid_t fsgid;
– MestreLion
Oct 19 at 5:10
add a comment |
up vote
10
down vote
I found a fix to the compilation errors in another driver on this website:
http://www.arnelborja.com/compiling-rt2870-wifi-driver-in-fedora/
below is the patch content:
--- include/os/rt_linux.h 2013-09-12 13:27:14.000000000 +0800
+++ include/os/rt_linux.h.patched 2014-03-23 11:45:03.907628847 +0800
@@ -279,8 +279,8 @@ typedef struct file* RTMP_OS_FD;
typedef struct _OS_FS_INFO_
{
- int fsuid;
- int fsgid;
+ kuid_t fsuid;
+ kgid_t fsgid;
mm_segment_t fs;
} OS_FS_INFO;
1
This is a good, working solution for the MT7601U driver, used for the Mediatek/Ralink 148F:7601 chipset, as well. (Yes, I'm just adding these keywords for SEO reasons.)
– billyjmc
Mar 30 '15 at 3:29
for my kernel 4.13.16-302.fc27.x86_64 on Fedora 27, this don't work anymore. Fails with compiling error.
– kmonsoor
Dec 9 '17 at 12:27
@billyjmc: just note that, as-is, this solution does not work for kernels < 3.5, wherekuid_t
andkgid_t
were introduced. For those,k
must be dropped, as inuid_t fsuid;
andgid_t fsgid;
– MestreLion
Oct 19 at 5:10
add a comment |
up vote
10
down vote
up vote
10
down vote
I found a fix to the compilation errors in another driver on this website:
http://www.arnelborja.com/compiling-rt2870-wifi-driver-in-fedora/
below is the patch content:
--- include/os/rt_linux.h 2013-09-12 13:27:14.000000000 +0800
+++ include/os/rt_linux.h.patched 2014-03-23 11:45:03.907628847 +0800
@@ -279,8 +279,8 @@ typedef struct file* RTMP_OS_FD;
typedef struct _OS_FS_INFO_
{
- int fsuid;
- int fsgid;
+ kuid_t fsuid;
+ kgid_t fsgid;
mm_segment_t fs;
} OS_FS_INFO;
I found a fix to the compilation errors in another driver on this website:
http://www.arnelborja.com/compiling-rt2870-wifi-driver-in-fedora/
below is the patch content:
--- include/os/rt_linux.h 2013-09-12 13:27:14.000000000 +0800
+++ include/os/rt_linux.h.patched 2014-03-23 11:45:03.907628847 +0800
@@ -279,8 +279,8 @@ typedef struct file* RTMP_OS_FD;
typedef struct _OS_FS_INFO_
{
- int fsuid;
- int fsgid;
+ kuid_t fsuid;
+ kgid_t fsgid;
mm_segment_t fs;
} OS_FS_INFO;
edited Sep 28 '14 at 15:00
maxschlepzig
33.1k32135208
33.1k32135208
answered Sep 28 '14 at 14:26
Geert Kroone
10112
10112
1
This is a good, working solution for the MT7601U driver, used for the Mediatek/Ralink 148F:7601 chipset, as well. (Yes, I'm just adding these keywords for SEO reasons.)
– billyjmc
Mar 30 '15 at 3:29
for my kernel 4.13.16-302.fc27.x86_64 on Fedora 27, this don't work anymore. Fails with compiling error.
– kmonsoor
Dec 9 '17 at 12:27
@billyjmc: just note that, as-is, this solution does not work for kernels < 3.5, wherekuid_t
andkgid_t
were introduced. For those,k
must be dropped, as inuid_t fsuid;
andgid_t fsgid;
– MestreLion
Oct 19 at 5:10
add a comment |
1
This is a good, working solution for the MT7601U driver, used for the Mediatek/Ralink 148F:7601 chipset, as well. (Yes, I'm just adding these keywords for SEO reasons.)
– billyjmc
Mar 30 '15 at 3:29
for my kernel 4.13.16-302.fc27.x86_64 on Fedora 27, this don't work anymore. Fails with compiling error.
– kmonsoor
Dec 9 '17 at 12:27
@billyjmc: just note that, as-is, this solution does not work for kernels < 3.5, wherekuid_t
andkgid_t
were introduced. For those,k
must be dropped, as inuid_t fsuid;
andgid_t fsgid;
– MestreLion
Oct 19 at 5:10
1
1
This is a good, working solution for the MT7601U driver, used for the Mediatek/Ralink 148F:7601 chipset, as well. (Yes, I'm just adding these keywords for SEO reasons.)
– billyjmc
Mar 30 '15 at 3:29
This is a good, working solution for the MT7601U driver, used for the Mediatek/Ralink 148F:7601 chipset, as well. (Yes, I'm just adding these keywords for SEO reasons.)
– billyjmc
Mar 30 '15 at 3:29
for my kernel 4.13.16-302.fc27.x86_64 on Fedora 27, this don't work anymore. Fails with compiling error.
– kmonsoor
Dec 9 '17 at 12:27
for my kernel 4.13.16-302.fc27.x86_64 on Fedora 27, this don't work anymore. Fails with compiling error.
– kmonsoor
Dec 9 '17 at 12:27
@billyjmc: just note that, as-is, this solution does not work for kernels < 3.5, where
kuid_t
and kgid_t
were introduced. For those, k
must be dropped, as in uid_t fsuid;
and gid_t fsgid;
– MestreLion
Oct 19 at 5:10
@billyjmc: just note that, as-is, this solution does not work for kernels < 3.5, where
kuid_t
and kgid_t
were introduced. For those, k
must be dropped, as in uid_t fsuid;
and gid_t fsgid;
– MestreLion
Oct 19 at 5:10
add a comment |
up vote
2
down vote
make
only reports the errors but they are in fact errors from your compiler (probably gcc):
error: incompatible types when assigning to type ‘int’ from type ‘kuid_t’
Basically, your code is buggy or inappropriate for your platform but make
functions correctly.
add a comment |
up vote
2
down vote
make
only reports the errors but they are in fact errors from your compiler (probably gcc):
error: incompatible types when assigning to type ‘int’ from type ‘kuid_t’
Basically, your code is buggy or inappropriate for your platform but make
functions correctly.
add a comment |
up vote
2
down vote
up vote
2
down vote
make
only reports the errors but they are in fact errors from your compiler (probably gcc):
error: incompatible types when assigning to type ‘int’ from type ‘kuid_t’
Basically, your code is buggy or inappropriate for your platform but make
functions correctly.
make
only reports the errors but they are in fact errors from your compiler (probably gcc):
error: incompatible types when assigning to type ‘int’ from type ‘kuid_t’
Basically, your code is buggy or inappropriate for your platform but make
functions correctly.
answered Apr 16 '14 at 10:31
lgeorget
8,76622450
8,76622450
add a comment |
add a comment |
up vote
1
down vote
This solution worked for me. The procedure I followed was:
I followed the steps for my distribution (Debian Jessie) from here.
I saved de driver for Linux of the manufacturer (which comes with the equipment in the CDROM), and I unzipped it to a folder.
In the folder, I typed
make
(asroot
), and I got an error. So, I did the modification above, and it worked.I typed
make install
(asroot
), I rebooted the computer, and the wireless interface was recognized. I configured it and it worked. ;)
My system is: Debian Jessie, kernel 3.16.0-4-amd64, using gnome.
add a comment |
up vote
1
down vote
This solution worked for me. The procedure I followed was:
I followed the steps for my distribution (Debian Jessie) from here.
I saved de driver for Linux of the manufacturer (which comes with the equipment in the CDROM), and I unzipped it to a folder.
In the folder, I typed
make
(asroot
), and I got an error. So, I did the modification above, and it worked.I typed
make install
(asroot
), I rebooted the computer, and the wireless interface was recognized. I configured it and it worked. ;)
My system is: Debian Jessie, kernel 3.16.0-4-amd64, using gnome.
add a comment |
up vote
1
down vote
up vote
1
down vote
This solution worked for me. The procedure I followed was:
I followed the steps for my distribution (Debian Jessie) from here.
I saved de driver for Linux of the manufacturer (which comes with the equipment in the CDROM), and I unzipped it to a folder.
In the folder, I typed
make
(asroot
), and I got an error. So, I did the modification above, and it worked.I typed
make install
(asroot
), I rebooted the computer, and the wireless interface was recognized. I configured it and it worked. ;)
My system is: Debian Jessie, kernel 3.16.0-4-amd64, using gnome.
This solution worked for me. The procedure I followed was:
I followed the steps for my distribution (Debian Jessie) from here.
I saved de driver for Linux of the manufacturer (which comes with the equipment in the CDROM), and I unzipped it to a folder.
In the folder, I typed
make
(asroot
), and I got an error. So, I did the modification above, and it worked.I typed
make install
(asroot
), I rebooted the computer, and the wireless interface was recognized. I configured it and it worked. ;)
My system is: Debian Jessie, kernel 3.16.0-4-amd64, using gnome.
edited Jul 17 '16 at 17:14
clk
1,5741821
1,5741821
answered Jul 17 '16 at 15:56
Isaias Soares
111
111
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f125039%2ferror-compiling-drivers-for-ralink-rt2870%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I think you might need a different version of something, maybe the compiler?
– PlasmaPower
Apr 16 '14 at 13:43
As a side-note, why would someone new to Linux fiddle with Kali? Thats a distro for security tests and attacks, packed with low level tools. Surely not meant for an unexperienced linux user
– MestreLion
Oct 19 at 5:05