Search found 6 matches
- Fri Dec 22, 2017 4:48 pm
- Forum: Troubleshooting
- Topic: Lock-up with experimental gpu driver (full kms)
- Replies: 1
- Views: 752
Re: Lock-up with experimental gpu driver (full kms)
Here is Xorg.0.log in case it is useful [ 6.292] X.Org X Server 1.19.2 Release Date: 2017-03-02 [ 6.292] X Protocol Version 11, Revision 0 [ 6.292] Build Operating System: Linux 4.9.41-v7+ armv7l Raspbian [ 6.292] Current Operating System: Linux raspberrypi 4.9.59-v7+ #1047 SMP Sun Oct 29 12:19:23 G...
- Fri Dec 22, 2017 4:48 pm
- Forum: Troubleshooting
- Topic: Lock-up with experimental gpu driver (full kms)
- Replies: 1
- Views: 752
Lock-up with experimental gpu driver (full kms)
This is more of a bug report than a troubleshoot request, but because the whole pi locks up I don't really know where to file it. Basically using xrandr to switch modes followed by mpv to play a file nearly always loks up the pi. My steps to reproduce (probably not all necessary) Install 2017-11-29-...
- Wed Jan 25, 2017 5:53 pm
- Forum: Raspberry Pi OS
- Topic: Unmount/Mount systematically sets dirty bit
- Replies: 15
- Views: 5385
Re: Unmount/Mount systematically sets dirty bit
Looks like this is not pi specific: http://unix.stackexchange.com/questions ... ounting-it
- Tue Aug 30, 2016 8:59 am
- Forum: C/C++
- Topic: Getting GPU memory usage
- Replies: 4
- Views: 15965
Re: Getting GPU memory usage
Thanks! That's exactly what I was looking for.
- Fri Aug 26, 2016 7:06 pm
- Forum: C/C++
- Topic: Getting GPU memory usage
- Replies: 4
- Views: 15965
Re: Getting GPU memory usage
Thanks. This seems to be returning the total GPU memory size: $ /opt/vc/bin/vcmailbox 0x00010006 0x10 0 0 0 0 0 0 0x0000002c 0x80000000 0x00010006 0x00000010 0x80000008 0x37000000 0x08000000 0x00000000 0x00000000 0x00000000 0x00000000 (128Mb in my case). What I would like is the amount of free memor...
- Thu Aug 25, 2016 10:33 am
- Forum: C/C++
- Topic: Getting GPU memory usage
- Replies: 4
- Views: 15965
Getting GPU memory usage
Is there a better way of obtaining GPU memory usage than using `vcdbg reloc`? Since that requires that you flush the cache first, it's not reliable. The vcgencmd mem_reloc_stats and mem_oom commands are useful, but it would be nice to get the usage before we run out. I notice there is a mem_test com...