Thanks to both of you !

Indeed, xterm showed that it was missing libsdl-ttf, which the deb package had not forced me to install. I have installed it but still get an error related to the fonts:

Code:

X Error of failed request:  BadName (named color or font does not exist)
  Major opcode of failed request:  45 (X_OpenFont)
  Serial number of failed request:  8
  Current serial number in output stream:  10

progressing :-)

I have tried copying /usr/share/fonts/truetype/msttcorefonts/ from the core, but no luck.

Hi Michael,

Nokia 770 here, OS 2007-hacker edition fresh install. I'll give some links to try answer the queries above...

I have activated red pill (http://www.deal-times.com/content/view/36/), added the maemo repository and maemo extras repository (http://maemo.org/community/wiki/ApplicationRepositories#head-369f33ae286ce0361aa5640a92300b4d6314346a)

then I installed the orbiter for OS2007 (plutohomeorbiter-2.0.0.45-01_armel.deb), using the deb on the same page for the dependencies.

The orbiter installed fine, but when I launch it, it says " PlutohomeOrbiter - loading" for a few seconds, then nothing happens.

Any idea how to troubleshoot this ?

Sam

I had trouble getting the gc100 recognized. Some troubleshooting led me to find that there was a bug in the gc100 install script that came with LMCE 1.1-b2, so that it would not detect the MAC address of the gc100. So I have made some dirty hacks to hardcode the MAC address, you can find the info in the post here: http://smart-home-blog.com/archives/688 (comments section)
I should file a mantis for this, but I don't know if I am the only one with that same prob.

Same for me, what I want is the N800 skin...

LMCE includes MythTV and using this you should be able to view and record from a DVB card, if your model is supported.

In the admin site, going to Advanced->Configuration->Phone setup you end-up on the asterisk management portal. This page: http://aussievoip.com.au/wiki/Tested+and+working+SIP+provider+configurations#Voxalot gives you some example of configurations for known Voip providers.

Of course this doesn't add them in the list in the MCE guy, but at least you can add any provider you like.

hope this helps

Many users are now on 1.1 beta2 and are investing a lot of efforts to configure their home, asterisk and cover art, or maybe some custom drivers...

Once the next version of LMCE comes out, what will the upgrade procedure be in order to get a "clean" install without loosing all the settings ?

I know it's hard to say when the release is not even out, but this can be seen as a feature request... for documentation :-)

I would like to upgrade to the latest stable version of slimserver (http://wiki.slimdevices.com/?DebianPackage).

Is it ok to do so, or would this break the pluto-slimserver-plugin ?

I confirm, by replacing all occurrences of  FK_File to CoverArtScan.FK_File, it works.
Thank you 1000 times !
Is there a bug filed already so it gets fixed in the next release

Hi Bobpaul,

so far I'm running as you suggested the orbiter on display :1 and KDM on display :0, two separate servers.
This does what I need as I can easily switch from one to the other, though there are still some glitches: alpha blending does not work and the flicker background is not visible. I'll try to swap the displays.

Anyway, the original question of starting the core automatically without X is still very interesting.

most of the options in /etc/pluto.conf are quite obvious.
But I'm wondering what's the meaning of these ?

Display = 0
It it the X display? Meaning, one could use this to run the orbiter on a separate head ?

SharedDesktop = 1

DesktopActivated = 1

thanks

thanks Cj_MaN, that's useful info.

I'm still not clear how to start the core services without user intervention while still running KDM.

Indeed, the dedicated LMCE scenario you mention above uses /usr/pluto/bin/Startup_Core-Hybrid.sh, which starts X and then /usr/pluto/bin/lmce_launch_manager. What I am looking for is a normal KDM start, but have the pluto core services running in the background.

The /etc/pluto.conf autostart options you mention relate to the launch-manager, which is a graphical application that requires the user to enter root credentials when started as a user (e.g. with KDM autologin).

The /etc/event.d/media-center-startup script calls /usr/pluto/bin/startup-script.sh, which seems to leave some services behind (e.g. slimserver)

What's the correct way to do it ?

I have the same problem and would like to rephrase the question as follows:

on an Hybrid installation (1.1 beta2), how can we start the core services from the init scripts ?

thanks!

if Beta 1 installation went fine, is there a reason to upgrade to beta 2 ?
Or actually re-install beta2, since there is no upgrade procedure yet ?