BTW - Did you double check on the C1 Disconnect issue? If not search the fourms for more details.

As the guy behind the NForce post you quote, thought I might share status a few months later.

My FC1 backend is running FLAWLESSLY, churning out hours and hours of quality video every month. The only trouble I've had, period, since changing the backend to FC1 is my own playing around with CK's IVTV drivers. (Thanks btw bud, appreciate all the work).

Finally settled on 100z, which are the absolute picture of stability. (Get em HERE: http://67.18.1.101/~ckennedy/ivtv/OLD_g ... ck100z.tgz)

Ahh, one more thing...

My frontend, also NForce2, which was Knopp, I redid one weekend to FC1, because my wife was complaining of so many frontend crashes. Bad enough I had SecureCRT on her laptop, and a "fixme" script....

Since I reformatted her machine to FC1, it's also been the picture of stability.

I haven't played with R4V5 yet, so I can't begin to comment on it, but I wouldn't run the kernel under KnoppR4V4 on any Nforce chipset. Something borked.

I would imagine that there are many around here that would dissagree with you. I know cesman runs at least one nforce2 chipset board, and several others do too. I do myself as well, however I cannot comment on the stability of R4V3 - R4V5 as I went from R4V2 to R5 alpha. And I did not have any stability issues with R3, R4V2, or for the most part R5 alpha (but it is alpha after all, and most of the issues are not stability problems.)

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

You can see my signature block for details, but I'm using an nForce2 chipset with KnoppMyth R4V5 (same kernel as R4V4.1). I recently turned off commercial flagging and earned a great deal of stability in return.

A trick with the ivtv drivers is that it's not simply the driver version you choose; the card firmware version can matter, too. It definitely seems to matter in my case, since I have a card with a tuner too new to be recognized by the 0.1.9* tree. (Type 39, recognized automatically by the 0.1.10* tree.) You can get the latest Hauppage firmware here: http://www.hauppage.com/pages/support_pvr250-350.html The PVR_INF file is what you'll want to run ivtvfwextract.pl on before recompiling ivtv.

One thing I do think may be a bad interaction with the the R4 kernels (2.4.25-chw) is that ogg encoding crashes 100% of the time, whether from the command-line or through MythMusic. By contrast, mp3 encoding works 100% of the time.

I'm waiting for R5 so I can test out a newer kernel with the same hardware.

_________________
KnoppMyth R5.5
MythiC Dragon v2.0
Join the KnoppMyth Frappr!

I have a Chaintech 7NIF2 in master backend. Since disabling APIC/local APIC in R4V3 (kernel), it has been rock solid, running 24 x 7 (practically 24 x 7, I do use it to test and update to newer releases).

_________________
cesman

When the source is open, the possibilities are endless!

Yeah, me too. I know of two or three ways to lock up the front end, most or all of which are fixed in MythTV post 0.16 CVS, but the OS is rock steady and the least of my worries on my Nforce2 based system running KnoppMyth R4V4 upgraded to the R4V5 0.16 debs.

Well since repairing all my mysql tables things have been running just fine. {sound of knocking on wood}. If the frontend goes south on me again I will drag a monitor out to it so I can get into the CMOS and check the C1-disconnect issue. I have had the case (antec aria) sealed up for several days now so I'm hopeful that it wasn't a temperature issue. I did monitor the temperature for a little while and never saw any problem.

Now comes the challenging part for the system - the family test. After I got IR working to the cable box I deposed our replaytv and so now the myth is getting more of a workout.

Thanks again for all the suggestions.

I appreciate peoples feedback about disabling commercial flagging, or ogg encoding, or a specific version of firmware needed. It's great to get something locally stable for YOU. Disabling commerical flagging for example, gimps what I think is one of the coolest features (and the most in demand by my family who uses this thing)

However, the fact, for me remains thus:

Same version of Myth, IVTV, firmware, hardware, etc, wasn't stable on (3) different motherboards with (3) different CPU's, and a myriad of other parts swapped in an attempt to get things stable, including multiple "format the machine" reinstalls. I cleaned & repaired tables, I started over, etc.

Reformatted to FC1, and it's flawless.

Again, I'm sure other people have found something "magic" to fix or repair or tune in their setup to get it happy. In my case it was removing Knopp from the mix, sadly.

Well I must admit that I turned off comm flag, but I had quit using it long before that, because it just plain sucked on most of the shows I watched anyways. I can't imagine that not computer geek family would request such a shoddy implementation, my girlfriend was nothing but pissed, because it would skip 3/4 of the show and we would have to try to back up to where we needed to be.

And that's fine and dandy if FC1 worked for you but don't come back here spreading FUD that Knoppmyth isn't stable and you need to switch to FC1. I've heard more than it's share of horror stories about FC1/2 as well.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

Damn! {Shaking fists at sky}

Front end locked up again. Nothing but a black screen.

Backend seems to still be running. I haven't reset it yet while I poke at it. Same usual messages in the logs, with lots of



One question, is it normal to have a lot of backend and frontend processes running? I am ssh'd into the box right now and I can see 12 pids associated with mythbackend and 6 mythfrontend's. I am assuming that is normal.

Looking at the cpu usage (top), nothing seems to be using the CPU.

I just killed the front end. Had to kill -9 and selected the first pid, which then took down all the rest. Then tried restarting it (from fvwm) which appeared to work until I tried watching TV, at which point it went back to black screen mode and froze up again.

I am also looking at mythbackend.log and see this every so often:



Does anybody know if that is normal or what to do about it?

I guess I'll wait until the backend is idle (recording jeopardy now) and then I'll reset it, check the cmos for the C1-disconnect, then turn off commercial flagging.

I thought I would try these settings which I read in another thread, with the following results:



Anybody have an comment on the powersave mode message? Also I forgot that I had already turned off commercial flagging a while back (wasn't working right anyway) so that isn't to blame for my frontend woes.

I tried putting the above setterm statments in /etc/init.d/bootmisc.sh but then my backend wouldn't start at all (but the frontend would). Any details on where to put those statements would be appreciated.