ASUS router not visible

I just finished my first update after installing Manjaro and it seems that the router I used to connect through is not visible anymore.

Hi @bluedemon382,

I have an ASUS router that I use for internet myself. And it’s working perfectly. I wonder what you mean by not visible, but please, provide the information as requested by @cscs. Specifically:

  • How was it visible before? and
  • how is it no longer visible?

My ASUS router is standalone and has nothing to do with whatever operating system is in use, and I suspect yours as well. So it might be some kind of network-related thing. But unsure at the moment.

Stuff like: “i cannot see any wireless network on the menu/i see many neighbour networks but not mine/i see about half of the networks i used to/i see my network on the menu but when i click the circle rotates for a while and then disconnects” etc. “And that happened after i…” (Updated yeserday, changed adapters, installed software X, thinkered with the router settings, thinkered with the network settings, whatever).

A ultra quick suggestion fix: right click and see if wireless is enabled at all. There is a strange bug and it gets disabled from itsself sometimes on my machine, for example.

At the very beginning exactly after installing the system and groping in the dark it wasn’t visible, then it became visible for a couple of days, then after the update it disappeared again. At my other location in Austria (now being in Romania) I had no problem connecting to my router (of course another type). I’m suspecting it has something to do with either the special key + F11 (PineBook Pro kill switch for Wi-Fi) or choosing and ISO (actually the archive which I used to burn the image on my SD card I booted from) which was “generic” and not “PineBook”. By that I don’t mean that I’m so stupid that I forgot that I disabled the Wi-Fi module. But this problem intervened after disabling it and re-enabling it and then restarting. The Wi-Fi module is more than functional because I can use the hotspot from my phone or see my neighbours’ connections. It’s exactly my connection that I’m not able to see although I could a couple of days ago. This is driving me mad.

You keep saying this, and I don’t really understand it. But with

…it makes me think your PC doesn’t get an IP. Which might be because of a missing driver. Which could have been determined from the info @cscs requested.

It might also not have been, but without the additional information, there’s no way to even diagnose the cause…

First I’d try to power cycle the router.

Then there are terminal commands you can use instead of the GUI applet.

NetworkManager - ArchWiki

nmcli device wifi list

And a terminal based GUI that you can use as well.


… but I have never used or even seen a pine book pro …

