From: Adrian Bunk <bunk@stusta.de>
To: Gerd Knorr <kraxel@bytesex.org>
Cc: mchehab@brturbo.com.br, video4linux-list@redhat.com,
linux-kernel@vger.kernel.org
Subject: saa7134 card no longer working
Date: Sun, 10 Jul 2005 18:58:39 +0200 [thread overview]
Message-ID: <20050710165839.GQ28243@stusta.de> (raw)
Hi,
I observed the following problem with a Tevion MD 9717 card:
It works in 2.6.12-rc6-mm1, but AFAIR this was the last kernel where it
worked, in more recent kernels (including 2.6.13-rc2-mm1) tvtime only
says "no signal".
dmesg output with 2.6.12-rc6-mm1:
saa7134[0]: found at 0000:00:0a.0, rev: 1, irq: 6, latency: 32, mmio: 0xcfffcc00
saa7134[0]: subsystem: 1131:0000, board: Tevion MD 9717 [card=6,insmod option]
saa7134[0]: board init: gpio is 100a0
saa7134[0]: Huh, no eeprom present (err=-5)?
saa7134[0]: registered device video0 [v4l2]
saa7134[0]: registered device vbi0
saa7134[0]: registered device radio0
tuner 4-0060: chip found @ 0xc0 (saa7134[0])
tuner 4-0060: type set to 5 (Philips PAL_BG (FI1216 and compatibles))
In 2.6.13-rc2-mm1 there's an additional line
tuner 4-0060: All bytes are equal. It is not a TEA5767
I'm always saying "saa7134.card=6" at the kernel command line since I
got a "no eeprom present" message from the driver without this.
The card is working with 2.6.12-rc6-mm1, but during running, I
occasionally get the following message in the syslog:
saa7134[0]/audio: audio carrier scan failed, using 5.500 MHz [last detected]
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next reply other threads:[~2005-07-10 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-10 16:58 Adrian Bunk [this message]
2005-07-12 12:25 ` saa7134 card no longer working Adrian Bunk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050710165839.GQ28243@stusta.de \
--to=bunk@stusta.de \
--cc=kraxel@bytesex.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@brturbo.com.br \
--cc=video4linux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox