From 890503ad08d2219a869cc83d728374ec41672875 Mon Sep 17 00:00:00 2001 From: Slavic Dragovtev Date: Tue, 10 Dec 2024 15:20:05 +0200 Subject: [PATCH 1/3] Update README.md Fixes grammar. --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 17f0599..4c56f07 100644 --- a/README.md +++ b/README.md @@ -115,7 +115,7 @@ And more. ## Manual installation ### Clean -* Make sure you cleaned old build files before builds new one +* Make sure you clean old build files before building new ones ``` make clean ``` @@ -142,7 +142,7 @@ sudo make uninstall ## Using DKMS (Dynamic Kernel Module Support) -Allows smooth integration with kernel updates +Allows smooth integration with kernel updates. ### Initial DKMS installation ``` @@ -161,16 +161,16 @@ dkms install rtl88x2bu/git --force ``` # USB 3.0 Support -You can try use `modprobe 88x2bu rtw_switch_usb_mode=1` to force the adapter run under USB 3.0. But if your adapter/port/motherboard not support it, the driver will be in restart loop. Remove the parameter and reload the driver to restore. Alternatively, `modprobe 88x2bu rtw_switch_usb_mode=2` let\'s it run as USB 2 device. +You can try using `modprobe 88x2bu rtw_switch_usb_mode=1` to force the adapter to run under USB 3.0. But if your adapter/port/motherboard does not support it, the driver will be stuck in a restart loop. Remove the parameter and reload the driver to restore. Alternatively, `modprobe 88x2bu rtw_switch_usb_mode=2` runs it as a USB 2 device. -Notice: If you had already loaded the moduel, use `modprobe -r 88x2bu` to unload it first. +Notice: If you had already loaded the module, use `modprobe -r 88x2bu` to unload it first. If you want to force a given mode permanently (even when switching the adapter across devices), create the file `/etc/modprobe.d/99-RTL88x2BU.conf` with the following content: `options 88x2bu rtw_switch_usb_mode=1` # Debug -Set debug log use `echo 5 > /proc/net/rtl88x2bu/log_level` or `modprobe 88x2bu rtw_drv_log_level=5` +To set debug log use `echo 5 > /proc/net/rtl88x2bu/log_level` or `modprobe 88x2bu rtw_drv_log_level=5` # Distribution * Archlinux AUR https://aur.archlinux.org/packages/rtl88x2bu-dkms-git/ From daf03e4717389aa54a1417e133447f261717d957 Mon Sep 17 00:00:00 2001 From: Slavic Dragovtev Date: Mon, 26 May 2025 13:55:25 +0300 Subject: [PATCH 2/3] Updates readme grammar. --- README.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 6e5f5ec..5e12c0a 100644 --- a/README.md +++ b/README.md @@ -2,27 +2,27 @@ **Current Driver Version**: 5.13.1-30 **Support Kernel**: 2.6.24 ~ 6.14 (with unofficial patches) -Linux in-tree rtw8822bu driver is working in process, check [this](https://lore.kernel.org/lkml/20220518082318.3898514-1-s.hauer@pengutronix.de/) patchset. +Linux in-tree rtw8822bu driver is a work in progress. Check [this](https://lore.kernel.org/lkml/20220518082318.3898514-1-s.hauer@pengutronix.de/) patchset. -Official release note please check ReleaseNotes.pdf +For official release note please check ReleaseNotes.pdf. -**Note:** if you believe your device is **RTL8812BU** or **RTL8822BU** but after loaded the module no NIC shows up, the device ID maybe not in the driver whitelist. In this case please submit a new issue with `lsusb` result, and your device name, brand, website, etc. +**Note:** if you believe your device is **RTL8812BU** or **RTL8822BU** but after loading the module no NIC shows up, the device ID maybe not be in the driver whitelist. In this case, please submit a new issue with `lsusb` result, and your device name, brand, website, etc. ## Linux 5.18+ and RTW88 Driver Starting from Linux 5.18, some distributions have added experimental RTW88 USB support (include RTW88x2BU support). It is not yet stable but if it works well on your system, then you no longer need this driver. -But if it doesn't work or is unstable, you need to manually blacklist it because it has a higher loading priority than this external drivers. +If it doesn't, then you need to manually blacklist it because it has a higher loading priority than this external drivers. -Check the currently loaded module using `lsmod`. If you see `rtw88_core`, `rtw88_usb`, or any name beginning with `rtw88_` then you are using the RTW88 driver. +Check the currently loaded modules using `lsmod`. If you see `rtw88_core`, `rtw88_usb`, or any name beginning with `rtw88_` then you are using the RTW88 driver. If you see `88x2bu` then you are using this RTW88x2BU driver. -To blacklist RTW88 8822bu USB driver, run the following command: +To blacklist RTW88 8822bu USB driver run: ``` echo "blacklist rtw88_8822bu" > /etc/modprobe.d/rtw8822bu.conf ``` -And reboot your system. +...and reboot your system. ## Supported Devices
From 4e8d492b1e8c333d9001fe5e3bbff628e62fed6c Mon Sep 17 00:00:00 2001 From: Slavic Dragovtev Date: Mon, 26 May 2025 13:58:41 +0300 Subject: [PATCH 3/3] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 5e12c0a..9b76b05 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ Linux in-tree rtw8822bu driver is a work in progress. Check [this](https://lore.kernel.org/lkml/20220518082318.3898514-1-s.hauer@pengutronix.de/) patchset. -For official release note please check ReleaseNotes.pdf. +For official release notes please check ReleaseNotes.pdf. **Note:** if you believe your device is **RTL8812BU** or **RTL8822BU** but after loading the module no NIC shows up, the device ID maybe not be in the driver whitelist. In this case, please submit a new issue with `lsusb` result, and your device name, brand, website, etc.