Manjaro ARM Minimal 21.04 - Raspberry Pi 4 wifi not working

So, I’d love to start a thread here that can maybe get a sticky later, but I’m having a hard time getting info on how to get the Wifi built into the Raspberry Pi 4 to work.

I’ve tried at least using NetworkManager to get the connection going, and it sees and tries to connect, but it drops out frequently and it won’t keep a stable connection.

Has anyone else got it successfully working on Manjaro ARM Minimal with a Raspberry Pi 4?

Thanks in advance.

I can reinstall, or give any command line info you need.

Ideally I’d like a George R. R. Martin setup where I can use it via command line mostly, then have wifi when I need it to do updates, or Git pushes.

Thanks in advance… again. :slight_smile:

I’m not into ARM specifically, but know a bit about networks.

  1. Can you post an inxi --admin --verbosity=7 --filter --no-host --width so I have an idea of what kind of hardware you’re dealing with?
  2. If I understand correctly, you want to do everything through nmcli. Please correct me if my understanding is wrong…

:scream:

System:
  Kernel: 5.10.25-3-MANJARO-ARM aarch64 bits: 64 compiler: N/A 
  parameters: coherent_pool=1M 8250.nr_uarts=0 
  snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
  video=HDMI-A-1:1280x1024M@60 smsc95xx.macaddr=DC:A6:32:DE:1D:E7 
  vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 
  root=PARTUUID=6e694e14-02 rw rootwait console=ttyS0,115200 console=tty3 
  selinux=0 quiet splash plymouth.ignore-serial-consoles smsc95xx.turbo_mode=N 
  dwc_otg.lpm_enable=0 kgdboc=ttyS0,115200 elevator=noop usbhid.mousepoll=8 
  snd-bcm2835.enable_compat_alsa=0 audit=0 
  Desktop: N/A dm: N/A Distro: Manjaro ARM 
Machine:
  Type: ARM Device System: Raspberry Pi 4 Model B Rev 1.4 details: BCM2835 
  rev: d03114 serial: <filter> 
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Touch Keyboard K400 Plus 
  serial: <filter> charge: Normal status: Discharging 
Memory:
  RAM: total: 7.64 GiB used: 185.1 MiB (2.4%) 
  RAM Report: missing: Required program dmidecode not available 
CPU:
  Info: Quad Core model: N/A variant: cortex-a72 bits: 64 type: MCP 
  arch: ARMv8 family: 8 model-id: N/A stepping: 3 microcode: N/A bogomips: 432 
  Speed: 600 MHz min/max: 600/1500 MHz Core speeds (MHz): 1: 1100 2: 1100 
  3: 1100 4: 1100 
  Features: asimd cpuid crc32 evtstrm fp 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown 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 
Graphics:
  Device-1: bcm2711-vc5 driver: vc4_drm v: N/A bus ID: N/A chip ID: brcm:gpu 
  Device-2: bcm2711-hdmi0 driver: N/A bus ID: N/A chip ID: brcm:soc 
  Device-3: bcm2711-hdmi1 driver: N/A bus ID: N/A chip ID: brcm:soc 
  Display: server: No display server data found. Headless machine? 
  resolution: <xdpyinfo missing> 
  Message: Unable to show advanced data. Required tool glxinfo missing. 
Audio:
  Device-1: bcm2835-audio driver: bcm2835_audio bus ID: N/A 
  chip ID: brcm:bcm2835_audio 
  Device-2: bcm2711-hdmi0 driver: N/A bus ID: N/A chip ID: brcm:soc 
  Device-3: bcm2711-hdmi1 driver: N/A bus ID: N/A chip ID: brcm:soc 
  Sound Server: ALSA v: k5.10.25-3-MANJARO-ARM 
Network:
  Message: No ARM data found for this feature. 
  IF-ID-1: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  IP v4: <filter> type: dynamic noprefixroute scope: global 
  broadcast: <filter> 
  IP v6: <filter> type: deprecated dynamic noprefixroute scope: global 
  IP v6: <filter> type: dynamic mngtmpaddr noprefixroute scope: global 
  IP v6: <filter> scope: link 
  IF-ID-2: wlan0 state: down mac: <filter> 
  WAN IP: <filter> 
