Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to specify DRM device? #64

Closed
tobiasht opened this issue Jun 23, 2020 · 2 comments
Closed

How to specify DRM device? #64

tobiasht opened this issue Jun 23, 2020 · 2 comments

Comments

@tobiasht
Copy link
Contributor

I am trying to run the flutter program on a 7inch display, but when I run the code I get this error:

./flutter-pi/out/flutter-pi ./dots-clock-master/dots_clock/build/flutter_assets

engine_argv[0] = ./flutter-pi/out/flutter-pi
initializing display...
Finding a suitable DRM device, since none is given...
could not query drm device list: No such file or directory

Seems like it doesn´t find the screen, even though I am currently using the display and it is showing the CLI perfectly. Is there a way to specify the "DRM" device? Any tips are much appreciated.

@ardera
Copy link
Owner

ardera commented Jun 23, 2020

Can you provide more details on the device & system you are using? Are you using a raspberry pi, if yes what model, OS, etc

If you're using a Raspberry Pi, can you give me complete output of the raspinfo command? (You may need to install it using sudo apt install raspinfo)

Seems like it doesn´t find the screen, even though I am currently using the display and it is showing the CLI perfectly

Almost, a DRM device is basically a GPU. If it finds the GPU (/DRM device), but doesn't find a screen you'd see some other error (couldn't find a connected connector or so). DRM devices are located inside /dev/dri. Can you execute ls /dev/dri and give me the output of that?

Is there a way to specify the "DRM" device? Any tips are much appreciated.

There was a way in earlier versions. Though I don't think you'd get any further with the ability to manually specify the DRM device, since this error is more likely caused by no DRM devices being present on your system at all

@tobiasht
Copy link
Contributor Author

Thank you so much for the help. I managed to solve the problem by restoring the raspberry pi and using another driver for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants