View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 40 posts ] 
Go to page Previous  1, 2, 3  Next

Print view Previous topic   Next topic  
Author Message
Search for:
 Post subject:
PostPosted: Thu Apr 13, 2006 8:00 pm 
Offline
Joined: Tue Nov 08, 2005 7:31 am
Posts: 195
Location: Secret Lair
This looks like your problem.
Quote:
Apr 12 00:08:28 mythtv kernel: tuner 1-0061: tuner type not set
Apr 12 00:08:28 mythtv kernel: tuner 1-0061: tuner type not set

Someone else recently had a similar issue and they had to set the tuner type in their /etc/mythtv/modules/ivtv something like this:
Code:
options ivtv tuner=50,50


Top
 Profile  
 
 Post subject:
PostPosted: Fri Apr 14, 2006 8:57 am 
Offline
Joined: Thu Mar 30, 2006 3:54 pm
Posts: 14
EvilTwin wrote:
This looks like your problem.
Quote:
Apr 12 00:08:28 mythtv kernel: tuner 1-0061: tuner type not set
Apr 12 00:08:28 mythtv kernel: tuner 1-0061: tuner type not set

Someone else recently had a similar issue and they had to set the tuner type in their /etc/mythtv/modules/ivtv something like this:
Code:
options ivtv tuner=50,50


Well, I just made the changes and rebooted. Unfortunately, I'm at work so I can't give it the full test, but on the bright side I'm no longer getting the
"tuner 1-0061: type not set"

It has been replaced with:
"Apr 14 09:48:33 mythtv kernel: tuner 2-0061: type set to 50 (TCL 2002N)"

I'll report back on the status tonight.
Also, for anyone else with the problem here is the thread mentioned by EvilTwin http://mysettopbox.tv/phpBB2/viewtopic. ... sung+tuner


Top
 Profile  
 
 Post subject:
PostPosted: Fri Apr 14, 2006 10:36 am 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
You may discover in the end that type 50 is not the best choice, but given the basic technique it's easy to experiment.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Apr 14, 2006 11:46 am 
Offline
Joined: Thu Mar 30, 2006 3:54 pm
Posts: 14
Does it vary by individual card or is there a known good number out there? I'm willing to experiment, but I don't want to reinvent the wheel.


Top
 Profile  
 
 Post subject:
PostPosted: Sat Apr 15, 2006 1:41 pm 
Offline
Joined: Thu Mar 30, 2006 3:54 pm
Posts: 14
Great! It works, but as stated 50 probably isn't the best tuner setting. Some channels work others are just static. I'll mess around with the config and post if I ever get it working perfect.

Thanks for all the help!


Top
 Profile  
 
 Post subject:
PostPosted: Sun Apr 16, 2006 1:05 pm 
Offline
Joined: Thu Mar 30, 2006 3:54 pm
Posts: 14
I found an ivtv page that says in version 0.4.4 the Samsung tuner is number 68. So I made the changes and rebooted, but I am still missing channels. I also found that when the tuner is set to type 68 I get these messages in /var/log/messages:
Apr 15 16:13:59 mythtv kernel: tuner 2-000a: i2c i/o error: rc == -121 (should be 2)

There are quite a few of them. I ended up changing it back to type 50 as it doesn't give me any errors. Any ideas or should I be asking in the ivtv mailing list for this?


Top
 Profile  
 
 Post subject:
PostPosted: Sun Apr 16, 2006 8:29 pm 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
Gather all the hardware identification information from the log files and using lspci -vv (Only report on the appropriate multimedia device however) and give them that. The problem is most likley that our friends at Hauppauge have switched to yet another tuner chip which the drivers don't recognize automatically.


Top
 Profile  
 
 Post subject:
PostPosted: Mon Apr 17, 2006 1:26 pm 
Offline
Joined: Mon Sep 27, 2004 1:26 pm
Posts: 16
FWIW, I just bought a PVR150 and my experience is the same as UNOmar's. Let me know if there is something I can help with.


Top
 Profile  
 
 Post subject:
PostPosted: Mon Apr 17, 2006 7:08 pm 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
Looks like this is a reversion on the IVTV fix for carda with tuner "type 4", and the ivtv folks are working on 0.4.5 version of the driver.


Top
 Profile  
 
 Post subject:
