SDK/Docs/1.1/Troubleshooting

$ md5sum <image file>

The images are large so you might try a download program that handles connection interrupts, such as wget:

$ wget --continue <link to file>

If you connect the internet by a proxy,you should use:

# sudo mad-admin fetch [-x proxyhost[:port]] URL|URL_ALIAS

Examples:

# sudo mad-admin fetch -x http://proxy.host:8080 http://server/path/file.tgz

Note: see also MADDE command manual (for Linux: /usr/share/madde/docs/MadTools.html)

Or you can do it like this:

# zypper addrepo -f http://repo.meego.com/MeeGo/sdk/host/repos/meego/1.1/meego-sdk.repo"

# export http_proxy="http://username:passwd@<proxy_IP>:<proxy_port>"

# mad-admin create -f <target> 

[Ubuntu 10.04, NVIDIA, handset 2010/10/31] QMAKESPEC has not been set when running qmake.

$ mad -t meego-handset-ia32-1.1 qmake
-unix is deprecated.
QMAKESPEC has not been set, so configuration cannot be deduced.
Error processing project file:
/home/user_x/work/meego/qthello-handset/qthello-handset.pro

Set QMAKESPEC using a command such as the following (bash):

$ export QMAKESPEC=linux-g++

This is a known issue: see bug 8938
The solution is Compiling MTF applications here.

[Ubuntu 10.04, NVIDIA, handset 2010/10/31] Depending on the umask setting during installation, access to the SDK components may not be available to non-root users. This results in errors such as the following:

$ mad -t meego-handset-ia32-1.1 qmake
-unix is deprecated.
Could not find mkspecs for your QMAKESPEC(linux-g++) after trying:
	/usr/lib/madde/linux-i686/sysroots/meego-core-ia32-madde-sysroot-1.1-fs/usr/share/qt4/mkspecs
Error processing project file:
/home/user_x/work/meego/qthello-handset/qthello-handset.pro

Change the permissions on the SDK installation (/usr/lib/madde/linux-i686/ on Ubuntu) using commands such as the following:

find ./ -perm 700 -exec chmod 755 {} \;
find ./ -perm 600 -exec chmod 644 {} \;

Ubuntu 9.04, Intel graphics

Could not access KVM kernel module: No such file or directory
failed to initialize KVM 

or running below command did not show up QEMU window.

mad remote -r meego-handset-ia32-qemu-1.1.20101031.2201-sda-runtime poweron

In SDK 1.1 update release, the launching scripts has been updated to check whether the KVM module is loaded. If not, QEMU will start without "-enable-kvm" option. So with 1.1 update release, user should be able to launch QEMU always, although slow if KVM is not enabled. We did not start KVM automatically because of the KVM bug.

error while loading shared libraries: /usr/lib/libGL.so.1:
cannot restore segment prot after reloc: Permission denied
  

This error is due to SELinux security policy settings. There are two possible solutions:

1. Temporary (needs to be repeated on each reboot)

   sudo /usr/sbin/setenforce 0

2. Permanent
   In the /etc/selinux/config file, set the value of the enforcing variable to disabled.
   You will also need to do sudo /usr/sbin/setenforce 0 to make this change immediately. SELinux should be disabled on the next boot.

After disabling the selinux enforcement policy the QEMU version from 1.1 SDK can then be launched via mad tools:

mad remote –r meego-handset-ia32-qemu-1.1.20101031.2201-sda-runtime poweron

glxinfo|grep renderer

If the output is "Software Rasterizing", the feature is not enabled. In such case, one possible reason is that the graphic driver on host is not properly installed. On both linux and windows system, QEMU could disable graphic acceleration automatically if it failed driver capability check.

Meanwhile, the benefit of graphic acceleration relies on the power of host graphic card. It is especially true for Windows system. Advanced graphic card could help.

$ sudo mad-admin create -f -e meego-handset-ia32-qemu-1.1.20101031.2201-sda-runtime
Extracting QEMU runtime meego-handset-ia32-qemu-1.1.20101031.2201-sda-runtime
.....9....8....7....6....5....4....3....2....1....0
Creating missing links... done.
$ mad-admin list runtimes
qemu-n900-pr12                                         (installable)
rx48-diablo                                            (installable)
meego-handset-ia32-qemu-1.1.20101031.2201-sda-runtime  (installable)
meego-netbook-ia32-qemu-1.1.20101031.2037-sda-runtime  (installable)

$ sudo mad remote -r meego-handset-ia32-qemu-1.1.20101031.2201-sda-runtime poweron
Starting QEMU runtime meego-handset-ia32-qemu-1.1.20101031.2201-sda-runtime
This may take some time ...
$ ssh meego@127.0.0.1 -p 6666
ssh: connect to host 127.0.0.1 port 6666: Connection refused

sudo rm -rf /etc/ssh/*key*
sudo /etc/init.d/sshd start 

On Linux host system, you could mount into the image and do the change directly as well:

sudo mount -o loop,offset=512 xxx.raw /mnt/
sudo rm -rf /mnt/etc/ssh/*key*
sudo umount

Systems which have had trouble with kqemu: Intel Core 2 Duo P9400 in Thinkpad T400; Intel Core 2 Q9400 in HP7900 Ultra-slim; Intel i5 (sandybridge)

One trick to try is to enable CPUID limit from Host PC system BIOS. Then start kqemu by:

net start kqemu

NOTE! In general it's not recommended to touch this BIOS setting.

net stop kqemu