Ok got it so I could manually modprobe it. The report is clean now. Mythtv still complains about same thing and will not play live tv or record. Playing an old recording still works so I assume it's something wrong with the encoder.
Also, even when I use startx and then allow x to terminate after logout, ivtv still complains that its in use. A quick fix that appears to be working at this moment is to do a make install of the base 4.0 then do a make install of the previous (first 4.1 release candidate?) 4.1 you gave me a link to. Everyhing appears to work. Depmod still complains about the jiffies but it works. I know this products redundant driver files with no way of knowing which ones are running. I am still getting the odd log entries ( never got around to in original posts). In my mythbackend log I am getting <timestamp> 6 128000 <timestamp> 6 128000 <timestamp> 6 128000 <timestamp> 6 128000 <timestamp> 6 128000 over and over once ever second or so the entire time I am watching live tv. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Deyan Bektchiev Sent: Thursday, December 08, 2005 2:50 PM To: Discussion list for development of the IVTV driver Subject: Re: [ivtv-devel] 4.1 report and odd log entries It might be simpler to just boot into level 3 and then use startx to start the X server. Then either logging out, or Ctrl+Alt+Backspace would kill X. Dejan Brent Kilgore wrote: > > I am using the ivtvctl from the current 4.1 svn. I have also, just for > the heck of it. Tried replacing it with the ivtvctl from the previous > 4.1 svn, the 4.0 and the 3.7i. I get the exact same errors with all of > them. > > I removed all options from all the ivtv loading. I don't know if > modprobe is giving the same messages about warnings because X is set > to use it and will not unload while x is running. I have not found a > "graceful" way to kill x other than reboot. init 3 does not work for > some reason. > > The last time this error occurs was way ack in the 0.1 days according > to google. > > -----Original Message----- > *From:* [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] *On Behalf Of *Keith C > *Sent:* Thursday, December 08, 2005 2:15 PM > *To:* Discussion list for development of the IVTV driver > *Subject:* Re: [ivtv-devel] 4.1 report and odd log entries > > On Dec 8, 2005, at 12:45 PM, Brent Kilgore wrote: > >> Ok, nevermind I think I got it. The firmware files were not in right >> place of course. I had to move and rename them. I put a note on the >> wiki about having to rename them under the hotplug section. It still >> isn't working though. >> >> I am getting errors in mythtv now when I try to watch live tv. >> Watching a recording works fine as does the direct dd if=/dev/video0 >> of=/dev/video16. This worked great before I updated >> >> Changing from None to WatchingLiveTV >> >> 2005-12-08 13:38:39.375 Using profile 'Live TV' to record >> >> 2005-12-08 13:38:39.381 Channel(/dev/video0)::CheckSignalFull(): >> input = 4 >> >> 2005-12-08 13:38:39.386 Channel(/dev/video0)::SetColourAttribute(): >> failed to set controls, error: Invalid argument >> >> 2005-12-08 13:38:39.390 Channel(/dev/video0)::SetColourAttribute(): >> failed to set controls, error: Invalid argument >> >> 2005-12-08 13:38:39.394 Channel(/dev/video0)::SetColourAttribute(): >> failed to set controls, error: Invalid argument >> >> 2005-12-08 13:38:39.397 Channel(/dev/video0)::SetColourAttribute(): >> failed to set controls, error: Invalid argument >> >> Error setting codec params >> >> VIDIOC_S_CTRL:: Invalid argument >> > ivtvctl does like the arguments that myth sent it. You might want to > check that you are using the ivtvctl that came with your new drivers > and not an older one. > > <snip> > > > > Warning: ignoring enable_output=1, no such parameter in this module > > Warning: ignoring output_select=0, no such parameter in this module > > Module saa7127 loaded, with warnings > > Module saa7115 loaded, with warnings > > Module msp3400 loaded, with warnings > > Looks like you have tons of garbage in your modprobe.conf that isn't > needed and/or is detrimental. Very few NTSC users have to have any > options at all for recording. > > Keith C > _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
