Dev fb0 no such file or directory

Collectives on Stack Overflow. Learn more. Yocto: Can't get my beagleboard working: no framebuffer device Ask Question.

Asked 5 years, 7 months ago. Active 5 years, 7 months ago. Viewed 2k times. Because of the missing fb0 device the xserver cannot start: [ 3. INIT: version 2. Because of the missing framebuffer device xinit ends up with an Error: X.

Org X Server 1. EE EE Server terminated with error 1. Closing log file. Hochl Hochl 41 5 5 bronze badges. Add a comment. Active Oldest Votes. Remove x11 and wayland in local. Once the command fails, immediately unplug the device. The trace is going to be large, so it may be better to add as an attachment rather than inline.

Ideally, capture a trace where the device breaks on the first invocation of your test program. I've first updated the firmware to see if I get any "magical bug fix" but the bug is still present. Then I've run your test and updated the bug report repository with the requested traces:. Note: If you want to reproduce the bug in your lab, we can send you a device free of charge.

Just send use an email to support yoctopuce. Both devices have been updated to latest Yocto firmwares. The Pi 4 has no other devices attached and is using VLI firmware version ab. An upgrade of the VLI firmware can be done semi-automatically by installing the apt package rpi-eeprom and rebooting. To check the current version of bootloader and VLI firmware, run sudo rpi-eeprom-update with no arguments.

The problem is that we have multiples customers who are using our product on Raspberry Pi 4 and our product is not working correctly on it.

It would be nice to have some documentation which explain what the sudo rpi-eeprom-update -a do and what will be changed. It is installed by default if the rpi-eeprom package is installed. The package is not yet a default package but this will change soon. The package installs a tool that reads the pci config space for the firmware version.

Alternatively, use the pciutils tool lspci to read the config space:. And do you have any official documentation on the magic command sudo rpi-eeprom-update -a. The program is a shell script. What is the difference between rpi-eeprom-update and sudo rpi-update? Will one day rpi-update install this new firmware?

It pulls in untested beta software, so should not be recommended to end users. Use apt for all updating. I've done more intensive test and I confirm that the following commands fix the issue:.

I look at the USB bus traces you posted and noticed that you send one request per second and I was wondering if you ever performed the test at much higher rate maybe send the requests in a tight loop to see if any packet loss occurs? Our production code send much more packet up to 1 every millisecond and everything work fine.

On the Pi 4 all works fine. But on the Pi 3 I get random corrupt data and timeouts. Is there somthing I need to do on the Pi 3 to get it to work the same way as the Pi 4? I am communicating with a very slow usb device. This is one with a name like xxxxxfb. How are we doing? Please help us improve Stack Overflow. Take our short survey. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow.

Learn more. DirectFB bringup [duplicate] Ask Question. Asked 11 years, 7 months ago.