[visionegg] Re: Maximum priority mode and Debian GNU/Linux

Hi Hubertus,

Time constraints have prevented me from testing timing too deeply in linux -- as I've said before, once I found out that things mostly work in Windows without skipping frames, I stopped pushing further in linux. So, these answers are unfortunately not tested.

What happens if you lower the priority from 99? After trying that, the next place I'd go looking is to follow up on the idea that in X Windows, graphical display requires at least 2 processes: 1) your application and 2) the X server. So, if the X server is shut out of the CPU, nothing will ever display. This suggests to me that you could try raising the priority of both processes simultaneously or perhaps even trying a multi-processing computer.

Cheers!
Andrew

Hubertus Becker wrote:

Hi all,

Does anyone know how to get the maximum priority mode in
VisionEgg under Debian GNU/Linux to work properly? If I set
'VISIONEGG_MAXPRIORITY = 1' in the 'VisionEgg.cfg' file I get the
following messages in the command line

# ./dots.py
2005-05-01 13:48:47,522 (2860) INFO: Script ./dots.py started Vision Egg 1.0-cvs with process id 2860.
2005-05-01 13:48:48,157 (2860) INFO: Requesting window 800 x 600 0 bpp (0 0 0 0 RGBA).
2005-05-01 13:48:48,175 (2860) INFO: OpenGL 1.3 Mesa 4.0.4, Mesa GLX Indirect, Mesa project: www.mesa3d.org
2005-05-01 13:48:48,176 (2860) INFO: Video system reports 32 bpp (8 8 8 0 RGBA).
2005-05-01 13:48:48,184 (2860) INFO: Setting priority for POSIX-compatible platform to policy SCHED_FIFO and priority to 99

After the messages the machine stop working immediately and
hang. Any tips are greatly appreciated.

Best,

       Hubertus





======================================
The Vision Egg mailing list
Archives: http://www.freelists.org/archives/visionegg
Website: http://www.visionegg.org/mailinglist.html

Other related posts: