PineBook Pro Wireless

ARM General system
1

WiFi works during the installation process but after rebooting into the installed system WiFi is missing.

ip link only shows “lo:”

However, so far, it seems that after a poweroff and turning back on again WiFi works, so the issue seems to be tied to rebooting.

Logs from power off/on:

#################### systemd-analyze blame ########################

4.419s firewalld.service
2.510s dev-mmcblk1p2.device
2.376s NetworkManager.service
2.062s upower.service
1.631s systemd-random-seed.service
1.246s udisks2.service
 800ms systemd-journal-flush.service
 745ms boot.mount
 547ms systemd-udevd.service
 545ms systemd-tmpfiles-setup-dev-early.service
 512ms user@1000.service
 455ms systemd-udev-trigger.service
 363ms polkit.service
 362ms systemd-timesyncd.service
 343ms colord.service
 329ms systemd-tmpfiles-setup.serviceYq5naR;Qhr=XNWvYq5naR;Qhr=XNWv
 304ms systemd-tmpfiles-clean.service
 303ms dbus-broker.service
 290ms wpa_supplicant.service
 242ms systemd-hostnamed.service
 231ms systemd-journald.service
 228ms systemd-modules-load.service
 207ms systemd-logind.service
 207ms systemd-udev-load-credentials.service
 195ms accounts-daemon.service
 188ms power-profiles-daemon.service
 181ms alsa-restore.service
 171ms systemd-vconsole-setup.service
 165ms systemd-tmpfiles-setup-dev.service
 154ms dev-hugepages.mount
 150ms dev-mqueue.mount
 149ms gdm.service
 145ms sys-kernel-debug.mount
 137ms tmp.mount
 134ms kmod-static-nodes.service
 132ms modprobe@drm.service
 130ms modprobe@configfs.service
 127ms systemd-backlight@backlight:edp-backlight.service
 122ms user-runtime-dir@1000.service
 106ms systemd-update-utmp.service
 105ms rtkit-daemon.service
 101ms systemd-userdbd.service
  67ms systemd-sysctl.service
  63ms sys-fs-fuse-connections.mount
  61ms sys-kernel-config.mount
  59ms modprobe@fuse.service
  55ms systemd-rfkill.service
  49ms systemd-remount-fs.service
  45ms systemd-user-sessions.service
  35ms modprobe@dm_mod.service
  35ms modprobe@loop.service


#################### lspci -vnn ########################



#################### lsusb ########################

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 258a:001e HAILUCK CO.,LTD USB KEYBOARD
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


#################### inxi -Fxxc0z ########################

System:
  Kernel: 6.13.2-1-eos-arm arch: aarch64 bits: 64 compiler: gcc v: 14.1.1
  Desktop: GNOME v: 47.3 tk: GTK v: 3.24.48 wm: gnome-shell dm: GDM Distro: EndeavourOS
    base: Arch Linux
Machine:
  Type: ARM System: Pine64 Pinebook Pro details: N/A serial: <filter>
Battery:
  ID-1: cw2015-battery charge: 27.6 Wh (92.0%) condition: 30.0/30.0 Wh (100.0%) volts: 4.1 min: 3.0
    model: N/A serial: N/A status: discharging
CPU:
  Info: 6-core model: N/A variant-1: cortex-a53 variant-2: cortex-a72 bits: 64 type: MCP
    arch: ARMv8 rev: 4 cache: L1: 416 KiB L2: 1.5 MiB
  Speed (MHz): avg: 1416 min/max: 408/1416:1800 cores: 1: 1416 2: 1416 3: 1416 4: 1416 5: 1416
    6: 1416 bogomips: N/A
  Features: Use -f option to see features
