Unable to boot properly with edi-cl built image on Compulab IOT-GATE-imx8

General Discussions
1

Hi,
I am integrating mender on Compulab IOT-GATE-iMX8 device for OTA firnware upgrade. I followed all instructions as mentioned in GitHub - lueschem/edi-cl: This repository contains an edi project configuration for Compulab embedded devices. and am able to copy the mender-enabled image to USB stick and boot from the USB stick but with following error:
imx-sdma 30bd0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2

Also, am unable to set up WiFi with this new image. Trying to figure out the reason, I saw that wlan0 setup is removed from the edi project in one of the commits. I have below questions related to this:

  1. Why was the wlan- setup removed? I do not see this information in any high-level document. May-be I missed seeing it.
  2. Are there any plans to enable this back?
  3. If I want to add it myself, would just reverting the commit (while resolving needed conflicts) suffice or do you think there will be something additional to be done?
  4. How can I get successful loading of imx/sdma/sdma-imx7d.bin? A quick look indicates that this file is present in /lib/firmware/imx folder in rootfs in by-default provided image from Compulab, but the same when built using edi-cl, this file and the imx folder within rootfs is missing. I did try copying this file and booting, but with no success.

Please see below the boot log for reference.

[    0.772551] imx-sdma 302c0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
[    0.780229] imx-sdma 302c0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin
[    0.781637] mxs-dma 33000000.dma-controller: initialized
[    0.796201] Bus freq driver module loaded
[    0.803618] Serial: 8250/16550 driver, 4 ports, IRQ sharing P¹       ±5
                                                                          [    0.809278] printk: console [ttymxc2] enabled
