On Thu, 2005-10-27 at 17:19 +0300, Ville Syrjälä wrote: > On Thu, Oct 27, 2005 at 02:47:35PM +0100, Laurence Abbott wrote: > > > > Hi, > > > > I've been using DirectFB with a Unichrome board for a while (vdr + > > softdevice). If I run this from a shell on the console, I can kill it > > with CTRL-C, switch virtual terminal, etc.: the keyboard responds. > > > > Now I'm setting up a system with a Matrox G450 card in it. Using the > > same home-built package of DirectFB 0.9.23 on the Matrox system, I lose > > control of the keyboard when I run a DirectFB app! If I run df_xine it > > will play back a file but then never return back to the shell. I have to > > kill the process over ssh. The same thing happens with vdr + softdevice: > > if I run it from a shell, I cannot kill it or switch vt, and need to > > kill it over ssh. If I start the same things over ssh, I can kill them > > with CTRL-C. > > > > df_xine has a whole load of key commands whilst it is running but they > > are ignored on the Matrox system. Come to think of it, I was never > > really convinced that pressing keys did anything on the Unichrome system > > but at least I could exit! > > > > Is this a common problem? I have definitely built the keyboard input > > module (should this be enabled or disabled in /etc/directfbrc? I've > > tried both and got the same effect). dfbinfo does tell me that it is > > loading the keyboard module. > > > > I'm using no-vt on both systems so that I can run the apps as non-root. > > no-vt disables the keyboard driver. The linux_input driver will work in > that case.
Hmmm...I'll check whether that got built: seeing as it works on one system and not on another (same package used on both) it must have been! It's possible that the kernel configs regarding input drivers are different on the two systems: I'll look into it. > no-vt isn't really required to run as non-root. You just have to set the > /dev/tty permissions as described in the README. I'll have another look but I'm sure that I needed it to get it to work. Maybe my problem there was that it was running from an init script (as non-root) and permissions hadn't been set up by that point. > I'm not sure why ctrl-c doesn't respond though. Since DirectFB isn't doing > anything with the tty (due to no-vt) it should still respond to the > keyboard. At least it did so for me at one point. That was when I just > started using the linux_input driver. A totally frustrating thing when you > press ctrl-c in an xterm and the whole XDirectFB process dies :) Further info: if I use mplayer with the dfbmga output driver, all key presses result in 'no key bound' or whatever the messge is. On the Epia / Unichrome system, I have vdr + softdevice running with no-vt. Any console output is covered up by the OSD. When it is running, I can use the console, switch vt, etc., and see what I'm doing over the top of the TV picture! Not always the easiest thing to read but can be helpful at times (such as ssh-ing into the Matrox system and killing things ;)) I'll try some more things this evening. Cheers, Laz _______________________________________________ directfb-users mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
