After extensive testing with the acoustic management set to "fast" rather than quiet it does seem to make quite a difference

I started testing at about 2pm yesterday, with the uk childrens channel "cbeebies" - great for testing this a lot of the programs last only 15 mins each, so plenty of boundaries.


It went from 2pm till end of transmission at 6:30 without a hitch, so it was looking good.

I switched to another channel (e4+1) and let it run all night.

When I came back this morning the front end had crashed completely, not
"Error Was encountered while displaying video"

looking at the backend log i see



I dont have a frontend log for this so cant say if it was the same error but it is it seems to have happended very shortly *after* a program change (1 minute 22 seconds later) and the whole frontend crashed as opposed to the usual problem which happens within 10 seconds after the program change.... so it may have been a different issue. (my test setup is unfortunately not locate near a good aerial - so the signal from a set top aerial is "marginal" on some stations)


In conclusion then I think that changing the acoustic management of the disk does seem to have made a difference (you can set this paramater for most manufacturers using the tools on the ultimate boot cd http://www.ultimatebootcd.com/ - in this case its the original Samsung tool on the bood cd)

Im going to try some more testing today and if i still not getting the issue im gonna risk trying r5e50 again - im becoming a bit of an expert at installs - thats easily 10 ive done in the last 2 weeks !

Ok, like i said, i tried the r5e50 again tonight...
Not good news


even with acoustic management set at fast
The dreaded "Error Was encountered while displaying video"
was apparent within 15 minutes of the reinstall....

Ok, im running out of options a little but here are the possibilites

1) give up and await a new version of knoppmyth/myth - hoping this will sort it
2) go back to r5c7 and just lose out on the newest features
3) try installing on a different brand of hard disk (I have a 160Gb Maxtor which might be worth a try) - not convinced this would make any difference
4) procure new mobo and/or cpu - unwilling to do this unless i have a surety that the new gear would work 100% + I have no real evidence that what i have is faulty in any way...


Options 3 then 2 are the most likely and possibly I would do 1 before 4 - dunno tho.

I get that with Seagate drives, so I doubt changing your Maxtor would make any difference.
I turned the family loose on a R5C7 unit & it just sits there & runs... I never get any kickback about it.... Just fix the 'log rotation' problem or that'll sneak up & bite you in a couple months....

Let me offer this complete shot-in-the-dark...
All of you guys with this problem: do you all have hyperthreading CPUs, and does KM use a hyperthreading aware kernel? If you 'cat /proc/cpuinfo' do you see one or 2 CPUs?

razalasm,

Funnny you should mention that.


Looking back since you mentioned CPU's. I also changed from a 2.80 GHz Celeron, to the current P4 shortly after upgrading from R5C7 to R5D1 w/v.20 fixes.

S' what I get...

Yeah "siblings: 2" means a hyperthreading CPU. Why not disable it and see if it makes a difference (either disable it in your BIOS or boot with the "noht" option)?

Mine is a Willamette 1.7ghz P4 which does not support hyperthreading.

so I dont think thats the issue for me.
D

EDIT : For completeness mine is as follows

Here's my findings... However I've had this problem with 2 CPU's, AMD single and dual core.

razalasm,

How do I change it at boot time?
Where does the "noht" option get set?

Thanks

Well it's looking like hyperthreading is a wild goose, but if you want to give it a short chase just hold down CTRL as your system boots to make sure the LILO boot prompt come up, then enter "knoppix noht". I think that'll do it.

Will have to test out after work tonight.

My Processor is a P4 2.4c with HT and shows up as 2 cpu's.

_________________
DRM 'manages access' in the same way that jail 'manages freedom.'
_________________
Intel P4 2.6
Intel Desktop Board
2GB DDR400
nVidia 6600GT
Dvico HDTV+
Dvico Dual 4
200GB WD for Swap /boot & /
2x 500GB WD with LVM & XFS for /myth/tv

Just wanted to add a "me too", in case there are still thoughts that this is an isolated problem.

I've found the best way to keep the wife happy is remind her about the Motorola 6412's shortcomings (bad UI, small disk, 2 tuners, etc). Of course 900 GB of storage and 4 tuners keeps plenty of good programming available on the backend. I tell her, there's no real reason to watch LiveTV anymore, but...

She still puts on LiveTV every morning and inevitably ends up with the blue screen+error. So she clicks the remote and turns LiveTV back on. At this point, she's seen it enough that it is no longer a "big deal"...

Still, a fix will definitely get me a couple of brownie points

Chris

Hmm, wish my wife was so tolerant - I'm stuck on r5a16 till i get a reliable workaround.

Anyone try upgrading to latest SVN?

I was having the same problem on QAM channels using my HDhomerun tuner when I 1st got it and that was the fix. The HDhomerun wasn't around before MythtTV .20 so I never seen on previous versions. I don't recall if the SVN fix was specific to the HDhomerun or all QAM tuners.

Some other things, try looking at the "bad recordings" with another media player over the network such as VLC and see if they are playable?