search

Hexxeh / rpi-firmware

Firmware files for the Raspberry Pi
Other
778 stars 208 forks source link

xrandr broken: failed to get size of the gamma for the output default #239

Open alanbork opened 4 years ago

alanbork commented 4 years ago

after rpi-update 039088f7d929b0d1cc49e8d2012df0652f908518

startx works fine, but if I try to run xrandr: xrandr: Failed to get size of the gamma for the output default and it just reports one resolution: 576x416

as far as I know my configuration is stock other than running rpi-update. And yes, it worked fine minutes before I ran rpi-update.

alanbork commented 4 years ago

realized I left out some useful details:

dtoverlay=vc4-fkms-v3d

Linux raspberrypi 5.4.61-v7l+ #1339 SMP Tue Sep 1 18:51:27 BST 2020 armv7l GNU/Linux

popcornmix commented 4 years ago

Can you identify the exact update which caused this. See: https://github.com/Hexxeh/rpi-firmware/commits/master

If you click on each commit the end of the url contains a git hash. Run sudo rpi-update <hash> to revert back to that version. Report the first version with this error.

alanbork commented 4 years ago

That would be a lot easier if there was a way to tell what the previous commit number (git hash) I was running was. Then I could do a binary search, rather than a serial search. I was at least a month behind, maybe two before updating.

On Wed, Sep 2, 2020 at 3:59 AM popcornmix notifications@github.com wrote:

Can you identify the exact update which caused this. See: https://github.com/Hexxeh/rpi-firmware/commits/master

If you click on each commit the end of the url contains a git hash. Run sudo rpi-update to revert back to that version. Report the first version with this error.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Hexxeh/rpi-firmware/issues/239#issuecomment-685620654, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANPGZ5MHKX72ILGV2HQOLIDSDYQPTANCNFSM4QSLWIRA .

alanbork commented 4 years ago

This is going to be tricky to diagnose because it seems to come and go with reboots. Either it always works fine or it always fails.