inxi --full --admin --filter --width
  Kernel: 6.3.9-1-MANJARO-ARM arch: aarch64 bits: 64 compiler: gcc v: 12.1.0
    parameters: initrd=/initramfs-linux.img console=ttyS2,1500000
    root=PARTUUID=1eeb7b54-686c-447f-80a7-b57c8d7b3345 rw rootwait audit=0
    splash plymouth.ignore-serial-consoles
  Desktop: KDE Plasma v: 5.27.6 tk: Qt v: 5.15.10 wm: kwin_wayland vt: 1
    dm: SDDM Distro: Manjaro ARM base: Arch Linux
  Type: ARM System: Pine64 Pinebook Pro details: N/A serial: <filter>
  ID-1: cw2015-battery charge: 93% condition: N/A volts: 4.1 min: N/A
    model: N/A type: Li-ion serial: N/A status: discharging
  Info: model: N/A variant-1: cortex-a53 variant-2: cortex-a72 bits: 64
    type: MST AMCP arch: ARMv8 family: 8 model-id: 0 stepping: 4
  Topology: cpus: 1x cores: 4 mt: 2 tpc: 2 st: 2 threads: 6
    smt: <unsupported> cache: N/A
  Speed (MHz): avg: 944 high: 1200 min/max: 408/1416:1800 scaling:
    driver: cpufreq-dt governor: schedutil cores: 1: 816 2: 816 3: 816 4: 816
    5: 1200 6: 1200 bogomips: N/A
  Features: Use -f option to see features
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_store_bypass status: Vulnerable
  Type: spectre_v1 mitigation: __user pointer sanitization
  Type: spectre_v2 status: Vulnerable
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
  Device-1: display-subsystem driver: rockchip_drm v: N/A bus-ID: N/A
    chip-ID: rockchip:display-subsystem class-ID: display-subsystem
  Device-2: rk3399-mali driver: panfrost v: kernel bus-ID: N/A
    chip-ID: rockchip:ff9a0000 class-ID: gpu
  Display: wayland server: v: with: Xwayland v: 23.1.2
    compositor: kwin_wayland driver: X: loaded: modesetting alternate: fbdev
    dri: rockchip gpu: rockchip_drm,panfrost display-ID: 0
  Monitor-1: eDP-1 res: 1536x864 size: N/A modes: N/A
  API: OpenGL v: 3.1 Mesa 23.0.4 renderer: Mali-T860 (Panfrost)
    direct-render: Yes
  Device-1: simple-audio-card driver: asoc_simple_card bus-ID: N/A
    chip-ID: simple-audio-card:es8316-sound class-ID: es8316-sound
  Device-2: simple-audio-card driver: N/A bus-ID: N/A
    chip-ID: simple-audio-card:hdmi-sound class-ID: hdmi-sound
  API: ALSA v: k6.3.9-1-MANJARO-ARM status: kernel-api
    tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 0.3.71 status: active with: 1: pipewire-pulse
    status: active 2: pipewire-media-session status: active 3: pipewire-alsa
    type: plugin tools: pactl,pw-cat,pw-cli
  Message: No ARM data found for this feature.
  IF-ID-1: wlan0 state: up mac: <filter>
  Device-1: rk3399-uart driver: dw_apb_uart bus-ID: N/A
    chip-ID: rockchip:ff180000 class-ID: serial
  Report: rfkill ID: hci0 rfk-id: 1 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
  Local Storage: total: 58.24 GiB used: 8.53 GiB (14.7%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/mmcblk2 maj-min: 179:0 vendor: SanDisk model: DA4064
    size: 58.24 GiB block-size: physical: 512 B logical: 512 B tech: SSD
    serial: <filter> fw-rev: 0x8 scheme: GPT
  ID-1: / raw-size: 57.77 GiB size: 56.79 GiB (98.32%) used: 8.48 GiB (14.9%)
    fs: ext4 dev: /dev/mmcblk2p2 maj-min: 179:2
  ID-2: /boot raw-size: 457.8 MiB size: 457.5 MiB (99.94%)
    used: 53.6 MiB (11.7%) fs: vfat dev: /dev/mmcblk2p1 maj-min: 179:1
  Kernel: swappiness: 60 (default) cache-pressure: 80 (default 100)
  ID-1: swap-1 type: zram size: 5.62 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
  System Temperatures: cpu: 43.3 C mobo: N/A
  Fan Speeds (RPM): N/A
  Processes: 203 Uptime: 12m Memory: total: N/A available: 3.75 GiB
  used: 1.82 GiB (48.6%) Init: systemd v: 253 default: graphical
  tool: systemctl Compilers: gcc: 12.1.0 Packages: pm: pacman pkgs: 767
  libs: 199 tools: pamac Shell: Bash v: 5.1.16 running-in: konsole inxi: 3.3.28

OK, since this is an ARM device, I have to officially throw in my towel, since I know nothing of it. But what @Nachlese is also true, so have a look at that also.

Basically it outputs the same list as the interface…

Of course.

If you / your device can see all other networks, then the router is likely the reason - power cycle it.

Can any other devices see/use that network?
Your phone, for example - can it see and connect to that router?

So if you can connect to other router and your phone, that means your wireless basically works. I think we can strike hardware issues from the list. Still, there are many reasons, why a specific combination of router hardware+firmware and specific wifi adapter+drivers+os config might not work.
Rebooting the rooter and the os are of course “just to be sure” measures. Especially rebooting to router.
Problems with dhcp on both sides (for router firmwares that have dhcp options to config in their interface) were already mentioned.
Another thing that can occur is an incompatibility at the security/authentication level. Especially if the router is very new (AC, WPA3, Wifi 6 etc.) or very old (like using TKIP on WPA2) and the OS/driver/config does not support any of theese.
Last but not least, sometimes there are problems with a specific band. We recently had a thread in the forum for someone not able to connect to 5GHz networks, and the 2.4Ghz working fine (search “5Ghz” in the forum search, the first topic is about an arm device). You can try tinkering with that on the side of the router, frequently the default setting is a combined (2.4+5) network, so the PC chooses automatically. Which won’t work if your card/driver has problems with 5Ghz band.

Yes. Both my mac and my Samsung A20. 2.4G and 5G. The strangest thing is that it hasn’t functioned then it did then it stopped functioning once again. At my other location I had no problem connecting to the building Wi-Fi or to my router which is actually wired to the WLAN.

If it just wasn’t working I’d have attempted to help diagnose this.
But if it is as intermittent as you describe I do not see any way to approach this and cannot help you.

Intermittent speaks for a band problem. Both wifis are in competition with each other, manjaro roams automatically between just like an android phone, but i has a problem connecting with one network.

If you can, try going into the router settings and set separate names for 2.4g and 5g. It will be easier to debug.

Theoretically it can also be a channel problem. If one of the parties is set to wrong regulatory domain, lets say the router is set to Japan, and to channel auto selection. It sees there is little noise on channel 14 and sometimes switches to it, but manjaro is set to US and thus only has 11 channels …and drops the connection.

You can use wavemon to monitor the connection once it is connected and to see the band, channel, channel width, short GI etc. stuff that can cause compatibility issues and can be thinkered on the router side.

What does nmcli device status return?

You are on arm, not sure about your os, but if you dont have mncli, try networkctl status

The only problem is that it’s not connecting anymore.

lo             loopback  connected (externally)  lo         
wlan0          wifi      disconnected            --         
p2p-dev-wlan0  wifi-p2p  disconnected            --

So this rules out most issues with the OS itself.

This makes me think - country specification?

Is the package wireless-regdb installed?

It also makes me think channel collision

I get it - I really do …

networkctl status
●        State: no-carrier
  Online state: unknown

Aug 13 14:48:32 razvan-pc systemd[1]: Starting Network Configuration...
Aug 13 14:48:32 razvan-pc systemd-networkd[543]: lo: Link UP
Aug 13 14:48:32 razvan-pc systemd-networkd[543]: lo: Gained carrier
Aug 13 14:48:32 razvan-pc systemd-networkd[543]: Enumeration completed
Aug 13 14:48:32 razvan-pc systemd[1]: Started Network Configuration.
Aug 13 14:48:33 razvan-pc systemd-networkd[543]: wlan0: Link UP