public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Ruediger Dohmhardt <ruediger.dohmhardt@freenet.de>
To: linux-media@vger.kernel.org
Subject: Re: Which modules for the VP-2033? Where is the module "mantis.ko"?
Date: Wed, 23 Dec 2009 22:03:39 +0100	[thread overview]
Message-ID: <4B3285AB.4070108@freenet.de> (raw)
In-Reply-To: <1a297b360912231226j704e2c92jd9bb04cf23275829@mail.gmail.com>

Manu Abraham schrieb:
> On Thu, Dec 24, 2009 at 12:01 AM, Ruediger Dohmhardt
> <ruediger.dohmhardt@freenet.de> wrote:
>   
>> Manu Abraham schrieb:
>>     
>>> Hello Ruediger,
>>>
>>> On Wed, Dec 23, 2009 at 11:04 PM, Ruediger Dohmhardt
>>> <ruediger.dohmhardt@freenet.de> wrote:
>>>
>>>       
>>>> Aljaž Prusnik schrieb:
>>>>
>>>>         
>>>>> If using the http://jusst.de/hg/v4l-dvb tree, everything compiles ok,
>>>>> module loads, but there is no remote anywhere (there is an IR folder
>>>>> with the ir-common.ko file, under common there is not).
>>>>>
>>>>>
>>>>>
>>>>>           
>>>> Aljaz, do you have the module mantis.ko?
>>>>
>>>> Ruediger
>>>>
>>>>
>>>>         
>>> There was a build issue when i posted the link originally, but it had
>>> been fixed..
>>>
>>>
>>>       
>> Yupp, it works now!
>>
>> I just downloaded version 2315248f648c. It compiles fine on Suse 11.1 and
>> it works here with vdr-1.7.10 and xineliboutput (from CVS).
>>
>> However, as Aljaž also noted, the driver does not "autoload".
>> I need to do modprobe mantis.ko.
>>
>> Manu, this used to work, but I do not remember when the "autoload was lost".
>>     
>
>
> Have you run depmod ?
>   
Yes, I did

    depmod -a

several times. Actually, if I were to miss a "depmod" than also the command

    modprobe mantis

would not work, because the module would not be found.

Ruediger


  reply	other threads:[~2009-12-23 21:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07 20:12 Which modules for the VP-2033? Where is the module "mantis.ko"? Ruediger Dohmhardt
2009-12-23 14:30 ` Aljaž Prusnik
2009-12-23 15:53   ` Igor M. Liplianin
2009-12-23 16:41     ` Aljaž Prusnik
2009-12-23 19:04       ` Ruediger Dohmhardt
2009-12-23 19:24         ` Manu Abraham
2009-12-23 20:01           ` Ruediger Dohmhardt
2009-12-23 20:26             ` Manu Abraham
2009-12-23 21:03               ` Ruediger Dohmhardt [this message]
2009-12-23 23:45           ` Aljaž Prusnik
2009-12-24 16:45             ` Ruediger Dohmhardt
2009-12-24 16:51               ` Aljaž Prusnik
2009-12-27 22:23                 ` Manu Abraham
2009-12-28 19:28                   ` Aljaž Prusnik
2009-12-28 20:06                     ` Aljaž Prusnik
2009-12-29 18:25                       ` Aljaž Prusnik
2010-01-09 17:26                   ` Aljaž Prusnik

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=4B3285AB.4070108@freenet.de \
    --to=ruediger.dohmhardt@freenet.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox