Is there a dedicated process for TV in mythTV?
I would like to see in "top" if it's still running or not! I'm away from my box.
I just have ssh.

Hi zetoune,

Ok, I am misunderstanding some details here. Are you saying that if you boot up your KnoppMyth box and walk away, it crashes with in 24 hours?

Since you are just starting, may I suggest that you install cesman's latest release, don't upgrade, fresh install. (good for the practice too)
http://mysettopbox.tv/phpBB2/viewtopic. ... a77b03f148

I did an install this AM, set the cache 1gig less as I mentioned earlier, went through all the setup screens (except weather & news) and when I hit the ball 'Watch Tv' it was there. That is about as 'out of the box' as one can get.

To learn all there is about any linux command in KnoppMyth, just enter
" $ man command-you-want-to-know-about "
ie man df

1000 is 1k, 1024 = refered to as 1k, the 24 byte difference will bite you when it is not on the correct side of your equation.

Mike

It's a fresh install. No upgrade. I'm using last release (R5A22).
Just the frontend crashes. The backend is running with no problem.
Before setting cache 1 GB less than my cache partition, all the frontend crashed. (mythfrontend was not in "top" list process anymore). Now it's still here but watching TV has quit. (I'm trying to let watching TV run all the time).
I have to reboot to reenter watching TV.

That's it.
Maybe I could make the box reboot each night at 4.00 am (but I don't know how). It will fix my problem !

Hi zetoune,

Thanks for the clarification. The A22 is not the latest of cesman's, A26 is and it fixes some small issues also.

If you have the resources to download and start fresh, I would suggest that as you may have future upgrade problems with A22. Check his annoucements for details.

The frontend, by it's self should not stop as nothing is really being used for resources. Kill the frontend, exc / control esc however you do it (I prefer control esc) then do alt X to start a term, enter mythfrontend to restart. The term will log all that occurs and if the frontend stops, you can then read what it was trying to do just before the spirit went south.

You could have a defective cd that loaded a defective install which will give you all kinds of strange happenings. When everything is setup properly, the only reboot you should have to do is when there is a power failure. up 27 days, 7:27, that was my last power outage

Mike

I was too sure that A22 was the last release! Thank you for the tip.
I will download it. I'm using CDRW from staples for knoppmyth. Do you think I should go with more reliable CDRW?

Hi zetoune,

I would rather make a more lasting coaster so I only use plain cd's. I also burn it at the slowest speed as I like things "well done"

Just as a note of interest, I do everything (except print) on my analog version KnoppMyth box and it all works solid like a rock. Yes, including burning iso's (many thanks to cesman for the howto)

Mike

It's not terribly well documented how to use the testcd option to verify your CD image, but it's almost trivial. Simply add the word "testcd" to the end of your options when booting from the CD. It doesn't work all by itself so you need to say something like "tv testcd" or "expert testcd" or "knoppmyth tescd", but it does work.

Hi,
tjc is correct about that test feature. I didn't think to mention it for a couple of reasons.

1. I have found that cdrw's are often not readable in a different drive. So it could check good in the burn drive and may not in the install drive (assuming different machine) Maybe it is the color of the laser or something.

2. He indicated that he was going for the A26 so that would be the one of concern to be tested but if he does the slow burn on a cdr it should be a 99.99% chance of being good. I think I had one in a year that was bad and it had a scratch that I didn't notice. I haven't had any bad ones burning with KnoppMyth.

3. I had forgotten about that built-in feature to the iso

Mike

Since using testcd just adds a few minutes extra to an install or upgrade there's really no reason not to do it as a matter of course while you're doing that install. It's a heck of a lot smarter to spend a few extra minutes up front if it can keep you from spending hours troublshhoting a bad burn...

I haven't install R5A26 yet, but I've started frontend from xterm
and this is the log.

I've also attached the backend log.

Add the end of each log, I can see something about RingBuffer.
I've read somewhere it can be a ivtv driver problem or can be a problem of cache.

I hope R5A26 can fix this problem?

Hi zetoune,

It looks like the ol' ringbuffer permissions issue. Do an ls -al /cache and it should look something like this:
mythtv@KnoppMyth-20:~$ ls -al /cache
total 28
drwxr-xr-x 4 mythtv mythtv 4096 Nov 11 10:56 .
drwxr-xr-x 26 root root 4096 Nov 15 22:51 ..
drwxr-xr-x 2 mythtv mythtv 4096 Nov 22 00:40 cache
drwx------ 2 root root 16384 Nov 11 10:53 lost+found

mythtv needs to be able to write to that directory as it puts the ringbuffer in there.

I did not do any driver patches to anything. It all worked but I did have to adjust the cache size in the mythtv-setup as mentioned earlier to keep it running. That applies to both analog & digital.

Mike

Hi Mike,

This is the output for ls -al /cache



anyway, I can use myth for almost 2 days without crash. I think if it was a permission issue, it would crash instantly, wouldn't it?

I agree, but let me guess, does the problem occur when you're changing channels? That's the usual correlation with these problems (search here and in http://www.gossamer-threads.com/lists/mythtv/users/ for that ring_buffer error you were getting). It used to be somewhat common when your tuner couldn't get a good lock on the new channel, but was supposedly fixed in MythTV a couple revs back...

hi tjc,
Actually no, I don't think it happens when changing channels.
Because most of the time, it crashes when I'm sleeping.
I'm gonna take a look at the mailing list
thx.