# Critical Error info-beamer pi

**URL:** <https://community.info-beamer.com/t/critical-error-info-beamer-pi/1006>\
**Category:** Help\
**Created:** [March 15, 2021, 12:13pm UTC](https://community.info-beamer.com/t/critical-error-info-beamer-pi/1006 "2021-03-15T12:13:19Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![shaby\_c](https://community.info-beamer.com/letter_avatar_proxy/v3/letter/s/85e7bf/32.png) [@shaby\_c](https://community.info-beamer.com/u/shaby_c)\
**Post date:** [March 15, 2021, 12:13pm UTC](https://community.info-beamer.com/t/critical-error-info-beamer-pi/1006/1 "2021-03-15T12:13:20Z")

</div>

Hi,

I’ve been trying to run info-beamer pi on a Raspberry PI 4 (set to FKMS driver, GPU memory set to 256MB and installed all dependencies according to the readme file) unit but get the following errors:

Info Beamer PI 1.0.1.b40a5f~buster-fkms ([https://info-beamer.com](https://info-beamer.com))  
Copyright © 2012-2020, Florian Wesch [fw@info-beamer.com](mailto:fw@info-beamer.com)

FKMS release for the Pi4. Be sure to read what has changed  
compared to the classic info-beamer pi version on earlier  
Pi models by running `info-beamer -fkms`.

info-beamer for the raspberry pi is free for private use. If you  
would like to make use of this software in a commercial way, you  
must buy a license which will support the continued development.

You might also take a look at info-beamer hosted. It’s the best  
platform to run your info-beamer code. It does all the hard work  
for you: installation, maintenance, asset delivery, management…  
That way you can focus on the content. Learn more at:

[watchdog.c] software watchdog installed. 15 seconds timeout  
[main.c] chdir /home/pi/info-beamer-pi/samples  
[main.c] root node is shader  
[main.c] running as euid/egid 1000/1000  
[main.c] luajit version: LuaJIT 2.1.0-beta3~f0e865  
[main.c] linux version: 5.4.68-v7l+ #1343 SMP Mon Sep 28 12:44:25 BST 2020 armv7l  
[main.c] firmware version: Sep 28 2020 12:52:29 Copyright © 2012 Broadcom version 2c4b5cf8e4a920c2976ebdb62b27bd742b69ea8b (clean)release) (start)  
[main.c] bootloader version: Sep 3 2020 13:11:43 version c305221a6d7e532693cc7ff57fddfc8649def167 (release) timestamp 1599135103  
[main.c] pi version: 00b03111  
[main.c] pi model: Raspberry Pi 4 Model B Rev 1.1  
[main.c] config: arm\_freq=1500 audio\_pwm\_mode=514 config\_hdmi\_boost=5 core\_freq=550 core\_freq\_min=220 disable\_commandline\_tags=2 disae\_l2cache=1 disable\_overscan=1 disable\_splash=1 display\_hdmi\_rotate=-1 display\_lcd\_rotate=-1 enable\_gic=1 enable\_uart=1 force\_eeprom\_ad=1 force\_pwm\_open=1 framebuffer\_ignore\_alpha=1 framebuffer\_swap=1 gpu\_freq=500 gpu\_freq\_min=250 hdmi\_enable\_4kp60=1 hdmi\_samples\_lit=0x1f4000 init\_uart\_clock=0x2dc6c00 lcd\_framerate=60 mask\_gpu\_interrupt0=1024 mask\_gpu\_interrupt1=0x10000 max\_framebuffer\_height=216max\_framebuffer\_width=3840 max\_framebuffers=2 over\_voltage\_avs=-36250 pause\_burst\_frames=1 program\_serial\_random=1 total\_mem=2048 hdmforce\_cec\_address:0=65535 hdmi\_force\_cec\_address:1=65535 hdmi\_pixel\_freq\_limit:0=0x23c34600 hdmi\_pixel\_freq\_limit:1=0x9a7ec80  
[main.c] environ: INFOBEAMER\_LOG\_LEVEL=3  
[main.c] memory: arm=768M gpu=256M  
[main.c] file descriptor limit: 1024  
[surface.c] DRM device /dev/dri/card1  
[surface.c] connectors: 1  
[surface.c] encoders: 1  
[surface.c] crtcs: 1  
[surface.c] found 1 attached devices  
[surface.c] Connector 0:  
[surface.c] detected HDMI 0 display 2 device SAM S23B300  
[surface.c] 1920x1080@60.000 Custom 0  
[surface.c] physical size 510x290mm  
[surface.c] vv— T = tvservice match, D = drm match  
[surface.c] T 0, 1920x1080: 60.00Hz name: 1920x1080, clock: 148500 (flag:0x5 phsync pvsync)  
[surface.c] T 1, 1920x1080: 59.94Hz name: 1920x1080, clock: 148352 (flag:0x5 phsync pvsync)  
[surface.c] 2, 1920x1080: 50.00Hz name: 1920x1080, clock: 148500 (flag:0x5 phsync pvsync)  
[surface.c] 3, 1680x1050: 59.88Hz name: 1680x1050, clock: 119000 (flag:0x9 phsync nvsync)  
[surface.c] 4, 1600x900: 60.00Hz name: 1600x900, clock: 108000 (flag:0x5 phsync pvsync)  
[surface.c] 5, 1280x1024: 75.02Hz name: 1280x1024, clock: 135000 (flag:0x5 phsync pvsync)  
[surface.c] 6, 1280x1024: 60.02Hz name: 1280x1024, clock: 108000 (flag:0x5 phsync pvsync)  
[surface.c] 7, 1440x900: 59.90Hz name: 1440x900, clock: 88750 (flag:0x9 phsync nvsync)  
[surface.c] 8, 1280x800: 59.91Hz name: 1280x800, clock: 71000 (flag:0x9 phsync nvsync)  
[surface.c] 9, 1152x864: 75.00Hz name: 1152x864, clock: 108000 (flag:0x5 phsync pvsync)  
[surface.c] 10, 1280x720: 60.00Hz name: 1280x720, clock: 74250 (flag:0x5 phsync pvsync)  
[surface.c] 11, 1280x720: 59.94Hz name: 1280x720, clock: 74176 (flag:0x5 phsync pvsync)  
[surface.c] 12, 1280x720: 50.00Hz name: 1280x720, clock: 74250 (flag:0x5 phsync pvsync)  
[surface.c] 13, 1024x768: 75.03Hz name: 1024x768, clock: 78750 (flag:0x5 phsync pvsync)  
[surface.c] 14, 1024x768: 70.07Hz name: 1024x768, clock: 75000 (flag:0xa nhsync nvsync)  
[surface.c] 15, 1024x768: 60.00Hz name: 1024x768, clock: 65000 (flag:0xa nhsync nvsync)  
[surface.c] 16, 832x624: 74.55Hz name: 832x624, clock: 57284 (flag:0xa nhsync nvsync)  
[surface.c] 17, 800x600: 75.00Hz name: 800x600, clock: 49500 (flag:0x5 phsync pvsync)  
[surface.c] 18, 800x600: 72.19Hz name: 800x600, clock: 50000 (flag:0x5 phsync pvsync)  
[surface.c] 19, 800x600: 60.32Hz name: 800x600, clock: 40000 (flag:0x5 phsync pvsync)  
[surface.c] 20, 800x600: 56.25Hz name: 800x600, clock: 36000 (flag:0x5 phsync pvsync)  
[surface.c] 21, 720x576: 50.00Hz name: 720x576, clock: 27000 (flag:0xa nhsync nvsync)  
[surface.c] 22, 720x480: 60.00Hz name: 720x480, clock: 27027 (flag:0xa nhsync nvsync)  
[surface.c] 23, 720x480: 59.94Hz name: 720x480, clock: 27000 (flag:0xa nhsync nvsync)  
[surface.c] 24, 640x480: 75.00Hz name: 640x480, clock: 31500 (flag:0xa nhsync nvsync)  
[surface.c] 25, 640x480: 72.81Hz name: 640x480, clock: 31500 (flag:0xa nhsync nvsync)  
[surface.c] 26, 640x480: 66.67Hz name: 640x480, clock: 30240 (flag:0xa nhsync nvsync)  
[surface.c] 27, 640x480: 60.00Hz name: 640x480, clock: 25200 (flag:0xa nhsync nvsync)  
[surface.c] 28, 640x480: 59.94Hz name: 640x480, clock: 25175 (flag:0xa nhsync nvsync)  
[surface.c] 29, 720x400: 70.08Hz name: 720x400, clock: 28320 (flag:0x6 nhsync pvsync)  
[surface.c] selected 0 as primary mode  
[surface.c] crtc:87(0) → encoder:88 → connector:89  
[surface.c] set up 1 displays  
[surface.c] display #0 (dispmanx 2): 1920x1080+0,0  
[surface.c] GBM device: drm (open took 0.53s)  
[surface.c] DRM display initialized to 1920x1080 across 1 displays  
[surface.c] framerate is 60.000000  
[surface.c] Loading GL subsystem took 0.00s  
[surface.c] found format in config 0 (18992856): fourcc=AR24!  
[surface.c] display configs matching: 8. using config 18992856  
failed to export dumb buffer: Permission denied  
Failed to create scanout resource  
[surface.c] max texture size: 0x0  
[surface.c] GL surface 1920x1080 (interval 1/60.000 fps) into 1920x1080+0,0  
failed to export dumb buffer: Permission denied  
Failed to create scanout resource  
[threadpool.c] submitting 0x447bb9((nil))  
[threadpool.c] submitting 0x447db1((nil))  
[video.c] initializing video subsystem  
[mmalvideo.c] RPI HEVC decoding enabled  
[threadpool.c] 4 cores detected  
[threadpool.c] using 12 pool threads  
[threadpool.c] running vsync-poll 0x447bb9((nil))  
CRITICAL ERROR: cannot set priority  
[threadpool.c] running vsync-flip 0x447db1((nil))  
CRITICAL ERROR: cannot set priority  
[main.c] loading nodes

Please advise how to solve this.  
Thanks

---

<div class="post-metadata">

**Author:** ![infobeamer-fw](https://community.info-beamer.com/user_avatar/community.info-beamer.com/infobeamer-fw/32/3_2.png) [@infobeamer-fw](https://community.info-beamer.com/u/infobeamer-fw)\
**Post date:** [April 13, 2021, 11:15am UTC](https://community.info-beamer.com/t/critical-error-info-beamer-pi/1006/2 "2021-04-13T11:15:23Z")

</div>

Sorry about the massively delayed response. Notification for new topics got stuck somewhere.

> [@shaby\_c](#):
>
> [main.c] running as euid/egid 1000/1000

This is most likely the reason. info-beamer works best with root permissions as it requires access to some resources (for example KMS or the Pi firmware) that’s not user-accessible by default.

---

<div class="post-metadata">

**Author:** ![pdxinuus](https://community.info-beamer.com/letter_avatar_proxy/v3/letter/p/f9ae1b/32.png) [@pdxinuus](https://community.info-beamer.com/u/pdxinuus)\
**Post date:** [May 18, 2021, 11:21pm UTC](https://community.info-beamer.com/t/critical-error-info-beamer-pi/1006/3 "2021-05-18T23:21:21Z")

</div>

One thing I noticed is your firmware version is from Sep 2020. It has been updated since then. {Pi release notes: [rpi-eeprom/release-notes.md at master · raspberrypi/rpi-eeprom · GitHub](https://github.com/raspberrypi/rpi-eeprom/blob/master/firmware/release-notes.md)} I would suggest updating the EEPROM and trying it again. [[Raspberry Pi 4 boot EEPROM - Raspberry Pi Documentation](https://www.raspberrypi.org/documentation/hardware/raspberrypi/booteeprom.md) ]  
Good luck.

---

<div class="post-metadata">

**Author:** ![infobeamer-fw](https://community.info-beamer.com/user_avatar/community.info-beamer.com/infobeamer-fw/32/3_2.png) [@infobeamer-fw](https://community.info-beamer.com/u/infobeamer-fw)\
**Post date:** [May 19, 2021, 9:51am UTC](https://community.info-beamer.com/t/critical-error-info-beamer-pi/1006/4 "2021-05-19T09:51:07Z")

</div>

> [@pdxinuus](#):
>
> I would suggest updating the EEPROM

While that’s generally a good idea, this isn’t the root cause seen in the log output. It’s definitely a permission issue.
