public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Matyas Sustik <linux-dvb.list@sustik.com>
To: hermann pitton <hermann-pitton@arcor.de>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Fusion HDTV7 again
Date: Sun, 21 Dec 2008 08:47:06 -0600	[thread overview]
Message-ID: <494E56EA.7080604@sustik.com> (raw)
In-Reply-To: <1229809078.4702.34.camel@pc10.localdom.local>

hermann pitton wrote:
> Hi Matyas,
> In this case the old compat-ioctl32 is not replaced by the new
> v4l2-compat-ioctl32 module.
> 
> If you do on top of the modules of your kernel version
> "less modules.symbols |grep ioctl32",
> you likely will see this.
> alias symbol:v4l_compat_ioctl32 compat_ioctl32
> alias symbol:v4l_compat_ioctl32 v4l2-compat-ioctl32
> 
> But it should be only that.
> less modules.symbols |grep ioctl32
> alias symbol:v4l_compat_ioctl32 v4l2-compat-ioctl32
> 
> On top of the mercurial v4l-dvb do
> "make rmmod", since some complaints are visible do it again.
> 
> Then "make rminstall" should remove all old modules,
> but renamed ones or such in distribution specific wrong locations
> remain.
> 
> Check with "ls -R |grep .ko" on top of your kernel's media modules
> folder.
> 
> Delete the media folder or the modules.

I edited modules.symbols to comply to your suggestion.  I made sure that
the old modules are gone.  After a recompile, install and reboot the driver
started to work again!

Thanks a lot.
Matyas
-
Every hardware eventually breaks.  Every software eventually works.

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

  reply	other threads:[~2008-12-21 14:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-20 19:39 [linux-dvb] Fusion HDTV7 again Matyas Sustik
2008-12-20 21:37 ` hermann pitton
2008-12-21 14:47   ` Matyas Sustik [this message]
2008-12-23 19:02     ` Tu-Tu Yu
  -- strict thread matches above, loose matches on Subject: below --
2008-12-20 21:45 William Melgaard

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=494E56EA.7080604@sustik.com \
    --to=linux-dvb.list@sustik.com \
    --cc=hermann-pitton@arcor.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox