From: Sean Young <sean@mess.org>
To: Rolf Pedersen <rolfpedersen@mindspring.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: HauppaugeTV-quadHD DVB-T mpeg risc op code error
Date: Thu, 23 Apr 2020 16:35:05 +0100 [thread overview]
Message-ID: <20200423153505.GA22057@gofer.mess.org> (raw)
In-Reply-To: <0c0ab661-17bb-231a-7311-c35d8d0435c0@mindspring.com>
Hi,
On Thu, Apr 23, 2020 at 05:32:32AM -0700, Rolf Pedersen wrote:
> Hi Folks,
> I just subscribed after having trouble with this card that worked for 3
> years on Skylake i5-6500 but stopped tuning when I moved it to AMD Ryzen 5
> 3400G machine. I found the workaround in the archived thread referenced in
> the subject line and don't know any way to reply directly to it:
> https://www.spinics.net/lists/linux-media/msg114563.html
>
> My card is ATSC as on this page:
> https://www.kernel.org/doc/html/v4.10/media/v4l-drivers/cx23885-cardlist.html
> 57 Hauppauge WinTV-QuadHD-ATSC 0070:6a18, 0070:6b18
>
> and
>
> [rolf@x570i coup]$ lspcidrake -v | grep Conexant
> cx23885 : Conexant Systems, Inc.|CX23887/8 PCIe Broadcast Audio and
> Video Decoder with 3D Comb [MULTIMEDIA_VIDEO] (vendor:14f1 device:8880
> subv:0070 subd:6b18) (rev: 04)
> cx23885 : Conexant Systems, Inc.|CX23887/8 PCIe Broadcast Audio and
> Video Decoder with 3D Comb [MULTIMEDIA_VIDEO] (vendor:14f1 device:8880
> subv:0070 subd:6a18) (rev: 04)
>
> Neither scan, dvbscan, nor w_scan2, nor Kaffeine TV, while finding working
> frequencies, could divulge any services. The workaround was in the
> referenced post: cx23885.debug=8
>
> I've seen another report of a different kernel option that worked on Ryzen:
> |cx23885.dma_reset_workaround=2 here:
> https://www.dslreports.com/forum/r32639318-SFF-3400G-build#32640298
>
> Ok. Just wanted to join the chorus with a *metoo* in case I can provide
> some (guided) forensics.
So there is a commit for a related issue:
https://git.linuxtv.org/media_tree.git/commit/?id=4bd46aa0353e022c2401a258e93b107880a66533
That is kernel v5.0 and higher. So:
1. What kernel are you using?
2. What is the full lspci -n of your machine?
Thanks,
Sean
next prev parent reply other threads:[~2020-04-23 15:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 12:32 HauppaugeTV-quadHD DVB-T mpeg risc op code error Rolf Pedersen
2020-04-23 15:35 ` Sean Young [this message]
2020-04-23 15:49 ` Rolf Pedersen
2020-04-23 15:59 ` Sean Young
2020-04-23 16:09 ` Rolf Pedersen
2020-04-23 16:35 ` Sean Young
2020-04-24 17:46 ` Martin Burnicki
2020-04-25 11:41 ` Sean Young
2020-04-25 14:06 ` Martin Burnicki
2020-04-27 7:03 ` Martin Burnicki
2020-04-27 8:07 ` Sean Young
2020-04-27 8:59 ` Martin Burnicki
2020-04-28 18:24 ` Martin Burnicki
2020-04-30 16:49 ` Sean Young
2022-05-23 22:36 ` HauppaugeTV-quadHD DVB-T & HVR5525 " Ken Smith
2022-05-24 7:51 ` Martin Burnicki
2022-05-26 17:06 ` Ken Smith
2022-06-06 13:59 ` Ken Smith
2022-06-30 9:59 ` Ken Smith
2022-05-24 8:36 ` Ken Smith
2022-05-26 9:52 ` Ken Smith
2022-05-26 11:33 ` Ken Smith
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=20200423153505.GA22057@gofer.mess.org \
--to=sean@mess.org \
--cc=linux-media@vger.kernel.org \
--cc=rolfpedersen@mindspring.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