Here's my half-assed solution to this problem. Using these scripts to
launch X and the mythfrontend, this hung condition can be detected and
the mythfrontend killed and restarted. Not pretty, but better than
having to do a reboot. In my limited testing so far, it has been
working pretty well. I did experience one "hard" lockup, where it
didn't work, but I couldn't even ssh into the atv in that instance.
I'm more or less a noob when it comes to Linux and bash scripts and
welcome ideas on how to improve these (or better yet, ideas to address
the REAL problem).
/etc/rc.local
---------------
#!/bin/sh -e
su - mythtv -c xinit
exit 0
~mythtv/.xinitrc
--------------------
xset -dpms
xset s off
nvidia-settings -a GPUOverclockingState=1 > nvidia.log
nvidia-settings -a GPU2DClockFreqs=200,720 >> nvidia.log
./startmythfrontend > mythfrontend.log &
xterm
~mythtv/startmythfrontend
-----------------------------------
#!/bin/bash
mythfrontend | ./checkifhung > mythfrontend.log &
sleep 10
ps -ef | grep "/usr/bin/mythfrontend.real" > /tmp/mythfrontend.txt
exec 3<> /tmp/mythfrontend.txt
read ID PID REST <&3
echo $PID > /tmp/mythfrontend.pid
~mythtv/checkifhung
----------------------------
#!/bin/bash
while read line
do
echo $line
echo $line | grep "Warning: Waited too long for decoder to pause" > /
dev/null
if [ $? -ne 1 ]
then
echo "mythfrontend is likely hung. Restarting..."
exec 3<> /tmp/mythfrontend.pid
read pid <&3
kill $pid
./startmythfrontend &
exit
fi
done
On Oct 2, 1:38 pm, Bruce E <bhelm...@gmail.com> wrote:
> I've tried a few more things to analyze this problem. Interestingly,
> when I try to play this recording using mplayer with the command:
>
> mplayer -vo xv 1691_201000926203000.mpg
>
> It plays more or less OK. I can skip backward and forward without
> mplayer locking up (note that it played OK in MythTV as well, until I
> started skipping around). It did have some audio sync problems after
> skipping.
>
> I tried using xv-blit as the decoder in Myth instead of xvmc-blit, but
> it had the same problems (locked up after skipping around). This gives
> me the impression that I'm looking at a bug in MythTV. What does this
> mean to you?
>
> Bruce
>
> On Oct 2, 11:08 am, Bruce E <bhelm...@gmail.com> wrote:
>
> > Yes. In my .xinitrc, I'm doing the following:
>
> > xset -dpms
> > xset s off
> > nvidia-settings -a GPUOverclockingState=1 > nvidia.log
> > nvidia-settings -a GPU2DClockFreqs=200,720 >> nvidia.log
>
> > I've tried even lowering the upper frequency value down to 450 because
> > I had seen another poster using that value, but to no avail. Here's my
> > output from nvclock -i:
>
> > -- General info --
> > Card: nVidia Geforce Go 7300
> > Architecture: NV46/G72 A3
> > PCI id: 0x1d7
> > GPU clock: 200.000 MHz
> > Bustype: PCI-Express
>
> > -- Pipeline info --
> > Pixel units: 2x2 (11b)
> > Vertex units: 3x1 (111b)
> > HW masked units: None
> > SW masked units: None
>
> > -- Memory info --
> > Amount: 64 MB
> > Type: 128 bit DDR3
> > Clock: 729.000 MHz
>
> > -- PCI-Express info --
> > Current Rate: 2X
> > Maximum rate: 16X
>
> > -- Sensor info --
> > Sensor: GPU Internal Sensor
> > GPU temperature: 55C
>
> > -- VideoBios information --
> > Version: 05.72.22.68.00
> > Signon message: GeForce Go 7300 VGA BIOS (Apple M63)
> > Performance level 0: gpu 360MHz/memory 720MHz/100%
>
> > Thanks for the suggestion!
>
> > Bruce
>
> > On Oct 2, 12:27 am, "Scott D. Davilla" <davi...@4pi.com> wrote:
>
> > > >I haven't been feeling much love on this forum as of late, but I'm
> > > >desperate for some help on this one. It's really killing the
> > > >experience for me. I feel like I'm so close to nirvana, its driving me
> > > >nuts!
>
> > > You did underclock the nvidia GPU? This is critical for getting
> > > reliable XVMC playback.
>
>
--
To post to this group, send email to atv-bootloader@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/atv-bootloader?hl=en
