All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduard Huguet <eduardhc@gmail.com>
To: Matthias Schwarzott <zzam@gentoo.org>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] How to force adaptor order when using 2 DVB cards?
Date: Thu, 07 Feb 2008 21:14:05 +0100	[thread overview]
Message-ID: <47AB668D.2090405@gmail.com> (raw)
In-Reply-To: <200802071940.09143.zzam@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 2009 bytes --]

Hi,
    Thank you. This is what I finally did (blacklisting and manually 
loading), as the udev rules have a really "ugly" syntax ;). I found the 
tip in Gentoo wiki and it's working fine now.

Thank you all anyway.
  Eduard




En/na Matthias Schwarzott ha escrit:
> On Donnerstag, 7. Februar 2008, John Drescher wrote:
>   
>> On Feb 7, 2008 11:46 AM, Eduard Huguet <eduardhc@gmail.com> wrote:
>>     
>>> Hi,
>>>     I currently have a media center computer set up using Gentoo 64 bit
>>> and a Hauppauge Nova-T 500 card (dual DVB-T receiver). Now I'm trying to
>>> add a new card (DVB-S), and here my problems begin: not mentioning the
>>> experimental state of the driver (this is a different story that doesn't
>>> matter now), my problem is that the new card porks the order in which
>>> the device nodes were created in /dev. And even worse, the actual order
>>> ing schema is different between a cold boot and rebooting:
>>>
>>> Cold boot:
>>>   · DVB:0: DVB-S tuner from Avermedia A700
>>>   · DVB:1,2: DVB-T tuners from Nova-T
>>>
>>> Reboot:
>>>   · DVB:0: 1st DVB-T tuner from Nova-T
>>>   · DVB:1: DVB-S tuner from A700
>>>   · DVB:2: 2nd DVB-T tuner from Nova-T
>>>
>>> I guess that on a cold boot the Nova-T 500 takes longer to initialize
>>> (due to the firmware being loaded), so its adaptors gets both created
>>> later.
>>>
>>> Is there any way to avoid this? My MythTV setup currently expects to
>>> find the 2 Nova-T 500 adaptors on DVB:0 and DVB:1, and In expected the
>>> new DVB-S adaptor to be created as DVB:2. However, it seems this is not
>>> the case.
>>>
>>> Is there any way to force the numbering schema or the 2 adaptors?
>>>       
>> Create a udev rule.
>>
>> http://reactivated.net/writing_udev_rules.html
>>
>>     
> More people have tried this for dvb and failed as it seems. That would require 
> something like persistent-net.
>
> I suggest you first try blacklisting the modules like described here:
> http://www.gentoo.org/doc/en/udev-guide.xml
>
> Matthias
>
>   

[-- Attachment #1.2: Type: text/html, Size: 2716 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

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

  reply	other threads:[~2008-02-07 20:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-07 16:46 [linux-dvb] How to force adaptor order when using 2 DVB cards? Eduard Huguet
2008-02-07 17:01 ` John Drescher
2008-02-07 18:40   ` Matthias Schwarzott
2008-02-07 20:14     ` Eduard Huguet [this message]
2008-02-07 20:07   ` thomas schorpp
2008-02-07 20:41 ` Simeon Walker
  -- strict thread matches above, loose matches on Subject: below --
2008-02-12 16:54 Tim Hewett

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=47AB668D.2090405@gmail.com \
    --to=eduardhc@gmail.com \
    --cc=linux-dvb@linuxtv.org \
    --cc=zzam@gentoo.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.