Graphics:
  Device-1: display-subsystem driver: rockchip_drm v: N/A bus-ID: N/A
    chip-ID: rockchip:display-subsystem
  Device-2: rk3399-mali driver: panfrost v: kernel bus-ID: N/A chip-ID: rockchip:ff9a0000
  Display: wayland server: X.Org v: 24.1.4 with: Xwayland v: 24.1.4 compositor: gnome-shell
    driver:
    gpu: cdn-dp,dw-mipi-dsi-rockchip,dwhdmi-rockchip,innohdmi-rockchip,rockchip-dp,rockchip-drm,rockchip-lvds,rockchip-vop,rockchip-vop2
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96
  Monitor-1: eDP-1 res: 1920x1080 hz: 60 dpi: 158
  API: EGL v: 1.5 platforms: device: 0 drv: panfrost device: 1 drv: swrast gbm: drv: panfrost
    surfaceless: drv: panfrost wayland: drv: panfrost x11: drv: panfrost
  API: OpenGL v: 4.5 compat-v: 3.1 vendor: mesa v: 24.3.4-arch1.1 glx-v: 1.4 direct-render: yes
    renderer: Mali-T860 (Panfrost) device-ID: ffffffff:ffffffff
  Info: Tools: api: eglinfo,glxinfo x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: simple-audio-card driver: asoc_simple_card bus-ID: N/A
    chip-ID: simple-audio-card:es8316-sound
  Device-2: simple-audio-card driver: N/A bus-ID: N/A chip-ID: simple-audio-card:hdmi-sound
  API: ALSA v: k6.13.2-1-eos-arm status: kernel-api
  Server-1: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
Network:
  Message: No ARM data found for this feature.
  IF-ID-1: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: rk3399-uart driver: dw_apb_uart bus-ID: N/A chip-ID: rockchip:ff180000
  Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: disabled rfk-block: hardware: no
    software: no address: N/A
Drives:
  Local Storage: total: 117.18 GiB used: 6.14 GiB (5.2%)
  ID-1: /dev/mmcblk1 model: USD00 size: 58.94 GiB type: Removable serial: <filter>
  ID-2: /dev/mmcblk2 vendor: SanDisk model: DA4064 size: 58.24 GiB type: Removable
    serial: <filter>
Partition:
  ID-1: / size: 57.52 GiB used: 6.05 GiB (10.5%) fs: ext4 dev: /dev/mmcblk1p2
  ID-2: /boot size: 383.8 MiB used: 83.7 MiB (21.8%) fs: vfat dev: /dev/mmcblk1p1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 41.1 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: N/A available: 3.77 GiB used: 1.42 GiB (37.6%)
  Processes: 244 Power: uptime: 17m wakeups: 0 Init: systemd v: 257 default: graphical
  Packages: pm: pacman pkgs: 828 Compilers: gcc: 14.1.1 Client: shell wrapper v: 5.2.37-release
    inxi: 3.3.37

Logs after a reboot:

#################### systemd-analyze blame ########################

6.044s firewalld.service
2.822s dev-mmcblk1p2.device
2.438s NetworkManager.service
1.769s upower.service
1.533s systemd-random-seed.service
1.247s udisks2.service
 993ms systemd-journal-flush.service
 875ms boot.mount
 741ms systemd-udevd.service
 648ms systemd-tmpfiles-setup-dev-early.service
 593ms user@1000.service
 589ms accounts-daemon.service
 513ms wpa_supplicant.service
 477ms systemd-tmpfiles-setup.service
 474ms dbus-broker.service
 444ms systemd-udev-trigger.service
 368ms systemd-timesyncd.service
 345ms systemd-vconsole-setup.service
 326ms colord.service
 310ms polkit.service
 282ms power-profiles-daemon.service
 252ms systemd-journald.service
 225ms systemd-logind.service
 222ms alsa-restore.service
 218ms systemd-backlight@backlight:edp-backlight.service
 218ms systemd-hostnamed.service
 200ms rtkit-daemon.service
 198ms systemd-tmpfiles-setup-dev.service
 169ms systemd-userdbd.service
 154ms systemd-modules-load.service
 147ms gdm.service
 139ms systemd-udev-load-credentials.service
 138ms systemd-rfkill.service
 129ms modprobe@drm.service
 104ms dev-hugepages.mount
 100ms user-runtime-dir@1000.service
 100ms dev-mqueue.mount
  94ms sys-kernel-debug.mount
  87ms systemd-update-utmp.service
  86ms tmp.mount
  86ms modprobe@loop.service
  86ms systemd-sysctl.service
  84ms modprobe@dm_mod.service
  82ms kmod-static-nodes.service
  77ms modprobe@configfs.service
  64ms systemd-remount-fs.service
  59ms modprobe@fuse.service
  46ms systemd-user-sessions.service
  29ms sys-fs-fuse-connections.mount
  27ms sys-kernel-config.mount


