I will give it a shot. I haven't the vaguest idea where to start but will have a go. Can you point me to the existing source code?

http://deb.linuxmce.org/PlutoMO_3rd.sisx

or

http://deb.linuxmce.org/PlutoMO_2nd.sis

Thanks a stack posde... just what I was looking for.

Sadly, still not having luck here. I tried both on the phone which has Symbian edition 5. The PlutoMO_2nd doesn't install at all, the PlutoMO_3rd does install with a bunch of warnings "Security warning: application untrusted....", "Application not compatible with phone", etc.

But when run, it says :"PlutoMO: Unable to execute file for security reasons."

Hmmff.

I thought the "Application not compatible with phone" might be the problem - Symbian 5th ed vs Symbian 3rd so I downloaded a neat little app called http://cdtools.net/symbiandev/home.html called SISContents which allows you to hack the SIS package and I managed to open PlutoMO_3rd.sisx and change the Symbian Edition to 5th, resign the package and upload it to phone.

That seemed to prevent the "Application not compatible with phone" warning but same issue when executing.

I even tried to see if there was a

http://deb.linuxmce.org/PlutoMO_5th.sisx    but I guess not!

So... unless anyone has further suggestions, I'll probably go with the web orbiter once my wireless access point arrives. Or the java one, what about that? Pity, though, because this phone is soon to be replaced when the contract expires and it would be nice to have it lying around the house as a semi permanent orbiter with the bluetooth proximity stuff working.

OK, so I decided to try to send the file manually to the Nokia....

Incidentally, Nokias will tell you their MAC if you dial *#2820# which is quite useful.

sshd into the MD, and ran

Code:

/usr/pluto/bin/SymbianPhoneInstall.sh 5C:57:C8:BF:D9:F7 /usr/pluto/bin/Pluto_S60.sis

But had the same result- the phone asks for a passcode. Bummer.

Not to be thwarted, I stuck a USB stick into the core, copied the /usr/pluto/bin/Pluto_S60.sis file to it, put that in another windows pc and bluetoothed the file to my Nokia. Only to find that the file is zero bytes in size 

Checked back on the /usr/pluto/bin/ folder on the MD and noticed the same. What's with that? So I searched the entire core harddrive and could not find any other copies of the file. Presume this is a problem?

Does anyone know where I can get this file?

I see the other MDs do not have it so I guess it's only added when you turn on the bluetooth in the software setup. so I guess I'll try to redo that on the MD- turn off bluetooth then turn it on again and hope it adds the file correctly this time.

Fantastico! sorted out thanks to the link posted by l3mce in the thread below

http://forum.linuxmce.org/index.php/topic,12175.0.html

Here's the link

https://wiki.ubuntu.com/X/Troubleshooting/FglrxInteferesWithRadeonDriver#Problem:%20%20Need%20to%20fully%20remove%20-fglrx%20and%20reinstall%20-ati%20from%20scratch

Ran these steps on the MD after ssh ing into it and voila! Have it up and running.

Hey l3mce, just wanted to say a big thanks to you for this thread because the link below and Roman's response to it prompted me to try this method with my IBM T30 notebook and finally I have it up and running as a media director. I'm super chuffed about that, thanks a stack. It was also getting to the "failed to setup X" stage and the steps outlined below sorted it out. Thanks again.

*On further review I see that you MAY actually have to purge that fglrx driver. Directions here IF you have problems.
https://wiki.ubuntu.com/X/Troubleshooting/FglrxInteferesWithRadeonDriver#Problem:%20%20Need%20to%20fully%20remove%20-fglrx%20and%20reinstall%20-ati%20from%20scratch

Howzit Karel and other S. Africans

Just getting started on LMCE. I'm in Pietermaritzburg.

And more... so the shortcut is supposed to run

/usr/pluto/bin/ActivateOrbiterFromKDE.sh

Which it does for me but that, in itself, doesn't do anything on my system. So I guess I need to get to the bottom of that. I guess I can first try the manual way as outlined below....

No. but you can send a message to the media director device (for the core/hybrid, this is 1):

/usr/pluto/bin/MessageSend localhost 0 X 1 912 119 "0"

replace X with the PK_Device # of the Media director.

-Thom

and if that works then I know the problem is in the above script trying to figure out the right message and can debug from there.

More on this-

Ctrl-alt-f2 to go to terminal, followed by ctrl-alt-f7 shows frozen ui with some interference lines across top and machine (core) is well hung 

From KDE-desktop, I tried the "Activate orbiter" application and the bouncing gear runs for a bit and then nothing changes. I had a little look at the script behind it and also tried running that from a kde terminal command line and also, nothing happens. Will search the forums a bit to see if anyone else has had this and maybe try to debug a little.

Not sure if you tried this, there suppose to be an desktop link, that relaunches the orbiter.

On my system, its on the top left hand corner.

Thanks for the tip. I think I did and got the bouncing gear for a bit and then nothing. At first I was mighty nervous to click that link because it looked a lot like the original install link! I will check again when I get home, and perhaps have a look at the code it runs and see what it is supposed to do as well.