[    0.814437] printk: bootconsole [ec_imx6q0] disabled
[    0.819865] 30890000.serial: ttymxc1 at MMIO 0x30890000 (irq = 32, base_baud = 1500000) is a IMX
[    0.830591] imx-drm soc@0:bus@32c00000:display-subsystem: no available port
[    0.845747] loop: module loaded
[    0.850788] imx ahci driver is registered.
[    0.856742] libphy: Fixed MDIO Bus: probed
[    0.861637] tun: Universal TUN/TAP device driver, 1.6
[    0.866855] CAN device driver interface
[    0.871215] thunder_xcv, ver 1.0
[    0.874486] thunder_bgx, ver 1.0
[    0.877753] nicpf, ver 1.0
[    0.881232] pps pps0: new PPS source ptp0
[    0.886325] libphy: fec_enet_mii_bus: probed
[    0.891605] fec 30be0000.ethernet eth0: registered PHC device 0
[    0.898030] Freescale FM module, FMD API version 21.1.0
[    0.903477] Freescale FM Ports module
[    0.907153] fsl_mac: fsl_mac: FSL FMan MAC API based driver
[    0.912869] fsl_dpa: FSL DPAA Ethernet driver
[    0.917326] fsl_advanced: FSL DPAA Advanced drivers:
[    0.922301] fsl_proxy: FSL DPAA Proxy initialization driver
[    0.927974] fsl_oh: FSL FMan Offline Parsing port driver
[    0.933862] hclge is initializing
[    0.937190] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version
[    0.944421] hns3: Copyright (c) 2017 Huawei Corporation.
[    0.949807] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
[    0.956865] e1000: Copyright (c) 1999-2006 Intel Corporation.
[    0.962655] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[    0.968497] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    0.974456] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.6.0-k
[    0.981425] igb: Copyright (c) 2007-2014 Intel Corporation.
[    0.987041] igbvf: Intel(R) Gigabit Virtual Function Network Driver - version 2.4.0-k
[    0.994881] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[    1.000952] sky2: driver version 1.30
[    1.005034] VFIO - User Level meta-driver version: 0.3
[    1.011748] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.018304] ehci-pci: EHCI PCI platform driver
[    1.022831] ehci-platform: EHCI generic platform driver
[    1.028220] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.034429] ohci-pci: OHCI PCI platform driver
[    1.038914] ohci-platform: OHCI generic platform driver
[    1.044645] usbcore: registered new interface driver usb-storage
[    1.051965] imx_usb 32e40000.usb: No over current polarity defined
[    1.058293] imx_usb 32e50000.usb: No over current polarity defined
[    1.065862] i2c /dev entries driver
[    1.073814] imx2-wdt 30280000.watchdog: timeout 60 sec (nowayout=0)
[    1.081743] sdhci: Secure Digital Host Controller Interface driver
[    1.087942] sdhci: Copyright(c) Pierre Ossman
[    1.092420] Synopsys Designware Multimedia Card Interface Driver
[    1.098938] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.105150] mmc1: CQHCI version 5.10
[    1.139895] mmc1: SDHCI controller on 30b50000.mmc [30b50000.mmc] using ADMA
[    1.147346] mmc2: CQHCI version 5.10
[    1.181992] mmc2: SDHCI controller on 30b60000.mmc [30b60000.mmc] using ADMA
[    1.190357] ledtrig-cpu: registered to indicate activity on CPUs
[    1.197507] caam 30900000.crypto: device ID = 0x0a16040100000000 (Era 9)
[    1.204277] caam 30900000.crypto: job rings = 3, qi = 0
[    1.219661] caam algorithms registered in /proc/crypto
[    1.226602] caam 30900000.crypto: caam pkc algorithms registered in /proc/crypto
[    1.236178] caam_jr 30901000.jr: registering rng-caam
[    1.246730] caam-snvs 30370000.caam-snvs: can't get snvs clock
[    1.252718] caam-snvs 30370000.caam-snvs: violation handlers armed - non-secure state
[    1.261257] usbcore: registered new interface driver usbhid
[    1.266913] usbhid: USB HID core driver
[    1.272176] No fsl,qman node
[    1.275148] Freescale USDPAA process driver
[    1.279405] fsl-usdpaa: no region found
[    1.283311] Freescale USDPAA process IRQ driver
[    1.291602] NET: Registered protocol family 26
[    1.296633] NET: Registered protocol family 10
[    1.301775] Segment Routing with IPv6
[    1.305518] NET: Registered protocol family 17
[    1.309986] can: controller area network core (rev 20170425 abi 9)
[    1.316218] NET: Registered protocol family 29
[    1.320680] can: raw protocol (rev 20170425)
[    1.325188] Bluetooth: RFCOMM TTY layer initialized
[    1.330194] Bluetooth: RFCOMM socket layer initialized
[    1.335386] Bluetooth: RFCOMM ver 1.11
[    1.339156] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    1.344591] Bluetooth: BNEP filters: protocol multicast
[    1.349943] Bluetooth: BNEP socket layer initialized
[    1.355024] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    1.360990] mmc2: Command Queue Engine enabled
[    1.361061] Bluetooth: HIDP socket layer initialized
[    1.365463] mmc2: new DDR MMC card at address 0001
[    1.370557] 8021q: 802.1Q VLAN Support v1.8
[    1.379542] lib80211: common routines for IEEE802.11 drivers
[    1.379651] mmcblk2: mmc2:0001 DG4032 29.1 GiB
[    1.389883] mmcblk2boot0: mmc2:0001 DG4032 partition 1 4.00 MiB
[    1.389967] 9pnet: Installing 9P2000 support
[    1.395945] mmcblk2boot1: mmc2:0001 DG4032 partition 2 4.00 MiB
[    1.400216] tsn generic netlink module v1 init...
[    1.406151] mmcblk2rpmb: mmc2:0001 DG4032 partition 3 4.00 MiB, chardev (238:0)
[    1.410896] Key type dns_resolver registered
[    1.422774] registered taskstats version 1
[    1.426938]  mmcblk2: p1 p2
[    1.426950] Loading compiled-in X.509 certificates
[    1.454755] regulator-uart1-trmen GPIO handle specifies active low - ignored
[    1.462899] usb_phy_generic usbphynop1: usbphynop1 supply vcc not found, using dummy regulator
[    1.471681] usb_phy_generic usbphynop2: usbphynop2 supply vcc not found, using dummy regulator
[    1.481968] at24 0-0054: 1024 byte 24c08 EEPROM, writable, 16 bytes/write
[    1.488810] i2c i2c-0: IMX I2C adapter registered
[    1.494630] rtc-abx80x 1-0069: model 1805, revision 2.3, lot 330, wafer 6, uid 140
[    1.503772] rtc-abx80x 1-0069: Oscillator failure, data is invalid.
[    1.510146] rtc-abx80x 1-0069: registered as rtc0
[    1.517794] at24 1-0050: 1024 byte 24c08 EEPROM, writable, 16 bytes/write
[    1.524646] i2c i2c-1: IMX I2C adapter registered
[    1.533179] at24 3-0054: 1024 byte 24c08 EEPROM, writable, 16 bytes/write
[    1.540027] i2c i2c-3: IMX I2C adapter registered
[    1.545673] imx6q-pcie 33800000.pcie: couldn't get pcie-phy
[    1.545882] 30860000.serial: ttymxc0 at MMIO 0x30860000 (irq = 30, base_baud = 5000000) is a IMX
[    1.560091] imx6q-pcie 33800000.pcie: 33800000.pcie supply epdev_on not found, using dummy regulator
[    1.560821] imx_usb 32e40000.usb: No over current polarity defined
[    1.575475] imx6q-pcie 33800000.pcie: host bridge /soc@0/pcie@33800000 ranges:
[    1.575477] imx_usb 32e40000.usb: 32e40000.usb supply vbus not found, using dummy regulator
[    1.578254] ci_hdrc ci_hdrc.0: EHCI Host Controller
[    1.582738] imx6q-pcie 33800000.pcie:    IO 0x1ff80000..0x1ff8ffff -> 0x00000000
[    1.591089] ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1
[    1.595967] imx6q-pcie 33800000.pcie:   MEM 0x18000000..0x1fefffff -> 0x18000000
[    1.616686] ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00
[    1.617878] imx6q-pcie 33800000.pcie: EXT REF_CLK is used!.
[    1.623686] hub 1-0:1.0: USB hub found
[    1.632568] hub 1-0:1.0: 1 port detected
[    1.637566] imx_usb 32e50000.usb: No over current polarity defined
[    1.643837] imx_usb 32e50000.usb: 32e50000.usb supply vbus not found, using dummy regulator
[    1.654986] ci_hdrc ci_hdrc.1: EHCI Host Controller
[    1.659891] ci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 2
[    1.680683] ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00
[    1.686553] hub 2-0:1.0: USB hub found
[    1.690333] hub 2-0:1.0: 1 port detected
[    1.694972] imx-cpufreq-dt imx-cpufreq-dt: cpu speed grade 3 mkt segment 0 supported-hw 0x8 0x1
[    1.708060] input: bd718xx-pwrkey as /devices/platform/soc@0/soc@0:bus@30800000/30a30000.i2c/i2c-1/1-004b/gpio-keys.0.auto/input/input0
[    1.736733] imx6q-pcie 33800000.pcie: PCIe PLL locked after 20 us.
[    1.843095] imx6q-pcie 33800000.pcie: Link up
[    1.947503] imx6q-pcie 33800000.pcie: Link up
[    1.951873] imx6q-pcie 33800000.pcie: Link up, Gen2
[    1.956893] imx6q-pcie 33800000.pcie: PCI host bridge to bus 0000:00
[    1.963377] pci_bus 0000:00: root bus resource [bus 00-ff]
[    1.968866] pci_bus 0000:00: root bus resource [io  0x0000-0xffff]
[    1.975060] pci_bus 0000:00: root bus resource [mem 0x18000000-0x1fefffff]
[    1.981952] pci 0000:00:00.0: [16c3:abcd] type 01 class 0x060400
[    1.987984] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x000fffff]
[    1.994262] pci 0000:00:00.0: reg 0x38: [mem 0x00000000-0x0000ffff pref]
[    2.001004] pci 0000:00:00.0: supports D1
[    2.005017] pci 0000:00:00.0: PME# supported from D0 D1 D3hot D3cold
[    2.012772] pci 0000:01:00.0: [8086:2723] type 00 class 0x028000
[    2.018881] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
[    2.025992] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
[    2.042043] pci 0000:00:00.0: BAR 0: assigned [mem 0x18000000-0x180fffff]
[    2.048846] pci 0000:00:00.0: BAR 14: assigned [mem 0x18100000-0x181fffff]
[    2.055841] pci 0000:00:00.0: BAR 6: assigned [mem 0x18200000-0x1820ffff pref]
[    2.056701] usb usb1-port1: over-current condition
[    2.063074] pci 0000:01:00.0: BAR 0: assigned [mem 0x18100000-0x18103fff 64bit]
[    2.075206] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[    2.080447] pci 0000:00:00.0:   bridge window [mem 0x18100000-0x181fffff]
[    2.087497] pcieport 0000:00:00.0: PME: Signaling with IRQ 215
[    2.093520] pcieport 0000:00:00.0: AER: enabled with IRQ 215
[    2.099457] Waiting for root device /dev/sda3...
[    2.116702] usb usb2-port1: over-current condition
[    2.336676] usb 1-1: new high-speed USB device number 2 using ci_hdrc
[    2.376029] usb-storage 1-1:1.0: USB Mass Storage device detected
[    2.382393] scsi host0: usb-storage 1-1:1.0
[    2.392681] usb 2-1: new high-speed USB device number 2 using ci_hdrc
[    2.425721] hub 2-1:1.0: USB hub found
[    2.429634] hub 2-1:1.0: 5 ports detected
[    2.720696] usb 2-1.1: new high-speed USB device number 3 using ci_hdrc
[    2.756126] random: fast init done
[    2.836700] usb 2-1.4: new full-speed USB device number 4 using ci_hdrc
[    3.555866] scsi 0:0:0:0: Direct-Access     USB      Flash Disk       1100 PQ: 0 ANSI: 6
[    3.565220] sd 0:0:0:0: [sda] 31129600 512-byte logical blocks: (15.9 GB/14.8 GiB)
[    3.573573] sd 0:0:0:0: [sda] Write Protect is off
[    3.579072] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    3.601615]  sda: sda1 sda2 sda3 sda4
[    3.609086] sd 0:0:0:0: [sda] Attached SCSI removable disk
[    3.955373] EXT4-fs (sda3): recovery complete
[    3.964576] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[    3.972299] VFS: Mounted root (ext4 filesystem) on device 8:3.
[    3.984740] devtmpfs: mounted
[    3.988342] Freeing unused kernel memory: 2496K
[    3.992962] Run /sbin/init as init process
[    4.424202] systemd[1]: System time before build time, advancing clock.
[    4.489596] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[    4.511485] systemd[1]: Detected architecture arm64.

