Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Mythtvnz

DVB cards changing

 

 

MythTV mythtvnz RSS feed   Index | Next | Previous | View Threaded


barryc at bcsystems

Jul 16, 2009, 2:05 AM

Post #1 of 12 (2332 views)
Permalink
DVB cards changing

I have a second problem, same system. I have two Hauppauge Nova S cards and
a dual Nova T. The cards keep changing their assignments, eg DVBS0 becomes
the Nova T then after a reboot becomes the Nova S.
Can't figure this one out but it sure stuffs up myth.
I also have problems trying to tune one of the nova T, sometimes it just
sits there and won't tune, other times it flys through.
Aaargh! Help anyone?



--

Barry Clearwater
Managing director
BC Systems Consultancy Limited
___________________________
18 Shaw Street
Mosgiel
Dunedin 9024
Phone: +64 3 489 3915
Mobile: +64 27 221 9338
Email: barryc [at] bcsystems


krizze at bluezone

Jul 16, 2009, 4:33 AM

Post #2 of 12 (2263 views)
Permalink
Re: DVB cards changing [In reply to]

> I have a second problem, same system. I have two Hauppauge Nova S cards
> and
> a dual Nova T. The cards keep changing their assignments, eg DVBS0 becomes
> the Nova T then after a reboot becomes the Nova S.
> Can't figure this one out but it sure stuffs up myth.
> I also have problems trying to tune one of the nova T, sometimes it just
> sits there and won't tune, other times it flys through.
> Aaargh! Help anyone?
One way would be to blacklist the kernel modules the cards are using
(/etc/modprobe.d/blacklist afaik). Then you can manually modprobe them in
order during bootup, e.g. in /etc/rc.local:
modprobe module-of-card-1 options=xxx
modprobe module-of-card-2 options=xxx

I also have problems with tuning on my Nova-T-500, it just stands there
with no lock, and 0 signal. After a reboot it's OK again, for a cople of
hours, if i'm lucky. Guess it's broken or something.


Regards,
Kristian Haga Karstensen



_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/


g.woollett at irl

Jul 16, 2009, 2:22 PM

Post #3 of 12 (2254 views)
Permalink
Re: DVB cards changing [In reply to]

krizze [at] bluezone wrote:
>> I have a second problem, same system. I have two Hauppauge Nova S cards
>> and
>> a dual Nova T. The cards keep changing their assignments, eg DVBS0 becomes
>> the Nova T then after a reboot becomes the Nova S.
>> Can't figure this one out but it sure stuffs up myth.
>> I also have problems trying to tune one of the nova T, sometimes it just
>> sits there and won't tune, other times it flys through.
>> Aaargh! Help anyone?
>>
> One way would be to blacklist the kernel modules the cards are using
> (/etc/modprobe.d/blacklist afaik). Then you can manually modprobe them in
> order during bootup, e.g. in /etc/rc.local:
> modprobe module-of-card-1 options=xxx
> modprobe module-of-card-2 options=xxx
>
> I also have problems with tuning on my Nova-T-500, it just stands there
> with no lock, and 0 signal. After a reboot it's OK again, for a cople of
> hours, if i'm lucky. Guess it's broken or something.
>
>
> Regards,
> Kristian Haga Karstensen
>
>
>
> _______________________________________________
> mythtvnz mailing list
> mythtvnz [at] lists
> http://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>
Make sure you are not running the 1.2 version firmware. A UDev rule can
stop them changing around.
I had a HVR4000 & Nova T that did this. I found that they only changed
order when I did a warm reboot. Cold booting didn't change them.
Once the firmware gets loaded they must change the product or vendor ID
and this causes them to be allocated in a different order by the OS.



--
Graeme Woollett
Research Engineer
Applied Physics and Engineering Team
Industrial Research Ltd
ph 04 931 0193
email g.woollett [at] irl


_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/


killerkiwi2005 at gmail

Jul 16, 2009, 4:50 PM

Post #4 of 12 (2252 views)
Permalink
Re: DVB cards changing [In reply to]

Create a udev rule....

See script on this bug
https://bugs.launchpad.net/ubuntu/+source/mythbuntu-meta/+bug/370696

They got my name wrong in the copyright lol

2009/7/17 Graeme Woollett <g.woollett [at] irl>:
> krizze [at] bluezone wrote:
>>> I have a second problem, same system. I have two Hauppauge Nova S cards
>>> and
>>> a dual Nova T. The cards keep changing their assignments, eg DVBS0 becomes
>>> the Nova T then after a reboot becomes the Nova S.
>>> Can't figure this one out but it sure stuffs up myth.
>>> I also have problems trying to tune one of the nova T, sometimes it just
>>> sits there and won't tune, other times it flys through.
>>> Aaargh! Help anyone?
>>>
>> One way would be to blacklist the kernel modules the cards are using
>> (/etc/modprobe.d/blacklist afaik). Then you can manually modprobe them in
>> order during bootup, e.g. in /etc/rc.local:
>> modprobe module-of-card-1 options=xxx
>> modprobe module-of-card-2 options=xxx
>>
>> I also have problems with tuning on my Nova-T-500, it just stands there
>> with no lock, and 0 signal. After a reboot it's OK again, for a cople of
>> hours, if i'm lucky. Guess it's broken or something.
>>
>>
>> Regards,
>> Kristian Haga Karstensen
>>
>>
>>
>> _______________________________________________
>> mythtvnz mailing list
>> mythtvnz [at] lists
>> http://lists.ourshack.com/mailman/listinfo/mythtvnz
>> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>>
> Make sure you are not running the 1.2 version firmware.  A UDev rule can
> stop them changing around.
> I had a HVR4000 & Nova T that did this.  I found that they only changed
> order when I did a warm reboot.  Cold booting didn't change them.
> Once the firmware gets loaded they must change the product or vendor ID
> and this causes them to be allocated in a different order by the OS.
>
>
>
> --
> Graeme Woollett
> Research Engineer
> Applied Physics and Engineering Team
> Industrial Research Ltd
> ph 04 931 0193
> email g.woollett [at] irl
>
>
> _______________________________________________
> mythtvnz mailing list
> mythtvnz [at] lists
> http://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>



--
"Weekends don't count unless you spend them doing something completely
pointless. " - Calven

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/


barryc at bcsystems

Jul 16, 2009, 7:40 PM

Post #5 of 12 (2247 views)
Permalink
Re: DVB cards changing [In reply to]

Jason, thanks for this. I have only a cursory understanding of the udev
rules, can you give me an example for using your script. I have a
/dev/video0 and /dev/video1 device which are pointed to by
/dev/v4l/by-path/pci-0000:01:06.0-video-index0 and index1 symlinks.
I've found /lib/udev/rules.d/60-persistent-v4l.rules but I'm not sure which
two devices I'm telling your script about - the script asks for an old
device and new device.
In mythtv-setup, i've got dvb devices 0-3 which keep changing (don't know
how they are referenced!) I'm typing all this to try and document it better
for the next "bloke" who thinks he knows what hes doing :-) So thanks for
the script, just need a wee nudge.
Regards
Barry

2009/7/17 Jason Taylor <killerkiwi2005 [at] gmail>

> Create a udev rule....
>
> See script on this bug
> https://bugs.launchpad.net/ubuntu/+source/mythbuntu-meta/+bug/370696
>
> They got my name wrong in the copyright lol
>
> 2009/7/17 Graeme Woollett <g.woollett [at] irl>:
> > krizze [at] bluezone wrote:
> >>> I have a second problem, same system. I have two Hauppauge Nova S cards
> >>> and
> >>> a dual Nova T. The cards keep changing their assignments, eg DVBS0
> becomes
> >>> the Nova T then after a reboot becomes the Nova S.
> >>> Can't figure this one out but it sure stuffs up myth.
> >>> I also have problems trying to tune one of the nova T, sometimes it
> just
> >>> sits there and won't tune, other times it flys through.
> >>> Aaargh! Help anyone?
> >>>
> >> One way would be to blacklist the kernel modules the cards are using
> >> (/etc/modprobe.d/blacklist afaik). Then you can manually modprobe them
> in
> >> order during bootup, e.g. in /etc/rc.local:
> >> modprobe module-of-card-1 options=xxx
> >> modprobe module-of-card-2 options=xxx
> >>
> >> I also have problems with tuning on my Nova-T-500, it just stands there
> >> with no lock, and 0 signal. After a reboot it's OK again, for a cople of
> >> hours, if i'm lucky. Guess it's broken or something.
> >>
> >>
> >> Regards,
> >> Kristian Haga Karstensen
> >>
> >>
> >>
> >> _______________________________________________
> >> mythtvnz mailing list
> >> mythtvnz [at] lists
> >> http://lists.ourshack.com/mailman/listinfo/mythtvnz
> >> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
> >>
> > Make sure you are not running the 1.2 version firmware. A UDev rule can
> > stop them changing around.
> > I had a HVR4000 & Nova T that did this. I found that they only changed
> > order when I did a warm reboot. Cold booting didn't change them.
> > Once the firmware gets loaded they must change the product or vendor ID
> > and this causes them to be allocated in a different order by the OS.
> >
> >
> >
> > --
> > Graeme Woollett
> > Research Engineer
> > Applied Physics and Engineering Team
> > Industrial Research Ltd
> > ph 04 931 0193
> > email g.woollett [at] irl
> >
> >
> > _______________________________________________
> > mythtvnz mailing list
> > mythtvnz [at] lists
> > http://lists.ourshack.com/mailman/listinfo/mythtvnz
> > Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
> >
>
>
>
> --
> "Weekends don't count unless you spend them doing something completely
> pointless. " - Calven
>
> _______________________________________________
> mythtvnz mailing list
> mythtvnz [at] lists
> http://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>



