On Tue, 2008-09-09 at 19:59 -0600, engage wrote: > Well Andy, I downloaded and extracted the tarball & compared the extracted > firmware files to the firmware in /lib/firmware/ and they are a match. In > other words, I already had the firmware installed.
OK. One unknown eliminated. > So, there must be another > issue at work here. Yup. There has to be. See below.... > Google hasn't been much help concerning this issue > either. And I'm not getting any replies in #ivtv-dev either. > > On Sunday 07 September 2008 19:09:49 engage wrote: > > On Sunday 07 September 2008 18:05:30 Andy Walls wrote: > > > On Sun, 2008-09-07 at 14:49 -0600, engage wrote: > > > > >From what I have read, this dmesg output indicates that > > > > > > > > ivtv-firmware-20070217-1plf2007.1 should be the correct firmware. The > > > > PVR-250 works but I get 0 byte files from the PVR-150. Both are > > > > installed in the same box. > > > > > > > > ivtv: Start initialization, version 1.3.0 > > > > ivtv0: Initializing card #0 > > > > ivtv0: Autodetected Hauppauge card (cx23416 based) > > > > ivtv0: Unreasonably low latency timer, setting to 64 (was 32) > > > > ivtv0: Autodetected Hauppauge WinTV PVR-150 > > > > ivtv0: Reopen i2c bus for IR-blaster support > > > > cx25840 0-0044: cx25843-24 found @ 0x88 (ivtv i2c driver #0) > > > > tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0) > > > > wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0) > > > > ivtv0: Registered device video0 for encoder MPG (4096 kB) > > > > ivtv0: Registered device video32 for encoder YUV (2048 kB) > > > > ivtv0: Registered device vbi0 for encoder VBI (1024 kB) > > > > ivtv0: Registered device video24 for encoder PCM (320 kB) > > > > ivtv0: Initialized card #0: Hauppauge WinTV PVR-150 > > > > ivtv1: Initializing card #1 > > > > ivtv1: Autodetected Hauppauge card (cx23416 based) > > > > ivtv1: Unreasonably low latency timer, setting to 64 (was 32) > > > > ivtv1: Autodetected Hauppauge WinTV PVR-250 > > > > saa7115 1-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv i2c driver > > > > #1) msp3400 1-0040: MSP3435G-B6 found @ 0x80 (ivtv i2c driver #1) > > > > tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #1) > > > > ivtv1: Registered device video1 for encoder MPG (4096 kB) > > > > ivtv1: Registered device video33 for encoder YUV (2048 kB) > > > > ivtv1: Registered device vbi1 for encoder VBI (1024 kB) > > > > ivtv1: Registered device video25 for encoder PCM (320 kB) > > > > ivtv1: Initialized card #1: Hauppauge WinTV PVR-250 > > > > ivtv: End initialization > > > > ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes) > > > > ivtv0: Encoder revision: 0x02060039 > > > > [<f8e57ae0>] (ivtv_irq_handler+0x0/0x12f0 [ivtv]) The above line is *not* emitted by the ivtv driver. This sort of line is usually emitted by another part of the kernel that trapped something bad. The dump from the trap usually includes a lot more context. (See linux/arch/x86/kernel/traps_32.c) Since the log you provided had "ivtv" on every line, I assumed you did a 'dmesg | grep ivtv' or something similar to generate the log output. The problem is, I cannot help you resolve your problem without all that additional debug context that the kernel outputs. One line telling me that something happened at offset 0 of the ivtv_irq_handler() is not enough to work with. Please carefully check the dmesg or /var/log/messages output for a full dump from the kernel. That'll at least give me some hope of telling you what has happened. All I can tell you right now is that setup of the driver for one card probably failed. But you already knew that. :) Regards, Andy > > > Something bad happened here. Likely a kernel oops. Don't just grep for > > > ivtv. PLease give the whole log between start and end initialization. > > > > That is what is in the log from start to finish during initialization. > > There are no errors or warnings. > > > > > > ivtv1: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes) > > > > ivtv1: Encoder revision: 0x02060039 > > > > [EMAIL PROTECTED] ~]$ rpm -qa | grep ivtv > > > > ivtv-firmware-20070217-1plf2007.1 > > > > perl-Video-ivtv-0.13-3mdv2008.1 > > > > ivtv-0.10-0.10.2-3mdv2008.1 > > > > > > As for what firmware to use, maybe you can look in this directory: > > > > > > http://dl.ivtvdriver.org/ivtv/firmware/ > > > > I'd rather use the rpm package. > > > > > The readme file may help. It says all the firmware files you would need > > > are in: > > > > > > http://dl.ivtvdriver.org/ivtv/firmware/ivtv-firmware.tar.gz > > > > > > > > > (I only have a PVR-150MCE myself and I used the firmware that came with > > > the Windows driver.) > > > > > > Regards, > > > Andy > > _______________________________________________ > ivtv-users mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-users > _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
