[26383.139688] anx7688 0-0028: recv ocm message cmd=0xf2 01 f2 Ød
[26383.139732] anx7688 0-0028: received HARD_RST, idiot firmware is bored
This indicates that the PinePhone is encountering issues with the anx7688 modem driver and is receiving a Hard Reset (HARD_RST). The "idiot firmware is bored" is likely a humorous or sarcastic remark about the perceived quality or stability of the modem firmware causing this issue.
Based on the "bored" remake, I assume it probably has to do with some sort of wake state, where after some time of not receiving signals the modem hardware turns off then doesn't wake when signals are sent, requiring a hard reset to power on, but that's just speculation.
The PinePhone uses a power management processor called "CRUST" to achieve great standby numbers, but it can lead to issues with the modem waking up after deep sleep, so I believe my speculation is plausible.
Maybe a possible fix would to be to send the modem dummy "do nothing" packets or signals at repeating intervals to keep the hardware awake.
Edit : my speculation here seems incorrect, thus the solution is incorrect as well.
See below.
This indicates that the PinePhone is encountering issues with the anx7688 modem driver and is receiving a Hard Reset (HARD_RST). The “idiot firmware is bored” is likely a humorous or sarcastic remark about the perceived quality or stability of the modem firmware causing this issue.
Tell me you used ChatGPT without telling me you used ChatGPT.
I actually did not... chatgpt isn't the only ai that exists (◠‿◕)
Tbf, my writing style is already quite AI-like due to constantly reading documentation.
Unironically, that's not even the bit written by AI.
The only part that is,
the BC 1.2 result indicating the USB charging mode, and the change in the charge controller status.
As I had no clue what the hell "BC 1.2" was indicating and didn't want to go digging around in the docs for something that obscure. Other things, like "HARD_RST" being a hard reset signal is kinda obvious, imho. I will admit, some is pulled straight from the docs though.
The PinePhone uses a power management processor called "CRUST" to achieve great standby numbers.
Verbatim ripped from the PinePhone docs, that's why it reads more like an advertisement trying to hype up the power management, lol.
P.S. I use uncensored Llama.
P.P.S. I have reading OCD when it comes to my own messages, that's why 99% of them are edited.
P.P.P.S. I put my comment through Llama just now asking it to "AI-ify" it and it's less AI-like then my actual writing :
Or maybe it's more, because honestly who the hell says "tongue-in-cheek"?
Ah, that makes sense! I didn't realise that it was the modem. It runs proprietary firmware, which developers can't really replace.
Edit:
I noticed this message when trying to plug in USB devices while the keyboard addon is attached. For some reason USB devices only work without the keyboard. But I couldn't find any mention of this other than some old bug that has already been fixed.
The modem does have issues with waking up from sleep and I sometimes have to restart it with a script. WiFi has a similar problem.
I see, with that in mind the other lines in the output make more sense.
[26380.765876] anx7688 0-0028: enabling vbus_in power path
[26381.373155] anx7688 0-0028: BC 1.2 result: SDP
They show the modem's power path being enabled, the BC 1.2 result indicating the USB charging mode, and the change in the charge controller status. These lines are related to the modem's power management and charging behavior.
Finally, the output :
[26398.882595] anx7688 0-0028: cc_status changed to CC1 = SRC. Open CC2 = SRC.Open
Is related to the anx76880 USB Type-C controller on the PinePhone, indicating a change in the CC (Communication Channel) status, specifically stating that CC1 is now in the SRC (Source) state and CC2 is in the SRC.Open state.
My speculation then, doesn't seem quite right.
It seems that the modem is behaving improperly when the USB power management state is changed. When plugging in the keyboard along with the other USB devices, it triggers a USB power state change, which makes sense as it needs power from the USB port to work, but the modem firmware seems to improperly handle that change and probably hard crashes and turns off the hardware, then requires a hard reset to power back on which is detected by the "idiot firmware is bored" mechanism that sends the hard reset signal.
As for :
For some reason USB devices only work without the keyboard
That seems unrelated to this specific output. This maybe tangentially related however, pointing to a possible underlying root cause. I recommend looking into the journald logs and see if you can find other related messages. For this, Kjournald is a really good GUI that can help sort the messages.