FS#6443 - ivtv and kernel 2.6.20
Attached to Project:
Arch Linux
Opened by enderst (enderst) - Saturday, 17 February 2007, 22:25 GMT
Last edited by Paul Mattal (paul) - Wednesday, 02 May 2007, 03:54 GMT
Opened by enderst (enderst) - Saturday, 17 February 2007, 22:25 GMT
Last edited by Paul Mattal (paul) - Wednesday, 02 May 2007, 03:54 GMT
|
Details
when i try to load the ivtv module everything seems fine
until i try to watch tv, i get a picture and no sound. dmesg
shows 'fw_register_device: device_register failed
cx25840 2-0044: unable to open firmware v4l-cx25840.fw' as tpb pointed out in the forum, the readme states "NOTE: This driver will work with kernels 2.6.18, 2.6.19 and 2.6.20. For the latter kernel you will need to apply the cx25840.diff patch that is in the 'misc' directory (only if your card has the cx2584x chip, it is not needed otherwise). The 2.6.20 kernel caused a cx2584x bug to surface that prevents loading of the cx2584x firmware." |
This task depends upon
Closed by Paul Mattal (paul)
Wednesday, 02 May 2007, 03:54 GMT
Reason for closing: Not a bug
Additional comments about closing: Apparently not an ivtv bug but rather an i2c issue.
Wednesday, 02 May 2007, 03:54 GMT
Reason for closing: Not a bug
Additional comments about closing: Apparently not an ivtv bug but rather an i2c issue.
Please let me know!
Sound is working for me on my PVR150.
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.10.0 (tagged release) loading
ivtv: Linux version: 2.6.20-ARCH SMP preempt mod_unload 686
ivtv: In case of problems please include the debug info between
ivtv: the START INIT IVTV and END INIT IVTV lines, along with
ivtv: any module options, when mailing the ivtv-users mailinglist.
ivtv0: Autodetected Hauppauge card (cx23416 based)
ACPI: PCI Interrupt 0000:01:08.0[A] -> Link [APC1] -> GSI 16 (level, low) -> IRQ 20
ivtv0: loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
ivtv0: Encoder revision: 0x02060039
tveeprom 5-0050: Hauppauge model 26032, rev C199, serial# 2979196
tveeprom 5-0050: tuner model is TCL 2002N 5H (idx 99, type 50)
tveeprom 5-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 5-0050: audio processor is CX25841 (idx 35)
tveeprom 5-0050: decoder processor is CX25841 (idx 28)
tveeprom 5-0050: has no radio, has IR receiver, has IR transmitter
ivtv0: Autodetected Hauppauge WinTV PVR-150
ivtv0: reopen i2c bus for IR-blaster support
tuner 5-0061: chip found @ 0xc2 (ivtv i2c driver #0)
cx25840 5-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
kobject_add failed for i2c-5 with -EEXIST, don't try to register things with the same name in the same directory.
[<c0225045>] kobject_add+0x115/0x1b0
[<c028ad1c>] device_add+0xbc/0x520
[<f8ce45f8>] ivtv_xfer+0xa8/0x3c0 [ivtv]
[<c0224cff>] kobject_get+0xf/0x20
[<c0291020>] _request_firmware+0xf0/0x300
[<c02912df>] request_firmware+0xf/0x20
[<f8d4eba4>] cx25840_loadfw+0x24/0x210 [cx25840]
[<f8b85378>] i2c_master_send+0x38/0x50 [i2c_core]
[<f8d4c8cd>] cx25840_initialize+0x15d/0x2a0 [cx25840]
[<f8d4e2c4>] cx25840_detect_client+0x234/0x260 [cx25840]
[<f8b85b9e>] i2c_probe_address+0x3e/0x130 [i2c_core]
[<f8b85e97>] i2c_probe+0x207/0x220 [i2c_core]
[<f8d4e090>] cx25840_detect_client+0x0/0x260 [cx25840]
[<c028d273>] driver_create_file+0x33/0x50
[<f8d4e090>] cx25840_detect_client+0x0/0x260 [cx25840]
[<f8b86399>] i2c_register_driver+0x79/0xa0 [i2c_core]
[<c0144d9f>] sys_init_module+0x15f/0x1ad0
[<c0225d8f>] prio_tree_insert+0x1f/0x250
[<c0103200>] sysenter_past_esp+0x5d/0x81
=======================
fw_register_device: device_register failed
cx25840 5-0044: unable to open firmware v4l-cx25840.fw
wm8775 5-001b: chip found @ 0x36 (ivtv i2c driver #0)
ivtv0: Registered device video0 for encoder MPEG (4 MB)
ivtv0: Registered device video32 for encoder YUV (2 MB)
ivtv0: Registered device vbi0 for encoder VBI (1 MB)
ivtv0: Registered device video24 for encoder PCM audio (1 MB)
tuner 5-0061: type set to 50 (TCL 2002N)
ivtv0: Initialized Hauppauge WinTV PVR-150, card #0
ivtv: ==================== END INIT IVTV ====================
please close this. seems to be an i2c issue not ivtv. i've never had an i2c issue before but ivtv is a crap shoot after ivtv/kernel upgrades. thanks for your help
I don't know if the i2c issue you're having is broader than just with ivtv but maybe this can help you out! And I don't mind leaving this open awhile and helping you through the i2c issue.