Wifi USB Dongle not detected TP-Link TL-WN821N V6

[sunrat]

Did you see post 4 in this thread?

The question was more in hope or suggestion if MX could make it work out of the box ... without any compiling or hacking.

Sorry, no. Build the module from Github. It would take maybe 5 minutes.

[sagsaw]

Did you see post 4 in this thread?

The question was more in hope or suggestion if MX could make it work out of the box ... without any compiling or hacking.

Sorry, no. Build the module from Github. It would take maybe 5 minutes.

I am already doing the same but compiling the driver from source code provided by manufacturer but it works only till kernel 4.9

But wanna know why no? I thought over time more and more drivers are included with kernel standard by many distros.

[Stevo]

Why won't you use the github version when you know the version from TP-Link is outdated and won't work? You just keep repeating that it will only build on an older kernel. Yes, we get that by now.

[sagsaw]

Why won't you use the github version when you know the version from TP-Link is outdated and won't work? You just keep repeating that it will only build on an older kernel. Yes, we get that by now.

Dunno if its the same code base as the manufacturer.

And my second question is why its not standard bundled with kernel like many other drivers?

[JayM]

Why won't you use the github version when you know the version from TP-Link is outdated and won't work? You just keep repeating that it will only build on an older kernel. Yes, we get that by now.

Dunno if its the same code base as the manufacturer.

And my second question is why its not standard bundled with kernel like many other drivers?

Because if every single driver or module for every single piece of hardware in existence was included and enabled in the kernel, the kernel would be extremely bloated, huge and very slow.

You should have been around in the early days of Linux before kernels were modular. The kernel that came with distros was just generic enough to let you boot up but didn't perform well nor accommodate a huge variety of hardware, and the standard operating procedure was to recompile it for your particular hardware first thing, adding needed drivers and removing unneeded ones to optimize the kernel for your particular computer while still keeping it lean and fast. Nobody ever complained that distros' kernels weren't pre-optimized for their own particular computer hardware, they just rolled up their sleeves and started configuring and compiling.

[sagsaw]

Why won't you use the github version when you know the version from TP-Link is outdated and won't work? You just keep repeating that it will only build on an older kernel. Yes, we get that by now.

Dunno if its the same code base as the manufacturer.

And my second question is why its not standard bundled with kernel like many other drivers?

Because if every single driver or module for every single piece of hardware in existence was included and enabled in the kernel, the kernel would be extremely bloated, huge and very slow.

You should have been around in the early days of Linux before kernels were modular. The kernel that came with distros was just generic enough to let you boot up but didn't perform well nor accommodate a huge variety of hardware, and the standard operating procedure was to recompile it for your particular hardware first thing, adding needed drivers and removing unneeded ones to optimize the kernel for your particular computer while still keeping it lean and fast. Nobody ever complained that distros' kernels weren't pre-optimized for their own particular computer hardware, they just rolled up their sleeves and started configuring and compiling.

Been there done that ... Debian Potato onwards ... Kernel 2.0 I think it was ... where getting a serial mouse working on linux was an issue ... CorelLinux was a very very superb commercial attempt at linux ... I had it shipped from US via a relative. It was a superb distro and how lovely was the BOX pack with all the manuals and the monitor top Linux Penquin mascot soft toy frreee gift inside and al frree 3d linux game licence was it Civilization dunt remember ... I thought microsoft will die soon because it also had staroffice licenced.

Only that over the years ... ever since I laid my hands on the first ever live cd I have experienced KNOPPIX ... well what to say ... OLD HABBITS DIED SOFT.

Hence the demand.

And if this driver works for many different dongles then It make a case for inclusion.

[Stevo]

Why won't you use the github version when you know the version from TP-Link is outdated and won't work? You just keep repeating that it will only build on an older kernel. Yes, we get that by now.

Dunno if its the same code base as the manufacturer.

And my second question is why its not standard bundled with kernel like many other drivers?

It's modified from Realtek's original code in order to build on newer kernels and fix other bugs, which you can see if you ever went to that Github repo.

As for the second question, how should we know why and what the kernel developers decide to support in the kernel?

It looks like you may also have to blacklist the standard rtl8xxxu driver by editing /etc/modprobe.d/blacklist.conf and adding the line

Code: Select all

blacklist rtl8xxxu

[sagsaw]

Why won't you use the github version when you know the version from TP-Link is outdated and won't work? You just keep repeating that it will only build on an older kernel. Yes, we get that by now.

Dunno if its the same code base as the manufacturer.

And my second question is why its not standard bundled with kernel like many other drivers?

It's modified from Realtek's original code in order to build on newer kernels and fix other bugs, which you can see if you ever went to that Github repo.

As for the second question, how should we know why and what the kernel developers decide to support in the kernel?

It looks like you may also have to blacklist the standard rtl8xxxu driver by editing /etc/modprobe.d/blacklist.conf and adding the line

Code: Select all

blacklist rtl8xxxu

Finally, is MX or for that matter anyone else or a DISTRO not allowed to add a driver with their distro kernel ?

[sunrat]

Finally, is MX or for that matter anyone else or a DISTRO not allowed to add a driver with their distro kernel ?

Kernels are open source, you can do what you like as long as you keep the same licence for the modified one. That said, Realtek have an unbelievably huge number of different devices and drivers it would be unrealistic to add them all to default distro kernels.
Have you tried building the driver from Github yet? Is your wifi working?

[sagsaw]

Finally, is MX or for that matter anyone else or a DISTRO not allowed to add a driver with their distro kernel ?

Kernels are open source, you can do what you like as long as you keep the same licence for the modified one. That said, Realtek have an unbelievably huge number of different devices and drivers it would be unrealistic to add them all to default distro kernels.
Have you tried building the driver from Github yet? Is your wifi working?

Yes built the driver from GITHUB got it to work on live usb ... yes compiled it on live ... but speed is not good ... 300n dongle but does not work at good speed in fact the connection information does not show anything ...
am attaching screen shot ...

And you can see in the second screen shot the speed using openspeedtest website indicating 38mbps which actually should be 75mbps at least as seen on my mobile phone with full HD streaming on my TV active simultaneously else the speed is 100mbps.