I related this problem of L5 not charging on another post. In order to charge it, I must always plug to a laptop with usb A to usb C unplug and battery and plug it again, and with phone always off. After charging a bit I put on the powerwall, after around 1hour I am able to turn it on, again always unlugging the battery and pluging it back again, with phone on, battery always displays 0% and does not charge when on.
I was able to reflash pure OS, it changed nothing, then I tried postmarket OS, same thing.
Please help.
What’s the output of these commands?
ls /sys/class/power_supply/
sudo journalctl -b 0 -k | egrep 'bq|max|tps'
sudo sha256sum /dev/mtd0ro
the first command shows that power_supply is empty, maybe because I just isntalled postmarket OS.
The other two commands don’t work on pmos.
Should I reflash pure OS?
Yes, please. I have nothing against postmarketOS, but it’s different enough that it will be much easier to troubleshoot on PureOS 
I finally had some time for it. I flashed bizantyum but it does not start, I see green light flashing, it boots for 5 sec shows purism logo then turns off
I let it charging for a few hours now it boots properly, but now I have the problem that I can’t connect to wifi, I even created a new wifi on my router withot pasword and does not connect, also tried a rj4 to usb-c and no connection.
Can you get to the shell prompt?
Check whether the Librem 5 has the correct date and time?
I assume that the WiFi card is switched on.
Does the system log show any messages relating to the WiFi? Which WiFi card is it? (Redpine or SparkLAN)
Does it have a SIM in it and is the cellular modem switched on and does it register on the mobile network? i.e. WiFi isn’t happy but what about cellular?
For now the battery just died when I tried connecting via cable, so charging for a few hours then I try again.
it was wrong
If it was wildly wrong then this can cause the WiFi to be unable to get an IP address (and hence in effect be unusable).
how to check?
$ sudo journalctl -b 0 -k | egrep 'bq|max|tps'
[sudo] password for purism:
Jun 23 15:43:39 pureos kernel: clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x1ec0311ec, max_idle_ns: 440795202152 ns
Jun 23 15:43:39 pureos kernel: pid_max: default: 32768 minimum: 301
Jun 23 15:43:39 pureos kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Jun 23 15:43:39 pureos kernel: cryptd: max_cpu_qlen set to 1000
Jun 23 15:43:39 pureos kernel: workingset: timestamp_bits=46 max_order=20 bucket_order=0
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:40 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:41 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:41 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:41 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:41 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:41 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:41 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:41 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:41 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:41 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:41 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:41 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:41 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:41 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:41 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:41 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:41 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:41 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:41 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:42 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:42 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:42 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:42 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:43 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:43 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:43 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:43 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:43 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:43 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:44 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:44 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:49 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:49 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
Jun 23 15:43:59 pureos kernel: bq25890-charger 3-006a: using DT ‘/soc@0/bus@30800000/i2c@30a50000/charger@6a’ for ‘otg’ GPIO lookup
Jun 23 15:43:59 pureos kernel: bq25890-charger 3-006a: Got otg gpio hack
$ sudo sha256sum /dev/mtd0ro
5337b9ca29d72a8d0ff6d668a763e66af697e0a66fd3c8aded7dac8762ffef23 /dev/mtd0ro
Sorry for the late reply I was very busy with work lately.
$ nmcli -f GENERAL.DRIVER d show wlan0
GENERAL.DRIVER: RSI-SDIO WLAN
I was able to connect to wifi, maybe after updating the time and date.
1 Like
Another observation, after reflashing lucks encryption is off, no password to start the phone. Can it be done manually, I mean turn luks encryption on?
The flashing tool still defaults to unencrypted images. If you want it to be encrypted, you need to flash again with --variant luks argument.
Thanks for the info, my priority is still to fix the battery problem. I will reflash once it’s solved.
The USB-C controller isn’t seen on the i2c bus. Please contact support.
Thanks for analysing it. So it can be some firmware problem?