# General Discussions

**URL:** https://hub.mender.io/c/general-discussions/12.md?page=76

[Latest](https://hub.mender.io/latest.md) · [Categories](https://hub.mender.io/categories.md) · [Tags](https://hub.mender.io/tags.md)

**Page:** 77

---

## [Change Screen Resolution of .biosimg in GRUB](https://hub.mender.io/t/change-screen-resolution-of-biosimg-in-grub/975)

<div class="topic-metadata">

**Author:** [@Alex](https://hub.mender.io/u/Alex)\
**Replies:** 2\
**Last updated:** [September 2, 2019, 2:50pm UTC](https://hub.mender.io/t/change-screen-resolution-of-biosimg-in-grub/975 "2019-09-02T14:50:32Z")

</div>

Hi Guys, I’m in a bit of trouble with configuring the screen resolution of my .biosimg. It seems to be 640x480 by default but I can’t change it to 1920x1080x32 with gfxpayload or similar GRUB settings. Do you can tell …

---

## [Function failed: do\_image\_biosimg](https://hub.mender.io/t/function-failed-do-image-biosimg/966)

<div class="topic-metadata">

**Author:** [@Alex](https://hub.mender.io/u/Alex)\
**Replies:** 2\
**Last updated:** [August 27, 2019, 12:43pm UTC](https://hub.mender.io/t/function-failed-do-image-biosimg/966 "2019-08-27T12:43:34Z")

</div>

Hi Folks! I’m trying to bitbake a core-image-full-cmdline.biosimg. In my local.conf I set INHERIT += "mender-full-bios" and it throws the error Function failed: do\_image\_biosimg. This is the log: ERROR: core-image-min…

---

## [Yocto Image wont boot from SSD](https://hub.mender.io/t/yocto-image-wont-boot-from-ssd/923)

<div class="topic-metadata">

**Author:** [@Alex](https://hub.mender.io/u/Alex)\
**Replies:** 24\
**Last updated:** [August 27, 2019, 10:09am UTC](https://hub.mender.io/t/yocto-image-wont-boot-from-ssd/923 "2019-08-27T10:09:32Z")

</div>

Hi Guys! I created a core-image-full-cmdline Image for the intel-corei7-64 machine and have some big troubles booting it via grub (and everything else). The Image boots without any trouble from a usb drive but when I dd…

---

## [Problems booting from version 2 artifact following successful download to device](https://hub.mender.io/t/problems-booting-from-version-2-artifact-following-successful-download-to-device/961)

<div class="topic-metadata">

**Author:** [@beruti](https://hub.mender.io/u/beruti)\
**Replies:** 7\
**Last updated:** [August 27, 2019, 6:14am UTC](https://hub.mender.io/t/problems-booting-from-version-2-artifact-following-successful-download-to-device/961 "2019-08-27T06:14:37Z")

</div>

Hi @mirzak, Been trying to follow through that mega thread rossbcan created and the subsequent integration page and have made great progress, integrating mender with the nanopineo2 with musl, which I have you both to th…

---

## [U-boot environment located past 0xFFFFFFFF fails](https://hub.mender.io/t/u-boot-environment-located-past-0xffffffff-fails/861)

<div class="topic-metadata">

**Author:** [@dwalkes](https://hub.mender.io/u/dwalkes)\
**Replies:** 8\
**Last updated:** [August 26, 2019, 5:32pm UTC](https://hub.mender.io/t/u-boot-environment-located-past-0xffffffff-fails/861 "2019-08-26T17:32:51Z")

</div>

Hi Folks, I’m working on an update for the mender tegra port which will allow users to specify larger rootfs sizes. The tegra platform has a very specific and unique flash layout, with a bunch of reserved flash sectors…

---

## [Self-hosted Mender 2.1 - Bug report: GATEWAY\_IP not set in default config](https://hub.mender.io/t/self-hosted-mender-2-1-bug-report-gateway-ip-not-set-in-default-config/959)

<div class="topic-metadata">

**Author:** [@will](https://hub.mender.io/u/will)\
**Replies:** 1\
**Last updated:** [August 23, 2019, 1:12pm UTC](https://hub.mender.io/t/self-hosted-mender-2-1-bug-report-gateway-ip-not-set-in-default-config/959 "2019-08-23T13:12:32Z")

</div>

I just followed the instructions at https://docs.mender.io/2.1/administration/production-installation and lost some time before finding that I had to set the undocumented GATEWAY\_IP. Symptoms: The RELEASES page fails …

---

## [Reading logs for deployments?](https://hub.mender.io/t/reading-logs-for-deployments/953)

<div class="topic-metadata">

**Author:** [@MBConsultingUK](https://hub.mender.io/u/MBConsultingUK)\
**Replies:** 3\
**Last updated:** [August 22, 2019, 5:48am UTC](https://hub.mender.io/t/reading-logs-for-deployments/953 "2019-08-22T05:48:37Z")

</div>

Hey folks, I’m up and running with Mender, my Pi is connected, the Artifact is being built and uploaded from Jenkins via the API, and I can see it sat in the release tab and in the S3 bucket. The problem I have is that…

---

## [Integration of NVIDIA Tegra Jetson TX2](https://hub.mender.io/t/integration-of-nvidia-tegra-jetson-tx2/927)

<div class="topic-metadata">

**Author:** [@MarekBelisko](https://hub.mender.io/u/MarekBelisko)\
**Replies:** 7\
**Last updated:** [August 20, 2019, 3:34pm UTC](https://hub.mender.io/t/integration-of-nvidia-tegra-jetson-tx2/927 "2019-08-20T15:34:01Z")

</div>

---

## [Issue With Mender 2.0 UI - Blank Release List Page](https://hub.mender.io/t/issue-with-mender-2-0-ui-blank-release-list-page/619)

<div class="topic-metadata">

**Author:** [@alkindirizky](https://hub.mender.io/u/alkindirizky)\
**Replies:** 11\
**Last updated:** [August 19, 2019, 3:34pm UTC](https://hub.mender.io/t/issue-with-mender-2-0-ui-blank-release-list-page/619 "2019-08-19T15:34:17Z")

</div>

Hi, I’ve recently installed Mender 2.0 (production, not demo) on a private server. I’ve encountered an issue while using the UI. The issue is similar to the one that have been mentioned in this post : UI Issue. However,…

---

## [Working with S3 instead of Minio - no artifacts found and blank releases page](https://hub.mender.io/t/working-with-s3-instead-of-minio-no-artifacts-found-and-blank-releases-page/946)

<div class="topic-metadata">

**Author:** [@MBConsultingUK](https://hub.mender.io/u/MBConsultingUK)\
**Replies:** 10\
**Last updated:** [August 19, 2019, 3:33pm UTC](https://hub.mender.io/t/working-with-s3-instead-of-minio-no-artifacts-found-and-blank-releases-page/946 "2019-08-19T15:33:12Z")

</div>

Hey folks, Running Mender 2.1 via the docker-compose scripts for the production environment as documented, using LetsEncrypt certificates for the TLS connections. In order to see if I can fix the issues I’m encounterin…

---

## [Module update - poll inventory after successful update](https://hub.mender.io/t/module-update-poll-inventory-after-successful-update/920)

<div class="topic-metadata">

**Author:** [@speeltronics](https://hub.mender.io/u/speeltronics)\
**Replies:** 10\
**Last updated:** [August 19, 2019, 7:45am UTC](https://hub.mender.io/t/module-update-poll-inventory-after-successful-update/920 "2019-08-19T07:45:17Z")

</div>

I noticed that after a successful module update, the devices inventory on the production server still shows the old artifact until the device does its next inventory poll. Is there a way to force the device to do an inve…

---

## [Is it possible to get the artifact version in standalone mode?](https://hub.mender.io/t/is-it-possible-to-get-the-artifact-version-in-standalone-mode/901)

<div class="topic-metadata">

**Author:** [@ajithpv](https://hub.mender.io/u/ajithpv)\
**Replies:** 5\
**Last updated:** [August 19, 2019, 5:35am UTC](https://hub.mender.io/t/is-it-possible-to-get-the-artifact-version-in-standalone-mode/901 "2019-08-19T05:35:14Z")

</div>

Hi, AFAIK, currently, the mender server is checking the artifact version and deciding whether the artifact need to be installed (by checking whether it is already installed on the target platform). Please correct me if …

---

## [Issues with dir-overlay Update Module rollback state](https://hub.mender.io/t/issues-with-dir-overlay-update-module-rollback-state/914)

<div class="topic-metadata">

**Author:** [@speeltronics](https://hub.mender.io/u/speeltronics)\
**Replies:** 14\
**Last updated:** [August 16, 2019, 8:09am UTC](https://hub.mender.io/t/issues-with-dir-overlay-update-module-rollback-state/914 "2019-08-16T08:09:28Z")

</div>

The rollback state of this module doesn’t seem to be working correctly. This line “\[\[ -f $prev\_files\_tar \]\]” always fails. This is a bash command not a shell command and since the dir-overlay module is using “#!/bin/sh” …

---

## [State Scripts sanity check](https://hub.mender.io/t/state-scripts-sanity-check/941)

<div class="topic-metadata">

**Author:** [@brianPTL](https://hub.mender.io/u/brianPTL)\
**Replies:** 1\
**Last updated:** [August 15, 2019, 11:35am UTC](https://hub.mender.io/t/state-scripts-sanity-check/941 "2019-08-15T11:35:38Z")

</div>

I have the following file: /etc/mender/scripts/ArtifactReboot\_Enter\_01\_machine-safe.sh Contents are as follows: #!/usr/bin/env bash 1\>&2 echo "Script aborted due to failed bash command. Telling Mender to try later"; …

---

## [Issues integrating Broadcom .dtbs in meta-raspberrypi](https://hub.mender.io/t/issues-integrating-broadcom-dtbs-in-meta-raspberrypi/918)

<div class="topic-metadata">

**Author:** [@gtg811q](https://hub.mender.io/u/gtg811q)\
**Replies:** 1\
**Last updated:** [August 14, 2019, 7:43pm UTC](https://hub.mender.io/t/issues-integrating-broadcom-dtbs-in-meta-raspberrypi/918 "2019-08-14T19:43:33Z")

</div>

I’m building yocto thud + mender for a Raspberry Pi 0 + wifi along with some custom yocto layers (one of which patches the config to U-Boot). Recently, we noticed we are failing builds as the Broadcom proprietary .dtb fi…

---

## [Issue building meta-mender-core/recipes-devtools/e2fsprogs - no recipes available](https://hub.mender.io/t/issue-building-meta-mender-core-recipes-devtools-e2fsprogs-no-recipes-available/913)

<div class="topic-metadata">

**Author:** [@Valks](https://hub.mender.io/u/Valks)\
**Replies:** 2\
**Last updated:** [August 14, 2019, 6:40am UTC](https://hub.mender.io/t/issue-building-meta-mender-core-recipes-devtools-e2fsprogs-no-recipes-available/913 "2019-08-14T06:40:04Z")

</div>

When trying to build meta-mender-core I have been receiving an error: ERROR: No recipes available for: /home/user/yocto/layers/meta-mender/meta-mender-core/recipes-devtools/e2fsprogs/e2fsprogs\_1.44.%.bbappend I curren…

---

## [Microchip-sama5d27-som1-ek1 integrate with google IOT cloud](https://hub.mender.io/t/microchip-sama5d27-som1-ek1-integrate-with-google-iot-cloud/892)

<div class="topic-metadata">

**Author:** [@nidev01](https://hub.mender.io/u/nidev01)\
**Replies:** 7\
**Last updated:** [August 13, 2019, 5:45pm UTC](https://hub.mender.io/t/microchip-sama5d27-som1-ek1-integrate-with-google-iot-cloud/892 "2019-08-13T17:45:16Z")

</div>

Used this link for setting up for atmel platform using https://hub.mender.io/t/microchip-sama5d27-som1-ek1/127 This works great with demo server. Then followed this link https://mkrak.org/wp-content/uploads/2019/04/Int…

---

## [Dismiss vs Reject](https://hub.mender.io/t/dismiss-vs-reject/910)

<div class="topic-metadata">

**Author:** [@brianPTL](https://hub.mender.io/u/brianPTL)\
**Replies:** 1\
**Last updated:** [August 13, 2019, 4:16pm UTC](https://hub.mender.io/t/dismiss-vs-reject/910 "2019-08-13T16:16:35Z")

</div>

Hi All, I may have missed it in the docs, but can someone explain the difference between “Dismiss” and “Reject” in the Devices tab? Thanks!

---

## [Identity Attribute - Default vs Commissioned Device](https://hub.mender.io/t/identity-attribute-default-vs-commissioned-device/911)

<div class="topic-metadata">

**Author:** [@brianPTL](https://hub.mender.io/u/brianPTL)\
**Replies:** 1\
**Last updated:** [August 13, 2019, 1:03pm UTC](https://hub.mender.io/t/identity-attribute-default-vs-commissioned-device/911 "2019-08-13T13:03:08Z")

</div>

Hi All, I am reading the documentation here: link and I see the statement: identity attributes must never change for the lifetime of a device, so that a device can be recognized over its lifetime My use case is as f…

---

## [Problems with Raspbian Buster](https://hub.mender.io/t/problems-with-raspbian-buster/888)

<div class="topic-metadata">

**Author:** [@genedupre](https://hub.mender.io/u/genedupre)\
**Replies:** 12\
**Last updated:** [August 12, 2019, 11:50am UTC](https://hub.mender.io/t/problems-with-raspbian-buster/888 "2019-08-12T11:50:25Z")

</div>

---

## [Troubles with Management API](https://hub.mender.io/t/troubles-with-management-api/244)

<div class="topic-metadata">

**Author:** [@jbman35](https://hub.mender.io/u/jbman35)\
**Replies:** 11\
**Last updated:** [August 9, 2019, 6:35pm UTC](https://hub.mender.io/t/troubles-with-management-api/244 "2019-08-09T18:35:07Z")

</div>

Hello, I am facing some troubles while using the management API. When I am getting a list of devices using the GET “/api/management/v1/inventory/devices” URL by specifying attributes it works properly instead when I am…

---

## [Error in U-Boot setup: Boot and Root partitions don't match](https://hub.mender.io/t/error-in-u-boot-setup-boot-and-root-partitions-dont-match/855)

<div class="topic-metadata">

**Author:** [@davidknezic](https://hub.mender.io/u/davidknezic)\
**Replies:** 9\
**Last updated:** [August 7, 2019, 3:30pm UTC](https://hub.mender.io/t/error-in-u-boot-setup-boot-and-root-partitions-dont-match/855 "2019-08-07T15:30:55Z")

</div>

Dear community, I recently had to upgrade my entire build to Yocto 2.7 (warrior). I’m aware that Mender doesn’t officially support this latest version yet, but was hopeful that I might still get basic standalone updatin…

---

## [\`version\` of state-scripts in /etc/mender](https://hub.mender.io/t/version-of-state-scripts-in-etc-mender/894)

<div class="topic-metadata">

**Author:** [@ster](https://hub.mender.io/u/ster)\
**Replies:** 1\
**Last updated:** [August 7, 2019, 12:51pm UTC](https://hub.mender.io/t/version-of-state-scripts-in-etc-mender/894 "2019-08-07T12:51:52Z")

</div>

Trying to use state-scripts for Sync state, I was catching this error: level=error msg="transient error: error calling enter script for (error) authorize state: error running enter state script(s) for Sync state: states…

---

## [State script version](https://hub.mender.io/t/state-script-version/882)

<div class="topic-metadata">

**Author:** [@mterwoord](https://hub.mender.io/u/mterwoord)\
**Replies:** 2\
**Last updated:** [August 5, 2019, 9:37am UTC](https://hub.mender.io/t/state-script-version/882 "2019-08-05T09:37:20Z")

</div>

I’m building images using yocto. The mender artifact includes a state script named ArtifactReboot\_Enter\_50. When updating, it seems the old version is used. ie the one already on the device. How can I make sure only th…

---

## [Server upgrade from 1.5.x to 1.6.1](https://hub.mender.io/t/server-upgrade-from-1-5-x-to-1-6-1/868)

<div class="topic-metadata">

**Author:** [@juliosmelo](https://hub.mender.io/u/juliosmelo)\
**Replies:** 4\
**Last updated:** [August 2, 2019, 7:57pm UTC](https://hub.mender.io/t/server-upgrade-from-1-5-x-to-1-6-1/868 "2019-08-02T19:57:14Z")

</div>

Hi there, I’m trying to update my production to version 2.0.1. I just tried to follow the documentation but something weird is happening. When a tried to merge with the tag 1.6.1 some git conflicts appears. git merge …

---

## [Freeze on accept](https://hub.mender.io/t/freeze-on-accept/866)

<div class="topic-metadata">

**Author:** [@bentech](https://hub.mender.io/u/bentech)\
**Replies:** 3\
**Last updated:** [August 1, 2019, 3:10pm UTC](https://hub.mender.io/t/freeze-on-accept/866 "2019-08-01T15:10:26Z")

</div>

I’m using mender 2.0.1 and i’m getting a hanging issue. When I use the admin interface for manually accepting a device ‘Authorization request for this device’ as soon as i press accept it becomes unresponsive. If I ssh …

---

## [Rootfs size overrides maxsize for core-image-sato](https://hub.mender.io/t/rootfs-size-overrides-maxsize-for-core-image-sato/879)

<div class="topic-metadata">

**Author:** [@Austriker](https://hub.mender.io/u/Austriker)\
**Replies:** 7\
**Last updated:** [August 1, 2019, 2:50pm UTC](https://hub.mender.io/t/rootfs-size-overrides-maxsize-for-core-image-sato/879 "2019-08-01T14:50:39Z")

</div>

Hi, I have been testing mender with the Jetson TX2. But I am unable to build the core-image-sato. I followed the demo tutorial for the tegra and I have a working example with core-image-base. but I can’t managed to foll…

---

## [New operators for devices inventory API](https://hub.mender.io/t/new-operators-for-devices-inventory-api/881)

<div class="topic-metadata">

**Author:** [@rsirac](https://hub.mender.io/u/rsirac)\
**Replies:** 2\
**Last updated:** [August 1, 2019, 1:25pm UTC](https://hub.mender.io/t/new-operators-for-devices-inventory-api/881 "2019-08-01T13:25:10Z")

</div>

Hi I am currently working with Mender API and I would like to get devices list with some filters. I am using the route : /api/management/v1/inventory With this example: GET /devices?attr\_name\_1=foo& attr\_name\_2=100&…

---

## [How to adjust Mender disk image artifact](https://hub.mender.io/t/how-to-adjust-mender-disk-image-artifact/574)

<div class="topic-metadata">

**Author:** [@gpram](https://hub.mender.io/u/gpram)\
**Replies:** 37\
**Last updated:** [August 1, 2019, 12:01pm UTC](https://hub.mender.io/t/how-to-adjust-mender-disk-image-artifact/574 "2019-08-01T12:01:56Z")

</div>

Hi am doing new mender artifact image… Am getting error from mender diak image adjust size… I have rawdisk image size 16gb how can I do adjust menderdisk size

---

## [Cannot cleanup the deviceauth database](https://hub.mender.io/t/cannot-cleanup-the-deviceauth-database/877)

<div class="topic-metadata">

**Author:** [@Ks89](https://hub.mender.io/u/Ks89)\
**Replies:** 6\
**Last updated:** [August 1, 2019, 8:29am UTC](https://hub.mender.io/t/cannot-cleanup-the-deviceauth-database/877 "2019-08-01T08:29:22Z")

</div>

Hi, I’m trying to upgrade from mender server 1.7.1 to 2.0.1 using the official 2.0 tutorial on mender website. I created backups using the ../migration/dump-db script and with docker run -it --rm...... command. Next, …

[Previous page](https://hub.mender.io/c/general-discussions/12.md?page=75)

[Next page](https://hub.mender.io/c/general-discussions/12.md?page=77)
