On Tuesday, January 29, 2013 05:12:45 PM Dr. H. Nikolaus Schaller wrote: > Hi, > using the new 3.7 kernel with debian squeeze Xorg also makes troubles... > > Am 28.01.2013 um 00:36 schrieb Neil Jerram: > > Radek Polak <pson...@seznam.cz> writes: > >> On Friday, January 25, 2013 04:37:05 PM Iain B. Findleton wrote: > >>> Thanks for the hint. > >>> > >>> When I start QM from the qtmoko menu, I get nothing but a blank screen > >>> and an input for an application. I have updated the files in > >>> /opt/qtmoko/etc/qm as described in the Openmoko wiki, but the menu > >>> items for favourites shows nothing. Is there any other updated > >>> documentation? Need I install something? > >> > >> Install your favourite X application - e.g. foxtrotgps and then select > >> "Favourites" from context menu. The application should appear there (if > >> it has .desktop file in /usr/share/applications). Then you can also > >> configure it some more - like fullscreen, virtiual keyboard... > > > > It seems to me that there are a couple of problems here; please see the > > attached patches. > > > > From 2764304b0a4ad50e608f57bb00ecc1388217b9fc Mon Sep 17 00:00:00 2001 > > From: Neil Jerram <n...@ossau.homelinux.net> > > Date: Sat, 26 Jan 2013 00:23:34 +0000 > > Subject: [PATCH 1/3] qx - fix setting of DISPLAY variable > > > > --- > > src/3rdparty/applications/qx/qx.cpp | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/src/3rdparty/applications/qx/qx.cpp > > b/src/3rdparty/applications/qx/qx.cpp index 6c22ba1..65a651e 100644 > > --- a/src/3rdparty/applications/qx/qx.cpp > > +++ b/src/3rdparty/applications/qx/qx.cpp > > @@ -172,7 +172,7 @@ QX::QX(QWidget *parent, Qt::WFlags f) > > > > screen = QX::ScreenMain; > > > > if(getenv("DISPLAY") == NULL) > > > > - setenv("DISPLAY", "0:0", true); > > + setenv("DISPLAY", ":0.0", true); > > > > #if QTOPIA > > > > powerConstraint = QtopiaApplication::Disable; > > the event-numbers have changed between 2.6.32 and 3.7 kernels. > > > touchscreen = 0 > > Power = 2 > > AUX = 5 > > > > although I suppose even better would be to use the symlinks > > > > /dev/input/touchscreen > > /dev/input/power > > /dev/input/aux > > Yes, definitively. The event numbers aren't guaranteed. > > > Are those symlinks created on Freerunner too? If so, that's the best > > overall solution. > > Hm. How do you get these symlinks? On my 3.7 system they are not > created automatically at all. And the touch is even missing in
General advice - try in QtMoko, if it works there search in this doc: https://github.com/radekp/qtmoko/blob/master/doc/txt/old/debian_rootfs_howto_gta04_squeeze.txt In this case you need udev running and download this rules: cd /etc/udev/rules.d wget https://raw.github.com/radekp/linux-2.6/v3.7-gta04-qtmoko-v52/GTA04/udev-rules/hso.rules wget https://raw.github.com/radekp/linux-2.6/v3.7-gta04-qtmoko-v52/GTA04/udev-rules/input.rules > Another issue is that evtouch (from debian squeeze) is segfaulting. > And tslib (also from squeeze) is no longer recognizing any events > since the kernel presents a different EV_VERSION. Same general advice, just a few lines below: wget http://lindi.iki.fi/lindi/tslib/libts-0.0-0_1.0-8lindi1_armel.deb dpkg -i libts-0.0-0_1.0-8lindi1_armel.deb Regards Radek
_______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community