View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 48 posts ] 
Go to page Previous  1, 2, 3, 4  Next

Print view Previous topic   Next topic  
Author Message
Search for:
 Post subject:
PostPosted: Mon Mar 12, 2007 12:51 pm 
Offline
Joined: Tue Aug 08, 2006 7:08 pm
Posts: 554
Location: UK
Delete the current symlink, then recreate the symlink in /etc/udev/rules.d with a different prefix, say z20. I don't know if this will solve your problem.

You are able to set permissions as well with UDEV if you are still having problems with them, can you do a ls -l for the /dev/video* devices?

Bruce S.

_________________
Updated 2011/11/19: Athlon64 3700+ Asus A8N4-SLI Deluxe
1Gb PC 3200, 200Gb+250Gb+500Gb SATA HDD,
SATA DVD-RW Optiarc , Gigabyte GV-NX66128DP
Hauppauage Nova-T 500,+ 2x Nova HD S2 LinHes R6.02


Top
 Profile  
 
 Post subject:
PostPosted: Sat Mar 17, 2007 9:49 am 
Offline
Joined: Wed Jun 01, 2005 3:59 pm
Posts: 199
Bruce thanks for continued help.

root@mythtvmasterbackend:~# ls -l /dev/video*
crw-rw---- 1 root video 81, 0 Mar 11 20:42 /dev/video0
crw-rw---- 1 root video 81, 3 Mar 11 20:42 /dev/video03
crw-rw---- 1 root video 81, 4 Mar 11 20:42 /dev/video04
crw-rw---- 1 root video 81, 1 Mar 11 20:42 /dev/video1
crw-rw---- 1 root video 81, 2 Mar 11 20:42 /dev/video2
crw-rw---- 1 root video 81, 24 Mar 11 20:42 /dev/video24
crw-rw---- 1 root video 81, 25 Mar 11 20:42 /dev/video25
crw-rw---- 1 root video 81, 32 Mar 11 20:42 /dev/video32
crw-rw---- 1 root video 81, 33 Mar 11 20:42 /dev/video33


Top
 Profile  
 
 Post subject:
PostPosted: Sat Mar 17, 2007 10:03 am 
Offline
Joined: Wed Jun 01, 2005 3:59 pm
Posts: 199
Hi I ran the command TJC said again for the full card information and it appears that the cards are still registering as /dev/video3 and /dev/video4 not /dev/video03 and /dev/video04. Is this the problem?

