All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miroslav Rovis <m.rovis@inet.hr>
To: linux-dvb@linuxtv.org
Subject: [linux-dvb] [PATCH] cx88-dvb: Fix order of frontend allocations (Re: current v4l-dvb - cannot access /dev/dvb/: No such file or directory
Date: Fri, 23 Jan 2009 20:21:52 +0100	[thread overview]
Message-ID: <497A18D0.70009@inet.hr> (raw)
In-Reply-To: <mailman.1.1232708401.9307.linux-dvb@linuxtv.org>

I pasted the subject line from:
http://www.linuxtv.org/pipermail/linux-dvb/2009-January/thread.html#31463
the last message of the thread on the problem that I still have (there
is the patch in there in some post on the thread that should fix my
problem).
Tha card is a Hauppauge HVR-3000 that works fine on M$ Windoze Vista.
Arch is 64bit Athlon based...
With the kernel ("uname -r" output):
2.6.28-gentoo-r1
In fact, cx88-dvb sometimes loads and then I have the populated
/dev/dvb... (very choppy but I got anything I tried after dvbscan and
szap etc.)
And sometimes it doesn't load at all and there is no /dev/dvb directory
at all.
The error when issuing "modprobe cx88-dvb" is:
FATAL: Error inserting cx88_dvb
(/lib/modules/2.6.28-gentoo-r1/v4l-dvb/video/cx88/cx88-dvb.ko): Unknown
symbol in module, or unknown parameter (see dmesg)
dmesg on its part only has:
cx88_dvb: Unknown parameter `frontend'
The kernel (2.6.28-gentoo-r1) does have the aforementioned Andy's patch
applied...
Firmare is as suggested here:
http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-4000#Firmware_v1.23.86.1
I am at a loss where to turn, what to try...
Cheers!
Miro Rovis
www.exDeo.com
www.CroatiaFidelis.hr


_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

           reply	other threads:[~2009-01-23 19:21 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <mailman.1.1232708401.9307.linux-dvb@linuxtv.org>]

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=497A18D0.70009@inet.hr \
    --to=m.rovis@inet.hr \
    --cc=linux-dvb@linuxtv.org \
    --cc=linux-media@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 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.