--

Barry Clearwater
Managing director
BC Systems Consultancy Limited
___________________________
18 Shaw Street
Mosgiel
Dunedin 9024
Phone: +64 3 489 3915
Mobile: +64 27 221 9338
Email: barryc [at] bcsystems


barryc at bcsystems

Jul 16, 2009, 7:52 PM

Post #6 of 12 (2256 views)
Permalink
Re: DVB cards changing [In reply to]

Further info to my last post, the install has 2 Nova S cards and a Nova T
pci, which comes up on the usb bus. I'm betting all my tuning issues with
the nova T are related to this card id swapping nonsense. Not sure how the
Nova T selects its device number wrt Myth, but thats the setup.
Barry

2009/7/17 Barry Clearwater <barryc [at] bcsystems>

> Jason, thanks for this. I have only a cursory understanding of the udev
> rules, can you give me an example for using your script. I have a
> /dev/video0 and /dev/video1 device which are pointed to by
> /dev/v4l/by-path/pci-0000:01:06.0-video-index0 and index1 symlinks.
> I've found /lib/udev/rules.d/60-persistent-v4l.rules but I'm not sure which
> two devices I'm telling your script about - the script asks for an old
> device and new device.
> In mythtv-setup, i've got dvb devices 0-3 which keep changing (don't know
> how they are referenced!) I'm typing all this to try and document it better
> for the next "bloke" who thinks he knows what hes doing :-) So thanks for
> the script, just need a wee nudge.
> Regards
> Barry
>
> 2009/7/17 Jason Taylor <killerkiwi2005 [at] gmail>
>
> Create a udev rule....
>>
>> See script on this bug
>> https://bugs.launchpad.net/ubuntu/+source/mythbuntu-meta/+bug/370696
>>
>> They got my name wrong in the copyright lol
>>
>> 2009/7/17 Graeme Woollett <g.woollett [at] irl>:
>> > krizze [at] bluezone wrote:
>> >>> I have a second problem, same system. I have two Hauppauge Nova S
>> cards
>> >>> and
>> >>> a dual Nova T. The cards keep changing their assignments, eg DVBS0
>> becomes
>> >>> the Nova T then after a reboot becomes the Nova S.
>> >>> Can't figure this one out but it sure stuffs up myth.
>> >>> I also have problems trying to tune one of the nova T, sometimes it
>> just
>> >>> sits there and won't tune, other times it flys through.
>> >>> Aaargh! Help anyone?
>> >>>
>> >> One way would be to blacklist the kernel modules the cards are using
>> >> (/etc/modprobe.d/blacklist afaik). Then you can manually modprobe them
>> in
>> >> order during bootup, e.g. in /etc/rc.local:
>> >> modprobe module-of-card-1 options=xxx
>> >> modprobe module-of-card-2 options=xxx
>> >>
>> >> I also have problems with tuning on my Nova-T-500, it just stands there
>> >> with no lock, and 0 signal. After a reboot it's OK again, for a cople
>> of
>> >> hours, if i'm lucky. Guess it's broken or something.
>> >>
>> >>
>> >> Regards,
>> >> Kristian Haga Karstensen
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> mythtvnz mailing list
>> >> mythtvnz [at] lists
>> >> http://lists.ourshack.com/mailman/listinfo/mythtvnz
>> >> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>> >>
>> > Make sure you are not running the 1.2 version firmware. A UDev rule can
>> > stop them changing around.
>> > I had a HVR4000 & Nova T that did this. I found that they only changed
>> > order when I did a warm reboot. Cold booting didn't change them.
>> > Once the firmware gets loaded they must change the product or vendor ID
>> > and this causes them to be allocated in a different order by the OS.
>> >
>> >
>> >
>> > --
>> > Graeme Woollett
>> > Research Engineer
>> > Applied Physics and Engineering Team
>> > Industrial Research Ltd
>> > ph 04 931 0193
>> > email g.woollett [at] irl
>> >
>> >
>> > _______________________________________________
>> > mythtvnz mailing list
>> > mythtvnz [at] lists
>> > http://lists.ourshack.com/mailman/listinfo/mythtvnz
>> > Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>> >
>>
>>
>>
>> --
>> "Weekends don't count unless you spend them doing something completely
>> pointless. " - Calven
>>
>> _______________________________________________
>> mythtvnz mailing list
>> mythtvnz [at] lists
>> http://lists.ourshack.com/mailman/listinfo/mythtvnz
>> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>>
>
>
>
> --
>
> Barry Clearwater
> Managing director
> BC Systems Consultancy Limited
> ___________________________
> 18 Shaw Street
> Mosgiel
> Dunedin 9024
> Phone: +64 3 489 3915
> Mobile: +64 27 221 9338
> Email: barryc [at] bcsystems
>



