Gadgetguy wrote: ↑Sun Jun 30, 2019 9:44 pmI guess this post may not qualify as an official bug report but is more my somewhat subjective but distinct impressions of problems I experienced with Raspbian Buster. I loaded a fresh Buster image onto a 32gb Samsung Evo plus sd for my Raspberry Pi 3B. (It is not my fastest sd card - my sandisk extreme plus 32 gb seems to me to be more responsive on things like web browsing etc. but the samsung evo plus still has a pretty good reputation as a speedy card for the Raspberry Pi.)
As I do in stretch, I allocated 128gb ram to the gpu and used the legacy graphics driver. The comparison I make below is for this same card running stretch versus buster
My “impression” is that the Chromium browser version 72 in Stretch is on a 3B noticeably faster, more fluid and responsive and uses less cpu and ram and consequently runs at a lower cpu temperature than Chromium version 74 in Buster. I find in Buster I get frequent temperature warnings that I rarely get in stretch. Buster loads tabs more slowly switches between tabs with more difficulty, and starts to slow down, freeze or overheat with fewer tabs open. I am wondering if Raspbian Buster’s Chromium browser has been optimized for the new Raspberrry 4 at the expense of the experience on older Pi’s. Will stretch’s Chromium be updated periodically as in the past or will it be frozen.
I have done the Ookla internet speed test a number of times with both OS on this same card and I consistently get much higher internet speeds on the Stretch system. (This test may not be definitive because my internet speeds of late seem to fluctuate even operating on the same system)
I am wondering if anyone else has experienced these problems with older Raspberry Pis on Buster’s Chromium browser using the legacy driver? The Chromium experience on Buster with an older pi using the fkms driver is even more problematic with more frequent freezes and artifacts that stay on the screen untill reboot.
On Stretch I enjoy using vlc player and also omxplayer ( omxplayergui) and they both work well on Buster with the legacy driver. I am wondering if Vlc on stretch will be kept up to date to reflect changes in youtube code etc? I guess if we use fkms on Buster we will lose osd timings and subtitles on omxplayer?
However on Stretch I also use mpv video player (compiled with mmal enabled in ffmpeg) with smplayer as a gui. So far I have not succeeded in getting it to work satisfactorily with hw acceleration in Buster and I don’t want to lose it.
On stretch mpv in smplayer plays just about any video format up to 1080p
( although some in software). By configuring smplayer to open mpv in mpv’s own (overlay) window and by toggling back and forth between full screen and a small defined window I can get gui control of mpv which opens up all kinds of options. Smplayer in addition to using youtube-dl has its own very fast internal youtube code that is kept up to date and by using the open with extension by G Lankow in the Chrome store I am able to speedily and efficiently browse youtube videos and watch them either full screen or in a small overlay window defined as a specific size and at a specific unobtrusive location on the screen so as to permit multi-tasking. To make a long story short I really do not want to lose a functional mpv player on Buster. Has anyone been able to get mpv working in Buster with an older pi?
On Buster using fkms graphics driver and the ffmpeg preinstalled in Buster and the mpv in the buster repository and configuring mpv to use the default gpu driver mpv will play a play a 1080p youtube video albeit at very high cpu usage which quickly results in overheating.
It also “seems” to me that Buster in general is somewhat more prone to overheating in an older Pi.
I do note that glxgears now seems to work fine with the legacy driver.
I look forward to getting a Raspberry Pi 4 at some point but I hope to keep my older Pis working just as well as they did in Stretch.
I hereby retract my above noted bug report(which nobody was paying any attention to anyways!! After experimentation and/or modifications or updates to my buster os on pi 3b everthing I complained about seems to be somewhat copacetic. I now have mpv and smplayer working with mmal hw acceleration and running chromium no longer seems to generate excessive cpu usage and overheating although with chromium it still seems to operate with higher cpu usage and at a higher temperature than in stretch. At the time of my original comments I had been experiencing some intermittent problems with my internet connection speed which may have been part of the problem and I have also made updates and some modifications on buster that I had enabled on stretch, such as enabling zram, reducing swappiness, and changing my hosts file a la:
"Blocking Unwanted Connections with a Hosts File"
I now anxiously and hopefully look forward to an rpi optimized kodi on buster. I appreciate the fact that vlc is now playing formats other than h264 albeit partially in software.