Wifi not working on Asus vivobook 16

R

rajeevrdev

New Member
Joined
Jul 23, 2023
Messages
12
Reaction score
6
Credits
98
I have bought a new Asus Vivobook 16 and installed Mint 21.2. I was able to fix most issues but the wifi and bluetooth. I can live without bluetooth. I dont see a wifi(wireless) option at all. From the information its a Mediatek wifi card. I am pretty new to linux driver world. I have updated kernel to the latest version but issue still persist.

lspci
00:00.0 Host bridge: Intel Corporation Device a707
00:02.0 VGA compatible controller: Intel Corporation Device a7a0 (rev 04)
00:04.0 Signal processing controller: Intel Corporation Device a71d
00:06.0 PCI bridge: Intel Corporation Device a74d
00:08.0 System peripheral: Intel Corporation Device a74f
00:0a.0 Signal processing controller: Intel Corporation Device a77d (rev 01)
00:14.0 USB controller: Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller (rev 01)
00:14.2 RAM memory: Intel Corporation Alder Lake PCH Shared SRAM (rev 01)
00:15.0 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #0 (rev 01)
00:15.1 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #1 (rev 01)
00:16.0 Communication controller: Intel Corporation Alder Lake PCH HECI Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation Device 51b8 (rev 01)
00:1c.6 PCI bridge: Intel Corporation Device 51be (rev 01)
00:1f.0 ISA bridge: Intel Corporation Device 519d (rev 01)
00:1f.3 Audio device: Intel Corporation Device 51ca (rev 01)
00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 01)
00:1f.5 Serial bus controller: Intel Corporation Alder Lake-P PCH SPI Controller (rev 01)
01:00.0 Non-Volatile memory controller: Intel Corporation Device f1aa (rev 03)
03:00.0 Network controller: MEDIATEK Corp. Device 7902
Click to expand...

