Hello Since a month I had several hangups. When they happen (eg. recording), I do not know. For sure I know they don't happened during playback. The problem started as soon as I wanted to update to the new kernel fc5-2288. This I didn't get to work due to fb failures and due to lack of time I reverted back to my stable fc5-2257 kernel. Something what I missed and noticed today, was the installation of ivtv-firmware-20070217-13.at.
ivtv0: Encoder revision: 0x02060039 ivtv0 warning: Encoder Firmware can be buggy, use version 0x02040011, 0x02040024 or 0x02050032. Do you have ivtv-firmware-20070217-13.at installed ? I do not know the previous version installed, is there a way to find out ? In /var/log/rpm* I found ivtv-firmware-1.8a-10.at.noarch.rpm (29.05.2006). Searching atrpms I noticed there were several patches since this release. I can not remember, but I think I never installed newer ones. I had some old dmesg outputs, I believe 0x02050032 was the version I used since a year without problems. When I have time I will try ivtv-firmware-1.8a-10.at.noarch.rpm. Regards Hans ivtv: ==================== START INIT IVTV ==================== ivtv: version 0.8.2 (tagged release) loading ivtv: Linux version: 2.6.18-1.2257.fc5 mod_unload 686 REGPARM 4KSTACKS gcc-4.1 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. ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 201 PCI: Setting latency timer of device 0000:00:1d.1 to 64 uhci_hcd 0000:00:1d.1: UHCI Host Controller uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2 uhci_hcd 0000:00:1d.1: irq 201, io base 0x00002460 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 23 (level, low) -> IRQ 209 PCI: Setting latency timer of device 0000:00:1d.7 to 64 ehci_hcd 0000:00:1d.7: EHCI Host Controller ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 3 ehci_hcd 0000:00:1d.7: debug port 1 PCI: cache line size of 128 is not supported by device 0000:00:1d.7 ehci_hcd 0000:00:1d.7: irq 209, io mem 0xfc480000 ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 usb usb3: configuration #1 chosen from 1 choice hub 3-0:1.0: USB hub found hub 3-0:1.0: 6 ports detected ivtv0: Autodetected Hauppauge card (cx23415 based) ACPI: PCI Interrupt 0000:05:04.0[A] -> GSI 16 (level, low) -> IRQ 193 ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes) saa7127 2-0044: saa7129 found @ 0x88 (ivtv i2c driver #0) tveeprom 2-0050: Hauppauge model 48139, rev K257, serial# 7805538 tveeprom 2-0050: tuner model is Philips FM1216 ME MK3 (idx 57, type 38) tveeprom 2-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K) (eeprom 0x74) tveeprom 2-0050: audio processor is MSP4418 (idx 25) tveeprom 2-0050: decoder processor is SAA7115 (idx 19) tveeprom 2-0050: has radio, has IR remote ivtv0: Autodetected Hauppauge WinTV PVR-350 tuner 2-0043: chip found @ 0x86 (ivtv i2c driver #0) tda9887 2-0043: tda988[5/6/7] found @ 0x43 (tuner) tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0) saa7115 2-0021: saa7115 found @ 0x42 (ivtv i2c driver #0) msp3400 2-0040: MSP4418G-B3 found @ 0x80 (ivtv i2c driver #0) msp3400 2-0040: MSP4418G-B3 supports nicam and radio, mode is autodetect and autoselect ivtv0: Encoder revision: 0x02060039 ivtv0 warning: Encoder Firmware can be buggy, use version 0x02040011, 0x02040024 or 0x02050032. ivtv0: Decoder revision: 0x02020023 ivtv0: Registered device video0 for encoder MPEG ivtv0: Registered device video32 for encoder YUV ivtv0: Registered device vbi0 for encoder VBI ivtv0: Registered device video24 for encoder PCM audio ivtv0: Registered device radio0 for encoder radio ivtv0: Registered device video16 for decoder MPEG ivtv0: Registered device vbi8 for decoder VBI ivtv0: Registered device vbi16 for decoder VOUT ivtv0: Registered device video48 for decoder YUV ivtv0: loaded v4l-cx2341x-init.mpg firmware (155648 bytes) tuner 2-0061: type set to 38 (Philips PAL/SECAM multi (FM1216ME MK3)) ivtv0: Initialized Hauppauge WinTV PVR-350, card #0 ivtv: ====================== NEXT CARD ====================== ivtv1: Autodetected Hauppauge card (cx23416 based) ACPI: PCI Interrupt 0000:06:08.0[A] -> GSI 21 (level, low) -> IRQ 217 ivtv1: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) tuner 3-0043: chip found @ 0x86 (ivtv i2c driver #1) tda9887 3-0043: tda988[5/6/7] found @ 0x43 (tuner) tuner 3-0060: TEA5767 detected. tuner 3-0060: chip found @ 0xc0 (ivtv i2c driver #1) tuner 3-0060: type set to 62 (Philips TEA5767HN FM Radio) tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #1) tveeprom 3-0050: Hauppauge model 23559, rev D591, serial# 8201932 tveeprom 3-0050: tuner model is Philips FQ1216AME MK4 (idx 91, type 56) tveeprom 3-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K) (eeprom 0x74) tveeprom 3-0050: second tuner model is Philips TEA5768HL FM Radio (idx 101, type 62) tveeprom 3-0050: audio processor is CX25843 (idx 37) tveeprom 3-0050: decoder processor is CX25843 (idx 30) tveeprom 3-0050: has radio, has no IR remote ivtv1: Autodetected WinTV PVR 500 (unit #1) cx25840 3-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1) cx25840 3-0044: loaded v4l-cx25840.fw firmware (16382 bytes) wm8775 3-001b: chip found @ 0x36 (ivtv i2c driver #1) ivtv1: Encoder revision: 0x02060039 ivtv1 warning: Encoder Firmware can be buggy, use version 0x02040011, 0x02040024 or 0x02050032. ivtv1: Registered device video1 for encoder MPEG ivtv1: Registered device video33 for encoder YUV ivtv1: Registered device vbi1 for encoder VBI ivtv1: Registered device video25 for encoder PCM audio ivtv1: Registered device radio1 for encoder radio tuner 3-0061: type set to 56 (Philips PAL/SECAM multi (FQ1216AME MK4)) ivtv1: Initialized WinTV PVR 500 (unit #1), card #1 ivtv: ====================== NEXT CARD ====================== ivtv2: Autodetected Hauppauge card (cx23416 based) ACPI: PCI Interrupt 0000:06:09.0[A] -> GSI 22 (level, low) -> IRQ 225 ivtv2: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) tuner 4-0043: chip found @ 0x86 (ivtv i2c driver #2) tda9887 4-0043: tda988[5/6/7] found @ 0x43 (tuner) tuner 4-0061: chip found @ 0xc2 (ivtv i2c driver #2) cx25840 4-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #2) cx25840 4-0044: loaded v4l-cx25840.fw firmware (16382 bytes) wm8775 4-001b: chip found @ 0x36 (ivtv i2c driver #2) tveeprom 4-0050: Hauppauge model 23559, rev D591, serial# 8201932 tveeprom 4-0050: tuner model is Philips FQ1216AME MK4 (idx 91, type 56) tveeprom 4-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K) (eeprom 0x74) tveeprom 4-0050: second tuner model is Philips TEA5768HL FM Radio (idx 101, type 62) tveeprom 4-0050: audio processor is CX25843 (idx 37) tveeprom 4-0050: decoder processor is CX25843 (idx 30) tveeprom 4-0050: has radio, has no IR remote ivtv2: Correcting tveeprom data: no radio present on second unit ivtv2: Autodetected WinTV PVR 500 (unit #2) ivtv2: Encoder revision: 0x02060039 ivtv2 warning: Encoder Firmware can be buggy, use version 0x02040011, 0x02040024 or 0x02050032. ivtv2: Registered device video2 for encoder MPEG ivtv2: Registered device video34 for encoder YUV ivtv2: Registered device vbi2 for encoder VBI ivtv2: Registered device video26 for encoder PCM audio tuner 4-0061: type set to 56 (Philips PAL/SECAM multi (FQ1216AME MK4)) ivtv2: Initialized WinTV PVR 500 (unit #2), card #2 ivtv: ==================== END INIT IVTV ==================== ivtv0-osd: Framebuffer module loaded (attached to ivtv card id 0) ivtv0-osd: screen coords: [0 0] -> [720 576] ivtv0-osd: original global alpha = 208 ivtv0-osd: current OSD state = 39 ivtv0-osd: new global alpha = 208 (1 255 0) ivtv0-osd: framebuffer at 0xed510000, mapped to 0xe1010000, size 1665k ivtv0-osd: mode is 720x576x32, linelength=2880 ivtv0-osd warning: ivtvfb_set_par Console: switching to colour frame buffer device 90x36 ivtv0-osd: fb0: cx23415 TV out frame buffer device ----- Original Message ----- From: "Marcel Janssen" <[EMAIL PROTECTED]> To: "john bray" <[EMAIL PROTECTED]> Cc: "atrpms-user list" <[email protected]> Sent: Thursday, 29. March 2007 19:59 Subject: Re: [ATrpms-users] Latest IVTV > On Thursday 29 March 2007, john bray wrote: >> ivtv has been crashing my box for months now. i had a period in >> february when it worked fine, but it's back to crashing frequently now. >> >> i've tried to collect information on it for a good while, but the kernel >> seldom puts out any information before the crash. i have a feeling that >> ivtv is scribbling over kernel data and it doesn't show up for a while. >> so far, i haven't been able to collect any information to give the ivtv >> developers. >> >> there are some indications on the ivtv site that it's related to udev. >> but there appear to be no real workarounds available at this point. >> >> the crashes will trash your databases pretty frequently. i've been >> using zmanda to back them up multiple times a day. i've had quite good >> luck with restoring from the backups. beware of all the other things >> that ivtv crashing your box can cause. i'm doing rsync to another box >> all the time now just to have a copy of stuff that ivtv trashes. >> >> frankly, i'm about of the opinion that ivtv is close to hopeless. yah, >> i'm just extremely discouraged with the whole situation. > > I've had a a lot of trouble with IVTV using FC5 and FC6 when it just came out > mostly related to udev, but this trouble has completely vanished a few months > ago. I also haven't experienced any crashes after that until this week, but > it's just a one time occurrence so far, so I don't worry that much about it > yet. > > The issues I previously had seemed also related to my mainboard (VIA > chipset), > but don't have any details about this. > > At my place IVTV runs quite stable again (the old 0.3 series also worked very > stable here) and I'm quite happy with it. Perhaps the issues you have are > related to a combination of the mainboard and IVTV as well. This does seem > very hard to find out though, but perhaps you get more insight if you find > other users who use the same combination (or just using the same > chipsets/drivers). > > Do crashes only occur when switching to live TV and/or change channels ? > My experience is that IVTV never crashes once it is running, just when > changing channels or starting live TV. > > regards, > Marcel > > > > > _______________________________________________ > atrpms-users mailing list > [email protected] > http://lists.atrpms.net/mailman/listinfo/atrpms-users _______________________________________________ atrpms-users mailing list [email protected] http://lists.atrpms.net/mailman/listinfo/atrpms-users
