Please Help me! Cant get my Wireless to work
Hi @all
i try to get my wireless adapter to work on Kali Linux (3.18.0-kali3-amd64). I read lots of post abot exactlly that topic, but none of that worked for me. I have a D-LINK WIRELESS ADAPTER DWA-171 i even read this post right here: http://ubuntuforums.org/showthread.php?t=2177333 this user seems to have the exactly the same problem with the same adapter like i have... but for me it didnt worked. Pls help me!!! my lsusb outpu is: Quote:
|
This may help: D-Link DWA-171 not detected (Linux Mint 16).
|
Hiluvr
ive tried that also... and now tried it again. it doesnt work. get following errors after "make" Quote:
Quote:
|
I'll have to look into this.
One thing I can already tell you: If the "make" step runs into an error, then there really is no point in trying "make install", since that needs the results from a successful make step. Could you perhaps post a link to the Kali disc image (or whichever format you downloaded) that you used to install the system? If the compilation and installation works on my Ubuntu or Slackware systems, and I can find the time, then I may want to try it under Kali, too. UPDATE: Just tried the "make" under Xubuntu 14.04. Works great. |
takes a while
Quote:
I downloaded the disc image (kali-linux-1.1.0.iso) from https://www.kali.org/downloads/ .... should be fine Any other suggestions? |
Quote:
I'm not sure if there will be an autoconfigurable version of the source files available anywhere, but I'll let you know if I find anything. UPDATE: Ignore this post. I was on the wrong track. |
1 Attachment(s)
Quote:
The code, as published, won’t compile on Linux kernel 3.18 (which happens to be the version that you are using). A patch is documented on the Kodi Community Forum. However, due to a few peculiarities about the source code (particularly, its use of <CR><LF> line endings, as is common under “TOOS—TOFR”, i.e., “That Other Operating System—The One From Redmond”), and about the way the patch was posted (missing spaces at the start of a few lines), a bit of extra work was required to make the patch usable. Just so you won’t have go through the hassle of figuring out how to get the patch in a working state, I attached a copy of the corrected version to this post. You should download the patch (i.e., file ‘cfg80211_rx_mgmt.txt’) into the directory that contains the driver source (i.e., the directory from where you run the ‘make’ command when you attempt to compile the driver). IMPORTANT: Verify that the file is exactly 1111 bytes in size (No, that’s not a typo: It really is a sequence of four ones). Otherwise, the patch must have gotten mangled again between my upload and your download. Make sure you are in the driver source directory (ready to retry the compile), and run the following command: Code:
patch --binary --strip=1 --verbose < cfg80211_rx_mgmt.txt Code:
Hmm... Looks like a unified diff to me... This time, it should succeed. |
i have tried what you said but i got an error message
"Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/include/ioctl_cfg80211.h b/include/ioctl_cfg80211.h |index 08357ac..8e85dc9 100644 |--- a/include/ioctl_cfg80211.h |+++ b/include/ioctl_cfg80211.h -------------------------- Patching file include/ioctl_cfg80211.h using Plan A... Hunk #1 FAILED at 109. 1 out of 1 hunk FAILED -- saving rejects to file include/ioctl_cfg80211.h.rej " i made sure of the file and i was in the right directory if you please could help me thanks |
Quote:
Also, the “include/ioctl_cfg80211.h” would be interesting. It looks like the patch doesn’t correspond to the version of the header file that you have on your system. I would have to see the header file in order to understand where it goes wrong. If possible, I would very much appreciate if you could attach the files, rather than pasting them into a message, to make sure that the spacing doesn’t get messed up. To attach them, you will likely have to add a “.txt” extension to their names. Perhaps copy them to a place where you can easily find them, then rename the copies (to add the extension), then attach them to your next message here (use the paper clip icon above the text field where you type your text). They should then be named “ioctl_cfg80211.h.rej.txt” and “include/ioctl_cfg80211.h.txt”. I will then have a look at them, and see what I can do to help you out. |
Quote:
Could you retry the “make” without patching? |
All times are GMT -5. The time now is 04:26 AM. |