TV card problem, but great Feisty

I did a network install yesterday of Ubuntu Feisty Fawn Herd 5 on my meant to be TV-computer. I have earlier struggled with getting a good picture with my Hauppauge PVR 500MCE. A few weeks ago I noted that Feisty will have full support for the TV-card, including firmware.

Today it was time to try it out. It worked out of the box, I did noting extra. Brilliant!! But, a big BUT ... there is still a bad picture. If I amplify the signal, it get worse. If I reduce the signal then it, also, get worse. It looks like there are two problems; noise and not fully correct tuned signal. So on the picture quality view nothing had been better since last time. Does anyone have any ideas? I start to believe that I have a hardware problem, maybe it is time to buy another card.

The new feature within Feisty that suggests what application or decoder you need to show a file works great. This feature will simplify for a lot of users.

By the way, here is a dump of my dmesg output. Everything looks good, from my point of view.
[ 26.060000] ivtv: ==================== START INIT IVTV ====================
[ 26.060000] ivtv: version 0.9.1 (tagged release) loading
[ 26.060000] ivtv: Linux version: 2.6.20-9-generic SMP mod_unload 586
[ 26.060000] ivtv: In case of problems please include the debug info between
[ 26.060000] ivtv: the START INIT IVTV and END INIT IVTV lines, along with
[ 26.060000] ivtv: any module options, when mailing the ivtv-users mailinglist.
[ 26.060000] ivtv0: Autodetected Hauppauge card (cx23416 based)
[ 26.060000] ACPI: PCI Interrupt 0000:02:08.0[A] -> Link [LNKB] -> GSI 12 (level, low) -> IRQ 12
[ 26.060000] ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
[ 26.112000] input: PC Speaker as /class/input/input3
[ 26.216000] irda_init()
[ 26.216000] NET: Registered protocol family 23
[ 26.252000] Floppy drive(s): fd0 is 1.44M
[ 26.272000] FDC 0 is a post-1991 82077
[ 27.592000] ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
[ 27.792000] **WARNING** I2C adapter driver [ivtv i2c driver #0] forgot to specify physical device; fix it!
[ 27.876000] tveeprom 1-0050: Hauppauge model 23559, rev D591, serial# 8104296
[ 27.876000] tveeprom 1-0050: tuner model is Philips FQ1216AME MK4 (idx 91, type 56)
[ 27.876000] tveeprom 1-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K) (eeprom 0x74)
[ 27.876000] tveeprom 1-0050: second tuner model is Philips TEA5768HL FM Radio (idx 101, type 62)
[ 27.876000] tveeprom 1-0050: audio processor is CX25843 (idx 37)
[ 27.876000] tveeprom 1-0050: decoder processor is CX25843 (idx 30)
[ 27.876000] tveeprom 1-0050: has radio, has no IR receiver, has no IR transmitter
[ 27.876000] ivtv0: Autodetected WinTV PVR 500 (unit #1)
[ 27.920000] tuner 1-0043: chip found @ 0x86 (ivtv i2c driver #0)
[ 27.920000] tda9887 1-0043: tda988[5/6/7] found @ 0x43 (tuner)
[ 27.928000] tuner 1-0060: TEA5767 detected.
[ 27.928000] tuner 1-0060: chip found @ 0xc0 (ivtv i2c driver #0)
[ 27.928000] tuner 1-0060: type set to 62 (Philips TEA5767HN FM Radio)
[ 27.928000] tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
[ 27.988000] cx25840 1-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
[ 33.104000] cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
[ 33.264000] wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
[ 33.352000] ivtv0: Encoder revision: 0x02050032
[ 33.352000] ivtv0: Registered device video0 for encoder MPEG
[ 33.352000] ivtv0: Registered device video32 for encoder YUV
[ 33.352000] ivtv0: Registered device vbi0 for encoder VBI
[ 33.352000] ivtv0: Registered device video24 for encoder PCM audio
[ 33.356000] ivtv0: Registered device radio0 for encoder radio
[ 33.356000] tuner 1-0061: type set to 56 (Philips PAL/SECAM multi (FQ1216AME MK4))
[ 33.744000] ivtv0: Initialized WinTV PVR 500 (unit #1), card #0
[ 33.744000] ivtv: ====================== NEXT CARD ======================
[ 33.744000] ivtv1: Autodetected Hauppauge card (cx23416 based)
[ 33.744000] ACPI: PCI Interrupt 0000:02:09.0[A] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
[ 33.744000] ivtv1: Unreasonably low latency timer, setting to 64 (was 32)
[ 34.424000] ivtv1: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
[ 34.624000] **WARNING** I2C adapter driver [ivtv i2c driver #1] forgot to specify physical device; fix it!
[ 34.632000] tuner 2-0043: chip found @ 0x86 (ivtv i2c driver #1)
[ 34.632000] tda9887 2-0043: tda988[5/6/7] found @ 0x43 (tuner)
[ 34.636000] tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #1)
[ 34.664000] cx25840 2-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1)
[ 39.764000] cx25840 2-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
[ 39.876000] wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #1)
[ 39.980000] tveeprom 2-0050: Hauppauge model 23559, rev D591, serial# 8104296
[ 39.980000] tveeprom 2-0050: tuner model is Philips FQ1216AME MK4 (idx 91, type 56)
[ 39.980000] tveeprom 2-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K) (eeprom 0x74)
[ 39.980000] tveeprom 2-0050: second tuner model is Philips TEA5768HL FM Radio (idx 101, type 62)
[ 39.980000] tveeprom 2-0050: audio processor is CX25843 (idx 37)
[ 39.980000] tveeprom 2-0050: decoder processor is CX25843 (idx 30)
[ 39.980000] tveeprom 2-0050: has radio, has no IR receiver, has no IR transmitter
[ 39.980000] ivtv1: Correcting tveeprom data: no radio present on second unit
[ 39.980000] ivtv1: Autodetected WinTV PVR 500 (unit #2)
[ 40.128000] ivtv1: Encoder revision: 0x02050032
[ 40.128000] ivtv1: Registered device video1 for encoder MPEG
[ 40.128000] ivtv1: Registered device video33 for encoder YUV
[ 40.128000] ivtv1: Registered device vbi1 for encoder VBI
[ 40.128000] ivtv1: Registered device video25 for encoder PCM audio
[ 40.132000] tuner 2-0061: type set to 56 (Philips PAL/SECAM multi (FQ1216AME MK4))
[ 40.516000] ivtv1: Initialized WinTV PVR 500 (unit #2), card #1
[ 40.520000] ACPI: PCI Interrupt 0000:00:11.5[C] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
[ 40.520000] PCI: Setting latency timer of device 0000:00:11.5 to 64
[ 40.524000] ivtv: ==================== END INIT IVTV ====================

Comments

Post a Comment

Popular posts from this blog

Circles in PostGIS

Image
OGC and PostGIS has no data type to represent a circle. Instead one use ST_Buffer(geom, distance) to get a geometry that covers the area within the distance to geom . So if geom is a point you get a circle. But it does not return an exact circle. The circle is approximated represented by a polygon using eight points. One can increase the precission by adding a third argument to ST_buffer that is the number of points in the polygon returned. The unit for distance depends on what SRID is used. But what if you have a geometry that you know is a circle created with the method above? There is no exact method as far as I know, but her comes a good approximation. First we want the origo of the circle. ST_Centroid(geom) comes to handy. It returns the centeroid point of the geometry, in this case the origo of the circle. To get the radius we pick out the first point in the polygon returned by ST_Buffer with PointN(ExteriorRing(geom),1) . We need to call ExteriorRing to get the polygon of...
Read more

Create your own CA with TinyCA2 (part 1)

Image
A Certificate Authorities (CA) issues certificates to people and organization that gives us the possibility to know that we surf to the right web site and not a phising site. This concept can be nice to use on your private sites too, but you may not want to spend a lot of money to get a certificate for your site. Most common when one installs a web-mail server at home is using a self signed certificate. When one surf to the web-mail server from a friends computer one can not be sure that nobody listens to the traffic if one not verifies the signature of the self signed certificate. Maybe an easier and definitely a more scalable solution to this is to create ones own CA structure. When we are ready with this how to you will have installed a certificate on your web server, installed the root certificate into your Firefox, and you will have the root certificate stored on a USB-memory stick. First time you want to read your mail from a friends computer you install the root certificate f...
Read more

Create your own CA with TinyCA2 (part 2)

Image
In part one of this series we created a root CA, a sub-CA and a certificate for our web site All certificates are stored in TinyCA2 s configuration. In this part we will: export the root CA:s certificate import the root CA:s certificate into Firefox export the certificate for the web site configure our web server to use the web site certificate To be able to import the root CA certificate to Firefox we must export it from TinyCA2. In the main window of TinyCA2, open the CA-menu and select Open CA. Select your root CA. Select Export CA Certificate in the toolbar, which is the second icon from the right. You may change the file name. Press Save when ready. Start Firefox, select the Edit-menu and Preferences. Click the Advanced icon and then the Encryption tab. Select View certificates and then the Authorities tab. You can see all the CA:s you trust. Click Import and select the file with your exported root certificate. You can in the Downloading Certificate window control what purpo...
Read more