erebion/pdx213-temp
Watch
1
0
Fork
You've already forked pdx213-temp
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

clean up: move notes on components into separate files

Browse source
This commit is contained in:
erebion 2026-11-01 13:59:29 +01:00
commit fdc03a27f0
5 changed files with 80 additions and 62 deletions
Download patch file Download diff file Expand all files Collapse all files

5
notes/bluetooth.md Normal file
View file

@ -0,0 +1,5 @@
#### Bluetooth
Works fine.
Note to myself: If Bluetooth does not work... Check that the kernel modules are present and load hci_uart and btqca... Yes, this breaks if I use a boot image with a rootfs that does not have the modules on it... (I'm building those separetely so I don't have to flash the microSD all the time to try out a new kernel).

14
notes/gps.md Normal file
View file

@ -0,0 +1,14 @@
### GPS
GPS likely also works via the modem. But the modem occasionally crashes:
```
[ 2792.695395] qcom_q6v5_pas 4080000.remoteproc: fatal error received: dog_hb.c:367:Task starvation: mmgsdi_1, ping: 4, triage with owner(d.dump 0x1ecf7180)
```
```
root@mobian:~# mmcli -m any --location-enable-gps-nmea
error: couldn't setup location gathering: 'GDBus.Error:org.freedesktop.ModemManager1.Error.MobileEquipment.PhoneFailure: QMI protocol error: Couldn't enable location 'gps-nmea' gathering: Couldn't start GPS engine: QMI protocol error (46): 'GeneralError''
```
Needs investigation, lower priority than some other parts for now.

21
notes/modem.md Normal file
View file

@ -0,0 +1,21 @@
#### Modem
```
[ 50.440514] qcom_q6v5_pas 4080000.remoteproc: fatal error received: dog_hal_common.c:180:DOG detects stalled initialization, triage with IMAGE OWNER
[ 50.440562] remoteproc remoteproc1: crash detected in modem: type fatal error
[ 50.440733] remoteproc remoteproc1: handling crash #1 in modem
[ 50.440744] remoteproc remoteproc1: recovering modem
[ 50.473165] ath10k_snoc 18800000.wifi: firmware crashed! (guid c1e5bbb2-ee6c-4853-9f47-ba65dbda4174)
[ 91.131777] qcom_q6v5_pas 4080000.remoteproc: fatal error received: dog_hal_common.c:180:DOG detects stalled initialization, triage with IMAGE OWNER
[ 91.131827] remoteproc remoteproc1: crash detected in modem: type fatal error
[ 91.131998] remoteproc remoteproc1: handling crash #2 in modem
[ 91.132009] remoteproc remoteproc1: recovering modem
[ 91.179283] ath10k_snoc 18800000.wifi: firmware crashed! (guid a814647c-fc5c-4ad6-b35e-8b88eec81fef)
```
Modem crashes. Reason is missing TA service. Modem works fine with TA service running.
Error message `[ 50.440514] qcom_q6v5_pas 4080000.remoteproc: fatal error received: dog_hal_common.c:180:DOG detects stalled initialization, triage with IMAGE OWNER
` seems to come from `drivers/remoteproc/qcom_q6v5.c`, see https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/remoteproc/qcom_q6v5.c?h=v6.19.12#n126
Error message `[ 50.440562] remoteproc remoteproc1: crash detected in modem: type fatal error` seems to come from https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/remoteproc/remoteproc_core.c?h=v6.19.12#n2707

19
notes/touch.md Normal file
View file

@ -0,0 +1,19 @@
#### Touch
```
[ 63.964541] gpi 900000.dma-controller: Error in Transaction
[ 63.964562] geni_i2c 988000.i2c: DMA txn failed:3
[ 63.964594] geni_i2c 988000.i2c: GPI transfer failed: -5
[ 63.966484] s6sy761 0-0048: failed to turn off sensing
[ 64.599984] gpi 900000.dma-controller: Error in Transaction
[ 64.600041] geni_i2c 988000.i2c: DMA txn failed:3
[ 64.601254] geni_i2c 988000.i2c: GPI transfer failed: -5
```
When logging in, `/dev/input/event2` disappears while Phosh starts... if no finger is on the touch screen (lol), [seemingly needs this patch](https://lore.kernel.org/all/20260923-s6sy761-suspend-v1-1-6fff96e71cb0@ixit.cz/)
There's a patch in the kernel now: [link](https://lore.kernel.org/all/arnvS7Hk7uIKKLrZ@google.com/)
Have not tried it yet.
To Do: Verify the patch fixes broken touch...