@agherzan commented on Wed Jul 27 2016

http://www.intel.co.uk/content/www/uk/en/nuc/change-the-game-with-nuc.html

[spanceac] uinput kernel module missing on Intel NUC images.
Needs to be activated by CONFIG_INPUT_UINPUT

Also we need to not allow the boot process to be stopped

https://github.com/balena-os/resin-intel/blob/f0df498b5324a946941ea50ebacc993f300745a2/genericx86-64.coffee#L38-L40

should be changed to point to https://www.balena.io/docs/learn/getting-started/intel-nuc/nodejs/

Hello!

I am have builded image with yocto for genericx86-64 and tried to boot my Gigabyte Brix GB BLCE-4105 with Intel Gemini Lake CPU J4105 but when i tried boot this box, i saw blank screen with cursor at the left top of screen. I tried build with compress option of barys and without it, but this is was without any success for me.

I use dd for flashing it to the SD card and HDD and tried to boot with USB and SATA, but without success. Can anybody help me, which step i can do wrong ?

After balena-os/meta-balena#891 is merged and release we should source the 99-resin-grub from there.

Hello!

Can anybody explain me how we can put files to the read/write mounts (/resin-data for example) during build resinOS image ?

Thanks!

Seems to be related to https://bugzilla.kernel.org/show_bug.cgi?id=200779
Updating the kernel to 4.19 or reverting torvalds/linux@e31f645 should fix it.

Front conversations

Hi there,

I followed these steps trying to use the 2.0.6-rev1 version for NUC:

$ time sudo resin local flash resin.img --drive /dev/disk4
? This will erase the selected drive. Are you sure? Yes
Flashing [========================] 100% eta 0s 
Validating [========================] 100% eta 0s 
sudo resin local flash resin-nuc-2.0.6-rev1.img --drive /dev/disk4  59.61s user 24.87s system 77% cpu 1:48.35 total

I inserted the hard drive into my NUC DN2820FYK (the older one from 2015 using 12v power). It seems to boot OK, but when I ssh it shows this:

local ➜  ~  ssh [email protected] -p22222
ssh_exchange_identification: read: Connection reset by peer
local ➜  ~  
local ➜  ~  ssh [email protected] -p22222
ssh: connect to host resin.local port 22222: Connection refused

So it seems on first connect it fails to ssh and then the ssh process dies completely? -- I also tried connecting an HDMI monitor and alt+f1 just shows the Resin splash screen (I tried waiting a while) and alt+f2 etc shows a blank screen.

