[09:46] hi all [10:50] hi all [12:38] hi all [12:43] I have problem with mythwelcome, when I leave mythfrontend does the count down but don't execute the script (that are executable and tested from bash) [12:44] I don't know what goes wrong, I cecked all the configuration menu (mythwelcome setup, general setup into mythfrontend and mythtv-setup) and they seem correct [12:44] there is a way to know what stop mythwelcome? [15:34] hi all [15:34] I have problem with mythwelcome, when I leave mythfrontend does the count down but don't execute the script (that are executable and tested from bash) [15:38] launching mythbackend -v idle,system seems that mythtv repeat many times mythshutdown --check [15:39] hi gedakc [15:43] hi #gedakc [15:47] spoky99: Hi. :-) [15:47] I'm still there :D [15:47] Did you get it working? [15:47] don't work -_- [15:47] launching mythbackend -v idle,system seems that mythtv repeat many times mythshutdown --check [15:48] Did you try using all the steps I had in the tutorial I wrote? [15:48] yesss [15:49] Does MythTV work for everything else (recording, watching shows, etc)? 'Just not for auto shutdown and wakeup? [15:49] yes [15:50] the other computer work :) [15:50] And just to confirm, was the test of RTC wakeup on your motherboard successful? [15:52] Hmm... so your other computer works.... [15:52] the old-new mediacenter make from mythbuntu 14.04 don't work properly, during shutdown frozed [15:53] war 1 or 2 month that was on witouth shutdown [15:53] Could you describe "frozed"? [15:53] I put shutdown -P [15:53] and now shutdown [15:54] Does it shutdown properly now? [15:55] I really don't know why froze, start go down service and suddenly he stopped, without write someting in the log file [15:55] now It work [15:56] (the next step was connect a serial cable and start telnet connection for to see what goes wrong) [15:56] Do you recall making a change that caused shutdown to start working? [15:57] shutdown -P [15:57] Okay. If I recall correctly some systems did need that. [15:57] sometime they shutdown well before this change, sometime froze [15:58] I read it [15:58] I'm not luky :) [15:59] sometime don't wakeup, I don't know if is a motherboard problem or a system problem, and I'm trying to replace motherboard and filesysem [15:59] filesystem [15:59] In the MythBackend setup, have you disabled "block shutdown before client connected"? [16:00] but I don't want use mythbuntu [16:00] yesss! I disable it, is uncecked [16:00] Oh, sorry, my mistake. I assumed you were using mythbuntu. What distro are you using? [16:01] ubuntu with mate desktopmanager [16:01] I haven't used that setup. [16:01] 14.04 [16:02] Only kubuntu, ubuntu, lubuntu, and xubuntu. [16:02] in theory it should not change anything [16:02] mate use ligtdm like xubuntu [16:02] 'Agreed, although there are differences that might impact the setup. [16:03] and sometime gnome [16:03] From my past experience, intermittent problems are often caused by faulty hardware. [16:03] maybe [16:03] If the problem is consistent (repeatable), then I've often found it to be with software. [16:04] Since you have one computer working, that implies that you have correctly set up MythTV at least once. [16:04] You might try comparing settings between the systems to see if there are any key differences. [16:04] I'm not shure with the old computer, but new motherboard work well, the tvcard work well, harddisk is ok [16:04] Is exactly the same [16:05] If it's exactly the same, you might try making an image backup of both computers. Then restore the image from the working computer onto the non-working computer to see if that fixes the problem. [16:06] I compare the screen of the setup, checking each caracter and spooky space [16:07] That would be the first thing I would try. However, comparing screens is a manual process and something might be missed. [16:07] there is not difference, I check mythfrontend general, mytwelcome --setup and mytwelocme -i and mythtv-setup [16:07] I know [16:07] The problem might be in a script or some other area too. [16:08] Since it is the same hardware, it should work with exactly the same settings. [16:08] Is the firmware the same version on the motherboards? [16:08] yesterday the old mediacenter don't shutdown because I leave a strange caracter in the path (insert for don't shutdown the computer for the problem ahead) [16:09] are two different motherboard [16:09] is not the same hardware [16:10] is not new hardware, but it work [16:10] launching the script from bash... work [16:10] I guess when you said "exactly the same", you meant the MythTV setup, not the hardware. [16:11] mytwelcome enters loop and does not exceed the check [16:11] yess the configuration is the same [16:11] same script [16:11] same path [16:11] no [16:11] So mythwelcome is in a loop (does not shutdown)? [16:12] is not true, now in the new there is your setting [16:12] yess [16:12] Mythwelcome runs a script to check if it is okay to shutdown before it invokes the shutdown. [16:12] launching from bash mythbackend -v idle,system seems that mythtv repeat many times mythshutdown --check [16:12] yes I know [16:13] I read someting about put env into sudoers file [16:13] So then there is something causing mythshutdown --check to report that "It is not okay to shutdown". [16:13] I son't know, I suppose [16:14] You can check from the command line by running "mythshutdown --check" and then immediately looking at the return code. [16:14] Use "echo $?" to get the return code of the last executed command. [16:15] ahaha [16:15] they return [16:15] OK to shutdown [16:16] By OK do you mean it returns zero "0" or a non-zero value? [16:16] no return exactly "OK to shutdown" [16:17] and mythbackend repeat [16:17] Hmm... [16:18] I managed child (pid 292020) has started! command=/usr/bin/mythshutdown --check, timeout=0 [16:18] If it is "OK to shutdown", then mythtv is supposed to run the "command to set wakeup time". [16:18] I managed child (pid 292020) has started! command=/usr/bin/mythshutdown --check, status=32512, result=127 [16:19] result=127? I thought the return code had to be zero to shutdown... [16:21] I cat /proc/driver/rtc and... the wakeup time is the same of the next record [16:21] Okay. I assume same time of upcoming recording minus a few minutes to allow the system to start up. [16:21] return could be 0 and not 127? [16:22] It is possible that "result" is not equal to "return code". [16:22] It would seem that the time is being set in the RTC for the next recording. [16:23] So.... that means that there might be a problem with the actual shutdown command. [16:23] yes, seem thath setwakeup $time is execute [16:23] What do you have "Server halt command" set to? [16:23] Mine is: [16:23] sudo sh -c "mythshutdown --shutdown" [16:25] I'm rebooting [16:25] I copy the shutdown comand into a terminal and it work [16:26] mythwelcome comand [16:26] now, when reboot I restart mythtv-setup and copy the mythshutdown path into a terminal [16:27] Okay. It should shutdown then. [16:28] Did it reboot by itself, or did you power it on? [16:29] Mine used to go into a reboot loop. To stop it I had to set "Command to reboot" to "/sbin/poweroff". [16:30] I look some strange thing [16:31] copy the command directly into the bash there is a return from mythshutdown and -- [16:34] I understand the problem, launch sudo -sh -c "/usr/bin/mythshutdown --shutdown" from bash ask me password [16:34] I could insert sh into sudoers [16:35] Yes, that is needed. [16:35] /sbin/shutdown, /bin/sh, /usr/bin/setwakeup.sh, /usr/bin/mythshutdown, /sbin/poweroff, /sbin/reboot [16:36] now from bash it work! :) [16:36] was ok for the other command I don't insert /bin/sh [16:37] I think you might have solved the problem. :-) [16:38] I'm ceck it! [16:38] thank's [16:38] You're welcome. [16:38] :D [16:38] work it!!!! [16:39] Congratulations! [16:39] It was giving birth! [16:39] ahahahaha [16:40] I owe you one [16:40] I hope you enjoy your working PVR. :-) [16:40] ahaha [16:41] I use mythtv for 12 year, the old old hardware it worked with nvram-wakeup -_- [16:42] and worked fine for a long time, acpi is not the same :P [16:42] Yes, it is a challenge to keep up with changing hardware. [16:42] I've only been using MythTV since 2011. I built 3 PVRs the exact same for family and a friend. [16:44] And regarding "you owe me one", just pass the favour along to the next person needing help. :-) [16:46] I did and I will continue to do so [16:46] Cool. You don't owe me anything. 'Glad to help. [16:47] nothing is due [16:47] :-) [16:49] I remember two guys, one help me many times the other tell me 10 years ago that the analogic audio output was outdated [16:50] and my audio problem was not a problem :) [16:51] There is a lot of trial and error involved with helping others. [16:51] The same goes for diagnosing and fixing problems by yourself. ;-) [16:52] Anyways, I'm off for now. Have a great day spoky99! [16:54] now I could invent a way to decrease the temperature into the mobo without noise, with summer don't work well [16:54] thanks [16:54] and bye!