Hi Iḿ trying to take a peak at the new n900 OS. So Ive downloaded the SDK and followed the directions found at
http://wiki.maemo.org/Documentation/...l_Installation

Below is a paste of the console. When I try to start up the graphical emulator I always have a white screen, and then I get some scary looking error messages.

Any help would be appreciated!
Thanks

maemo@maemo-desktop:~$ sudo Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -kb &
[1] 8505
maemo@maemo-desktop:~$ Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed

maemo@maemo-desktop:~$ sudo /scratchbox/login
ERROR: Not allowed to run this as root!
maemo@maemo-desktop:~$ /scratchbox/login

Welcome to Scratchbox, the cross-compilation toolkit!

Use 'sb-menu' to change your compilation target.
See /scratchbox/doc/ for documentation.

[sbox-FREMANTLE_ARMEL: ~] > export DISPLAY=:2
[sbox-FREMANTLE_ARMEL: ~] > af-sb-init.sh start
Note: For remote X connections DISPLAY should contain hostname!
Sample files present.
Starting DBUS system bus
Starting D-BUS session bus daemon
Starting Maemo Launcher: maemo-launcher start failed.
getsockopt level=1 optname=17 not yet supported
Starting Sapwood image server
getsockopt level=1 optname=17 not yet supported
Error setting value: No D-BUS daemon running

getsockopt level=1 optname=17 not yet supported
Error setting value: No D-BUS daemon running

Xlib: extension "Generic Event Extension" missing on display ":2.0".
Xlib: extension "Generic Event Extension" missing on display ":2.0".
Xlib: extension "Generic Event Extension" missing on display ":2.0".
Xlib: extension "Generic Event Extension" missing on display ":2.0".
Xlib: extension "Generic Event Extension" missing on display ":2.0".
Starting hildon-desktop
qemu: uncaught target signal 13 (Broken pipe) - exiting
Starting Keyboard
getsockopt level=1 optname=17 not yet supported
Initializing trackerd...
Starting browser daemon: Xlib: extension "Generic Event Extension" missing on display ":2.0".
Xlib: extension "Generic Event Extension" missing on display ":2.0".
Xlib: extension "Generic Event Extension" missing on display ":2.0".
Xlib: extension "Generic Event Extension" missing on display ":2.0".
Xlib: extension "Generic Event Extension" missing on display ":2.0".
qemu: Unsupported syscall: 314
qemu: Unsupported syscall: 314
Starting log:
File:'/home/maemo/.local/share/tracker/trackerd.log'
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
Xlib: extension "Generic Event Extension" missing on display ":2.0".
Xlib: extension "Generic Event Extension" missing on display ":2.0".
Xlib: extension "Generic Event Extension" missing on display ":2.0".
Xlib: extension "Generic Event Extension" missing on display ":2.0".
Xlib: extension "Generic Event Extension" missing on display ":2.0".
getsockopt level=1 optname=17 not yet supported
browserd
GConf Error: No D-BUS daemon running

[sbox-FREMANTLE_ARMEL: ~] > getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
process 8911: arguments to dbus_bus_name_has_owner() were incorrect, assertion "connection != NULL" failed in file dbus-bus.c line 1235.
This is normally a bug in some application using the D-Bus library.
process 8911: arguments to dbus_bus_name_has_owner() were incorrect, assertion "connection != NULL" failed in file dbus-bus.c line 1235.
This is normally a bug in some application using the D-Bus library.
process 8911: arguments to dbus_bus_name_has_owner() were incorrect, assertion "connection != NULL" failed in file dbus-bus.c line 1235.
This is normally a bug in some application using the D-Bus library.
process 8911: arguments to dbus_bus_name_has_owner() were incorrect, assertion "connection != NULL" failed in file dbus-bus.c line 1235.
This is normally a bug in some application using the D-Bus library.
process 8911: arguments to dbus_connection_send() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3099.
This is normally a bug in some application using the D-Bus library.
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
getsockopt level=1 optname=17 not yet supported
qemu: uncaught target signal 11 (Segmentation fault) - core dumped

Well the error message Xephyr present are normal. Some of the errors in the scratchbox are normal. But the problem appears that dbus didn't start. I'm not sure why it didn't. But you can try:
First to see if the dbus service starts. If not, do:
That should restart the scratchbox. And then hopefully dbus will start.
I'm not familure at all with the maemovmware sdk image, so if that doesn't work I have no idea what is broken in it.

I do know the "vpc-sdk" virtualpc sdk image will run in vmware properly, .(http://vpc-sdk.garage.maemo.org)

Nathan
P.s. disclaimer I'm the developer of the vpc-sdk image; not trying to push it; just have gotten feedback that it does work on vmware.

You are using FREMANTLE_ARMEL and try to use this in GUI mode. As explained in the FAQ this is not supported, and a known QEMU bug. Please use FREMANTLE_X86 instead if you intend to run the GUI.