When I try to reboot the unit, it can no longer boot and just shows me the Grub prompt :(

Any ideas?

Hi there,

I am trying your Resin img file on an Intel NUC and while it is working beautifully, I am not able to find the relevant files in /sys to check the CPU temperature.

I had a look and it seems these files are missing in /lib/modules:

/lib/modules/*/kernel/drivers/hwmon/coretemp.ko
/lib/modules/*/kernel/drivers/hwmon/nct6775.ko

Could these please be added in the next version?

Hello!

I am have builded image for genericx86-64 but some needed firmware not present here, but it need to use wifi on new inter brix. Here is this firmware:

iwlwifi-3168-21.ucode
iwlwifi-3168-22.ucode
iwlwifi-3168-27.ucode
iwlwifi-3168-29.ucode

I am added this manually, but i sure, many other people need it to be added to the
./layers/meta-resin/meta-resin-sumo/recipes-core/packagegroups/packagegroup-resin-connectivity.bbappend
./layers/poky/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb
inside this repo https://github.com/balena-os/resin-intel

Thank you!

The resin-image is currently unbootable. This image is not bootable as UEFI image nor as non-UEFI one. The resin-image used to be bootable in the past (can't remember what was the default mode).

The Intel Dual Band Wireless-AC 9560 firmware was supposed to be included in v2.27, but it looks like we did not do that, as we did not properly manage the flow of the previously reported issue.
The needed firmware is iwlwifi-9000-pu-b0-jf-b0-34.ucode

Front conversations

I am in the process of trying to create the build myself, but it would be much appreciated if you folks would consider adding this firmware. Thank You
https://github.com/hadess/rtl8723bs

Observed on the Intel Compute Stick

Front conversations

In latest OS releases (2.44.0+rev1) the shutdown command takes a while to complete.

Ran this on Resin OS 2.12.0+rev1 (prod)

root@5ac66e4:~# modprobe cdc_acm
modprobe: FATAL: Module cdc_acm not found in directory /lib/modules/4.12.12-yocto-standard

In this thread https://app.frontapp.com/open/cnv_tx9xyr the customer is trying to get greengrass working, but cannot because overlayFS is not available. It should be. Florin has agreed to put it in.

5th gen NUCs print the following while they boot:

[    0.873360] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-13.ucode failed with error -2
[    0.873366] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-12.ucode failed with error -2
[    0.873367] iwlwifi 0000:02:00.0: request for firmware file 'iwlwifi-7265D-12.ucode' failed.
[    0.873371] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-11.ucode failed with error -2
[    0.873372] iwlwifi 0000:02:00.0: request for firmware file 'iwlwifi-7265D-11.ucode' failed.
[    0.875961] iwlwifi 0000:02:00.0: New firmware can be obtained from http://www.intellinuxwireless.org/.
[    0.876130] iwlwifi 0000:02:00.0: loaded firmware version 23.15.10.0 op_mode iwlmvm

5th Gen NUCs print the following when they boot:

[    1.703892] bluetooth hci0: Direct firmware load for intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq failed with error -2
[    1.705303] Bluetooth: hci0 failed to open Intel firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq(-2)
[    1.706739] bluetooth hci0: Direct firmware load for intel/ibt-hw-37.8.bseq failed with error -2

Also, remove https://github.com/resin-os/resin-intel/blob/master/intel-nuc.svg

Provisioned some devices following this guide, and seems like the partition expansion does not happen correctly.

root@3b072fe:~# df -h
Filesystem                      Size  Used Avail Use% Mounted on
devtmpfs                        993M     0  993M   0% /dev
/dev/disk/by-label/resin-rootA  300M  227M   54M  81% /mnt/sysroot/active
none                            300M  227M   54M  81% /
tmpfs                          1000M   28K 1000M   1% /dev/shm
tmpfs                          1000M  4.1M  996M   1% /run
tmpfs                          1000M     0 1000M   0% /sys/fs/cgroup
tmpfs                          1000M     0 1000M   0% /tmp
tmpfs                          1000M   28K 1000M   1% /var/volatile
/dev/sda5                        19M  200K   17M   2% /mnt/state
/dev/sda1                        40M   12M   28M  30% /mnt/boot
/dev/sda6                       960M  199M  694M  23% /mnt/data
/dev/sda3                       300M  2.2M  278M   1% /mnt/sysroot/inactive

The resize service:

root@3b072fe:~# systemctl status resin-filesystem-expand.service
● resin-filesystem-expand.service - Expand resin-data partition
   Loaded: loaded (/lib/systemd/system/resin-filesystem-expand.service; enabled; vendor preset: enabled)
   Active: active (exited) since Thu 2018-07-26 14:05:39 UTC; 1min 51s ago
  Process: 410 ExecStart=/bin/sh /usr/bin/resin-filesystem-expand (code=exited, status=0/SUCCESS)
 Main PID: 410 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/resin-filesystem-expand.service

Jul 26 14:05:38 localhost systemd[1]: Starting Expand resin-data partition...
Jul 26 14:05:39 localhost sh[410]: [INFO] Filesystem check on /dev/disk/by-label/resin-data...
Jul 26 14:05:39 localhost sh[410]: e2fsck 1.43.5 (04-Aug-2017)
Jul 26 14:05:39 localhost sh[410]: resin-data: clean, 2686/131072 files, 28468/262144 blocks
Jul 26 14:05:39 localhost sh[410]: [INFO] Expand ext4 filesystem on /dev/disk/by-label/resin-data...
Jul 26 14:05:39 localhost sh[410]: resize2fs 1.43.5 (04-Aug-2017)
Jul 26 14:05:39 localhost sh[410]: Resizing the filesystem on /dev/disk/by-label/resin-data to 263168 (4k) blocks.
Jul 26 14:05:39 localhost sh[410]: The filesystem on /dev/disk/by-label/resin-data is now 262144 (4k) blocks long.
Jul 26 14:05:39 localhost systemd[1]: Started Expand resin-data partition.

And fdisk:

Device     Boot   Start     End Sectors  Size Id Type
/dev/sdb1  *       8192   90111   81920   40M  e W95 FAT16 (LBA)
/dev/sdb2         90112 5210111 5120000  2.5G 83 Linux
/dev/sdb3       5210112 5218303    8192    4M 83 Linux
/dev/sdb4       5218304 5259263   40960   20M  f W95 Ext'd (LBA)
/dev/sdb5       5226496 5234687    8192    4M 83 Linux
/dev/sdb6       5242880 5259263   16384    8M 83 Linux

Seems like all resinOS 2.x is affected.

• 1.26.0 expands properly
• tested 2.0.0+rev3, 2.2.0, 2.12.7, 2.13.6, none of them expands properly

Flowdock

[removed]

For this device

root@462a4e8:~# cat /etc/os-release
ID="resin-os"
NAME="Resin OS"
VERSION="2.13.6+rev1"
VERSION_ID="2.13.6"
PRETTY_NAME="Resin OS 2.13.6+rev1"
RESIN_BOARD_REV="c561fa5"
META_RESIN_REV="e167839"
SLUG="intel-nuc"
MACHINE="genericx86-64"
VARIANT="Development"
VARIANT_ID="dev"

The log is full of these error messages

root@462a4e8:~# journalctl -f -a
-- Logs begin at Tue 2018-08-07 06:29:29 UTC. --
Aug 07 11:27:35 462a4e8 systemd[1]: Started Serial Getty on ttyS0.
Aug 07 11:27:35 462a4e8 agetty[14865]: /dev/ttyS0: not a tty
Aug 07 11:27:45 462a4e8 systemd[1]: [email protected]: Service has no hold-off time, scheduling restart.
Aug 07 11:27:45 462a4e8 systemd[1]: Stopped Serial Getty on ttyS0.
Aug 07 11:27:45 462a4e8 systemd[1]: Started Serial Getty on ttyS0.
Aug 07 11:27:45 462a4e8 agetty[14903]: /dev/ttyS0: not a tty
Aug 07 11:27:55 462a4e8 systemd[1]: [email protected]: Service has no hold-off time, scheduling restart.
Aug 07 11:27:55 462a4e8 systemd[1]: Stopped Serial Getty on ttyS0.
Aug 07 11:27:55 462a4e8 systemd[1]: Started Serial Getty on ttyS0.
Aug 07 11:27:55 462a4e8 agetty[14904]: /dev/ttyS0: not a tty
Aug 07 11:28:05 462a4e8 systemd[1]: [email protected]: Service has no hold-off time, scheduling restart.
Aug 07 11:28:05 462a4e8 systemd[1]: Stopped Serial Getty on ttyS0.
Aug 07 11:28:05 462a4e8 systemd[1]: Started Serial Getty on ttyS0.
Aug 07 11:28:05 462a4e8 agetty[14907]: /dev/ttyS0: not a tty
Aug 07 11:28:15 462a4e8 systemd[1]: [email protected]: Service has no hold-off time, scheduling restart.
Aug 07 11:28:15 462a4e8 systemd[1]: Stopped Serial Getty on ttyS0.
Aug 07 11:28:15 462a4e8 systemd[1]: Started Serial Getty on ttyS0.
Aug 07 11:28:15 462a4e8 agetty[14943]: /dev/ttyS0: not a tty
Aug 07 11:28:25 462a4e8 systemd[1]: [email protected]: Service has no hold-off time, scheduling restart.
Aug 07 11:28:25 462a4e8 systemd[1]: Stopped Serial Getty on ttyS0.
Aug 07 11:28:25 462a4e8 systemd[1]: Started Serial Getty on ttyS0.
Aug 07 11:28:25 462a4e8 agetty[14945]: /dev/ttyS0: not a tty

Looks like resinOS does not find any storage device (should be probably mmcblk0)

Front conversations

relevant flowdock conv

The kernel configuration currently available is customized for the Intel NUC.
In order to boot BalenaOS on a broader range of Intel based devices, a generic Linux kernel configuration file that compiled many more modules is required.

We would like to have TPM 2.0 support in Balena on the Intel NUC platform.

Use Case

We're using TPM 2.0 modules to sign tokens on the edge to identify edge devices to our cloud tier. Using the TPM is more secure than storing certs on the device because the private key never leaves the TPM.

Solution

Add kernel support for TPM. I'm not sure exactly what modules will need to be included, but there are some clues here:

https://askubuntu.com/questions/414747/does-ubuntu-use-tpm-2-0-chip

Expected Interfaces

When TPM 2.0 support is present, we expect to see the following files:

/dev/tpm0
/dev/tpmrm0

Original forum thread:
https://forums.balena.io/t/intel-nuc-and-tpm/3785/18

Hi guys,

So I'm new to Balena and have been trying to build a large scale 'kiosk' deployment using the platform....

In essence:

• I'm running the Balena Intel OS on a bunch of Intel Compute Sticks (So I can use GPU)
• I've got a multi-container deployment with various micro-services running on the stick, one-of which is Chromium on top of x11...
• In order to track the insert/removal of portable media devices (USB Sticks) I'm monitoring udev messages, and hooking various services inside the x11 container with systemd (this container also has dbus enabled in it)....
• If a systemd service in the x11 container fails to properly stop, and I issue new release code, the system will try and stop/restart the containers (as expected) HOWEVER... the messages from the child container seem to hook into the host balena-os, giving the following message in the balena cloud: balena "Failed to activate service 'org.freedesktop.systemd1':".

The problem, is that once this has happened - it's virtually impossible to recover the device - if you reboot it, the device will just be stuck with: random: crng init done messages in the boot log which seems to block the rest of the OS services (such as networking etc) from loading...

Not an issue today because I'm still developing, so I can just reflash the device, however if this was in the field with this bug - we'd be recalling 100's of devices...

Happy to give you Balena cloud access to my container/git if you need to recreate the bug also.

Cheers,

I am running Debian 9 with gcc 6.30 and this build is failing on a past issue fixed by: balena-os/meta-balena#430

omar@omarsbox:/mnt/hdd/src/resin-intel/build$ MACHINE=genericx86-64 bitbake ucl-native
WARNING: Host distribution "debian-9" has not been validated with this version of the build system; y
ou may possibly experience unexpected failures. It is recommended that you use a tested distribution.
Loading cache: 100% |#################################################################| Time: 0:00:00
Loaded 2745 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION        = "1.34.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "x86_64-poky-linux"
MACHINE           = "genericx86-64"
DISTRO            = "resin-os"
DISTRO_VERSION    = "2.9.7"
TUNE_FEATURES     = "m64 core2"
TARGET_FPU        = ""
meta
meta-poky
meta-yocto-bsp    = "HEAD:827eb5b232d54909377e2b18d39d34d6c1c21413"
meta-oe
meta-filesystems
meta-networking
meta-python       = "HEAD:dfbdd28d206a74bf264c2f7ee0f7b3e5af587796"
meta-resin-common
meta-resin-pyro   = "HEAD:585641b7196b3ef1edddf32ff71819564aa6edc5"
meta-resin-genericx86 = "master:ed59bef8e8c6633b8f688ebe11ca5c20398d3362"
meta-rust         = "HEAD:f6d973c5cacb9b52f32118caa879dcc7922d3c98"

Initialising tasks: 100% |############################################################| Time: 0:00:00
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: ucl-native-1.03-r0 do_configure: configure failed
ERROR: ucl-native-1.03-r0 do_configure: Function failed: do_configure (log file is located at /mnt/hd
d/src/resin-intel/build/tmp/work/x86_64-linux/ucl-native/1.03-r0/temp/log.do_configure.25848)        ERROR: Logfile of failure stored in: /mnt/hdd/src/resin-intel/build/tmp/work/x86_64-linux/ucl-native/
1.03-r0/temp/log.do_configure.25848
...
| checking whether your compiler passes the ACC conformance test... FAILED
| configure:
| configure: Your compiler failed the ACC conformance test - for details see
| configure: `config.log'. Please check that log file and consider sending
| configure: a patch or bug-report to <[email protected]>.
| configure: Thanks for your support.
| configure:
| configure: error: ACC conformance test failed. Stop.
| ERROR: Function failed: do_configure (log file is located at /mnt/hdd/src/resin-intel/build/tmp/work/x86_64-linux/ucl-native/1.03-r0/temp/log.do_configure.25848)

Ideas for further debugging?

Front conversations

I'm trying to boot ResinOS on the Gigabyte Brix GB-BXBT-1900 (https://www.gigabyte.com/Mini-PcBarebone/GB-BXBT-1900-rev-10) but for some reason I'm just getting a blank screen.

The Brix is quite similar to the NUC in terms of dimensions and specs and I am able to use Ubuntu Server on it. When using Ubuntu Server I normally put the following in /etc/default/grub for both the NUC and Brix, otherwise, it sometimes fails to reboot:

GRUB_RECORDFAIL_TIMEOUT=30
GRUB_TIMEOUT=0
GRUB_CMDLINE_LINUX="text nomodeset intel_idle.max_cstate=1"
GRUB_TERMINAL="console"

Any advice how to troubleshoot?

This behavior is new. I have had to erase partition tables in between flashes or it stalls. Reproduced on two different model NUCs. intel-nuc-2.31.2+rev1-dev-v9.11.1

Intel NUC built in bluetooth controller not recognized
https://forums.balena.io/t/intel-nuc-built-in-bluetooth-controller-not-recognized/6441

• NUC model number BLKNUC7i7DNH1E
• balenaOS v2.32.0+rev2

$ dmesg
[ 3.605811] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-9260-th-b0-jf-b0-36.ucode failed with error -2
[ 3.605817] bluetooth hci0: Direct firmware load for intel/ibt-18-16-1.sfi failed with error -2
[ 3.605821] Bluetooth: hci0: Failed to load Intel firmware file (-2)

Front conversations

root@90d75f6:~# dmesg|grep -i firmware
[ 0.144697] Spectre V2 : Enabling Restricted Speculation for firmware calls
[ 0.263019] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 2.885496] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
[ 2.888519] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 2.920347] [drm] HuC: Loaded firmware i915/kbl_huc_ver02_00_1810.bin (version 2.0)
[ 2.931347] [drm] GuC: Loaded firmware i915/kbl_guc_ver9_39.bin (version 9.39)
[ 2.943113] i915 0000:00:02.0: GuC firmware version 9.39
[ 20.066524] mwifiex_pcie 0000:01:00.0: == mwifiex firmware dump start ==
[ 34.986274] mwifiex_pcie 0000:01:00.0: Ignore scan. Card removed or firmware in bad state
[ 34.991677] mwifiex_pcie 0000:01:00.0: Ignore scan. Card removed or firmware in bad state
[ 37.963917] mwifiex_pcie 0000:01:00.0: Ignore scan. Card removed or firmware in bad state
[ 60.971929] mwifiex_pcie 0000:01:00.0: Ignore scan. Card removed or firmware in bad state
[ 62.403611] mwifiex_pcie 0000:01:00.0: Firmware dump Finished!
[ 62.403612] mwifiex_pcie 0000:01:00.0: == mwifiex firmware dump end ==

and

root@90d75f6:~# dmesg|grep -i wifi
[ 2.893913] mwifiex_pcie 0000:01:00.0: enabling device (0000 -> 0002)
[ 2.894062] mwifiex_pcie: try set_consistent_dma_mask(32)
[ 2.894079] mwifiex_pcie: PCI memory map Virt0: 00000000d02e78af PCI memory map Virt2: 0000000003f4fb8d
[ 4.206077] mwifiex_pcie 0000:01:00.0: info: FW download over, size 723540 bytes
[ 5.250428] mwifiex_pcie 0000:01:00.0: WLAN FW is active
[ 5.306980] mwifiex_pcie 0000:01:00.0: Unknown api_id: 4
[ 5.329940] mwifiex_pcie 0000:01:00.0: info: MWIFIEX VERSION: mwifiex 1.0 (15.68.19.p21)
[ 5.329942] mwifiex_pcie 0000:01:00.0: driver_version = mwifiex 1.0 (15.68.19.p21)
[ 5.331176] mwifiex_pcie 0000:01:00.0 wlp1s0: renamed from mlan0
[ 20.065354] mwifiex_pcie 0000:01:00.0: mwifiex_cmd_timeout_func: Timeout cmd id = 0xf7, act = 0x2
[ 20.065371] mwifiex_pcie 0000:01:00.0: num_data_h2c_failure = 0
[ 20.065379] mwifiex_pcie 0000:01:00.0: num_cmd_h2c_failure = 0
[ 20.065385] mwifiex_pcie 0000:01:00.0: is_cmd_timedout = 1
[ 20.065391] mwifiex_pcie 0000:01:00.0: num_tx_timeout = 0
[ 20.065395] mwifiex_pcie 0000:01:00.0: last_cmd_index = 0
[ 20.065400] mwifiex_pcie 0000:01:00.0: last_cmd_id: f7 00 10 00 28 00 0c 01 4d 00
[ 20.065404] mwifiex_pcie 0000:01:00.0: last_cmd_act: 02 00 01 00 13 00 01 00 01 00
[ 20.065409] mwifiex_pcie 0000:01:00.0: last_cmd_resp_index = 4
[ 20.065413] mwifiex_pcie 0000:01:00.0: last_cmd_resp_id: 07 81 10 80 28 80 0c 81 4d 80
[ 20.065417] mwifiex_pcie 0000:01:00.0: last_event_index = 1
[ 20.065422] mwifiex_pcie 0000:01:00.0: last_event: 0b 00 0a 00 58 00 58 00 58 00
[ 20.065427] mwifiex_pcie 0000:01:00.0: data_sent=0 cmd_sent=1
[ 20.065431] mwifiex_pcie 0000:01:00.0: ps_mode=1 ps_state=0
[ 20.065727] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.065883] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.066147] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.066225] mwifiex_pcie 0000:01:00.0: ===mwifiex driverinfo dump start===
[ 20.066233] mwifiex_pcie 0000:01:00.0: info: MWIFIEX VERSION: mwifiex 1.0 (15.68.19.p21)
[ 20.066249] mwifiex_pcie 0000:01:00.0: PCIE register dump start
[ 20.066357] mwifiex_pcie 0000:01:00.0: pcie scratch register:
[ 20.066457] mwifiex_pcie 0000:01:00.0: reg:0xcf0, value=0xfedcba00
[ 20.066462] mwifiex_pcie 0000:01:00.0: PCIE register dump end
[ 20.066513] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.066520] mwifiex_pcie 0000:01:00.0: ===mwifiex driverinfo dump end===
[ 20.066524] mwifiex_pcie 0000:01:00.0: == mwifiex firmware dump start ==
[ 20.072798] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.072799] mwifiex_pcie 0000:01:00.0: deleting the crypto keys
[ 20.072810] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.072811] mwifiex_pcie 0000:01:00.0: deleting the crypto keys
[ 20.072820] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.072821] mwifiex_pcie 0000:01:00.0: deleting the crypto keys
[ 20.072829] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.072830] mwifiex_pcie 0000:01:00.0: deleting the crypto keys
[ 20.073044] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.073046] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.073047] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.073048] mwifiex_pcie 0000:01:00.0: Failed to set AP configuration
[ 20.073049] mwifiex_pcie 0000:01:00.0: Failed to start AP
[ 20.073078] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.073079] mwifiex_pcie 0000:01:00.0: deleting the crypto keys
[ 20.073089] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.073089] mwifiex_pcie 0000:01:00.0: deleting the crypto keys
[ 20.073099] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.073100] mwifiex_pcie 0000:01:00.0: deleting the crypto keys
[ 20.073112] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.073113] mwifiex_pcie 0000:01:00.0: deleting the crypto keys
[ 20.073172] mwifiex_pcie 0000:01:00.0: wlp1s0: changing to 2 not supported
[ 20.073184] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.073194] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.073203] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.073203] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.075141] mwifiex_pcie 0000:01:00.0: wlp1s0: changing to 2 not supported
[ 20.075156] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.075157] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.075170] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.075171] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.076251] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.076252] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.099501] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.099534] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.099664] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.099924] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.099926] mwifiex_pcie 0000:01:00.0: deleting the crypto keys
[ 20.099943] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.099944] mwifiex_pcie 0000:01:00.0: deleting the crypto keys
[ 20.099960] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.099961] mwifiex_pcie 0000:01:00.0: deleting the crypto keys
[ 20.099977] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.099978] mwifiex_pcie 0000:01:00.0: deleting the crypto keys
[ 20.100027] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.100029] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.100030] mwifiex_pcie 0000:01:00.0: Failed to set AP configuration
[ 20.100031] mwifiex_pcie 0000:01:00.0: Failed to start AP
[ 20.100075] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.100076] mwifiex_pcie 0000:01:00.0: deleting the crypto keys
[ 20.100093] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.100094] mwifiex_pcie 0000:01:00.0: deleting the crypto keys
[ 20.100109] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.100111] mwifiex_pcie 0000:01:00.0: deleting the crypto keys
[ 20.100126] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.100127] mwifiex_pcie 0000:01:00.0: deleting the crypto keys
[ 20.100192] mwifiex_pcie 0000:01:00.0: wlp1s0: changing to 2 not supported
[ 20.100204] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.100218] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.100231] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.100233] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.103961] mwifiex_pcie 0000:01:00.0: wlp1s0: changing to 2 not supported
[ 20.103994] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.103997] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.104023] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.104025] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.104070] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 20.104073] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 34.965085] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 34.965097] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 34.965098] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 34.967566] mwifiex_pcie 0000:01:00.0: wlp1s0: changing to 2 not supported
[ 34.967581] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 34.967582] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 34.967599] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 34.967601] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 34.967633] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 34.967635] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 34.969862] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 34.969863] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[ 34.986274] mwifiex_pcie 0000:01:00.0: Ignore scan. Card removed or firmware in bad state
[ 34.986276] mwifiex_pcie 0000:01:00.0: scan failed: -14
[ 34.991677] mwifiex_pcie 0000:01:00.0: Ignore scan. Card removed or firmware in bad state
[ 34.991679] mwifiex_pcie 0000:01:00.0: scan failed: -14
[ 37.963917] mwifiex_pcie 0000:01:00.0: Ignore scan. Card removed or firmware in bad state
[ 37.963919] mwifiex_pcie 0000:01:00.0: scan failed: -14
[ 60.971929] mwifiex_pcie 0000:01:00.0: Ignore scan. Card removed or firmware in bad state
[ 60.971931] mwifiex_pcie 0000:01:00.0: scan failed: -14
[ 62.403611] mwifiex_pcie 0000:01:00.0: Firmware dump Finished!
[ 62.403612] mwifiex_pcie 0000:01:00.0: == mwifiex firmware dump end ==
[ 62.403781] mwifiex_pcie 0000:01:00.0: == mwifiex dump information to /sys/class/devcoredump start
[ 62.403811] mwifiex_pcie 0000:01:00.0: == mwifiex dump information to /sys/class/devcoredump end
[ 62.403834] mwifiex_pcie 0000:01:00.0: info: shutdown mwifiex...
[ 62.406223] mwifiex_pcie 0000:01:00.0: PREP_CMD: card is removed
[ 62.406226] mwifiex_pcie 0000:01:00.0: PREP_CMD: card is removed
[ 62.406227] mwifiex_pcie 0000:01:00.0: PREP_CMD: card is removed
[ 63.484850] mwifiex_pcie 0000:01:00.0: WLAN FW already running! Skip FW dnld
[ 63.484854] mwifiex_pcie 0000:01:00.0: WLAN FW is active
[ 73.787985] mwifiex_pcie 0000:01:00.0: mwifiex_cmd_timeout_func: Timeout cmd id = 0xfa, act = 0xf000
[ 73.788004] mwifiex_pcie 0000:01:00.0: num_data_h2c_failure = 0
[ 73.788014] mwifiex_pcie 0000:01:00.0: num_cmd_h2c_failure = 0
[ 73.788019] mwifiex_pcie 0000:01:00.0: is_cmd_timedout = 1
[ 73.788025] mwifiex_pcie 0000:01:00.0: num_tx_timeout = 0
[ 73.788033] mwifiex_pcie 0000:01:00.0: last_cmd_index = 1
[ 73.788039] mwifiex_pcie 0000:01:00.0: last_cmd_id: f7 00 fa 00 28 00 0c 01 4d 00
[ 73.788046] mwifiex_pcie 0000:01:00.0: last_cmd_act: 02 00 00 f0 13 00 01 00 01 00
[ 73.788052] mwifiex_pcie 0000:01:00.0: last_cmd_resp_index = 4
[ 73.788060] mwifiex_pcie 0000:01:00.0: last_cmd_resp_id: 07 81 10 80 28 80 0c 81 4d 80
[ 73.788066] mwifiex_pcie 0000:01:00.0: last_event_index = 1
[ 73.788072] mwifiex_pcie 0000:01:00.0: last_event: 0b 00 0a 00 58 00 58 00 58 00
[ 73.788080] mwifiex_pcie 0000:01:00.0: data_sent=0 cmd_sent=1
[ 73.788087] mwifiex_pcie 0000:01:00.0: ps_mode=0 ps_state=0
[ 73.788118] mwifiex_pcie 0000:01:00.0: info: _mwifiex_fw_dpc: unregister device

Steps to reproduce issue

Connect to the HDMI connected to a monitor
Boot the device

Expected result

Resin logo splash screen should be visible

Actual result

Logo is not displayed at boot-up. The HDMI screen shows only the boot log

Notes:

• boot may be too fast to actually have time to show the logo.
• needs some testing on a different HDMI screen as the one I am using loses signal for a short period of time during boot-up

At reboot and shutdown, the logo is displayed correctly

Other information

Reported by: Florin Sarbu

Test configuration: NUC

Test case number: TC07

Test run: https://resinio.testlodge.com/projects/16238/runs/196239?tab=2&run_section_id=176152&executed_case_id=9459437#executed_case_9459437

Looks like something is missing from the kernel to support ipset:

root@intel-corei7-64-06fd714:/# ipset create domain-filter-ipv4 hash:net                                                                   
ipset v6.23: Kernel error received: Invalid argument                                                                                       

root@intel-corei7-64-06fd714:/# ipset list                                                                                                 
ipset v6.23: Kernel error received: Invalid argument   

The same works fine on the RPi1, RPi2 and RPi3 builds.

This one is a show-stopper.

Front conversations

The Intel RealSense kernel module

I am looking to be able to run this code on a NUC-like device, and I would like it to have the same workflow as the Raspberry Pi and Odroid devices. That way I can boot the OS from the MicroSD card, and always be running off the MicroSD card.

The part which seems most promising to me is here:
On the Pi3:
raspberrypi3.coffee

	yocto:
		machine: 'raspberrypi3'
		image: 'resin-image'
		fstype: 'resinos-img'
		version: 'yocto-warrior'
		deployArtifact: 'resin-image-raspberrypi3.resinos-img'
		compressed: true

On the NUC:
genericx86-64.coffee

	yocto:
		machine: 'genericx86-64'
		image: 'resin-image-flasher'
		fstype: 'resinos-img'
		version: 'yocto-warrior'
		deployArtifact: 'resin-image-flasher-genericx86-64.resinos-img'
		compressed: true

If I just switched from resin-image-flasher to resin-image, would that create a non-flasher image?

Is there anything special that I need to put into the local.conf file? If I just change this .coffee file will the barys build program build correctly?

My first attempt at a contribution at Balena, thanks for any help!

Hello!

We try to start docker container inside balena os, based on resin/amd64-debian:stretch and
amd64/ubuntu:bionic. And fist started correctly and i can see mouse and operate mouse and keyboard. But we want use Ubuntu, and how o start x11/chrome - see cursor but do not operate mouse or keyboard - i see no any reaction. Can anybody explain me, what i can do wrong ? And can we use dockerfiles from other repository, not resin, for start x11/chrome inside and use keyboard and mouse ?

Thank you!

The needed firmware is iwlwifi-8000*

Device

• Jetson Nano
• Intel® Dual Band Wireless-AC 8265 M.2 card
• Dashboard link
  • support access enabled for 1 week

Firmware

• Intel firmwares
  • Intel® Dual Band Wireless-AC 8265 firmware
  • AC 8265 firmware size is 1,811,984 bytes (1.8 MB)

Workaround

Here's what I did:

• Download firmware
• Mount SD card on a computer
• Put the firmware into /lib/firmware
• Unmount SD card and put it back to Jetson Nano
• Boot Jetson Nano

WiFi

dmesg | grep iwlwifi:

[   11.233465] iwlwifi 0000:01:00.0: enabling device (0000 -> 0002)
[   11.235647] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-8265-26.ucode failed with error -2
[   11.235650] iwlwifi 0000:01:00.0: Falling back to user helper
[   11.353231] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-8265-25.ucode failed with error -2
[   11.429465] iwlwifi 0000:01:00.0: Falling back to user helper
[   11.431960] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-8265-24.ucode failed with error -2
[   11.431963] iwlwifi 0000:01:00.0: Falling back to user helper
[   11.434654] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-8265-23.ucode failed with error -2
[   11.434656] iwlwifi 0000:01:00.0: Falling back to user helper
[   11.458543] iwlwifi 0000:01:00.0: loaded firmware version 22.361476.0 op_mode iwlmvm
[   11.519283] iwlwifi 0000:01:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230
[   11.530281] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[   11.539865] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[   11.677210] thermal thermal_zone6: Registering thermal zone thermal_zone6 for type iwlwifi
[   12.829112] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[   12.835114] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[   12.958584] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[   12.964618] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[   13.046335] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[   13.052750] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[   13.175074] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[   13.181039] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[   16.707338] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[   16.714139] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[   16.836336] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[   16.844134] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled

ifconfig wlan0:

wlan0     Link encap:Ethernet  HWaddr A0:51:0B:4A:6F:05  
          inet addr:192.168.1.70  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::91cd:389a:7706:3a87/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:545 errors:0 dropped:0 overruns:0 frame:0
          TX packets:465 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:84943 (82.9 KiB)  TX bytes:84346 (82.3 KiB)

Bluetooth

dmesg | grep -i bluetooth

[    0.586367] Bluetooth: Core ver 2.22
[    0.586448] Bluetooth: HCI device and connection manager initialized
[    0.586467] Bluetooth: HCI socket layer initialized
[    0.586481] Bluetooth: L2CAP socket layer initialized
[    0.586509] Bluetooth: SCO socket layer initialized
[    3.666372] Bluetooth: RFCOMM socket layer initialized
[    3.666383] Bluetooth: RFCOMM ver 1.11
[    3.666387] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    3.666391] Bluetooth: HIDP socket layer initialized
[   11.200316] Bluetooth: hci0: Bootloader revision 0.0 build 26 week 38 2015
[   11.201358] Bluetooth: hci0: Device revision is 16
[   11.201360] Bluetooth: hci0: Secure boot is enabled
[   11.201362] Bluetooth: hci0: OTP lock is enabled
[   11.201364] Bluetooth: hci0: API lock is enabled
[   11.201365] Bluetooth: hci0: Debug lock is disabled
[   11.201368] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   11.206111] bluetooth hci0: Direct firmware load for intel/ibt-12-16.sfi failed with error -2
[   11.206114] bluetooth hci0: Falling back to user helper
[   11.359560] Bluetooth: hci0: Failed to load Intel firmware file (-11)
[   11.364376] Bluetooth: hci0: Bootloader revision 0.0 build 26 week 38 2015
[   11.365391] Bluetooth: hci0: Device revision is 16
[   11.365394] Bluetooth: hci0: Secure boot is enabled
[   11.365395] Bluetooth: hci0: OTP lock is enabled
[   11.365397] Bluetooth: hci0: API lock is enabled
[   11.365399] Bluetooth: hci0: Debug lock is disabled
[   11.365401] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   11.365436] bluetooth hci0: Direct firmware load for intel/ibt-12-16.sfi failed with error -2
[   11.365438] bluetooth hci0: Falling back to user helper
[   11.371733] Bluetooth: hci0: Failed to load Intel firmware file (-11)
[   12.021478] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   12.026981] Bluetooth: BNEP socket layer initialized

hcitool scan:

Device is not available: No such device

Therefore, it requires the user to manually shutdown.