All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Timothy D. Lenz" <tlenz@vorgon.com>
To: <linux-dvb@linuxtv.org>
Subject: [linux-dvb] Correct drivers for HVR-1800
Date: Wed, 26 Mar 2008 02:51:41 -0700	[thread overview]
Message-ID: <000b01c88f27$93923bf0$0a00a8c0@vorg> (raw)

Found out both the PCIe x1 slots on my motherboard seem to be bad. But the
card does show up in the x16 slot which i'll using until I can get an RMA
from Asus (hope they do cross shiping).

I had to blacklist cx23885 so that the nexus drivers would work.

I load driver cx23885 (after the nexus drivers) which then also loads
compat_ioctl32 and videobuf_dvb. I also have tried loading ivtv which in
turn loads cx2341x, but these seem to have no effect. I got the firmware
from http://steventoth.net/linux/hvr1800/, ran the script and put the files
in /lib/firmware which already has the firmware for my Nexus.

I got dvb-apps but am having problems compiling it. I am able to compile
just scan and used it to scan for atsc channels. There are 2 channels which
it says it tunes that don't show up in the list it makes but it also says it
won't include analog channels in the list :(.

I patched VDR for atsc channels and added the atscepg plugin. I now have 2
adapters but when I try to scan from the plugin, it says not atsc device
found. I also tried seeding the channels.conf with a valid atsc channel
using info posted about the patch/plugin, but I get channel not available
even if I switch primary devices.

I posted in the dvbn board about the problems with the plugin, but wanted to
know if I missed any drivers I need to load.


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

             reply	other threads:[~2008-03-26  9:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26  9:51 Timothy D. Lenz [this message]
2008-03-26 14:08 ` [linux-dvb] Correct drivers for HVR-1800 Steven Toth

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='000b01c88f27$93923bf0$0a00a8c0@vorg' \
    --to=tlenz@vorgon.com \
    --cc=linux-dvb@linuxtv.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.