Hi.
I dont have a Samsung but my system went furious after updating svn to 3150,
3149 is fine tho.
Here is what comes on 2.6.15-gentoo-r2 #5 Tue Feb 7 00:02:53 CET 2006 x86_64
AMD Athlon(tm) 64 Processor 2800+
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.4.3 (development revision 3150) loading
ivtv: Linux version: 2.6.15-gentoo-r2 gcc-3.4
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 WinTV PVR 350 card (cx23415 based)
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 19
GSI 19 sharing vector 0xC9 and IRQ 19
ACPI: PCI Interrupt 0000:02:08.0[A] -> Link [LNKC] -> GSI 19 (level, low) ->
IRQ 201
msp3400 2-0040: ivtv driver
msp3400 2-0040: chip=MSP4418G-A2 +nicam +simple +simpler +radio mode=simpler
ivtv0: i2c attach to card #0 ok [client=MSP4418G-A2, addr=40]
msp3400 2-0040: msp34xxg daemon started
tveeprom: ivtv version
tveeprom: Hauppauge: model = 48134, rev = I121, serial# = 6183422
tveeprom: tuner = Philips FM1216 (idx = 21, type = 5)
tveeprom: tuner fmt = PAL(B/G) (eeprom = 0x04, v4l2 = 0x00000007)
tveeprom: audio processor = MSP4418 (type = 19)
tveeprom: decoder processor = SAA7115 (type = 13)
ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
saa7115 2-0021: ivtv driver
saa7115 2-0021: saa7115 found @ 0x42 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=saa7115, addr=21]
saa7127 2-0044: ivtv driver
saa7127 2-0044: saa7127 found @ 0x88 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=saa7127, addr=44]
Unable to handle kernel paging request at ffffc20001141000 RIP:
<ffffffff88027a14>{:ivtv:load_fw_direct+116}
PGD 80df067 PUD 80de067 PMD 1e631067 PTE 0
Oops: 0000 [1]
CPU 0
Modules linked in: tda9887 saa7127 saa7115 tuner tveeprom ivtv msp3400
i2c_algo_bit videodev i2c_nforce2 i2c_core
Pid: 5124, comm: modprobe Not tainted 2.6.15-gentoo-r2 #5
RIP: 0010:[<ffffffff88027a14>] <ffffffff88027a14>{:ivtv:load_fw_direct+116}
RSP: 0018:ffff81001e5f9b08 EFLAGS: 00010287
RAX: 0000000000000000 RBX: 0000000000040000 RCX: 0000000000020000
RDX: ffffc20001141000 RSI: ffffc200000c0000 RDI: ffff81001e554dc0
RBP: ffff81001e700000 R08: 0000000000000001 R09: 000000000000005f
R10: 0000000000000000 R11: ffffffff802d79b0 R12: ffffffff8803abb3
R13: 0000000000040000 R14: ffffc20000080000 R15: 0000000000000017
FS: 0000000000514ae0(0000) GS:ffffffff805dd800(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: ffffc20001141000 CR3: 000000001e551000 CR4: 00000000000006e0
Process modprobe (pid: 5124, threadinfo ffff81001e5f8000, task ffff81001f334b70)
Stack: ffff81001f334b70 ffff81001e554dc0 ffff81001e700000 0000000080000640
000000000000001a ffff81001feb0800 ffff81001e7000e0 ffffffff880283fa
ffff81001e700000 ffffffff88028918
Call Trace:<ffffffff880283fa>{:ivtv:ivtv_firmware_copy+74}
<ffffffff88028918>{:ivtv:ivtv_firmware_init+632}
<ffffffff880205e2>{:ivtv:ivtv_probe+5970}
<ffffffff80140748>{call_usermodehelper_keys+200}
<ffffffff80248c42>{kobject_get+18}
<ffffffff80254416>{pci_device_probe+102}
<ffffffff802d31df>{driver_probe_device+79}
<ffffffff802d32e0>{__driver_attach+0}
<ffffffff802d331f>{__driver_attach+63}
<ffffffff802d32e0>{__driver_attach+0}
<ffffffff802d2719>{bus_for_each_dev+73}
<ffffffff802d2c68>{bus_add_driver+136}
<ffffffff802d378a>{driver_register+58}
<ffffffff80254210>{__pci_register_driver+144}
<ffffffff88020f23>{:ivtv:module_start+243}
<ffffffff8014ada9>{sys_init_module+6089}
<ffffffff80162850>{remove_vma+80} <ffffffff80163d8e>{do_munmap+670}
<ffffffff8010e936>{system_call+126}
Code: 48 8b 02 83 c1 04 48 83 c2 08 48 89 06 48 83 c6 08 eb e9 e8
RIP <ffffffff88027a14>{:ivtv:load_fw_direct+116} RSP <ffff81001e5f9b08>
CR2: ffffc20001141000
/Fredrik
2006-02-07 00:22 skrev Hans Verkuil <[EMAIL PROTECTED]>
>I finally had time to look at the reported Samsung tuner problems and I
>discovered that I had forgotten to take a NTSC offset into account. The
>attached patch is for tuner.c from ivtv-0.4.2 and should correct all
>problems. Please test!
>
>I\'ve also committed the change to ivtv-0.4 in subversion, so you can
>also you that for testing.
>
>Please let me know any test results asap as I also have to fix this
>before the 2.6.16 kernel is released.
>
> Hans
>
>
>_______________________________________________
>ivtv-devel mailing list
>[email protected]
><b><a href=http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>TARGET=\"_new\">http://ivtvdriver.org/mailman/listinfo/ivtv-devel</a></b>
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
