How to force adaptor order when using 2 DVB cards?
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? ¿Would maybe help i.e. setting RC_DEVICE_TARBALL="yes" in /etc/conf.d/rc (currently is set to "no") with only the Nova-T connected and then adding te other one? I wonder is this would force its adaptors to be created always at the same position.
Thanks for any help you could provide.
Eduard
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 22 lines · Eduard Huguet
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-TReboot:
· DVB:0: 1st DVB-T tuner from Nova-T
· DVB:1: DVB-S tuner from A700
· DVB:2: 2nd DVB-T tuner from Nova-TI 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.
Quoted 6 lines
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
John
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 28 lines · John Drescher
Quoted 27 lines · Eduard Huguet
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-TReboot:
· DVB:0: 1st DVB-T tuner from Nova-T
· DVB:1: DVB-S tuner from A700
· DVB:2: 2nd DVB-T tuner from Nova-TI 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.
Quoted 6 lines
Quoted 1 line
Is there any way to force the numbering schema or the 2 adaptors?
Create a udev rule.
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
Signature · 6 lines
Matthias Schwarzott (zzam) _______________________________________________ linux-dvb mailing list [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 28 lines · John Drescher
Quoted 27 lines · Eduard Huguet
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-TReboot:
· DVB:0: 1st DVB-T tuner from Nova-T
· DVB:1: DVB-S tuner from A700
· DVB:2: 2nd DVB-T tuner from Nova-TI 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.
Quoted 8 lines
Quoted 1 line
Is there any way to force the numbering schema or the 2 adaptors?
Create a udev rule.
http://reactivated.net/writing_udev_rules.html
John
no, this would be too lowlevel.
man modprobe.conf -> install.
y
tom
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
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:
Quoted 38 lines · John Drescher
Quoted 30 lines · Eduard Huguet
Quoted 28 lines
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-TReboot:
· DVB:0: 1st DVB-T tuner from Nova-T
· DVB:1: DVB-S tuner from A700
· DVB:2: 2nd DVB-T tuner from Nova-TI 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.
Quoted 7 lines
Quoted 2 lines
Is there any way to force the numbering schema or the 2 adaptors?
Create a udev rule.
Quoted 8 lines
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.xmlMatthias
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Yep, it's horrible. This is what I did, the adapters 0,1,2 are still there but MythTV is configured to used 4,5 and 6.
# My own DVB hell
# Twinhan DVB-S Card
#
KERNEL=="dvb[0-9].frontend0", ATTR{dev}=="212:3", symlink+="dvb/adapter4/frontend0", GROUP="video" KERNEL=="dvb[0-9].demux0", ATTR{dev}=="212:4", symlink+="dvb/adapter4/demux0", GROUP="video" KERNEL=="dvb[0-9].net0", ATTR{dev}=="212:7", symlink+="dvb/adapter4/net0", GROUP="video" KERNEL=="dvb[0-9].dvr0", ATTR{dev}=="212:5", symlink+="dvb/adapter4/dvr0", GROUP="video"
#
# Nova-T Stick 1
#
KERNEL=="dvb[0-9].frontend0", ATTRS{serial}=="4030489593", symlink+="dvb/adapter5/frontend0", GROUP="video"
KERNEL=="dvb[0-9].demux0", ATTRS{serial}=="4030489593",
symlink+="dvb/adapter5/demux0", GROUP="video" KERNEL=="dvb[0-9].net0", ATTRS{serial}=="4030489593", symlink+="dvb/adapter5/net0", GROUP="video" KERNEL=="dvb[0-9].dvr0", ATTRS{serial}=="4030489593", symlink+="dvb/adapter5/dvr0", GROUP="video"
#
# Nova-T Stick 2
#
KERNEL=="dvb[0-9].frontend0", ATTRS{serial}=="4027844315", symlink+="dvb/adapter6/frontend0", GROUP="video" KERNEL=="dvb[0-9].demux0", ATTRS{serial}=="4027844315", symlink+="dvb/adapter6/demux0", GROUP="video" KERNEL=="dvb[0-9].net0", ATTRS{serial}=="4027844315", symlink+="dvb/adapter6/net0", GROUP="video" KERNEL=="dvb[0-9].dvr0", ATTRS{serial}=="4027844315", symlink+="dvb/adapter6/dvr0", GROUP="video"
I'm not sure if gmail has split the lines above but each actual line should start with KERNEL.
Sim
Quoted 35 lines · Eduard Huguet
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-TReboot:
· DVB:0: 1st DVB-T tuner from Nova-T
· DVB:1: DVB-S tuner from A700
· DVB:2: 2nd DVB-T tuner from Nova-TI 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? ¿Would maybe help i.e. setting RC_DEVICE_TARBALL="yes" in
/etc/conf.d/rc(currently is set to "no") with only the Nova-T connected and then adding te other one? I wonder is this would force its adaptors to be created always at the same position.Thanks for any help you could provide.
Quoted 8 lines
Eduard
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb