LinHES Forums
http://forum.linhes.org/

Soooo close, I have snow and no signal
http://forum.linhes.org/viewtopic.php?f=2&t=11079
Page 1 of 3

Author:  roontoon [ Sat Aug 05, 2006 8:39 am ]
Post subject:  Soooo close, I have snow and no signal

I am soooo close to being done I can taste it. I have all my hardware installed and have install Knoppmyth from CD. I went through the setup and "think" I did it correctly. When I go to watch TV I get snow which the program dutyfully records as it were live TV. I do have a channel line up and can change channels as per the program guide but I am seeing snow on every channel.

In my settings I have

Capture Cards:
Tuner 1 is Video Device /dev/video0
Tuner 2 is Video Device /dev/video1

Input Connections:

I have both tuners set for DataDirect as the video source starting at channel 2

I have also looked at http://www.knoppmythwiki.org/index.php? ... WatchingTV and I am not sure if this is the right place for my issue.

Thanks AGAIN for all your help.

d

Author:  tjc [ Sat Aug 05, 2006 9:35 am ]
Post subject: 

That is indeed the correct troubleshooting page to be looking at. Go back and go through all the diagnostic procedures there. Check the logs to make sure that the drivers recognize your tuner and don't think it's "type 4". Make sure that you've only got the "Video Source" associated with the real inputs (tuner 0). Try the other frequency sets. ...

BTW - There's a good chance that with the current versions of that card you will need to upgrade your ivtv drivers. All the info you need to decide this and do it are linked from that page.

You may also want to see this page for basic issues like "Is everything connected correctly?" http://www.knoppmythwiki.org/index.php? ... lityIssues

Author:  roontoon [ Sat Aug 05, 2006 11:27 am ]
Post subject: 

tjc wrote:
That is indeed the correct troubleshooting page to be looking at.


Thanks TJC... but I now have a bigger problem. My motherboard is now not posting and I will have to return it. When I get reassembled I will work on your suggestions..... Close but no cigar.


Thanks

d

Author:  tjc [ Sat Aug 05, 2006 11:34 am ]
Post subject: 

- Did you try the BIOS reset jumper?

- How about stripping out or disconnecting as much hardware as possible?

- Also look at the tips on the AssemblingTheBox page on the wiki.

Author:  roontoon [ Sat Aug 05, 2006 1:24 pm ]
Post subject: 

tjc wrote:
- Did you try the BIOS reset jumper?

- How about stripping out or disconnecting as much hardware as possible?

- Also look at the tips on the AssemblingTheBox page on the wiki.


Stripped it down to RAM and the processer and it will not post. Oh well.. :-(

d

Author:  tjc [ Sat Aug 05, 2006 1:45 pm ]
Post subject: 

Did you follow the first aid procedure for choking on conductive crumbs? That has saved me on a number of occasions. Most recently when it brought my SN41G2 back to life by dislodging a flake of aluminum that was apparently stuck in it's DIMM sockets.

Author:  roontoon [ Sat Aug 05, 2006 3:21 pm ]
Post subject: 

tjc wrote:
Did you follow the first aid procedure for choking on conductive crumbs? That has saved me on a number of occasions. Most recently when it brought my SN41G2 back to life by dislodging a flake of aluminum that was apparently stuck in it's DIMM sockets.


I did read about this on the wiki before I started but for good measure I checked the board and blew it off with air and it is still a door stop. Already have one on the way to replace it. Thanks

d

Author:  roontoon [ Wed Aug 09, 2006 5:51 pm ]
Post subject: 

tjc wrote:
BTW - There's a good chance that with the current versions of that card you will need to upgrade your ivtv drivers. All the info you need to decide this and do it are linked from that page.


Well I am back at it with a new motherboard that will now post and I found that my driver does need to be updated. I started going thought the instructions at http://www.knoppmythwiki.org/index.php?page=CompileIvtv but I have run into a snag on step 4. I am a little confused as to what the exact command is.

Is it:

for module in cx25840/cx25840.ko saa7127.ko tda9887.ko tuner.ko tveeprom.ko ; do mv $module $module.orig done



as one big command or what... I keep getting errors refering me to help. Being a Lunix newbie I don't want to screw this up.

Thanks again for any help

d

Author:  tjc [ Wed Aug 09, 2006 6:34 pm ]
Post subject: 

roontoon wrote:
for module in cx25840/cx25840.ko saa7127.ko tda9887.ko tuner.ko tveeprom.ko ; do mv $module $module.orig done

as one big command or what...

If you do it as one big comand you need to add another semicolon to seperate the statements.
Quote:
for module in cx25840/cx25840.ko saa7127.ko tda9887.ko tuner.ko tveeprom.ko ; do mv $module $module.orig ; done

Author:  roontoon [ Thu Aug 10, 2006 4:04 pm ]
Post subject:  OK now I am frustrated....

I just finished up the driver update as suggested and when I go to watch TV the screen flashes and then returns directly to the menus. No snow no nothing. I am not quite sure where to go from here.

d

Author:  cesman [ Thu Aug 10, 2006 5:40 pm ]
Post subject: 

Check your backend log... Read the troubleshooting info on the wiki...

Author:  roontoon [ Thu Aug 10, 2006 5:55 pm ]
Post subject:  A little closer...

Since I last posted I have been messing with the box and I am not sure what I did but I have a poor quality picture now. I quit the front end stoped the backend and opened up setup again. Only this time I scanned for channels which it rattled off. I did that for each tuner and now I have a picture at least. I have checked the cable connections and as far as I know I don't have any splitters. I am checking out http://www.knoppmythwiki.org/index.php? ... lityIssues but other than that I am driving in the dark as I am not sure what I am doing.

Thanks for any push in the correct direction.

Thanks

d

Author:  roontoon [ Thu Aug 10, 2006 6:20 pm ]
Post subject:  A little more info

I have gone into utilities and adjusted recording profiles a little as suggested in the Wiki. I still am getting very poor quality. The picture looks like it is not very crisp and it has diagonal hash marks or lines. Also the picture will from time to time jump. I am currently viewing from a computer monitor would that have anything to do with the quality? BTW in my last post I thought I posted a copy of the ivtv logs but the seem not to be there now.

TIA

d

Author:  roontoon [ Thu Aug 10, 2006 7:08 pm ]
Post subject:  got the logs

I looked at the logs and it looks like the driver update woked OK as far as I know. Still looking for other issues but have not found any.

d



Aug 10 17:04:54 mythtv kernel: ivtv: ==================== START INIT IVTV ====================
Aug 10 17:04:54 mythtv kernel: ivtv: version 0.4.6 (tagged release) loading
Aug 10 17:04:54 mythtv kernel: ivtv: Linux version: 2.6.15-chw-2 SMP preempt 586 gcc-3.3
Aug 10 17:04:54 mythtv kernel: ivtv: In case of problems please include the debug info between
Aug 10 17:04:54 mythtv kernel: ivtv: the START INIT IVTV and END INIT IVTV lines, along with
Aug 10 17:04:54 mythtv kernel: ivtv: any module options, when mailing the ivtv-users mailinglist.
Aug 10 17:04:54 mythtv kernel: ivtv0: Autodetected WinTV PVR 150 card (cx23416 based)
Aug 10 17:04:54 mythtv kernel: ACPI: PCI Interrupt 0000:02:08.0[A] -> GSI 18 (level, low) -> IRQ 22
Aug 10 17:04:54 mythtv kernel: ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
Aug 10 17:04:54 mythtv kernel: tveeprom: Second (radio) tuner idx 101
Aug 10 17:04:54 mythtv kernel: tveeprom: ivtv version
Aug 10 17:04:54 mythtv kernel: tveeprom: Hauppauge: model = 23552, rev = D487, serial# = 9525414
Aug 10 17:04:54 mythtv kernel: tveeprom: tuner = Samsung TCPN 2221P30A (idx = 87, type = 68)
Aug 10 17:04:54 mythtv kernel: tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
Aug 10 17:04:54 mythtv kernel: tveeprom: audio processor = CX25843 (type = 25)
Aug 10 17:04:54 mythtv kernel: tveeprom: decoder processor = CX25843 (type = 1e)
Aug 10 17:04:54 mythtv kernel: ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
Aug 10 17:04:54 mythtv kernel: tuner (ivtv): chip found at addr 0xc0 i2c-bus ivtv i2c driver #0
Aug 10 17:04:54 mythtv kernel: TEA5767 detected.
Aug 10 17:04:54 mythtv kernel: ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=60]
Aug 10 17:04:54 mythtv kernel: tuner: type set to 62 (Philips TEA5767HN FM Radio) by autodetect
Aug 10 17:04:54 mythtv kernel: type set to 62 (Philips TEA5767HN FM Radio)
Aug 10 17:04:54 mythtv kernel: tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
Aug 10 17:04:54 mythtv kernel: ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
Aug 10 17:04:55 mythtv kernel: cx25840 0-0044: ivtv driver
Aug 10 17:04:55 mythtv kernel: cx25840 0-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
Aug 10 17:04:58 mythtv kernel: cx25840 0-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
Aug 10 17:04:58 mythtv kernel: ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44]
Aug 10 17:04:58 mythtv kernel: wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0)
Aug 10 17:04:58 mythtv kernel: ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b]
Aug 10 17:04:58 mythtv kernel: ivtv0: This is the first unit of a PVR500
Aug 10 17:04:58 mythtv kernel: ivtv0: Detected a TEA5767 radio tuner. Enabling radio support.
Aug 10 17:04:59 mythtv kernel: ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
Aug 10 17:05:00 mythtv kernel: ivtv0: Encoder revision: 0x02050032
Aug 10 17:05:00 mythtv kernel: ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
Aug 10 17:05:00 mythtv kernel: ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
Aug 10 17:05:00 mythtv kernel: ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
Aug 10 17:05:00 mythtv kernel: ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
Aug 10 17:05:00 mythtv kernel: ivtv0: Create encoder radio stream
Aug 10 17:05:00 mythtv kernel: tuner: type set to 68 (Samsung TCPN 2221P30A) by ivtv i2c driver #0
Aug 10 17:05:00 mythtv kernel: ivtv0: Initialized WinTV PVR 500 (unit #1), card #0
Aug 10 17:05:00 mythtv kernel: ivtv: ====================== NEXT CARD ======================
Aug 10 17:05:00 mythtv kernel: ivtv1: Autodetected WinTV PVR 150 card (cx23416 based)
Aug 10 17:05:00 mythtv kernel: ACPI: PCI Interrupt 0000:02:09.0[A] -> GSI 19 (level, low) -> IRQ 21
Aug 10 17:05:00 mythtv kernel: ivtv1: Unreasonably low latency timer, setting to 64 (was 32)
Aug 10 17:05:00 mythtv kernel: tveeprom: Second (radio) tuner idx 101
Aug 10 17:05:00 mythtv kernel: tveeprom: ivtv version
Aug 10 17:05:00 mythtv kernel: tveeprom: Hauppauge: model = 23552, rev = D487, serial# = 9525414
Aug 10 17:05:00 mythtv kernel: tveeprom: tuner = Samsung TCPN 2221P30A (idx = 87, type = 68)
Aug 10 17:05:00 mythtv kernel: tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
Aug 10 17:05:00 mythtv kernel: tveeprom: audio processor = CX25843 (type = 25)
Aug 10 17:05:00 mythtv kernel: tveeprom: decoder processor = CX25843 (type = 1e)
Aug 10 17:05:00 mythtv kernel: ivtv1: i2c attach to card #1 ok [client=tveeprom, addr=50]
Aug 10 17:05:00 mythtv kernel: tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #1
Aug 10 17:05:00 mythtv kernel: ivtv1: i2c attach to card #1 ok [client=(tuner unset), addr=61]
Aug 10 17:05:00 mythtv kernel: cx25840 1-0044: ivtv driver
Aug 10 17:05:00 mythtv kernel: cx25840 1-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1)
Aug 10 17:05:03 mythtv kernel: cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
Aug 10 17:05:04 mythtv kernel: ivtv1: i2c attach to card #1 ok [client=cx25840, addr=44]
Aug 10 17:05:04 mythtv kernel: wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #1)
Aug 10 17:05:04 mythtv kernel: ivtv1: i2c attach to card #1 ok [client=wm8775, addr=1b]
Aug 10 17:05:04 mythtv kernel: ivtv1: This is the second unit of a PVR500
Aug 10 17:05:04 mythtv kernel: ivtv1: Correcting tveeprom data: no radio present on second unit
Aug 10 17:05:04 mythtv kernel: ivtv1: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
Aug 10 17:05:05 mythtv kernel: ivtv1: Encoder revision: 0x02050032
Aug 10 17:05:05 mythtv kernel: ivtv1: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
Aug 10 17:05:05 mythtv kernel: ivtv1: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
Aug 10 17:05:05 mythtv kernel: ivtv1: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
Aug 10 17:05:05 mythtv kernel: ivtv1: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
Aug 10 17:05:05 mythtv kernel: tuner: type set to 68 (Samsung TCPN 2221P30A) by ivtv i2c driver #1
Aug 10 17:05:05 mythtv kernel: ivtv1: Initialized WinTV PVR 500 (unit #2), card #1
Aug 10 17:05:05 mythtv kernel: ivtv: ==================== END INIT IVTV ====================

Author:  tjc [ Thu Aug 10, 2006 7:12 pm ]
Post subject: 

If you're in the US and thus can get your guide info from zap2it, scanning for SDTV channels is contra-indicated. It will only cause you grief. You'll eventually have to drop your lineups and recreate them (and the input connections) to correct the problems this causes.

As far as I can see (whoops signature blocks weren't showing from the "post a reply" screen!) you never said what you're using for your video output. It really helps to have an accelerated driver with Xv support builtin. It also helps to match the output resolution (especially the vertical) to the capture resolution. I got a dramatic improvement in quality going from 800x600 output to 640x480. if you're mapping 480x480 (the default capture settings) to 1024x768 you are going to see artifacts that'll just about make your eyes bleed.

Finally enabling deinterlacing can make a significant improvement, the best results I've seen are with Bob 2x.

Page 1 of 3 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/