PostPosted: Mon Apr 17, 2006 8:47 pm 
Offline
Joined: Tue Mar 21, 2006 2:18 pm
Posts: 6
I am looking for any help that I can get at this point. I have what I have been told is the PVR-500 with Samsung tuners. I have followed the compile ivtv (http://knoppmythwiki.org/index.php?page=CompileIvtv) how to on Knoppmyth Wiki. So I am now running ivtv-0.4.4.

For the life of me, I cannot get my video cards to be detected correctly. I have tried setting the tuners to 50,50. No avail.

Can someone lend me a hand?

AMD x86_64
Knoppmyth version R5B7
Linux version: 2.6.15-chw-2 SMP preempt 586 gcc-3.3
mythbackend version: 0.19.20060121-2
ivtv: version 0.4.4 (tagged release) loading
ivtv0: Autodetected WinTV PVR 150 card (cx23416 based)


End of lspci -v output
Code:
0000:03:08.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01)
        Subsystem: Hauppauge computer works Inc.: Unknown device e807
        Flags: bus master, medium devsel, latency 64, IRQ 21
        Memory at f0000000 (32-bit, prefetchable) [size=64M]
        Capabilities: [44] Power Management version 2

0000:03:09.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01)
        Subsystem: Hauppauge computer works Inc.: Unknown device e817
        Flags: bus master, medium devsel, latency 64, IRQ 20
        Memory at f4000000 (32-bit, prefetchable) [size=64M]
        Capabilities: [44] Power Management version 2



dmesg output

