Librem5 issueshttps://source.puri.sm/groups/Librem5/-/issues2020-11-24T18:38:18Zhttps://source.puri.sm/Librem5/firmware-tps6598x-nonfree/-/issues/2Enable VConn2020-11-24T18:38:18ZGuido GuntherEnable VConnThe last set of adapters that did not negotiate alt mode did fail due to a rejected VConn swap request. With VConn enabled they work as well. I'll add an MR once i know something else broke.The last set of adapters that did not negotiate alt mode did fail due to a rejected VConn swap request. With VConn enabled they work as well. I'll add an MR once i know something else broke.Evg++https://source.puri.sm/Librem5/firmware-tps6598x-nonfree/-/issues/1Birch and Chestnut version2020-09-20T15:05:44ZAngus Ainslieangus.ainslie@puri.smBirch and Chestnut versionWe should also create a 5V only variant for Birch and Chestnut to protect the CC linesWe should also create a 5V only variant for Birch and Chestnut to protect the CC lineshttps://source.puri.sm/Librem5/deb-build-jobs/-/issues/62blessed builds: Does not stash build artifacts2020-10-30T08:53:14ZGuido Guntherblessed builds: Does not stash build artifactsSigh, I had another look at the blessed build scripts. In contrast to the CI build script these fail to stash build artifacts but execute the upload script in a separte step. So while this can work (and usually does) it's just luck. This...Sigh, I had another look at the blessed build scripts. In contrast to the CI build script these fail to stash build artifacts but execute the upload script in a separte step. So while this can work (and usually does) it's just luck. This is how it should be done:
https://source.puri.sm/Librem5/deb-build-jobs/-/blob/master/ci_build.groovy#L151
So while !222 is nice for not wasting resouces (and hence speeding up builds) we need to stash things for this to work reliably.
/cc @martin.kepplinger since this is what happens with the kernel builds:
```
Running on Jenkins in /var/lib/jenkins/workspace/Builds/debs/deb-linux-kernel-amber-phone-staging-aarch64@2
... [ kernel build ] ...
Running on Jenkins in /var/lib/jenkins/workspace/Builds/debs/deb-linux-kernel-amber-phone-staging-aarch64@3
[Pipeline] {
[Pipeline] archiveArtifacts
Archiving artifacts
‘*.deb’ doesn’t match anything
```https://source.puri.sm/Librem5/linux/-/issues/216USB gadget resets spontaneously2021-10-03T17:55:38ZSebastian KrzyszkowiakUSB gadget resets spontaneouslySometimes when I have the phone connected to a PC, the connection resets spontaneously.
dmesg on the host side shows:
```
[419552.532692] usb 1-9: USB disconnect, device number 21
[419552.532830] cdc_eem 1-9:1.0 enp0s20f0u9: unregister ...Sometimes when I have the phone connected to a PC, the connection resets spontaneously.
dmesg on the host side shows:
```
[419552.532692] usb 1-9: USB disconnect, device number 21
[419552.532830] cdc_eem 1-9:1.0 enp0s20f0u9: unregister 'cdc_eem' usb-0000:00:14.0-9, CDC EEM Device
[419552.533524] br0: port 1(enp0s20f0u9) entered disabled state
[419552.540814] device enp0s20f0u9 left promiscuous mode
[419552.540844] br0: port 1(enp0s20f0u9) entered disabled state
[419552.868227] usb 1-9: new high-speed USB device number 22 using xhci_hcd
[419558.108387] usb 1-9: unable to read config index 0 descriptor/start: -110
[419558.108398] usb 1-9: can't read configurations, error -110
[419558.231673] usb 1-9: new high-speed USB device number 23 using xhci_hcd
[419558.376828] usb 1-9: New USB device found, idVendor=0525, idProduct=a4a2, bcdDevice= 5.07
[419558.376832] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[419558.376835] usb 1-9: Product: RNDIS/Ethernet Gadget
[419558.376837] usb 1-9: Manufacturer: Linux 5.7.0-1-librem5 with dwc3-gadget
[419558.381870] cdc_eem 1-9:1.0 usb0: register 'cdc_eem' at usb-0000:00:14.0-9, CDC EEM Device, 56:97:fa:9c:a4:eb
[419558.417293] cdc_eem 1-9:1.0 enp0s20f0u9: renamed from usb0
```
(the log shows `g_ether` module being used, but it also happens with `g_multi`)
No signs of it happening on the device's dmesg (other that usb0 interface going down and up).https://source.puri.sm/Librem5/linux/-/issues/215wm8962: Expose DMIC_ENA, ADCL_ENA and ADCR_ENA as ALSA controls2022-02-04T08:30:33ZSebastian Krzyszkowiakwm8962: Expose DMIC_ENA, ADCL_ENA and ADCR_ENA as ALSA controlsIn order to be able to use the analog microphone input from the headphone jack, digital microphones need to be disabled in the codec. However, currently there's no way to do it - the driver automatically sets DMIC_ENA as part of its powe...In order to be able to use the analog microphone input from the headphone jack, digital microphones need to be disabled in the codec. However, currently there's no way to do it - the driver automatically sets DMIC_ENA as part of its power management routines.
The ideal scenario would be to still have the driver enable and disable DMIC_ENA automatically for power savings, but only when an appropriate ALSA mixer control is enabled - so the headset UCM device can leave it disabled.
(register `WM8962_PWR_MGMT_1` [0x19], bit `WM8962_DMIC_ENA_SHIFT` [10])
Related to #5Evghttps://source.puri.sm/Librem5/linux/-/issues/214max17055: Put into a hibernation mode at power off2020-08-10T02:49:13ZSebastian Krzyszkowiakmax17055: Put into a hibernation mode at power offmax17055 can be put into a low-power hibernation mode - it automatically sleeps once the current draw becomes low enough. It makes the ADC readings much rarer, so we don't want it to get into that mode when the phone is running, but sinc...max17055 can be put into a low-power hibernation mode - it automatically sleeps once the current draw becomes low enough. It makes the ADC readings much rarer, so we don't want it to get into that mode when the phone is running, but since max17055 is one of the few things that remains on even when the whole phone is off, we may want to utilize the hibernation mode then and save a few µA.
Currently the max170xx driver doesn't touch hibernation config at all. I think we would like it to wake up the gauge and disable hibernation at init, and allow it to hibernate again when the system shuts down.
See https://pdfserv.maximintegrated.com/en/an/AN6358.pdf - pages 33-35; and https://pdfserv.maximintegrated.com/en/an/MAX17055-software-implementation-guide.pdf - page 4.https://source.puri.sm/Librem5/linux/-/issues/213Constant activity on the i2c-3 bus2020-08-08T21:13:37ZSebastian KrzyszkowiakConstant activity on the i2c-3 busSomething seems to be constantly talkative on the i2c-3 bus, which doesn't sound like a good thing for the battery life:
```
[24731.728803] [3739] i2c_imx:i2c_imx_xfer_common:995: i2c i2c-3: <i2c_imx_xfer_common>
[24731.728816] [3739] i...Something seems to be constantly talkative on the i2c-3 bus, which doesn't sound like a good thing for the battery life:
```
[24731.728803] [3739] i2c_imx:i2c_imx_xfer_common:995: i2c i2c-3: <i2c_imx_xfer_common>
[24731.728816] [3739] i2c_imx:i2c_imx_start:604: i2c i2c-3: <i2c_imx_start>
[24731.728995] [3739] i2c_imx:i2c_imx_bus_busy:463: i2c i2c-3: <i2c_imx_bus_busy>
[24731.729007] [3739] i2c_imx:i2c_imx_xfer_common:1029: i2c i2c-3: <i2c_imx_xfer_common> transfer message: 0
[24731.729022] [3739] i2c_imx:i2c_imx_write:847: i2c i2c-3: <i2c_imx_write> write slave address: addr=0x6c
[24731.729080] [3739] i2c_imx:i2c_imx_trx_complete:524: i2c i2c-3: <i2c_imx_trx_complete> TRX complete
[24731.729090] [3739] i2c_imx:i2c_imx_acked:536: i2c i2c-3: <i2c_imx_acked> ACK received
[24731.729100] [3739] i2c_imx:i2c_imx_write:857: i2c i2c-3: <i2c_imx_write> write data
[24731.729112] [3739] i2c_imx:i2c_imx_write:863: i2c i2c-3: <i2c_imx_write> write byte: B0=0xA
[24731.729170] [3739] i2c_imx:i2c_imx_trx_complete:524: i2c i2c-3: <i2c_imx_trx_complete> TRX complete
[24731.729182] [3739] i2c_imx:i2c_imx_acked:536: i2c i2c-3: <i2c_imx_acked> ACK received
[24731.729194] [3739] i2c_imx:i2c_imx_xfer_common:1020: i2c i2c-3: <i2c_imx_xfer_common> repeated start
[24731.729206] [3739] i2c_imx:i2c_imx_bus_busy:463: i2c i2c-3: <i2c_imx_bus_busy>
[24731.729220] [3739] i2c_imx:i2c_imx_xfer_common:1029: i2c i2c-3: <i2c_imx_xfer_common> transfer message: 1
[24731.729231] [3739] i2c_imx:i2c_imx_read:888: i2c i2c-3: <i2c_imx_read> write slave address: addr=0x6d
[24731.729290] [3739] i2c_imx:i2c_imx_trx_complete:524: i2c i2c-3: <i2c_imx_trx_complete> TRX complete
[24731.729303] [3739] i2c_imx:i2c_imx_acked:536: i2c i2c-3: <i2c_imx_acked> ACK received
[24731.729313] [3739] i2c_imx:i2c_imx_read:899: i2c i2c-3: <i2c_imx_read> setup bus
[24731.729328] [3739] i2c_imx:i2c_imx_read:916: i2c i2c-3: <i2c_imx_read> read data
[24731.729376] [3739] i2c_imx:i2c_imx_trx_complete:524: i2c i2c-3: <i2c_imx_trx_complete> TRX complete
[24731.729388] [3739] i2c_imx:i2c_imx_read:968: i2c i2c-3: <i2c_imx_read> set TXAK
[24731.729405] [3739] i2c_imx:i2c_imx_read:979: i2c i2c-3: <i2c_imx_read> read byte: B0=0x7
[24731.729450] [3739] i2c_imx:i2c_imx_trx_complete:524: i2c i2c-3: <i2c_imx_trx_complete> TRX complete
[24731.729462] [3739] i2c_imx:i2c_imx_read:949: i2c i2c-3: <i2c_imx_read> clear MSTA
[24731.729476] [3739] i2c_imx:i2c_imx_bus_busy:463: i2c i2c-3: <i2c_imx_bus_busy>
[24731.729493] [3739] i2c_imx:i2c_imx_read:979: i2c i2c-3: <i2c_imx_read> read byte: B1=0x0
[24731.729505] [3739] i2c_imx:i2c_imx_xfer_common:1067: i2c i2c-3: <i2c_imx_xfer_common> exit with: success msg: 2
[24731.729617] [3739] i2c_imx:i2c_imx_xfer_common:995: i2c i2c-3: <i2c_imx_xfer_common>
[24731.729630] [3739] i2c_imx:i2c_imx_start:604: i2c i2c-3: <i2c_imx_start>
[24731.729810] [3739] i2c_imx:i2c_imx_bus_busy:463: i2c i2c-3: <i2c_imx_bus_busy>
[24731.729824] [3739] i2c_imx:i2c_imx_xfer_common:1029: i2c i2c-3: <i2c_imx_xfer_common> transfer message: 0
[24731.729868] [3739] i2c_imx:i2c_imx_write:847: i2c i2c-3: <i2c_imx_write> write slave address: addr=0x6c
[24731.729928] [3739] i2c_imx:i2c_imx_trx_complete:524: i2c i2c-3: <i2c_imx_trx_complete> TRX complete
[24731.729960] [3739] i2c_imx:i2c_imx_acked:536: i2c i2c-3: <i2c_imx_acked> ACK received
[24731.729971] [3739] i2c_imx:i2c_imx_write:857: i2c i2c-3: <i2c_imx_write> write data
[24731.729983] [3739] i2c_imx:i2c_imx_write:863: i2c i2c-3: <i2c_imx_write> write byte: B0=0xB
[24731.730045] [3739] i2c_imx:i2c_imx_trx_complete:524: i2c i2c-3: <i2c_imx_trx_complete> TRX complete
[24731.730089] [3739] i2c_imx:i2c_imx_acked:536: i2c i2c-3: <i2c_imx_acked> ACK received
[24731.730101] [3739] i2c_imx:i2c_imx_xfer_common:1020: i2c i2c-3: <i2c_imx_xfer_common> repeated start
[24731.730146] [3739] i2c_imx:i2c_imx_bus_busy:463: i2c i2c-3: <i2c_imx_bus_busy>
[24731.730179] [3739] i2c_imx:i2c_imx_xfer_common:1029: i2c i2c-3: <i2c_imx_xfer_common> transfer message: 1
[24731.730191] [3739] i2c_imx:i2c_imx_read:888: i2c i2c-3: <i2c_imx_read> write slave address: addr=0x6d
[24731.730848] [3739] i2c_imx:i2c_imx_trx_complete:524: i2c i2c-3: <i2c_imx_trx_complete> TRX complete
[24731.730861] [3739] i2c_imx:i2c_imx_acked:536: i2c i2c-3: <i2c_imx_acked> ACK received
[24731.730873] [3739] i2c_imx:i2c_imx_read:899: i2c i2c-3: <i2c_imx_read> setup bus
[24731.730889] [3739] i2c_imx:i2c_imx_read:916: i2c i2c-3: <i2c_imx_read> read data
[24731.730936] [3739] i2c_imx:i2c_imx_trx_complete:524: i2c i2c-3: <i2c_imx_trx_complete> TRX complete
[24731.730948] [3739] i2c_imx:i2c_imx_read:968: i2c i2c-3: <i2c_imx_read> set TXAK
[24731.730963] [3739] i2c_imx:i2c_imx_read:979: i2c i2c-3: <i2c_imx_read> read byte: B0=0x9
[24731.731011] [3739] i2c_imx:i2c_imx_trx_complete:524: i2c i2c-3: <i2c_imx_trx_complete> TRX complete
[24731.731021] [3739] i2c_imx:i2c_imx_read:949: i2c i2c-3: <i2c_imx_read> clear MSTA
[24731.731034] [3739] i2c_imx:i2c_imx_bus_busy:463: i2c i2c-3: <i2c_imx_bus_busy>
[24731.731048] [3739] i2c_imx:i2c_imx_read:979: i2c i2c-3: <i2c_imx_read> read byte: B1=0x0
[24731.731061] [3739] i2c_imx:i2c_imx_xfer_common:1067: i2c i2c-3: <i2c_imx_xfer_common> exit with: success msg: 2
```https://source.puri.sm/Librem5/feedbackd/-/issues/25End feedback when client disconnects?2021-04-26T09:34:14ZGuido GuntherEnd feedback when client disconnects?On the list for quite a while but let's have a bug: Need to investigate if e.g. listening to `GDBusConnection` `close` does the right thing and if so if we want that? E.g. LED feedback should likely go on after a missed call even when ca...On the list for quite a while but let's have a bug: Need to investigate if e.g. listening to `GDBusConnection` `close` does the right thing and if so if we want that? E.g. LED feedback should likely go on after a missed call even when calls vanishes completely. So client would need to be able to opt out.https://source.puri.sm/Librem5/Apps_Issues/-/issues/192Feature Request: A system-tray2020-08-17T11:19:40ZBjörn TantauFeature Request: A system-trayIs a system tray somewhere on the roadmap? I installed twinkle (an SIP client) today but could not really control it, as it minimizes to the system tray.
I'd even use a dedicated app to display tray icons. But any way to access them is w...Is a system tray somewhere on the roadmap? I installed twinkle (an SIP client) today but could not really control it, as it minimizes to the system tray.
I'd even use a dedicated app to display tray icons. But any way to access them is welcome.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/165Phone went into a call loop after failing to hangup and possible be called back2020-08-07T10:08:31ZJonas Smedegaardjonas.smedegaard@puri.smPhone went into a call loop after failing to hangup and possible be called backWith my new phone - Dogwood - I tried call a friend today, and that went quite badly: My friend didn't pick up and it went to voicemail - I wanted to hang up without leaving a message but the phone had moved to a different screen (I wou...With my new phone - Dogwood - I tried call a friend today, and that went quite badly: My friend didn't pick up and it went to voicemail - I wanted to hang up without leaving a message but the phone had moved to a different screen (I would expect it to have a sensor and block touch input - apparently it doesn't or it failed, and I am left-handed and noticed afterwards that my ear would likely rest on the screen at the top left corner where there's some button), so I fumbled to navigate to the hangup button in time.
Then, while the call window was still open, the phone started ringing. I guess my friend called back (not sure, will confirm later). I could not answer and could not (and was confused to still need to) hang up.
...and then the call kinda doubled and tripled and quadrupled - it sounded like a nightmare.
I took a deep breath (thankfully I was not somewhere with other people around, that would certainly have stressed the hell out of me), systematically backed out of the window and closed everything I could, but phone was still ringing.
After maybe a minute of fumbling, I gave up and held down the power button until the noise stopped.https://source.puri.sm/Librem5/image-builder/-/issues/56Librem 5 disables package recommendations by default2021-02-02T09:54:24ZJonas Smedegaardjonas.smedegaard@puri.smLibrem 5 disables package recommendations by defaultMy Dogwood phone includes file `/etc/apt/apt.conf.d/71-no-recommends` which contains APT options to suppress recommended and suggested packages.
A Debian-based system generally ignoring package recommendations is a broken system.
Pleas...My Dogwood phone includes file `/etc/apt/apt.conf.d/71-no-recommends` which contains APT options to suppress recommended and suggested packages.
A Debian-based system generally ignoring package recommendations is a broken system.
Please don't.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/164Librem 5 disables package recommendations by default2020-08-06T14:26:42ZJonas Smedegaardjonas.smedegaard@puri.smLibrem 5 disables package recommendations by defaultMy Dogwood phone includes file `/etc/apt/apt.conf.d/71-no-recommends` which contains APT options to suppress recommended and suggested packages.
A Debian-based system generally ignoring package recommendations is a broken system.
Pleas...My Dogwood phone includes file `/etc/apt/apt.conf.d/71-no-recommends` which contains APT options to suppress recommended and suggested packages.
A Debian-based system generally ignoring package recommendations is a broken system.
Please don't.https://source.puri.sm/Librem5/debs/libhandy-1/-/issues/1Package for PureOS2020-09-28T16:21:04ZJonas Smedegaardjonas.smedegaard@puri.smPackage for PureOS* [ ] Release fast-tracked to PureOS amber-phone
* [ ] Get accepted into PureOS amber-phone-staging
* [ ] Get auto-built for PureOS amber-phone-staging
* [x] Release sustainably to PureOS byzantium, via Debian
https://software.pureo...* [ ] Release fast-tracked to PureOS amber-phone
* [ ] Get accepted into PureOS amber-phone-staging
* [ ] Get auto-built for PureOS amber-phone-staging
* [x] Release sustainably to PureOS byzantium, via Debian
https://software.pureos.net/search_pkg?term=libhandy-1-0https://source.puri.sm/Librem5/developer.puri.sm/-/issues/163broken link on API Documentation page2020-08-25T14:46:13ZRich Morinbroken link on API Documentation pageThe API Documentation page has a broken link: "Squeekboard HACKING.md guide".
I think it's supposed to go to https://developer.puri.sm/projects/squeekboard/hacking.html,
but I don't understand enough RST magic to make this happen.The API Documentation page has a broken link: "Squeekboard HACKING.md guide".
I think it's supposed to go to https://developer.puri.sm/projects/squeekboard/hacking.html,
but I don't understand enough RST magic to make this happen.David BoddieDavid Boddiehttps://source.puri.sm/Librem5/developer.puri.sm/-/issues/162typos on Sqeekboard "hacking" page2020-08-06T10:54:53ZRich Morintypos on Sqeekboard "hacking" pageHere are some typos from https://developer.puri.sm/projects/squeekboard/hacking.html:
- "Nonwithstanding" should be "Notwithstanding"
- "develpment" should be "development"Here are some typos from https://developer.puri.sm/projects/squeekboard/hacking.html:
- "Nonwithstanding" should be "Notwithstanding"
- "develpment" should be "development"https://source.puri.sm/Librem5/deb-build-jobs/-/issues/61please add libhandy-12020-11-04T13:16:07ZJonas Smedegaardjonas.smedegaard@puri.smplease add libhandy-1Please add `https://source.puri.sm/librem5-apps/libhandy-1` to `jobs.yml` - or grant me write access to this repo so I can do it myself.Please add `https://source.puri.sm/librem5-apps/libhandy-1` to `jobs.yml` - or grant me write access to this repo so I can do it myself.https://source.puri.sm/Librem5/librem5-devkit-tools/-/issues/25librem5-flash-image: drop variant2020-08-05T11:24:18ZGuido Guntherlibrem5-flash-image: drop variantthis is not something for end users and we should always use plain. For development purpose we can use an env var.this is not something for end users and we should always use plain. For development purpose we can use an env var.https://source.puri.sm/Librem5/linux/-/issues/212USB power management instability2021-06-01T01:15:12ZSebastian KrzyszkowiakUSB power management instabilitySometimes, when all the devices connected to the USB2642 hub suspend, allowing the hub itself to suspend as well, the system has troubles with communicating with them after resume afterwards.
I've seen this happening with the SD card:
`...Sometimes, when all the devices connected to the USB2642 hub suspend, allowing the hub itself to suspend as well, the system has troubles with communicating with them after resume afterwards.
I've seen this happening with the SD card:
```
[ 362.796724] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
[ 362.806087] sd 0:0:0:0: [sda] tag#0 Sense Key : 0x6 [current]
[ 362.812057] sd 0:0:0:0: [sda] tag#0 ASC=0x28 ASCQ=0x0
[ 362.817305] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 08 d3 86 e0 00 00 f0 00
[ 362.825162] blk_update_request: I/O error, dev sda, sector 148080352 op 0x0:(READ) flags 0x84700 phys_seg 16 prio class 0
[ 362.837352] sd 0:0:0:0: [sda] tag#0 device offline or changed
[ 362.843373] blk_update_request: I/O error, dev sda, sector 148080592 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
[ 363.125483] sd 0:0:0:0: [sda] tag#0 device offline or changed
[ 363.131543] blk_update_request: I/O error, dev sda, sector 148080608 op 0x0:(READ) flags 0x84700 phys_seg 2 prio class 0
[ 363.143432] sd 0:0:0:0: [sda] tag#0 device offline or changed
[ 363.149332] blk_update_request: I/O error, dev sda, sector 148080848 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 363.161100] sd 0:0:0:0: [sda] tag#0 device offline or changed
[ 363.167020] blk_update_request: I/O error, dev sda, sector 148080352 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 363.228716] sd 0:0:0:0: [sda] tag#0 device offline or changed
[ 363.235058] blk_update_request: I/O error, dev sda, sector 148080352 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 363.247926] sd 0:0:0:0: [sda] tag#0 device offline or changed
[ 363.254232] blk_update_request: I/O error, dev sda, sector 148080352 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 364.124499] sd 0:0:0:0: [sda] tag#0 device offline or changed
[ 364.130540] blk_update_request: I/O error, dev sda, sector 148080352 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 364.277566] sd 0:0:0:0: [sda] tag#0 device offline or changed
[ 364.283732] blk_update_request: I/O error, dev sda, sector 148080352 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 364.384446] sd 0:0:0:0: [sda] tag#0 device offline or changed
[ 364.392011] blk_update_request: I/O error, dev sda, sector 148080352 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 364.479720] sd 0:0:0:0: [sda] tag#0 device offline or changed
[ 364.578303] sd 0:0:0:0: [sda] tag#0 device offline or changed
[ 364.674929] sd 0:0:0:0: [sda] tag#0 device offline or changed
[ 364.775344] sd 0:0:0:0: [sda] tag#0 device offline or changed
[ 364.879329] sd 0:0:0:0: [sda] tag#0 device offline or changed
[ 364.976736] sd 0:0:0:0: [sda] tag#0 device offline or changed
[ 365.076756] sd 0:0:0:0: [sda] tag#0 device offline or changed
```
and with the modem. It gets reset though, giving it a chance to recover:
```
Aug 03 14:39:53 pureos kernel: usb 1-1.2: reset high-speed USB device number 4 using xhci-hcd
Aug 03 14:39:53 pureos kernel: usb 1-1.2: USB disconnect, device number 4
Aug 03 14:39:53 pureos kernel: qmi_wwan 1-1.2:1.4: Tx URB error: -19
Aug 03 14:39:53 pureos kernel: option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Aug 03 14:39:53 pureos kernel: option 1-1.2:1.0: device disconnected
Aug 03 14:39:53 pureos kernel: option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Aug 03 14:39:53 pureos kernel: option 1-1.2:1.1: device disconnected
Aug 03 14:39:53 pureos kernel: option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
Aug 03 14:39:53 pureos kernel: option 1-1.2:1.2: device disconnected
Aug 03 14:39:53 pureos kernel: option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
Aug 03 14:39:53 pureos kernel: option 1-1.2:1.3: device disconnected
Aug 03 14:39:53 pureos kernel: qmi_wwan 1-1.2:1.4 wwan0: unregister 'qmi_wwan' usb-xhci-hcd.4.auto-1.2, WWAN/QMI device
Aug 03 14:39:53 pureos kernel: usb 1-1.2: new high-speed USB device number 5 using xhci-hcd
Aug 03 14:39:53 pureos kernel: usb 1-1.2: New USB device found, idVendor=2020, idProduct=2060, bcdDevice= 0.00
Aug 03 14:39:53 pureos kernel: usb 1-1.2: New USB device strings: Mfr=3, Product=2, SerialNumber=4
Aug 03 14:39:53 pureos kernel: usb 1-1.2: Product: Qualcomm CDMA Technologies MSM
Aug 03 14:39:53 pureos kernel: usb 1-1.2: Manufacturer: Qualcomm, Incorporated
Aug 03 14:39:54 pureos kernel: option 1-1.2:1.0: GSM modem (1-port) converter detected
Aug 03 14:39:54 pureos kernel: usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB0
Aug 03 14:39:54 pureos kernel: option 1-1.2:1.1: GSM modem (1-port) converter detected
Aug 03 14:39:54 pureos kernel: usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB1
Aug 03 14:39:54 pureos kernel: option 1-1.2:1.2: GSM modem (1-port) converter detected
Aug 03 14:39:54 pureos kernel: usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB2
Aug 03 14:39:54 pureos kernel: option 1-1.2:1.3: GSM modem (1-port) converter detected
Aug 03 14:39:54 pureos kernel: usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB3
Aug 03 14:39:54 pureos kernel: qmi_wwan 1-1.2:1.4: cdc-wdm0: USB WDM device
```
However, when I disable the periodic signal strength polling in ModemManager it seems like it doesn't reset anymore and just stays in a bad state until MM actually tries to communicate with the modem.
So far I haven't seen it happening when either the modem or the SD card wasn't allowed to suspend; I'll keep testing.https://source.puri.sm/Librem5/linux/-/issues/211Flashlight support2020-10-07T08:33:30ZGuido GuntherFlashlight supportThere's a driver for `lm3560` in media/.
Needed for camera flash as well as torch.There's a driver for `lm3560` in media/.
Needed for camera flash as well as torch.https://source.puri.sm/Librem5/linux/-/issues/210etnaviv: Don't hard code runtime pm value2022-01-05T11:14:51ZGuido Guntheretnaviv: Don't hard code runtime pm valueNo idea why i didn't do this via udev but we should https://source.puri.sm/Librem5/linux-next/-/commit/10a99e20d7778ede8b8a6403f5bdad1392925fbf - i'll move that over to librem5-base and do a MR here to drop it once rolled out.No idea why i didn't do this via udev but we should https://source.puri.sm/Librem5/linux-next/-/commit/10a99e20d7778ede8b8a6403f5bdad1392925fbf - i'll move that over to librem5-base and do a MR here to drop it once rolled out.