Drives:
  Local Storage: total: 29.81 GiB used: 1.85 GiB (6.2%) 
  SMART Message: Required tool smartctl not installed. Check --recommends 
  ID-1: /dev/mmcblk0 model: EB1QT size: 29.81 GiB block size: physical: 512 B 
  logical: 512 B serial: <filter> scheme: MBR 
  Message: No Optical or Floppy data was found. 
RAID:
  Message: No RAID data was found. 
Partition:
  ID-1: / raw size: 29.57 GiB size: 29.09 GiB (98.36%) used: 1.80 GiB (6.2%) 
  fs: ext4 dev: /dev/mmcblk0p2 label: ROOT_MNJRO 
  uuid: 2b97478e-20fc-4e87-820e-708382fe6c5d 
  ID-2: /boot raw size: 213.6 MiB size: 213.4 MiB (99.89%) 
  used: 51.8 MiB (24.3%) fs: vfat dev: /dev/mmcblk0p1 label: BOOT_MNJRO 
  uuid: 980A-B3A2 
Swap:
  Kernel: swappiness: 60 (default) cache pressure: 100 (default) 
  ID-1: swap-1 type: zram size: 11.46 GiB used: 0 KiB (0.0%) priority: 100 
  dev: /dev/zram0 
Unmounted:
  Message: No unmounted partitions found. 
USB:
  Hub: 1-0:1 info: Full speed (or root) Hub ports: 1 rev: 2.0 speed: 480 Mb/s 
  chip ID: 1d6b:0002 
  Hub: 1-1:2 info: Full speed (or root) Hub ports: 4 rev: 2.1 speed: 480 Mb/s 
  chip ID: 2109:3431 
  Device-1: 1-1.4:3 info: Logitech USB Receiver type: Keyboard,Mouse,HID 
  driver: logitech-djreceiver,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s 
  chip ID: 046d:c52b 
  Hub: 2-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.0 speed: 5 Gb/s 
  chip ID: 1d6b:0003 
Sensors:
  Missing: Required tool sensors not installed. Check --recommends 
Info:
  Processes: 128 Uptime: 43m Init: systemd v: 248 Compilers: gcc: N/A 
  Packages: pacman: 203 lib: 46 Shell: fish (login) v: 3.2.1 inxi: 3.1.08

It doesn’t matter, preferrably, I’d just use whatever’s built into Manjaro ARM Minimal for Wifi network connectivity, but if it doesn’t come with anything standard, then I’m willing to install whatever to save a cable.

Minimal edition does not have NetworkManager, but rather has iwd which is the new CLI wifi interface manager from Intel.

https://wiki.archlinux.org/index.php/Iwd

1 Like
  1. In the future, when providing code/output, please copy-paste that output in-between 3 backticks ``` at the beginning and end of the code/text so that the output looks like this:

    Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
    Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
    Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
    Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
    

    instead of like this:

    Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

    (as that makes both our lives much easier)

  2. No need to do anything right now as I’m an editor here on this site and have fixed it for you already. However, in the future I might not see your post so review my edits by pushing the orange pencil above the post I just fixed. :wink:

  3. @Strit Can’t see anything from a hardware level here… Care to shed a :bulb: :scream: *I’m slow and you’re fast! Sorry!!!

:+1:

According to the inxi, the wlan0 is detected. He just needs to use the tool provided to connect to wifi.

1 Like

Recent inxi updates feature full support restored for pi 4, might want to update the inxi there.

Thanks. Just updated it in unstable branch.

1 Like

Pi 4 had some non trivial changes, one I’d been aware of, the failure to get the wlan, since 3 but had not been able to find a clear solution for, the other was new, significant change in the ethernet device location. This led to total failure to detect the network devices in the Pi 4. These were both finally resolved thanks to a series of user data sets. Then I was, finally, able to snag the bluetooth device as well, which was very tricky, it’s a completely non standard bluetooth type, in a non standard location in the device tree, if the word ‘standard’ can ever be applied to ARM SOC device trees.

ARM saw some pretty significant changes and upgrades over last inxi versions, including much improved support for Android devices, though those changes depend on /sys and /proc not being locked down, which they usually are in current Android phones, though not always.

As usual, these upgrades for the Pi were 100% dependent on someone stepping up and providing the data, repeatedly, until the issues were finally resolved.

1 Like

:+1:

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.