Code:
ivtv:  ==================== START INIT IVTV ====================
ivtv:  version 0.4.4 (tagged release) loading
ivtv:  Linux version: 2.6.15-chw-2 SMP preempt 586 gcc-3.3
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 150 card (cx23416 based)
ACPI: PCI Interrupt 0000:03:08.0[A] -> GSI 17 (level, low) -> IRQ 21
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
tuner 1-0060: TEA5767 detected.
tuner 1-0060: chip found @ 0xc0 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=60]
tuner 1-0060: type set to 62 (Philips TEA5767HN FM Radio)
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
cx25840 1-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
cx25840 1-0044: loaded v4l-cx25840.fw firmware (14264 bytes)
ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44]
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b]
tda9887 1-0043: chip found @ 0x86 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=tda9887, addr=43]
tveeprom 1-0050: Hauppauge model 23552, rev E492, serial# 9308876
tveeprom 1-0050: tuner model is Philips FQ1236A MK4 (idx 92, type 57)
tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 1-0050: second tuner model is Philips TEA5768HL FM Radio (idx 101, type 62)
tveeprom 1-0050: audio processor is CX25843 (idx 37)
tveeprom 1-0050: decoder processor is CX25843 (idx 30)
tveeprom 1-0050: has radio, has no IR remote
ivtv0: This is the first unit of a PVR500
eth0: no IPv6 routers present
ivtv0: Detected a TEA5767 radio tuner. Enabling radio support.
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv0: Encoder revision: 0x02050032
ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
ivtv0: Create encoder radio stream
tuner 1-0061: type set to 50 (TCL 2002N)
ivtv0: Initialized WinTV PVR 500 (unit #1), card #0
ivtv:  ======================  NEXT CARD  ======================
ivtv1: Autodetected WinTV PVR 150 card (cx23416 based)
ACPI: PCI Interrupt 0000:03:09.0[A] -> GSI 18 (level, low) -> IRQ 20
ivtv1: Unreasonably low latency timer, setting to 64 (was 32)
ivtv1: i2c attach to card #1 ok [client=tveeprom, addr=50]
tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #1)
ivtv1: i2c attach to card #1 ok [client=(tuner unset), addr=61]
cx25840 2-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1)
cx25840 2-0044: loaded v4l-cx25840.fw firmware (14264 bytes)
ivtv1: i2c attach to card #1 ok [client=cx25840, addr=44]
wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #1)
ivtv1: i2c attach to card #1 ok [client=wm8775, addr=1b]
tda9887 2-0043: chip found @ 0x86 (ivtv i2c driver #1)
ivtv1: i2c attach to card #1 ok [client=tda9887, addr=43]
tveeprom 2-0050: Hauppauge model 23552, rev E492, serial# 9308876
tveeprom 2-0050: tuner model is Philips FQ1236A MK4 (idx 92, type 57)
tveeprom 2-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 2-0050: second tuner model is Philips TEA5768HL FM Radio (idx 101, type 62)
tveeprom 2-0050: audio processor is CX25843 (idx 37)
tveeprom 2-0050: decoder processor is CX25843 (idx 30)
tveeprom 2-0050: has radio, has no IR remote
ivtv1: This is the second unit of a PVR500
ivtv1: Correcting tveeprom data: no radio present on second unit
ivtv1: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv1: Encoder revision: 0x02050032
ivtv1: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv1: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
ivtv1: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
ivtv1: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
tuner 2-0061: type set to 50 (TCL 2002N)
ivtv1: Initialized WinTV PVR 500 (unit #2), card #1
ivtv:  ====================  END INIT IVTV  ====================
cx2388x v4l2 driver version 0.0.5 loaded



Code:
root@mythbox:/var/log/mythtv# mythbackend -v debug-level
Unknown argument for -v/--verbose: debug-level
2006-04-17 19:40:13.767 Using runtime prefix = /usr
2006-04-17 19:40:13.778 New DB connection, total: 1
2006-04-17 19:40:13.780 Connected to database 'mythconverg' at host: localhost
2006-04-17 19:40:13.782 Current Schema Version: 1123
Starting up as the master server.
2006-04-17 19:40:13.787 mythbackend: MythBackend started as master server
2006-04-17 19:40:13.791 New DB connection, total: 2
2006-04-17 19:40:13.792 Connected to database 'mythconverg' at host: localhost
2006-04-17 19:40:14.104 New DB connection, total: 3
2006-04-17 19:40:14.105 Connected to database 'mythconverg' at host: localhost
2006-04-17 19:40:14.253 New DB scheduler connection
2006-04-17 19:40:14.253 Connected to database 'mythconverg' at host: localhost
2006-04-17 19:40:14.256 mythbackend version: 0.19.20060121-2 www.mythtv.org
2006-04-17 19:40:14.257 Enabled verbose msgs:  important general
2006-04-17 19:40:14.257 AutoExpire: Found 1 recorders w/max rate of 72 MiB/min
2006-04-17 19:40:14.258 AutoExpire: Required Free Space: 2.1 GB w/freq: 10 min
2006-04-17 19:40:16.258 Reschedule requested for id -1.
2006-04-17 19:40:16.551 Scheduled 0 items in 0.3 = 0.29 match + 0.00 place
2006-04-17 19:40:16.551 scheduler: Scheduled items
2006-04-17 19:40:16.553 Seem to be woken up by USER
2006-04-17 19:40:23.798 Running HouseKeeping
2006-04-17 19:40:23.799 mythbackend: Running housekeeping thread
2006-04-17 19:40:54.752 MainServer::HandleAnnounce Monitor
2006-04-17 19:40:54.752 adding: mythbox as a client (events: 0)
2006-04-17 19:40:54.767 MainServer::HandleAnnounce Monitor
2006-04-17 19:40:54.767 adding: mythbox as a client (events: 1)
2006-04-17 19:40:54.779 MainServer::HandleAnnounce Playback
2006-04-17 19:40:54.779 adding: mythbox as a client (events: 0)


At this point I selected Watch TV from the front end. I see the invalid argument, but I would think it's an artifact of the inputs being fouled.

Code:
2006-04-17 19:40:54.786 TVRec(1): Changing from None to WatchingLiveTV
2006-04-17 19:40:55.030 Can't enable VBI recording (2)
vbi: Invalid argument
select timeout - ivtv driver has stopped responding
2006-04-17 19:41:01.534 TVRec(1): Changing from WatchingLiveTV to None
select timeout - ivtv driver has stopped responding
2006-04-17 19:41:08.809 Finished recording Pay-Per-View Previews: channel 1100
2006-04-17 19:41:08.809 scheduler: Finished recording


Top
 Profile  
 
PostPosted: Mon Apr 17, 2006 9:10 pm 
Offline
Joined: Thu Feb 16, 2006 8:51 pm
Posts: 2
I've been running a KnoppMyth box for several months, now. Started off with just a WinTV PVR-350. Worked great.

Then the problems started. I bought a WinTV PVR-500 (yes, the Samsung tuner chip one) and after upgrading to R5A30 those tuners wouldn't work. Came to find out that no IVTV tuner support was available for the Samsung tuner (but we all know that already, don't we?). After using the wrong tuner settings and generating a ton of errors, IVTV was kind enough to come out with a fix. Patched the R5A30 KnoppMyth with IVTV 0.4.2 and all tuners worked great for two or three months!

Then I did something stupid. I messed with a good thing. I wanted the KnoppMyth built-in MythBurn support and better tuner definition released with IVTV 0.4.3. So I decided to upgrade to R5B7, with 0.4.4. Everything went smoothly until the IVTV tuner recognition part in the log. Once again, the Samsung tuner chips would not be recognized. Tried several versions of the IVTV drivers, but no luck. Ended up rolling it all back to R5A30 and reinstalling the IVTV 0.4.3 driver. I had to manually clean up the databases a bit, but everything is working smoothly again. All tuners recognized and no errors.

My advice to those of you out there with a WinTV PVR-500 with the Samsung tuner chips: use KnoppMyth R5A30 with the IVTV 0.4.3 patched. Don't even try R5B7 until the new IVTV drivers come out. I think something got lost in the upgrade. The tuners will be autodetected correctly, no manual configuration required.

When I get brave enough to try it, I'll let you know. My wife almost killed me last time I disabled the PVR when she didn't get he West Wing (grin). Still, it says something that it's stable enough that we now depend on the PVR instead of the VCR, don't it?


Top
 Profile  
 
 Post subject:
PostPosted: Mon Apr 17, 2006 9:38 pm 
Offline
Joined: Tue Mar 21, 2006 2:18 pm
Posts: 6
I am now removing my fist from my TV and getting the burner warmed up for a R5A30 iso.

My goodness, you can't possibly imagine how I've been beating my head over this one.

I will be sure to report back on this one. I'll ping the Knoppmyth guys on it too.

Thanks so much! Can you tell I'm excited just to hear that there might be an explination?

Let's just say this little exercise started with Gentoo and Mythtv .18 and morphed because I could not get any of this to work. For what appear to be different reasons at this point.

TonyC


Top
 Profile  
 
 Post subject:
PostPosted: Tue Apr 18, 2006 12:56 pm 
Offline
Joined: Tue Mar 21, 2006 2:18 pm
Posts: 6
I've now rolled back to R5A30, and ivtv-0.4.4 on AMD 64.

I read the instructions as I needed to updated the firmware due to name changes with ivtv-0.4.4 driver. Fine, so I did.

Depending on my Capture card definitions, I am now seeing a frozen image, or static that after a few seconds locks the systems up. I've found that if I really mess up on the capture card definition, I can actually crash the system when I select Watch TV.

Is there a document that explains the correct mapping of Capture Card > DataDirect > Input mapping? I believe I've done it correctly, but obviously an incorrect mapping is problematic. For example, the default input for a PVR card. Should it be Tuner, or should it be mapped to the actual connection (ie. - S-Video)?

For example, I've tried to define two capture cards like...
PVR-x50
Device: /dev/video0
Default: Tuner 0

Should the Default be Tuner 0 always, or should it be S-Video 0 if I'm connected using that method. What does default mean if I've got to assign a Source to a Connection later in the setup?

TonyC


Top
 Profile  
 
 Post subject:
PostPosted: Tue Apr 18, 2006 5:55 pm 
Offline
Joined: Thu Feb 16, 2006 8:51 pm
Posts: 2
Actually, I haven't tried ivtv 0.4.4 yet. That may be part of your problem. I've only installed up to ivtv 0.4.3, and I know that works.

As far as the capture card definitions and mapping, here's the web page I used as a guide:

http://www.knoppmythwiki.org/index.php? ... 0DualTuner

With the newer drivers, it will no longer detect as Tuner 0 and Tuner 1, I believe. I think they both detect as just Tuner, so there isn't any Tuner number. I'll check on that one. And the first one should be /dev/video0 and the second /dev/video1. As far as the SVideo, are you using SVideo as an input source? Or just as an output? If you've got cable, no SVideo stuff should be set up in the sources.

Let me know if this helps....


Top
 Profile  
 
 Post subject:
PostPosted: Tue Apr 18, 2006 8:16 pm 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
Toneus wrote:
For the life of me, I cannot get my video cards to be detected correctly. I have tried setting the tuners to 50,50. No avail.

Well given this:
Quote:
tveeprom 1-0050: tuner model is Philips FQ1236A MK4 (idx 92, type 57)

I think you should be trying type 57 rather than type 50.

Are you sure that you've got the right frequency set selected in mythtv-setup? See:
http://www.knoppmythwiki.org/index.php?page=BlackScreenWatchingTV

Oh and VBI isn't supported on the PVR-150 or PVR-500 cards, don't try to force it on. if it isn't disabled automatically turn it off yourself.


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 40 posts ] 
Go to page Previous  1, 2, 3  Next



All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu