I'd suggest also using ivtvctl to poke around. Also ivtv-tune. Disable everything not needed, shut the machine down for 3 minutes. Start it back up and do some sanity checks. Look at the log. list the modules. Cat the stream to a file. Assuming everything is still working the way it is now, can you tune the card?
Can you force a reload of the firmware (ivtvctl -H)?
Can you get a sync (ivtvctl -k)?
Can you set and read registers on the card (ivtvctl -Y ; ivtvctl -y mute=1 ; ivtvctl -Y ; ivtvctl -y mute=0 ; ivtvctl -Y)?
I'm not sure - does anyone know if the debug level set with ivtvctl is sticky across invocations? Otherwise, add -D=99 to the above. (actually this flag doesn't seem to work)
[ ~]$ ivtvctl -m
ioctl VIDIOC_QUERYCAP ok
Driver name : ivtv
Card type : Hauppauge WinTV PVR-350
Bus info : 0000:01:04.0
Driver version: 1537
Capabilities : 0x010700F3
[ ~]$
and some followup inline below,
HTH
On Sat, 2006-04-15 at 20:13 -0400, Bill Baker wrote:
Are they still owned by the MythTV user? Mine are owned by the logged in user and that's the only R/W permissions for them.On Sat, 2006-04-15 at 17:56 -0500, Richard Hendershot wrote: > On Sat, 2006-04-15 at 17:05 -0400, Bill Baker wrote: > > On Sat, 2006-04-15 at 10:09 -0500, Richard Hendershot wrote: > > > My video devices are owned by my login user, root group. can you sudo > > > cat /dev/video0 > tst.mpg ? or perhaps this trace was while you > > > logged in as root? > > > > Logging in as root did the trick, although all I got was a few seconds > > of a black screen. So I at least chown'd my /dev/video* devices to the > > mythtv group. > make sure they're RW for that group. Mine have no group permissions. > I think it's udev that sets these to be owned by me (as a regular > user) when I login. After I rebooted, I found that the video devices had been changed back to the root group, and from the Fedora Myth(TV)ology web page, it seems like that's normal.
[rhendershot ~]$ ls -l /dev/video*
lrwxrwxrwx 1 root root 6 Apr 15 17:38 /dev/video -> video0
crw------- 1 rhendershot root 81, 0 Apr 15 17:38 /dev/video0
crw------- 1 rhendershot root 81, 16 Apr 15 17:38 /dev/video16
crw------- 1 rhendershot root 81, 24 Apr 15 17:38 /dev/video24
crw------- 1 rhendershot root 81, 32 Apr 15 17:38 /dev/video32
crw------- 1 rhendershot root 81, 48 Apr 15 17:38 /dev/video48
[rhendershot ~]$
> > > I don't load the framebuffer nor lirc. I'm ignoring the mplayer deal > > > at this point since it sounds broken. capturing the stream is a good > > > test. > > > > > > All I have in my modprobe.conf is for snd and eth0. Since a lot of > > > this is in the kernel I don't think anything is needed. I'm not sure > > > about FB and LIRC though. I'd suggest taking that all out and seeing > > > what works, add it back in one at a time. I have an all-encompassing > > > (or encompassing enough for my needs ;) mod removal that I use to dump > > > ivtv related modules so I can load fresh. your needs are probably a > > > little different but here goes, fyi > > > > > > /sbin/rmmod ivtv bttv cx8800 cx88xx cx25840 tuner tveeprom msp3400 > > > wm8775 tda9887 saa7115 saa7127 > > > /sbin/depmod -a > > > /sbin/modprobe ivtv > > > > Unfortunately, all that did was to make it return to the main MythTV > > screen faster after I pressed "Watch TV". > > Using MythTV to troubleshoot adds a lot of indirection and > abstraction. There's a lot of mention in the ivtv readme's about > making sure to cold boot (leaving the machine off for a minute or more > before powering up again), the framebuffer device interacting with the > driver > "3. The framebuffer will not allow direct writing safely, it > will mess up > encoding and decoding, usually making the chip inoperable > until another > reboot." > , and that module options are not necessary most all of the time. > > what do you get from > grep -A 11 ivtv /etc/sysconfig/hwconf driver: ivtv desc: "Internext Compression Inc iTVC15 MPEG-2 Encoder" vendorId: 4444 deviceId: 0803 subVendorId: 0070 subDeviceId: 4000 pciType: 1 pcidom: 0 pcibus: 0 pcidev: a pcifn: 0 - > ..which kudzu places into this file on boot. I don't think you need > anything about ivtv in modprobe.conf I think all you need are the > eth0 and usb-controller lines, until ivtv is working, then put lirc > back in then put ivtv_fb back in. I tried commenting those lines out and rebooting, but it didn't make a difference. > btw, in the docs, the first node (char-major-81) is videodev, not > ivtv. the minor node (char-major-81-0) is ivtv > alias char-major-81 videodev > alias char-major-81-0 ivtv > ...so if you keep these, this might have an effect. I saw that on the page and changed the modprobe.conf file to reflect that. > Do you have videodev module loaded? > > [sys]# /sbin/lsmod |grep ivtv > ivtv 160400 0 > v4l1_compat 11973 1 ivtv > tveeprom 13905 1 ivtv > videodev 9409 1 ivtv > i2c_core 20673 9 msp3400,saa7127,saa7115,tda9887,tuner,ivtv,tveeprom,i2c_algo_bit,i2c_i801 > [sys]# I sure do. # lsmod | grep ivtv ivtv_fb 26980 0 ivtv 179216 1 ivtv_fb v4l1_compat 13381 1 ivtv tveeprom 14673 1 ivtv i2c_core 21825 7 msp3400,saa7127,saa7115,tda9887,tuner, ivtv,tveeprom videodev 9537 1 ivtv
The only other thing I notice is your i2c_core lacks algo_bit and i801 members, but that's probably due to different hardware, fedora release, kernel build or some mixture of those...
> > > btw- If you'd built ivtv from sources you probably have detritus in > > > usr/local. Maybe you're loading old msp or other modules from there, > > > so another suggestion would be to make certain the ivtv stuff is all > > > in one place and the stuff you want it to be. > > > > Actually, I just followed the instructions at > > http://wilsonet.com/mythtv/fcmyth.php > > I didn't build any packages at all. > That one's a little out of date. Can you suggest a better site? I'm also open to using other distributions. I've tried KnoppMyth and Fedora so far, with no luck.
well, I find that installing the firmware and kernel pieces from atrpms has pretty much never failed to get the ability to get a stream from the capture device. The instructions for MythTV go beyond that, as have you, towards getting remote control and framebuffer features that I've not yet tried too hard for. Times this has failed for me had to do with old utilities built from source, not finding firmware, needing to upgrade settings in modprobe.conf (for a short time we had to relabel them to prevent collision with the kernel modules, prior to that we had to remove the kernel modules, now is much much better :)
But none of this has anything to do with such instructions as you mention since getting a stream from the card needs nothing from Myth or xawtv (and likewise, IR remote nor PVR-350 framebuffer shenannigans ;)
|
-- Richard Hendershot <[EMAIL PROTECTED]> |
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