#################### lspci -vnn ########################



#################### lsusb ########################

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 258a:001e HAILUCK CO.,LTD USB KEYBOARD
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 007 Device 003: ID 0c45:6321 Microdia HP Integrated Webcam
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub


#################### inxi -Fxxc0z ########################

System:
  Kernel: 6.13.2-1-eos-arm arch: aarch64 bits: 64 compiler: gcc v: 14.1.1
  Desktop: GNOME v: 47.3 tk: GTK v: 3.24.48 wm: gnome-shell dm: GDM Distro: EndeavourOS
    base: Arch Linux
Machine:
  Type: ARM System: Pine64 Pinebook Pro details: N/A serial: <filter>
Battery:
  ID-1: cw2015-battery charge: 25.2 Wh (84.0%) condition: 30.0/30.0 Wh (100.0%) volts: 4.0 min: 3.0
    model: N/A serial: N/A status: discharging
CPU:
  Info: 6-core model: N/A variant-1: cortex-a53 variant-2: cortex-a72 bits: 64 type: MCP
    arch: ARMv8 rev: 4 cache: L1: 416 KiB L2: 1.5 MiB
  Speed (MHz): avg: 600 min/max: 408/1416:1800 cores: 1: 600 2: 600 3: 600 4: 600 5: 600 6: 600
    bogomips: N/A
  Features: Use -f option to see features
Graphics:
  Device-1: display-subsystem driver: rockchip_drm v: N/A bus-ID: N/A
    chip-ID: rockchip:display-subsystem
  Device-2: rk3399-mali driver: panfrost v: kernel bus-ID: N/A chip-ID: rockchip:ff9a0000
  Device-3: Microdia HP Integrated Webcam driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s
    lanes: 1 bus-ID: 7-1.2:3 chip-ID: 0c45:6321
  Display: wayland server: X.Org v: 24.1.4 with: Xwayland v: 24.1.4 compositor: gnome-shell
    driver:
    gpu: cdn-dp,dw-mipi-dsi-rockchip,dwhdmi-rockchip,innohdmi-rockchip,rockchip-dp,rockchip-drm,rockchip-lvds,rockchip-vop,rockchip-vop2
    display-ID: _interface_:0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96
  Monitor-1: eDP-1 res: 1920x1080 hz: 60 dpi: 158
  API: EGL v: 1.5 platforms: device: 0 drv: panfrost device: 1 drv: swrast gbm: drv: panfrost
    surfaceless: drv: panfrost wayland: drv: panfrost x11: drv: panfrost
  API: OpenGL v: 4.5 compat-v: 3.1 vendor: mesa v: 24.3.4-arch1.1 glx-v: 1.4 direct-render: yes
    renderer: Mali-T860 (Panfrost) device-ID: ffffffff:ffffffff
  Info: Tools: api: eglinfo,glxinfo x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: simple-audio-card driver: asoc_simple_card bus-ID: N/A
    chip-ID: simple-audio-card:es8316-sound
  Device-2: simple-audio-card driver: N/A bus-ID: N/A chip-ID: simple-audio-card:hdmi-sound
  API: ALSA v: k6.13.2-1-eos-arm status: kernel-api
  Server-1: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
Network:
  Message: No ARM data found for this feature.
Bluetooth:
  Device-1: rk3399-uart driver: dw_apb_uart bus-ID: N/A chip-ID: rockchip:ff180000
  Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: disabled rfk-block: hardware: no
    software: no address: N/A
