View Single Post
Posts: 2 | Thanked: 0 times | Joined on Dec 2009 @ Austria
#1
Hi! Some great stuff going on here!


I've successfully managed to install and setup SDK+ in a chroot environment in my Debian/sid system running a 64 bit kernel. I'm completely new to this, so some things are a bit mysterious to me.


Info first:
Code:
maemo-sdk list rootstraps
fremantle5.0minimal_armel
*fremantle5.0minimal_i386

I've successfully managed to install maemopad using
Code:
sb2 -eR apt-get install maemopad osso-icons-default

The I try to start the gui:
Code:
maemo-sdk start gui
Starting up runtime for fremantle5.0minimal_i386...
Forcing bit depth to be 24.
Done
But Xephyr stays blank.

I get no error message except for one strange one:
Code:
maemo-sdk stop gui
Stopping runtime fremantle5.0minimal_i386...
Warning: Gui Stop (af-sb-init.sh stop) returned with an error.

Please give me some advice, I'm a bit lost at the moment.


Edit:
Forgot to tell you, that I can display xeyes from the chroot without problems. So I don't think that problem is related to Xephyr itself. And I've even tried with diablo4.1.2_armel rootstrap.

Edit 2:
I've now tried to use maemo-sdk in native 64 bit environment and Xephyr starts and displays everything correctly when using diablo 4.1.2.

Last edited by AlexH; 2009-12-11 at 00:03.