MX Linux Forum

Stevo wrote: Sat Mar 23, 2019 3:10 pm If it's the Realtek 8192eu, this repo has updated drivers source that will build up to the 5.1 kernel: https://github.com/Mange/rtl8192eu-linux-driver Please read the full README to see how to blacklist the existing kernel driver.

lsusb

Stevo wrote: Sat Mar 23, 2019 3:02 pm First, run

Code: Select all

sudo update-usbids

to make sure your USB ID database is fully updated (requires Net connection).

Then give us the result of

Code: Select all

inxi -Nxxz

so our strong Google-Fu has something to work with.

Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
           v: kernel port: e800 bus ID: 05:00.0 chip ID: 10ec:8168

sunrat wrote: Sat Mar 23, 2019 6:56 pm

Stevo wrote: Sat Mar 23, 2019 3:10 pm If it's the Realtek 8192eu, this repo has updated drivers source that will build up to the 5.1 kernel: https://github.com/Mange/rtl8192eu-linux-driver Please read the full README to see how to blacklist the existing kernel driver.

The install instructions with that driver are for Ubuntu. You will need to install the headers for your actual kernel, not linux-headers-generic.
Is there a metapackage for MX kernels @Stevo?
Also I'm not sure if the TP-Link TL-WN821N V6 is rtl8192eu, I know the V5 is. It would help if we could see the device ID from the command

Code: Select all

lsusb

Bus 005 Device 006: ID 2717:ff88 Xiaomi Inc. Mi/Redmi series (RNDIS + ADB)
Bus 005 Device 004: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2
Bus 005 Device 002: ID 2357:0107 TP-Link TL-WN821N Version 5 RTL8192EU
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Stevo wrote: Wed Apr 03, 2019 8:36 pm Did you see post 4 in this thread?

sagsaw wrote: Thu Apr 04, 2019 3:04 am

Stevo wrote: Wed Apr 03, 2019 8:36 pm 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.

sunrat wrote: Thu Apr 04, 2019 7:10 am

sagsaw wrote: Thu Apr 04, 2019 3:04 am

Stevo wrote: Wed Apr 03, 2019 8:36 pm 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.

Stevo wrote: Thu Apr 04, 2019 5:08 pm 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 wrote: Fri Apr 05, 2019 3:07 am

Stevo wrote: Thu Apr 04, 2019 5:08 pm 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 wrote: Fri Apr 05, 2019 3:44 am

sagsaw wrote: Fri Apr 05, 2019 3:07 am

Stevo wrote: Thu Apr 04, 2019 5:08 pm 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 wrote: Fri Apr 05, 2019 3:07 am

Stevo wrote: Thu Apr 04, 2019 5:08 pm 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?

blacklist rtl8xxxu

Stevo wrote: Fri Apr 05, 2019 5:25 pm

sagsaw wrote: Fri Apr 05, 2019 3:07 am

Stevo wrote: Thu Apr 04, 2019 5:08 pm 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 wrote: Sat Apr 06, 2019 1:44 amFinally, is MX or for that matter anyone else or a DISTRO not allowed to add a driver with their distro kernel ?

sunrat wrote: Sat Apr 06, 2019 2:45 am

sagsaw wrote: Sat Apr 06, 2019 1:44 amFinally, 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?

Stevo wrote: Fri Apr 05, 2019 5:25 pm

sagsaw wrote: Fri Apr 05, 2019 3:07 am

Stevo wrote: Thu Apr 04, 2019 5:08 pm 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

Eadwine Rose wrote: Sat Mar 13, 2021 6:16 am So.. your advice on fixing this is using something other than MX Linux, and that is why you dug up an old thread. How is this helpful exactly?