Welcome to Debian GNU/Linux 10 (buster)!

[    4.569754] systemd[1]: Set hostname to <iot-gate-imx8>.
[    4.854089] systemd[1]: File /lib/systemd/system/systemd-journald.service:12 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.
[    4.871175] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)
[    5.069740] random: systemd: uninitialized urandom read (16 bytes read)
[    5.079032] random: systemd: uninitialized urandom read (16 bytes read)
[    5.085721] systemd[1]: Reached target Remote File Systems.
[  OK  ] Reached target Remote File Systems.
[    5.104783] random: systemd: uninitialized urandom read (16 bytes read)
[    5.111454] systemd[1]: Reached target Swap.
[  OK  ] Reached target Swap.
[    5.129116] systemd[1]: Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Journal Socket (/dev/log).
[    5.148925] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Started Forward Password R…uests to Wall Directory Watch.
[    5.173078] systemd[1]: Listening on udev Kernel Socket.
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Created slice system-getty.slice.
[  OK  ] Created slice system-serial\x2dgetty.slice.
[  OK  ] Started Dispatch Password …ts to Console Directory Watch.
[  OK  ] Reached target Local Encrypted Volumes.
[  OK  ] Listening on Journal Audit Socket.
[  OK  ] Listening on fsck to fsckd communication Socket.
[  OK  ] Listening on udev Control Socket.
[  OK  ] Reached target Paths.
[  OK  ] Reached target Remote Encrypted Volumes.
[  OK  ] Listening on Network Service Netlink Socket.
[  OK  ] Listening on initctl Compatibility Named Pipe.
[  OK  ] Reached target Slices.
[  OK  ] Listening on Journal Socket.
         Starting Create list of re…odes for the current kernel...
         Starting Journal Service...
         Starting Nameserver information manager...
         Starting Load Kernel Modules...
         Starting udev Coldplug all Devices...
         Mounting Huge Pages File System...
         Starting Remount Root and Kernel File Systems...
         Mounting Kernel Debug File System...
[    5.545739] EXT4-fs (sda3): re-mounted. Opts: (null)
[    5.550783] ext4 filesystem being remounted at / supports timestamps until 2038 (0x7fffffff)
         Starting Wait Until Kernel Time Synchronized...
         Mounting POSIX Message Queue File System...
