Now the Meego Handset can run on the snapdragon platform (still with some display error), following guides as below from Carsten:
1. copy /usr/share/meegotouch/targets/N900.conf to /usr/share/meegotouch/targets/Default.conf 2. edit /etc/profile.d/qt.sh: export QT_GRAPHICSSYSTEM=native then chmod +x etc/profile.d/qt.sh 3. sed -i 's!mcompositor!meegotouchhome -software!g' $INSTALL_ROOT/etc/sysconfig/uxlaunch 4. echo 'export M_USE_SOFTWARE_RENDERING=1' >> $INSTALL_ROOT/home/meego/.bashrc Thank you Carsten! Hope helpful to other people. Best Regards Carsten Munk <[email protected]> Sent by: [email protected] 2011-04-28 14:12 To Bo Liu <[email protected]> cc "[email protected]" <[email protected]> Subject Re: [MeeGo-dev] how to port meego to snapdragon Bo, So, chances are that you are not having any kind of GLESv2/EGL acceleration on your device file system, for your device, so the Handset UX won't work properly. It might be possible to work around with hacking in "-software" flags. In truth, you should rather spend time on getting the MeeGo UX running ('tablet' images), which is more likely to succeed and has longer life expectancy than current Handset UX. /Carsten 2011/4/28 Bo Liu <[email protected]> It seems that no "com.meego.core.MInputMethodStautsIndicator" service available? Bo Liu/RC-MI/LENOVO 2011-04-28 09:34 To Auke Kok <[email protected]> cc Cornelius Hald <[email protected]>, "[email protected]" < [email protected]> Subject Re: [MeeGo-dev] how to port meego to snapdragonLink Dear all, content of file /home/meego/.xsession-errors is as below. seems that there are many errors... localuser:meego being added to access control list Initializing tracker-store... Starting log: File:'/home/meego/.local/share/tracker/tracker-store.log' sion 0 Build Operating System: Linux 2.6.37-4-default armv7l Current Operating System: Linux localhost.localdomain 2.6.32.9 #11 PREEMPT Fri Apr 15 08:05:58 EDT 2011 armv7l Kernel command line: root=/dev/mmcblk0p1 rw rootfs=ext2 init=/sbin/init rootwait noinitrd console=ttyMSM2,115200n8 androidboot.hardware=qcom Build Date: 24 April 2011 07:32:54PM Build ID: xorg-x11-server 1.9.0-11.20 Current version of pixman: 0.20.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (++) Log file: "/tmp/Xorg.0.meego.log", Time: Sat Jan 26 17:49:30 1980 (==) Using config file: "/etc/X11/xorg.conf" (==) Using config directory: "/etc/X11/xorg.conf.d" Primary device is not PCI (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument ...... (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument (EE) PreInit returned NULL for "cm3602-proximity" (EE) PreInit returned NULL for "kxsd9" (EE) PreInit returned NULL for "W88_CTP" (EE) PreInit returned NULL for "surf_keypad" (EE) PreInit returned NULL for "docking event" (EE) PreInit returned NULL for "8k_handset" sh: /usr/bin/gnome-screensaver: No such file or directory Adding Master Pointer: Virtual core pointer ( 2 ) Skipping non-Touch device: Virtual core XTEST pointer ( 4 ) Skipping non-Touch device: cm3602-light ( 6 ) Adding Master Pointer: Virtual core pointer ( 2 ) Skipping non-Touch device: Virtual core XTEST pointer ( 4 ) Skipping non-Touch device: cm3602-light ( 6 ) libEGL warning: DRI2: failed to authenticate Adding Master Pointer: Virtual core pointer ( 2 ) Skipping non-Touch device: Virtual core XTEST pointer ( 4 ) Skipping non-Touch device: cm3602-light ( 6 ) Loading meegotouch-qt-style for plain qt app. PhoneProvider Initializing phone provider PhoneProvider First subscriber appeared, connecting to CallVolume "modem count:" 0 Adding Master Pointer: Virtual core pointer ( 2 ) Skipping non-Touch device: Virtual core XTEST pointer ( 4 ) Skipping non-Touch device: cm3602-light ( 6 ) Use system compositor void MIndicatorServiceClient::connectToIndicatorDBus() MInputContextDBusConnection was unable to connect to indicator server: "The name com.meego.core.MInputMethodStatusIndicator was not provided by any .service files" Adding Master Pointer: Virtual core pointer ( 2 ) Skipping non-Touch device: Virtual core XTEST pointer ( 4 ) Skipping non-Touch device: cm3602-light ( 6 ) Not loading meegotouch-qt-style for meegotouch app. meegotouch-qt-style loading success. Only the MeeGo and the native graphicssystem are supported to create shareable pixmaps. "/usr/bin/sysuid" Connection timeout when waiting for packet 3 Retrying. "/usr/bin/sysuid" Connection timeout when waiting for packet 3 Retrying. "/usr/bin/sysuid" Connection timeout when waiting for packet 3 Retrying. .... "/usr/bin/sysuid" Connection timeout when waiting for packet 3 Retrying. "/usr/bin/sysuid" Connection timeout when waiting for packet 3 Retrying. ... (repeat many times) "/usr/bin//meego-im-uiserver" Connection timeout when waiting for packet 3 Retrying. "/usr/bin/meego-im-uiserver" Connection timeout when waiting for packet 3 Retrying. ....... (repeat many times) Best Regards Auke Kok <[email protected]> 2011-04-28 02:22 To Bo Liu <[email protected]> cc Cornelius Hald <[email protected]>, "[email protected]" < [email protected]> Subject Re: [MeeGo-dev] how to port meego to snapdragon On 04/27/11 01:49, Bo Liu wrote: > > Dear Cornelius and Martin, > > After all the rootfs was built with attached .ks successfully. > > Then I copied this rootfs into phone's SD card, which was mounted after kernel booting. > > Then the whole system (kernel + rootfs) run, but no meego GUI appears. I cat the /var/log/uxlaunch.log and found that Xorg always exited. The log is below. > > On the serial console, if I run command: > $/usr/bin/Xorg :0 -logfile /tmp/Xorg.0.meego.log -dpi 120 -nolisten tcp -noreset -auth /home/meego/.Xauthority vt2& > > then "x" cursor appeared. So it seems that X server can run mannually. > > After Xorg running, I run: > $export DISPLAY=":0" > $xterm > then xterm window appeared. So it seems that client can connect to X. > > So maybe the failure result from autostarting of desktop? the 10 second delay suggest that Xorg failed to start with the options that uxlaunch passes. did you build your own Xorg? please include the contents of /home/meego/.xsession-errors, after the normal graphical startup crashes. (do not start a manual Xorg). This should provide some debugging information as to why Xorg failed to start. Auke _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
