LinuxMCE Forums
General => Developers => Topic started by: pigdog on April 09, 2009, 04:17:24 pm
-
Hi,
Don't know if this ever worked I had never tried it before.
Since there is no KDE desktop I thought I'd shutdown my MD's via the Core.
Menu> Advanced> Power> Select the orbiter that you want to control. Select room. Then Power of m/d.
Everyone powers down.
Thanks for the other info jondecker76.
Cheers.
-
The remote power down of the MD is working fine under LMCE 0810
-
Hi,
So my setup has a problem then... when I select one MD and both MD's and the Core shutdown?
Any ideas as to where I could begin searching or should I just wait until the next release, reload and retest?
Thanks.
-
You probably selected the room the core is in.
-
Hi,
I am on the Core system.
So I decided to try it again.
I had the Core and both MD's (Home Theatre and Playroom) running.
Selected Advanced> Power> on the Core.
In the select the orbiter you want to control box in the upper left corner I selected Home Theatre.
On exit Home Theatre was displayed in the box and only Home Theatre.
Then I selected Power Off m/d.
Got Powering off... message and Home Theatre, Playroom plus Core went down.
Am I doing something wrong? Or can you only shutdown a single MD from the MD itself?
I just tried it again this time selecting Playroom only. Everything shutdown.
If this is not suppose to work like this, is there some BIOS settings I'd need to check?
Thanks for your time.
-
I think that's a bug, people have complained about it before if I recall correctly.
-
O.K.
Thanks Zaerc.
If it's a bug, then it's a bug.
I'm only trying to test the alpha. I can't code, can barely dance but I try to help as much as I am able to.
Thanks Posde for making me double and triple check my results.
One off's are a complaint. Being able to replicate at will is an undocumented design feature.
Thanks again.
-
Hello all,
also me like pigdog, encounter the same problem.
If I try to make a power on from my core to my MD situated in another room nothing happens.
If I try to power down the MD from the CORE, both the MD and the Core went down.
What are the possible files to check for make a possible debug about that?
Best regards
Luke
-
Please check your DCERouter.log for hints.
(As a side note: I just tried to power down my MD via the Web Orbiter. No problem here)
-
Hi Posde,
thanks for your suggestion. I've finished now to check the file. It seems that when you send the power down to the MD the message were sent to the core id and not to the md id.
Here the logs (id 19 is the Core [Sottotetto is its room]and not the MD):
05/11/09 19:23:54.452 Received Message from 20 ([36;1mOnScreen Orbiter / Sottotetto[0m) to 4 ([36;1mGeneral Info Plug-in / Sottotetto[0m), type 1 id 323 Command:[35;1mHalt Device[0m, retry none, parameters: <0x6ea9ab90>
05/11/09 19:23:54.452 Parameter 2(PK_Device): 19 <0x6ea9ab90>
05/11/09 19:23:54.453 Parameter 21(Force): <0x6ea9ab90>
05/11/09 19:23:54.453 Parameter 47(Mac address): <0x6ea9ab90>
05/11/09 19:23:54.454 Received Message from 20 ([36;1mOnScreen Orbiter / Sottotetto[0m) to 15 ([36;1mApp Server / Sottotetto[0m), type 1 id 323 Command:[35;1mHalt Device[0m, retry none, parameters: <0xb18feb90>
05/11/09 19:23:54.454 Parameter 2(PK_Device): 19 <0xb18feb90>
05/11/09 19:23:54.454 Parameter 21(Force): <0xb18feb90>
05/11/09 19:23:54.454 Parameter 47(Mac address): <0xb18feb90>
Instead if I make the procedure directly from the md (id 43 [Soggiorno is its room] ) all work correctly:
05/11/09 20:14:47.050 Received Message from 45 ([36;1mOnScreen Orbiter / Soggiorno[0m) to 4 ([36;1mGeneral Info Plug-in / Sottotetto[0m), type 1 id 323 Command:[35;1mHalt Device[0m, retry none, parameters: <0x6aeccb90>
05/11/09 20:14:47.050 Parameter 2(PK_Device): 43 <0x6aeccb90>
05/11/09 20:14:47.050 Parameter 21(Force): <0x6aeccb90>
05/11/09 20:14:47.052 Received Message from 45 ([36;1mOnScreen Orbiter / Soggiorno[0m) to 44 ([36;1mApp Server / Soggiorno[0m), type 1 id 323 Command:[35;1mHalt Device[0m, retry none, parameters: <0xb1cfeb90>
05/11/09 20:14:47.052 Parameter 2(PK_Device): 43 <0xb1cfeb90>
05/11/09 20:14:47.052 Parameter 21(Force): <0xb1cfeb90>
05/11/09 20:14:47.052 Parameter 47(Mac address): <0xb1cfeb90>
I've also see that on the web interface that both the core and the md are checked like "Diskless Boot" is it correct or not?
I never checked this parameter and I think is from the initial installation / configuration. I hope.
How could be possibile to debug better this kind of issue.
I 've already verified the scripts for the wake and halt MDs. If I try to execute from mysql shell I receive the correct MAC address for the MD.
Any suggestion is welcome
Best regards
Luke
P.S. : at the moment I don't have the Web orbiter up and running for an alternative test, and also no windows orbiter.
-
Try switching the orbiter to the room you want to power down first, then select power> turn off MD. See if doing it in that order gives you different results.
-Krys
-
Hi krys,
the logs are related to first switch to power , than select the room and for last select halt MD.
I can try this other kind of process. First change the room, than select the power tab and finally click halt MD.
I'll do it when I arrived at home.
But, if I remember correctly, with 0710 I never had problems with the first process (power, room and halt md).
I'll send you the result after the tests.
Best regards
Luke
-
hi felpouse,
FYI,
I've tried it 2 ways.
On the Core I changed room to home theatre then advanced > power (home theatre was selected room) > power off m/d both shutdown.
On the Core with the room set as Office (default) advanced > power (selected home theatre as the room) > power off m/d both shutdown.
Cheers.
-
I had tried both the solution looking to the DCERouter.log . Both the tests result in sending the wake event to the id incorrect . Starting from first changing the room and than do power md and also from starting from power menu and than change the room ando finally send the wakeup event.
I used for an exaustive test also an orbiter (the 0710 release) on windows platform . If I make the same tests the wakeup event were sent to the correct id of the MD.
Now I had to investigate why the MD don't wakeup, but this is another problem (not related to this issue). I need to check if something in last week wont wrong on the MB of the MD, like BIOS settings.
I think that there is something on the linux orbiter (Core/Hybrid) that is not working well.
Best regards,
Luke
-
felpouse,
do you have any fancy settings for your MDs? Like no mac address or stuff like that in the device settings in web admin?
-
Hi Posde,
thanks for your question. The settings are completly standard and related to the automatic creation of MD during the first boot process.
In webadmin I have both ip and mac adresses completed and correct.
The only think that I don't know if it's correct in webadmin is : CORE has Diskless Boot flagged like the MD.
Is this correct or not? It is in this form from the beginning of the instalation.
Regards
Luke
-
Hi all,
here my screenshot about MD properties.
Regards
Luke
-
That looks good to me :/ - I wonder what is happening. I will have another install today, and see what's happening there.
-
Hi posde,
let me know when you have done.
Best regards
Luke
-
let me know when you have done.
Todays install went without a hitch. Installed Kubuntu on my Thinkpad T61p, ran the installer, moved a MD from an existing install onto the internal net of the Thinkpad, booted it, announced to router, rebooted
BLACK SCREEN
hmm. There was something with a black screen in the wiki ... ah, press 2 for DVI, and low and behold the AV Wizards page comes up - noob problem fixed :)
Went thru AV Wizard and Sarah, and have the Orbiter up and running. On the core, change room to the MD, press power, power off - MD goes down. GOOD. Press Power On - MD goes on. Good
/me is happy.
-
w000000t!!!!!
-
Hi posde,
I'm very happy for you but not for me. At the moment is still working only from an orbiter in windows ambient. Not from the core system.
It's possible that this week-end I'll restart from the beginning the complete reinstallation from the installer for the core , and will follow whats happen.
I'll send you my impressions at the end of the installation. This is very strange, because I'm able to use all the other features, like VDR (compiled from sources based on VDR packages for 0710) from the MDs both DVB-S and DVB-T, videos, music and so on.
Best regards
Luke
-
Good to hear, that the rest is working quite well. Would you mind explaining, why you compiled VDR yourself? It should automatically be installed from the kubuntu repository. I am using the one from the hanno.de repository, as it contains support for the vompserver plugin and the source caps patch.
-
Hi posde,
this is only an exercise for me. Would be a test in trying to create deb packages from sources.
-
Hi posde and all people,
I've finished the reinstallation from scratch. And now the problem persit. If I use the power menu from the CORE the MD will go down but also the core ???
I've checked the DCERouter.log and the message is sent to the id of the core and not to the md.
Where is possible to check also the GUI configuration managed from the mysql tables? I think it's not possible to be a mine mistacke. I've installed several times LinuxMCE also the releases before and never happen this.
If someone could give me some references where to investigate?
Best regards
-
felpouse,
please setup a web orbiter, and see what happens, if you shutdown your MD using the web orbiter.
-
posde,
thanks for your suggestion.
This evening I'll create a web orbiter and then I'll try to do all test for the power on and off.
I'll send you the result ASAP.
Regards
-
Hi posde,
now with a web orbiter I could shutdown my md. Actually the wol is not working but I think this is not related to linuxmce installation (mobo hw problem).
Could you please tell me, why the weborbiter is working as aspect and not the orbiter on the CORE ?
Did you think this only a moment bug or not ?
Regards
-
felpouse,
I have no idea.
Are you using UI1 or UI2 on your core?
-
Posde,
I'm using UI2 + Alpha Blending .
A possible test could be, I don't know exactly when, try to test it in UI2 w/o Alpha B. and also with UI1.
Regards
-
Try it with UI1 and see if that exhibits the same behavior. Ui2 alpha or masked really does not matter, as they both use the same internal mechanism.
-
I will try it ASAP , and send you a feedback about it.
-
Posde,
I've changed my mobo for the MD. And now, ladies and gentlemen, from the web orbiter I can power off and on and off and on ....... and so on my MD . :D :D :D :D
Greatfully. Now I'll need to investigate more on the problem from the CORE's orbiter . During the next days I'll start to check whats going on.
Regards.
P.S. : all the other features, like TV, audio, video are working really great. Good job guys for only an alpha version!!!