[  OK  ] Started Journal Service.
[  OK  ] Started Create list of req… nodes for the current kernel.
[  OK  ] Started Load Kernel Modules.
[  OK  ] Mounted Huge Pages File System.
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Mounted Kernel Debug File System.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Started Nameserver information manager.
         Starting Create System Users...
         Starting Load/Save Random Seed...
         Mounting Kernel Configuration File System...
         Starting Apply Kernel Variables...
         Starting Flush Journal to Persistent Storage...
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Started Create System Users.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Mounted Kernel Configuration File System.
[  OK  ] Started Apply Kernel Variables.
         Starting Create Static Device Nodes in /dev...
         Starting Helper to synchronize boot up for ifupdown...
[    5.969607] systemd-journald[357]: Received request to flush runtime journal from PID 1
[  OK  ] Started Helper to synchronize boot up for ifupdown.
[  OK  ] Started Flush Journal to Persistent Storage.
[  OK  ] Started Create Static Device Nodes in /dev.
[  OK  ] Reached target Local File Systems (Pre).
         Mounting /data...
         Mounting /boot/firmware...
[    6.088819] EXT4-fs (sda2): recovery complete
[    6.101239] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[    6.101423] EXT4-fs (sda1): recovery complete
[    6.113345] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[    6.113350] ext4 filesystem being mounted at /data supports timestamps until 2038 (0x7fffffff)
         [    6.129688] ext4 filesystem being mounted at /boot/firmware supports timestamps until 2038 (0x7fffffff)
Starting udev Kernel Device Manager...
[  OK  ] Mounted /data.
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Mounted /boot/firmware.
         Starting Network Service...
[  OK  ] Reached target Local File Systems.
         Starting Create Volatile Files and Directories...
         Starting Raise network interfaces...
[  OK  ] Started Create Volatile Files and Directories.
         Starting Network Time Synchronization...
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Started Network Service.
[  OK  ] Started Network Time Synchronization.
[  OK  ] Started Raise network interfaces.
[    6.472622] imx-sdma 302b0000.dma-controller: external firmware not found, using ROM firmware
[    6.472740] imx-sdma 302c0000.dma-controller: external firmware not found, using ROM firmware
[    6.491049] imx-sdma 30bd0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
         Starting Networ[    6.503222] imx-sdma 30bd0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin
k Name Resolution...
[    6.506571] spi_imx 30820000.spi: probed
[  OK  ] Reached target System Initialization.
[    6.527758] spi_imx 30840000.spi: probed
[    6.542200] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[  OK  ] Listening on OpenBSD Secure Shell server socket.
[  OK  ] Reached target Sockets.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[    6.590356] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    6.604429] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    6.613142] platform regulatory.0: Falling back to sysfs fallback for: regulatory.db
[  OK  ] Reached target Basic System.
         Starting getty on tty2-tty…nd logind are not available...
         Starting Adjust mender con…on according to boot device...
[    6.673298] imx-sdma 30bd0000.dma-controller: external firmware not found, using ROM firmware
         Starting Generate host keys for openssh-server[    6.696606] cfg80211: failed to load regulatory.db
....
[    6.706039] usbcore: registered new interface driver btusb
[    6.713388] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[    6.721966] Bluetooth: hci0: Device revision is 1
[    6.726756] Bluetooth: hci0: Secure boot is enabled
[    6.726762] Bluetooth: hci0: OTP lock is enabled
[    6.736322] Bluetooth: hci0: API lock is enabled
[    6.740971] Bluetooth: hci0: Debug lock is disabled
         [    6.745895] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Starting resize root file system...
[    6.760101] mcp25xxfd spi2.0 can0: MCP2518FD rev0.0 successfully initialized.
[  OK  ] Started resize root file system.
[  OK  ] Found device /dev/ttymxc2.
[  OK  ] Started Adjust mender conf…tion according to boot device.
[    6.826519] Intel(R) Wireless WiFi driver for Linux
[    6.832027] Copyright(c) 2003- 2015 Intel Corporation
[    6.837712] iwlwifi 0000:01:00.0: enabling device (0000 -> 0002)
[    6.860489] smsc95xx v1.0.6
[    6.929961] smsc95xx 2-1.1:1.0 eth1: register 'smsc95xx' at usb-ci_hdrc.1-1.1, smsc95xx USB 2.0 Ethernet, 00:01:c0:2a:ca:f5
[    6.941324] usbcore: registered new interface driver smsc95xx
[    6.945324] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[    7.029541] iwlwifi 0000:01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 58.3.35.22
[    7.037059] iwlwifi 0000:01:00.0: Found debug destination: EXTERNAL_DRAM
[    7.043819] iwlwifi 0000:01:00.0: Found debug configuration: 0
[    7.051467] iwlwifi 0000:01:00.0: loaded firmware version 50.3e391d3e.0 op_mode iwlmvm
[  OK  ] Started getty on tty2-tty6… and logind are not available.
[  OK  ] Reached target Bluetooth.
[  OK  ] Started ifup for eth0.
[    7.315536] iwlwifi 0000:01:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
[    7.335483] iwlwifi 0000:01:00.0: Applying debug destination EXTERNAL_DRAM
[    7.343418] iwlwifi 0000:01:00.0: Allocated 0x00400000 bytes for firmware monitor.
[    7.384970] random: crng init done
[    7.388391] random: 7 urandom warning(s) missed due to ratelimiting
[  OK  ] Started Generate host keys for openssh-server..
[    7.432495] Atheros 8031 ethernet 30be0000.ethernet-1:00: attached PHY driver [Atheros 8031 ethernet] (mii_bus:phy_addr=30be0000.ethernet-1:00, irq=POLL)
[  OK  ] Started Network Name Resolution.
[  OK  ] Reached target Network.
         Starting Permit User Sessions...
