Próbuję zainstalować sterownik do karty wifi USB archer T4U ver. 3.
komenda dkms stautus - nic nie zwraca. Co jest pewnie wynikiem błędu w kompilacji sterownika.
Ktoś może ma jakiś pomysł jak rozwiązać ten problem?
Building module:
Cleaning build area...
kernelver=6.17.0-20-generic ./dkms-make.sh............(bad exit status: 2)
ERROR (dkms apport): binary package for rtl88x2bu: 5.13.1 not found
Error! Bad return status for module build on kernel: 6.17.0-20-generic (x86_64)
Consult /var/lib/dkms/rtl88x2bu/5.13.1/build/make.log for more information.
Command exited with non-zero status 10
Compile time: 92.49 seconds
An error occurred. dkms build error: 10
Please report this error.
Please copy all screen output and paste it into the problem report.
Run the following before reattempting installation.
$ sudo ./remove-driver.sh
Ostatnio zmieniony 23 kwie 2026, 20:21 przez gd_muniek, łącznie zmieniany 1 raz.
Dostaję taki komunikat. na moje oko nie różni się on zbyt wiele od poprzedniej próby instalacji tego sterownika.
Używałem też skryptu. sudo ./fix_driver.sh - ale zwraca komunikat not found.
Sign command: /usr/bin/kmodsign
Binary update-secureboot-policy not found, modules won't be signed
Building module:
Cleaning build area...
kernelver=6.17.0-22-generic ./dkms-make.sh...........(bad exit status: 2)
ERROR (dkms apport): binary package for rtl88x2bu: 5.13.1 not found
Error! Bad return status for module build on kernel: 6.17.0-22-generic (x86_64)
Consult /var/lib/dkms/rtl88x2bu/5.13.1/build/make.log for more information.
Command exited with non-zero status 10
Compile time: 91.61 seconds
An error occurred. dkms build error: 10
Please report this error.
Please copy all screen output and paste it into the problem report.
Run the following before reattempting installation.
$ sudo ./remove-driver.sh
[+] Done. Please reboot the system.
Binary update-secureboot-policy not found, modules won't be signed
To oznacza tylko, że system nie znalazł narzędzia do podpisywania modułów Secure Boot.
Sterownik mógłby się zbudować mimo tego, ale nie załaduje się przy włączonym Secure Boot.
Pewnie lepiej to wyłączyć w BIOS
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 2357:0115 TP-Link Archer T4U ver.3
Bus 001 Device 004: ID 1ea7:0066 SHARKOON Technologies GmbH [Mediatrack Edge Mini Keyboard]
Bus 001 Device 005: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 003: ID 1d57:ad17 Xenta ZELOTES GAME MOUSE
CC [M] core/rtw_vht.o
CC [M] core/rtw_pwrctrl.o
CC [M] core/rtw_rf.o
CC [M] core/rtw_chplan.o
CC [M] core/monitor/rtw_radiotap.o
CC [M] core/rtw_recv.o
CC [M] core/rtw_sta_mgt.o
CC [M] core/rtw_ap.o
CC [M] core/wds/rtw_wds.o
CC [M] core/mesh/rtw_mesh.o
CC [M] core/mesh/rtw_mesh_pathtbl.o
CC [M] core/mesh/rtw_mesh_hwmp.o
CC [M] core/rtw_xmit.o
CC [M] core/rtw_p2p.o
CC [M] core/rtw_rson.o
CC [M] core/rtw_tdls.o
CC [M] core/rtw_br_ext.o
CC [M] core/rtw_iol.o
CC [M] core/rtw_sreset.o
CC [M] core/rtw_btcoex_wifionly.o
CC [M] core/rtw_btcoex.o
CC [M] core/rtw_beamforming.o
CC [M] core/rtw_odm.o
CC [M] core/rtw_rm.o
CC [M] core/rtw_rm_fsm.o
CC [M] core/rtw_ft.o
CC [M] core/rtw_wnm.o
CC [M] core/rtw_mbo.o
CC [M] core/rtw_rm_util.o
CC [M] core/efuse/rtw_efuse.o
CC [M] core/rtw_roch.o
CC [M] core/crypto/aes-internal.o
CC [M] core/crypto/aes-internal-enc.o
CC [M] core/crypto/aes-gcm.o
CC [M] core/crypto/aes-ccm.o
CC [M] core/crypto/aes-omac1.o
CC [M] core/crypto/ccmp.o
CC [M] core/crypto/gcmp.o
CC [M] core/crypto/aes-siv.o
CC [M] core/crypto/aes-ctr.o
CC [M] core/crypto/sha256-internal.o
CC [M] core/crypto/sha256.o
CC [M] core/crypto/sha256-prf.o
CC [M] core/crypto/rtw_crypto_wrap.o
CC [M] core/rtw_swcrypto.o
CC [M] os_dep/osdep_service.o
CC [M] os_dep/linux/os_intfs.o
CC [M] os_dep/linux/usb_intf.o
CC [M] os_dep/linux/usb_ops_linux.o
CC [M] os_dep/linux/ioctl_linux.o
CC [M] os_dep/linux/xmit_linux.o
CC [M] os_dep/linux/mlme_linux.o
CC [M] os_dep/linux/recv_linux.o
CC [M] os_dep/linux/ioctl_cfg80211.o
CC [M] os_dep/linux/rtw_cfgvendor.o
CC [M] os_dep/linux/wifi_regd.o
os_dep/linux/ioctl_cfg80211.c:10474:29: error: initialization of ‘int (*)(struct wiphy *, int, u32)’ {aka ‘int (*)(struct wiphy *, int, unsigned int)’} from incompatible pointer type ‘int (*)(struct wiphy *, u32)’ {aka ‘int (*)(struct wiphy *, unsigned int)’} [-Werror=incompatible-pointer-types]
10474 | .set_wiphy_params = cfg80211_rtw_set_wiphy_params,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
os_dep/linux/ioctl_cfg80211.c:10474:29: note: (near initialization for ‘rtw_cfg80211_ops.set_wiphy_params’)
os_dep/linux/ioctl_cfg80211.c:10480:25: error: initialization of ‘int (*)(struct wiphy *, struct wireless_dev *, int, enum nl80211_tx_power_setting, int)’ from incompatible pointer type ‘int (*)(struct wiphy *, struct wireless_dev *, enum nl80211_tx_power_setting, int)’ [-Werror=incompatible-pointer-types]
10480 | .set_tx_power = cfg80211_rtw_set_txpower,
| ^~~~~~~~~~~~~~~~~~~~~~~~
os_dep/linux/ioctl_cfg80211.c:10480:25: note: (near initialization for ‘rtw_cfg80211_ops.set_tx_power’)
os_dep/linux/ioctl_cfg80211.c:10481:25: error: initialization of ‘int (*)(struct wiphy *, struct wireless_dev *, int, unsigned int, int *)’ from incompatible pointer type ‘int (*)(struct wiphy *, struct wireless_dev *, unsigned int, int *)’ [-Werror=incompatible-pointer-types]
10481 | .get_tx_power = cfg80211_rtw_get_txpower,
| ^~~~~~~~~~~~~~~~~~~~~~~~
os_dep/linux/ioctl_cfg80211.c:10481:25: note: (near initialization for ‘rtw_cfg80211_ops.get_tx_power’)
CC [M] os_dep/linux/rtw_android.o
CC [M] os_dep/linux/rtw_proc.o
CC [M] os_dep/linux/nlrtw.o
cc1: some warnings being treated as errors
make[4]: *** [/usr/src/linux-headers-6.17.0-22-generic/scripts/Makefile.build:287: os_dep/linux/ioctl_cfg80211.o] Błąd 1
make[4]: *** Oczekiwanie na niezakończone zadania....
make[3]: *** [/usr/src/linux-headers-6.17.0-22-generic/Makefile:2016: .] Błąd 2
make[2]: *** [/usr/src/linux-headers-6.17.0-22-generic/Makefile:248: __sub-make] Błąd 2
make[2]: Opuszczenie katalogu '/var/lib/dkms/rtl88x2bu/5.13.1/build'
make[1]: *** [Makefile:248: __sub-make] Błąd 2
make[1]: Opuszczenie katalogu '/usr/src/linux-headers-6.17.0-22-generic'
make: *** [Makefile:2533: modules] Błąd 2
git clone https://github.com/morrownr/88x2bu-20210702.git
cd 88x2bu-20210702
sudo ./install-driver.sh
reboot
Ten fork jest regularnie łatany pod nowe kernele.
Jeśli dalej nie zadziała
to może starszy kernel
Na Ubuntu/Mint uruchomić z GRUB np. kernel:
6.8
6.5
6.2
Wtedy stary driver 5.13.1 często działa
Ostatnio zmieniony 20 kwie 2026, 22:04 przez kobrawerde, łącznie zmieniany 1 raz.