Has anyone else had this problem with MDs or hybrid/cores. My core is running UI1 because I'm planning for it to sit in the closet when I'm done setting up and not bothering with NVidia on this machine if I can avoid it....

That said, all seems to run ok until I try to switch out of the UI-

Either to get to command line via ctrl-alt-f2 or whatever or if I start the KDE desktop. In either case, I don't seem able to get back to the Orbiter UI.

Actually, I think they're different issues:

If I go to KDE desktop, the machine seems to carry on running OK but I can't get back to the UI. I've tried:

• Clicking on the "Orbiter renderer" in the taskbar but nothing happens
• Logging out of KDE - but then I just get to the KDE login screen
• ctrl-alt-fx
• but then I end up with the problem below:
  

If I go from the UI to a tty, using ctrl-alt-fx key, I can't get back to the UI. As soon as I hit ctrl-alt-f7 I see the UI but it has some blurred stripes at the top and the machine appears to hang. At that point nothing but a hard power-off works... I think, though I haven't tested extensively yet, it even stops functioning as a router/dhcp server etc.

I will investigate further but has anyone had these issues?

[First Prize]

Ok, did some thorough searching of the forums and I have a few new tools to tinker with when trying to get to the First Prize so if I can go just one more night without sleep I can have a crack at that again this evening...

[First Prize:]

Hi All

Trying to keep the budget down and I have an old notebook that I'd like to use to supply basic stereo sound to my old Onkyo stereo AMP in the lounge.

I took out the HDD which was faulty and noisy and have successfully used the T30 to run as a thin-client off fedora 13 (using ltsp) and that worked reasonably for driving the audio.

Now that I'm embracing LMCE   I would like to try to get similar functionality there- basically be able to play my music through the amp. Theoretically, it should be a nicer solution, too, because using a mobile orbiter (or any other) I can control the music remotely.... pretty cool.

The problem I'm having, though, is the setup of the MD. When trying to start the AVWizard the first time, I get a blue screen with a text box saing "Failed to setup X". Naturally, this doesn't surprise me- after all it's an ATI Radeon card and I knew we need Nvidia chipsets for stuff to work nicely in LMCE. But... I don't need high quality video here, or even video at all for that matter, or even graphics... the MD could run headlessly once set up and be controlled via orbiter. But it first needs to be set up!

So, I'm wanting to try a couple of routes and need some advice-

First Prize: Try to get the AVWizard to work- get past the "Failed to setup X" point.

• I've looked at the http://http://wiki.linuxmce.org/index.php/Display_Drivers wiki and haven't had much luck with that - it appears I already have the latest drivers but
  the Xorg log still shows "Fatal error No screens" or something similar
• I've tried to replace xorg.conf.pluto.avwizard with an xorg.conf file off the web that supposedly works for the T30 but xorg.conf.pluto.avwizard seems to get "overwritten" everytime the MD is restarted, perhaps because AVWizard is running?

Second Prize: Bypass AVWizard somehow, "force" setup and just start it without X.
Is this an option? Can I potentially just setup my MD in the webadmin page. Video setup really isn't important to me provided the sound works. I probably won't even use the screen but obviously if the MD won't start up properly because of incorrect video config that would be a problem.


Any thoughts/advice/ help welcome. I'll post my findings here.

Aha- the link below shows how to go about a bit of manual intervention. Will try this evening.

http://forum.linuxmce.org/index.php/topic,157.0.html

Starting a new thread on this one because I seem to have sorted out the MD to some extent so this is now more about how to get the above orbiter to work.

Some progress with onboard bluetooth of md (hp 6710b notebook)- UI detected my symbian 60 phone but when I tried to select it in the wizard, the phone popped up a message asking for a passcode or passkey to receive info from the MD. 1234 did not work. Should it do that? What passcode should I use? Now it doesn't seem to detect it any more. Will get into admin site and see if I can see the device.

I can get the MD to detect the device, I choose Symbian S60 but then when (I presume) the MD tries to send the app to the phone (Nokia 5800), the phone responds wanting a passcode. It (the phone) won't do anything until you enter some number.

I tried entering 1234, but no luck; I tried just waiting without entering anything. Either way, the MD soon says it failed to setup the device, try again or contact support.

I've searched the forum for this but it only comes up once or twice. The one solution is to open a kde desktop and then make the phone discoverable and pair at there. That didn't work for me... nothing popped up and when I tried from the MD side to search for the device it wants to make it an "input" device and can't find any "input" services on it.

Any ideas? What I didn't try, I think is searching for the "moon-33" from my phone and trying to connect so I'll try that one this evening.

However, to get back to the beginning, I found deleting the orbiter for the phone from the admin webpage, then restarting the MD and turning bluetooth on the phone on seemed to work to get the pop-up again.

Another question- can I just download the orbiter software to my phone some other way and then try to make it work?

Some progress with onboard bluetooth of md (hp 6710b notebook)- UI detected my symbian 60 phone but when I tried to select it in the wizard, the phone popped up a message asking for a passcode or passkey to receive info from the MD. 1234 did not work. Should it do that? What passcode should I use? Now it doesn't seem to detect it any more. Will get into admin site and see if I can see the device.