[  OK  ] Started Mender OTA update service.
[  OK  ] Reached target Host and Network Name Lookups.
[  OK  ] Started Permit User Sessions.
[  OK  ] Started Getty on tty1.
[  OK  ] Started Serial Getty on ttymxc2.
[  OK  ] Started Getty on tty2.
[  OK  ] Started Getty on tty3.
[  OK  ] Started Getty on tty4.
[  OK  ] Started Getty on tty5.
[  OK  ] Started Getty on tty6.
[  OK  ] Reached target Login Prompts.
[  OK  ] Reached target Multi-User System.
[  OK  ] Reached target Graphical Interface.
         Starting Update UTMP about System Runlevel Changes...
[    7.784712] usb 2-1.5: new high-speed USB device number 5 using ci_hdrc
[  OK  ] Started Update UTMP about System Runlevel Changes.
[    7.847010] usbcore: registered new interface driver cdc_wdm
[    7.861019] qmi_wwan 2-1.5:1.5: cdc-wdm0: USB WDM device
[    7.868256] qmi_wwan 2-1.5:1.5 wwan0: register 'qmi_wwan' at usb-ci_hdrc.1-1.5, WWAN/QMI device, ce:85:ce:26:c2:33
[    7.878904] usbcore: registered new interface driver qmi_wwan
[    7.884983] usbcore: registered new interface driver option
[    7.890741] usbserial: USB Serial support registered for GSM modem (1-port)
[    7.898102] option 2-1.5:1.0: GSM modem (1-port) converter detected
[    7.904760] usb 2-1.5: GSM modem (1-port) converter now attached to ttyUSB0
[    7.912046] option 2-1.5:1.1: GSM modem (1-port) converter detected
[    7.918648] usb 2-1.5: GSM modem (1-port) converter now attached to ttyUSB1
[    7.925933] option 2-1.5:1.2: GSM modem (1-port) converter detected
[    7.932544] usb 2-1.5: GSM modem (1-port) converter now attached to ttyUSB2
[    7.939831] option 2-1.5:1.3: GSM modem (1-port) converter detected
[    7.946432] usb 2-1.5: GSM modem (1-port) converter now attached to ttyUSB3
[    7.953719] option 2-1.5:1.4: GSM modem (1-port) converter detected
[    7.960296] usb 2-1.5: GSM modem (1-port) converter now attached to ttyUSB4
[    8.372709] iwlwifi 0000:01:00.0: Collecting data: trigger 15 fired.
[    8.379196] iwlwifi 0000:01:00.0: Start IWL Error Log Dump:
[    8.384781] iwlwifi 0000:01:00.0: Status: 0x00000000, count: 731714787
[    8.391325] iwlwifi 0000:01:00.0: Loaded firmware version: 50.3e391d3e.0
[    8.398036] iwlwifi 0000:01:00.0: 0x07ADB5F6 | ADVANCED_SYSASSERT
[    8.405009] iwlwifi 0000:01:00.0: 0x8A0AC8C1 | trm_hw_status0
[    8.410763] iwlwifi 0000:01:00.0: 0xC76B997F | trm_hw_status1
[    8.416519] iwlwifi 0000:01:00.0: 0x33C678C8 | branchlink2
[    8.422011] iwlwifi 0000:01:00.0: 0xFB4AFE6A | interruptlink1
[    8.427766] iwlwifi 0000:01:00.0: 0x91CA984D | interruptlink2
[    8.433518] iwlwifi 0000:01:00.0: 0xFBAD77E9 | data1
[    8.438494] iwlwifi 0000:01:00.0: 0x4503490F | data2
[    8.443466] iwlwifi 0000:01:00.0: 0x37DCB6EE | data3
[    8.448441] iwlwifi 0000:01:00.0: 0x11A0555A | beacon time
[    8.453934] iwlwifi 0000:01:00.0: 0x2D154E8F | tsf low
[    8.459081] iwlwifi 0000:01:00.0: 0x6012DABA | tsf hi
[    8.464141] iwlwifi 0000:01:00.0: 0x7DEEBBD6 | time gp1
[    8.469378] iwlwifi 0000:01:00.0: 0x8FEEA935 | time gp2
[    8.474612] iwlwifi 0000:01:00.0: 0x6D786EF9 | uCode revision type
[    8.480804] iwlwifi 0000:01:00.0: 0x56345283 | uCode version major
[    8.486993] iwlwifi 0000:01:00.0: 0xEAF71B6A | uCode version minor
[    8.493185] iwlwifi 0000:01:00.0: 0x42243C7C | hw version
[    8.498593] iwlwifi 0000:01:00.0: 0x9CE2793D | board version
[    8.504272] iwlwifi 0000:01:00.0: 0xF9ABEAF4 | hcmd
[    8.509160] iwlwifi 0000:01:00.0: 0x705306F0 | isr0
[    8.514047] iwlwifi 0000:01:00.0: 0xEDEAE65F | isr1
[    8.518932] iwlwifi 0000:01:00.0: 0x51DA205C | isr2
[    8.523819] iwlwifi 0000:01:00.0: 0x17D873E0 | isr3
[    8.528706] iwlwifi 0000:01:00.0: 0xB51C8864 | isr4
[    8.533592] iwlwifi 0000:01:00.0: 0xA3A9F3D3 | last cmd Id
[    8.539087] iwlwifi 0000:01:00.0: 0x22D62DDE | wait_event
[    8.544496] iwlwifi 0000:01:00.0: 0x9EF3FDE9 | l2p_control
[    8.550010] iwlwifi 0000:01:00.0: 0x0548E080 | l2p_duration
[    8.555602] iwlwifi 0000:01:00.0: 0xA3D7319A | l2p_mhvalid
[    8.561097] iwlwifi 0000:01:00.0: 0x85603434 | l2p_addr_match
[    8.566854] iwlwifi 0000:01:00.0: 0xF9D9EB39 | lmpm_pmg_sel
[    8.572433] iwlwifi 0000:01:00.0: 0x849B6463 | timestamp
[    8.577756] iwlwifi 0000:01:00.0: 0x9CD3FEFF | flow_handler
[    8.583371] iwlwifi 0000:01:00.0: Start IWL Error Log Dump:
[    8.588957] iwlwifi 0000:01:00.0: Status: 0x00000000, count: -2107820443
[    8.595667] iwlwifi 0000:01:00.0: 0xEEF708C1 | ADVANCED_SYSASSERT
[    8.601787] iwlwifi 0000:01:00.0: 0x3A116FC3 | umac branchlink1
[    8.603012] Bluetooth: hci0: Waiting for firmware download to complete
[    8.607721] iwlwifi 0000:01:00.0: 0x2FC55BDE | umac branchlink2
[    8.614250] Bluetooth: hci0: Firmware loaded in 1857794 usecs
[    8.614382] Bluetooth: hci0: Waiting for device to boot
[    8.620180] iwlwifi 0000:01:00.0: 0x386C3292 | umac interruptlink1
[    8.620185] iwlwifi 0000:01:00.0: 0x2B0F50EF | umac interruptlink2
[    8.632898] Bluetooth: hci0: Device booted in 18132 usecs
[    8.637351] iwlwifi 0000:01:00.0: 0x69703834 | umac data1
[    8.637354] iwlwifi 0000:01:00.0: 0xED0CCBF0 | umac data2
[    8.637357] iwlwifi 0000:01:00.0: 0xAFF144D2 | umac data3
[    8.644738] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
[    8.648944] iwlwifi 0000:01:00.0: 0xEBB83F6E | umac major
[    8.648949] iwlwifi 0000:01:00.0: 0xA0EBC523 | umac minor
[    8.655908] Bluetooth: hci0: Applying Intel DDC parameters completed
[    8.659773] iwlwifi 0000:01:00.0: 0xE168ABEF | frame pointer
[    8.695139] iwlwifi 0000:01:00.0: 0xAFF03C37 | stack pointer
[    8.700811] iwlwifi 0000:01:00.0: 0xFAC0EED8 | last host cmd
[    8.706483] iwlwifi 0000:01:00.0: 0x7C819C96 | isr status reg
[    8.712248] iwlwifi 0000:01:00.0: Fseq Registers:
[    8.716958] iwlwifi 0000:01:00.0: 0x20000000 | FSEQ_ERROR_CODE
[    8.722790] iwlwifi 0000:01:00.0: 0x00290021 | FSEQ_TOP_INIT_VERSION
[    8.729143] iwlwifi 0000:01:00.0: 0x00000000 | FSEQ_CNVIO_INIT_VERSION
[    8.735669] iwlwifi 0000:01:00.0: 0x0000A503 | FSEQ_OTP_VERSION
[    8.741588] iwlwifi 0000:01:00.0: 0x80000003 | FSEQ_TOP_CONTENT_VERSION
[    8.748201] iwlwifi 0000:01:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
[    8.754119] iwlwifi 0000:01:00.0: 0x00100530 | FSEQ_CNVI_ID
[    8.759690] iwlwifi 0000:01:00.0: 0x00000532 | FSEQ_CNVR_ID
[    8.765262] iwlwifi 0000:01:00.0: 0x00100530 | CNVI_AUX_MISC_CHIP
[    8.771358] iwlwifi 0000:01:00.0: 0x00000532 | CNVR_AUX_MISC_CHIP
[    8.777452] iwlwifi 0000:01:00.0: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[    8.785282] iwlwifi 0000:01:00.0: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[    8.793504] iwlwifi 0000:01:00.0: SecBoot CPU1 Status: 0x0, CPU2 Status: 0xa30000
[    8.800999] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
[    8.807023] iwlwifi 0000:01:00.0: Firmware not running - cannot dump error
[    8.826155] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110

