public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
* tuner type
@ 2009-10-15 20:16 Michael Grützmann
  2009-10-15 22:40 ` Michael Krufky
  2009-10-15 23:06 ` hermann pitton
  0 siblings, 2 replies; 4+ messages in thread
From: Michael Grützmann @ 2009-10-15 20:16 UTC (permalink / raw)
  To: video4linux-list

Dear to all,

I have an Medion 7134 card, so I use the saa7134 module with a 2.6.25 kernel (card=12). But I have a question. Which tuner type should I use? 
 cat /var/log/boot.msg |grep saa
<6>saa7130/34: v4l2 driver version 0.2.14 loaded
<6>saa7134[0]: found at 0000:00:0b.0, rev: 1, irq: 18, latency: 32, mmio: 0xdffffc00
<6>saa7134[0]: subsystem: 16be:0003, board: Medion 7134 [card=12,autodetected]
<6>saa7134[0]: board init: gpio is 0
<6>saa7134[0]: i2c eeprom 00: be 16 03 00 08 20 1c 55 43 43 a9 1c 55 43 43 a9
<6>saa7134[0]: i2c eeprom 10: ff ff ff ff 15 00 0e 01 0c c0 08 00 00 00 00 00
<6>saa7134[0]: i2c eeprom 20: 00 00 00 e3 ff ff ff ff ff ff ff ff ff ff ff ff
<6>saa7134[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
<6>saa7134[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
<6>saa7134[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
<6>saa7134[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
<6>saa7134[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
<6>saa7134[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
<6>saa7134[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
<6>saa7134[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
<6>saa7134[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
<6>saa7134[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
<6>saa7134[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
<6>saa7134[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
<6>saa7134[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
<6>tuner' 2-0043: chip found @ 0x86 (saa7134[0])
<6>tuner' 2-0060: chip found @ 0xc0 (saa7134[0])
<6>saa7134[0] Tuner type is 38
<6>saa7134[0]: registered device video0 [v4l2]
<6>saa7134[0]: registered device vbi0
<6>saa7134[0]: registered device radio0
<3>saa7134[0]/dvb: frontend initialization failed
It is not tuner=38. 
On the card, there stands: 'tuner philips 3139 147 18201H#'.
There are two Ambient chips on it. One chip ctis0tp. If needed, I can write to you the full chip labelings. 
Your help would be appreciated.
ps. I'm a linux newbie (use it for 2 years). Maybe you could also tell me how to write the changes made manually to modules.d, so the changes aren't lost when rebooting.

Thanks in advance,
Dirk
______________________________________________________
GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://movieflat.web.de


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: tuner type
  2009-10-15 20:16 tuner type Michael Grützmann
@ 2009-10-15 22:40 ` Michael Krufky
  2009-10-15 23:06 ` hermann pitton
  1 sibling, 0 replies; 4+ messages in thread
From: Michael Krufky @ 2009-10-15 22:40 UTC (permalink / raw)
  To: Michael Grützmann; +Cc: video4linux-list

On Thu, Oct 15, 2009 at 4:16 PM, Michael Grützmann <Avalone@web.de> wrote:
> Dear to all,
>
> I have an Medion 7134 card, so I use the saa7134 module with a 2.6.25 kernel (card=12). But I have a question. Which tuner type should I use?
>  cat /var/log/boot.msg |grep saa
> <6>saa7130/34: v4l2 driver version 0.2.14 loaded
> <6>saa7134[0]: found at 0000:00:0b.0, rev: 1, irq: 18, latency: 32, mmio: 0xdffffc00
> <6>saa7134[0]: subsystem: 16be:0003, board: Medion 7134 [card=12,autodetected]
> <6>saa7134[0]: board init: gpio is 0
> <6>saa7134[0]: i2c eeprom 00: be 16 03 00 08 20 1c 55 43 43 a9 1c 55 43 43 a9
> <6>saa7134[0]: i2c eeprom 10: ff ff ff ff 15 00 0e 01 0c c0 08 00 00 00 00 00
> <6>saa7134[0]: i2c eeprom 20: 00 00 00 e3 ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>tuner' 2-0043: chip found @ 0x86 (saa7134[0])
> <6>tuner' 2-0060: chip found @ 0xc0 (saa7134[0])
> <6>saa7134[0] Tuner type is 38
> <6>saa7134[0]: registered device video0 [v4l2]
> <6>saa7134[0]: registered device vbi0
> <6>saa7134[0]: registered device radio0
> <3>saa7134[0]/dvb: frontend initialization failed
> It is not tuner=38.
> On the card, there stands: 'tuner philips 3139 147 18201H#'.
> There are two Ambient chips on it. One chip ctis0tp. If needed, I can write to you the full chip labelings.
> Your help would be appreciated.
> ps. I'm a linux newbie (use it for 2 years). Maybe you could also tell me how to write the changes made manually to modules.d, so the changes aren't lost when rebooting.
>
> Thanks in advance,
> Dirk

Dirk,

The tuner labelled, "3139 147 18201H" should be tuner # 63 - Philips
FMD1216ME MK3 Hybrid Tuner

I hope this helps you.

Regards,

Mike

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: tuner type
  2009-10-15 20:16 tuner type Michael Grützmann
  2009-10-15 22:40 ` Michael Krufky
@ 2009-10-15 23:06 ` hermann pitton
  1 sibling, 0 replies; 4+ messages in thread
From: hermann pitton @ 2009-10-15 23:06 UTC (permalink / raw)
  To: Michael Grützmann; +Cc: video4linux-list

Hi,

Am Donnerstag, den 15.10.2009, 22:16 +0200 schrieb Michael Grützmann:
> Dear to all,
> 
> I have an Medion 7134 card, so I use the saa7134 module with a 2.6.25 kernel (card=12). But I have a question. Which tuner type should I use? 
>  cat /var/log/boot.msg |grep saa
> <6>saa7130/34: v4l2 driver version 0.2.14 loaded
> <6>saa7134[0]: found at 0000:00:0b.0, rev: 1, irq: 18, latency: 32, mmio: 0xdffffc00
> <6>saa7134[0]: subsystem: 16be:0003, board: Medion 7134 [card=12,autodetected]
> <6>saa7134[0]: board init: gpio is 0
> <6>saa7134[0]: i2c eeprom 00: be 16 03 00 08 20 1c 55 43 43 a9 1c 55 43 43 a9
> <6>saa7134[0]: i2c eeprom 10: ff ff ff ff 15 00 0e 01 0c c0 08 00 00 00 00 00
> <6>saa7134[0]: i2c eeprom 20: 00 00 00 e3 ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>saa7134[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> <6>tuner' 2-0043: chip found @ 0x86 (saa7134[0])
> <6>tuner' 2-0060: chip found @ 0xc0 (saa7134[0])
> <6>saa7134[0] Tuner type is 38

that is the working eeprom detection of the tuner type.
But there have been breakages in between, you might have to force the
tuner type on 2.6.25. Card=12 means lots of different cards.
What CTX revision and version do you have?

> <6>saa7134[0]: registered device video0 [v4l2]
> <6>saa7134[0]: registered device vbi0
> <6>saa7134[0]: registered device radio0
> <3>saa7134[0]/dvb: frontend initialization failed

Hm, on that tuner is no DVB-T.

> It is not tuner=38. 
> On the card, there stands: 'tuner philips 3139 147 18201H#'.

I have on one of them exactly the same.
You should read on the second line "FM1216ME/I H-3".

The third line has Philips internal variations of the model.
SV20 0241 is common for cards with tuner=38, not the older tuner=5 and
not yet the FMD1216ME hybrid,tuner=63, with also DVB-T support. (notice
the "D" on FMD1216ME)

> There are two Ambient chips on it. One chip ctis0tp. If needed, I can write to you the full chip labelings. 
> Your help would be appreciated.
> ps. I'm a linux newbie (use it for 2 years). Maybe you could also tell me how to write the changes made manually to modules.d, so the changes aren't lost when rebooting.

Maybe try to create some /etc/modprobe.conf for them.

Cheers,
Hermann


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: tuner type
       [not found] <1309684974@web.de>
@ 2009-10-16 22:00 ` hermann pitton
  0 siblings, 0 replies; 4+ messages in thread
From: hermann pitton @ 2009-10-16 22:00 UTC (permalink / raw)
  To: avalone; +Cc: linux-media

Hi Dirk,

Am Freitag, den 16.10.2009, 10:32 +0200 schrieb avalone@web.de:
> Thanks alot, Herman.
> What does ctx mean? I use opensuse 11.0.

you will find the CTX (Creatix) revision and version printed on the
board and also on a sticker on the card, mostly at the modem or ISDN
part. With that information and the second and third line printed on the
tuner, I should know which card you have.

Do you have it in an original blue MSI/Medion PCI slot.
At least variants with the Cologne ISDN chip (Kölner Dom Pictogramm) are
close to impossible to become stable in regular PCI slots.

They all have the same PCI subsystem, I have six different cards alone,
and we just detect the three different tuner types over the eeprom
content, since all other inputs are the same.

DVB-T support started with CTX917, 918 and 921 cardbus.
 
> So you say, it's not tuner=5 and not 63. So something in between?

If you read on the second line of the tuner label FM1216ME/I H-3, I
expect yours is from Singapore, others are from Indonesia etc ..., it is
a tuner=38. MK3 MultiEurope with tda9887. Works from Portugal/Ireland to
Vladivostok.

> I tired 51, if I remember it right. It worked, but sometimes there were muting breakes in between, but maybe it's just my vcr. 
> Can you name me a lightweight capture program? Maybe even something where you can adjust bitrate and container format? Best would be a command-line program.
> Thanks alot.
> ps. I'm from Germany, so maybe it's a german tuner?
> 
> best regards,
> 
> Dirk

On 2.6.25 and 2.6.26 were several known bugs introduced. First the user
could not set the detailed TV subnorm anymore, then the user was not
able to force a tuner type anymore and also the eeprom detection of the
tuner on the saa7134 was broken.

Further, if tuner stuff was not build as modules, there was an oops and
I'm still aware of more, but not related to your tuner.

This is all fixed, but it would take me time, to check how far it made
it into old distro kernels and stable vanilla revisions.

Try with at least 2.6.27 or compile current v4l-dvb and remove/backup
your old media modules folder. Currently you need at least a 2.6.26 to
compile latest.

Cheers,
Hermann



^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2009-10-16 22:01 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-10-15 20:16 tuner type Michael Grützmann
2009-10-15 22:40 ` Michael Krufky
2009-10-15 23:06 ` hermann pitton
     [not found] <1309684974@web.de>
2009-10-16 22:00 ` hermann pitton

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox