That's reassuring to hear Mark! How do you have the SB doing audio but still using the TV out of the 350? Are you just using the audio for the mplayer or whatever? The understanding I have of the 350 is that the audio output for using it's internal mpeg decoder has to be the built in, then of course you can pipe it back into a cards input if you wanted to vol adjust or use other audio output stuff. Is that what your doing?
As for other differences, well, you're on Fedora, and I'm on debian, but I'm not apposed to switching if it'll fix my issues.... What tuner type is your PVR-350? (It should show it when the ivtv module loads). I'm not talking about what tuner type you might be setting, but what the card actually is. Thanks for the good news, -Kenneth On Fri, 25 Feb 2005 13:17:20 -0500, Mark Schindel <[EMAIL PROTECTED]> wrote: > I'm running a PVR-350 using tvout on a slower machine and have yet to > have any hang problems at all. I started with 2.6.9-?.???_FC3 and am now > running 2.6.10-1.760_FC3. All required kmdls are from ATrpms as well as > current MythTV. > The machine is a P3 500 320MB using an old SB AWE64 for sound. > > Lots of record and playback activity (approx 200hrs) and the associated > skip, jump RW/FW activity. But probably only 10hrs of live tv although > this did include a fair bit of PVR function stuff. Still no hangs...... > > Is there anything I can help you guys with to diagnose your problems? > > Mark. > > ---- > > kernel-2.6.10-1.760_FC3 > ivtv-kmdl-2.6.10-1.760_FC3-0.3.2d-67.rhfc3.at > alsa-kmdl-2.6.10-1.760_FC3-1.0.8-36.rhfc3.at > video4linux-kmdl-2.6.10-1.760_FC3-20050113_172233-54.1.rhfc3.at > lirc-kmdl-2.6.10-1.760_FC3-0.7.0-43.1.rhfc3.at > > ivtv-0.3.2d-67.rhfc3.at > ivtv-firmware-1.8a-4.at > ivtv-firmware-dec-2.02.023-4.at > ivtv-firmware-enc-2.04.024-4.at > ivtvdev-0.8-1.rhfc3.at > mythtv-0.17-95.rhfc3.at > mythtv-frontend-0.17-95.rhfc3.at > mythtv-backend-0.17-95.rhfc3.at > mythtvsetup-0.17-95.rhfc3.at > libmyth-0.17-95.rhfc3.at > mythmusic-0.17-68.rhfc3.at > mythtv-themes-0.17-95.rhfc3.at > mythweb-0.17-64.at > mythweather-0.17-65.rhfc3.at > > ---- > > Maverick wrote: > > >In my experience, the 350 locks up when you do stuff with the > >framebuffer while watching TV or a recording, like FF and REW (how it > >pops up the OSD overlay thingy to tell you where you're at)... If > >you're in an SSH session, you can unlock the box with a simple enter > >at the cmd prompt. This is on slower machines (533-667 range). I have > >not tried on a newer/faster board yet, as I just got a little > >frustrated at my mythbox and figured I'd let my head cool before > >moving the hardware to a different box... In any case, I think ivtv > >and mythtv are stable, and we know Linux is reasonably stable, but > >there is a certain combination of either hardware (some VIA chipsets > >are known bad?) and software/drivers/etc that cause some flakiness > >using the PVR-350's output. > > > >I am super frustrated too, because I bought the 350 because of > >MythTV's specific support for it, and the lower CPU requirement. What > >I'm now finding out, is I still have to buy a faster system so it will > >work (without locking up). I didn't need the TV out nVidia features > >like games, etc, but it looks like that's where I'll be at to make > >things work. > > > >I don't have a VIA chipset, it's an Intel motherboard and a P3-667. > > > >I've tried every "current" version of IVTV, up until v0.3.2d. Haven't > >tried the new e release yet. It has some vsync timing stuff I'm > >interested in seeing if it fixes the problems I'm having... > > > >I upgraded my kernel to 2.6.10, since I have one of the "new" tuners, > >a Type 47. Thinking that would help, it only caused me lots of work > >converting the system to modprobe.conf..blahblahblah. Still same > >lockups. > > > >Compiled MythTV 0.17. For the hell of it, can't use the box, midas > >well try that to. No effect. > > > >I still have no working mythbox... not that I'm a whole lotta help, > >just offering up what I've tried thus far. > > > >I'd be willing to accept that it's my hardware, except that a friend > >on a completely different system with the same PVR-350 card as me > >(Tuner=47) has the SAME EXACT problem. > > > >We both blame ivtv's (mis)handling of dma, but are too ignorant to > >make that claim for real or even figure it out and fix it if it really > >is the case. > > > >I still haven't found someone with a low end (sub 1Ghz) machine and a > >PVR-350 Tuner =47, so sorta says to me it can't be done. I've found > >plenty of people experiencing the lockups with newer versions of ivtv > >though... > > > >One workaround that we've figured out is to put the X server output on > >a monitor, and just use MythTV's PVR-350 output support to watch > >TV/recordings. That stops the lockups completely. Makes you think it's > >the ivtv / X / framebuffer output, huh? Says to me, it's not hardware > >like the software guys would have you believe... :) > > > >-Kenneth > > > > > >------------------------------------------------------------------------ > > > >_______________________________________________ > >mythtv-users mailing list > >mythtv-users@mythtv.org > >http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users > > > > > _______________________________________________ > mythtv-users mailing list > mythtv-users@mythtv.org > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users >
_______________________________________________ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