Debian GNU/Linux 10 iot-gate-imx8 ttymxc2

Aprreciate your help to resolve this.
Thanks,
Minal

1 Like
2

@lueschem is probably best to answer any questions related to EDI

3

Hi Minal

Thanks for trying out the edi-cl setup!

Here are the answers to the above questions:

1) WLAN Setup

The WLAN setup got inherited from the edi-pi project configuration. However, it was not very elegant and therefore I removed it. From my point of view the setup proposed by Compulab is more elegant. As NetworkManager is not preinstalled by edi-cl you need to install it first and then setup the network:

sudo apt update
sudo apt install network-manager
sudo ip link wlan0 up
sudo nmcli dev wifi con "SSID" password "PASSWORD" name "WLANNAME"

To add this setup to the initial image I suggest that you fork edi-cl and add a new role that does the WLAN setup (by installing NetworkManager and eventually providing a configuration). If it is generic enough, we can also merge it into the edi-cl setup.

2) Re-add WLAN Setup

So far edi-cl just provides a minimal setup that can then be tailored to the needs of a specific project. But of course we can add an additional configuration that e.g. does a WLAN setup. The WLAN setup would also be a good example for a Mender state script that does a backup and restore of an existing WLAN setup when doing a full Mender based upgrade.
Anyway, I would prefer to do the WLAN setup based on NetworkManager instead of the very basic implementation done within edi-pi.

3) Reverting Commits

As explained above, I would not recommend that approach. But of course it should be feasible too.

4) sdma-imx7d.bin Failure

I did not care too much about the sdma-imx7d.bin failure as it is already present in the Compulab provided image:

compulab@iot-gate-imx8:~$ uname -a
Linux iot-gate-imx8 5.4.24-iot-gate-imx8-2.0 #1 SMP PREEMPT Thu Sep 3 10:30:00 IDT 2020 aarch64 GNU/Linux
compulab@iot-gate-imx8:~$ dmesg | grep -i error
[    0.770417] imx-sdma 302c0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
[    5.977059] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2

