From: folkert@vanheusden.com (Folkert van Heusden)
To: Gerd Knorr <kraxel@bytesex.org>
Cc: James Bruce <bruce@andrew.cmu.edu>, linux-kernel@vger.kernel.org
Subject: Re: Potentially dead bttv cards from 2.6.10
Date: Mon, 28 Feb 2005 17:45:00 +0100 [thread overview]
Message-ID: <20050228164459.GI21514@vanheusden.com> (raw)
In-Reply-To: <87mzto3c78.fsf@bytesex.org>
> > Well, are there any theories as to why it would work flawlessly, then
> > after a hard lockup (due to what I think is a buggy V4L2 application),
> > that the cards no longer work?
> No idea why the eeprom doesn't respond any more. Maybe it's really
> broken. Note that the eeprom is read only at insmod time (and even
> that for some cards only), thus there isn't a clear connection between
> the crash and the eeprom issue. It could have died earlied unnoticed.
> The eeprom holds the PCI Subsystem ID, so without a working eeprom
> bttv can't figure automatically what exact card that is (see the
> "unknown/default" card name in the log) and maybe thats why does not
> work any more for the card in question. Thats should be easily
> fixable using the card= insmod option.
I remember something about that you shouldn't use the teletext-decoder
at the same time as viewing regular tv. That would damage the eeprom.
Maybe it is related?
Folkert van Heusden
Op zoek naar een IT of Finance baan? Mail me voor de mogelijkheden!
+------------------------------------------------------------------+
|UNIX admin? Then give MultiTail (http://vanheusden.com/multitail/)|
|a try, it brings monitoring logfiles to a different level! See |
|http://vanheusden.com/multitail/features.html for a feature list. |
+------------------------------------------= www.unixsoftware.nl =-+
Phone: +31-6-41278122, PGP-key: 1F28D8AE
Get your PGP/GPG key signed at www.biglumber.com!
next prev parent reply other threads:[~2005-02-28 16:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-26 4:57 Potentially dead bttv cards from 2.6.10 James Bruce
2005-02-28 13:44 ` Gerd Knorr
2005-02-28 14:43 ` James Bruce
2005-02-28 16:02 ` Gerd Knorr
2005-02-28 16:45 ` Folkert van Heusden [this message]
2005-02-28 16:52 ` Gerd Knorr
2005-03-01 6:41 ` James Bruce
2005-03-01 8:44 ` Gerd Knorr
2005-03-01 13:10 ` James Bruce
2005-03-04 20:37 ` James Bruce
2005-02-28 23:14 ` Bill Davidsen
2005-03-01 7:06 ` James Bruce
2005-03-01 14:11 ` Paulo Marques
2005-03-01 15:44 ` James Bruce
2005-03-01 16:03 ` Gerd Knorr
2005-03-01 20:32 ` Bill Davidsen
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=20050228164459.GI21514@vanheusden.com \
--to=folkert@vanheusden.com \
--cc=bruce@andrew.cmu.edu \
--cc=kraxel@bytesex.org \
--cc=linux-kernel@vger.kernel.org \
/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