well, I didnt have any other symptoms aside form full disks....so I guess I'm happy

_________________
R5F1 - Dell P4 2.4Ghz 500MB - PVR250 x 2 - GeForce FX 5200 - Onboard sound/NIC 80GB ATA/250GB ATA/400GB SATA

Ah, yes... The classic "solution" of sticking your fingers in your ears and singing "La-la-la! I-can't-hear-you! La-la-la!" as loudly as possible. Sadly, sometimes it's the only choice...

exactly, if a tree in the woods falls onto my ivtv configs and doesnt fill my / partition, did it really fall

_________________
R5F1 - Dell P4 2.4Ghz 500MB - PVR250 x 2 - GeForce FX 5200 - Onboard sound/NIC 80GB ATA/250GB ATA/400GB SATA

Could one of you point me in the right direction?

I placed into /etc/init.d/bootmisc.sh.

Or should I add
to /etc/mythtv/modules/ivtv

As of right now, when I reboot my machine, it does not help the recorded video from slowing down or skipping portions (about 10 or 20 sec.) nor the filled logs issue.

This all started happening to me after I came home from vacation, recordings had filled my hard drive up. So I deleted a few shows and put my used capacity to about 61%. Ever since then my recorded shows are going into slow-motion or skipping parts of the recorded show. My live video is pretty much OK. Nothing has worked. I still have to clear my log files as they keep growing and growing.

I'm not sure what versio of ivtv I'm running, apt only shows be libvideo-ivtv-perl 0.13. I'm using R5A15.1.

Thanks for any help you can give me.

Should not be necessary to add the ivtvctl command to your bootmisc. Just run the command as root. Verify that it's sticking with "ivtvctl -X". It should say that VBI is off.

Second, I think you have the syntax wrong, should be "options ivtv ivtv_debug=0".

Jon

Thanks for the help GB but for some reason setting the VBI to off will not stick even when I run it as root. The log files seem to be under control now but recorded shows are slowing down in certain parts, skipping 10 or 20 seconds of the program and when I FF, I get a very pixelated image (I've never seen this before). The over all stability of Myth is much much worse. It's not usable.

I can't record any programming at the moment. I'm suprised that only a few users are seeing this. It's not something I can live with.

Queston: I'm using R5A15.1. Is there a more stable release I could use? It seems to me that there are quite a few happy users out there that aren't complaining so I assumed that they are running a more stable version.

My wife has just about had it. I need help!

Errrr...try upgrading your ivtv.

I'm using 0.3.3 something.

That may be the reason I'm able to disable the VBI.

Also, just for the heck of it try turning off closed captioning in setup.

Oh man; thanks for the quick response GB!

I'll give it a go. But not to sound like a complete idiot. I don't see ivtv in apt, do I need to compile and install ivtv from scratch. Also, how can I search for my version cumber?

The only app installed or that can be found using apt is libvideo-ivtv-perl.

Thanks again for the quick help.

http://www.ivtv.tv/

It's pretty easy install. Extract the archive and then 'make' and 'make install'. Do this for both the driver and util.

I don't know what version is best for you; you'll probably have to do some searching and googling depending your card.

Will do. Thanks again.

I'll reply with my results.

Well, I upgraded to 0.3.6o (you were right GB, it was a breeze). You were correct with the ivtvctl -x 0 setting. It finally showed that vbi was off but still no cigar. One problem is when I rebooted, vbi was back on. Should I add the debugging=o to the ivtv module?

I'm now getting ledxmit error. I had this one time before and it kept my irBlaster from working properly. It's my second instance of lirc. This just might be the last nail in the coffin for me. But hey, the ivtv overlow error is gone.

Instead of slow motion and skipping 10 to 20 seconds of video I get the 1 second freeze about every minute, including the audio.

I also disabled commercial flagging via the setup menu's.

There is a ivtv-0.3.7c version but I doubt the stability of that one.

I'll let it record tonight to see how recorded shows come out but I'd be willing to bet that the freezing of audio and video will be there as well.

Thanks for you help and quick response GB. I'm game for any more suggestions though.

Cheers,

Gummy,

If I were to install KNoppMyth from scratch, which version would be the most stable?

I was also seeing this error:

ivtv0 warning: ENC Stream 0 OVERFLOW

My Myth was working fine for several days until it froze during a program delete, had to reboot. After that, I saw the above error and could not watch the program being recorded without Myth dumping out to the menu (select recording to watch), hard drive thrashing like crazy.

I also found this error in the log:

Can't open file: 'recordedmarkup.MYI'

Found a thread about my database being corrupted and provided an easy way to repair, see here:

http://mythtv.org/pipermail/mythtv-user ... 20788.html

After repairing the database, the overflow problem has gone away...

KnoppMyth R5A31
Dell 4100 586 - 256 ram
Maxtor 200 PATA
PVR-250 / 5200 AGP

My system was very stable for about six months then took a dive one day. I could have just fixed it but I decided to do a full rebuild (it's just the geek in me - why fix something when you have an opportunity to rip it open and start from scratch?). Ever since then I've been plagued with the 'stealing a buffer' error. I've tried everything from disabling logging, messing with VBI, upgrading IVTV (not a small task for a newbie), swapping PCI slots, editing my BIOS, etc. I've tried a clean install of every single release that has been released in the last six months. All to no avail. In every case the system goes belly up within a day or two (if it installs at all). I was resigned that it must be something to do with the VIA chipset problem that has been noted in these forums. I fully recognize that this does not explain why/how the system was stable for six months but sometimes we just choose to ignore certain details because they ruin an otherwise perfectly good explaination.

That being the case I was trying to find a new MB or barebones box that would do the trick and would not force me to buy new CPU and memory as well (working on a pretty tight budget so far -- $0 and a whack of old gear from the basement).

However, a couple of weeks ago I may have discovered the problem. I was experimenting with a new release and found that I was getting CRC errors. However the disks were all reporting to be good (both via MD5 tests and the testcd switch). Hmmm... I ran 'memtest' at the Knoppmyth install screen and lo and behold - my system looked like an alzeimers patient at an SAT exam.

Located the bad stick of RAM, replaced, and all is well and good in the world again. Coming up on two weeks with no problems.

Hope this helps some of you.

Must have been the RAM because here I am four months later and all is well. As noted, the only thing that I did differently to resolve the problem was to replace a stick of RAM. Too easy.