Read the statement by Michael Teeuw here.
Flickering in portrait mode
-
Same here, if I’m not using the legacy driver, all hell breaks loose.
-
Update, the 2.6.0 does the same thing.
From @dazza120 and @BKeyport , I will look further into using different drivers. If either of you can point me to where I can get instructions on installing lagacy or normal drivers, it will save me much searching and testing.
I am also considering trying the server and web page route, even if it is on the same machine. This is because the long web page test with the youtube video didn’t fritz out on me.
Still looking for clues (like which version of Rasbpian/MM/drivers did this problem start) so I can continue my search for a solution.
-
sudo Raspi-configAdvanced Options -> GL Drivers -> Legacy.
“legacy” and “normal” drivers are the same thing.
-
PROBLEM SOLVED ! ! ! Thanks @BKeyport for the really easy way to change the driver.
My screen has been running 48 hrs with no problems. I don’t know if using the old drivers has any adverse impact, but this is all I am using this particular Pi for, so it doesn’t impact me (yet?).
Many thanks for the advice. I am going to mark this thread as solved (as soon as I figure THAT out)
-
No problem. The “adverse effect” is apparently more CPU use, but, as most MM projects are on single use Pi computers, there’s no issue IMO.
-
@lamachine you may find youll need to setup a Cron Job as Legacy taxes the Pi memory a little more and causes the temps to be higher a heatsink is a good addition all is still well within spec so nothing to worry about.
I’ve got a fan on mine as well so when I have my monitor on which basically means I’m using the Pi and with that drops the Pi temp about 13c, when the Pi is just having the modules run in the background temps in a 20c room are about 46/47c, with the monitor powered up and playing with the Pi temps can go up another 10c so 56c still well within spec and 56c isn’t with the fan going.
-
@dazza120 Course, I can report the opposite, with my setup. While I don’t have exact figures the one thing that seems to have happened is that my system isn’t triggering the temp. icon anymore now that I’m back on the normal driver.
That being said, I’ve got a fan+heatsink on the way for the final setup, there’s no reason not to protect the pi.