I did not detect any misbehavior that would be caused by this missing firmware.

If you need further assistance with the WLAN setup just let me know.

Best regards
Matthias

4

What actually worries me more are all the iwlwifi messages in your log. I cannot reproduce this:

root@iot-gate-imx8:~# dmesg | grep iwlwifi
[    4.119170] iwlwifi 0000:01:00.0: enabling device (0000 -> 0002)
[    4.184493] iwlwifi 0000:01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 58.3.35.22
[    4.195367] iwlwifi 0000:01:00.0: Found debug destination: EXTERNAL_DRAM
[    4.207961] iwlwifi 0000:01:00.0: Found debug configuration: 0
[    4.218561] iwlwifi 0000:01:00.0: loaded firmware version 50.3e391d3e.0 op_mode iwlmvm
[    4.301437] iwlwifi 0000:01:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
[    4.332786] iwlwifi 0000:01:00.0: Applying debug destination EXTERNAL_DRAM
[    4.340887] iwlwifi 0000:01:00.0: Allocated 0x00400000 bytes for firmware monitor.
[    4.497981] iwlwifi 0000:01:00.0: base HW address: 14:f6:d8:44:ad:ef
[   97.871865] iwlwifi 0000:01:00.0: Applying debug destination EXTERNAL_DRAM
[   98.028403] iwlwifi 0000:01:00.0: FW already configured (0) - re-configuring
[   98.067751] iwlwifi 0000:01:00.0: Applying debug destination EXTERNAL_DRAM
[   98.224558] iwlwifi 0000:01:00.0: FW already configured (0) - re-configuring
root@iot-gate-imx8:~# dpkg -l | grep iwlwifi
ii  firmware-iwlwifi                                         20200918-1~bpo10+1                             all          Binary firmware for Intel Wireless cards
5

Hi Matthias,
Thanks for replying back.

WLAN Setup:
I will try setting up WLAN using network manager. Will let you know how that goes.

sdma-imx7d.bin Failure:
I dont see this error in the Compulab provided image, so am not sure whats different. The image I am referring to is the one thats present in eMMC by default.
Also, I see that this bin file is present in boot/firmware/imx folder in compulab image. I did a quick try of copying the bin to edi-cl built-and-booted image but probably there is somewhere something missing in edi-cl setup/environment to be able to pick this bin correctly. I am not quite sure of the implications of not having this bin loaded in our use-case and hence wanted to have a clean matching setup between compulab image and edi-cl image.

iwlwifi messages
Thats strange that you cannot see the error messages but I can. Could it be probably related to the compulab release version being different, if any, between mine and your setup?
Compulab suggested to ensure that the setup has following kernel patch


This CompuLab patch should fix the iwlwifi load firmware issue that prevents the device from getting loaded correctly.
Reading the kernel build instructions https://github.com/lueschem/edi-cl/blob/master/docs/kernel_build.md, looks like this patch is not picked up?
I am very new to the edi, lxd, ansible world. I couldnt find out how is kernel built within the edi framework. Can you please help me with steps to apply this patch?

In your dmesg log snapshot, I see you are logged in as root. Is there a way to be able to login as root with edi-cl built image? I could login as compulab user but not root.

Thanks,
Minal

6

Hi Matthias,
I installed network-manager (ensuring wireless-tools, wpasupplicant and nmcli are installed) but I actually dont see any wireless interface on my device. I believe thats because of the iwlwifi errors and I definitely need the kernel patch in? I havent yet been able to figure out how to get that patch in (with edi-cl).

Below are my ifconfig and iwlist outputs:

