# OMXPLAYER on Bullseye fresh install (32-bit)

**URL:** https://dietpi.com/forum/t/omxplayer-on-bullseye-fresh-install-32-bit/5706
**Category:** Troubleshooting
**Created:** [13 September 2021 22:54 UTC](https://dietpi.com/forum/t/omxplayer-on-bullseye-fresh-install-32-bit/5706 "2021-09-13T22:54:35Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![pinipon](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/p/ea666f/32.png) [@pinipon](https://dietpi.com/forum/u/pinipon)
#### Post date: [13 September 2021 22:54 UTC](https://dietpi.com/forum/t/omxplayer-on-bullseye-fresh-install-32-bit/5706/1 "2021-09-13T22:54:35Z")

</div>

OMXPLAYER doesn’t work on Bullseye fresh install. After installing the package:

```nohighlight
$ apt install omxplayer

```

running the command:

```nohighlight
$ omxplayer my-video.mp4

```

results in:

```nohighlight
/usr/bin/omxplayer.bin: error while loading shared libraries: libvcos.so: cannot open shared object file: No such file or directory

```

That’s because Bullseye doesn’t install raspberrypi firmware on /opt/vc/lib anymore. This didn’t happened on Buster.  
So, putting libraries [/opt/vc/lib](https://github.com/raspberrypi/firmware/tree/master/opt/vc/lib) from [raspberrypi firmware](https://github.com/raspberrypi/firmware) in /opt/vc/lib solve the issue and omxplayer is playing back again.

Could someone tell me if there is any “_cleanest_” way to install those libraries in /opt/vc/lib instead of “_manually_” copying those files? Is any package installation that provides this operation?

Thanks in advance for your comments.

---

<div class="post-metadata">

### Author: ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)
#### Post date: [13 September 2021 23:03 UTC](https://dietpi.com/forum/t/omxplayer-on-bullseye-fresh-install-32-bit/5706/2 "2021-09-13T23:03:28Z")

</div>

Basically same as this [https://dietpi.com/forum/t/solved-minidlna-stop-working-after-updating-to-dietpi-7-5-2/5703/2](https://dietpi.com/forum/t/solved-minidlna-stop-working-after-updating-to-dietpi-7-5-2/5703/2)

RPi Devs changed package structure an this is causing incorrect libraries name

---

<div class="post-metadata">

### Author: ![pinipon](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/p/ea666f/32.png) [@pinipon](https://dietpi.com/forum/u/pinipon)
#### Post date: [17 September 2021 20:49 UTC](https://dietpi.com/forum/t/omxplayer-on-bullseye-fresh-install-32-bit/5706/3 "2021-09-17T20:49:11Z")

</div>

Using:

```nohighlight
cd /usr/lib/arm-linux-gnueabihf
ln -s libmmal_core.so.0 libmmal_core.so
ln -s libmmal_util.so.0 libmmal_util.so
ln -s libmmal_vc_client.so.0 libmmal_vc_client.so
ln -s libbcm_host.so.0 libbcm_host.so
ln -s libvcsm.so.0 libvcsm.so
ln -s libvchiq_arm.so.0 libvchiq_arm.so
ln -s libvcos.so.0 libvcos.so

```

cause:

```nohighlight
/usr/bin/omxplayer.bin: error while loading shared libraries: libbrcmEGL.so: cannot open shared object file: No such file or directory
/usr/bin/omxplayer.bin: error while loading shared libraries: libopenmaxil.so: cannot open shared object file: No such file or directory
/usr/bin/omxplayer.bin: error while loading shared libraries: libbrcmGLESv2.so: cannot open shared object file: No such file or directory

```

So I still need to copy these three libraries to /opt/vc/lib/

---

<div class="post-metadata">

### Author: ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)
#### Post date: [21 September 2021 00:03 UTC](https://dietpi.com/forum/t/omxplayer-on-bullseye-fresh-install-32-bit/5706/4 "2021-09-21T00:03:19Z")

</div>

maybe the sym link to be created for the other 3 libraries as well

---

<div class="post-metadata">

### Author: ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)
#### Post date: [21 September 2021 16:54 UTC](https://dietpi.com/forum/t/omxplayer-on-bullseye-fresh-install-32-bit/5706/5 "2021-09-21T16:54:48Z")

</div>

Hmm, those three libraries are not part of libraspberrypi0 anymore 🤔.

A workaround may then be to download them manually, as they are still present on the GitHub repository:

```nohighlight
cd /usr/lib/arm-linux-gnueabihf
curl -sSfLO 'https://raw.githubusercontent.com/raspberrypi/firmware/master/hardfp/opt/vc/lib/libbrcmEGL.so'
curl -sSfLO 'https://raw.githubusercontent.com/raspberrypi/firmware/master/hardfp/opt/vc/lib/libbrcmGLESv2.so'
curl -sSfLO 'https://raw.githubusercontent.com/raspberrypi/firmware/master/hardfp/opt/vc/lib/libopenmaxil.so'

```

---

<div class="post-metadata">

### Author: ![pinipon](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/p/ea666f/32.png) [@pinipon](https://dietpi.com/forum/u/pinipon)
#### Post date: [21 September 2021 19:07 UTC](https://dietpi.com/forum/t/omxplayer-on-bullseye-fresh-install-32-bit/5706/6 "2021-09-21T19:07:31Z")

</div>

It works. Thanks.  
But I decided to install the VideoCore - EGL/GLES/OpenVG version.  
So, final solution after installing Omxplayer on fresh install:

```nohighlight
cd /usr/lib/arm-linux-gnueabihf
ln -s libmmal_core.so.0 libmmal_core.so
ln -s libmmal_util.so.0 libmmal_util.so
ln -s libmmal_vc_client.so.0 libmmal_vc_client.so
ln -s libbcm_host.so.0 libbcm_host.so
ln -s libvcsm.so.0 libvcsm.so
ln -s libvchiq_arm.so.0 libvchiq_arm.so
ln -s libvcos.so.0 libvcos.so
curl -sSfLO 'https://raw.githubusercontent.com/raspberrypi/firmware/master/opt/vc/lib/libbrcmEGL.so'
curl -sSfLO 'https://raw.githubusercontent.com/raspberrypi/firmware/master/opt/vc/lib/libbrcmGLESv2.so'
curl -sSfLO 'https://raw.githubusercontent.com/raspberrypi/firmware/master/opt/vc/lib/libopenmaxil.so'

```

Could be interesting to add this entry on Dietpi-Software. What do you think if I create a new Software Request on your GitHub?

---

<div class="post-metadata">

### Author: ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)
#### Post date: [21 September 2021 21:31 UTC](https://dietpi.com/forum/t/omxplayer-on-bullseye-fresh-install-32-bit/5706/7 "2021-09-21T21:31:42Z")

</div>

I guess soon (at latest when a first Raspberry Pi OS Bullseye image is released) it will be again as simple as

```nohighlight
apt install omxplayer

```

so that a dietpi-software option would be overkill 🙂.

The issue may be reported here to inform the RPi repo maintainers that the package requires a rebuild: [https://github.com/RPi-Distro/repo/issues](https://github.com/RPi-Distro/repo/issues)  
Probably they know already, but it doesn’t hurt.

---

<div class="post-metadata">

### Author: ![pinipon](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/p/ea666f/32.png) [@pinipon](https://dietpi.com/forum/u/pinipon)
#### Post date: [22 September 2021 18:30 UTC](https://dietpi.com/forum/t/omxplayer-on-bullseye-fresh-install-32-bit/5706/8 "2021-09-22T18:30:12Z")

</div>

I found this report:  
[https://github.com/RPi-Distro/repo/issues/134](https://github.com/RPi-Distro/repo/issues/134)  
which is related with this issue.

As you mentioned before, libraspberrypi0 doesn’t install those libraries anymore because they are installed by rpi-update now.

So, it is not an issue in RPi OS because this [firmware](https://github.com/RPi-Distro/firmware) is installed by default on RPi OS and already contains these libraries.

One solution could be install rpi-update and running it, but as you can see [here](https://github.com/Hexxeh/rpi-update) this is certainly not safe (i guess because of different kernel)

---

<div class="post-metadata">

### Author: ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)
#### Post date: [22 September 2021 19:00 UTC](https://dietpi.com/forum/t/omxplayer-on-bullseye-fresh-install-32-bit/5706/9 "2021-09-22T19:00:12Z")

</div>

I’m not going to fully agree on your conclusion. Because rpi-update us going to install thinks like beta kernel. It’s not recommended if not really needed.

DietPi themselves did not have own kernel as DietPi is based on Raspberry OS. Hence it is exactly the same kernel.

---

<div class="post-metadata">

### Author: ![pinipon](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/p/ea666f/32.png) [@pinipon](https://dietpi.com/forum/u/pinipon)
#### Post date: [22 September 2021 21:56 UTC](https://dietpi.com/forum/t/omxplayer-on-bullseye-fresh-install-32-bit/5706/10 "2021-09-22T21:56:26Z")

</div>

Installing rpi-update on Dietpi fresh install (7.6.2) solve the issue, but many errors loading modules during installation (depmod errors) and other non-needed additional libraries are installed. So, I prefer to stay with this [solution](https://dietpi.com/forum/t/omxplayer-on-bullseye-fresh-install-32-bit/5706/6) above to maintain a cleaner installation and not be bloated by rpi-update.  
Would be great if the entry is created on Dietpi-Software (the installation of omxplayer would be more convenient for anyone).  
Anyway, the solution is now here for anyone.

---

<div class="post-metadata">

### Author: ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)
#### Post date: [27 September 2021 13:06 UTC](https://dietpi.com/forum/t/omxplayer-on-bullseye-fresh-install-32-bit/5706/11 "2021-09-27T13:06:47Z")

</div>

Makes sense, as rpi-update still installs the VC userland tools and binaries to the old path.
