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

Using Raspbian on a Raspberry pi zero W doesn't retrieve any graphics info #66

Closed
jjtbsomhorst opened this issue Aug 22, 2017 · 13 comments

Comments

@jjtbsomhorst
Copy link

Hi,

I'm currently using your package for retrieval of the graphics information of the system. On my windows device I get the information I need ( resolution of all connected displays). On my raspberry pi zero W on the other hand I get the following:

{
"controllers": [],
"displays": [
{
"connection": "default",
"main": false,
"builtin": false
}
]
}

@sebhildebrandt
Copy link
Owner

Let me check it on my raspberry machines... Need to see what the issue can be here ...

@jjtbsomhorst
Copy link
Author

Could it be because the resolution is set in the /boot/config.txt

@sebhildebrandt
Copy link
Owner

Not sure right now. I will be at my office tomorrow. There I can test several raspberry machines. OK for you?

@jjtbsomhorst
Copy link
Author

yeah ofcourse. Take your time. I'm just working on a little hobby project 👍

@ItsEcholot
Copy link

Probing the raspberry pi drivers to retrieve the resolution could present itself as very difficult (semi open-source drivers). The solution that comes to mind is like @jjtbsomhorst mentioned to read out the config file under /boot/config.txt.
This approach only works if the resolution has been set manually, as the pi supports getting the screens resolution over CEC. In that case the user would most likely not have defined any resolution in the config.txt.

@jjtbsomhorst
Copy link
Author

@ItsEcholot how would you retrieve the screen resolution when the user has not set the reso in the config?

@ItsEcholot
Copy link

I read somewhere that the pi uses CEC to get information about the timings & resolution from the display.
So I guess an approach would be to use a library like libcec to send the appropriate commands to the display and receive the responses. This obviously would only work on devices that support CEC (you also need a "full" hdmi cable, had some problems getting CEC to work last time because of a cheap hdmi cable).

Another approach would be fbset -s. Although not sure if that reports the correct resolution reliably.

@ItsEcholot
Copy link

@jjtbsomhorst Did the approach mentioned by me (fbset) work for you? This information will help greatly in fixing this issue.

@jjtbsomhorst
Copy link
Author

@ItsEcholot haven't tested it yet. I will come back with my findings when I have time to do so

@jjtbsomhorst
Copy link
Author

I thought, if I have time to write a reaction that I will do it in the future I could also just fire up my raspberry and see what happens. So When I use the command fbset -s I do get the resolution.

@sebhildebrandt
Copy link
Owner

Setting up a new Raspberry today ... maybe I can come up with some fix here ...

@sebhildebrandt
Copy link
Owner

Just commited a fix on GitHub. Will release the npm package (as new version 4.0 with lot of changes / new features) within the next 2 weeks.

@sebhildebrandt
Copy link
Owner

Should work now. Version 4.0.0 published

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

No branches or pull requests

3 participants