sudo lshw -C network
*-network UNCLAIMED
description: Network controller
product: MEDIATEK Corp.
vendor: MEDIATEK Corp.
physical id: 0
bus info: pci@0000:03:00.0
version: 00
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm bus_master cap_list
configuration: latency=0
resources: iomemory:600-5ff memory:6000000000-60000fffff memory:80800000-80807fff
Click to expand...
nxi -Fxz
System:
Kernel: 6.2.0-25-generic x86_64 bits: 64 compiler: N/A
Desktop: Cinnamon 5.8.4 Distro: Linux Mint 21.2 Victoria
base: Ubuntu 22.04 jammy
Machine:
Type: Laptop System: ASUSTeK product: Vivobook_ASUSLaptop X1605VA_X1605VA
v: 1.0 serial: <superuser required>
Mobo: ASUSTeK model: X1605VA v: 1.0 serial: <superuser required>
UEFI: American Megatrends LLC. v: X1605VA.304 date: 05/29/2023
Battery:
ID-1: BAT0 charge: 15.6 Wh (36.6%) condition: 42.6/42.1 Wh (101.3%)
volts: 11.1 min: 11.8 model: ASUSTeK ASUS Battery status: Discharging
CPU:
Info: 12-core (4-mt/8-st) model: 13th Gen Intel Core i5-13500H bits: 64
type: MST AMCP arch: N/A rev: 2 cache: L1: 1.1 MiB L2: 9 MiB L3: 18 MiB
Speed (MHz): avg: 2739 high: 3200 min/max: 400/4700:3500 cores: 1: 1879
2: 3200 3: 848 4: 3200 5: 3200 6: 3200 7: 1978 8: 3200 9: 3200 10: 3200
11: 723 12: 3200 13: 3200 14: 3200 15: 3200 16: 3200 bogomips: 101990
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel vendor: ASUSTeK driver: i915 v: kernel bus-ID: 00:02.0
Device-2: IMC Networks USB2.0 HD UVC WebCam type: USB driver: uvcvideo
bus-ID: 1-9:3
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting
unloaded: fbdev,vesa gpu: i915 resolution: 1920x1200~60Hz
OpenGL: renderer: Mesa Intel Graphics (RPL-P)
v: 4.6 Mesa 22.2.5-0ubuntu0.1~22.04.3 direct render: Yes
Audio:
Device-1: Intel vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus-ID: 00:1f.3
Sound Server-1: ALSA v: k6.2.0-25-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: MEDIATEK vendor: AzureWave driver: N/A port: N/A bus-ID: 03:00.0
IF-ID-1: enx7a8bcdcfa930 state: unknown speed: -1 duplex: half
mac: <filter>
Bluetooth:
Device-1: IMC Networks Wireless_Device type: USB driver: btusb v: 0.8
bus-ID: 1-10:4
Report: hciconfig ID: hci0 rfk-id: 2 state: down
bt-service: enabled,running rfk-block: hardware: no software: no
address: <filter>
Device-2: Xiaomi Mi/Redmi series (RNDIS + ADB) type: USB
driver: rndis_host v: kernel bus-ID: 1-4:11
Drives:
Local Storage: total: 476.94 GiB used: 121.24 GiB (25.4%)
ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKNU512GZ size: 476.94 GiB
temp: 30.9 C
Partition:
ID-1: / size: 109.44 GiB used: 16.73 GiB (15.3%) fs: ext4
dev: /dev/nvme0n1p2
ID-2: /boot/efi size: 486 MiB used: 6.1 MiB (1.2%) fs: vfat
dev: /dev/nvme0n1p1
ID-3: /home size: 357.91 GiB used: 104.5 GiB (29.2%) fs: ext4
dev: /dev/nvme0n1p3
Swap:
ID-1: swap-1 type: file size: 2 GiB used: 768 KiB (0.0%) file: /swapfile
Sensors:
System Temperatures: cpu: 50.0 C mobo: N/A
Fan Speeds (RPM): cpu: 1500
Info:
Processes: 342 Uptime: 1h 34m Memory: 15.25 GiB used: 3.61 GiB (23.6%)
Init: systemd runlevel: 5 Compilers: gcc: 11.3.0 Packages: 2327 Shell: Bash
v: 5.1.16 inxi: 3.3.13
Click to expand...
 


Thanks for your help . Heres the info. And is there something I can try till support is implemented, temporarily?
Code: 
lspci -knn | grep -iA3 net
03:00.0 Network controller [0280]: MEDIATEK Corp. Device [14c3:7902]
    DeviceName: WLAN
    Subsystem: AzureWave Device [1a3b:5520]
 
Last edited:
arochester said:
Look at this https://forums.linuxmint.com/viewtopic.php?t=400132

Which lead to this https://forum.manjaro.org/t/not-detecting-my-bluetooth-and-wifi-drivers/142209/7

Suggests it is not supported yet.

Might have to buy and uses a small, cheap USB Wi-Fi dongle for a while.
Click to expand...
which states "there is no support for it yet up through kernel 6.3"
Click to expand...

He could always try 6.4.4-1-liquorix-amd64 and see if it's there yet?
https://www.linuxcapable.com/how-to-install-liquorix-kernel-on-linux-mint/
 
you are not showing the drivers needed try andinstall the Broadcom 43 drivers from the software manager
 
xlbooyahlx said:
He could always try 6.4.4-1-liquorix-amd64 and see if it's there yet?
https://www.linuxcapable.com/how-to-install-liquorix-kernel-on-linux-mint/
Click to expand...
i ran that install on a fully updated mint 21.1 (hadn't upgraded to 21.2 yet, but i don't think that would affect the outcome) virtual machine and got a 6.4.5-1-liquorix-amd64 kernel, but don't see that adapter (vendor id 14c3 and device id 7902) listed:
grep -i 14c3 /usr/lib/modules/6.4.5-1-liquorix-amd64/modules.alias | grep 79
alias pci:v000014C3d00007906sv*sd*bc*sc*i* mt7915e
alias pci:v000014C3d00007915sv*sd*bc*sc*i* mt7915e
alias pci:v000014C3d0000790Asv*sd*bc*sc*i* mt7915e
alias pci:v000014C3d00007916sv*sd*bc*sc*i* mt7915e
alias pci:v000014C3d00000616sv*sd*bc*sc*i* mt7921e
alias pci:v000014C3d00000608sv*sd*bc*sc*i* mt7921e
alias pci:v000014C3d00007922sv*sd*bc*sc*i* mt7921e
alias pci:v000014C3d00007961sv*sd*bc*sc*i* mt7921e
alias pci:v000014C3d00007990sv*sd*bc*sc*i* mt7996e
alias pci:v000014C3d00007991sv*sd*bc*sc*i* mt7996e
Click to expand...
at least i believe that's how the aliases work...
 
