>>>>> On Thu, 12 Jun 2008 10:17:52 -0400 (EDT), Junk Mail <[EMAIL PROTECTED]> sa id:
JM> I did see that thread, but assumed that silence indicated some sort of JM> resolution. The lack of resolution is a little concerning, but at the same JM> time, if it were a common problem there would be more traffic about it, JM> right? I've never gotten the problem to go away. I can trigger it much more easily the more the machine is doing. The CPU never breaks a sweat which is why I think it's more likely a bus issue (and hence am more likely to blame my fairly cheap motherboard that I got for free with my decent CPU). I don't think it's a really common problem, but I don't think I'm the only one. The people with the problem are fairly small in number though (you make a definite 2 but I'm sure there are a few others)... Anyway, if I record two shows at once and watch another it'll trigger it. Maybe. And frequently if I'm watching a show *before* the recordings start, it doesn't have an issue. It's often only when I try to starting watching a recording (or doing just about anything with the system actually, including playing something like supertux) and the system is already recording something that the failures start. Right now, the machine has been up for 9 days because we haven't watched much when the machines been busy recording. >> I've been sort of convinced I need a better motherboard, but I'm not >> positive. Any chance your motherboard is based on the VIA chipset? JM> No, not a VIA chipset (as far as I can tell). lsmod | grep via will likely tell you. If you have via_rhine or sata_via installed, eg, you might have a via chipset. I'm very much interested to know if you have issues with a different chipset! -- "In the bathtub of history the truth is harder to hold than the soap, and much more difficult to find." -- Terry Pratchett _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