root@mythtvmasterbackend:~# dmesg | sed -n '/= START INIT IVTV/,/= *END INIT IVTV/p'
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.8.2 (tagged release) loading
ivtv: Linux version: 2.6.18-chw-13 SMP preempt mod_unload 586 gcc-4.1
ivtv: In case of problems please include the debug info between
ivtv: the START INIT IVTV and END INIT IVTV lines, along with
ivtv: any module options, when mailing the ivtv-users mailinglist.
tveeprom 2-0050: Huh, no eeprom present (err=-121)?
PCI: Enabling device 0000:02:09.2 (0014 -> 0016)
PCI: Found IRQ 10 for device 0000:02:09.2
PCI: Sharing IRQ 10 with 0000:00:1f.3
PCI: Sharing IRQ 10 with 0000:02:09.0
cx88[1]/2: found at 0000:02:09.2, rev: 5, irq: 10, latency: 64, mmio: 0xe6000000
cx88[1]/2: cx2388x based dvb card
DVB: registering new adapter (cx88[1]).
DVB: registering frontend 1 (Oren OR51132 VSB/QAM Frontend)...
PCI: Enabling device 0000:02:09.0 (0014 -> 0016)
PCI: Found IRQ 10 for device 0000:02:09.0
PCI: Sharing IRQ 10 with 0000:00:1f.3
PCI: Sharing IRQ 10 with 0000:02:09.2
cx88[1]/0: found at 0000:02:09.0, rev: 5, irq: 10, latency: 64, mmio: 0xe7000000
cx88[1]/0: registered device video1 [v4l2]
cx88[1]/0: registered device vbi1
cx88[1]/0: registered device radio1
PCI: Enabling device 0000:02:0a.0 (0014 -> 0016)
PCI: Found IRQ 12 for device 0000:02:0a.0
PCI: Sharing IRQ 12 with 0000:02:02.0
PCI: Sharing IRQ 12 with 0000:02:0a.2
PCI: Sharing IRQ 12 with 0000:02:0e.0
CORE cx88[2]: subsystem: 7063:3000, board: pcHDTV HD3000 HDTV [card=22,autodetected]
TV tuner 60 at 0x1fe, Radio tuner -1 at 0x1fe
tuner 3-0043: chip found @ 0x86 (cx88[2])
tda9887 3-0043: tda988[5/6/7] found @ 0x43 (tuner)
tuner 3-0061: chip found @ 0xc2 (cx88[2])
tuner 3-0061: type set to 60 (Thomson DTT 761X (ATSC/NTSC))
cx88[2]/0: found at 0000:02:0a.0, rev: 5, irq: 12, latency: 64, mmio: 0xe5000000
cx88[2]/0: registered device video2 [v4l2]
cx88[2]/0: registered device vbi2
cx88[2]/0: registered device radio2
ivtv0: Autodetected Hauppauge card (cx23416 based)
PCI: Enabling device 0000:02:0b.0 (0014 -> 0016)
PCI: Found IRQ 7 for device 0000:02:0b.0
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
tuner 4-0061: chip found @ 0xc2 (ivtv i2c driver #0)
msp3400 4-0040: MSP4448G-A2 found @ 0x80 (ivtv i2c driver #0)
msp3400 4-0040: MSP4448G-A2 supports radio, mode is autodetect and autoselect
saa7115 4-0021: saa7115 found @ 0x42 (ivtv i2c driver #0)
tveeprom 4-0050: Hauppauge model 32032, rev B310, serial# 6985383
tveeprom 4-0050: tuner model is Philips FI1236 MK2 (idx 10, type 2)
tveeprom 4-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 4-0050: audio processor is MSP4448 (idx 27)
tveeprom 4-0050: decoder processor is SAA7115 (idx 19)
tveeprom 4-0050: has no radio, has IR remote
ivtv0: Autodetected Hauppauge WinTV PVR-250
ivtv0: Encoder revision: 0x02050032
ivtv0: Registered device video3 for encoder MPEG
ivtv0: Registered device video32 for encoder YUV
ivtv0: Registered device vbi3 for encoder VBI
ivtv0: Registered device video24 for encoder PCM audio
tuner 4-0061: type set to 2 (Philips NTSC (FI1236,FM1236 and compatibles))
ivtv0: Initialized Hauppauge WinTV PVR-250, card #0
PCI: Enabling device 0000:02:0a.2 (0014 -> 0016)
PCI: Found IRQ 12 for device 0000:02:0a.2
PCI: Sharing IRQ 12 with 0000:02:02.0
PCI: Sharing IRQ 12 with 0000:02:0a.0
PCI: Sharing IRQ 12 with 0000:02:0e.0
cx88[2]/2: found at 0000:02:0a.2, rev: 5, irq: 12, latency: 64, mmio: 0xe4000000
cx88[2]/2: cx2388x based dvb card
DVB: registering new adapter (cx88[2]).
DVB: registering frontend 2 (Oren OR51132 VSB/QAM Frontend)...
cx2388x blackbird driver version 0.0.6 loaded
ivtv: ====================== NEXT CARD ======================
ivtv1: Autodetected Hauppauge card (cx23416 based)
PCI: Enabling device 0000:02:0e.0 (0014 -> 0016)
PCI: Found IRQ 12 for device 0000:02:0e.0
PCI: Sharing IRQ 12 with 0000:02:02.0
PCI: Sharing IRQ 12 with 0000:02:0a.0
PCI: Sharing IRQ 12 with 0000:02:0a.2
ivtv1: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
tuner 5-0061: chip found @ 0xc2 (ivtv i2c driver #1)
msp3400 5-0040: MSP4448G-A2 found @ 0x80 (ivtv i2c driver #1)
msp3400 5-0040: MSP4448G-A2 supports radio, mode is autodetect and autoselect
saa7115 5-0021: saa7115 found @ 0x42 (ivtv i2c driver #1)
tveeprom 5-0050: Hauppauge model 32032, rev B310, serial# 6984990
tveeprom 5-0050: tuner model is Philips FI1236 MK2 (idx 10, type 2)
tveeprom 5-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 5-0050: audio processor is MSP4448 (idx 27)
tveeprom 5-0050: decoder processor is SAA7115 (idx 19)
tveeprom 5-0050: has no radio, has IR remote
ivtv1: Autodetected Hauppauge WinTV PVR-250
ivtv1: Encoder revision: 0x02050032
ivtv1: Registered device video4 for encoder MPEG
ivtv1: Registered device video33 for encoder YUV
ivtv1: Registered device vbi4 for encoder VBI
ivtv1: Registered device video25 for encoder PCM audio
tuner 5-0061: type set to 2 (Philips NTSC (FI1236,FM1236 and compatibles))
ivtv1: Initialized Hauppauge WinTV PVR-250, card #1
ivtv: ==================== END INIT IVTV ====================
root@mythtvmasterbackend:~#


Top
 Profile  
 
 Post subject:
PostPosted: Sat Mar 17, 2007 10:58 am 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
This is the bit that worries me...
Code:
tveeprom 2-0050: Huh, no eeprom present (err=-121)?

You might want to try Googling that...


Top
 Profile  
 
 Post subject:
PostPosted: Sat Mar 17, 2007 11:24 am 
Offline
Joined: Tue Aug 08, 2006 7:08 pm
Posts: 554
Location: UK
Quote:
Hi I ran the command TJC said again for the full card information and it appears that the cards are still registering as /dev/video3 and /dev/video4 not /dev/video03 and /dev/video04. Is this the problem?

Everything seems to working as it should, the permissions and groups seem to be OK. If you look at video devices '03 and '04 have minor numbers 3 and 4 so that seems to be OK in the ordering.
Remember now, what we are trying to do is to create fixed references to the devices so that the backend can consistently identify them. So that seems to be working.
I cannot understand why those error messages are appearing, doing a grep on mythbackend.log.1 on my box:
Code:
cat /var/log/mythtv/mythbackend.log.1 |grep MPEGRec
2007-03-16 09:00:07.495 MPEGRec(/dev/video) Error: Error getting codec params using old IVTV ioctl
2007-03-16 12:00:07.445 MPEGRec(/dev/video) Error: Error getting codec params using old IVTV ioctl
2007-03-16 19:00:07.495 MPEGRec(/dev/video) Error: Error getting codec params using old IVTV ioctl
2007-03-16 20:00:08.290 MPEGRec(/dev/video) Error: Error getting codec params using old IVTV ioctl
2007-03-16 21:00:08.996 MPEGRec(/dev/video) Error: Error getting codec params using old IVTV ioctl
2007-03-17 00:00:07.683 MPEGRec(/dev/video) Error: Error getting codec params using old IVTV ioctl
2007-03-17 02:00:08.414 MPEGRec(/dev/video) Error: Error getting codec params using old IVTV ioctl
2007-03-17 03:50:08.681 MPEGRec(/dev/video) Error: Error getting codec params using old IVTV ioctl
I get another error message (as have previously mentioned) but everything seems to work OK.

I'm sorry, as we seem to be not getting very far. :?

[fx=scratch-head]Hmm[/fx]

Right, can we try this first? Remove one of your PVRx50s, set it up as on my machine for /dev/video and see what happens?

Bruce S.

Editied to fix formatting

_________________
Updated 2011/11/19: Athlon64 3700+ Asus A8N4-SLI Deluxe
1Gb PC 3200, 200Gb+250Gb+500Gb SATA HDD,
SATA DVD-RW Optiarc , Gigabyte GV-NX66128DP
Hauppauage Nova-T 500,+ 2x Nova HD S2 LinHes R6.02


Last edited by bruce_s01 on Sun Mar 18, 2007 4:14 pm, edited 1 time in total.


Top
 Profile  
 
 Post subject:
PostPosted: Sat Mar 17, 2007 11:59 am 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
bruce_s01 wrote:
I cannot understand why those error messages are appearing, doing a grep on mythbackend.log.1 on my box: [code]cat /var/log/mythtv/mythbackend.log.1 |grep MPEGRec
2007-03-16 09:00:07.495 MPEGRec(/dev/video) Error: Error getting codec params using old IVTV ioctl
2007-03-16 12:00:07.445 MPEGRec(/dev/video) Error: Error getting codec[code]

Make sure you've got the updated /etc/init.d/set_ivtv_params script I posted and that the cfg-* files under /etc/sysconfig/ivtv correspond to the correct video devices...


Top
 Profile  
 
 Post subject:
PostPosted: Sat Mar 17, 2007 12:05 pm 
Offline
Joined: Wed Jun 01, 2005 3:59 pm
Posts: 199
TJC googling that error appears to be some kernel bugs . I also found it related to an error with BTTV cards. Here is post about the kernel one I am not sure its related.

tveeprom 2-0050: Huh, no eeprom present (err=-121)? cx88[0]/0: found at 0000:05:08.0, rev: 3, irq: 18, latency: 32, mmio: 0xd0000000

On Tuesday December 12, hancockr@xxxxxxx wrote:
> Seeing this oops on 2.6.19-rc6-mm2 intermittently on bootup. Also, when
> this doesn't happen it seems like udev goes crazy adding and removing
> /dev/md0 over and over using up a ton of CPU. Is this a known problem?
> This also happened with -mm1.

Yes.... There is a patch in -mm called
md-change-lifetime-rules-for-md-devices.patch

which tries to remove md devices when they are no longer needed.
However it is racy, and it seems to be impossible to close the race
without making changes in core code as well.

For now, just revert that patch.
Andrew: you can drop that patch and the two related one. This is
going to need a lot more thought, and I'm not sure it is worth it
at the moment.

Thanks,
NeilBrown
-


Top
 Profile  
 
 Post subject:
PostPosted: Sat Mar 17, 2007 12:10 pm 
Offline
Joined: Wed Jun 01, 2005 3:59 pm
Posts: 199
TJC when you wrote

Make sure you've got the updated /etc/init.d/set_ivtv_params script I posted and that the cfg-* files under /etc/sysconfig/ivtv correspond to the correct video devices...

that was for Bruce errors right.


Should I just wipe the existing build and do a clean install. It will be a pain in the but, but this is going nowhere.

TJC did cecil ever update the LINHES document for the latest build. Its kinda confusing and I have had some issues with getting NFS setup properly.


Top
 Profile  
 
 Post subject:
PostPosted: Sat Mar 17, 2007 12:25 pm 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
alexvd wrote:
TJC when you wrote ... that was for Bruce errors right.

Yes. I try to be explict about this but a quote usually indicates I'm responding to that person or reinforcing what they're saying.
alexvd wrote:
TJC did cecil ever update the LINHES document for the latest build. Its kinda confusing and I have had some issues with getting NFS setup properly.

Not sure. I think it may be mildly out of date, but the known changes in the upgrade hints try to cover most of the potential issues I know about. I seem to remember something about changing the way the way you set up mysql for remote access which may not be covered there, but since I'm only running a single server setup my expertise on remote FEs and slave BEs is very limited.


Top
 Profile  
 
 Post subject:
PostPosted: Sun Mar 18, 2007 4:12 pm 
Offline
Joined: Tue Aug 08, 2006 7:08 pm
Posts: 554
Location: UK
Quote:
Make sure you've got the updated /etc/init.d/set_ivtv_params script I posted and that the cfg-* files under /etc/sysconfig/ivtv correspond to the correct video devices...


I've modified the set_ivtv_params file, haven't tried it out yet.

Bruce S.

Edited to fix formatting.

_________________
Updated 2011/11/19: Athlon64 3700+ Asus A8N4-SLI Deluxe
1Gb PC 3200, 200Gb+250Gb+500Gb SATA HDD,
SATA DVD-RW Optiarc , Gigabyte GV-NX66128DP
Hauppauage Nova-T 500,+ 2x Nova HD S2 LinHes R6.02


Top
 Profile  
 
 Post subject:
PostPosted: Thu Jun 28, 2007 4:42 am 
Offline
Joined: Thu Feb 24, 2005 2:50 am
Posts: 58
Speaking of udev video device ordering issues, FYI here's an example udev configuration file I ended up creating in a system with multiple tuners. In this case it is simply creating new symlinks during boot to the randomly-selected udev video device numbers, instead of trying to override udev's selection (which I had problems with). Then these fixed-name symlinks must be specified as the tuner devices in mythtv setup.
Code:
# Mark's local.rules file for video device naming consistency -
# Put in /etc/udev, and create a z90_local.rules symlink in udev/rules.d to this file -
# Then manually enter /dev/video-pvr150 etc when adding tuners in myth setup -
# "ID" numbers below are dependent on PCI slot position

KERNEL=="video[0-9]", SYSFS{name}=="saa7133_0_ video*", SYMLINK+="video-kworld"

KERNEL=="video[0-9]", SYSFS{name}=="cx88*", DRIVERS=="cx88*", SYMLINK+="video-pcHDTV"

KERNEL=="video[0-9]", SYSFS{name}=="ivtv? encoder MPEG", ID=="0000:02:01.0", DRIVERS=="ivtv", SYMLINK+="video-pvr250"

KERNEL=="video[0-9]", SYSFS{name}=="ivtv? encoder MPEG", ID=="0000:02:02.0", DRIVERS=="ivtv", SYMLINK+="video-pvr150"

I haven't noticed any "MPEG controls" errors so I can't comment on that facet of this post.


Top
 Profile  
 
 Post subject:
PostPosted: Thu Jun 28, 2007 6:50 am 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
no2u - This is a really useful bit of info. Could you do a more detailed "drunk monkey" tutorial (how to get the PCI device IDs, which screens in mythtv-setup to enter these names on, ...) for the newbies, maybe even hang it off the troubleshooting page on the wiki? Thanks!


Top
 Profile  
 
 Post subject:
PostPosted: Thu Jun 28, 2007 10:21 am 
Offline
Joined: Tue Aug 08, 2006 7:08 pm
Posts: 554
Location: UK
no2u wrote:
Speaking of udev video device ordering issues, FYI here's an example udev configuration file I ended up creating in a system with multiple tuners. In this case it is simply creating new symlinks during boot to the randomly-selected udev video device numbers, instead of trying to override udev's selection (which I had problems with). Then these fixed-name symlinks must be specified as the tuner devices in mythtv setup.
Code:
# Mark's local.rules file for video device naming consistency -
# Put in /etc/udev, and create a z90_local.rules symlink in udev/rules.d to this file -
# Then manually enter /dev/video-pvr150 etc when adding tuners in myth setup -
# "ID" numbers below are dependent on PCI slot position

KERNEL=="video[0-9]", SYSFS{name}=="saa7133_0_ video*", SYMLINK+="video-kworld"

KERNEL=="video[0-9]", SYSFS{name}=="cx88*", DRIVERS=="cx88*", SYMLINK+="video-pcHDTV"

KERNEL=="video[0-9]", SYSFS{name}=="ivtv? encoder MPEG", ID=="0000:02:01.0", DRIVERS=="ivtv", SYMLINK+="video-pvr250"

KERNEL=="video[0-9]", SYSFS{name}=="ivtv? encoder MPEG", ID=="0000:02:02.0", DRIVERS=="ivtv", SYMLINK+="video-pvr150"

I haven't noticed any "MPEG controls" errors so I can't comment on that facet of this post.


Great work!
You managed to get the symlinks to work, I saw that they would appear, but I could never select them in mythtv-setup, so I had to resort mucking about with the devices.
How did you manage to enter the symlinks, as I recall there is only a dropdown menu?

I wonder if there is a way of scripting this, as the KnoppMyth card detection on boot up, seems to keep the same device order.

Bruce S.

_________________
Updated 2011/11/19: Athlon64 3700+ Asus A8N4-SLI Deluxe
1Gb PC 3200, 200Gb+250Gb+500Gb SATA HDD,
SATA DVD-RW Optiarc , Gigabyte GV-NX66128DP
Hauppauage Nova-T 500,+ 2x Nova HD S2 LinHes R6.02


Top
 Profile  
 
 Post subject:
PostPosted: Thu Jun 28, 2007 12:57 pm 
Offline
Joined: Thu Feb 24, 2005 2:50 am
Posts: 58
TJC: Good idea; will try to summarize my findings in a single post if I get a chance.

Bruce: The video device selection in "Add Tuner" in MythTV Setup "looks" like a drop-down box, but actually you can type in any device path you like. After you type it in, the device is queried and it'll confirm the actual model of the device on the screen for confirmation (at least in the case of a Hauppauge card) or it will tell you that the device wasn't found if you type it in incorrectly.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Jun 29, 2007 4:45 pm 
Offline
Joined: Wed Jun 01, 2005 3:59 pm
Posts: 199
thanks I am going to try this with the one card that keeps giving me problems.


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 48 posts ] 
Go to page Previous  1, 2, 3, 4  Next



All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 4 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu