On Monday 10 April 2017 14:33:35 Diego Roversi wrote: Well, I guess I am stuck with it then. Synaptic, on a 24 bit screen, is much more pleasant to use.
But I also have another problem. The usb inputs from the mouse and keyboard aren't being given near enough priority, so keydown events are being ignored, but I can tap the key again. Hundreds of times more serious is that key-up events are also ignored, which can leave the machine running full tilt in one direction or the other, far enough to crash a tool and smash a $30 carbide tool tip into a cajilion pieces, not to mention wreck the workpiece being worked on. I did have a usb extension cord with a 4 port hub on it, and had similar problems, but found I could generate a 200 megabyte file in 10 seconds with usbmon. Raw noise because the cable wasn't shielded. Moved the bt buttons to the sockets on the pi seemed to fix it but was only temporary. usbmon now see's exactly what the keyboard is sending, nothing more nor less, but the pi is missing the keystrokes. At one point today I was looking at a directories contents, and the screen was scrolling rapidly from the enter key, and I had to hit the enter key 7 more times to stop the scrolling. Arriving at a fix for this is far more important than the screens color depth. I am going to reset it for 16 bit depth to see if that helps. The behaviour today is intolerable. I cannot edit a config file due to the sticky keys effects. > On Sun, 9 Apr 2017 22:21:43 -0400 > > Gene Heskett <ghesk...@shentel.net> wrote: > > I note there's a link to a help site at the top of /boot/config.txt, > > so I went thru the motions of setting it for a 1366x768, 32 bit > > screen. But on the reboot it was just noticably slower, and xwininfo > > now says its a 24 bit screen. And the screen update rate is halved, > > to about 3 frames a second. > > You should consider also that the frame buffer is stored in the ram, > and the gpu had to read like 60 times for seconds to send to the > monitor. It means that it consume 1366*768*3 (24bit) *60 (hz) byte per > second of ram bandwith, almost 200MB/s. And it looks that max ram > bandwith of the raspberry pi3, is around 1300MB/s. Reducing depth > colors can give you a small speed up (at least if your application use > a lot of ram) > > PS: 32bit sometime is really 24bit, with a byte wasted. It's sometimes > used because usually cpu read 16/32/64 bit at a time, so you can see > 32bit in the framebuffer, and still having X saying 24 bit. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