--

Barry Clearwater
Managing director
BC Systems Consultancy Limited
___________________________
18 Shaw Street
Mosgiel
Dunedin 9024
Phone: +64 3 489 3915
Mobile: +64 27 221 9338
Email: barryc [at] bcsystems


killerkiwi2005 at gmail

Jul 16, 2009, 7:53 PM

Post #7 of 12 (2246 views)
Permalink
Re: DVB cards changing [In reply to]

no problem... the bug says /dev/v4l /* dont work.. I'm assuming thats
still true?

I've only ever done this with analogue cards but this is what I did

sudo python udev-rules-jaunty.py /dev/video0 /dev/video_PVR150a
sudo python udev-rules-jaunty.py /dev/video1 /dev/video_PVR150b

And that will walk you through the rest

Then in myth setup change the devices to /dev/video_PVR150a and
/dev/video_PVR150b

The /dev/video_ links will then always point to the correct device,
the /dev/video0 etc will still change

Jason Taylor

2009/7/17 Barry Clearwater <barryc [at] bcsystems>:
> Jason, thanks for this. I have only a cursory understanding of the udev
> rules, can you give me an example for using your script. I have a
> /dev/video0 and /dev/video1 device which are pointed to by
> /dev/v4l/by-path/pci-0000:01:06.0-video-index0  and index1  symlinks.
> I've found /lib/udev/rules.d/60-persistent-v4l.rules but I'm not sure which
> two devices I'm telling your script about - the script asks for an old
> device and new device.
> In mythtv-setup, i've got dvb devices 0-3  which keep changing (don't know
> how they are referenced!) I'm typing all this to try and document it better
> for the next "bloke" who thinks he knows what hes doing :-) So thanks for
> the script, just need a wee nudge.
> Regards
> Barry
>
> 2009/7/17 Jason Taylor <killerkiwi2005 [at] gmail>
>>
>> Create a udev rule....
>>
>> See script on this bug
>> https://bugs.launchpad.net/ubuntu/+source/mythbuntu-meta/+bug/370696
>>
>> They got my name wrong in the copyright lol
>>
>> 2009/7/17 Graeme Woollett <g.woollett [at] irl>:
>> > krizze [at] bluezone wrote:
>> >>> I have a second problem, same system. I have two Hauppauge Nova S
>> >>> cards
>> >>> and
>> >>> a dual Nova T. The cards keep changing their assignments, eg DVBS0
>> >>> becomes
>> >>> the Nova T then after a reboot becomes the Nova S.
>> >>> Can't figure this one out but it sure stuffs up myth.
>> >>> I also have problems trying to tune one of the nova T, sometimes it
>> >>> just
>> >>> sits there and won't tune, other times it flys through.
>> >>> Aaargh! Help anyone?
>> >>>
>> >> One way would be to blacklist the kernel modules the cards are using
>> >> (/etc/modprobe.d/blacklist afaik). Then you can manually modprobe them
>> >> in
>> >> order during bootup, e.g. in /etc/rc.local:
>> >> modprobe module-of-card-1 options=xxx
>> >> modprobe module-of-card-2 options=xxx
>> >>
>> >> I also have problems with tuning on my Nova-T-500, it just stands there
>> >> with no lock, and 0 signal. After a reboot it's OK again, for a cople
>> >> of
>> >> hours, if i'm lucky. Guess it's broken or something.
>> >>
>> >>
>> >> Regards,
>> >> Kristian Haga Karstensen
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> mythtvnz mailing list
>> >> mythtvnz [at] lists
>> >> http://lists.ourshack.com/mailman/listinfo/mythtvnz
>> >> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>> >>
>> > Make sure you are not running the 1.2 version firmware.  A UDev rule can
>> > stop them changing around.
>> > I had a HVR4000 & Nova T that did this.  I found that they only changed
>> > order when I did a warm reboot.  Cold booting didn't change them.
>> > Once the firmware gets loaded they must change the product or vendor ID
>> > and this causes them to be allocated in a different order by the OS.
>> >
>> >
>> >
>> > --
>> > Graeme Woollett
>> > Research Engineer
>> > Applied Physics and Engineering Team
>> > Industrial Research Ltd
>> > ph 04 931 0193
>> > email g.woollett [at] irl
>> >
>> >
>> > _______________________________________________
>> > mythtvnz mailing list
>> > mythtvnz [at] lists
>> > http://lists.ourshack.com/mailman/listinfo/mythtvnz
>> > Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>> >
>>
>>
>>
>> --
>> "Weekends don't count unless you spend them doing something completely
>> pointless. " - Calven
>>
>> _______________________________________________
>> mythtvnz mailing list
>> mythtvnz [at] lists
>> http://lists.ourshack.com/mailman/listinfo/mythtvnz
>> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>
>
>
> --
>
> Barry Clearwater
> Managing director
> BC Systems Consultancy Limited
> ___________________________
> 18 Shaw Street
> Mosgiel
> Dunedin 9024
> Phone: +64 3 489 3915
> Mobile: +64 27 221 9338
> Email: barryc [at] bcsystems
>
> _______________________________________________
> mythtvnz mailing list
> mythtvnz [at] lists
> http://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>
>



--
"Weekends don't count unless you spend them doing something completely
pointless. " - Calven

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/


barryc at bcsystems

Jul 17, 2009, 4:57 AM

Post #8 of 12 (2230 views)
Permalink
Re: DVB cards changing [In reply to]

Hmm, not sure.
I may slightly get it now. The Nova S has a composite video out which is
probably why I also get /dev/video0 and /dev/video1 but they're not really
what I'm after.
I may be beating up the wrong runway.
I can see the cards in the pci bus.
To be honest very little about this install has gone easy. Lirc is all
changed, the cards have been mental, and audio has been elusive (Just
figured out making the master the volume control works). Granted that nvidia
graphics have been easy-ish, EIT off the dish is not too hard but l had a
large enough headache with trying to get diskless workstations to be
properly set up - MCC kept crashing for them.
Yes, its Mythbuntu 9.04 folks.
Barry

2009/7/17 Jason Taylor <killerkiwi2005 [at] gmail>

> no problem... the bug says /dev/v4l /* dont work.. I'm assuming thats
> still true?
>
> I've only ever done this with analogue cards but this is what I did
>
> sudo python udev-rules-jaunty.py /dev/video0 /dev/video_PVR150a
> sudo python udev-rules-jaunty.py /dev/video1 /dev/video_PVR150b
>
> And that will walk you through the rest
>
> Then in myth setup change the devices to /dev/video_PVR150a and
> /dev/video_PVR150b
>
> The /dev/video_ links will then always point to the correct device,
> the /dev/video0 etc will still change
>
> Jason Taylor
>
> 2009/7/17 Barry Clearwater <barryc [at] bcsystems>:
> > Jason, thanks for this. I have only a cursory understanding of the udev
> > rules, can you give me an example for using your script. I have a
> > /dev/video0 and /dev/video1 device which are pointed to by
> > /dev/v4l/by-path/pci-0000:01:06.0-video-index0 and index1 symlinks.
> > I've found /lib/udev/rules.d/60-persistent-v4l.rules but I'm not sure
> which
> > two devices I'm telling your script about - the script asks for an old
> > device and new device.
> > In mythtv-setup, i've got dvb devices 0-3 which keep changing (don't
> know
> > how they are referenced!) I'm typing all this to try and document it
> better
> > for the next "bloke" who thinks he knows what hes doing :-) So thanks for
> > the script, just need a wee nudge.
> > Regards
> > Barry
> >
> > 2009/7/17 Jason Taylor <killerkiwi2005 [at] gmail>
> >>
> >> Create a udev rule....
> >>
> >> See script on this bug
> >> https://bugs.launchpad.net/ubuntu/+source/mythbuntu-meta/+bug/370696
> >>
> >> They got my name wrong in the copyright lol
> >>
> >> 2009/7/17 Graeme Woollett <g.woollett [at] irl>:
> >> > krizze [at] bluezone wrote:
> >> >>> I have a second problem, same system. I have two Hauppauge Nova S
> >> >>> cards
> >> >>> and
> >> >>> a dual Nova T. The cards keep changing their assignments, eg DVBS0
> >> >>> becomes
> >> >>> the Nova T then after a reboot becomes the Nova S.
> >> >>> Can't figure this one out but it sure stuffs up myth.
> >> >>> I also have problems trying to tune one of the nova T, sometimes it
> >> >>> just
> >> >>> sits there and won't tune, other times it flys through.
> >> >>> Aaargh! Help anyone?
> >> >>>
> >> >> One way would be to blacklist the kernel modules the cards are using
> >> >> (/etc/modprobe.d/blacklist afaik). Then you can manually modprobe
> them
> >> >> in
> >> >> order during bootup, e.g. in /etc/rc.local:
> >> >> modprobe module-of-card-1 options=xxx
> >> >> modprobe module-of-card-2 options=xxx
> >> >>
> >> >> I also have problems with tuning on my Nova-T-500, it just stands
> there
> >> >> with no lock, and 0 signal. After a reboot it's OK again, for a cople
> >> >> of
> >> >> hours, if i'm lucky. Guess it's broken or something.
> >> >>
> >> >>
> >> >> Regards,
> >> >> Kristian Haga Karstensen
> >> >>
> >> >>
> >> >>
> >> >> _______________________________________________
> >> >> mythtvnz mailing list
> >> >> mythtvnz [at] lists
> >> >> http://lists.ourshack.com/mailman/listinfo/mythtvnz
> >> >> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
> >> >>
> >> > Make sure you are not running the 1.2 version firmware. A UDev rule
> can
> >> > stop them changing around.
> >> > I had a HVR4000 & Nova T that did this. I found that they only
> changed
> >> > order when I did a warm reboot. Cold booting didn't change them.
> >> > Once the firmware gets loaded they must change the product or vendor
> ID
> >> > and this causes them to be allocated in a different order by the OS.
> >> >
> >> >
> >> >
> >> > --
> >> > Graeme Woollett
> >> > Research Engineer
> >> > Applied Physics and Engineering Team
> >> > Industrial Research Ltd
> >> > ph 04 931 0193
> >> > email g.woollett [at] irl
> >> >
> >> >
> >> > _______________________________________________
> >> > mythtvnz mailing list
> >> > mythtvnz [at] lists
> >> > http://lists.ourshack.com/mailman/listinfo/mythtvnz
> >> > Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
> >> >
> >>
> >>
> >>
> >> --
> >> "Weekends don't count unless you spend them doing something completely
> >> pointless. " - Calven
> >>
> >> _______________________________________________
> >> mythtvnz mailing list
> >> mythtvnz [at] lists
> >> http://lists.ourshack.com/mailman/listinfo/mythtvnz
> >> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
> >
> >
> >
> > --
> >
> > Barry Clearwater
> > Email: barryc [at] bcsystems
> >
> > _______________________________________________
> > mythtvnz mailing list
> > mythtvnz [at] lists
> > http://lists.ourshack.com/mailman/listinfo/mythtvnz
> > Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
> >
> >
>
>
>
> --
> "Weekends don't count unless you spend them doing something completely
> pointless. " - Calven
>
> _______________________________________________
> mythtvnz mailing list
> mythtvnz [at] lists
> http://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>



--

Barry Clearwater
Email: barryc [at] bcsystems


lists at whitehouse

Jul 17, 2009, 3:22 PM

Post #9 of 12 (2218 views)
Permalink
Re: DVB cards changing [In reply to]

Hello,

I wouldn't have thought the composite would make a difference - the
PVR150 has a variety of inputs, but still is only one device node for me.

As Jason says (and he did write the script), it should work to go into
MythTV backend setup when the card is working and see what /dev/ path
the Nova-S card is using. Then type (assuming it is video0):

sudo python udev-rules-jaunty.py /dev/video0 /dev/video_novas

Then go back into MythTV Backend Setup and change the device node from
/debv/video0 to /dev/video_novas. As Jason says, the video0 and video1
will still change, so you need to use the ones that you created (which
will not change) to point MythTV and any LIRC stuff to. Then do the
same for your video1.

LIRC is a pain, but is more difficult with moving tuner cards - try
again once you have a static device node.

(Sorry about the name in the copyright, Jason, I couldn't find your real
one anywhere!)

Regards,

Aaron

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/


nick.rout at gmail

Jul 17, 2009, 3:31 PM

Post #10 of 12 (2215 views)
Permalink
Re: DVB cards changing [In reply to]

On Sat, Jul 18, 2009 at 10:22 AM, Aaron
Whitehouse<lists [at] whitehouse> wrote:
> Hello,
>
> I wouldn't have thought the composite would make a difference - the
> PVR150 has a variety of inputs, but still is only one device node for me.
>
> As Jason says (and he did write the script), it should work to go into
> MythTV backend setup when the card is working and see what /dev/ path
> the Nova-S card is using.  Then type (assuming it is video0):
>
> sudo python udev-rules-jaunty.py   /dev/video0   /dev/video_novas
>
> Then go back into MythTV Backend Setup and change the device node from
> /debv/video0 to /dev/video_novas.  As Jason says, the video0 and video1
> will still change, so you need to use the ones that you created (which
> will not change) to point MythTV and any LIRC stuff to.  Then do the
> same for your video1.
>
> LIRC is a pain, but is more difficult with moving tuner cards - try
> again once you have a static device node.
>
> (Sorry about the name in the copyright, Jason, I couldn't find your real
> one anywhere!)
>
> Regards,
>
> Aaron

The point that Barry needs to realise is that dvb devices do not make
/dev/videoN devices nodes. It makes
/dev/dvb/adaptorN/{demux0,dvr0,frontend0,net0} nodes.

There is a good description of using udev here:

http://www.mythtv.org/wiki/Device_Filenames_and_udev

There is a specific section showing how to set up a dvb device.

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/


killerkiwi2005 at gmail

Jul 18, 2009, 4:07 AM

Post #11 of 12 (2191 views)
Permalink
Re: DVB cards changing [In reply to]

no problem.. didn't expect this script to still be needed the promised
fix still dosnt seem to have landed...

2009/7/18 Aaron Whitehouse <lists [at] whitehouse>:
> Hello,
>
> I wouldn't have thought the composite would make a difference - the
> PVR150 has a variety of inputs, but still is only one device node for me.
>
> As Jason says (and he did write the script), it should work to go into
> MythTV backend setup when the card is working and see what /dev/ path
> the Nova-S card is using.  Then type (assuming it is video0):
>
> sudo python udev-rules-jaunty.py   /dev/video0   /dev/video_novas
>
> Then go back into MythTV Backend Setup and change the device node from
> /debv/video0 to /dev/video_novas.  As Jason says, the video0 and video1
> will still change, so you need to use the ones that you created (which
> will not change) to point MythTV and any LIRC stuff to.  Then do the
> same for your video1.
>
> LIRC is a pain, but is more difficult with moving tuner cards - try
> again once you have a static device node.
>
> (Sorry about the name in the copyright, Jason, I couldn't find your real
> one anywhere!)
>
> Regards,
>
> Aaron
>
> _______________________________________________
> mythtvnz mailing list
> mythtvnz [at] lists
> http://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>



--
"Weekends don't count unless you spend them doing something completely
pointless. " - Calven

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/


krizze at bluezone

Jul 18, 2009, 5:10 AM

Post #12 of 12 (2181 views)
Permalink
Re: DVB cards changing [In reply to]

What you're probably looking for is in /dev/dvb/

-Kristian

PĂ„ Fri, 17 Jul 2009 13:57:10 +0200, skrev Barry Clearwater
<barryc [at] bcsystems>:

> Hmm, not sure.
> I may slightly get it now. The Nova S has a composite video out which is
> probably why I also get /dev/video0 and /dev/video1 but they're not
> really
> what I'm after.
> I may be beating up the wrong runway.
> I can see the cards in the pci bus.
> To be honest very little about this install has gone easy. Lirc is all
> changed, the cards have been mental, and audio has been elusive (Just
> figured out making the master the volume control works). Granted that
> nvidia
> graphics have been easy-ish, EIT off the dish is not too hard but l had a
> large enough headache with trying to get diskless workstations to be
> properly set up - MCC kept crashing for them.
> Yes, its Mythbuntu 9.04 folks.
> Barry
>
> 2009/7/17 Jason Taylor <killerkiwi2005 [at] gmail>
>
>> no problem... the bug says /dev/v4l /* dont work.. I'm assuming thats
>> still true?
>>
>> I've only ever done this with analogue cards but this is what I did
>>
>> sudo python udev-rules-jaunty.py /dev/video0 /dev/video_PVR150a
>> sudo python udev-rules-jaunty.py /dev/video1 /dev/video_PVR150b
>>
>> And that will walk you through the rest
>>
>> Then in myth setup change the devices to /dev/video_PVR150a and
>> /dev/video_PVR150b
>>
>> The /dev/video_ links will then always point to the correct device,
>> the /dev/video0 etc will still change
>>
>> Jason Taylor
>>
>> 2009/7/17 Barry Clearwater <barryc [at] bcsystems>:
>> > Jason, thanks for this. I have only a cursory understanding of the
>> udev
>> > rules, can you give me an example for using your script. I have a
>> > /dev/video0 and /dev/video1 device which are pointed to by
>> > /dev/v4l/by-path/pci-0000:01:06.0-video-index0 and index1 symlinks.
>> > I've found /lib/udev/rules.d/60-persistent-v4l.rules but I'm not sure
>> which
>> > two devices I'm telling your script about - the script asks for an old
>> > device and new device.
>> > In mythtv-setup, i've got dvb devices 0-3 which keep changing (don't
>> know
>> > how they are referenced!) I'm typing all this to try and document it
>> better
>> > for the next "bloke" who thinks he knows what hes doing :-) So thanks
>> for
>> > the script, just need a wee nudge.
>> > Regards
>> > Barry
>> >
>> > 2009/7/17 Jason Taylor <killerkiwi2005 [at] gmail>
>> >>
>> >> Create a udev rule....
>> >>
>> >> See script on this bug
>> >> https://bugs.launchpad.net/ubuntu/+source/mythbuntu-meta/+bug/370696
>> >>
>> >> They got my name wrong in the copyright lol
>> >>
>> >> 2009/7/17 Graeme Woollett <g.woollett [at] irl>:
>> >> > krizze [at] bluezone wrote:
>> >> >>> I have a second problem, same system. I have two Hauppauge Nova S
>> >> >>> cards
>> >> >>> and
>> >> >>> a dual Nova T. The cards keep changing their assignments, eg
>> DVBS0
>> >> >>> becomes
>> >> >>> the Nova T then after a reboot becomes the Nova S.
>> >> >>> Can't figure this one out but it sure stuffs up myth.
>> >> >>> I also have problems trying to tune one of the nova T, sometimes
>> it
>> >> >>> just
>> >> >>> sits there and won't tune, other times it flys through.
>> >> >>> Aaargh! Help anyone?
>> >> >>>
>> >> >> One way would be to blacklist the kernel modules the cards are
>> using
>> >> >> (/etc/modprobe.d/blacklist afaik). Then you can manually modprobe
>> them
>> >> >> in
>> >> >> order during bootup, e.g. in /etc/rc.local:
>> >> >> modprobe module-of-card-1 options=xxx
>> >> >> modprobe module-of-card-2 options=xxx
>> >> >>
>> >> >> I also have problems with tuning on my Nova-T-500, it just stands
>> there
>> >> >> with no lock, and 0 signal. After a reboot it's OK again, for a
>> cople
>> >> >> of
>> >> >> hours, if i'm lucky. Guess it's broken or something.
>> >> >>
>> >> >>
>> >> >> Regards,
>> >> >> Kristian Haga Karstensen
>> >> >>
>> >> >>
>> >> >>
>> >> >> _______________________________________________
>> >> >> mythtvnz mailing list
>> >> >> mythtvnz [at] lists
>> >> >> http://lists.ourshack.com/mailman/listinfo/mythtvnz
>> >> >> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>> >> >>
>> >> > Make sure you are not running the 1.2 version firmware. A UDev
>> rule
>> can
>> >> > stop them changing around.
>> >> > I had a HVR4000 & Nova T that did this. I found that they only
>> changed
>> >> > order when I did a warm reboot. Cold booting didn't change them.
>> >> > Once the firmware gets loaded they must change the product or
>> vendor
>> ID
>> >> > and this causes them to be allocated in a different order by the
>> OS.
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Graeme Woollett
>> >> > Research Engineer
>> >> > Applied Physics and Engineering Team
>> >> > Industrial Research Ltd
>> >> > ph 04 931 0193
>> >> > email g.woollett [at] irl
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > mythtvnz mailing list
>> >> > mythtvnz [at] lists
>> >> > http://lists.ourshack.com/mailman/listinfo/mythtvnz
>> >> > Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> "Weekends don't count unless you spend them doing something
>> completely
>> >> pointless. " - Calven
>> >>
>> >> _______________________________________________
>> >> mythtvnz mailing list
>> >> mythtvnz [at] lists
>> >> http://lists.ourshack.com/mailman/listinfo/mythtvnz
>> >> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>> >
>> >
>> >
>> > --
>> >
>> > Barry Clearwater
>> > Email: barryc [at] bcsystems
>> >
>> > _______________________________________________
>> > mythtvnz mailing list
>> > mythtvnz [at] lists
>> > http://lists.ourshack.com/mailman/listinfo/mythtvnz
>> > Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>> >
>> >
>>
>>
>>
>> --
>> "Weekends don't count unless you spend them doing something completely
>> pointless. " - Calven
>>
>> _______________________________________________
>> mythtvnz mailing list
>> mythtvnz [at] lists
>> http://lists.ourshack.com/mailman/listinfo/mythtvnz
>> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>>
>
>
>


--
Sendt med Operas revolusjonerende e-postprogram: http://www.opera.com/mail/

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

MythTV mythtvnz RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.