Since about 1 month ago I have had a serious problem that is reducing
the WAF (wife acceptance factor) since it seems to manifest only on
the her shows. I mean about 1 day a week I get blank recordings from
my hauppage pvr 500. What I mean is the screen is black with no volume
for the entirety of the recording. Before 1 month ago this had never
happened. There are no error messages in dmesg or mythtv at all. When
the tuner gets into this blank screen mode if I
mplayer /dev/video1
I do get a blank screen with no sound as well.
This seems to be more frequent on a reboot or restarting of mythtv.
Since I updated to the latest myth 0.21 fixes svn, updated to a
2.6.27.21 kernel and to the bleeding edge ivtv all at the same time I
can not rule out any of these so this makes it difficult to debug.
Also when it did this yesterday (seemed to be triggered by restarting
mythbackend) after stoping mythbackend I could not modprobe -r ivtv
because it said that the device was in use. However I do not believe
this was the case. There were no myth processes running and I did not
have any other captures running either.
Has anyone had this problem? Ideas how to debug this?
--
John M. Drescher
_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
the WAF (wife acceptance factor) since it seems to manifest only on
the her shows. I mean about 1 day a week I get blank recordings from
my hauppage pvr 500. What I mean is the screen is black with no volume
for the entirety of the recording. Before 1 month ago this had never
happened. There are no error messages in dmesg or mythtv at all. When
the tuner gets into this blank screen mode if I
mplayer /dev/video1
I do get a blank screen with no sound as well.
This seems to be more frequent on a reboot or restarting of mythtv.
Since I updated to the latest myth 0.21 fixes svn, updated to a
2.6.27.21 kernel and to the bleeding edge ivtv all at the same time I
can not rule out any of these so this makes it difficult to debug.
Also when it did this yesterday (seemed to be triggered by restarting
mythbackend) after stoping mythbackend I could not modprobe -r ivtv
because it said that the device was in use. However I do not believe
this was the case. There were no myth processes running and I did not
have any other captures running either.
Has anyone had this problem? Ideas how to debug this?
--
John M. Drescher
_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users