# Gigabyte Brix issues with mender i.c.w. Ubuntu Server 19.04

**URL:** https://hub.mender.io/t/gigabyte-brix-issues-with-mender-i-c-w-ubuntu-server-19-04/1529
**Category:** General Discussions
**Created:** [February 11, 2020, 2:38pm UTC](https://hub.mender.io/t/gigabyte-brix-issues-with-mender-i-c-w-ubuntu-server-19-04/1529 "2020-02-11T14:38:05Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)
#### Post date: [February 13, 2020, 10:43pm UTC](https://hub.mender.io/t/gigabyte-brix-issues-with-mender-i-c-w-ubuntu-server-19-04/1529/5 "2020-02-13T22:43:26Z")

</div>

Hi @PJK I don’t think we deliberately remove features from the build-time configuration but rather just use the defaults. I’ve been working on a more robust fix for this where grub actually provides a variable specifically for the device grub itself was launched from. We should then be able to build up the rest of the paths we need from that. Unfortunately I have not had time to get back to this recently and it will likely be several weeks before I have the time.

If you work out a solution with regex please post it here. We would love to see it.

Drew

---

_[View the full topic](https://hub.mender.io/t/gigabyte-brix-issues-with-mender-i-c-w-ubuntu-server-19-04/1529)._