Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
09-26-2018, 04:37 PM
|
#16
|
Member
Registered: Aug 2013
Distribution: Debian, Ubuntu
Posts: 271
Original Poster
Rep: 
|
No joy with either command.
Quote:
Originally Posted by ferrari
Yes, but 'usb-devices' will show if it is bound to the device. Check if it is loaded with
and perhaps check that the particular chipset (product ID 0115) is supported
Code:
modinfo 8812au |grep 0115
If not, that may be the issue here perhaps.
|
|
|
|
09-26-2018, 06:24 PM
|
#17
|
LQ Guru
Registered: Dec 2011
Distribution: Slackware, Debian 12, Devuan & MX Linux
Posts: 9,528
|
ferrari:
Is it possible that the wrong module is loading first thus causing the device not to work?
|
|
|
09-26-2018, 06:29 PM
|
#18
|
LQ Guru
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 6,016
|
Run it unfiltered like this
and report back.
It's looking like the module you built does NOT explicitly support this chipset. That's not to say that it's not compatible, but the source code doesn't include this particular chipset.
Quote:
ferrari:
Is it possible that the wrong module is loading first thus causing the device not to work?
__________________
|
More like no driver matches this particular hardware.
|
|
|
09-26-2018, 06:33 PM
|
#19
|
LQ Guru
Registered: Dec 2011
Distribution: Slackware, Debian 12, Devuan & MX Linux
Posts: 9,528
|
Quote:
More like no driver matches this particular hardware.
|
Maybe OP could order one of those usb wifi adapters that work with Linux pretty much out of the box.
https://www.wirelesshack.org/top-lin...-adapters.html
|
|
|
09-26-2018, 06:37 PM
|
#20
|
LQ Guru
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 6,016
|
That is a pragmatic option IMHO. 
|
|
|
09-26-2018, 06:41 PM
|
#21
|
LQ Guru
Registered: Dec 2011
Distribution: Slackware, Debian 12, Devuan & MX Linux
Posts: 9,528
|
Quote:
Originally Posted by ferrari
That is a pragmatic option IMHO. 
|
Thanks- 
|
|
|
09-26-2018, 07:48 PM
|
#22
|
Member
Registered: Aug 2013
Distribution: Debian, Ubuntu
Posts: 271
Original Poster
Rep: 
|
Here it is:
Quote:
root@harold:~# modinfo 8812au
filename: /lib/modules/4.9.0-7-amd64/kernel/drivers/net/wireless/8812au.ko
version: v5.2.20_25672.20171213
author: Realtek Semiconductor Corp.
description: Realtek Wireless Lan Driver
license: GPL
srcversion: C2702161DF2301F83044327
alias: usb:v2357p0103d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v2357p0101d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v2357p0122d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v2357p010Fd*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v2357p010Ed*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v2357p010Dd*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v2001p3316d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v2001p3315d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v07B8p8812d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v2019pAB30d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1740p0100d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1058p0632d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v2001p3313d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0586p3426d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0E66p0022d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0B05p17D2d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0409p0408d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0789p016Ed*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v04BBp0952d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0DF6p0074d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v7392pA822d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v2001p330Ed*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v050Dp1106d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0BDAp881Cd*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0BDAp881Bd*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0BDAp881Ad*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0BDAp8812d*dc*dsc*dp*ic*isc*ip*in*
depends: usbcore,cfg80211
retpoline: Y
vermagic: 4.9.0-7-amd64 SMP mod_unload modversions
parm: rtw_ips_mode:The default IPS mode (int)
parm: rtw_lps_level:The default LPS level (int)
parm: rtw_usb_rxagg_mode:int
parm: rtw_dynamic_agg_enable:int
parm: rtw_drv_log_level:set log level when insert driver module, default log level is _DRV_INFO_ = 4 (uint)
parm: rtw_tx_bw_mode:The max tx bw for 2.4G and 5G. format is the same as rtw_bw_mode (uint)
parm: rtw_rx_ampdu_sz_limit_1ss:RX AMPDU size limit for 1SS link of each BW, 0xFF: no limitation (array of uint)
parm: rtw_rx_ampdu_sz_limit_2ss:RX AMPDU size limit for 2SS link of each BW, 0xFF: no limitation (array of uint)
parm: rtw_rx_ampdu_sz_limit_3ss:RX AMPDU size limit for 3SS link of each BW, 0xFF: no limitation (array of uint)
parm: rtw_rx_ampdu_sz_limit_4ss:RX AMPDU size limit for 4SS link of each BW, 0xFF: no limitation (array of uint)
parm: rtw_vht_enable:int
parm: rtw_vht_rx_mcs_map:VHT RX MCS map (uint)
parm: rtw_rf_config:int
parm: rtw_country_code:The default country code (in alpha2) (charp)
parm: rtw_channel_plan:The default chplan ID when rtw_alpha2 is not specified or valid (int)
parm: rtw_excl_chs:exclusive channel array (array of uint)
parm: rtw_qos_opt_enable:int
parm: ifname:The default name to allocate for first interface (charp)
parm: if2name:The default name to allocate for second interface (charp)
parm: rtw_pwrtrim_enable:int
parm: rtw_initmac:charp
parm: rtw_special_rf_path:int
parm: rtw_chip_version:int
parm: rtw_rfintfs:int
parm: rtw_lbkmode:int
parm: rtw_network_mode:int
parm: rtw_channel:int
parm: rtw_mp_mode:int
parm: rtw_wmm_enable:int
parm: rtw_vrtl_carrier_sense:int
parm: rtw_vcs_type:int
parm: rtw_busy_thresh:int
parm: rtw_ht_enable:int
parm: rtw_bw_mode:int
parm: rtw_ampdu_enable:int
parm: rtw_rx_stbc:int
parm: rtw_rx_ampdu_amsdu:int
parm: rtw_tx_ampdu_amsdu:int
parm: rtw_beamform_cap:int
parm: rtw_lowrate_two_xmit:int
parm: rtw_power_mgnt:int
parm: rtw_smart_ps:int
parm: rtw_low_power:int
parm: rtw_wifi_spec:int
parm: rtw_full_ch_in_p2p_handshake:int
parm: rtw_antdiv_cfg:int
parm: rtw_antdiv_type:int
parm: rtw_drv_ant_band_switch:int
parm: rtw_single_ant_path:int
parm: rtw_switch_usb_mode:int
parm: rtw_enusbss:int
parm: rtw_hwpdn_mode:int
parm: rtw_hwpwrp_detect:int
parm: rtw_hw_wps_pbc:int
parm: rtw_check_hw_status:int
parm: rtw_max_roaming_times:The max roaming times to try (uint)
parm: rtw_mc2u_disable:int
parm: rtw_80211d:Enable 802.11d mechanism (int)
parm: rtw_notch_filter:0 isable, 1:Enable, 2:Enable only for P2P (uint)
parm: rtw_hiq_filter:0:allow all, 1:allow special, 2:deny all (uint)
parm: rtw_adaptivity_en:0:disable, 1:enable (uint)
parm: rtw_adaptivity_mode:0:normal, 1:carrier sense (uint)
parm: rtw_adaptivity_dml:0:disable, 1:enable (uint)
parm: rtw_adaptivity_dc_backoff C backoff for Adaptivity (uint)
parm: rtw_adaptivity_th_l2h_ini:th_l2h_ini for Adaptivity (int)
parm: rtw_adaptivity_th_edcca_hl_diff:th_edcca_hl_diff for Adaptivity (int)
parm: rtw_amplifier_type_2g:BIT3:2G ext-PA, BIT4:2G ext-LNA (uint)
parm: rtw_amplifier_type_5g:BIT6:5G ext-PA, BIT7:5G ext-LNA (uint)
parm: rtw_RFE_type:default init value:64 (uint)
parm: rtw_powertracking_type:default init value:64 (uint)
parm: rtw_GLNA_type:default init value:0 (uint)
parm: rtw_TxBBSwing_2G:default init value:0xFF (uint)
parm: rtw_TxBBSwing_5G:default init value:0xFF (uint)
parm: rtw_OffEfuseMask:default open Efuse Mask value:0 (uint)
parm: rtw_FileMaskEfuse:default drv Mask Efuse value:0 (uint)
parm: rtw_rxgain_offset_2g:default RF Gain 2G Offset value:0 (uint)
parm: rtw_rxgain_offset_5gl:default RF Gain 5GL Offset value:0 (uint)
parm: rtw_rxgain_offset_5gh:uint
parm: rtw_rxgain_offset_5gm:default RF Gain 5GM Offset value:0 (uint)
parm: rtw_pll_ref_clk_sel:force pll_ref_clk_sel, 0xF:use autoload value (uint)
parm: rtw_tx_pwr_by_rate:0 isable, 1:Enable, 2: Depend on efuse (int)
parm: rtw_target_tx_pwr_2g_a:2.4G target tx power (unit:dBm) of RF path A for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm: rtw_target_tx_pwr_2g_b:2.4G target tx power (unit:dBm) of RF path B for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm: rtw_target_tx_pwr_2g_c:2.4G target tx power (unit:dBm) of RF path C for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm: rtw_target_tx_pwr_2g_d:2.4G target tx power (unit:dBm) of RF path D for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm: rtw_target_tx_pwr_5g_a:5G target tx power (unit:dBm) of RF path A for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm: rtw_target_tx_pwr_5g_b:5G target tx power (unit:dBm) of RF path B for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm: rtw_target_tx_pwr_5g_c:5G target tx power (unit:dBm) of RF path C for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm: rtw_target_tx_pwr_5g_d:5G target tx power (unit:dBm) of RF path D for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm: rtw_phy_file_path:The path of phy parameter (charp)
parm: rtw_load_phy_file:PHY File Bit Map (int)
parm: rtw_decrypt_phy_file:Enable Decrypt PHY File (int)
parm: rtw_en_napi:int
parm: rtw_en_gro:int
parm: rtw_iqk_fw_offload:int
|
Quote:
Originally Posted by ferrari
Run it unfiltered like this
and report back.
It's looking like the module you built does NOT explicitly support this chipset. That's not to say that it's not compatible, but the source code doesn't include this particular chipset.
More like no driver matches this particular hardware.
|
|
|
|
09-26-2018, 08:29 PM
|
#23
|
LQ Guru
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 6,016
|
So you can see that your chipset (2357:0115) as reported by 'usb-devices' and 'lsusb' is not in that list of supported chipsets for this driver. You can either try to build a suitable driver that does support this chipset, or take Ztcoracat's advice and find a device with "out-of-the-box" support.
|
|
|
10-16-2018, 03:11 PM
|
#24
|
Member
Registered: Aug 2013
Distribution: Debian, Ubuntu
Posts: 271
Original Poster
Rep: 
|
Apparently the driver provided for the Archer T4U works with V1 & V2. They do not support V3 "as yet".
|
|
|
10-16-2018, 04:04 PM
|
#25
|
LQ Guru
Registered: Dec 2011
Distribution: Slackware, Debian 12, Devuan & MX Linux
Posts: 9,528
|
Quote:
Originally Posted by piobair
Apparently the driver provided for the Archer T4U works with V1 & V2. They do not support V3 "as yet".
|
Have you been able to get another wifi dongle that supports Linux?
|
|
|
11-12-2018, 07:32 PM
|
#26
|
Member
Registered: Aug 2013
Distribution: Debian, Ubuntu
Posts: 271
Original Poster
Rep: 
|
Supposedly, the Panda PAU05 works.
iwconfig reports:
Quote:
modinfo rt2800usb | grep 5572
|
gives a bunch of devices, the last one (alphabetically) usb:v07B8p2870d*dc*dsc*dp*ic*isc*ip*in*
If I am reading that correctly, wlx9cefd5fda976 is missing.
Quote:
Originally Posted by Ztcoracat
Have you been able to get another wifi dongle that supports Linux?
|
|
|
|
11-12-2018, 08:35 PM
|
#27
|
LQ Guru
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 6,016
|
You output shows that the wireless network device node is wlx9cefd5fda976. The wifi device is not yet associated, so now you need to configure it.
|
|
|
11-12-2018, 08:39 PM
|
#28
|
LQ Guru
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 6,016
|
BTW, enclose your output in code tags like this
Code:
root@harold:/home/william# /sbin/iwconfig
lo no wireless extensions.
wlx9cefd5fda976 IEEE 802.11 ESSIDff/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry short long limit:2 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
|
|
|
11-13-2018, 06:54 PM
|
#29
|
Member
Registered: Aug 2013
Distribution: Debian, Ubuntu
Posts: 271
Original Poster
Rep: 
|
SUCCESS!
Code:
su
(password)
kate /etc/NetworkManager/NetworkManager.conf
(paste):
[device]
wifi.scan-rand-mac-address=no
(save, reboot)
Prior to this, the KDE Network Manager would see the device, but would not connect
|
|
|
11-13-2018, 07:22 PM
|
#30
|
LQ Guru
Registered: Dec 2011
Distribution: Slackware, Debian 12, Devuan & MX Linux
Posts: 9,528
|
Quote:
Originally Posted by piobair
SUCCESS!
Code:
su
(password)
kate /etc/NetworkManager/NetworkManager.conf
(paste):
[device]
wifi.scan-rand-mac-address=no
(save, reboot)
Prior to this, the KDE Network Manager would see the device, but would not connect
|
So....your wireless is now working?
|
|
|
All times are GMT -5. The time now is 09:57 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|