z7vl7abxc said:
i ran that install on a fully updated mint 21.1 (hadn't upgraded to 21.2 yet, but i don't think that would affect the outcome) virtual machine and got a 6.4.5-1-liquorix-amd64 kernel, but don't see that adapter (vendor id 14c3 and device id 7902) listed:

at least i believe that's how the aliases work...
Click to expand...
And I don't know how VMs interact with regards to Wifi Adapters. I use "bridge" when testing out a distro in a VM.
Way above my paygrade bro.
Sorry :(
 
Last edited:
xlbooyahlx said:
And I don't know how VMs interact with regards to Wifi Adapters
Click to expand...
General rule of thumb for VM's.... the VM is a guest of the main [host] OS which controls the network adaptor ,wired network,and wi-fi. to connect a VM to the internet, the VM uses a bridge to the Host [shows as either wired or bridge in the vm network manager],
to connect the VM direct to the outside world direct, normally you will need to enable the USB in the VM and use an additional USB wi-fi connector
 
Last edited:
Brickwizard said:
General rule of thumb for VM's.... the VM is a guest of the main [host] OS which controls the network adaptor ,wired network,and wi-fi. to connect a VM to the internet, the VM uses a bridge to the Host [shows as either wired or bridge in the vm network manager,
to connect the VM direct to the outside world direct, normally you will need to enable the USB in the VM and use an additional USB wi-fi connector
Click to expand...
xlbooyahlx said:I use "bridge" when testing out a distro in a VM.
Click to expand...
 
@xlbooyahlx i didn't notice the 6.4.5-1-liquorix-amd64 kernel in your signature previously. you should be able to run something like

grep -i 14c3 /usr/lib/modules/6.4.5-1-liquorix-amd64/modules.alias | grep 79

to see if there is a driver that would be assigned to op's 7902 device id adapter.
 
z7vl7abxc said:
grep -i 14c3 /usr/lib/modules/6.4.5-1-liquorix-amd64/modules.alias | grep 79

to see if there is a driver that would be assigned to op's 7902 device id adapter.
Click to expand...
Code: 
john@PhantomRocket:~$ grep -i 14c3 /usr/lib/modules/6.4.5-1-liquorix-amd64/modules.alias | grep 79
alias pci:v000014C3d00007906sv*sd*bc*sc*i* mt7915e
alias pci:v000014C3d00007915sv*sd*bc*sc*i* mt7915e
alias pci:v000014C3d0000790Asv*sd*bc*sc*i* mt7915e
alias pci:v000014C3d00007916sv*sd*bc*sc*i* mt7915e
alias pci:v000014C3d00000616sv*sd*bc*sc*i* mt7921e
alias pci:v000014C3d00000608sv*sd*bc*sc*i* mt7921e
alias pci:v000014C3d00007922sv*sd*bc*sc*i* mt7921e
alias pci:v000014C3d00007961sv*sd*bc*sc*i* mt7921e
alias pci:v000014C3d00007990sv*sd*bc*sc*i* mt7996e
alias pci:v000014C3d00007991sv*sd*bc*sc*i* mt7996e

TY ;)
 
Last edited:
You must log in or register to reply here.

Members online

Total: 844 (members: 4, guests: 840)

Latest posts

Top