Drives:
  Local Storage: total: 117.18 GiB used: 6.34 GiB (5.4%)
  ID-1: /dev/mmcblk1 model: USD00 size: 58.94 GiB type: Removable serial: <filter>
  ID-2: /dev/mmcblk2 vendor: SanDisk model: DA4064 size: 58.24 GiB type: Removable
    serial: <filter>
Partition:
  ID-1: / size: 57.52 GiB used: 6.26 GiB (10.9%) fs: ext4 dev: /dev/mmcblk1p2
  ID-2: /boot size: 383.8 MiB used: 83.7 MiB (21.8%) fs: vfat dev: /dev/mmcblk1p1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 39.4 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: N/A available: 3.77 GiB used: 784 MiB (20.3%)
  Processes: 253 Power: uptime: 2m wakeups: 0 Init: systemd v: 257 default: graphical
  Packages: pm: pacman pkgs: 828 Compilers: gcc: 14.1.1 Client: shell wrapper v: 5.2.37-release
    inxi: 3.3.37
2

Welcome to :enos: forums!!

I changed the topic to be under arm.
Also pinging @Pudge in case he has seen the issue before

1 Like
3

It has dedicated hardware switches to enable the camera, microphone & wifi, check if it’s enabled. You may want to check the notes how to bind/unbind it properly without the need to reboot the machine each time you want to turn on/off the wifi.

Their wifi troubleshooting section should also provide some info.

Its a shame that they saved on the ethernet jack on that machine.

2 Likes
4

My Pinebook Pro also does this. It has nothing to do with the privacy switches. Wifi just doesn’t turn on when you reboot. It only turns on when you power up the device after being turned off.

It didn’t always do this, but has for the last year or two. There must have been some sort of hardware update that caused this.

3 Likes
5

I tried the hardware switches, didn’t make any difference

6

Is the issue distro-agnostic for you?

7

Yes, it did this when I was still running Manjaro, and it continues now that I’m running Endeavour. In both cases, though, KDE has been my destkop environment.

1 Like
8

i just put this here for ref

Every once in a great while, the kernel will just fail to detect the wifi hardware. (symptom: ip link shows no wlan0.) Only solution found so far is to hard-reset the machine. (Complete power-off then on again.)

Ref info :
" https://wiki.pine64.org/wiki/Pinebook_Pro_Troubleshooting_Guide#WiFi_issues "

EDit… so best just power off / power back on if use wifi when ( reboot needed )

if this no good for you , get Linux compatible USB wifi dongle … then problem no happen ( choice your )

3 Likes
9

I have not had this wifi problem with my Pinebook Pro.

One thing I have done, is the original Manjaro eMMC is still in the eMMC slot. I believe that it uses the boot loader on the eMMC when booting.

I did this because originally when it booted from uSD card it booted nice and clean. When I took the Manjaro eMMC out, then a uSD boot resulted in a scrambled screen followed by the tow-boot icon on the screen. I put the Manjaro eMMC back in just to clean things up, as I use uSD cards for my development and testing.

So, I believe (and I might be wrong) that with the Manjaro eMMC in place it uses the SPI on the eMMC. When the Manjaro eMMC is out, it uses the on board SPI.

That is my best guess.

The case is not thick enough for a ethernet jack.

Pudge

EDIT:

Here is the USB C to Ethernet adaptor I ended up with and it works great. I got this because when I am home, I wanted to be able to access my LAN file server running on a RPi 4b, and for security reasons the server does not offer WiFi.

10

yes they good Mr Pudge . Every Linux usr should have usb/ usb-c Ethernet adapter + a usb/usb-c Linux compatible wifi adatper in bag/tool box . They WILL be need at some point in time . ( you be thank full you have them )

1 Like
11

I just updated my pinebook pro after an year and it went smoothly. I don’t have any wifi issues. I’m running Cinnamon.

1 Like
12

Exactly the same on mine.