On Saturday 10 September 2005 15:27, Paul V. Gratz wrote:
> Bonk..
>
> Does anyone have any possible help for me on this? I'm really stuck. Is
> there anything I should try?
> Thanks!
> Paul
>
> On Thursday 08 September 2005 10:18 pm, Paul V. Gratz wrote:
> > Hi,
> > I have a myth box that has been happily running with an old winTV go
> > card for about a year or so and recently I picked up a pvr-500 as an
> > upgrade. I've taken the old wintv card out so I only have the pvr-500 in
> > the system. I've installed the ivtv 0.3.7k drivers and I'm running the
> > gentoo 2.6.12-r9 kernel with all the i2c stuff compiled in as part of the
> > kernel (is this a problem?).
Shouldn't be. I do the same.
> > When I modprobe the ivtv driver and then
> > try to cat /dev/video0 > tmp.mpg the file size stays 0. Following the
> > instructions on the wiki I downloaded and installed the
> > pvr48wdm_1.8.22037.exe version of the firmware and have used the
> > ivtvfwextract.pl script to extract the .rom files and place them in
> > /lib/modules/. Here is my modules.conf:
> >
> > -----
> > alias char-major-81 videodev
> > alias char-major-81-0 ivtv
> > alias char-major-81-1 ivtv
> > options ivtv ivtv_std=1 tuner=57,57 ivtv_debug=1
> > options cx25840 debug=1
> > options saa7127
> > options msp3400 once=1 simple=1
Remove all options. Not needed.
> > ------
> > Linux video capture interface: v1.00
> > ivtv: ==================== START INIT IVTV ====================
> > ivtv: version 0.3.7 (k) loading
...
> > cx25840 debug: Module init
> > cx25840 debug: starting probe on adapter ivtv i2c driver #0 (0x10005)
> > ivtv warning: i2c client addr: 0x44 not found for command 0x800464cb!
Strange. See below for more instructions.
> > ivtv: Failed to load module wm8775
Where is module wm8775? Have you done a 'depmod' after installation of the
drivers?
Address 0x44 is that of the cx25840 chip. It is strange that it cannot be
found. How do you load the modules? modprobe ivtv should be enough. Can you
give the output of 'lsmod' after loading the driver?
Also provide the output of the following: run i2cdetect (hopefully installed
on your system). You should see a list of installed i2c busses. Now run
i2cdetect -a <busnr> where busnr is the number of the ivtv i2c bus (pick
one). Say 'Y' to the 'Continue' question and mail the output.
Hans
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
