Librem5 issueshttps://source.puri.sm/groups/Librem5/-/issues2019-03-26T12:15:24Zhttps://source.puri.sm/Librem5/image-builder/-/issues/27Mass storage mode on USB C port2019-03-26T12:15:24ZAngus Ainslieangus.ainslie@puri.smMass storage mode on USB C portHaving mass storage mode on the USB C port would give us direct access to the eMMC for u-boot/M4/rootfs updatesHaving mass storage mode on the USB C port would give us direct access to the eMMC for u-boot/M4/rootfs updateshttps://source.puri.sm/Librem5/image-builder/-/issues/26Add ethernet to USB C port2019-03-26T12:05:18ZAngus Ainslieangus.ainslie@puri.smAdd ethernet to USB C portGadget mode is working on the USB C port so we could add ethernetGadget mode is working on the USB C port so we could add ethernethttps://source.puri.sm/Librem5/uboot-imx/-/issues/3Load M4 firmware from boot image2019-01-09T10:04:19ZGhost UserLoad M4 firmware from boot imageI've patched my uboot-imx and imx-mkimage to load the M4 firmware from the boot image.
The main benefit is it allows booting u-boot over USB if the eMMC is wiped.
u-boot patches: https://source.puri.sm/Jookia/uboot-imx/commits/librem_...I've patched my uboot-imx and imx-mkimage to load the M4 firmware from the boot image.
The main benefit is it allows booting u-boot over USB if the eMMC is wiped.
u-boot patches: https://source.puri.sm/Jookia/uboot-imx/commits/librem_m4
mkimage patches: https://source.puri.sm/Jookia/imx-mkimage/commits/librem-devkit
Instructions on use: https://source.puri.sm/Jookia/imx-mkimage/wikis/homehttps://source.puri.sm/Librem5/OS-issues/-/issues/13Handle fsck failures gracefully2019-11-25T08:35:32ZDorota CzaplejewiczHandle fsck failures gracefullyFsck failure can cause the system to drop the user into the emergency shell. Example while testing:
```
[FAILED] Failed to start File System Check o…03f04-af81-46c6-817c-e788adfa1d51.
See 'systemctl status "systemd-fsck@dev…\x2de788adfa...Fsck failure can cause the system to drop the user into the emergency shell. Example while testing:
```
[FAILED] Failed to start File System Check o…03f04-af81-46c6-817c-e788adfa1d51.
See 'systemctl status "systemd-fsck@dev…\x2de788adfa1d51.service"' for details.
[DEPEND] Dependency failed for /boot.
[DEPEND] Dependency failed for Local File Systems.
[ OK ] Reached target Sound Card.
[...]
[ OK ] Reached target Network.
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemcGive root password for maintenance
(or press Control-D to continue):
```
This needs to be handled gracefully on the phone, either by:
- giving the user some sort of a touch-based shell, or
- trying to repair (except for a data partition?), or
- restoring some known working image, or
- noisily telling the user to find a keyboard and deal with itArno BauernoppelArno Bauernoppelhttps://source.puri.sm/Librem5/OS-issues/-/issues/12Crash in the wifi stack2023-05-03T16:56:01ZFabrice DesréCrash in the wifi stackNot sure if that's the right place to report this issue, but I got this crash in wpa_supplicant:
```
[ 14.377404] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 14.377548] rsi_91x: ===> Interface UP <===
[ 14.380304] IPv6: ...Not sure if that's the right place to report this issue, but I got this crash in wpa_supplicant:
```
[ 14.377404] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 14.377548] rsi_91x: ===> Interface UP <===
[ 14.380304] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 14.382107] rsi_91x: ===> Interface DOWN <===
[ 14.383350] rsi_91x: ===> Interface UP <===
[ 14.383527] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 14.514619] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 14.518723] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 14.563852] systemd-journald[1209]: File /var/log/journal/63404380c564418ea450ae1e9c33565b/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[ 14.848121] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 15.043718] imx-sdma 30bd0000.sdma: load_address = 685
[ 15.043725] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 15.043729] imx-sdma 30bd0000.sdma: shp_addr = 0x308b00a0
[ 15.043732] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 15.043735] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000400
[ 15.043738] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 15.168250] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 15.487967] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 15.491849] imx-sdma 30bd0000.sdma: load_address = 749
[ 15.491856] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 15.491859] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 15.491862] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 15.491865] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 15.491868] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 15.808338] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 15.914723] imx-sdma 30bd0000.sdma: load_address = 685
[ 15.914732] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 15.914735] imx-sdma 30bd0000.sdma: shp_addr = 0x308b00a0
[ 15.914738] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 15.914742] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000400
[ 15.914745] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 16.127937] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 16.447777] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 16.629389] imx-sdma 30bd0000.sdma: load_address = 749
[ 16.629398] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 16.629401] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 16.629404] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 16.629407] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 16.629410] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 16.768979] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 17.075017] imx-sdma 30bd0000.sdma: sdma_prep_dma_cyclic channel: 1
[ 17.075027] imx-sdma 30bd0000.sdma: load_address = 749
[ 17.075033] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 17.075038] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 17.075042] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 17.075047] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 17.075051] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 17.075065] imx-sdma 30bd0000.sdma: entry 0: count: 2204 dma: 0xec180000 intr
[ 17.075071] imx-sdma 30bd0000.sdma: entry 1: count: 2204 dma: 0xec18089c intr
[ 17.075077] imx-sdma 30bd0000.sdma: entry 2: count: 2204 dma: 0xec181138 intr
[ 17.075083] imx-sdma 30bd0000.sdma: entry 3: count: 2204 dma: 0xec1819d4 wrap intr
[ 17.077780] imx-sdma 30bd0000.sdma: load_address = 685
[ 17.077786] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 17.077789] imx-sdma 30bd0000.sdma: shp_addr = 0x308b00a0
[ 17.077792] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 17.077795] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000400
[ 17.077798] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 17.087860] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 17.414001] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 17.522024] imx-sdma 30bd0000.sdma: sdma_prep_dma_cyclic channel: 2
[ 17.522033] imx-sdma 30bd0000.sdma: load_address = 685
[ 17.522036] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 17.522040] imx-sdma 30bd0000.sdma: shp_addr = 0x308b00a0
[ 17.522043] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 17.522046] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000400
[ 17.522049] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 17.522060] imx-sdma 30bd0000.sdma: entry 0: count: 2204 dma: 0xec200000 intr
[ 17.522065] imx-sdma 30bd0000.sdma: entry 1: count: 2204 dma: 0xec20089c intr
[ 17.522068] imx-sdma 30bd0000.sdma: entry 2: count: 2204 dma: 0xec201138 intr
[ 17.522072] imx-sdma 30bd0000.sdma: entry 3: count: 2204 dma: 0xec2019d4 wrap intr
[ 17.562311] imx-sdma 30bd0000.sdma: load_address = 749
[ 17.562319] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 17.562322] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 17.562325] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 17.562328] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 17.562331] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 17.727895] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 17.987421] imx-sdma 30bd0000.sdma: load_address = 749
[ 17.987429] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 17.987432] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 17.987436] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 17.987439] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 17.987442] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 18.048171] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 18.367875] rsi_91x: rsi_prepare_mgmt_desc: Failed to get vif
[ 18.410881] imx-sdma 30bd0000.sdma: load_address = 685
[ 18.410889] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 18.410893] imx-sdma 30bd0000.sdma: shp_addr = 0x308b00a0
[ 18.410896] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 18.410899] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000400
[ 18.410902] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 18.847953] imx-sdma 30bd0000.sdma: sdma_prep_dma_cyclic channel: 2
[ 18.847962] imx-sdma 30bd0000.sdma: load_address = 685
[ 18.847965] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 18.847968] imx-sdma 30bd0000.sdma: shp_addr = 0x308b00a0
[ 18.847971] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 18.847974] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000400
[ 18.847977] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 18.847989] imx-sdma 30bd0000.sdma: entry 0: count: 2204 dma: 0xec200000 intr
[ 18.847993] imx-sdma 30bd0000.sdma: entry 1: count: 2204 dma: 0xec20089c intr
[ 18.847997] imx-sdma 30bd0000.sdma: entry 2: count: 2204 dma: 0xec201138 intr
[ 18.848001] imx-sdma 30bd0000.sdma: entry 3: count: 2204 dma: 0xec2019d4 wrap intr
[ 18.862405] imx-sdma 30bd0000.sdma: load_address = 749
[ 18.862413] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 18.862416] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 18.862419] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 18.862423] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 18.862426] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 19.300079] imx-sdma 30bd0000.sdma: load_address = 749
[ 19.300087] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 19.300090] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 19.300094] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 19.300097] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 19.300100] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 19.716174] imx-sdma 30bd0000.sdma: load_address = 749
[ 19.716182] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 19.716185] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 19.716189] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 19.716192] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 19.716195] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 20.132651] imx-sdma 30bd0000.sdma: load_address = 749
[ 20.132658] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 20.132661] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 20.132664] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 20.132668] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 20.132671] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 20.550044] imx-sdma 30bd0000.sdma: load_address = 749
[ 20.550053] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 20.550058] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 20.550063] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 20.550067] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 20.550072] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 21.112810] imx-sdma 30bd0000.sdma: load_address = 749
[ 21.112819] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 21.112824] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 21.112829] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 21.112834] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 21.112838] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 21.544957] imx-sdma 30bd0000.sdma: load_address = 749
[ 21.544967] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 21.544972] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 21.544977] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 21.544981] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 21.544986] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 22.263948] imx-sdma 30bd0000.sdma: load_address = 749
[ 22.263956] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 22.263962] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 22.263966] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 22.263971] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 22.263976] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 22.755013] imx-sdma 30bd0000.sdma: load_address = 749
[ 22.755020] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 22.755024] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 22.755027] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 22.755030] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 22.755033] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 23.374749] imx-sdma 30bd0000.sdma: load_address = 749
[ 23.374758] imx-sdma 30bd0000.sdma: wml = 0x0000000c
[ 23.374761] imx-sdma 30bd0000.sdma: shp_addr = 0x308b0020
[ 23.374764] imx-sdma 30bd0000.sdma: per_addr = 0x00000000
[ 23.374768] imx-sdma 30bd0000.sdma: event_mask0 = 0x00000800
[ 23.374771] imx-sdma 30bd0000.sdma: event_mask1 = 0x00000000
[ 24.902488] rsi_91x: ===> Interface DOWN <===
[ 24.904758] rsi_91x: ===> Interface UP <===
[ 24.904876] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 37.262605] wlan0: authenticate with b0:93:5b:c7:60:79
[ 37.262735] wlan0: send auth to b0:93:5b:c7:60:79 (try 1/3)
[ 37.266741] wlan0: authenticated
[ 37.271261] wlan0: associate with b0:93:5b:c7:60:79 (try 1/3)
[ 37.275740] wlan0: RX AssocResp from b0:93:5b:c7:60:79 (capab=0x1411 status=0 aid=6)
[ 37.277010] wlan0: associated
[ 37.293757] wlan0: Limiting TX power to 27 (30 - 3) dBm as advertised by b0:93:5b:c7:60:79
[ 37.302110] rsi_91x: EAPOL 4 confirm
[ 37.311680] rsi_91x: rsi_hal_key_config: Cipher 0xfac04 key_type: 1 key_len: 16
[ 37.311697] rsi_91x: rsi_mac80211_set_key: RSI set_key
[ 37.314066] rsi_91x: rsi_hal_key_config: Cipher 0xfac04 key_type: 2 key_len: 16
[ 37.314081] rsi_91x: rsi_mac80211_set_key: RSI set_key
[ 37.314356] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 56.239938] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000d0
[ 56.248948] Mem abort info:
[ 56.251859] ESR = 0x96000004
[ 56.254912] Exception class = DABT (current EL), IL = 32 bits
[ 56.260944] SET = 0, FnV = 0
[ 56.264108] EA = 0, S1PTW = 0
[ 56.267307] Data abort info:
[ 56.270185] ISV = 0, ISS = 0x00000004
[ 56.274131] CM = 0, WnR = 0
[ 56.277107] user pgtable: 4k pages, 48-bit VAs, pgdp = 000000002d23c7d9
[ 56.283886] [00000000000000d0] pgd=0000000000000000
[ 56.288880] Internal error: Oops: 96000004 [#1] PREEMPT SMP
[ 56.294451] Modules linked in: aes_ce_ccm bnep qmi_wwan cdc_wdm usbnet tcpci tcpm roles typec bq25890_charger rtc_m41t80 st_gyro_spi st_sensors_spi st_gyro_i2c ov5640 st_sensors_i2c st_gyro st_sensors xhci_plat_hcd xhci_hcd usbcore usb_f_acm u_serial dwc3 ulpi rsi_sdio rsi_91x bluetooth aes_ce_blk crypto_simd crc32_ce crct10dif_ce ghash_ce sha2_ce sha1_ce snd_soc_simple_card snd_soc_simple_card_utils dwc3_of_simple i2c_imx spi_imx imx_sdma imx2_wdt g_serial libcomposite udc_core ip_tables x_tables ipv6
[ 56.338995] CPU: 2 PID: 2333 Comm: wpa_supplicant Not tainted 4.18.11-g59f358aa #1
[ 56.346561] Hardware name: Purism Librem 5 devkit (DT)
[ 56.351697] pstate: 20000005 (nzCv daif -PAN -UAO)
[ 56.356503] pc : rsi_send_probe_request+0x16c/0x328 [rsi_91x]
[ 56.362256] lr : rsi_send_probe_request+0x158/0x328 [rsi_91x]
[ 56.367998] sp : ffff8000a20d37e0
[ 56.371310] x29: ffff8000a20d37e0 x28: ffff80008db52db8
[ 56.376622] x27: ffff8000a783f0c8 x26: ffff80008db52db8
[ 56.381933] x25: ffff8000a783e3d8 x24: 0000000000000000
[ 56.387244] x23: 0000000000000079 x22: ffff800086d8ac40
[ 56.392555] x21: 0000000000000001 x20: ffff8000a783e000
[ 56.397866] x19: 000000000000000d x18: ffff000008b76000
[ 56.403177] x17: 0000000000000000 x16: 0000000000000000
[ 56.408488] x15: ffff800086d8ac00 x14: 0100000000000000
[ 56.413800] x13: 00000000ff01006e x12: 1a2d6c6048302418
[ 56.419110] x11: 120c080100000000 x10: 0000000000000100
[ 56.424422] x9 : 0000000000000000 x8 : 0000ff01006e1a2d
[ 56.429733] x7 : 6c60483004322418 x6 : ffff8000a783e42a
[ 56.435043] x5 : ffff8000abf85e30 x4 : 0000000000000008
[ 56.440354] x3 : 0000000000000000 x2 : ffffffffffffffca
[ 56.445665] x1 : ffff800086d8ae4a x0 : ffff8000a783e3d8
[ 56.450978] Process wpa_supplicant (pid: 2333, stack limit = 0x000000005a0a93a7)
[ 56.458370] Call trace:
[ 56.460824] rsi_send_probe_request+0x16c/0x328 [rsi_91x]
[ 56.466228] rsi_mac80211_hw_scan_start+0x168/0x200 [rsi_91x]
[ 56.471978] __ieee80211_start_scan+0x260/0x818
[ 56.476507] ieee80211_request_scan+0x34/0x58
[ 56.480864] ieee80211_scan+0x58/0xd0
[ 56.484527] nl80211_trigger_scan+0x5ac/0x820
[ 56.488883] genl_family_rcv_msg+0x248/0x368
[ 56.493151] genl_rcv_msg+0x60/0xa8
[ 56.496638] netlink_rcv_skb+0xf0/0x138
[ 56.500471] genl_rcv+0x3c/0x50
[ 56.503610] netlink_unicast+0x198/0x218
[ 56.507531] netlink_sendmsg+0x274/0x340
[ 56.511453] sock_sendmsg+0x34/0x50
[ 56.514939] ___sys_sendmsg+0x28c/0x2b8
[ 56.518773] __sys_sendmsg+0x78/0xd0
[ 56.522346] sys_sendmsg+0x38/0x48
[ 56.525749] el0_svc_naked+0x30/0x34
[ 56.529324] Code: 54fffba1 110062f7 7101e2ff 540002c9 (f9406b00)
[ 56.535416] ---[ end trace 8d185367b2287175 ]---
```https://source.puri.sm/Librem5/image-builder/-/issues/25Provide checksum and size of uncompressed image2019-06-13T09:37:03ZGuido GuntherProvide checksum and size of uncompressed imageFor the scripts fetching directly form jenkins it would be nice to have the checksum and size of the uncompressed image so it can be validated before flashing it to the device.For the scripts fetching directly form jenkins it would be nice to have the checksum and size of the uncompressed image so it can be validated before flashing it to the device.https://source.puri.sm/Librem5/OS-issues/-/issues/11YongXing LCD panel not detected on HDMI2019-01-14T10:24:37ZDorota CzaplejewiczYongXing LCD panel not detected on HDMIHDMI stubbornly doesn't work for some on the team for an unknown reason. Hardware damage is not ruled out.
Symptom: the board boots, but nothing is ever shown on the screen, and it doesn't go out of standby mode.
Setup: a no-name Mini-...HDMI stubbornly doesn't work for some on the team for an unknown reason. Hardware damage is not ruled out.
Symptom: the board boots, but nothing is ever shown on the screen, and it doesn't go out of standby mode.
Setup: a no-name Mini-HDMI → HDMI dongle (<4cm with the plug, competes for space with the USB plug), a HDMI → $foo cable, a display
Displays:
- a 1080x1920 (portrait), HDMI YongXing LCD panel (attached data from this one)
- DELL E207WFP 1680x1050 DVI
The cable plug/unplug events look like this:
```
[ 4201.094069] [drm:drm_sysfs_hotplug_event] generating hotplug event
[ 4201.118251] [drm:drm_add_display_info] HDMI-A-1: No deep color support on this HDMI sink.
[ 4201.118272] [drm:drm_add_display_info] HDMI-A-1: No deep color support on this HDMI sink.
[ 4201.118463] [drm:drm_mode_object_get] OBJ ID: 42 (2)
[ 4201.118487] [drm:drm_mode_object_get] OBJ ID: 46 (1)
[ 4201.118496] [drm:drm_mode_object_get] OBJ ID: 42 (3)
[ 4201.118500] [drm:drm_mode_object_get] OBJ ID: 42 (4)
[ 4201.118518] [drm:drm_mode_object_put] OBJ ID: 42 (5)
[ 4201.118523] [drm:drm_mode_object_put] OBJ ID: 42 (4)
[ 4201.118528] [drm:drm_mode_object_put] OBJ ID: 47 (1)
[ 4201.118534] [drm:drm_mode_object_put] OBJ ID: 46 (2)
[ 4201.118539] [drm] HDMI/DP Cable Plug In
[ 4217.822047] [drm:drm_sysfs_hotplug_event] generating hotplug event
[ 4217.822256] [drm:drm_mode_object_put] OBJ ID: 43 (1)
[ 4217.822271] [drm:drm_mode_object_put] OBJ ID: 42 (3)
[ 4217.822330] [drm] HDMI/DP Cable Plug Out
```
modetest output:
```
trying to open device 'imx-drm'...done
Connectors:
id encoder status name size (mm) modes encoders
42 0 disconnected HDMI-A-1 0x0 0 41
props:
1 EDID:
flags: immutable blob
blobs:
value:
2 DPMS:
flags: enum
enums: On=0 Standby=1 Suspend=2 Off=3
value: 0
5 link-status:
flags: enum
enums: Good=0 Bad=1
value: 0
6 non-desktop:
flags: immutable range
values: 0 1
value: 0
19 CRTC_ID:
flags: object
value: 0
```
fbset output:
```
root@pureos:~# fbset "640x480 60Hz 32bit (GTF)"
ioctl FBIOPUT_VSCREENINFO: Invalid argument
```
and, most confusingly:
```
root@pureos:~# cat /sys/class/drm/card1-HDMI-A-1/status
connected
root@pureos:~# cat /sys/class/drm/card1-HDMI-A-1/modes
root@pureos:~#
```
TODO: run with `drm.debug=0x2f` on the kernel command linehttps://source.puri.sm/Librem5/developer.puri.sm/-/issues/68Add LED description2018-12-31T17:10:18ZDorota CzaplejewiczAdd LED descriptionThe programmable LED needs to be descibed in the docs:
It can be controlled with:
```
root@pureos:/# echo 200 > /sys/class/leds/LED\ 1/brightness
```
where 0 is "off", and any value between 1 and 255 is "on" with the default device tr...The programmable LED needs to be descibed in the docs:
It can be controlled with:
```
root@pureos:/# echo 200 > /sys/class/leds/LED\ 1/brightness
```
where 0 is "off", and any value between 1 and 255 is "on" with the default device tree. The LED is driven by a PWM shared with the haptic motor, so only one can be gradual at a time, decided by device tree.
* * *
Eric about the 3 charge controller LEDs without a battery plugged in:
> the two LEDs that were on are one that is on VBAT_REG (meaning VBAT_REG is likely being properly regulated), and PG# (Power Good). The third LED is attached to the charge controller's STAT pin, which would indicate whether or not a battery is being charged (can blink @ ~11Hz or be off if no battery is present, basically meaningless without a battery)
> if you are powering from a battery but are _not_ supplying VBUS, then you will just see the VBAT_REG LED on, the PG# and STAT ones will be off (unless you _are_ supplying VBUS)
VBUS is USB.
> for the LEDs, best thing to do is look at the schematic and charge controller's datasheet to know what it actually meanshttps://source.puri.sm/Librem5/OS-issues/-/issues/10UART connection blocks USB console2019-01-04T18:43:17ZDorota CzaplejewiczUART connection blocks USB consoleWhen booting with UART connected, the console from the USB device doesn't do anything.
This should be fixed if possible (allocate a separate console?), and if not, documented somewhere near UART/USB console to prevent user confusion.When booting with UART connected, the console from the USB device doesn't do anything.
This should be fixed if possible (allocate a separate console?), and if not, documented somewhere near UART/USB console to prevent user confusion.https://source.puri.sm/Librem5/OS-issues/-/issues/9Point to the use of a regular image2019-12-08T11:48:36ZDorota CzaplejewiczPoint to the use of a regular imageThere should be one image we encourage everyone to use. The following needs to be adjusted:
- adjust the build scripts
- [x] image build (https://source.puri.sm/Librem5/image-builder/merge_requests/57)
- [x] kernel build (https://...There should be one image we encourage everyone to use. The following needs to be adjusted:
- adjust the build scripts
- [x] image build (https://source.puri.sm/Librem5/image-builder/merge_requests/57)
- [x] kernel build (https://source.puri.sm/Librem5/image-builder/merge_requests/59)
- [x] u-boot build for uuu flashing
- [x] u-boot build for the image
- adjust build jobs
- [x] image build (https://source.puri.sm/Librem5/image-builder/merge_requests/51 , etc)
- [x] kernel build (rename and branch switch) (https://source.puri.sm/Librem5/image-builder/merge_requests/70)
- [x] u-boot build for uuu flashing
- [ ] u-boot build for the image
- [x] the [download scripts](https://source.puri.sm/Librem5/librem5-devkit-tools/) (image URLs) (https://source.puri.sm/Librem5/librem5-devkit-tools/merge_requests/12)
- [x] the documentation when referencing the scripts https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/130
- [ ] the documentation should explain differences between images if we have more than one (we can hold this off until we support more than one distribution, so ticking this off for the moment)
- [ ] the Jenkins jobs should be removed or stopped if an image is no longer used
- [x] image
- [x] kernel
- [x] uboot
- [ ] prune unused jobs after a couple of days (we want to keep the devkit-test related ones although having them disabled)
- [ ] image upload scripts for blessed image (to CDN)
https://source.puri.sm/Librem5/OS-issues/-/issues/8flash-kernel support2019-03-08T18:09:08ZGuido Guntherflash-kernel supportFor https://source.puri.sm/Librem5/image-builder/issues/24 as well as https://source.puri.sm/Librem5/librem5-base/merge_requests/9 we want proper flash-kernel support to
* configure the kernel command line
* use an initramfsFor https://source.puri.sm/Librem5/image-builder/issues/24 as well as https://source.puri.sm/Librem5/librem5-base/merge_requests/9 we want proper flash-kernel support to
* configure the kernel command line
* use an initramfsDorota CzaplejewiczDorota Czaplejewiczhttps://source.puri.sm/Librem5/image-builder/-/issues/24Use an initramfs on the devkit2019-03-08T18:20:01ZGuido GuntherUse an initramfs on the devkitThis allows for bootsplash and growrootfsThis allows for bootsplash and growrootfsDorota CzaplejewiczDorota Czaplejewiczhttps://source.puri.sm/Librem5/image-builder/-/issues/23Integrate arm64 kernels like the armhf ones2018-12-29T15:51:55ZGuido GuntherIntegrate arm64 kernels like the armhf onesOn armhf/imx6/nitrogen kernel updates happen automatically via
* https://source.puri.sm/Librem5/image-builder/blob/master/data/update-zImage-link
* https://source.puri.sm/Librem5/image-builder/blob/master/root.sh#L43
This was done di...On armhf/imx6/nitrogen kernel updates happen automatically via
* https://source.puri.sm/Librem5/image-builder/blob/master/data/update-zImage-link
* https://source.puri.sm/Librem5/image-builder/blob/master/root.sh#L43
This was done differently for arm64/devkit:
* https://source.puri.sm/Librem5/image-builder/blob/master/root.sh#L52
The `/etc/kernel/postinst.d/` logic should be adjusted to handle arm64/devkit as well.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/67Add instructions for compiling devkit kernel2019-02-12T22:13:45ZBob HamAdd instructions for compiling devkit kernelFrom Matrix:
```
mdz0: I just compiled a kernel package using https://source.puri.sm/Librem5/linux-emcraft by adjusting the instructions here https://source.puri.sm/Librem5/image-builder/blob/master/build/kernel.txt
08:49
sudo apt-get i...From Matrix:
```
mdz0: I just compiled a kernel package using https://source.puri.sm/Librem5/linux-emcraft by adjusting the instructions here https://source.puri.sm/Librem5/image-builder/blob/master/build/kernel.txt
08:49
sudo apt-get install gcc-aarch64-linux-gnu build-essential crossbuild-essential-arm64
cp arch/arm64/configs/librem5-evk_defconfig .config
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- menuconfig
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- deb-pkg
```David BoddieDavid Boddiehttps://source.puri.sm/Librem5/OS-issues/-/issues/7NetworkManager becomes unresponsive after connecting to wifi.2018-12-23T10:28:21ZJosh FlemingNetworkManager becomes unresponsive after connecting to wifi.# What problem did you encounter
NetworkManager (or wpa_supplicant) Becomes unresponsive after connecting to wifi.
## What is the actual behaviour?
After connecting to wifi with nmtui, commands like: `ip addr` that depend on NetworkMana...# What problem did you encounter
NetworkManager (or wpa_supplicant) Becomes unresponsive after connecting to wifi.
## What is the actual behaviour?
After connecting to wifi with nmtui, commands like: `ip addr` that depend on NetworkManager sometimes don't respond. Also the wifi connection doesn't seem to actually connect after reboot.
## What is the expected behaviour?
After connecting wifi, connections should work after reboot, and `ip addr` and other commands should print expected results.
## How to reproduce
* Run through the steps to flash the main image here: https://developer.puri.sm/Librem5/Development_Environment/Boards/imx8.html
* Once the flash is complete reboot with ethernet, HDMI, and USB attached
* Connect to the device over USB with picocom as documented in the above linked documentation.
* Test `ip addr` get an expected response, also ping a known domain to test connectivity. Everything looks good at this point.
* Update with `apt update` then `apt upgrade`
* Reboot with reboot button
* Once again Connect over USB and test `ip addr` get an expected response, also ping a known domain to test connectivity. Everything still looks good.
* Use `nmtui` to connect to a wifi access point.
* Reboot with reboot button
* Try `ip addr` no response given, in fact ctrl-c won't quit the process.
* Reboot with reboot button
* Try `nmcli d s` devices are listed wifi is shown as disconnected
* `nmcli d wifi list` won't list any access points
* `nmcli d wifi rescan` returns `Error: Scanning not allowed while already scanning.`
* `nmtui` shows no wifi access points either.
* Pinging a domain returns no response and ctrl-c will not exit the process.
* Reboot with reboot button.
* Once the Reboot button is pressed the the GUI shell leaves the screen, but does not reboot. The three lights above the battery are all solid green.
* Unplug / Remove battery & Replug USB
* Try `nmcli d s` Response: `Error: Could not create NMClient object: Timeout was reached.`
* Run `systemctl status NetworkManager` results (included below) include a warning about "sup-iface" though the full warning is cut off
* Run `journalctl -xe` results (included below) include errors related to NetworkManager and wpa_supplicant
* At this point if I reboot I still have network access through ethernet, upon reboot I can look at nmtui which intermittently doesn't load at all or loats with no wifi access points, or loads claiming it's connected to my access point.
* With ethernet disconnected, if I ping an ip address it responds as unreachable, even when nmtui claims it's connected to an access point.
* Also booting with ethernet disconnected takes much longer than without. (at least once I've tried to connect to an access point) With ethernet connected The boot process is within 5-10 seconds until the GUI shows on the monitor. With ethernet disconnected, the boot process sits with the 4 penguins on the screen for just over 2 minutes. I'm assuming this is while it's attempting to find a network.
# What hardware are you running on?
Librem5 devkit
# Relevant OS information
## Which kernel are you using?
`Linux pureos 4.18.11-g59f358aa #1 SMP PREEMPT Tue Dec 18 13:54:35 PST 2018 aarch64 GNU/Linux`
## Which OS are you using?
``
PRETTY_NAME="Debian GNU/Linux buster/sid"
NAME="Debian GNU/Linux"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
``
## Any other information that may be helpful?
Depending on the nature of the issue, you may consider adding the output of:
* lsblk (for mounting issues)
* lsusb (for usb attachment issues)
```
# systemctl status NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor p
Active: active (running) since Sun 2018-12-23 03:02:48 UTC; 2min 25s ago
Docs: man:NetworkManager(8)
Main PID: 2339 (NetworkManager)
Tasks: 3 (limit: 3216)
Memory: 10.4M
CGroup: /system.slice/NetworkManager.service
└─2339 /usr/sbin/NetworkManager --no-daemon
Dec 23 03:03:12 pureos dhclient[2793]: bound to 192.168.43.3 -- renewal in 1554
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.4146] policy: s
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.4178] device (w
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.4273] manager:
Dec 23 03:03:15 pureos NetworkManager[2339]: <info> [1545534195.5804] supplican
Dec 23 03:03:15 pureos NetworkManager[2339]: <info> [1545534195.5806] device (w
Dec 23 03:03:15 pureos NetworkManager[2339]: <warn> [1545534195.5954] sup-iface
Dec 23 03:03:15 pureos NetworkManager[2339]: <info> [1545534195.5964] device (w
Dec 23 03:03:15 pureos NetworkManager[2339]: <info> [1545534195.6012] dhcp4 (wl
Dec 23 03:03:15 pureos NetworkManager[2339]: <info> [1545534195.6013] dhcp4 (wl
```
* any journalctl logs that look suspicious
```
# journalctl -xe
-- Unit UNIT has finished starting up.
--
-- The start-up result is RESULT.
Dec 23 03:03:09 pureos systemd[2764]: Startup finished in 164ms.
-- Subject: User manager start-up is now complete
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The user manager instance for user 0 has been started. All services queued
-- for starting have been started. Note that other services might still be start
-- up or be started at any later time.
--
-- Startup of the manager took 164551 microseconds.
Dec 23 03:03:10 pureos login[2776]: ROOT LOGIN on '/dev/ttyGS0'
Dec 23 03:03:10 pureos systemd[2764]: Started D-Bus User Message Bus.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is RESULT.
Dec 23 03:03:10 pureos wpa_supplicant[2328]: wlan0: CTRL-EVENT-REGDOM-CHANGE ini
Dec 23 03:03:11 pureos wpa_supplicant[2328]: wlan0: SME: Trying to authenticate
Dec 23 03:03:11 pureos kernel: wlan0: authenticate with 02:1a:11:f7:78:9b
Dec 23 03:03:11 pureos kernel: wlan0: send auth to 02:1a:11:f7:78:9b (try 1/3)
Dec 23 03:03:11 pureos wpa_supplicant[2328]: wlan0: Trying to associate with 02:
Dec 23 03:03:11 pureos kernel: wlan0: authenticated
Dec 23 03:03:11 pureos kernel: wlan0: associate with 02:1a:11:f7:78:9b (try 1/3)
Dec 23 03:03:11 pureos wpa_supplicant[2328]: wlan0: Associated with 02:1a:11:f7:
Dec 23 03:03:11 pureos wpa_supplicant[2328]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPD
Dec 23 03:03:11 pureos kernel: wlan0: RX AssocResp from 02:1a:11:f7:78:9b (capab
Dec 23 03:03:11 pureos kernel: wlan0: associated
Dec 23 03:03:11 pureos NetworkManager[2339]: <info> [1545534191.8545] device (w
Dec 23 03:03:11 pureos NetworkManager[2339]: <info> [1545534191.8628] device (w
Dec 23 03:03:11 pureos kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as ad
Dec 23 03:03:11 pureos wpa_supplicant[2328]: wlan0: CTRL-EVENT-SIGNAL-CHANGE abo
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.0038] device (w
Dec 23 03:03:12 pureos kernel: rsi_91x: EAPOL 4 confirm
Dec 23 03:03:12 pureos kernel: rsi_91x: rsi_hal_key_config: Cipher 0xfac04 key_t
Dec 23 03:03:12 pureos kernel: rsi_91x: rsi_mac80211_set_key: RSI set_key
Dec 23 03:03:12 pureos wpa_supplicant[2328]: wlan0: WPA: Key negotiation complet
Dec 23 03:03:12 pureos wpa_supplicant[2328]: wlan0: CTRL-EVENT-CONNECTED - Conne
Dec 23 03:03:12 pureos systemd-networkd[2267]: wlan0: Gained carrier
Dec 23 03:03:12 pureos kernel: rsi_91x: rsi_hal_key_config: Cipher 0xfac04 key_t
Dec 23 03:03:12 pureos kernel: rsi_91x: rsi_mac80211_set_key: RSI set_key
Dec 23 03:03:12 pureos kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link become
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.0382] device (w
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.0383] device (w
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.0402] device (w
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.0428] dhcp4 (wl
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.0482] dhcp4 (wl
Dec 23 03:03:12 pureos dhclient[2793]: DHCPREQUEST for 192.168.43.3 on wlan0 to
Dec 23 03:03:12 pureos dhclient[2793]: DHCPACK of 192.168.43.3 from 192.168.43.1
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.3899] dhcp4 (wl
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.3902] dhcp4 (wl
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.3903] dhcp4 (wl
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.3903] dhcp4 (wl
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.3904] dhcp4 (wl
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.3904] dhcp4 (wl
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.3904] dhcp4 (wl
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.3971] device (w
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.4004] device (w
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.4013] device (w
Dec 23 03:03:12 pureos dhclient[2793]: bound to 192.168.43.3 -- renewal in 1554
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.4146] policy: s
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.4178] device (w
Dec 23 03:03:12 pureos gsd-sharing[2551]: Failed to StopUnit service: GDBus.Erro
Dec 23 03:03:12 pureos gsd-sharing[2551]: Failed to StopUnit service: GDBus.Erro
Dec 23 03:03:12 pureos gsd-sharing[2551]: Failed to StopUnit service: GDBus.Erro
Dec 23 03:03:12 pureos gsd-sharing[2551]: Failed to StopUnit service: GDBus.Erro
Dec 23 03:03:12 pureos dbus-daemon[2311]: [system] Activating via systemd: servi
Dec 23 03:03:12 pureos NetworkManager[2339]: <info> [1545534192.4273] manager:
Dec 23 03:03:12 pureos systemd[1]: Starting Network Manager Script Dispatcher Se
-- Subject: Unit NetworkManager-dispatcher.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit NetworkManager-dispatcher.service has begun starting up.
Dec 23 03:03:12 pureos wpa_supplicant[2328]: wlan0: CTRL-EVENT-SIGNAL-CHANGE abo
Dec 23 03:03:12 pureos dbus-daemon[2311]: [system] Successfully activated servic
Dec 23 03:03:12 pureos systemd[1]: Started Network Manager Script Dispatcher Ser
-- Subject: Unit NetworkManager-dispatcher.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit NetworkManager-dispatcher.service has finished starting up.
--
-- The start-up result is RESULT.
Dec 23 03:03:12 pureos nm-dispatcher[2803]: req:1 'up' [wlan0]: new request (1 s
Dec 23 03:03:12 pureos nm-dispatcher[2803]: req:1 'up' [wlan0]: start running or
Dec 23 03:03:12 pureos nm-dispatcher[2803]: req:2 'connectivity-change': new req
Dec 23 03:03:12 pureos nm-dispatcher[2803]: req:2 'connectivity-change': start r
Dec 23 03:03:13 pureos systemd-networkd[2267]: wlan0: Gained IPv6LL
Dec 23 03:03:15 pureos wpa_supplicant[2328]: wlan0: CTRL-EVENT-SIGNAL-CHANGE abo
Dec 23 03:03:15 pureos kernel: Unable to handle kernel NULL pointer dereference
Dec 23 03:03:15 pureos kernel: Mem abort info:
Dec 23 03:03:15 pureos kernel: ESR = 0x96000004
Dec 23 03:03:15 pureos kernel: Exception class = DABT (current EL), IL = 32 bi
Dec 23 03:03:15 pureos kernel: SET = 0, FnV = 0
Dec 23 03:03:15 pureos kernel: EA = 0, S1PTW = 0
Dec 23 03:03:15 pureos kernel: Data abort info:
Dec 23 03:03:15 pureos kernel: ISV = 0, ISS = 0x00000004
Dec 23 03:03:15 pureos kernel: CM = 0, WnR = 0
Dec 23 03:03:15 pureos kernel: user pgtable: 4k pages, 48-bit VAs, pgdp = 000000
Dec 23 03:03:15 pureos kernel: [00000000000000d0] pgd=0000000000000000
Dec 23 03:03:15 pureos kernel: Internal error: Oops: 96000004 [#1] PREEMPT SMP
Dec 23 03:03:15 pureos kernel: Modules linked in: aes_ce_ccm qmi_wwan cdc_wdm us
Dec 23 03:03:15 pureos kernel: CPU: 2 PID: 2328 Comm: wpa_supplicant Not tainted
Dec 23 03:03:15 pureos kernel: Hardware name: Purism Librem 5 devkit (DT)
Dec 23 03:03:15 pureos kernel: pstate: 20000005 (nzCv daif -PAN -UAO)
Dec 23 03:03:15 pureos kernel: pc : rsi_send_probe_request+0x16c/0x328 [rsi_91x]
Dec 23 03:03:15 pureos kernel: lr : rsi_send_probe_request+0x158/0x328 [rsi_91x]
Dec 23 03:03:15 pureos kernel: sp : ffff8000a1eaf7e0
Dec 23 03:03:15 pureos kernel: x29: ffff8000a1eaf7e0 x28: ffff80008c9c8bb8
Dec 23 03:03:15 pureos kernel: x27: ffff8000a73c30c8 x26: ffff80008c9c8bb8
Dec 23 03:03:15 pureos kernel: x25: ffff8000a73c23d9 x24: 0000000000000000
Dec 23 03:03:15 pureos kernel: x23: 000000000000007a x22: ffff8000a1f92c40
Dec 23 03:03:15 pureos kernel: x21: 0000000000000001 x20: ffff8000a73c2000
Dec 23 03:03:15 pureos kernel: x19: 000000000000000e x18: ffff000008b76000
Dec 23 03:03:15 pureos kernel: x17: 0000000000000000 x16: 0000000000000000
Dec 23 03:03:15 pureos kernel: x15: ffff8000a1f92c00 x14: 0100000000000000
Dec 23 03:03:15 pureos kernel: x13: 00000000ff01006e x12: 1a2d6c6048302418
Dec 23 03:03:15 pureos kernel: x11: 120c080100000000 x10: 0000000000000100
Dec 23 03:03:15 pureos kernel: x9 : 0000000000000000 x8 : 0000ff01006e1a2d
Dec 23 03:03:15 pureos kernel: x7 : 6c60483004322418 x6 : ffff8000a73c242b
Dec 23 03:03:15 pureos kernel: x5 : ffff8000abf85e30 x4 : 0000000000000008
Dec 23 03:03:15 pureos kernel: x3 : 0000000000000000 x2 : ffffffffffffffca
Dec 23 03:03:15 pureos kernel: x1 : ffff8000a1f92e4a x0 : ffff8000a73c23d9
Dec 23 03:03:15 pureos kernel: Process wpa_supplicant (pid: 2328, stack limit =
Dec 23 03:03:15 pureos kernel: Call trace:
Dec 23 03:03:15 pureos kernel: rsi_send_probe_request+0x16c/0x328 [rsi_91x]
Dec 23 03:03:15 pureos kernel: rsi_mac80211_hw_scan_start+0x168/0x200 [rsi_91x]
Dec 23 03:03:15 pureos kernel: __ieee80211_start_scan+0x260/0x818
Dec 23 03:03:15 pureos kernel: ieee80211_request_scan+0x34/0x58
Dec 23 03:03:15 pureos kernel: ieee80211_scan+0x58/0xd0
Dec 23 03:03:15 pureos kernel: nl80211_trigger_scan+0x5ac/0x820
Dec 23 03:03:15 pureos kernel: genl_family_rcv_msg+0x248/0x368
Dec 23 03:03:15 pureos kernel: genl_rcv_msg+0x60/0xa8
Dec 23 03:03:15 pureos kernel: netlink_rcv_skb+0xf0/0x138
Dec 23 03:03:15 pureos kernel: genl_rcv+0x3c/0x50
Dec 23 03:03:15 pureos kernel: netlink_unicast+0x198/0x218
Dec 23 03:03:15 pureos kernel: netlink_sendmsg+0x274/0x340
Dec 23 03:03:15 pureos kernel: sock_sendmsg+0x34/0x50
Dec 23 03:03:15 pureos kernel: ___sys_sendmsg+0x28c/0x2b8
Dec 23 03:03:15 pureos kernel: __sys_sendmsg+0x78/0xd0
Dec 23 03:03:15 pureos kernel: sys_sendmsg+0x38/0x48
Dec 23 03:03:15 pureos kernel: el0_svc_naked+0x30/0x34
Dec 23 03:03:15 pureos kernel: Code: 54fffba1 110062f7 7101e2ff 540002c9 (f9406b
Dec 23 03:03:15 pureos kernel: ---[ end trace 15322be8d420ef7f ]---
Dec 23 03:03:15 pureos systemd[1]: wpa_supplicant.service: Main process exited,
Dec 23 03:03:15 pureos systemd[1]: wpa_supplicant.service: Failed with result 's
Dec 23 03:03:15 pureos NetworkManager[2339]: <info> [1545534195.5804] supplican
Dec 23 03:03:15 pureos NetworkManager[2339]: <info> [1545534195.5806] device (w
Dec 23 03:03:15 pureos NetworkManager[2339]: <warn> [1545534195.5954] sup-iface
Dec 23 03:03:15 pureos NetworkManager[2339]: <info> [1545534195.5964] device (w
Dec 23 03:03:15 pureos NetworkManager[2339]: <info> [1545534195.6012] dhcp4 (wl
Dec 23 03:03:15 pureos NetworkManager[2339]: <info> [1545534195.6013] dhcp4 (wl
```
https://source.puri.sm/Librem5/OS-issues/-/issues/6Make devkits use DHCP by default2022-01-18T17:19:50ZGuido GuntherMake devkits use DHCP by defaultThe static IP is more complicated to deal with since it will almost always need configuration.
Any objections?The static IP is more complicated to deal with since it will almost always need configuration.
Any objections?https://source.puri.sm/Librem5/developer.puri.sm/-/issues/65Introduction points to almost empty page "Hardware Reference"2018-12-23T10:44:01ZGuido GuntherIntroduction points to almost empty page "Hardware Reference"We know the hardware of the Devkit so the first link [Hardware Reference](https://developer.puri.sm/Librem5/Hardware_Reference.html) on
https://developer.puri.sm/Librem5/Introduction.html
Should point to an appropriate page. This also ...We know the hardware of the Devkit so the first link [Hardware Reference](https://developer.puri.sm/Librem5/Hardware_Reference.html) on
https://developer.puri.sm/Librem5/Introduction.html
Should point to an appropriate page. This also relates to #18.
Having things like RAM, CPU Module, modem, wifi would be start we could then fill in more details via MRs. The page should provide two separate sections for the devkit and the phone.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/64Patch submission should use "default branch" instead of "master"2019-01-08T11:01:06ZGuido GuntherPatch submission should use "default branch" instead of "master"For some projects where we're not upstream development happens on the projects default brunch (the one you get by default after clone) and not master since master is used for upstreams master, e.g. wlroots or linux-emcraft. We should exp...For some projects where we're not upstream development happens on the projects default brunch (the one you get by default after clone) and not master since master is used for upstreams master, e.g. wlroots or linux-emcraft. We should explain that at:
https://developer.puri.sm/Librem5/Contact/Contributing.html?highlight=contributing#submitting-patches
The branch is usually called `Librem5` (kernel is currently an exception).https://source.puri.sm/Librem5/OS-issues/-/issues/5Prevent breackage via PureOS green2019-10-31T10:03:02ZGuido GuntherPrevent breackage via PureOS greenOnce we switch to PureOS newer packages of the ones we patched (e.g. mesa) will break the devkits. We need scripts that alert us about newer packages in landing.Once we switch to PureOS newer packages of the ones we patched (e.g. mesa) will break the devkits. We need scripts that alert us about newer packages in landing.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/63Unify devkit and imx8 page2018-12-21T11:34:36ZGuido GuntherUnify devkit and imx8 pageThere's
https://developer.puri.sm/Librem5/Development_Environment/Boards/imx8.html
https://developer.puri.sm/Librem5/Development_Environment/Boards/Dev-kit.html
while both refer to the devkit.There's
https://developer.puri.sm/Librem5/Development_Environment/Boards/imx8.html
https://developer.puri.sm/Librem5/Development_Environment/Boards/Dev-kit.html
while both refer to the devkit.David BoddieDavid Boddie