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@xxxxxxxxx> 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
|
_______________________________________________
linux-dvb mailing list
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
