Wifi needs HKS toggle off/on to come up

Hardware Librem 5
1

Since one of the last system updates my Wifi does not come up alone. I have only the HKS for cam and micro in off position, the others in on.
After entering the SIM PIN this time I waited 5 minutes, then I toggled the HKS for Wifi/BT once. One minute later the L5 was connected to the AP. I have from this boot the dmesg and /var/log/syslog and can put this on my server if someone is willing to look into it. The problem is not always reproducible.

2

amber or byzantium? I think this has “always” been a problem but some people experience it very rarely and some more frequently.

You should check to see whether this is already reported as an Issue.

3

It is with byzantium. A search in


does not give any match. I will file a new one.
4

Here is the link to the filed issue: https://source.puri.sm/Librem5/OS-issues/-/issues/230

After a year of no comments I have here some more details: after a power-on reboot the following commands show:

sudo journalctl -b | grep redpine
(nothing)
sudo journalctl -b | grep 'state file' 
Jan 08 15:21:56 pureos NetworkManager[669]: <info>  [1673187716.6085] monitoring ifupdown state file '/run/network/ifstate'.
Jan 08 15:21:57 pureos NetworkManager[669]: <info>  [1673187717.0848] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Jan 08 15:21:57 pureos NetworkManager[669]: <info>  [1673187717.0859] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Jan 08 15:21:57 pureos NetworkManager[669]: <info>  [1673187717.0882] manager: Networking is enabled by state file
sudo rfkill
ID TYPE       DEVICE          SOFT      HARD
 0 microphone mic-hks    unblocked unblocked
 1 camera     camera-hks unblocked unblocked
 2 wlan       wlan-hks   unblocked unblocked
 3 wwan       wwan-hks   unblocked unblocked

When I then toggle the HKS for Wifi/BT it gives:

sudo journalctl -b | grep redpine
Jan 08 15:27:09 pureos kernel: redpine_91x: rsi_probe: ***** 9116 Module *****
Jan 08 15:27:09 pureos kernel: redpine_91x: redpine_hal_device_init: oper_mode = 5, coex_mode = 2
Jan 08 15:27:09 pureos kernel: redpine_91x: Received Board Version Number: 10
Jan 08 15:27:09 pureos kernel: redpine_91x: rsi_load_firmware: Loading file RS9116_NLINK_WLAN_BT_IMAGE.rps
Jan 08 15:27:09 pureos kernel: redpine_91x:  FW Length = 328192 bytes
Jan 08 15:27:09 pureos kernel: redpine_91x: ================================================
Jan 08 15:27:09 pureos kernel: redpine_91x: ================ RSI Version Info ==============
Jan 08 15:27:09 pureos kernel: redpine_91x: ================================================
Jan 08 15:27:09 pureos kernel: redpine_91x: FW Version        : 2.1.0.0
Jan 08 15:27:09 pureos kernel: redpine_91x: RSI FW Version        :  0000.2.1.0.0502
Jan 08 15:27:09 pureos kernel: redpine_91x: Driver Version        : RS9116.NB0.NL.GNU.LNX.OSD.2.0.0.0024
...

i.e. during boot the redpine chip is not probed. Why?

And, is there a way to get it probed from commandline, i.e. without the HKS toggle?

5

@guido.gunther or @dos, can you please lent me a helping hand, where to look next or how to debug this further to nail it down before the HKS itself gets broken :slight_smile: For how many off/on operations these HKS are designed for.
Thanks.

6

Purism HKS controller was tested for 10,000 times and still good, but this can vary in special cases, so to check if the hks it working like 0 - 1 it easy with multimeter.

1 Like
7

You got me wrong. The HKS (for Wifi/BT) is always doing fine as I can see in /var/log/syslog. But, I have to toggle it, sometimes more then once, to get the redpine chip probed by the kernel. And I’m afraid how long this HKS (and not the controller) will last physically.

8

Tried reinstalled the OS and the bug still persist?
Try without SIM PIM to test… < @guru

9

This L5 has no SIM. I will update uboot.

10

Seems a very strange issue, you definitely need a help from an extremely Gnu+Lnx-savvy like @dos

11

Just to track the issue what version of u-boot do u have a.t.m?

1 Like
12

Updating u-boot (see issue) didn’t fixed the problem.

13

Just repeating small/important tip, you can actually measure this particular HKS toggle current (amperage difference) with your USB meter (especially when red LED light off at 100% of the Librem 5 battery capacity). Please ensure several seconds time between readings of amperage value (precisely measured) and switching WiFi HKS ON/OFF. I’d expect coarse difference of up to 5.0V/0.1A (easy to be spotted there, when both modem and camera HKS off).

As already proposed:

14

If you want to know what u-boot version a *.deb package brings without installing it, one can use on any UNIX the following procedure:

mkdir deb && cd deb
tar tvzf ../debian/output/u-boot-librem5_2022.10-librem5.1_arm64.deb
-rw-r--r--  0 0      0           4  5 Okt. 22:08 debian-binary
-rw-r--r--  0 0      0         916  5 Okt. 22:08 control.tar.xz
-rw-r--r--  0 0      0      422392  5 Okt. 22:08 data.tar.xz

tar xzf ../debian/output/u-boot-librem5_2022.10-librem5.1_arm64.deb
xz -dc data.tar.xz | tar xf -
strings usr/lib/u-boot/librem5/u-boot.imx | grep 'version='
bootargs=u_boot_version=2022.10-ge40b320c3c
2 Likes