Hi all, After a bit more back and forth recently on the graphical environment on non-Intel cards issue, I thought I'd have a look at it myself when I (by chance) ended up needing to set up an SDK chroot on my (NVidia powered) laptop.
As some people rightfully pointed out, MeeGo failed to produce anything graphical inside the started Xephyr instance, which didn't overly surprise me given I have heard mixed reports about it working and not working. What did, however, surprise me was that, if I start Xephyr from outside the chroot environment: bur...@virgin:~$ Xephyr :2 -ac -host-cursor -screen 1024x768 and then proceed to launch the GUI inside the chroot: r...@meego-netbook-sdk:/# startmeego I seem to actually get something usable, even if not lightning fast (think Maemo scratchbox speeds..). (see: http://w00t.dereferenced.net/meego-gui.png) Is this something that we can use to help identify/fix up the SDK to work more robustly on non-Intel cards? (I haven't updated the wiki page with these findings yet as I've no clue how to word the instructions. Anyone up to the challenge?) Regards, -- Robin Burchell http://rburchell.com _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
