Re: [mythtv-users] is my processor to blame? (lockups, problems with FF and REW)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Maverick wrote: Everyone else seems to only have this problem using PVR-350 TVout. I'm using a 350 for tv out. For me the problem was the 2.6.10 kernel. I went back to the 2.6.8.1 kernel. With the 2.6.10 kernel, when I do a lot of jumping and skipping while watching my recordings, it's guaranteed to lock up ivtv with a failed api call. I don't get lockups at all with the 2.6.8.1 kernel. I haven't had a chance to try the 2.6.9 kernel to see if it has the same problem. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) iD8DBQFCO7+r91+pr0EM9zgRAjx2AJ45OaLyaTsqfrHQyCuGmMY37FzVNgCgmQ7y mHownmzI2eINQQI2I9jDCXE= =oh2N -END PGP SIGNATURE- ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] is my processor to blame? (lockups, problems with FF and REW)
Maverick wrote: Everyone else seems to only have this problem using PVR-350 TVout. I'm using a 350 for tv out. For me the problem was the 2.6.10 kernel. I went back to the 2.6.8.1 kernel. With the 2.6.10 kernel, when I do a lot of jumping and skipping while watching my recordings, it's guaranteed to lock up ivtv with a failed api call. I don't get lockups at all with the 2.6.8.1 kernel. I haven't had a chance to try the 2.6.9 kernel to see if it has the same problem. In my case, 2.4.25? and 2.6.10 both locked up, but i wasn't getting any error logs or anything... It would just freeze. Could be that the api ivtv is looking for in the kernel is changed in 2.6.10. My current stable box is a KnoppMyth R5A12 (kernel 2.6.9) and ivtv 0.2.0 (rc3h). Works great, though it's all new hardware from my lockup machine, which I'm sure would still lock up today even though it's not a VIA chipset. -Kenneth ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] is my processor to blame? (lockups, problems with FF and REW)
On Wed, 2 Mar 2005 22:40:49 -0500, Aaron Aguilar [EMAIL PROTECTED] wrote: If you can move the sound card to another IRQ in your BIOS setup and see if that solves your problem. Heck, share it with some other device instead of your PVR-250. If it fixes the ff/rew lockups, please let me know! :) Well I moved my PVR 250 so it doesn't share an IRQ with anything else. That didn't fix the problem unfortunately. I'm still having the freezing issue on FF and REW. Also my system seems to be crashing more frequently for some strange reason. I am thinking maybe it's FC3, but am hesitant to reinstall yet again lol. Anyways, any more ideas and I'd appreciate the input :) Cheers, Aaron This helped me with stability problems on my Pundit (SiS version) and PVR250+PVR350 backend+frontend system, installed using Jarod's guide: Add to kernel= line in grub.conf: parport=0 noapic nolapic acpi=off Also, I turned off USB, serial ports and parallel ports in the BIOS, as well as anything related to power management. Seems to be working so far; my mythfrontend hasn't locked up when using ff/rew since I added that, but it may just be me being careful when pushing the buttons on my remote. :) / Niklas ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
RE: [mythtv-users] is my processor to blame? (lockups, problems with FF and REW)
First off thanks so much to this list and to Jared for helping me set up a working mythtv box. My setup: AMD Duron 650Mhz 384mb RAM Samsung 160GB HDD FX5200 Hauppauge PVR250 FC3 2.6.10kernel This may not be what you wanted to hear but I was having loads of problems keeping my system running under FC3. Devices would just disappear. Lockups and other problems like ff/rew would crash my frontend. Also could not get my other services like dovecot and fetchmail to work reliably. I ended up wiping and reinstalling FC2. Since then the only problem I am having is that lircd does not want to start from sysinit. That was easily fixed by an entry in rc.local to reprobe and start lirc before starting the backend. Since that fix it has run for about a week without problems. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] is my processor to blame? (lockups, problems with FF and REW)
If you can move the sound card to another IRQ in your BIOS setup and see if that solves your problem. Heck, share it with some other device instead of your PVR-250. If it fixes the ff/rew lockups, please let me know! :) Well I moved my PVR 250 so it doesn't share an IRQ with anything else. That didn't fix the problem unfortunately. I'm still having the freezing issue on FF and REW. Also my system seems to be crashing more frequently for some strange reason. I am thinking maybe it's FC3, but am hesitant to reinstall yet again lol. Anyways, any more ideas and I'd appreciate the input :) Cheers, Aaron ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] is my processor to blame? (lockups, problems with FF and REW)
Thom, I have a similar setup to yours - 80+300gb LVM filesystem, stable with one tuner, backend locks up/crashes daily since adding a second tuner. How do you determine if bad IRQ's are the problem and how does one go about researching/fixing this type of thing? thanks, Russell Date: Mon, 28 Feb 2005 22:47:26 -0500 From: Thom Paine [EMAIL PROTECTED] Subject: Re: [mythtv-users] is my processor to blame? (lockups, problems with FF and REW) To: Discussion about mythtv mythtv-users@mythtv.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=US-ASCII Mine seemed stable before I upgraded to dual tuners. But I didn't have much of a chance to test it as I didn't get many shows recorded before I got excited and added more cards. I also added a 200G hard drive, and it's LVM, so granted I made alot of changes at once, but I can see mine be due to IRQ's. -- -=/Thom ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] is my processor to blame? (lockups, problems with FF and REW)
I have a similar setup to yours - 80+300gb LVM filesystem, stable with one tuner, backend locks up/crashes daily since adding a second tuner. How do you determine if bad IRQ's are the problem and how does one go about researching/fixing this type of thing? lspci -v will list all your devices, and then you can view which IRQ's they are on and compare with the other devices in the system to see what's sharing. Also, ivtv's driver init section displays the device id's of devices sharing IRQ's with a card supported by ivtv. Again, I'm not 100% sure it's IRQ conflicts ivtv causing the lockups, but everything points to that in my testing. Unfortunately, the system I have which habitually locks up will not allow me to rearrange the IRQ's. It forces both the onboard video card and the PVR-350 to the same IRQ, even if I try and change it. I need to test on my system that works and deliberately cause IRQ conflicts to see if it in fact locks up. We do know that the machine isn't really as hard locked as it seems, ivtv is just stuck in a deadlock sort of state. Ping flooding or hitting enter at an SSH prompt often brings the box back to temporary life. -Kenneth ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] is my processor to blame? (lockups, problems with FF and REW)
Sound IRQ3 Nic IRQ4 PVR-350 IRQ5 PVR-250 IRQ 10 Nexus IRQ 11 Video IRQ 9 USB IRQ 12 That theoretically gives me a nice split. If I can pile up the unused stuff like the USB and what not on 12, I'll leave the video card on 9 (which cascades down to 2) I should have my tuners and the good IRQ's. Sounds good. I'm anxious to hear your results. I'm surprised your BIOS is that flexible. My lockup machine has pathetic IRQ configuration options! :( -Kenneth ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] is my processor to blame? (lockups, problems with FF and REW)
Wow, the complaints keep coming on this issue... This is probably better suited for discussion on the ivtv-devel list though... Not that they any more helpful. :( You're the first person I've heard about this happening while using an nvidia card for output. Everyone else seems to only have this problem using PVR-350 TVout. Strange. In my opinion, it's a problem with IRQ sharing and the newer ivtv drivers that support newer tuners/cards. Unfortunately, no developer has had the problem happen to them, so it's unfixed for now. Changing your hardware (or BIOS irq assignment options if possible?) seems to be the only workaround... Do me a favour and lspci -v and paste the results, I'm curious to see if your PVR card is sharing an IRQ with your video card. I have yet to confirm if it really is the IRQ sharing, because it works on a machine that allows me to assign IRQ's, and it locks up on one that doesn't (and thus shares). -Kenneth On Mon, 28 Feb 2005 10:17:15 -0500, Aaron Aguilar [EMAIL PROTECTED] wrote: First off thanks so much to this list and to Jared for helping me set up a working mythtv box. My setup: AMD Duron 650Mhz 384mb RAM Samsung 160GB HDD FX5200 Hauppauge PVR250 FC3 2.6.10kernel My system works quite well recording shows, and even watching live tv if I don't do too many things. (changing channels, pulling up the guide, changing settings) However, once I start navigating through mythtv, sometimes my system will lockup and the only thing I can do is restart. I am thinking this happens because my processor can't keep up with the demands I am putting on it? So any opinions on this maybe from someone using a low end machine like mine? I don't want to upgrade my mobo/proc unless I have to. Also when fast forwarding or rewinding through a recorded show it will work just fine for about 10 seconds then the picture just freezes. I have to hit FF, REW, or play to get the picture to unfreeze. I don't know if this is hardware related or maybe I have some settings messed up on mythfrontend? Thanks so much for any help, Aaron ___ 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
Re: [mythtv-users] is my processor to blame? (lockups, problems with FF and REW)
Aaron Aguilar wrote: First off thanks so much to this list and to Jared for helping me set up a working mythtv box. My setup: AMD Duron 650Mhz 384mb RAM Samsung 160GB HDD FX5200 Hauppauge PVR250 FC3 2.6.10kernel Ugh. It could be so many things. Are you running a VIA chipset ? Have you checked the Capacitors on your board lately and are they leaking (Brown Goo) ? Do you have a decent power supply ? Have you checked the RAM lately with Memtest86 ? So many ways your system could be borked. It's possible you are triggering some weird race condition in myth due to a low-end cpu, but apparently people have run myth on PIIs so I doubt it. That's a fairly slow piece of gear these days. $99 bucks gets you a Sempron 2200 with motherboard if you shop around. I have myth running on a P3 933 quite well as a front end. Last time I had problems with the IVTV and a system it was because I had bad capacitors. Pulled it all and replaced it with a nforce2/sempron. Since then I fixed the bad caps on the old board and it runs reliably as a windows box. Haven't tested mythtv on it again. Good luck, Yan ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] is my processor to blame? (lockups, problems with FF and REW)
I run mythbackend on FC3 with a 1 GHz P3 and a pinnacle capture card, and the system is generally unstable. I generally run my front end on a 400 Mhz PII running KnoppMyth, and that system is more stable. I know this isn't terribly helpful, but I often run other apps (mostly firefox and bittorrent) while mythbackend is running, and I get a lot of system crashes. What I'm trying to say is, I don't believe FC3 is a terribly stable OS. On Mon, 28 Feb 2005 16:29:27 -0800, Yan-Fa Li [EMAIL PROTECTED] wrote: Aaron Aguilar wrote: First off thanks so much to this list and to Jared for helping me set up a working mythtv box. My setup: AMD Duron 650Mhz 384mb RAM Samsung 160GB HDD FX5200 Hauppauge PVR250 FC3 2.6.10kernel Ugh. It could be so many things. Are you running a VIA chipset ? Have you checked the Capacitors on your board lately and are they leaking (Brown Goo) ? Do you have a decent power supply ? Have you checked the RAM lately with Memtest86 ? So many ways your system could be borked. It's possible you are triggering some weird race condition in myth due to a low-end cpu, but apparently people have run myth on PIIs so I doubt it. That's a fairly slow piece of gear these days. $99 bucks gets you a Sempron 2200 with motherboard if you shop around. I have myth running on a P3 933 quite well as a front end. Last time I had problems with the IVTV and a system it was because I had bad capacitors. Pulled it all and replaced it with a nforce2/sempron. Since then I fixed the bad caps on the old board and it runs reliably as a windows box. Haven't tested mythtv on it again. Good luck, Yan ___ 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
Re: [mythtv-users] is my processor to blame? (lockups, problems with FF and REW)
On Mon, 28 Feb 2005 21:08:20 -0500, Chris Ribe [EMAIL PROTECTED] wrote: I run mythbackend on FC3 with a 1 GHz P3 and a pinnacle capture card, and the system is generally unstable. I generally run my front end on a 400 Mhz PII running KnoppMyth, and that system is more stable. I know this isn't terribly helpful, but I often run other apps (mostly firefox and bittorrent) while mythbackend is running, and I get a lot of system crashes. = What I'm trying to say is, I don't believe FC3 is a terribly stable OS. = I'd have to disagree there. My FC3 system is quite stable (though I'm wrestling w/ some issues, but none are related to FC3 or cause crashes).Aaron, what codec are you using (it would be in your recording profile under the LiveTV profile. MPEG-PS, DVD-SPECIAL2, another one? Have you tried changing those around to see if there's any difference in behavior? On Mon, 28 Feb 2005 16:29:27 -0800, Yan-Fa Li [EMAIL PROTECTED] wrote: Aaron Aguilar wrote: First off thanks so much to this list and to Jared for helping me set up a working mythtv box. My setup: AMD Duron 650Mhz 384mb RAM Samsung 160GB HDD FX5200 Hauppauge PVR250 FC3 2.6.10kernel Ugh. It could be so many things. Are you running a VIA chipset ? Have you checked the Capacitors on your board lately and are they leaking (Brown Goo) ? Do you have a decent power supply ? Have you checked the RAM lately with Memtest86 ? So many ways your system could be borked. It's possible you are triggering some weird race condition in myth due to a low-end cpu, but apparently people have run myth on PIIs so I doubt it. That's a fairly slow piece of gear these days. $99 bucks gets you a Sempron 2200 with motherboard if you shop around. I have myth running on a P3 933 quite well as a front end. Last time I had problems with the IVTV and a system it was because I had bad capacitors. Pulled it all and replaced it with a nforce2/sempron. Since then I fixed the bad caps on the old board and it runs reliably as a windows box. Haven't tested mythtv on it again. Good luck, Yan ___ 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
Re: [mythtv-users] is my processor to blame? (lockups, problems with FF and REW)
Chris Ribe wrote: I run mythbackend on FC3 with a 1 GHz P3 and a pinnacle capture card, and the system is generally unstable. I generally run my front end on a 400 Mhz PII running KnoppMyth, and that system is more stable. I know this isn't terribly helpful, but I often run other apps (mostly firefox and bittorrent) while mythbackend is running, and I get a lot of system crashes. What I'm trying to say is, I don't believe FC3 is a terribly stable OS. Semi agree, unless you run atrpms, in which case I would disagree. All the FC3 systems I'm running have been marvelous. One issue is the lack of support for multilib systems in apt-get, so AMD64 doesn't get no lovin if you're running mixed mode code. Yan ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] is my processor to blame? (lockups, problems with FF and REW)
Do me a favour and lspci -v and paste the results, I'm curious to see if your PVR card is sharing an IRQ with your video card. I have yet to confirm if it really is the IRQ sharing, because it works on a machine that allows me to assign IRQ's, and it locks up on one that doesn't (and thus shares). Sorry for this long post but here is a lspci -v copied and pasted. This also answers if I am running a VIA chipset. (Yes.) There is no visible brown goo, although there is quite a lot of dust in there I should probably clean off. I have a pretty new 300W power supply so I don't think that's an issue. I have not ran a memtest lately on the ram although I guess I could try it. Andy I will check on the different codecs after I send this email, don't want to crash before I get this sent. Aaron 00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev 02) Flags: bus master, medium devsel, latency 0 Memory at e000 (32-bit, prefetchable) [size=64M] Capabilities: [a0] AGP version 2.0 Capabilities: [c0] Power Management version 2 00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] (prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, medium devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: e800-e9ff Prefetchable memory behind bridge: d000-dfff 00:04.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 0a) Subsystem: Creative Labs SBLive! 5.1 Digital Model SB0220 Flags: bus master, medium devsel, latency 32, IRQ 3 I/O ports at c000 [size=32] Capabilities: [dc] Power Management version 1 00:04.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 0a) Subsystem: Creative Labs Gameport Joystick Flags: bus master, medium devsel, latency 32 I/O ports at c400 [size=8] Capabilities: [dc] Power Management version 1 00:05.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416)MPEG-2 Encoder (rev 01) Subsystem: Hauppauge computer works Inc. WinTV PVR 250 Flags: bus master, medium devsel, latency 64, IRQ 5 Memory at e400 (32-bit, prefetchable) [size=64M] Capabilities: [44] Power Management version 2 00:06.0 Ethernet controller: Linksys NC100 Network Everywhere Fast Ethernet 10/100 (rev 11) Subsystem: Linksys: Unknown device 0574 Flags: bus master, medium devsel, latency 32, IRQ 11 I/O ports at c800 [size=256] Memory at eb00 (32-bit, non-prefetchable) [size=1K] Capabilities: [c0] Power Management version 2 00:07.0 Communication controller: Ambient Technologies Inc HaM controllerless modem (rev 02) Subsystem: Askey Computer Corp.: Unknown device 1033 Flags: medium devsel, IRQ 10 Memory at eb001000 (32-bit, non-prefetchable) [size=4K] I/O ports at cc00 [size=256] Capabilities: [60] Power Management version 2 00:14.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22) Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA Bridge Flags: bus master, stepping, medium devsel, latency 0 00:14.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 10) (prog-if 8a [Master SecP PriP]) Flags: bus master, medium devsel, latency 32 I/O ports at d000 [size=16] Capabilities: [c0] Power Management version 2 00:14.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 10) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller Flags: bus master, medium devsel, latency 32, IRQ 11 I/O ports at d400 [size=32] Capabilities: [80] Power Management version 2 00:14.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 10) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller Flags: bus master, medium devsel, latency 32, IRQ 11 I/O ports at d800 [size=32] Capabilities: [80] Power Management version 2 00:14.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30) Flags: medium devsel, IRQ 9 Capabilities: [68] Power Management version 2 00:14.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 AudioController (rev 20) Subsystem: FIRST INTERNATIONAL Computer Inc: Unknown device 8905 Flags: medium devsel, IRQ 5 I/O ports at dc00 [size=256] I/O ports at e000 [size=4] I/O ports at e400 [size=4] Capabilities: [c0] Power Management version 2 01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1) (prog-if 00 [VGA]) Flags: bus master, 66Mhz, medium devsel, latency 248, IRQ 10 Memory at e800 (32-bit, non-prefetchable)
Re: [mythtv-users] is my processor to blame? (lockups, problems with FF and REW)
Do me a favour and lspci -v and paste the results, I'm curious to see if your PVR card is sharing an IRQ with your video card. I have yet to confirm if it really is the IRQ sharing, because it works on a machine that allows me to assign IRQ's, and it locks up on one that doesn't (and thus shares). Here is the info from my lspci -v Kenneth. -- 00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4) Flags: bus master, medium devsel, latency 0 Memory at e000 (32-bit, prefetchable) [size=32M] Capabilities: [a0] AGP version 2.0 Capabilities: [c0] Power Management version 2 00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] (prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, medium devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: a000-afff Memory behind bridge: dde0-dfef Prefetchable memory behind bridge: c5b0-cdcf Capabilities: [80] Power Management version 2 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22) Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA Bridge Flags: bus master, stepping, medium devsel, latency 0 00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 10) (prog-if 8a [Master SecP PriP]) Flags: bus master, medium devsel, latency 32 I/O ports at ffa0 [size=16] Capabilities: [c0] Power Management version 2 00:07.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 10) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller Flags: bus master, medium devsel, latency 64, IRQ 10 I/O ports at d800 [size=32] Capabilities: [80] Power Management version 2 00:07.4 SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30) Flags: medium devsel Capabilities: [68] Power Management version 2 00:09.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: Technotrend Systemtechnik GmbH Technotrend/Hauppauge DVB card rev2.1 Flags: bus master, medium devsel, latency 64, IRQ 12 Memory at de00 (32-bit, non-prefetchable) [size=512] 00:0a.0 Ethernet controller: Accton Technology Corporation EN-1216 Ethernet Adapter (rev 11) Subsystem: Standard Microsystems Corp [SMC]: Unknown device 1255 Flags: bus master, medium devsel, latency 64, IRQ 9 I/O ports at d400 [size=256] Memory at d800 (32-bit, non-prefetchable) [size=1K] Expansion ROM at dffc [disabled] [size=128K] Capabilities: [c0] Power Management version 2 00:0b.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 04) Subsystem: Creative Labs CT4850 SBLive! Value Flags: bus master, medium devsel, latency 64, IRQ 10 I/O ports at d000 [size=32] Capabilities: [dc] Power Management version 1 00:0b.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 01) Subsystem: Creative Labs Gameport Joystick Flags: bus master, medium devsel, latency 64 I/O ports at dc00 [size=8] Capabilities: [dc] Power Management version 1 00:0c.0 Multimedia video controller: Internext Compression Inc iTVC15 MPEG-2 Encoder (rev 01) Subsystem: Hauppauge computer works Inc. WinTV PVR-350 Flags: bus master, medium devsel, latency 64, IRQ 11 Memory at d800 (32-bit, prefetchable) [size=64M] Capabilities: [44] Power Management version 2 00:0d.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01) Subsystem: Hauppauge computer works Inc. WinTV PVR 250 Flags: bus master, medium devsel, latency 64, IRQ 12 Memory at d400 (32-bit, prefetchable) [size=64M] Capabilities: [44] Power Management version 2 01:00.0 VGA compatible controller: nVidia Corporation NV20 [GeForce3 Ti 500] (rev a3) (prog-if 00 [VGA]) Subsystem: Micro-Star International Co., Ltd.: Unknown device 8852 Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 11 Memory at de00 (32-bit, non-prefetchable) [disabled] [size=16M] Memory at c800 (32-bit, prefetchable) [disabled] [size=64M] Memory at cdc8 (32-bit, prefetchable) [disabled] [size=512K] Expansion ROM at dfef [disabled] [size=64K] Capabilities: [60] Power Management version 2 Capabilities: [44] AGP version 2.0 Some notes on my system. I don't have an onboard anything on this system. I have lan, sblive, pvr-350, pvr-250, and nexus 2.1 as well as an nvidia geforce 3 500. I run video out from the 350 into my tv, as well as the audio. I'll be switching my audio to pump through my sblive
Re: [mythtv-users] is my processor to blame? (lockups, problems with FF and REW)
BTW I just saw that there is an update to ivtv that I can download. Maybe this will help? I am scared to download it since I hear about people updating and their systems breaking totally. Andy where exactly do I find those settings? Thanks everyone for being so helpful. Cheers, Aaron ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
RE: [mythtv-users] is my processor to blame? (lockups, problems with FF and REW)
Chris wrote: I run mythbackend on FC3 with a 1 GHz P3 and a pinnacle capture card, and the system is generally unstable. I generally run my front end on a 400 Mhz PII running KnoppMyth, and that system is more stable. I know this isn't terribly helpful, but I often run other apps (mostly firefox and bittorrent) while mythbackend is running, and I get a lot of system crashes. What I'm trying to say is, I don't believe FC3 is a terribly stable OS. When I first went and looked at building a mythtv system I went with what I knew[1] SuSE 9.1, got to the bit about installing IvyTV drivers and after a bit more googling came across Jarod's site. Because of the step by step instructions (and atrpms) there I installed FC2, got it working (sort of) then because of stability and sound issues[2] swapped HD's and installed FC3, got it working then got fed up of the crashes/lockups and installed SuSE 9.1 again and it was *much* better, still crashed but not as often. I traced my stability issues in the end to dodgy memory, SuSE *seemed* to crash less but TBH that might be because I prefer SuSE. Make your own mind up but personally I say go with whatever you are the most comfortable with. FWIW my SuSE 9.1 system (Pundit-R/Nova-T/PVR-350) has had *zero* crashes. *HOWEVER* what I (and at least one other) have a problem with is if you play a mpeg2 file with errors[3] through mythtv and the pvr-350 tv out you can get the screen to freeze (normally when FF/REW) with errors in the frontend log such as 2005-02-23 15:27:26.722 Opening audio device '/dev/dsp'. 2005-02-23 15:27:26.722 Opening OSS audio device '/dev/dsp'. 2005-02-23 15:27:26.725 Using resampler. From: 0 to 1000 Using the PVR-350 decoder/TV-out 2005-02-23 15:27:27.098 Changing from None to WatchingPreRecorded 2005-02-23 15:27:27.113 Realtime priority would require SUID as root. IVTV_IOC_GET_TIMING: Input/output error ivtv rawframes descreased! did the decoder reset? IVTV_IOC_GET_TIMING: Input/output error ivtv rawframes descreased! did the decoder reset? This doesn't lock the box but needs a reboot for the frontend/X to work properly again. Druid [1] And had install disks for :-) [2] Which were stupidity issues not sound issues in the end ;-) [3] Such as for example a recording off a DVB-T/S card when the weathers crap. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] is my processor to blame? (lockups, problems with FF and REW)
Mine seemed stable before I upgraded to dual tuners. But I didn't have much of a chance to test it as I didn't get many shows recorded before I got excited and added more cards. I also added a 200G hard drive, and it's LVM, so granted I made alot of changes at once, but I can see mine be due to IRQ's. -- -=/Thom ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] is my processor to blame? (lockups, problems with FF and REW)
From the main screen in mythfronted: Utilities/Setup - Setup - TV Settings - Recording Profiles In the screen that comes up, choose MPEG-2 Encoders Then choose Live TV For me it's the 3rd screen in (first one is to change the profile name, second is to set the resolution... make sure it's at 720x480 or less). On the top field of the 3rd screen it will say something like Codec. Look below that for Stream Type. Change that around to some different ones (MPEG2-PS works great, but lots of people says DVDSpecial 2 is the best quality). Restart and see what happens. As for the IVTV codec, which are you using. If you installed from an rpm or via apt-get, you can check the version with the following command: # rpm -qa ivtv I am currently using ivtv 0.2 rc3e and it works well in terms of stability. -Andy On Mon, 28 Feb 2005 22:33:29 -0500, Aaron Aguilar [EMAIL PROTECTED] wrote: BTW I just saw that there is an update to ivtv that I can download. Maybe this will help? I am scared to download it since I hear about people updating and their systems breaking totally. Andy where exactly do I find those settings? Thanks everyone for being so helpful. Cheers, Aaron ___ 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
Re: [mythtv-users] is my processor to blame? (lockups, problems with FF and REW)
Aaron, 00:05.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416)MPEG-2 Encoder (rev 01) Subsystem: Hauppauge computer works Inc. WinTV PVR 250 Flags: bus master, medium devsel, latency 64, IRQ 5 00:14.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 AudioController (rev 20) Subsystem: FIRST INTERNATIONAL Computer Inc: Unknown device 8905 Flags: medium devsel, IRQ 5 If you can move the sound card to another IRQ in your BIOS setup and see if that solves your problem. Heck, share it with some other device instead of your PVR-250. If it fixes the ff/rew lockups, please let me know! :) Thom, 00:09.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: Technotrend Systemtechnik GmbH Technotrend/Hauppauge DVB card rev2.1 Flags: bus master, medium devsel, latency 64, IRQ 12 00:0c.0 Multimedia video controller: Internext Compression Inc iTVC15 MPEG-2 Encoder (rev 01) Subsystem: Hauppauge computer works Inc. WinTV PVR-350 Flags: bus master, medium devsel, latency 64, IRQ 11 00:0d.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01) Subsystem: Hauppauge computer works Inc. WinTV PVR 250 Flags: bus master, medium devsel, latency 64, IRQ 12 01:00.0 VGA compatible controller: nVidia Corporation NV20 [GeForce3 Ti 500] (rev a3) (prog-if 00 [VGA]) Subsystem: Micro-Star International Co., Ltd.: Unknown device 8852 Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 11 Whoa. With that many devices in there, I'd say it would be crazy hard to try and not share IRQ's. Then again, I'm not 100% sure it will fix ivtv's lockups. Maybe remove the DVB and pvr-250 and put the 350 on IRQ 12. While both of your all's lockups could be VIA chipset related, I'm less inclined to believe that in favour or some IRQ sharing problem in ivtv itself. Reason being is, I have experienced the ff/rew lockups on an intel chipset P3-667 system, but not on a VIA AMD 600Mhz system! :) I'm cross posting this on ivtv-devel in hopes someone has new information on IRQ sharing and lockups with newer ivtv driver versions. I know they're doing something with vsync IRQ code lately in the 0.3.x's, maybe that's somewhat related? Anyone in the know on that? -Kenneth ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