compulab@iot-gate-imx8:~$ sudo ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.124  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 2405:6e00:31b1:5700:201:c0ff:fe2a:8cc0  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::201:c0ff:fe2a:8cc0  prefixlen 64  scopeid 0x20<link>
        ether 00:01:c0:2a:8c:c0  txqueuelen 1000  (Ethernet)
        RX packets 44632  bytes 55202390 (52.6 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 9228  bytes 881023 (860.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:01:c0:2a:ca:f5  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 426  bytes 120280 (117.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 426  bytes 120280 (117.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wwan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::2c92:a8ff:fe58:ea81  prefixlen 64  scopeid 0x20<link>
        ether 2e:92:a8:58:ea:81  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 18  bytes 1485 (1.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

compulab@iot-gate-imx8:~$ sudo iwconfig
eth0      no wireless extensions.

wwan0     no wireless extensions.

can0      no wireless extensions.

eth1      no wireless extensions.

lo        no wireless extensions.

Also, below is the uname output
compulab@iot-gate-imx8:~$ uname -a Linux iot-gate-imx8 5.4.24-iot-gate-imx8-2.1-00095-g58514aa0572b #1 SMP PREEMPT Sat Sep 19 19:58:46 UTC 2020 aarch64 GNU/Linux
So, I think you are on uboot 2.0 and I am on 2.1

Thanks,
Minal

7

Hi Minal

Many thanks for your additional informations - they are very helpful!

The newer kernel version of the factory device and the patch you have pointed out will hopefully help to get rid of the iwlwifi issue.

Here are some background informations for the kernel build:

  1. The edi/Debian approach is to build a Debian package for the kernel within the Debian release that is also present on the target system. This is why we have the LXD container: Within the LXD container we can install the same Debian release that is also present on the target system. The pre installed cross compiler can then be used to cross compile the kernel.
  2. The resulting Debian kernel package then usually gets uploaded to a Debian repository. If you do not have your own Debian repository yet then you can also directly copy the package to the target device and install it using dpkg -i linux-image*arm64.deb. edi-boot-shim will make sure that the U-Boot setup gets done correctly.

Within this blog post I gave some more insights.

So the next thing we probably have to do is to update the kernel build instructions so that we are based on the latest Compulab kernel. I am happy to help here and I will post an update as soon as I find time to dig into the setup. If you are already successful earlier then please let me know.

About the root login: Usually I disable the root account (no password in /etc/shadow) and I do not allow it via ssh. This is just a security best practice. If you want to enable the root account then you can set a password (sudo passwd root) and modify the sshd configuration accordingly.

Best regards
Matthias

8

Hi Minal

I just pushed an experimental branch (kernel_upgrade_iwlwifi). The new kernel can also be found on PackageCloud. However, now the firmware imx/sdma/sdma-imx7d.bin is really needed. I will add it soon. In the meantime you can also install it using sudo apt update && sudo apt install firmware-linux-nonfree/buster-backports.
Does this new kernel fix the iwlwifi issue?

Best regards
Matthias

9

Hi Matthias,
Thanks for all the detailed explanation. It now all makes sense to me.
I will try your experimental branch/deb packages soon.

Re wlan0 setup, I feel there is no harm in having the network manager installed by default (just lilke the default compulab image setup)? That will make things look similar. I think its fine to start the wlan0 interface as recommended by Compulab, but the missing info/piece is the network manager related installation. I feel either that should be spelled out loud in edi-cl documentation so that novice person like me does not miss or rather I would say does not remain under impression that the only difference between default compulab image and edi-cl built image is the board integration related stuff. I am not sure if there are such other differences, if any, between the 2 images as I havent played around more with either of the 2 images.

I am sure you would have thought through well about not having the network manager installed by default. May be its just that I am quite new to this and hence feel it should have been there by default ( as one main reason of going through the mender exercise and edi-cl is to perform firmware upgrade OTA and hence having wifi capability by default). May be I am half-minded and failing to understand something. Would be keen to hear on your thoughts.

I will test the experimental branch and let you know.

Regards,
Minal

10

Hi Minal

In the meantime I have added the sdma-imx7d.bin firmware and merged the changes to master.
Your idea about NetworkManager is good and therefore I have opened this ticket.
Compulab also mentioned the WiFi issue in their release notes.

Best regards
Matthias

11

Hi Matthias,
Thank you very much for the updates. I confirm that iwlwifi issue and sdma-imx7 issue gets resolved with the latest changes.

compulab@iot-gate-imx8:~$ dmesg | grep -i error
[    3.454991] GPT: Use GNU Parted to correct GPT errors.
[    6.801929] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
compulab@iot-gate-imx8:~$
compulab@iot-gate-imx8:~$ dmesg | grep iwlfi
compulab@iot-gate-imx8:~$
compulab@iot-gate-imx8:~$ dpkg -l | grep iwlwifi
ii  firmware-iwlwifi                                         20200918-1~bpo10+1                             all          Binary firmware for Intel Wireless cards
compulab@iot-gate-imx8:~$

Also, thanks a lot for accepting and creating a ticket related to NetworkManager. Would be keen to know when are you planning to resolve it.

Please note that iwlwifi issue is resolved but I still cannot see the wlan0 interface in the ifconfig list. I think thats something that will be taken care along with the NetworkManager ticket?

For your information, you might know this but I see that with default compulab image I can see 2 ethernet interfaces displayed (eth0 and eth1) but with edi-cl built image I can see only eth0. Probably thats just one difference to get closer to the default image?

Also, a small feedback about some minor things when I went through the exercise of following instructions provided here:

  1. Under pre-requisites step1 (Install lxd) for Debian , I had to perform following:
    sudo apt install snapd
    systemctl start snapd.service
    sudo snap install core
    sudo snap install lxd
    sudo usermode -a -G lxd $USER

  2. While creating an image succesive time onwards (with and without recursive clean), I hit an error related to losetup. It tries to mount the files on /dev/loop6 and 7 but previous ones are already mounted and I have to manually detach them before triggering the command again.

Hope this feedback helps.

Thanks,
Minal

12

Hi Minal

Many thanks for confirming that the iwlwifi problem got fixed!

About the network interfaces:
I indeed just configured eth0. But the other interfaces should be available too. You can see them if you do an ifconfig -a.

About the NetworkManager ticket:
I do not know yet when it will make it to the top of my TODO list. Unfortunately I have more projects than spare time.

About the LXD installation:
Many thanks for pointing out this issue. I fixed the documentation.

About the loop devices:
What kind of error message did you get? I will try if I can reproduce this issue.

Best regards
Matthias

13

Hi Matthias,
Sorry, it didnt strike me that the interface was not up. I can see wlan0 and eth1 using ifconfig -a

About the loop devices, I will send you snapshots of what I mean, in my free time.

Would greatly appreciate if you can provide quick suggestion on how to add the installation of NetworkManager or in general any other packages(of choice). Apart from network issue, I am also looking at resolving the ticket as reference to do similar to install some other packages for our use case.

Thanks,
Minal

14

Hi Matthias,
I think my questions would be self-answered by going through the edi documentation. You can ignore my request on quick suggestion about how to install any other packages in general. I think I will figure it out myself.
Thanks,
Minal

15

Hi Minal

A new NetworkManager based setup is now available on this branch: https://github.com/lueschem/edi-cl/tree/mender_upgrade_and_networking
As soon as I have done a bit more testing I will merge it to master.

Best regards
Matthias

16

Hi Matthias,
Many thanks for the quick update. I will have a look at the branch shortly.

Regards,
Minal

17

Hi Matthias,
I confirm that I could get the WiFi up with this branch. I have not done detailed testing but the basic test in terms of ability to bring up wifi works nicely.
So, my overall initial issue of the sdma and wifi gets resolved. Thanks a lot for your support and for the quick changes.

Thanks,
Minal