F5F Stay Refreshed Software Operating Systems WiFi dongle for Linux setup

WiFi dongle for Linux setup

WiFi dongle for Linux setup

B
Blazer444
Member
146
01-06-2016, 11:19 AM
#1
You've made the switch to Linux and are using a Wi-Fi dongle that handles data quickly but struggles with latency. You're also trying a Windows adapter and have searched extensively without success, even checking GitHub for drivers. The correct driver you find often results in the system defaulting to Linux, which is convenient. If you need further assistance, please let me know.
B
Blazer444
01-06-2016, 11:19 AM #1

You've made the switch to Linux and are using a Wi-Fi dongle that handles data quickly but struggles with latency. You're also trying a Windows adapter and have searched extensively without success, even checking GitHub for drivers. The correct driver you find often results in the system defaulting to Linux, which is convenient. If you need further assistance, please let me know.

C
Coolpius
Member
142
01-07-2016, 05:54 PM
#2
It looks like this will likely be my only contribution since I’m offline. Could you clarify the operating system and kernel version you’re using? Also, have you verified that build-essential and the kernel headers are installed for your specific release? As mentioned, if no built-in drivers exist, it might be better to use the GitHub versions rather than manufacturer ones, which tend to be outdated. Referring to the blog post you shared, it seems you may need to edit a few header files—this feels like an older approach compared to recent driver updates on most distros. Also, if it functions now, double-check that latency issues are truly driver-related and not due to other factors. A note: checking dmesg can reveal more details about your system and any problems. Good luck!
C
Coolpius
01-07-2016, 05:54 PM #2

It looks like this will likely be my only contribution since I’m offline. Could you clarify the operating system and kernel version you’re using? Also, have you verified that build-essential and the kernel headers are installed for your specific release? As mentioned, if no built-in drivers exist, it might be better to use the GitHub versions rather than manufacturer ones, which tend to be outdated. Referring to the blog post you shared, it seems you may need to edit a few header files—this feels like an older approach compared to recent driver updates on most distros. Also, if it functions now, double-check that latency issues are truly driver-related and not due to other factors. A note: checking dmesg can reveal more details about your system and any problems. Good luck!

A
Azastias
Member
223
01-08-2016, 01:32 AM
#3
I believe you've already reviewed this and followed the related guidelines.
A
Azastias
01-08-2016, 01:32 AM #3

I believe you've already reviewed this and followed the related guidelines.

C
Chile_PvP
Junior Member
43
01-08-2016, 03:24 AM
#4
Thank you for your prompt response. I switched to the alternative option, which resolved the issue. The previous one led to a kernel panic, so I removed it and followed the link you provided.
C
Chile_PvP
01-08-2016, 03:24 AM #4

Thank you for your prompt response. I switched to the alternative option, which resolved the issue. The previous one led to a kernel panic, so I removed it and followed the link you provided.

S
SwagZor
Junior Member
42
01-08-2016, 08:33 AM
#5
Another issue on Linux is happening; it will attempt to locate another GitHub site to try. Appreciate the link!
S
SwagZor
01-08-2016, 08:33 AM #5

Another issue on Linux is happening; it will attempt to locate another GitHub site to try. Appreciate the link!

C
CheezBurgerzz
Member
202
01-08-2016, 02:34 PM
#6
Regardless of what I attempt, it still displays that error. Let me explain what it means and how to resolve it.
C
CheezBurgerzz
01-08-2016, 02:34 PM #6

Regardless of what I attempt, it still displays that error. Let me explain what it means and how to resolve it.

D
DJpurplekyle
Junior Member
21
01-09-2016, 11:55 PM
#7
From what I gathered from your previous screen, it seems someone likely made a significant error in the code I intended to test. On an Ubuntu 16.04.3 server with the 4.4 kernel, I successfully built the project in roughly five minutes on a single core using standard commands similar to those listed online. The output of `lsb_release -a uname -a` suggests a different system configuration compared to yours.
D
DJpurplekyle
01-09-2016, 11:55 PM #7

From what I gathered from your previous screen, it seems someone likely made a significant error in the code I intended to test. On an Ubuntu 16.04.3 server with the 4.4 kernel, I successfully built the project in roughly five minutes on a single core using standard commands similar to those listed online. The output of `lsb_release -a uname -a` suggests a different system configuration compared to yours.

W
WizGhalika
Junior Member
20
01-10-2016, 07:52 AM
#8
xuxu@xuxu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial
W
WizGhalika
01-10-2016, 07:52 AM #8

xuxu@xuxu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial

E
EdoubleO
Member
238
01-11-2016, 04:01 AM
#9
@code_glitch also should i run the commands to see if it gives the same error ( I made another thread someone suggested ndiswrapper and it messed up my install this is a brand new one)
E
EdoubleO
01-11-2016, 04:01 AM #9

@code_glitch also should i run the commands to see if it gives the same error ( I made another thread someone suggested ndiswrapper and it messed up my install this is a brand new one)

L
LionTurtle2
Junior Member
44
01-17-2016, 06:57 AM
#10
The ndiswrapper setup is quite outdated and likely unnecessary for most systems today. Since your environment is very similar, I recommend testing the build commands to check for a .ko file or any unusual errors.
L
LionTurtle2
01-17-2016, 06:57 AM #10

The ndiswrapper setup is quite outdated and likely unnecessary for most systems today. Since your environment is very similar, I recommend testing the build commands to check for a .ko file or any unusual errors.