How to Make the TP-Link Archer TX50Uh AX3000 USB WiFi Adapter Work on Ubuntu?
If you recently bought the TP-Link Archer TX50Uh AX3000 Wireless USB Adapter from Amazon India and discovered it doesn’t work out of the box on Ubuntu Linux, you’re not alone.
Here’s how I got it working smoothly on my Ubuntu system. ( Tested on the Newest Ubuntu 25.04 -when writing )
Amazon Product package: Tp-Link Archer Tx50Uh Ax3000 High Gain Wireless USB Adapter | 3000 Mbps Dual Band WiFi 6 | High Gain Antennas and Beamforming | USB 3.0 | Wpa3 | Ofdma and Mu-Mimo – Black
This device in lsusb shows up as ID 35bc:0101 Realtek 802.11ax WLAN Adapter.
It’s quite easy to make it work on Ubuntu. Here are the steps.
Thanks to morrownr for maintaining a reliable driver repo for this chipset.
git clone https://github.com/morrownr/rtl8852cu-20240510
cd rtl8852cu-20240510
3. Build and Install the Driver
make
sudo make install
4. Configure the Module
During installation, a config file will open in nano. Find this line:
options 8852cu rtw_switch_usb_mode=0
Change it to:
options 8852cu rtw_switch_usb_mode=1
Save and exit (Ctrl+O, Enter, Ctrl+X).
To edit this config later, you can find it at:
sudo nano /etc/modprobe.d/8852cu.conf or use Vi or gedit
5. Reboot and Connect
Now reboot your system:
sudo reboot
After rebooting, your TP-Link WiFi adapter should be detected. The LED should start blinking, and you should see WiFi networks available in your settings.
When working with external monitors on Ubuntu, adjusting the brightness of the external monitor connected to your laptop can often be a challenge, especially when traditional methods fail or when you’re working with specific hardware like NVIDIA GPUs or USB-C to HDMI adapters. Many users struggle with issues such as brightness settings not being adjustable or xrandr and ddcutil commands failing, even when everything seems to be set up correctly.
After installing the latest Ubuntu 25.04 Plucky Puffin, I found myself in a similar situation where my external monitor’s brightness was already at its lowest, yet it was still too bright for many users, leading to frustration. In this guide, we will explore multiple ways to adjust the brightness of your external monitor on just-launched Ubuntu 25.04 and add a special focus on the Xorg solution—an option that could save the day when everything else fails.
( Skip to Method 3 if you want a simple solution – Also check that Bonus Github Script )
Method 1: Using xrandr (Basic Brightness Control)
One of the most common methods to adjust brightness on Ubuntu is through xrandr, which allows users to manipulate various display properties directly from the terminal. For external monitors, you can try the following:
xrandr --output HDMI-A-0 --brightness 0.7
However, xrandr’s--brightness option has limited effectiveness, especially for certain monitors and drivers. It doesn’t directly change the hardware brightness but simulates brightness by adjusting the display’s gamma, which may not always work as expected.
It also usually doesn’t work these days on Ubuntu Wayland versions.
Method 2: Using ddcutil (DDC/CI Communication)
If you need to adjust hardware brightness (as in the actual brightness level controlled by the monitor), ddcutil is a great tool, provided your monitor supports DDC/CI (Display Data Channel/Command Interface). You can install it using the following command:
sudo apt install ddcutil
Once installed, you can attempt to adjust the brightness using ddcutil:
ddcutil setvcp 0x10 50
Unfortunately, this method doesn’t always work due to compatibility issues between the software, the monitor, and the connection type (such as USB-C to HDMI). You might encounter errors like:
DDCRC_READ_ALL_ZERO
Method 3: Switching to Xorg (A Potential Solution)
If traditional methods like xrandr and ddcutil fail, switching to Xorg could be a game-changer. By default, many modern Ubuntu systems use Wayland as the display server. However, Xorg might offer better compatibility with certain monitors, especially when it comes to adjusting external monitor brightness.
Why Switch to Xorg?
Better compatibility with legacy hardware and drivers.
Improved handling of external monitors and DDC/CI.
If your external monitor is not behaving as expected under Wayland, switching to Xorg can help address issues related to brightness control.
How to Switch to Xorg ( Recommended APproach )
Switching to Xorg on Ubuntu is simple. Follow these steps:
Log Out from your current session.
On the login screen, click on the gear icon (⚙️) down in the bottom right corner and select Ubuntu on Xorg.
Log back in.
Alternatively, if you want to make Xorg the default display server:
Edit the GDM configuration file: sudo nano /etc/gdm3/custom.conf
Uncomment (remove the #) the line that says WaylandEnable=false.
Save and exit the file, then reboot your system: sudo reboot
After switching to Xorg, you should see improved compatibility with xrandr, ddcutil, and other display tools, particularly for external monitors.
What Worked After Switching to Xorg
After switching to Xorg, I found that the xrandr command worked properly, but I had to first determine the correct monitor identifier. I used the following command to list all connected monitors:
xrandr | grep connected
This showed me the monitor I needed to target. Once I had the correct output identifier, I was able to adjust the brightness successfully:
xrandr --output HDMI-A-0 --brightness 0.7
Additionally, I found that xgamma could be used to adjust the gamma of the display. This is useful for fine-tuning the color and brightness in a different way, though it’s more of a gamma correction tool rather than a direct brightness control. To adjust the gamma, you can use the following command:
xgamma -display :0 -gamma 0.5
This command adjusts the gamma to 0.5, effectively darkening the screen (or brightening, depending on the value). While it doesn’t directly control the monitor’s brightness, it’s a good option for tweaking the overall appearance.
Persisting xrandr and xgamma Settings Across Reboots
Unfortunately, both xrandr and xgamma settings are temporary and will not survive a reboot or logout by default. When you log out or reboot, the display settings are reset, and you’ll need to reapply them after logging in again.
Workaround for Persistence:
To make these settings persist across reboots or logouts, you can create a startup script to automatically apply the settings when you log in. Here’s how you can do it:
Open a terminal and create a new script file: vi ~/set_display_brightness.sh
Add the xrandr and/or xgamma commands to this script. For example: #!/bin/bash xrandr --output HDMI-A-0 --brightness 0.7 You have to find your monitor name by running the command xrandr | grep connected ( For me, it’s HDMI-A-0 ) – WARNING – Don’t use 0 as the brightness value – your screen will go Black.
Save the file and close the editor.
Make the script executable: chmod +x ~/set_display_brightness.sh
Set the Script to Run on Startup
You can configure Ubuntu to run this script automatically when you log in:
Press Alt + F2, type gnome-session-properties, and press Enter to open the Startup Applications Preferences.
In the Startup Applications Preferences, click Add to add a new startup program.
In the Name field, enter something descriptive, such as Set Display Brightness.
In the Command field, enter the full path to the script, like: /home/yourusername/set_display_brightness.sh
Click Add, then Close.
Now, each time you log in, the script will run automatically and set your brightness settings to your preferences.
BONUS: A Bash Script to Create a System Tray Icon to Adjust Brightness ( for Ubuntu on Xorg only ) – Github link.
If you’ve experienced an unresponsive top or bottom section on your Android phone (where you access the notification drawer), likely caused by dead pixels or a broken screen, you’re not alone. I recently encountered this issue on my Google Pixel 7 Pro. To avoid costly display replacements, here’s a workaround I discovered.
The Issue: Dead Pixels on the Notification Drawer Area
My Google Pixel 7 Pro suffered a flat fall onto concrete, resulting in an unresponsive top section of the screen. This area, crucial for accessing the notification drawer, quick settings, and other essential features, became inoperable. While the issue likely stemmed from dead pixels, necessitating a hardware repair, I sought a swift, temporary solution.
Why the wm overscan Command No Longer Works
In earlier versions of Android, the wm overscan ADB command was a go-to solution for adjusting screen margins. This command allowed users to shift the functional screen area to bypass unresponsive regions. Unfortunately, this command has been deprecated in newer Android versions, leaving users searching for alternatives.
The Solution: Using the wm size ADB Command
After some research and experimentation, I discovered that the wm size command in ADB (Android Debug Bridge) could be used to adjust the display size, effectively bypassing the dead pixels at the top of the screen. Here’s how you can apply this workaround:
Enable Developer Options on your phone by going to Settings > About Phone and tapping “Build Number” seven times.
Enable USB Debugging in Developer Options.
Connect Your Phone:
Use a USB cable to connect your phone to your computer.
Open a command prompt or terminal window and verify the connection by running: adb devices Your device should appear in the list.
Run the wm size Command:
Use the following command to adjust the display size: adb shell wm size 1080x2000
Replace 1080x2000 with dimensions that work for your screen. These values represent the new width and height of the usable display area in pixels.
Test the Changes:
Check if the notification drawer is now accessible. Adjust the values as needed to find the optimal configuration.
Considerations
This solution works as a temporary fix. For a permanent resolution, you may need to get the screen repaired or replaced. ( I don’t plan to as my Google Pixel 7 Pro screen replacement cost is almost equal to buying a new Phone these days )
The adjusted display size may cause minor scaling issues in certain apps. Experiment with different resolutions to find the best balance.
Conclusion
While dead pixels can be a frustrating problem, the wm size ADB command offers a quick and effective workaround for users running newer Android versions. If you’re facing a similar issue on your Google Pixel 7 Pro or another Android device, give this method a try. It’s a handy solution to keep your phone functional without immediate hardware repairs.
Have you faced a similar problem? Let me know in the comments if this solution worked for you or if you have other tips to share!
![[ Solved ] Tp-Link Archer Tx50Uh Ax3000 WiFi not working on Ubuntu Linux](https://techstoriesindia.com/wp-content/uploads/2025/04/feature-image_2025-04-19_06-07-08.webp "[ Solved ] Tp-Link Archer Tx50Uh Ax3000 WiFi not working on Ubuntu Linux 1")
