RPi 3 - framebuffer: No such file

Help and Support
1

Hi,

after successfully upgrading my Vero 4K, i also wanted to upgrade osmc on my Raspberry Pi 3 Model B Plus Rev 1.3. I did this using ssh by apt.

Unfortunately the service can not start anymore and retries forever. In the journal I am getting:

 mediacenter[421]: could not open framebuffer: No such file or director

I am a little bit lost with this.
I am booting this RPi using pxe, but this should not really matter here.
This is my cmdline.txt:

dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.1.10:/mnt/raspiez/,vers=3 rw rootfstype=nfs ip=dhcp rootwait elevator=deadline debug smsc95xx.turbo_mode=N osmcdev=rbp2

and my config.txt:

[pi4]
dtoverlay=rpivid-v4l2
arm_64bit=1
kernel=kernel.img

[all]
dtoverlay=vc4-kms-v3d,cma-512
disable_overscan=1
start_x=1
disable_splash=1
disable_fw_kms_setup=1
include config-user.txt

I suppose that one of the options changed or is wrong…
Any help would be great!
Best regards and thanks in advance,
Otto

2

This is the current cmdline


coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1  vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  root=/dev/mmcblk0p2 rootfstype=ext4 rootwait quiet osmcdev=rbp2

So looks like you have some work to do.

3

Thanks for the fast reply!
It was not too much work :wink:
Now my cmdline is

coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1  vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  root=/dev/nfs nfsroot=192.168.1.10:/mnt/k/k/raspis/raspiez/,vers=3 rw rootfstype=nfs ip=dhcp rootwait osmcdev=rbp2

But this did not really help, now the journal shows:

ug 12 11:17:18 raspiez mediacenter[420]: Failed to set capabilities on file `/usr/lib/kodi/kodi.bin' (Operation not supported)
Aug 12 11:17:18 raspiez mediacenter[420]: The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file
Aug 12 11:17:18 raspiez mediacenter[420]: Starting Kodi...
Aug 12 11:17:18 raspiez sudo[820]:     root : TTY=unknown ; PWD=/ ; USER=osmc ; ENV=LIRC_SOCKET_PATH=/var/run/lirc/lircd ; COMMAND=/usr/lib/kodi/kodi.bin --standalone -fs
Aug 12 11:17:18 raspiez sudo[820]: pam_unix(sudo:session): session opened for user osmc by (uid=0)
Aug 12 11:17:18 raspiez mediacenter[420]: /usr/lib/kodi/kodi.bin: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: g_date_copy
Aug 12 11:17:18 raspiez sudo[820]: pam_unix(sudo:session): session closed for user osmc
Aug 12 11:17:18 raspiez mediacenter[420]: Kodi exited with return code 127 after 0 hours, 0 minutes and 0 seconds
Aug 12 11:17:18 raspiez mediacenter[420]: open /dev/fb0: No such file or directory
Aug 12 11:17:18 raspiez mediacenter[420]: open /dev/fb0: No such file or directory
Aug 12 11:17:18 raspiez mediacenter[420]: /usr/bin/mediacenter: line 9: /sys/class/vtconsole/vtcon1/bind: No such file or directory
Aug 12 11:17:19 raspiez mediacenter[420]: could not open framebuffer: No such file or directory
Aug 12 11:17:29 raspiez mediacenter[420]: Failed to set capabilities on file `/usr/lib/kodi/kodi.bin' (Operation not supported)
Aug 12 11:17:29 raspiez mediacenter[420]: The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file
Aug 12 11:17:29 raspiez mediacenter[420]: Starting Kodi...
Aug 12 11:17:29 raspiez sudo[835]:     root : TTY=unknown ; PWD=/ ; USER=osmc ; ENV=LIRC_SOCKET_PATH=/var/run/lirc/lircd ; COMMAND=/usr/lib/kodi/kodi.bin --standalone -fs
Aug 12 11:17:29 raspiez mediacenter[420]: /usr/lib/kodi/kodi.bin: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: g_date_copy
Aug 12 11:17:29 raspiez mediacenter[420]: Kodi exited with return code 127 after 0 hours, 0 minutes and 0 seconds
Aug 12 11:17:29 raspiez mediacenter[420]: open /dev/fb0: No such file or directory
Aug 12 11:17:29 raspiez mediacenter[420]: open /dev/fb0: No such file or directory
Aug 12 11:17:29 raspiez mediacenter[420]: /usr/bin/mediacenter: line 9: /sys/class/vtconsole/vtcon1/bind: No such file or directory
Aug 12 11:17:30 raspiez mediacenter[420]: could not open framebuffer: No such file or directory

There is still no framebuffer device :frowning:

4

Guess something not upgraded correctly. Guess best to do a new install to a SD Card and transfer that to your PXE server

5

I was afraid of that as I am also running some other things on this raspi… damn…
but thanks anyway!
Best regards and thanks again,
Otto

6

Unfortunately, providing just a small snippet of the system journal significantly reduces our view of your system. While you have focused on the framebuffer error, the root cause could lie elsewhere, for example higher up in the system journal.

Even in the snippet you posted, I see that an error occurs before the framebuffer error:

Aug 12 11:17:18 raspiez mediacenter[420]: /usr/lib/kodi/kodi.bin: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: g_date_copy
Aug 12 11:17:18 raspiez sudo[820]: pam_unix(sudo:session): session closed for user osmc
Aug 12 11:17:18 raspiez mediacenter[420]: Kodi exited with return code 127 after 0 hours, 0 minutes and 0 seconds

So Kodi actually seems to be failing to start because of an issue with libgobject-2.0.so.0. The problem might be in the library or in kodi.bin itself. You can try to reinstall the library with the command:

sudo apt-get install --reinstall libglib2.0-0

You might also notice a prior error:

ug 12 11:17:18 raspiez mediacenter[420]: Failed to set capabilities on file `/usr/lib/kodi/kodi.bin' (Operation not supported)
Aug 12 11:17:18 raspiez mediacenter[420]: The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file

This is a known limirtation of booting from an NFS root. On the previous kernel, kodi.bin was still able to start from an NFS root, despite the error, but perhaps it causes issues on the latest kernel.

7

Thanks!
reinstalling libglib did not help…
yes, I know regarding journal. but this were the lines related to mediacenter service. I also could post more if necessary of course.
does this mean that osmc is not running from nfs anymore? :frowning:

8

Please upload full logs – grab-logs -A – and post the URL it returns.

9

fine thing, thanks! (did not know about this function yet)
https://paste.osmc.tv/wixajolaqi

10

Unable to open guisettings file: /home/osmc/.kodi/userdata/guisettings.xml could it be that you lost your home folder or at least the .kodi folder? Should be easy to be checked on the NFS server what the content is.

11

It looks like the package reinstall ran into the same problem. :slight_smile:

Log started: 2021-08-12  19:29:19
Preparing to unpack .../libglib2.0-0_2.58.3-2+deb10u3_armhf.deb ...
Unpacking libglib2.0-0:armhf (2.58.3-2+deb10u3) over (2.58.3-2+deb10u3) ...
Setting up libglib2.0-0:armhf (2.58.3-2+deb10u3) ...
/usr/lib/arm-linux-gnueabihf/glib-2.0/glib-compile-schemas: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: g_date_copy
/usr/lib/arm-linux-gnueabihf/glib-2.0/gio-querymodules: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: g_date_copy
Processing triggers for libc-bin (2.28-10) ...
Log ended: 2021-08-12  19:29:25

The symbol g_date_copy should be defined in libglib-2.0.so.0, which is also part of the libglib2.0-0 package.

It’s possible that the libglib-2.0.so.0 library has gone walkabout or been corrupted. Another possibility is that there’s another (incompatible) one higher up in the LD_LIBRARY_PATH. So please provide the output from these commands:

ls -l /usr/lib/arm-linux-gnueabihf/libglib*
md5sum /usr/lib/arm-linux-gnueabihf/libglib*
find /lib -name libglib\* -ls
12

wow - you are fast, thanks!
omg, sorry - I did not see the apt-error… this is embrassing…
yes, I moved the .kodi folder because I got tons of errors on my vero when upgrading (addons, skripts and so on). so I thought to do this before on the raspi. just re-moved it to .kodi, but the error is the same…

root@raspiez:~# ls -l /usr/lib/arm-linux-gnueabihf/libglib*
lrwxrwxrwx 1 root root     23 Mar 27 12:34 /usr/lib/arm-linux-gnueabihf/libglib-2.0.so.0 -> libglib-2.0.so.0.5800.3
-rw-r--r-- 1 root root 854208 Mar 27 12:34 /usr/lib/arm-linux-gnueabihf/libglib-2.0.so.0.5800.3
root@raspiez:~# md5sum /usr/lib/arm-linux-gnueabihf/libglib*
600b9090a6803aba0e3ea73f29cc5920  /usr/lib/arm-linux-gnueabihf/libglib-2.0.so.0
600b9090a6803aba0e3ea73f29cc5920  /usr/lib/arm-linux-gnueabihf/libglib-2.0.so.0.5800.3
root@raspiez:~# find /lib -name libglib\* -ls
132514675    812 -rw-r--r--   1 root     root       830688 Nov  6  2019 /lib/arm-linux-gnueabihf/libglib-2.0.so.0.5000.3
132514663      0 lrwxrwxrwx   1 root     root           23 Nov 14  2020 /lib/arm-linux-gnueabihf/libglib-2.0.so.0 -> libglib-2.0.so.0.5000.3
13

OK, and as Kodi never successfully started it hasn’t recreated those files.

14

yes…

15

Different versions and different sizes. You’re picking up the one in /lib first. And it’s the wrong one.

16

Oh damn. Thanks!
Will look after this, but probably on monday.
Have a nice weekend!

17

You’ll need to find what caused the extra library and is the problem confined to just this one file.

18

Thanks!
I also have installed a bluetooth-ping utility for my home automation on the device. I suppose that this installed a different version of libglib. strangely I did not have any issues before upgrading…
I wanted to install the tool on my vero, but unfortunately it didnt work… so I installed it on this raspi…

19

Thanks for your help! Couldnt find out where the second version came from (dpgk did not show it). So I just renamed the .so-file. everything seems to work now…
Best regards,
Otto